From owner-freebsd-current Sat May 8 13:18:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 566D714FAB for ; Sat, 8 May 1999 13:18:16 -0700 (PDT) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id QAA03343; Sat, 8 May 1999 16:18:08 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Sat, 8 May 1999 16:18:07 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Mike Holling Cc: current@freebsd.org Subject: Re: RTP and RTSP support in libalias? 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 understand it, RTP is only a framework for a protocol, and not actually a protocol. I.e., they define some headers, but no delivery semantics. There are some RFC's that talk about how to put various video/audio formats on top, but I think they have explicitely avoided talking about things like redelivery, loss, etc, so there may not be enough information to do a generic RTP implementation. Instead, it may have to be written for each application that runs on top. On Wed, 5 May 1999, Mike Holling wrote: > Apple's QuickTime 4 uses these protocols for streaming QuickTime, and I've > got users asking me if the FreeBSD NAT box can be made to handle it. > Looks like these protocols are new internet standards, has anyone > integrated them into libalias yet? If not I might give it a shot, but I'm > probably in over my head... > > - Mike > > PS. Apple provides links to the RFCs: > > http://www.apple.com/quicktime/resources/qt4/us/proxy/proxy.html > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 13:48:36 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 B87BE151FB for ; Sat, 8 May 1999 13:48:28 -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 NAA09253; Sat, 8 May 1999 13:48:26 -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 NAA34474; Sat, 8 May 1999 13:48:26 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sat, 8 May 1999 13:48:26 -0700 (PDT) Message-Id: <199905082048.NAA34474@vashon.polstra.com> To: zach@uffdaonline.net Subject: Re: Disappearing/Reappearing Files... In-Reply-To: <19990507163249.A2406@k6n1.znh.org> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990507163249.A2406@k6n1.znh.org>, Zach Heilig wrote: > This is an example of what I just noticed: > > $ ls > aaa bbb ccc > $ cp aaa bbb > $ ls > aaa ccc > [ !!!, then a couple seconds later: ] > $ ls > aaa bbb ccc > > [a few (>5) minutes later in a different vty: ] > $ cd problem_dir > $ ls > aaa ccc > [ ugh.. ] > $ ls > aaa bbb ccc > > [this is a filesystem with soft-updates on] I'm seeing something possibly related (possibly not) on an Alpha with this morning's -current. First I was getting unaligned accesses and core dumps from the "cp" in /etc/rc that updates the /etc/motd file. (I added "set -v" to /etc/rc to catch it.) But I could do the copy by hand once the system was up. Now on the latest reboot I got this from it: + cp /tmp/_motd /etc/motd + chmod 644 /etc/motd chmod: : No such file or directory chmod in free(): warning: recursive call chmod in free(): warning: recursive call chmod in free(): warning: recursive call chmod in free(): warning: recursive call (Hmm, why didn't the filename come out in chmod's error message?) I'm running with soft-updates but I'll try turning them off. 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 May 8 14: 1: 5 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 31721151FB for ; Sat, 8 May 1999 14:00:58 -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 RAA19461; Sat, 8 May 1999 17:01:01 -0400 (EDT) Date: Sat, 8 May 1999 17:01:00 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Lee Cremeans Cc: current@FreeBSD.ORG Subject: Re: IDE strangeness In-Reply-To: <19990506223902.A428@erols.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, 6 May 1999, Lee Cremeans wrote: > On Thu, May 06, 1999 at 10:04:19PM -0400, Brian Feldman wrote: > > > 2. wd supports UDMA on my chipset, but won't enable any kind of DMA on my > > new Seagate, which does UDMA2 fine with ATA > > > > Can you boot -v and give the output of the ATA_INQUIRY line? That should say > which modes are available on the drive. So, any ideas at all? > > -lee > > -- > +--------------------------------------------------------------------+ > | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) | > | lcremeans@erols.com | http://wakky.dyndns.org/~lee | > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 Sat May 8 14: 9:25 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 6265E14C0E for ; Sat, 8 May 1999 14:09:17 -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 RAA19530; Sat, 8 May 1999 17:09:06 -0400 (EDT) Date: Sat, 8 May 1999 17:09:06 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Jordan K. Hubbard" Cc: Matthew Thyer , current@FreeBSD.ORG Subject: Re: Doesn't anyone care about the broken sio ?? In-Reply-To: <22229.926181448@zippy.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 Sat, 8 May 1999, Jordan K. Hubbard wrote: > > I mailed a simple way to reproduce the serious brokeness of the > > serial port driver on my system and no one responds. > > > > What does this mean ? > > It means that nobody is probably willing to go bring up a MAME > environment just to test this. You need to isolate it to a more > minimal test case if you want people to jump on what could be a local > problem (some serial hardware is better behaved than others) or a > misbehaving X server (which is masking interrupts for too long; see > mailing list archives on this topic). The more complex your > reproduction case, in other words, the less likely it is that anyone > will respond to it. Hmm, so now you're the second to cite the possibility of X masking interrupts too long, eh? ;) Actually, I use MAME all the time, and this problem does NOT occur (XF86_SVGA on an S3 ViRGE/DX). Oh, user-ppp too of course. If I could have reproduced this problem, I would have replied. > > If you can say "here's a small stand-alone C program which hogs things > to the extent that the serial driver seriously overruns its buffers" > then it's likely that someone will be at least motivated to compile, > run and try it. If it involves running some esoteric application > which requires downloading data of questionable legality on top of it, > it's far less likely that anyone will even bother to look. MAME is a great piece of software, and in and of itself entirely legal; what problem do you have with it? > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 Sat May 8 14:11:20 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 5CB6415453 for ; Sat, 8 May 1999 14:11:11 -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 OAA09375 for ; Sat, 8 May 1999 14:11:10 -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 OAA34534; Sat, 8 May 1999 14:11:10 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sat, 8 May 1999 14:11:10 -0700 (PDT) Message-Id: <199905082111.OAA34534@vashon.polstra.com> To: current@freebsd.org Subject: Re: Disappearing/Reappearing Files... In-Reply-To: <199905082048.NAA34474@vashon.polstra.com> Organization: Polstra & Co., Seattle, WA Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199905082048.NAA34474@vashon.polstra.com>, John Polstra wrote: > > I'm seeing something possibly related (possibly not) on an Alpha with > this morning's -current. First I was getting unaligned accesses and > core dumps from the "cp" in /etc/rc that updates the /etc/motd file. > (I added "set -v" to /etc/rc to catch it.) But I could do the copy by > hand once the system was up. Now on the latest reboot I got this from > it: > > + cp /tmp/_motd /etc/motd > + chmod 644 /etc/motd > chmod: : No such file or directory > chmod in free(): warning: recursive call > chmod in free(): warning: recursive call > chmod in free(): warning: recursive call > chmod in free(): warning: recursive call > > (Hmm, why didn't the filename come out in chmod's error message?) > > I'm running with soft-updates but I'll try turning them off. I tried about 10 reboots, half with and half without soft-updates enabled on the various filesystems. With soft-updates disabled, I didn't see the above problem at all. With soft-updates enabled, I saw it most of the time but not always. 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 May 8 14:19:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 21C16154AD for ; Sat, 8 May 1999 14:19:33 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id XAA09594 for ; Sat, 8 May 1999 23:19:28 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma009592; Sat, 8 May 99 23:19:29 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id XAA16520 for ; Sat, 8 May 1999 23:19:28 +0200 (MET DST) Received: (qmail 93766 invoked by uid 666); 8 May 1999 21:19:49 -0000 Date: Sat, 8 May 1999 23:19:49 +0200 From: Jos Backus To: current@freebsd.org Subject: Re: mountroot problem Message-ID: <19990508231949.A93718@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990508202536.A92612@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990508202536.A92612@hal.mpn.cp.philips.com>; from Jos Backus on Sat, May 08, 1999 at 08:25:36PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some more information: In sys/i386/i386/autoconf I'm seeing the following happen: static void setroot() { int majdev, mindev, unit, slice, part; dev_t newrootdev; char partname[2]; char *sname; if (boothowto & RB_DFLTROOT || (bootdev & B_MAGICMASK) != B_DEVMAGIC) return; majdev = B_TYPE(bootdev); printf("setroot: majdev=%d,bdevsw(majdev)=%p\n",majdev,bdevsw(majdev)); if (majdev >= nblkdev || bdevsw(majdev) == NULL) return; unit = B_UNIT(bootdev); slice = B_SLICE(bootdev); etc. which prints setroot: majdev=4,bdevsw(majdev)=0 Thus the function returns, without setting the name of the root device further on in the code (it would appear that that is where it happens). -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 15: 1:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 5B7F914CF7; Sat, 8 May 1999 15:01:24 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id RAA24414; Sat, 8 May 1999 17:01:23 -0500 (CDT) Date: Sat, 8 May 1999 17:01:22 -0500 (CDT) From: Steve Price To: brian@freebsd.org Cc: freebsd-current@freebsd.org Subject: latest ppp with PAP/CHAP coredumps Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1526973917-926200882=:24681" 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-1526973917-926200882=:24681 Content-Type: TEXT/PLAIN; charset=US-ASCII Brian, I CVSup'd earlier this morning and did a 'make world' on my -current box. If I try to use PAP/CHAP authentication, then ppp coredumps. Without using PAP/CHAP it seems to work fine. It also works when I did a cd /usr/src/usr.sbin/ppp cvs update -Dyesterday -PAd make clean && make && make install I haven't done a whole lot of investigation yet, but I did attach a copy of my ppp.conf, a stacktrace, and the tail(1) of /var/log/ppp.log. Any ideas on what might be happening? Thanks. -steve --0-1526973917-926200882=:24681 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; name=typescript Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: typescript Content-Disposition: attachment; filename=typescript U2NyaXB0IHN0YXJ0ZWQgb24gU2F0IE1heSAgOCAxNjozODoxOCAxOTk5DQpi b25zYWkjIGNhdCAvZXRjL3BwcC9wcHAuY29uZg0KZGVmYXVsdDoNCiBzZXQg bG9nIFBoYXNlIENoYXQgTENQIElQQ1AgQ0NQIHR1biBjb21tYW5kDQogc2V0 IGRldmljZSAvZGV2L21vZGVtDQogc2V0IHNwZWVkIDExNTIwMA0KIHNldCBk aWFsICJBQk9SVCBCVVNZIEFCT1JUIE5PXFxzQ0FSUklFUiBUSU1FT1VUIDUg XCJcIiBBVCBPSy1BVC1PSyBBVEUxUTAgT0sgXFxkQVREVFxcVCBUSU1FT1VU IDQwIENPTk5FQ1QiDQoNCmlzcDoNCiBzZXQgcGhvbmUgNTU1MTIzNA0KIHNl dCB0aW1lb3V0IDANCiBzZXQgYXV0aG5hbWUgbXlhdXRoDQogc2V0IGF1dGhr ZXkgbXlrZXkNCmJvbnNhaSMgcHBwDQpXb3JraW5nIGluIGludGVyYWN0aXZl IG1vZGUNClVzaW5nIGludGVyZmFjZTogdHVuMA0KcHBwIE9OIGJvbnNhaT4g ZGlhbCBpc3ANCnBwcCBPTiBib25zYWk+IA0KUHBwIE9OIGJvbnNhaT4gDQpQ UHAgT04gYm9uc2FpPiBTZWdtZW50YXRpb24gZmF1bHQgKGNvcmUgZHVtcGVk KQ0KYm9uc2FpIyBnZGIgYHdoaWNoIHBwcGAgcHBwLmNvcmUNCkdOVSBnZGIg NC4xOA0KQ29weXJpZ2h0IDE5OTggRnJlZSBTb2Z0d2FyZSBGb3VuZGF0aW9u LCBJbmMuDQpHREIgaXMgZnJlZSBzb2Z0d2FyZSwgY292ZXJlZCBieSB0aGUg R05VIEdlbmVyYWwgUHVibGljIExpY2Vuc2UsIGFuZCB5b3UgYXJlDQp3ZWxj b21lIHRvIGNoYW5nZSBpdCBhbmQvb3IgZGlzdHJpYnV0ZSBjb3BpZXMgb2Yg aXQgdW5kZXIgY2VydGFpbiBjb25kaXRpb25zLg0KVHlwZSAic2hvdyBjb3B5 aW5nIiB0byBzZWUgdGhlIGNvbmRpdGlvbnMuDQpUaGVyZSBpcyBhYnNvbHV0 ZWx5IG5vIHdhcnJhbnR5IGZvciBHREIuICBUeXBlICJzaG93IHdhcnJhbnR5 IiBmb3IgZGV0YWlscy4NClRoaXMgR0RCIHdhcyBjb25maWd1cmVkIGFzICJp Mzg2LXVua25vd24tZnJlZWJzZCIuLi4NCkNvcmUgd2FzIGdlbmVyYXRlZCBi eSBgcHBwJy4NClByb2dyYW0gdGVybWluYXRlZCB3aXRoIHNpZ25hbCAxMSwg U2VnbWVudGF0aW9uIGZhdWx0Lg0KUmVhZGluZyBzeW1ib2xzIGZyb20gL3Vz ci9saWIvbGliY3J5cHQuc28uMi4uLmRvbmUuDQpSZWFkaW5nIHN5bWJvbHMg ZnJvbSAvdXNyL2xpYi9saWJtZC5zby4yLi4uZG9uZS4NClJlYWRpbmcgc3lt Ym9scyBmcm9tIC91c3IvbGliL2xpYnV0aWwuc28uMi4uLmRvbmUuDQpSZWFk aW5nIHN5bWJvbHMgZnJvbSAvdXNyL2xpYi9saWJ6LnNvLjIuLi5kb25lLg0K UmVhZGluZyBzeW1ib2xzIGZyb20gL3Vzci9saWIvbGliYWxpYXMuc28uMy4u LmRvbmUuDQpSZWFkaW5nIHN5bWJvbHMgZnJvbSAvdXNyL2xpYi9saWJkZXMu c28uMy4uLmRvbmUuDQpSZWFkaW5nIHN5bWJvbHMgZnJvbSAvdXNyL2xpYi9s aWJyYWRpdXMuc28uMS4uLmRvbmUuDQpSZWFkaW5nIHN5bWJvbHMgZnJvbSAv dXNyL2xpYi9saWJjLnNvLjMuLi5kb25lLg0KUmVhZGluZyBzeW1ib2xzIGZy b20gL3Vzci9saWJleGVjL2xkLWVsZi5zby4xLi4uZG9uZS4NCiMwICAweDgw NWI1MTkgaW4gRnNtUmVjdkNvbmZpZ1JlaiAoZnA9MHg4MGFlNjA4LCBsaHA9 MHhiZmJmY2U5OCwgYnA9MHgwKQ0KICAgIGF0IGZzbS5jOjc5NQ0KNzk1CSAg KCpmcC0+Zm4tPkRlY29kZUNvbmZpZykoZnAsIE1CVUZfQ1RPUChicCksIGZs ZW4sIE1PREVfUkVKLCAmZGVjKTsNCihnZGIpIHdoZXJlDQojMCAgMHg4MDVi NTE5IGluIEZzbVJlY3ZDb25maWdSZWogKGZwPTB4ODBhZTYwOCwgbGhwPTB4 YmZiZmNlOTgsIGJwPTB4MCkNCiAgICBhdCBmc20uYzo3OTUNCiMxICAweDgw NWJhMTkgaW4gZnNtX0lucHV0IChmcD0weDgwYWU2MDgsIGJwPTB4ODA5NTEy MCkgYXQgZnNtLmM6MTAwOA0KIzIgIDB4ODA1MDE5MSBpbiBjY3BfSW5wdXQg KGJ1bmRsZT0weDgwN2ZmNjAsIGw9MHg4MGFlMDAwLCBicD0weDgwOTUxMjAp DQogICAgYXQgY2NwLmM6NTQwDQojMyAgMHg4MDYyNzBlIGluIERlc3BhdGNo IChidW5kbGU9MHg4MDdmZjYwLCBsPTB4ODBhZTAwMCwgYnA9MHg4MDk1MTIw LCANCiAgICBwcm90bz0zMzAyMSkgYXQgbGluay5jOjMyMg0KIzQgIDB4ODA2 MjYzOCBpbiBsaW5rX1B1bGxQYWNrZXQgKGw9MHg4MGFlMDAwLCBidWY9MHg4 MGIwODc0ICJ+XDIwMP1cMDA0XDAwMiIsIA0KICAgIGxlbj0zMiwgYj0weDgw N2ZmNjApIGF0IGxpbmsuYzoyNzANCiM1ICAweDgwNjc2ZWUgaW4gcGh5c2lj YWxfRGVzY3JpcHRvclJlYWQgKGQ9MHg4MGFlNzQwLCBidW5kbGU9MHg4MDdm ZjYwLCANCiAgICBmZHNldD0weGJmYmZkOTA0KSBhdCBwaHlzaWNhbC5jOjQ3 MA0KIzYgIDB4ODA1NmU3MSBpbiBkYXRhbGlua19SZWFkIChkPTB4ODBhYzAw MCwgYnVuZGxlPTB4ODA3ZmY2MCwgDQogICAgZmRzZXQ9MHhiZmJmZDkwNCkg YXQgZGF0YWxpbmsuYzo0MTcNCiM3ICAweDgwNGM1OGUgaW4gYnVuZGxlX0Rl c2NyaXB0b3JSZWFkIChkPTB4ODA3ZmY2MCwgYnVuZGxlPTB4ODA3ZmY2MCwg DQogICAgZmRzZXQ9MHhiZmJmZDkwNCkgYXQgYnVuZGxlLmM6NjA0DQojOCAg MHg4MDY0NWZiIGluIERvTG9vcCAoYnVuZGxlPTB4ODA3ZmY2MCkgYXQgbWFp bi5jOjU1Nw0KIzkgIDB4ODA2NDI3YSBpbiBtYWluIChhcmdjPTEsIGFyZ3Y9 MHhiZmJmZGFjMCkgYXQgbWFpbi5jOjQ0Nw0KIzEwIDB4ODA0YTlkMSBpbiBf c3RhcnQgKCkNCihnZGIpIHF1aXQNCmJvbnNhaSMgdGFpbCAvdmFyL2xvZy9w cHAubG9nDQpNYXkgIDggMTY6Mzk6MDUgYm9uc2FpIHBwcFsxMDI0XTogdHVu MDogQ0NQOiAgUFJFRDFbMl0gIA0KTWF5ICA4IDE2OjM5OjA1IGJvbnNhaSBw cHBbMTAyNF06IHR1bjA6IENDUDogZGVmbGluazogU2VuZENvbmZpZ1JlcSgy KSBzdGF0ZSA9IFJlcS1TZW50IA0KTWF5ICA4IDE2OjM5OjA1IGJvbnNhaSBw cHBbMTAyNF06IHR1bjA6IENDUDogICBbRU1QVFldIA0KTWF5ICA4IDE2OjM5 OjA1IGJvbnNhaSBwcHBbMTAyNF06IHR1bjA6IElQQ1A6IGRlZmxpbms6IFJl Y3ZDb25maWdOYWsoMSkgc3RhdGUgPSBBY2stU2VudCANCk1heSAgOCAxNjoz OTowNSBib25zYWkgcHBwWzEwMjRdOiB0dW4wOiBJUENQOiAgSVBBRERSWzZd ICBhYWEuYmJiLmNjYy5kZGQNCk1heSAgOCAxNjozOTowNSBib25zYWkgcHBw WzEwMjRdOiB0dW4wOiBJUENQOiAgSVBBRERSWzZdICBjaGFuZ2luZyBhZGRy ZXNzOiAxMjcuMC4wLjEgIC0tPiBhYWEuYmJiLmNjYy5kZGQgDQpNYXkgIDgg MTY6Mzk6MDUgYm9uc2FpIHBwcFsxMDI0XTogdHVuMDogSVBDUDogZGVmbGlu azogU2VuZENvbmZpZ1JlcSgyKSBzdGF0ZSA9IEFjay1TZW50IA0KTWF5ICA4 IDE2OjM5OjA1IGJvbnNhaSBwcHBbMTAyNF06IHR1bjA6IElQQ1A6ICBJUEFE RFJbNl0gIGFhYS5iYmIuY2NjLmRkZA0KTWF5ICA4IDE2OjM5OjA1IGJvbnNh aSBwcHBbMTAyNF06IHR1bjA6IElQQ1A6ICBDT01QUFJPVE9bNl0gIDE2IFZK IHNsb3RzIHdpdGggc2xvdCBjb21wcmVzc2lvbiANCk1heSAgOCAxNjozOTow NSBib25zYWkgcHBwWzEwMjRdOiB0dW4wOiBDQ1A6IGRlZmxpbms6IFJlY3ZD b25maWdSZWooMikgc3RhdGUgPSBSZXEtU2VudCANCmJvbnNhaSMgZXhpdA0K DQpTY3JpcHQgZG9uZSBvbiBTYXQgTWF5ICA4IDE2OjM5OjU0IDE5OTkNCg== --0-1526973917-926200882=:24681-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 15:28:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from pez.hyperreal.org (pez.hyperreal.org [207.181.224.6]) by hub.freebsd.org (Postfix) with SMTP id 6E35614E94 for ; Sat, 8 May 1999 15:28:08 -0700 (PDT) (envelope-from brian@hyperreal.org) Received: (qmail 7379 invoked by uid 4000); 8 May 1999 22:29:57 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 May 1999 22:29:57 -0000 Date: Sat, 8 May 1999 15:29:57 -0700 (PDT) From: Brian Behlendorf To: current@freebsd.org Subject: haveseen_isadev 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 seeing the following at boot (from a world built Wednesday night): ... chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 4.0 on pci0 ide_pci0: at device 4.1 on pci0 chip2: at device 4.3 on pci0 ahc0: at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: interrupting at irq 12 xl0: <3Com 3c905-TX Fast Etherlink XL> at device 9.0 on pci0 xl0: interrupting at irq 12 xl0: Ethernet address: 00:60:08:a3:51:e8 xl0: autoneg complete, link status good (half-duplex, 10Mbps) ahc1: at device 10.0 on pci0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: interrupting at irq 10 xl1: <3Com 3c905B-TX Fast Etherlink XL> at device 12.0 on pci0 xl1: interrupting at irq 11 xl1: Ethernet address: 00:10:5a:a7:e5:45 xl1: autoneg complete, link status good (half-duplex, 10Mbps) eisa0: on motherboard isa0: on motherboard fdc0: interrupting at irq 6 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: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S wdc0: interrupting at irq 14 haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! bt_isa_probe: Probe failed for card at 0x330 bt_isa_probe: Probe failed for card at 0x334 bt_isa_probe: Probe failed for card at 0x230 bt_isa_probe: Probe failed for card at 0x234 bt_isa_probe: Probe failed for card at 0x130 bt_isa_probe: Probe failed for card at 0x134 haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! haveseen_isadev() called - FIXME! atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 vga0: on isa0 ... Here's a diff between my kernel and GENERIC: 21c21 < ident TURBO --- > ident GENERIC 190c190 < pseudo-device pty 64 --- > pseudo-device pty 16 225,243d224 < < #### custom additions! < options MD5 < options PERFMON < < # Network options. NMBCLUSTERS defines the number of mbuf clusters and < # defaults to 256. This machine is a server that handles lots of traffic, < # so we crank that value. < options NMBCLUSTERS=4096 # mbuf clusters at 4096 < < # < # Misc. options < # < pseudo-device ccd 4 #Concatenated disk driver < options IPFIREWALL < options IPDIVERT < options ICMP_BANDLIM < options DUMMYNET < options BRIDGE Am I missing a device or controller line somewhere? Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 15:39:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-gw2adm.rcsntx.swbell.net (mail-gw2.rcsntx.swbell.net [151.164.30.52]) by hub.freebsd.org (Postfix) with ESMTP id 8956C14DC7; Sat, 8 May 1999 15:39:45 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ppp-207-193-10-165.hstntx.swbell.net [207.193.10.165]) by mail-gw2adm.rcsntx.swbell.net (8.8.5/8.8.5) with ESMTP id RAA03837; Sat, 8 May 1999 17:39:35 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id RAA00812; Sat, 8 May 1999 17:40:32 -0500 (CDT) (envelope-from chris) Date: Sat, 8 May 1999 17:40:22 -0500 From: Chris Costello To: Steve Price Cc: brian@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: latest ppp with PAP/CHAP coredumps Message-ID: <19990508174022.B471@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.1i In-Reply-To: ; from Steve Price on Sat, May 08, 1999 at 05:01:22PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 8, 1999, Steve Price wrote: > Program terminated with signal 11, Segmentation fault. > Reading symbols from /usr/lib/libcrypt.so.2...done. > Reading symbols from /usr/lib/libmd.so.2...done. > Reading symbols from /usr/lib/libutil.so.2...done. > Reading symbols from /usr/lib/libz.so.2...done. > Reading symbols from /usr/lib/libalias.so.3...done. > Reading symbols from /usr/lib/libdes.so.3...done. > Reading symbols from /usr/lib/libradius.so.1...done. > Reading symbols from /usr/lib/libc.so.3...done. > Reading symbols from /usr/libexec/ld-elf.so.1...done. > #0 0x805b519 in FsmRecvConfigRej (fp=0x80ae608, lhp=0xbfbfce98, bp=0x0) ^^^^^^ > at fsm.c:795 > 795 (*fp->fn->DecodeConfig)(fp, MBUF_CTOP(bp), flen, MODE_REJ, &dec); fp->fn->DecodeConfig should point to something that checks for a null pointer, or make FsmRecvConfigRej check something like... if (!bp || (bp && !*bp)) { return -1; } or something to that effect. -- Chris Costello Avoid temporary variables and strange women. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 15:42:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.bezeqint.net (mail1.bezeqint.net [192.115.106.20]) by hub.freebsd.org (Postfix) with ESMTP id AA01514DC7 for ; Sat, 8 May 1999 15:42:35 -0700 (PDT) (envelope-from Important_for@YourLife.com) Received: from yourlife.com ([212.25.115.5]) by mail1.bezeqint.net (Sun Internet Mail Server sims.3.5.1999.03.02.17.58.p5) with SMTP id <0FBF00MDNK99I4@mail1.bezeqint.net> for current@freebsd.org; Sun, 9 May 1999 01:20:47 +0300 (IDT) Date: Sun, 09 May 1999 01:20:42 +0300 (IDT) Date-warning: Date header was inserted by mail1.bezeqint.net From: Important_for@YourLife.com Subject: Why Jews Don't Beleive in ... To: Important_for@YourLife.com Message-id: <0FBF00M38Q2EI4@mail1.bezeqint.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Friend, Did you ever wonder why the Jewish people don't believe in the New Testament? How come for 2000 years the Jewish people have been dedicated to Judaism to the point of allowing themselves to be killed rather than convert to Christianity? In their 20 page scholarly work entitled "Why don't the Jewish people don't recognize the New Testament?", theological scholars Eliyahoo Silver and Isaac Even Zahav demonstrate that Christianity is based on mistaken premises, misperceptions, and misunderstanding of what God is really all about. These conclusions and insights may seem strange to many since they go against everything many people have learned all their lives. But, many have seen that in fact Truth is stranger than fiction, Truth has no friends, but we must accept the Truth; not my truth, not your truth....but God's Truth. Here are some excerpts from Eliyahoo Silver's and Isaac Even Zahav's scholarly work entitled "Why don't the Jewish people recognize the New Testament?" regarding the Oneness of God, Jesus as Messiah, Virgin Birth, and the Covenent God made with Noah The Oneness of God "The Jewish God is one, as it is written; "Hear Israel, Y-H-W-H is our God, Y-H-W-H is one." Deut. 6:4. So according to the Bible there is one God, and that One God is One. One means One; not two, not three, not three in one, not two in one, not three divisions of one, but One whole One Alone. ........ The ancient idol worshipping cultures believed that there are many different gods, but God made it very clear in the Bible that He is the One and only God. Christianity believes that God is divided into three parts; the father, the son and the holy ghost. They try to make one out of these three, because God clearly says in the Bible that He is One. However, by definition God is an ever present, all powerful, omniscient, intangible, and unlimited Being, therefore, by dividing God into 3 parts, by definition you thus limit Him. This cannot be so. Deut. 4:39: "Know therefore this day and consider it in your heart that the Lord He is God in heaven above, and upon the earth beneath; there is none else." Deut. 32:39: "See now that I, even I, am He, and there is no god with me." Isaiah 43:10: "I am He, before Me no god was created, neither shall there be after Me." Isaiah 44:6:"Thus saith the Y-H-W-H, the king of Israel, and his redeemer, the Lord of hosts; I am the first and I am the last, and beside me there is no god." Isaiah 45:18:"I am the Y-H-W-H and there is none else." Please notice that nowhere in the here is spoken about a trinity. The concept of trinity is nowhere to be found in the Old Testament or the New Testament. ... There is One God, and that One God is One. One means One. That is not two, not three, not three in one, not two in One, but One." Jesus as the Messiah "Who and what is the Messiah? Let us see according to the holy Hebrew scriptures what the Messiah is supposed to do as required and defined by God himself through His prophets. In Isaiah 2:4 it is written that in the messianic days the swords will be beaten into plowshares and the spears into pruninghooks. Isaiah 60:18: "Violence shall no more be heard in thy land, wasting nor destruction within your borders, but you shall call your walls Salvation and your gates Praise." Zechariah 14:11: "And there shall be no more destruction but Jerusalem will be safely inhabited. Amos 9:14-15: "And I will bring again the captivity of my people of Israel and they shall build the waste cities and inhabit them; and I will plant them upon their land, and they shall no more be pulled out of their land which I have given them, says Y-H-W-H your God." ... ... And then a Jew stands up and claims that he is the Messiah, the savior that is announced by the prophets. But he did not do what he was supposed to do, set the Jews free from their oppressors, the Romans, and establish an era of peace and tranquillity for the Jews and all mankind. Instead he gets killed and all that there is left of him is a collection of writings, called the New Testament. But he claimed that he would establish this all in THAT generation: See Mark 13:24-30 and Matthew 16:27-28; "Verily I say unto you; there be some standing here that shall not taste of death till they see the son of man coming in his kingdom." ... Unnecessary to say that he failed totally. ... .... By the Living Word of God Himself it is clear that the Messiah must redeem Israel and bring universal peace. However, this is not done by Jesus. On the contrary, after he was executed as a common criminal the temple got destroyed, and the Jewish people were exiled, and since then violent war after war has swept over the earth. In order to get around this problem, the christian church invented the second coming. However, nowhere in the Hebrew scriptures is it written that the messiah would come once, get killed, and come again in a second coming. This is a pure rationalization of Jesus failure to function in any way as a Messiah. ..." Virgin Birth "The angel tells Joseph (Matthew 1:22-23) that this is done in order to fulfill the word of the prophet; "Behold, a virgin shall be with child, and shall bring forth a son, and they shall call his name Emmanuel. ...This prophecy is quoted as being from Isaiah 7:14. There it says; "Behold a virgin shall conceive and bare a son and shall call his name Emmanuel." But for the Jewish reader that knows Hebrew, this also raises problems. The Hebrew word in Isaiah 7:14 that the King James translation translates as virgin is the Hebrew word "Almah". But, in Hebrew, the word "Almah" means young woman, NOT virgin. The Hebrew word for virgin is "Betulah". Therefore the word virgin in the king James translation of Isaiah 7:14 is a mistranslation. ... Nowhere in the Old Testament is a prophecy that the messiah will be born unto a virgin. In fact, virgins nowhere give birth in the Old Testament. This concept is only to be found in pagan mythology. By the way, if this was realy a virgin birth, than the requirement to be Messiah of being a direct paternal descandant of king David was not fullfilled.... To the Jews, what does this say about the reliability of the New Testament? " The Noachide and Israelite Covenants In conclusion Eliyahu Silver and Isaac Ewen Zahav point out that Gentiles must follow and live according to the Covenant that God made with Noah which requires descendants of Noah to follow seven catagories of laws known as the Seven Noachide Laws. Thus Noachidism is the proper religion of Gentiles. The seven catagories of Noachide commandments are: 1) Establish courts of law. 2) Do not blaspheme. 3) Do not worship idols. 4) Do not murder. 5) Do not commit adultery. 6) Do not steal. 7) Do not eat the limb of a live animal" Please learn these by memory and know these this day for this is what God commands you as descandants of Noah. For the Jewish people is is pointed out "The Jewish people have a different mission in life; "And you shall be unto me a kingdom of priests, a Holy nation." Exodus 19:6. For this reason the Jewish people have to live according 613 commandments commanded to them in their Holy book called the Torah and the Gentiles must be commited never to lead Jews astray from liveing by the Holy Torah. For more information on Noacidism how to join the Noachide movement if you are a Gentile, or, on Judaism and how to join a Jewish group if you are a Jew, we recomend you visit these oher great web sites. For Gentiles who want to join/form Noachide groups in your area http://www.fastlane.net/~bneinoah/world.html To learn the Seven Noachide Laws and their ramificiations in todays society gopher://gopher.chabad.org/11/outlook/7laws For Jews to learn the Torah so they can live a good Blessed Jewish life http://www.torah.org/programs/outsideinisrael.html For Jews to learn Torah on Mount Zion, Israel http://www.mznet.org/ For Jews worldwide to learn Torah or to experience a Sabbath in a warm, loving home http://www.chabad.org/ To read the full 20 page essay "Why the Jews don't believe in the New Testament" http://www.noachidetorah.home-page.org/ Current policy, music and insights of the re-established House of David http://www.thehouseofdavid.home-page.org/ To read the full copy of Eliyahu Silver's and Isaac Ewen Zahav's 20 page booklet titled: "Why don't the Jewish people recognize the new testament?" refer to our web sites at http://noachidetorah.mainpage.net/ or http://www.noachidetorah.allhere.com/ or search the keyword "CovenentDavid" in at least three search engines. Please feel free to download and share with your friends as we are sure this work will be a collectors item one day. To get Merit with God, make sure to tell this truth to all your friends, neighbors and collegues who are Gentiles that they must live by the Noachide Covenent and all the Jewish people that they must live in accordance with the Torah. The best way to live life is to serve God... properly and in Truth. Spread the Truth to all and God will shower us with His Blessing!!! The only way to acheive peace on earth is to live by God's rules so that God will then bestow peace upon us. This is the only way there will be peace on earth. To contact the writer by mail write Eliyahoo Silver P.O.B. 1651, zip code 91000, Jerusalem, Israel, or write the publisher by mail write Eliyahoo Silver C/O M. Ariel Cohen POB 32097 Jerusalem, Israel 91320. Thanks for subscribing to our mailing list of society and religion. We are sorry that it has been over two years for some who signed our mailing list and you may have forgotten about it but we hope you enjoy our message anyway. If you wish to be removed from future mailings, please simply and politely reply with the subject "Remove" to nocensores@altavista.net or nocensores@iname.com or Covenentdavid@iname.com or houseofdavid@joinme.com and you will happily be removed from any and all future mailings at no cost to you. Feel free to have your friends add themselves to our mailing lists by sending in their emails as many are already doing. "And it shall come to pass in the end of days, that the mountain of Y-H-W-H's house shall be established as the top of the mountains, and shall be exalted above the hills, and all nations shall flow unto it. And many peoples shall go and say ' Come ye, and let us go up to the mountain of Y-H-W-H, To the House of the God of Jacob, and He will teach us of His ways, and we will walk in His paths', for out of Zion shall come forth the Torah and the Word of Y-H-W-H from Jerusalem. And He shall judge between the nations, and shall decide for many peoples, and they shall beat their swords into plowshares, and their spears into pruninghooks, nation shall not lift up sword againt nation, neither shall they learn war anymore" Isaiah 2:2-4 Blessings from Mount Zion, Jerusalem, Israel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 16:14:19 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 7219115053 for ; Sat, 8 May 1999 16:14:18 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA23575; Sat, 8 May 1999 16:14:34 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Brian Feldman Cc: Matthew Thyer , current@FreeBSD.ORG Subject: Re: Doesn't anyone care about the broken sio ?? In-reply-to: Your message of "Sat, 08 May 1999 17:09:06 EDT." Date: Sat, 08 May 1999 16:14:34 -0700 Message-ID: <23571.926205274@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > MAME is a great piece of software, and in and of itself entirely legal; what > problem do you have with it? I'm not talking about MAME, go read the message again. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 17:26:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id BD1EC14C0B for ; Sat, 8 May 1999 17:26:21 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id RAA43188; Sat, 8 May 1999 17:25:36 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199905090025.RAA43188@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Watson Cc: Mike Holling , current@FreeBSD.ORG Subject: Re: RTP and RTSP support in libalias? In-reply-to: Your message of "Sat, 08 May 1999 16:18:07 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 May 1999 17:25:36 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just do a net search on mbone applications . vat , vic , sdr are examples of rtp compliant applications. A generic framework for building rtp based tools can be found at: http://www-mash.cs.berkeley.edu/mash/ Enjoy -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 17:30: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 62FE314C0B for ; Sat, 8 May 1999 17:30: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 KAA09424 for ; Sun, 9 May 1999 10:00:33 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA91738 for FreeBSD-current@FreeBSD.ORG; Sun, 9 May 1999 10:00:32 +0930 (CST) Date: Sun, 9 May 1999 10:00:31 +0930 From: Greg Lehey To: FreeBSD current users Subject: HEADS UP: bdevsw has changed its character Message-ID: <19990509100031.N68170@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i 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 A day or so ago, bdevsw changed from being an array of struct cdevsws to an inline function. That's not a problem in itself: do a make world and all will be well. It does, however, mean that klds which were compiled before the change will no longer load. I had a report today of one person who forgot to do this, and his source tree is on a vinum volume, and he can't load vinum. Beware! 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 Sat May 8 18:30:46 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 4E8CC151CA for ; Sat, 8 May 1999 18:30:42 -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 LAA13409; Sun, 9 May 1999 11:29:19 +1000 Date: Sun, 9 May 1999 11:29:19 +1000 From: Bruce Evans Message-Id: <199905090129.LAA13409@godzilla.zeta.org.au> To: imp@harmony.village.org, luigi@labinfo.iet.unipi.it Subject: Re: m_get(M_WAIT, ...) _can_ return NULL ? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >: m = m_get(M_WAIT, ...) >: looking at the code, it seems that m_get() _can_ return a NULL pointer >: even if one specifies M_WAIT. > >Looking at the man page for malloc: > M_WAITOK > indicates that it is Ok to wait for resources. It is unconve- > niently defined as 0 so care should be taken never to compare > against this value directly or try to AND it as a flag. The de- > fault operation is to block until the memory allocation succeeds. > malloc() can only return NULL if M_NOWAIT is specified. > >Sounds like a bug to me. Er, m_get != malloc M_WAIT != M_WAITOK Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 18:44:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id A6EA314D5F for ; Sat, 8 May 1999 18:44:15 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-15-41.camtech.net.au [203.55.243.41]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id LAA23337; Sun, 9 May 1999 11:05:51 +0930 (CST) Message-ID: <3734E580.58F2F009@camtech.com.au> Date: Sun, 09 May 1999 11:01:44 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Doesn't anyone care about the broken sio ?? References: <16823.926182364@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As far as I can tell, this is unrelated to newbus as the same actions would trigger this problem before and after newbus. I have been seeing this problem for many months (maybe years - but I've only recently identified a set of actions to reproduce it every time). The wierd thing is that I can download heaps of stuff all at the same time (at 48000 baud) and get over 5.5 K/s without a silo overflow BUT as soon as I run MAME, the serial port is stuffed and requires a reboot to do the smallest amount of traffic. NOTE: This occurs AFTER I exit MAME or while I keep it running!!!! Very strange. And its not just on this hardware. I'd just like someone to try to reproduce this. I realise that downloading a MAME ROM is problematic but surely someone out there owns an old space invaders machine or something similar. Poul-Henning Kamp wrote: > > Bruce said, in his own quite way, that somebody had broken fast > interrupts as part of newbus, and that is the end of that story. > > Poul-Henning > > In message <22229.926181448@zippy.cdrom.com>, "Jordan K. Hubbard" writes: > >> I mailed a simple way to reproduce the serious brokeness of the > >> serial port driver on my system and no one responds. > >> > >> What does this mean ? > > > >It means that nobody is probably willing to go bring up a MAME > >environment just to test this. You need to isolate it to a more > >minimal test case if you want people to jump on what could be a local > >problem (some serial hardware is better behaved than others) or a > >misbehaving X server (which is masking interrupts for too long; see > >mailing list archives on this topic). The more complex your > >reproduction case, in other words, the less likely it is that anyone > >will respond to it. > > > >If you can say "here's a small stand-alone C program which hogs things > >to the extent that the serial driver seriously overruns its buffers" > >then it's likely that someone will be at least motivated to compile, > >run and try it. If it involves running some esoteric application > >which requires downloading data of questionable legality on top of it, > >it's far less likely that anyone will even bother to look. > > > >- Jordan > > > > > >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 -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 19:32:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with ESMTP id 6CD9C14FF8 for ; Sat, 8 May 1999 19:32:42 -0700 (PDT) (envelope-from gjvc@extremis.demon.co.uk) Received: (from gjvc@localhost) by extremis.demon.co.uk (8.9.3/8.9.1) id DAA02779 for freebsd-current@freebsd.org; Sun, 9 May 1999 03:33:38 GMT (envelope-from gjvc) Date: Sun, 9 May 1999 03:33:38 +0000 From: George Cox To: freebsd-current@freebsd.org Subject: Re: raw disk devices (IDE) Message-ID: <19990509033337.A2006@extremis.demon.co.uk> References: <19990508194421.B264@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <19990508194421.B264@extremis.demon.co.uk>; from George Cox on Sat, May 08, 1999 at 07:44:22PM +0000 X-Operating-System: FreeBSD extremis.demon.co.uk 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08/05 19:44, George Cox wrote: > Just cvsupped now with the attached slightly alarming boot messages. The > kernel booted successfully however, and I am able to send this mail. :-) Well, just forget this one. I removed KERNFS and DEVFS from my config file and the messages disappear. gjvc --mode sheepish -- [gjvc] http://www.freebsd.org Dumb terminal, smart user. Smart terminal, [ THE POWER TO SERVE ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 20: 8:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-gw2adm.rcsntx.swbell.net (mail-gw2.rcsntx.swbell.net [151.164.30.52]) by hub.freebsd.org (Postfix) with ESMTP id 1E0D114FAB for ; Sat, 8 May 1999 20:08:20 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ppp-207-193-10-49.hstntx.swbell.net [207.193.10.49]) by mail-gw2adm.rcsntx.swbell.net (8.8.5/8.8.5) with ESMTP id WAA01764 for ; Sat, 8 May 1999 22:08:15 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id WAA01403 for current@FreeBSD.ORG; Sat, 8 May 1999 22:09:36 -0500 (CDT) (envelope-from chris) Date: Sat, 8 May 1999 22:09:35 -0500 From: Chris Costello To: current@FreeBSD.ORG Subject: ppp is totally broken Message-ID: <19990508220935.A1379@holly.dyndns.org> Reply-To: chris@calldei.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Somewhere in the mbuf code, either mbuf_Alloc or mbuf_Prepend, there is code that causes ppp to assign a particular mbuf structure pointer to a null pointer, causing ppp to dump core. Contrary to somebody else's email to this list, it is, in fact, a problem affecting any authentication method. -- Chris Costello Who is General Failure and why is he reading my disk? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 20: 9:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 0C82214FAB for ; Sat, 8 May 1999 20:09:10 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-13-85.camtech.net.au [203.55.243.213]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id MAA04554; Sun, 9 May 1999 12:44:03 +0930 (CST) Message-ID: <3734FC84.95F31E3B@camtech.com.au> Date: Sun, 09 May 1999 12:39:56 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Brian Feldman Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, David Dawes Subject: Re: Doesn't anyone care about the broken sio ?? References: Content-Type: multipart/mixed; boundary="------------DFBE461F7C8A0C55E1534890" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------DFBE461F7C8A0C55E1534890 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit *** STOP PRESS *** I have just confirmed that restarting the X server is enough to fix the problem. So my apologies to Bruce, -CURRENT and the whole FreeBSD community in general for blaming sio. For the benefit of David Dawes, I'll quickly restate the problem: Running xmame (from the ports collection) causes lots of silo overflows with user mode ppp until I either restart the X server or reboot. This occurs even after I exit xmame. This is all on FreeBSD-CURRENT but has been happenning for months and is not newbus related. Thankyou Brian, you are the first to NOT reproduce the problem. Note that all my recent testing of this has been at 300 MHz so dont jump on me when you see that I normally overclock at 450 MHz. So compare configuration: My X server is XFree86 3.3.3.1 (from ports) and I use the XF86_SVGA server. My video card is an ET6000 "Jaton VIDEO-58P" with 2.25 MB RAM. I run in 16 bit colour with KDE 1.1.1. I run MAME with sound enabled and I'm NOT using Luigi's PCM driver but rather the old driver (whats it called ??). I have a new ABIT BX6 release 2.0 motherboard (with 16550s I assume). I have an Intel Celeron 300a CPU which I normally run at 450 MHz (using a 100 MHz memory bus speed instead of 66 MHz but when I run it at 300 MHz it doesn't make any difference to this problem). I have PC100 SD RAM with an EPROM. This RAM is rated at 7ns believe it or not. I'd like to be using Soren's ATAPI driver but it doesn't like my CD-ROM drive so I'm using the normal wd driver with flags a0ffa0ff. I'm using a KTX V.90 modem at 115000 baud. I typically get 45333, 46667 or 48000 connections to my ISP. I'm using a Microsoft serial mouse but am not using moused. I do have a PS/2 intellimouse compatible mouse attached but only use it when I'm on the darkside (In Windows 95) as it doesn't work with moused or in XFree86. My whole system has been re-compiled within the last 2 days (world, updated /etc, kernel AND ALL ports [XFree86 3.3.3.1, kde 1.1.1 etc etc etc]) Kernel config file (MATTE), /etc/XF86Config file and dmesg output attached. I have one question about my kernel config: How do I know when it's unsafe to use "options CPU_DISABLE_5X86_LSSER" ? It would be good if the kernel disabled this option under those cases. My /etc/ppp/ppp.conf is: default: set log chat connect phase set device /dev/cuaa1 set speed 115200 allow users matt deny lqr deny chap set timeout 0 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATX4S95=47 OK-AT-OK \\dATDT\\T TIMEOUT 80 CONNECT" set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 isp: set phone ISPNUMBER set login "TIMEOUT 10 sername:--sername: MYUSER ssword: MYPASS" dial Brian Feldman wrote: > > On Sat, 8 May 1999, Jordan K. Hubbard wrote: > > > > I mailed a simple way to reproduce the serious brokeness of the > > > serial port driver on my system and no one responds. > > > > > > What does this mean ? > > > > It means that nobody is probably willing to go bring up a MAME > > environment just to test this. You need to isolate it to a more > > minimal test case if you want people to jump on what could be a local > > problem (some serial hardware is better behaved than others) or a > > misbehaving X server (which is masking interrupts for too long; see > > mailing list archives on this topic). The more complex your > > reproduction case, in other words, the less likely it is that anyone > > will respond to it. > > Hmm, so now you're the second to cite the possibility of X masking interrupts > too long, eh? ;) Actually, I use MAME all the time, and this problem does NOT > occur (XF86_SVGA on an S3 ViRGE/DX). Oh, user-ppp too of course. If I could > have reproduced this problem, I would have replied. > > > > > If you can say "here's a small stand-alone C program which hogs things > > to the extent that the serial driver seriously overruns its buffers" > > then it's likely that someone will be at least motivated to compile, > > run and try it. If it involves running some esoteric application > > which requires downloading data of questionable legality on top of it, > > it's far less likely that anyone will even bother to look. > > MAME is a great piece of software, and in and of itself entirely legal; what > problem do you have with it? > > > > > - Jordan > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Brian Feldman _ __ ___ ____ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | > http://www.freebsd.org _ |___)___/___/ -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------DFBE461F7C8A0C55E1534890 Content-Type: text/plain; charset=us-ascii; name="MATTE" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="MATTE" # $Id: MATTE,v 11.8 1999/05/08 11:04:00 +09:30 matt Exp $ # based on: $Id: LINT,v 1.594 1999/05/06 18:08:23 peter Exp $ # machine i386 ident "MATTE" maxusers 20 options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on wd0 cpu I686_CPU options CPU_DISABLE_5X86_LSSER # Dont use if you use memory mapped I/O device(s). options CPU_FASTER_5X86_FPU # Faster FPU exception handler options NO_F00F_HACK # Disable Pentium F00F hack # COMPATIBILITY OPTIONS options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options USER_LDT # Let processes manipulate their local descriptor table (needed for WINE) options SYSVSHM # Enable SYSV style shared memory options SYSVSEM # Enable SYSV style semaphores options SYSVMSG # Enable SYSV style message queues options MD5 # Include a MD5 routine in the kernel options VM86 # Allow processes to switch to vm86 mode (needed for doscmd) # DEBUGGING OPTIONS options DDB # Enable the kernel debugger #options INVARIANTS # Extra sanity checking (slower) #options INVARIANT_SUPPORT # Include sanity checking functions options UCONSOLE # Allow users to grab the console options USERCONFIG # Boot -c editor options VISUAL_USERCONFIG # Visual boot -c editor # NETWORKING OPTIONS options INET # Internet communications protocols # Network interfaces: pseudo-device ether # Generic Ethernet pseudo-device loop # Network loopback device pseudo-device tun 1 # Tunnel driver(user process ppp) pseudo-device streams # SysVR4 STREAMS emulation # FILESYSTEM OPTIONS options FFS # Berkeley Fast Filesystem options FFS_ROOT # FFS usable as root device options NFS # Network Filesystem options CD9660 # ISO 9660 Filesystem options MFS # Memory Filesystem options MSDOSFS # MSDOS Filesystem options PROCFS # Process Filesystem options NSWAPDEV=4 # Allow this many swap-devices options SOFTUPDATES # SoftUpdates aka delayed writes controller pci0 controller ncr0 options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L # SCSI DEVICE CONFIGURATION (CAM SCSI) controller scbus0 at ncr0 # Base SCSI code disk da0 at scbus0 target 0 disk da1 at scbus0 target 1 disk da2 at scbus0 target 2 disk da3 at scbus0 target 3 disk da4 at scbus0 target 4 disk da5 at scbus0 target 5 disk da6 at scbus0 target 6 options SCSI_DELAY=500 # Only wait 0.5 seconds for SCSI # MISCELLANEOUS DEVICES AND OPTIONS pseudo-device pty 64 # Pseudo ttys - can go as high as 256 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn 4 # Vnode driver (turns a file into a device) options MSGBUF_SIZE=81920 # Size of the kernel message buffer # HARDWARE DEVICE CONFIGURATION controller isa0 options AUTO_EOI_1 # Save 0.7-1.25 usec for each interrupt controller pnp0 # Enable PnP support in the kernel controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0 at isa? port ? conflicts pseudo-device splash # Splash screen at start up! device sc0 at isa? options MAXCONS=12 # Number of virtual consoles options SC_HISTORY_SIZE=800 # Number of history buffer lines options VESA # Needs VM86 defined too!! 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 device wcd0 controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff disk wd0 at wdc0 drive 0 controller wdc1 at isa? port IO_WD2 irq 15 flags 0xa0ffa0ff controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 device psm0 at atkbdc? irq 12 device ppc0 at isa? port? irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device sio0 at isa? port IO_COM1 irq 4 flags 0x10 device sio1 at isa? port IO_COM2 irq 3 options CONSPEED=38400 # Speed for serial console (default 9600) device ed0 at isa? port 0x300 irq 9 iomem 0xd8000 device apm0 at nexus? controller smbus0 controller intpm0 device smb0 at smbus? device joy0 at isa? port IO_GAME #device pcm0 at isa? port? irq 5 drq 1 flags 0x15 controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 --------------DFBE461F7C8A0C55E1534890 Content-Type: text/plain; charset=us-ascii; name="XF86Config" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="XF86Config" # File generated by xf86config. # # Copyright (c) 1995 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ********************************************************************** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ********************************************************************** # ********************************************************************** # Files section. This allows default font and rgb paths to be set # ********************************************************************** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. RgbPath "/usr/X11R6/lib/X11/rgb" # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath "/usr/X11R6/lib/X11/fonts/local/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" # For OSs that support Dynamically loaded modules, ModulePath can be # used to set a search path for the modules. This is currently supported # for Linux ELF, FreeBSD 2.x and NetBSD 1.x. The default path is shown # here. # ModulePath "/usr/X11R6/lib/modules" EndSection # ********************************************************************** # Module section -- this is an optional section which is used to specify # which dynamically loadable modules to load. Dynamically loadable # modules are currently supported only for Linux ELF, FreeBSD 2.x # and NetBSD 1.x. Currently, dynamically loadable modules are used # only for some extended input (XInput) device drivers. # ********************************************************************** # Section "Module" # # Matt's extra modules: Load "xie.so" Load "pex5.so" # # This loads the module for the Joystick driver # Load "xf86Jstk.so" # EndSection # ********************************************************************** # Server flags section. # ********************************************************************** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging # NoTrapSignals # Uncomment this to disable the server abort sequence # This allows clients to receive this key event. # DontZap # Uncomment this to disable the / mode switching # sequences. This allows clients to receive these key events. # DontZoom # Uncomment this to disable tuning with the xvidtune client. With # it the client can still run and fetch card and monitor attributes, # but it will not be allowed to change them. If it tries it will # receive a protocol error. # DisableVidModeExtension # Uncomment this to enable the use of a non-local xvidtune client. # AllowNonLocalXvidtune # Uncomment this to disable dynamically modifying the input device # (mouse and keyboard) settings. # DisableModInDev # Uncomment this to enable the use of a non-local client to # change the keyboard or mouse settings (currently only xset). # AllowNonLocalModInDev EndSection # ********************************************************************** # Input devices # ********************************************************************** # ********************************************************************** # Keyboard section # ********************************************************************** Section "Keyboard" Protocol "Standard" # when using XQUEUE, comment out the above line, and uncomment the # following line # Protocol "Xqueue" AutoRepeat 500 5 # Let the server do the NumLock processing. This should only be required # when using pre-R6 clients # ServerNumLock # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Xleds 1 2 3 # To set the LeftAlt to Meta, RightAlt key to ModeShift, # RightCtl key to Compose, and ScrollLock key to ModeLock: # LeftAlt Meta # RightAlt ModeShift # RightCtl Compose # ScrollLock ModeLock # To disable the XKEYBOARD extension, uncomment XkbDisable. # XkbDisable # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # XkbModel "pc102" # If you have a US Microsoft Natural keyboard, you can use: # XkbModel "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # XkbLayout "de" # or: # XkbLayout "de" # XkbVariant "nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # XkbOptions "ctrl:swapcaps" # These are the default XKB settings for XFree86 # XkbRules "xfree86" # XkbModel "pc101" # XkbLayout "us" # XkbVariant "" # XkbOptions "" XkbKeymap "xfree86(us)" EndSection # ********************************************************************** # Pointer section # ********************************************************************** Section "Pointer" Protocol "Microsoft" Device "/dev/cuaa0" # When using XQUEUE, comment out the above two lines, and uncomment # the following line. # Protocol "Xqueue" # Baudrate and SampleRate are only for some Logitech mice # or for the AceCad tablets which require 9600 baud # BaudRate 9600 # SampleRate 150 # Emulate3Buttons is an option for 2-button Microsoft mice # Emulate3Timeout is the timeout in milliseconds (default is 50ms) Emulate3Buttons # Emulate3Timeout 50 # ChordMiddle is an option for some 3-button Logitech mice # ChordMiddle EndSection # ********************************************************************** # Xinput section -- this is optional and is required only if you # are using extended input devices. This is for example only. Refer # to the XF86Config man page for a description of the options. # ********************************************************************** # Section "Xinput" # SubSection "WacomStylus" # Port "/dev/ttyS1" # DeviceName "Wacom" # EndSubSection # SubSection "WacomCursor" # Port "/dev/ttyS1" # EndSubSection # SubSection "WacomEraser" # Port "/dev/ttyS1" # EndSubSection # # SubSection "Elographics" # Port "/dev/ttyS1" # DeviceName "Elo" # MinimumXPosition 300 # MaximumXPosition 3500 # MinimumYPosition 300 # MaximumYPosition 3500 # Screen 0 # UntouchDelay 10 # ReportDelay 10 # EndSubSection # SubSection "Joystick" Port "/dev/joy0" DeviceName "Joystick" TimeOut 10 MinimumXPosition 100 MaximumXPosition 1300 MinimumYPosition 100 MaximumYPosition 1100 # CenterX 700 # CenterY 600 Delta 20 EndSubSection # # The Mouse Subsection contains the same type of entries as the # standard Pointer Section (see above), with the addition of the # DeviceName entry. # # SubSection "Mouse" # Port "/dev/mouse2" # DeviceName "Second Mouse" # Protocol "Logitech" # EndSubSection EndSection # ********************************************************************** # Monitor section # ********************************************************************** # Any number of monitor sections may be present Section "Monitor" Identifier "Crap Noel" VendorName "KTX" ModelName "SVGA Plus" # HorizSync is in kHz unless units are specified. # HorizSync may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. HorizSync 31.5-35.8 # HorizSync 30-64 # multisync # HorizSync 31.5, 35.2 # multiple fixed sync frequencies # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies # VertRefresh is in Hz unless units are specified. # VertRefresh may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. VertRefresh 60-95 # Modes can be specified in two formats. A compact one-line format, or # a multi-line format. # These two are equivalent # ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace # Mode "1024x768i" # DotClock 45 # HTimings 1024 1048 1208 1264 # VTimings 768 776 784 817 # Flags "Interlace" # EndMode # This is a set of standard mode timings. Modes that are out of monitor spec # are automatically deleted by the server (provided the HorizSync and # VertRefresh lines are correct), so there's no immediate need to # delete mode timings (unless particular mode timings don't work on your # monitor). With these modes, the best standard mode that your monitor # and video card can support for a given resolution is automatically # used. # 640x400 @ 70 Hz, 31.5 kHz hsync Modeline "640x400" 25.175 640 664 760 800 400 409 411 450 # 640x480 @ 60 Hz, 31.5 kHz hsync Modeline "640x480" 25.175 640 664 760 800 480 491 493 525 # 800x600 @ 56 Hz, 35.15 kHz hsync ModeLine "800x600" 36 800 824 896 1024 600 601 603 625 # 1024x768 @ 87 Hz interlaced, 35.5 kHz hsync Modeline "1024x768" 44.9 1024 1048 1208 1264 768 776 784 817 Interlace # 640x400 @ 85 Hz, 37.86 kHz hsync Modeline "640x400" 31.5 640 672 736 832 400 401 404 445 -HSync +VSync # 640x480 @ 72 Hz, 36.5 kHz hsync Modeline "640x480" 31.5 640 680 720 864 480 488 491 521 # 640x480 @ 75 Hz, 37.50 kHz hsync ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -HSync -VSync # 800x600 @ 60 Hz, 37.8 kHz hsync Modeline "800x600" 40 800 840 968 1056 600 601 605 628 +hsync +vsync # 640x480 @ 85 Hz, 43.27 kHz hsync Modeline "640x400" 36 640 696 752 832 480 481 484 509 -HSync -VSync # 1152x864 @ 89 Hz interlaced, 44 kHz hsync ModeLine "1152x864" 65 1152 1168 1384 1480 864 865 875 985 Interlace # 800x600 @ 72 Hz, 48.0 kHz hsync Modeline "800x600" 50 800 856 976 1040 600 637 643 666 +hsync +vsync # 1024x768 @ 60 Hz, 48.4 kHz hsync Modeline "1024x768" 65 1024 1032 1176 1344 768 771 777 806 -hsync -vsync # 640x480 @ 100 Hz, 53.01 kHz hsync Modeline "640x480" 45.8 640 672 768 864 480 488 494 530 -HSync -VSync # 1152x864 @ 60 Hz, 53.5 kHz hsync Modeline "1152x864" 89.9 1152 1216 1472 1680 864 868 876 892 -HSync -VSync # 800x600 @ 85 Hz, 55.84 kHz hsync Modeline "800x600" 60.75 800 864 928 1088 600 616 621 657 -HSync -VSync # 1024x768 @ 70 Hz, 56.5 kHz hsync Modeline "1024x768" 75 1024 1048 1184 1328 768 771 777 806 -hsync -vsync # 1280x1024 @ 87 Hz interlaced, 51 kHz hsync Modeline "1280x1024" 80 1280 1296 1512 1568 1024 1025 1037 1165 Interlace # 800x600 @ 100 Hz, 64.02 kHz hsync Modeline "800x600" 69.65 800 864 928 1088 600 604 610 640 -HSync -VSync # 1024x768 @ 76 Hz, 62.5 kHz hsync Modeline "1024x768" 85 1024 1032 1152 1360 768 784 787 823 # 1152x864 @ 70 Hz, 62.4 kHz hsync Modeline "1152x864" 92 1152 1208 1368 1474 864 865 875 895 # 1280x1024 @ 61 Hz, 64.2 kHz hsync Modeline "1280x1024" 110 1280 1328 1512 1712 1024 1025 1028 1054 # 1024x768 @ 85 Hz, 70.24 kHz hsync Modeline "1024x768" 98.9 1024 1056 1216 1408 768 782 788 822 -HSync -VSync # 1152x864 @ 78 Hz, 70.8 kHz hsync Modeline "1152x864" 110 1152 1240 1324 1552 864 864 876 908 # 1280x1024 @ 70 Hz, 74.59 kHz hsync Modeline "1280x1024" 126.5 1280 1312 1472 1696 1024 1032 1040 1068 -HSync -VSync # 1600x1200 @ 60Hz, 75.00 kHz hsync Modeline "1600x1200" 162 1600 1664 1856 2160 1200 1201 1204 1250 +HSync +VSync # 1152x864 @ 84 Hz, 76.0 kHz hsync Modeline "1152x864" 135 1152 1464 1592 1776 864 864 876 908 # 1280x1024 @ 74 Hz, 78.85 kHz hsync Modeline "1280x1024" 135 1280 1312 1456 1712 1024 1027 1030 1064 # 1024x768 @ 100Hz, 80.21 kHz hsync Modeline "1024x768" 115.5 1024 1056 1248 1440 768 771 781 802 -HSync -VSync # 1280x1024 @ 76 Hz, 81.13 kHz hsync Modeline "1280x1024" 135 1280 1312 1416 1664 1024 1027 1030 1064 # 1600x1200 @ 70 Hz, 87.50 kHz hsync Modeline "1600x1200" 189 1600 1664 1856 2160 1200 1201 1204 1250 -HSync -VSync # 1152x864 @ 100 Hz, 89.62 kHz hsync Modeline "1152x864" 137.65 1152 1184 1312 1536 864 866 885 902 -HSync -VSync # 1280x1024 @ 85 Hz, 91.15 kHz hsync Modeline "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +HSync +VSync # 1600x1200 @ 75 Hz, 93.75 kHz hsync Modeline "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +HSync +VSync # 1600x1200 @ 85 Hz, 105.77 kHz hsync Modeline "1600x1200" 220 1600 1616 1808 2080 1200 1204 1207 1244 +HSync +VSync # 1280x1024 @ 100 Hz, 107.16 kHz hsync Modeline "1280x1024" 181.75 1280 1312 1440 1696 1024 1031 1046 1072 -HSync -VSync # 1800x1440 @ 64Hz, 96.15 kHz hsync ModeLine "1800X1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync # 1800x1440 @ 70Hz, 104.52 kHz hsync ModeLine "1800X1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync # 512x384 @ 78 Hz, 31.50 kHz hsync Modeline "512x384" 20.160 512 528 592 640 384 385 388 404 -HSync -VSync # 512x384 @ 85 Hz, 34.38 kHz hsync Modeline "512x384" 22 512 528 592 640 384 385 388 404 -HSync -VSync # Low-res Doublescan modes # If your chipset does not support doublescan, you get a 'squashed' # resolution like 320x400. # 320x200 @ 70 Hz, 31.5 kHz hsync, 8:5 aspect ratio Modeline "320x200" 12.588 320 336 384 400 200 204 205 225 Doublescan # 320x240 @ 60 Hz, 31.5 kHz hsync, 4:3 aspect ratio Modeline "320x240" 12.588 320 336 384 400 240 245 246 262 Doublescan # 320x240 @ 72 Hz, 36.5 kHz hsync Modeline "320x240" 15.750 320 336 384 400 240 244 246 262 Doublescan # 400x300 @ 56 Hz, 35.2 kHz hsync, 4:3 aspect ratio ModeLine "400x300" 18 400 416 448 512 300 301 302 312 Doublescan # 400x300 @ 60 Hz, 37.8 kHz hsync Modeline "400x300" 20 400 416 480 528 300 301 303 314 Doublescan # 400x300 @ 72 Hz, 48.0 kHz hsync Modeline "400x300" 25 400 424 488 520 300 319 322 333 Doublescan # 480x300 @ 56 Hz, 35.2 kHz hsync, 8:5 aspect ratio ModeLine "480x300" 21.656 480 496 536 616 300 301 302 312 Doublescan # 480x300 @ 60 Hz, 37.8 kHz hsync Modeline "480x300" 23.890 480 496 576 632 300 301 303 314 Doublescan # 480x300 @ 63 Hz, 39.6 kHz hsync Modeline "480x300" 25 480 496 576 632 300 301 303 314 Doublescan # 480x300 @ 72 Hz, 48.0 kHz hsync Modeline "480x300" 29.952 480 504 584 624 300 319 322 333 Doublescan EndSection # ********************************************************************** # Graphics device section # ********************************************************************** # Any number of graphics device sections may be present # Standard VGA Device: Section "Device" Identifier "Generic VGA" VendorName "Unknown" BoardName "Unknown" Chipset "generic" # VideoRam 256 # Clocks 25.2 28.3 EndSection # Sample Device for accelerated server: # Section "Device" # Identifier "Actix GE32+ 2MB" # VendorName "Actix" # BoardName "GE32+" # Ramdac "ATT20C490" # Dacspeed 110 # Option "dac_8_bit" # Clocks 25.0 28.0 40.0 0.0 50.0 77.0 36.0 45.0 # Clocks 130.0 120.0 80.0 31.0 110.0 65.0 75.0 94.0 # EndSection # Sample Device for Hercules mono card: # Section "Device" # Identifier "Hercules mono" # EndSection # Device configured by xf86config: Section "Device" Identifier "Jaton VIDEO-58P" VendorName "Jaton" BoardName "VIDEO-58P" VideoRam 2304 #videoram 2304 # 2.25 MB, when memory probe is incorrect #Option "linear" # for linear mode at 8bpp #Option "noaccel" # when problems with accelerator #Option "power_saver" # enable VESA DPMS #Option "pci_retry" # faster, but problematic for ISA DMA #Option "hw_cursor" # Use hardware cursor (see docs for limitations) #Option "xaa_no_color_exp" # When text (or bitmap) is not rendered correctly # Insert Clocks lines here if appropriate EndSection # ********************************************************************** # Screen sections # ********************************************************************** # The Colour SVGA server Section "Screen" Driver "svga" # Use Device "Generic VGA" for Standard VGA 320x200x256 #Device "Generic VGA" Device "Jaton VIDEO-58P" DefaultColorDepth 16 Monitor "Crap Noel" Subsection "Display" Depth 8 # Omit the Modes line for the "Generic VGA" device Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" ViewPort 0 0 # Use Virtual 320 200 for Generic VGA EndSubsection Subsection "Display" Depth 16 Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" ViewPort 0 0 EndSubsection Subsection "Display" Depth 24 Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" ViewPort 0 0 EndSubsection Subsection "Display" Depth 32 Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" ViewPort 0 0 EndSubsection EndSection # The 16-color VGA server Section "Screen" Driver "vga16" Device "Generic VGA" Monitor "Crap Noel" Subsection "Display" Modes "640x480" "800x600" ViewPort 0 0 Virtual 800 600 EndSubsection EndSection # The Mono server Section "Screen" Driver "vga2" Device "Generic VGA" Monitor "Crap Noel" Subsection "Display" Modes "640x480" "800x600" ViewPort 0 0 Virtual 800 600 EndSubsection EndSection # The accelerated servers (S3, Mach32, Mach8, 8514, P9000, AGX, W32, Mach64) Section "Screen" Driver "accel" Device "Jaton VIDEO-58P" Monitor "Crap Noel" Subsection "Display" Depth 8 Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" ViewPort 0 0 EndSubsection Subsection "Display" Depth 16 Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" ViewPort 0 0 EndSubsection Subsection "Display" Depth 24 Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" ViewPort 0 0 EndSubsection Subsection "Display" Depth 32 Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" ViewPort 0 0 EndSubsection EndSection --------------DFBE461F7C8A0C55E1534890 Content-Type: text/plain; charset=us-ascii; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg" 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: Sat May 8 11:07:38 CST 1999 root@localhost:/usr/src/sys/compile/MATTE Timecounter "i8254" frequency 1193182 Hz CPU: Celeron (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping=0 Features=0x183f9ff real memory = 67108864 (65536K bytes) config> pnp 1 0 bios enable sio0: system console avail memory = 62124032 (60668K bytes) Preloaded elf kernel "kernel" at 0xc02f4000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02f409c. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: CTL0024 [0x24008c0e] Serial 0x100a1ec0 Comp ID: PNP0600 [0x0006d041] npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 7.0 on pci0 ide_pci0: at device 7.1 on pci0 chip2: at device 7.3 on pci0 ncr0: at device 13.0 on pci0 ncr0: interrupting at irq 7 isa0: on motherboard atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model IntelliMouse, device ID 3 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <12 virtual consoles, flags=0x0> wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S wdc0: interrupting at irq 14 wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 wdc1: unit 1 (atapi): , removable, dma, iordis wcd0: drive speed 4687KB/sec, 120KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wdc1: interrupting at irq 15 fdc0: interrupting at irq 6 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 sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ed0 at port 0x300-0x31f irq 9 on isa0 ed0: address 00:00:e8:20:33:e8, type NE2000 (16 bit) ed0: interrupting at irq 9 joy0 at port 0x201 on isa0 joy0: joystick sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: sb0: interrupting at irq 5 sbxvi0 at drq 5 on isa0 snd0: sbmidi0 at port 0x330 on isa0 snd0: opl0 at port 0x388 on isa0 snd0: changing root device to wd0s2a --------------DFBE461F7C8A0C55E1534890-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 20:20:21 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 ADDE014FAB for ; Sat, 8 May 1999 20:20:17 -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 XAA99072; Sat, 8 May 1999 23:18:05 -0400 (EDT) Date: Sat, 8 May 1999 23:18:04 -0400 (EDT) From: Chuck Robey To: Chris Costello Cc: current@FreeBSD.ORG Subject: Re: ppp is totally broken In-Reply-To: <19990508220935.A1379@holly.dyndns.org> 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, 8 May 1999, Chris Costello wrote: > > Somewhere in the mbuf code, either mbuf_Alloc or mbuf_Prepend, > there is code that causes ppp to assign a particular mbuf > structure pointer to a null pointer, causing ppp to dump core. > Contrary to somebody else's email to this list, it is, in fact, a > problem affecting any authentication method. Are you talking about user-space ppp? mine is from a 24 hour old buildworld, and humming along fine. Maybe I'm not using one of the features you use? I use pap, could that be it? To be honest, in the last month or so, I've noticed distinctly greater stability to ppp. Haven't any notion why that is, but I'm sure pleased with it. ----------------------------+----------------------------------------------- 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 (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 20:26:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.torah.org (rina.torah.org [207.239.101.206]) by hub.freebsd.org (Postfix) with ESMTP id 63FCC1573C for ; Sat, 8 May 1999 20:26:32 -0700 (PDT) (envelope-from menken@torah.org) Received: from moed (client196-127-99.bellatlantic.net [151.196.127.99]) by rina.torah.org (8.9.3/8.9.3/Debian/GNU) with SMTP id XAA28784 for ; Sat, 8 May 1999 23:26:26 -0400 Message-Id: <4.1.19990508232735.00b66650@mail.torah.org> X-Sender: menken@mail.torah.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 08 May 1999 23:29:12 -0400 To: freebsd-current@freebsd.org From: Yaakov Menken Subject: Killing spam... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To all readers, who received spam concerning a 'noachidetorah' organization, According to the copies of the message sent our way, the person who spammed you sent regards from Mt. Zion, along with a list of about 10 web sites, one of which was ours. The fellow is an embarrassment, but... Please be aware that the spammer has _NOTHING_ to do with us, Project Genesis, those who operate http://www.torah.org/ . We have no previous knowledge of 'noachidetorah' or anything to do with them. We have a zero-tolerance policy on spam (just like you). We were the third site on the list given, and obviously in a 'side reference.' We are based in Baltimore, MD, not Mt. Zion, Jerusalem (and if you found out that we're hosted by Team Genesis, you also found out our street address). Project Genesis, http://www.torah.org/ does NOT spam, was NOT responsible for the message you received, and does NOT know who sent it. Trust me that were it otherwise, we'd be moving fast to get rid of him. As I said above, we have a zero-tolerance policy and if someone with us were to spam, he'd be history. This guy is embarrassing. But rest assured we had NOThing to do with it! Yours truly, Yaakov Menken -- Rabbi Yaakov Menken menken@torah.org Director, Project Genesis (410) 602-1350 http://www.torah.org/ learn@torah.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 20:33:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-gw3adm.rcsntx.swbell.net (mail-gw3.rcsntx.swbell.net [151.164.30.53]) by hub.freebsd.org (Postfix) with ESMTP id 3DD5F15372 for ; Sat, 8 May 1999 20:33:02 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ppp-207-193-10-49.hstntx.swbell.net [207.193.10.49]) by mail-gw3adm.rcsntx.swbell.net (8.8.5/8.8.5) with ESMTP id WAA23839; Sat, 8 May 1999 22:32:53 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id WAA01547; Sat, 8 May 1999 22:34:11 -0500 (CDT) (envelope-from chris) Date: Sat, 8 May 1999 22:34:10 -0500 From: Chris Costello To: Chuck Robey Cc: Chris Costello , current@FreeBSD.ORG Subject: Re: ppp is totally broken Message-ID: <19990508223410.A1526@holly.dyndns.org> Reply-To: chris@calldei.com References: <19990508220935.A1379@holly.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.1i In-Reply-To: ; from Chuck Robey on Sat, May 08, 1999 at 11:18:04PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 8, 1999, Chuck Robey wrote: > On Sat, 8 May 1999, Chris Costello wrote: > > > > > Somewhere in the mbuf code, either mbuf_Alloc or mbuf_Prepend, > > there is code that causes ppp to assign a particular mbuf > > structure pointer to a null pointer, causing ppp to dump core. > > Contrary to somebody else's email to this list, it is, in fact, a > > problem affecting any authentication method. > > Are you talking about user-space ppp? mine is from a 24 hour old > buildworld, and humming along fine. Maybe I'm not using one of the > features you use? I use pap, could that be it? I use the default Unix-style login, and I also have the PPP from within 6-12 hours. It seems that it was broken within 24 hours. I'm using the 3.1R PPP right now, until the problem is resolved. I'm sending a problem report, as well. -- Chris Costello RAM DISK is not an installation procedure! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 20:51:29 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 43376155F6 for ; Sat, 8 May 1999 20:51:26 -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 XAA19723 for ; Sat, 8 May 1999 23:13:17 -0500 (EST) Date: Sat, 8 May 1999 23:13:16 -0500 (EST) From: Alfred Perlstein To: current@freebsd.org Subject: found 1 place where panic with bridge+divert 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 think i found one spot where having this setup causes a panic: ___________ de0 (no IP) |FreeBSD box| xl0 - ips = 216.55.74.58, 192.168.2.1 `-----------' i have bridge, and divert sockets along with ipfw in my kernel, I'm having bridged packets filtered by ipfw via the sysctl. about 1 second after enableing a divert rule on de0, i panic, it seems to happen here: /* $Id: if_de.c,v 1.104 1999/05/03 09:36:29 dfr Exp $ */ "/usr/src/sys/pci/if_de.c" line 3739 of 5928 --63%-- col 28-31 at: nextout->d_addr1 = TULIP_KVATOPHYS(sc, mtod(ms, caddr_t)); for some reason i've been having a hell of a time trying to get gdb working on this box and was stuck in DDB with an opcode: movl PTmap(,%eax,4),%eax which is really in pmap.h (i386): static __inline vm_offset_t pmap_kextract(vm_offset_t va) { vm_offset_t pa; if ((pa = (vm_offset_t) PTD[va >> PDRSHIFT]) & PG_PS) { pa = (pa & ~(NBPDR - 1)) | (va & (NBPDR - 1)); } else { pa = *(vm_offset_t *)vtopte(va); /* HERE */ pa = (pa & PG_FRAME) | (va & PAGE_MASK); } return pa; } people in -stable seem not to have problems with bridge+divert sockets, anyone have any ideas? btw, if i enable the divert socket on my 'xl' card then it also seems to happen in an intrupt context. btw, this newbus stuff looks sorta interesting, considering it took me about a week to understand the old way, is there any chance for an API to be published? any good pointers to know what i can do with this stuff? thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 8 20:53: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id 4454B1571B for ; Sat, 8 May 1999 20:52:54 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id NAA19431; Sun, 9 May 1999 13:52:46 +1000 (EST) Message-ID: <19990509135246.I27888@rf900.physics.usyd.edu.au> Date: Sun, 9 May 1999 13:52:46 +1000 From: David Dawes To: Matthew Thyer Cc: current@FreeBSD.ORG Subject: Re: Doesn't anyone care about the broken sio ?? References: <3734FC84.95F31E3B@camtech.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3734FC84.95F31E3B@camtech.com.au>; from Matthew Thyer on Sun, May 09, 1999 at 12:39:56PM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, May 09, 1999 at 12:39:56PM +0930, Matthew Thyer wrote: >*** STOP PRESS *** I have just confirmed that restarting the X server > is enough to fix the problem. So my apologies to Bruce, -CURRENT > and the whole FreeBSD community in general for blaming sio. > >For the benefit of David Dawes, I'll quickly restate the problem: >Running xmame (from the ports collection) causes lots of silo overflows >with user mode ppp until I either restart the X server or reboot. >This occurs even after I exit xmame. This is all on FreeBSD-CURRENT but >has been happenning for months and is not newbus related. OK, so there may be a problem with the tseng driver in XFree86. Does xmame use DGA? If so, the problem may be related to switching in and out of DGA mode. A test for that would be to try another DGA client and see if it triggers the same problem (like the 'dga' test client that comes with XFree86 -- if you try it, press 'q' to exit it). The first thing I would suspect is PCI retries. The driver doesn't use those by default, but a bug might cause it to overfill the ET6000's fifo queue, which would bring the PCI retry mechanism into action. Do you only get the overflows when the X server is doing things? Do you think the X server process is using more CPU when this problem shows up compared with before? One other thing to try is adding the following line to the relevant Device section in your XF86Config file: Option "xaa_no_color_exp" and see if that makes any difference. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 0:52:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 1914E14E36 for ; Sun, 9 May 1999 00:52:42 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id JAA06808; Sun, 9 May 1999 09:52:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id JAA19106; Sun, 9 May 1999 09:52:31 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Jos Backus Cc: current@FreeBSD.ORG Subject: Re: mountroot problem In-reply-to: Your message of "Sat, 08 May 1999 23:19:49 +0200." <19990508231949.A93718@hal.mpn.cp.philips.com> Date: Sun, 09 May 1999 09:52:31 +0200 Message-ID: <19104.926236351@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found it, will commit in a sec. Sorry. Poul-Henning In message <19990508231949.A93718@hal.mpn.cp.philips.com>, Jos Backus writes: >Some more information: > >In sys/i386/i386/autoconf I'm seeing the following happen: > >static void >setroot() >{ > int majdev, mindev, unit, slice, part; > dev_t newrootdev; > char partname[2]; > char *sname; > > if (boothowto & RB_DFLTROOT || (bootdev & B_MAGICMASK) != B_DEVMAGIC) > return; > majdev = B_TYPE(bootdev); > printf("setroot: majdev=%d,bdevsw(majdev)=%p\n",majdev,bdevsw(majdev)); > if (majdev >= nblkdev || bdevsw(majdev) == NULL) > return; > unit = B_UNIT(bootdev); > slice = B_SLICE(bootdev); > >etc. > >which prints > > setroot: majdev=4,bdevsw(majdev)=0 > >Thus the function returns, without setting the name of the root device further >on in the code (it would appear that that is where it happens). > >-- >Jos Backus _/ _/_/_/ "Reliability means never > _/ _/ _/ having to say you're sorry." > _/ _/_/_/ -- D. J. Bernstein > _/ _/ _/ _/ >Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; > > >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 Sun May 9 0:56:17 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 2023414E36 for ; Sun, 9 May 1999 00:56:15 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id AAA07768; Sun, 9 May 1999 00:54:50 -0700 Date: Sun, 9 May 1999 00:54:50 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: Jos Backus , current@FreeBSD.ORG Subject: Re: mountroot problem In-Reply-To: <19104.926236351@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 Ah- that's why root stuff is broke... good.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 1:15:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id D662C14E01 for ; Sun, 9 May 1999 01:15:54 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 6AB261F72; Sun, 9 May 1999 16:15:51 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: FreeBSD current users Subject: Re: HEADS UP: bdevsw has changed its character In-reply-to: Your message of "Sun, 09 May 1999 10:00:31 +0930." <19990509100031.N68170@freebie.lemis.com> Date: Sun, 09 May 1999 16:15:51 +0800 From: Peter Wemm Message-Id: <19990509081553.6AB261F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > A day or so ago, bdevsw changed from being an array of struct cdevsws > to an inline function. That's not a problem in itself: do a make > world and all will be well. It does, however, mean that klds which > were compiled before the change will no longer load. I had a report > today of one person who forgot to do this, and his source tree is on a > vinum volume, and he can't load vinum. Beware! That isn't all.. If you are using kld modules, it is a Really Good Idea to keep your kld modules compiled and in sync with your kernel while internal interfaces are changing. kget(8) also will need a recompile. People who are running -current for stability had better be damn careful and be very selective about what they choose to run as a stable snapshot. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 1:19:23 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 7D45E1551C for ; Sun, 9 May 1999 01:19:18 -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 RAA11058; Sun, 9 May 1999 17:49:16 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA36200; Sun, 9 May 1999 17:49:15 +0930 (CST) Date: Sun, 9 May 1999 17:49:14 +0930 From: Greg Lehey To: Peter Wemm Cc: FreeBSD current users Subject: Re: HEADS UP: bdevsw has changed its character Message-ID: <19990509174914.A22791@freebie.lemis.com> References: <19990509100031.N68170@freebie.lemis.com> <19990509081553.6AB261F72@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990509081553.6AB261F72@spinner.netplex.com.au>; from Peter Wemm on Sun, May 09, 1999 at 04:15:51PM +0800 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, 9 May 1999 at 16:15:51 +0800, Peter Wemm wrote: > Greg Lehey wrote: >> A day or so ago, bdevsw changed from being an array of struct cdevsws >> to an inline function. That's not a problem in itself: do a make >> world and all will be well. It does, however, mean that klds which >> were compiled before the change will no longer load. I had a report >> today of one person who forgot to do this, and his source tree is on a >> vinum volume, and he can't load vinum. Beware! > > That isn't all.. If you are using kld modules, it is a Really Good Idea to > keep your kld modules compiled and in sync with your kernel while internal > interfaces are changing. Right, it was just pretty unfortunate in this case (and I heard of another one) that the person had his source tree mounted on a vinum volume, so he could no longer access it :-) If this happens to anybody else, there's a version of the vinum kld compiled this morning on ftp://ftp.lemis.com/pub/vinum/vinum.ko. > kget(8) also will need a recompile. > > People who are running -current for stability had better be damn careful > and be very selective about what they choose to run as a stable snapshot. I think the real problem is that the klds get built with "make world" and not with a kernel build. How about changing that? I've got the opposite problem on another machine: I did a make world, but not a reboot, and now my Linux emulation is broken. 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 May 9 1:20:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id C7F571551C for ; Sun, 9 May 1999 01:20:53 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id KAA06960; Sun, 9 May 1999 10:20:52 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id KAA19226; Sun, 9 May 1999 10:20:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: Greg Lehey , FreeBSD current users Subject: Re: HEADS UP: bdevsw has changed its character In-reply-to: Your message of "Sun, 09 May 1999 16:15:51 +0800." <19990509081553.6AB261F72@spinner.netplex.com.au> Date: Sun, 09 May 1999 10:20:45 +0200 Message-ID: <19224.926238045@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990509081553.6AB261F72@spinner.netplex.com.au>, Peter Wemm write s: >Greg Lehey wrote: >> A day or so ago, bdevsw changed from being an array of struct cdevsws >> to an inline function. That's not a problem in itself: do a make >> world and all will be well. It does, however, mean that klds which >> were compiled before the change will no longer load. I had a report >> today of one person who forgot to do this, and his source tree is on a >> vinum volume, and he can't load vinum. Beware! > >That isn't all.. If you are using kld modules, it is a Really Good Idea to >keep your kld modules compiled and in sync with your kernel while internal >interfaces are changing. kget(8) also will need a recompile. > >People who are running -current for stability had better be damn careful >and be very selective about what they choose to run as a stable snapshot. Amen brother. In general any commit to sys/kern/* or sys/sys/* should make you pay a LOT of attention. -- 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 Sun May 9 1:22: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 082FB15511 for ; Sun, 9 May 1999 01:22:04 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id KAA06975; Sun, 9 May 1999 10:22:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id KAA19245; Sun, 9 May 1999 10:21:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: Peter Wemm , FreeBSD current users Subject: Re: HEADS UP: bdevsw has changed its character In-reply-to: Your message of "Sun, 09 May 1999 17:49:14 +0930." <19990509174914.A22791@freebie.lemis.com> Date: Sun, 09 May 1999 10:21:57 +0200 Message-ID: <19243.926238117@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990509174914.A22791@freebie.lemis.com>, Greg Lehey writes: >> People who are running -current for stability had better be damn careful >> and be very selective about what they choose to run as a stable snapshot. > >I think the real problem is that the klds get built with "make world" >and not with a kernel build. How about changing that? I've got the >opposite problem on another machine: I did a make world, but not a >reboot, and now my Linux emulation is broken. Well, it is a problem you cannot solve in general, in particular as we start to see 3rd parth KLDs... -- 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 Sun May 9 1:31:34 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 7183D15043 for ; Sun, 9 May 1999 01:31: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 SAA11104; Sun, 9 May 1999 18:01:28 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id SAA36250; Sun, 9 May 1999 18:01:27 +0930 (CST) Date: Sun, 9 May 1999 18:01:27 +0930 From: Greg Lehey To: Poul-Henning Kamp Cc: Peter Wemm , FreeBSD current users Subject: Building klds with kernel (was: HEADS UP: bdevsw has changed its character) Message-ID: <19990509180127.B22791@freebie.lemis.com> References: <19990509174914.A22791@freebie.lemis.com> <19243.926238117@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19243.926238117@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, May 09, 1999 at 10:21:57AM +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 Sunday, 9 May 1999 at 10:21:57 +0200, Poul-Henning Kamp wrote: > In message <19990509174914.A22791@freebie.lemis.com>, Greg Lehey writes: > >>> People who are running -current for stability had better be damn careful >>> and be very selective about what they choose to run as a stable snapshot. >> >> I think the real problem is that the klds get built with "make world" >> and not with a kernel build. How about changing that? I've got the >> opposite problem on another machine: I did a make world, but not a >> reboot, and now my Linux emulation is broken. > > Well, it is a problem you cannot solve in general, in particular as > we start to see 3rd parth KLDs... Well, as long as the third party klds are in source, that's fine. They're going to be a real problem otherwise anyway: what will they do with bdevsw? They'll have to be recompiled one way or the other if they're device drivers. Anyway, they're the exception. Most klds are part of the source tree, and they're logically part of the kernel, not of userland, so it makes more sense to build them when building the kernel. 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 May 9 1:37:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 40FC115043 for ; Sun, 9 May 1999 01:37:19 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id B4CF81F72; Sun, 9 May 1999 16:37:16 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: FreeBSD current users Subject: Re: HEADS UP: bdevsw has changed its character In-reply-to: Your message of "Sun, 09 May 1999 17:49:14 +0930." <19990509174914.A22791@freebie.lemis.com> Date: Sun, 09 May 1999 16:37:16 +0800 From: Peter Wemm Message-Id: <19990509083718.B4CF81F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Sunday, 9 May 1999 at 16:15:51 +0800, Peter Wemm wrote: > > Greg Lehey wrote: > >> A day or so ago, bdevsw changed from being an array of struct cdevsws > >> to an inline function. That's not a problem in itself: do a make > >> world and all will be well. It does, however, mean that klds which > >> were compiled before the change will no longer load. I had a report > >> today of one person who forgot to do this, and his source tree is on a > >> vinum volume, and he can't load vinum. Beware! > > > > That isn't all.. If you are using kld modules, it is a Really Good Idea to > > keep your kld modules compiled and in sync with your kernel while internal > > interfaces are changing. > > Right, it was just pretty unfortunate in this case (and I heard of > another one) that the person had his source tree mounted on a vinum > volume, so he could no longer access it :-) If this happens to anybody > else, there's a version of the vinum kld compiled this morning on > ftp://ftp.lemis.com/pub/vinum/vinum.ko. Which is why I use pseudo-device vinum :-) But the risk there is that the ioctl's change as /sbin/vinum is compiled seperately. > > kget(8) also will need a recompile. > > > > People who are running -current for stability had better be damn careful > > and be very selective about what they choose to run as a stable snapshot. > > I think the real problem is that the klds get built with "make world" > and not with a kernel build. How about changing that? I've got the > opposite problem on another machine: I did a make world, but not a > reboot, and now my Linux emulation is broken. I have a system in mind to replace config(8) entirely and will allow flexible kernel and module building, but it's barely even on the drawing board. It will make sys/modules obsolete, which is the main reason why I don't want code in there. (The screensavers are misplaced). I also have half thought about moving some particular kernel-specific tools under this system, but I'm not at all sure about that. On one hand, libkvm etc could benefit, along with ps etc which are hightly kernel specific. But it brings in a whole new set of chicken/egg problems. (like, if the kernel build supervisor is maintained by the same tool, then there will be problems.) > Greg Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 2:37: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 5D6DA153AD for ; Sun, 9 May 1999 02:37:02 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id SAA09089; Sun, 9 May 1999 18:36:42 +0900 (JST) Message-ID: <373556A0.91EC28E@newsguy.com> Date: Sun, 09 May 1999 18:34:24 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Greg Lehey Cc: Peter Wemm , FreeBSD current users Subject: Re: HEADS UP: bdevsw has changed its character References: <19990509100031.N68170@freebie.lemis.com> <19990509081553.6AB261F72@spinner.netplex.com.au> <19990509174914.A22791@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > I think the real problem is that the klds get built with "make world" > and not with a kernel build. How about changing that? I've got the > opposite problem on another machine: I did a make world, but not a > reboot, and now my Linux emulation is broken. Same problem with loader, with the added irony that loader is located under sys/... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 5:32:35 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 7BCC514C09 for ; Sun, 9 May 1999 05:32:32 -0700 (PDT) (envelope-from spud@i.am) Received: from i.am (RAS1-p6.hfa.netvision.net.il [62.0.145.6]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id PAA06307 for ; Sun, 9 May 1999 15:32:28 +0300 (IDT) Message-ID: <37357CCD.D77A1287@i.am> Date: Sun, 09 May 1999 15:17:19 +0300 From: Tomer Weller X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: KDE problems with -current. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i had problems with the old kdelibs packages(1.1), all the programs i compiled couldn't link. i think it's an EGCS issue, so i decided to compile the kdelibs (1.1.1) with -current. it compiled, but no KDE software worked (including kwm). tried to go back to the old pkg, but got the same error, i removed all kde components and reinstalled the kde-1.1 packages, got the same errors, can't get KDE to run at all now... what do i do ? P.S : kdebase-1.1.1 port errors with : gmake[3]: Entering directory `/usr/ports/x11/kdebase11/work/kdebase-1.1.1/kfm' /bin/sh ../libtool --silent --mode=link c++ -O -pipe -I/usr/local/include -DHAV E_GETUSERSHELL -DTIME_WITH_SYS_TIME -L/usr/local/lib -L/usr/X11R6/lib -rpath /u sr/local/lib -rpath /usr/X11R6/lib -o kfm kfmgui.o kfmview.o kbind.o main.o kfm dlg.o bookmark.o kfmprops.o kfmserver_ipc.o kfmserver_ipc2.o kfmserver.o kioserv er.o kioserver_ipc.o kioserver_ipc2.o kfmipc.o root.o kfmman.o kiojob.o htmlcach e.o autostart.o kfmtree.o krenamewin.o passworddialog.o kURLcompletion.o debug.o kfmw.o kfmpaths.o kfmjob.o kfmexec.o kmimemagic.o kfinder.o utils.o open-with.o finddlg.o kcookiejar.o kcookiewin.o popup.o kintlist.o -lkhtmlw -lkimgio -ljpeg -ltiff -ljpeg -lz -lpng -lz -lm -lqt -lX11 -lm -ljscript -lkfile -lkfm -lkdeco re -lXext -lqt -lX11 -lkdeui -lkdecore -lXext -lqt -lX11 root.o: file not recognized: File truncated gmake[3]: *** [kfm] Error 1 gmake[3]: Leaving directory `/usr/ports/x11/kdebase11/work/kdebase-1.1.1/kfm' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/x11/kdebase11/work/kdebase-1.1.1/kfm' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11/kdebase11/work/kdebase-1.1.1' gmake: *** [all-recursive-am] Error 2 *** Error code 2 ====================================== 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 Sun May 9 5:43:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id F21B814E61 for ; Sun, 9 May 1999 05:43:26 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup3-52.iptelecom.net.ua [212.42.69.243]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id PAA20100 for ; Sun, 9 May 1999 15:44:29 +0300 (EEST) Message-ID: <3735833E.1B1011B4@altavista.net> Date: Sun, 09 May 1999 15:44:46 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: NPX code reports negative i586_bzero() bandwidth Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I already submitted this (about a week ago).... :( Please take a look at negative bandwith reported by i586_bzero... (kernel cvsup'ed and rebuilded several minutes ago). Looks like data type owerflow (my machine have K6-2 266 running on 250MHz and 1MB of L2 cache). Calibrating clock(s) ... TSC clock: 250535974 Hz, i8254 clock: 1193028 Hz Timecounter "i8254" frequency 1193028 Hz CPU: AMD-K6(tm) 3D processor (250.54-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 64M bytes Write Allocate 15-16M bytes: Enable Hardware Write Allocate Control: Disable real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x00265000 - 0x03ffdfff, 64589824 bytes (15769 pages) sio0: system console avail memory = 62922752 (61448K bytes) Found BIOS32 Service Directory header at 0xc00faff0 Entry = 0xfb470 (0xc00fb470) Rev = 0 Len = 1 PCI BIOS entry at 0xb4a0 Other BIOS signatures found: ACPI: 00000000 $PnP: 000fc0b0 Preloaded elf kernel "kernel" at 0xc0250000. Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 PnP: CSN 1 COMP_DEVICE_ID = 0x0006d041 CSN 1 Vendor ID: CTL0028 [0x28008c0e] Serial 0x1013c276 Comp ID: PNP0600 [0x0006d041] Called nullpnp_probe with tag 0x00000001, type 0x28008c0e Called nullpnp_probe with tag 0x00000001, type 0x0006d041 pci_open(1): mode 1 addr port (0x0cf8) is 0x80000060 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=05971106) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = -2082577916 bytes/sec bzero() bandwidth = 184877056 bytes/sec Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 5:46:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 4FD1214E61 for ; Sun, 9 May 1999 05:46:38 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup3-52.iptelecom.net.ua [212.42.69.243]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id PAA20309; Sun, 9 May 1999 15:47:34 +0300 (EEST) Message-ID: <373583EC.311FBEAB@altavista.net> Date: Sun, 09 May 1999 15:47:40 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: Tomer Weller Cc: freebsd-current@FreeBSD.ORG Subject: Re: KDE problems with -current. References: <37357CCD.D77A1287@i.am> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tomer Weller wrote: > re -lXext -lqt -lX11 -lkdeui -lkdecore -lXext -lqt -lX11 > root.o: file not recognized: File truncated Maybe you are building ports over NFS - some time ago NFS client code on -CURRENT was broken, however now it seems to be fixed. Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 5:52:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id B900814E66 for ; Sun, 9 May 1999 05:52:22 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id OAA11163 for ; Sun, 9 May 1999 14:52:21 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma011160; Sun, 9 May 99 14:52:21 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id OAA06459 for ; Sun, 9 May 1999 14:52:20 +0200 (MET DST) Received: (qmail 98777 invoked by uid 666); 9 May 1999 12:52:41 -0000 Date: Sun, 9 May 1999 14:52:41 +0200 From: Jos Backus To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: mountroot problem Message-ID: <19990509145241.B98681@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990508231949.A93718@hal.mpn.cp.philips.com> <19104.926236351@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19104.926236351@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, May 09, 1999 at 09:52:31AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, May 09, 1999 at 09:52:31AM +0200, Poul-Henning Kamp wrote: > I found it, will commit in a sec. Sorry. No problem, and thanks. Kept me off the streets for an evening at least. Cheers, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 6:18:29 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 33EC2150E5 for ; Sun, 9 May 1999 06:18:26 -0700 (PDT) (envelope-from spud@i.am) Received: from i.am (RAS5-p106.hfa.netvision.net.il [62.0.147.106]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id QAA09080; Sun, 9 May 1999 16:17:51 +0300 (IDT) Message-ID: <37358778.313847F2@i.am> Date: Sun, 09 May 1999 16:02:49 +0300 From: Tomer Weller X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Maxim Sobolev Cc: freebsd-current@FreeBSD.ORG Subject: Re: KDE problems with -current. References: <37357CCD.D77A1287@i.am> <373583EC.311FBEAB@altavista.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nope. Maxim Sobolev wrote: > Tomer Weller wrote: > > > re -lXext -lqt -lX11 -lkdeui -lkdecore -lXext -lqt -lX11 > > root.o: file not recognized: File truncated > > Maybe you are building ports over NFS - some time ago NFS client code on -CURRENT was broken, however now it seems to be fixed. > > Sincerely, > > Maxim > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- ====================================== 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 Sun May 9 7:31:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from maile.telia.com (maile.telia.com [194.22.190.16]) by hub.freebsd.org (Postfix) with ESMTP id 0EF7B15509; Sun, 9 May 1999 07:31:13 -0700 (PDT) (envelope-from khaled@mailbox.telia.net) Received: from mailbox.telia.net (khaled@mailbox.telia.net [194.237.170.234]) by maile.telia.com (8.8.5/8.8.8) with ESMTP id QAA06395; Sun, 9 May 1999 16:31:12 +0200 (CEST) Received: from localhost (khaled@localhost) by mailbox.telia.net (8.9.1/8.8.5) with SMTP id QAA13086; Sun, 9 May 1999 16:31:18 +0200 (CEST) Date: Sun, 9 May 1999 16:31:18 +0200 (CEST) From: Khaled Daham To: freebsd-alpha@freebsd.org Cc: freebsd-current@freebsd.org Subject: de driver problem 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 folks I cvsupped,made world, built a kernel today and from now on the de interfaces only comes up in 100BaseTX, what causes it not to negotiate ? My Apr_29 kernel doesnt behave like this. The link lamp flickered like hell so it was quite a nice atmosphere for awhile , but i got tired of it :) /Khaled, Telia Network Services Mail: khaled@telia.net Cell: 070-6785492 Work: 08-4567281 :hacker: /n./ [originally, someone who makes furniture with an axe] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 9:45:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1316815718 for ; Sun, 9 May 1999 09:45:19 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.1) id JAA00886; Sun, 9 May 1999 09:45:00 -0700 (PDT) (envelope-from obrien) Message-ID: <19990509094500.A841@nuxi.com> Date: Sun, 9 May 1999 09:45:00 -0700 From: "David O'Brien" To: Peter Wemm Cc: FreeBSD current users Subject: Re: HEADS UP: bdevsw has changed its character Reply-To: obrien@NUXI.com References: <19990509100031.N68170@freebie.lemis.com> <19990509081553.6AB261F72@spinner.netplex.com.au> <19990509174914.A22791@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990509174914.A22791@freebie.lemis.com>; from Greg Lehey on Sun, May 09, 1999 at 05:49:14PM +0930 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think the real problem is that the klds get built with "make world" > and not with a kernel build. How about changing that? I've shot myself in the foot this way too. I'd really like to see modules built as part of the kernel and not userland. As time goes on, I think we will push more and more of the kernel into modules (rather like Solaris). This distinction of where the live kernel's bits live isn't useful. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 10:13:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-gw2adm.rcsntx.swbell.net (mail-gw2.rcsntx.swbell.net [151.164.30.52]) by hub.freebsd.org (Postfix) with ESMTP id 012D414CD5 for ; Sun, 9 May 1999 10:13:11 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ppp-207-193-13-174.hstntx.swbell.net [207.193.13.174]) by mail-gw2adm.rcsntx.swbell.net (8.8.5/8.8.5) with ESMTP id MAA10091; Sun, 9 May 1999 12:13:06 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id MAA21494; Sun, 9 May 1999 12:14:25 -0500 (CDT) (envelope-from chris) Date: Sun, 9 May 1999 12:14:24 -0500 From: Chris Costello To: Tomer Weller Cc: freebsd-current@FreeBSD.ORG Subject: Re: KDE problems with -current. Message-ID: <19990509121424.A21296@holly.dyndns.org> Reply-To: chris@calldei.com References: <37357CCD.D77A1287@i.am> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.1i In-Reply-To: <37357CCD.D77A1287@i.am>; from Tomer Weller on Sun, May 09, 1999 at 03:17:19PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, May 9, 1999, Tomer Weller wrote: > kdebase-1.1.1 port errors with : > root.o: file not recognized: File truncated Try doing: make deinstall make clean make all It looks like root.o may have been built with an older version of egcs, or perhaps it was an a.out object file. -- Chris Costello If at first you don't succeed, you must be a programmer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 12:50: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from knecht.sendmail.org (knecht.sendmail.org [209.31.233.160]) by hub.freebsd.org (Postfix) with ESMTP id E2A4614C4F for ; Sun, 9 May 1999 12:49:57 -0700 (PDT) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (root@flamingo.mckusick.com [209.31.233.178]) by knecht.sendmail.org (8.9.3/8.9.3) with ESMTP id MAA03037; Sun, 9 May 1999 12:49:56 -0700 (PDT) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.8.5/8.8.5) with ESMTP id MAA06832; Sun, 9 May 1999 12:12:44 -0700 (PDT) Message-Id: <199905091912.MAA06832@flamingo.McKusick.COM> To: John Polstra Subject: Re: Disappearing/Reappearing Files... (fwd) Cc: Julian Elischer , current@freebsd.org In-reply-to: Your message of "Sun, 09 May 1999 01:39:33 PDT." Date: Sun, 09 May 1999 12:12:44 -0700 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The changes that I added to soft updates two days ago only kick in when the soft dependency memory limit is hit. This certainly should not be happening at system startup, and on any machine with more than 64Mb of memory, almost never. I did make a couple of minor textual changes to other parts of the code which should not have had any effect, but just in case they did, I have put them back to their previous state in today's delta. I would appreciate your trying out the current delta (1.27) and seeing if the problem persists. If it does, please try out the version before I did my recent rework (1.24). If that version has the problem as well, then I believe that some other change is triggering the problem, as 1.24 represents a version that has been in production for half a year without trouble. Kirk McKusick =-=-=-=-=-=-=-= Date: Sun, 9 May 1999 01:39:33 -0700 (PDT) From: Julian Elischer To: mckusick@mckusick.com Subject: Re: Disappearing/Reappearing Files... (fwd) FYI also some other people are commenting on odd behaviour where a created file doesn't show up for a while... almost as if the readdir() is returning the 'backed out' version of the directory data. julian ---------- Forwarded message ---------- Date: Sat, 8 May 1999 14:11:10 -0700 (PDT) From: John Polstra To: current@FreeBSD.ORG Subject: Re: Disappearing/Reappearing Files... In article <199905082048.NAA34474@vashon.polstra.com>, John Polstra wrote: > > I'm seeing something possibly related (possibly not) on an Alpha with > this morning's -current. First I was getting unaligned accesses and > core dumps from the "cp" in /etc/rc that updates the /etc/motd file. > (I added "set -v" to /etc/rc to catch it.) But I could do the copy by > hand once the system was up. Now on the latest reboot I got this from > it: > > + cp /tmp/_motd /etc/motd > + chmod 644 /etc/motd > chmod: : No such file or directory > chmod in free(): warning: recursive call > chmod in free(): warning: recursive call > chmod in free(): warning: recursive call > chmod in free(): warning: recursive call > > (Hmm, why didn't the filename come out in chmod's error message?) > > I'm running with soft-updates but I'll try turning them off. I tried about 10 reboots, half with and half without soft-updates enabled on the various filesystems. With soft-updates disabled, I didn't see the above problem at all. With soft-updates enabled, I saw it most of the time but not always. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 13: 2: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id BE5D014F76; Sun, 9 May 1999 13:01:10 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id UAA11275; Sun, 9 May 1999 20:59:55 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA06797; Sun, 9 May 1999 20:59:31 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199905091959.UAA06797@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: chris@calldei.com Cc: Steve Price , brian@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: latest ppp with PAP/CHAP coredumps In-reply-to: Your message of "Sat, 08 May 1999 17:40:22 CDT." <19990508174022.B471@holly.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 May 1999 20:59:30 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > > #0 0x805b519 in FsmRecvConfigRej (fp=0x80ae608, lhp=0xbfbfce98, bp=0x0) > ^^^^^^ [.....] I'm on the case :-) The fsm_Input code now does an mbuf_Read() which will return a NULL mbuf if everything has been read from it. I'm just committing some changes now that make ppp a little more careful about this sort of things. Thanks. > -- > Chris Costello > Avoid temporary variables and strange women. > -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 13: 2:20 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 74B8E15864 for ; Sun, 9 May 1999 13:02:17 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id NAA15155; Sun, 9 May 1999 13:02:15 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA36037; Sun, 9 May 1999 13:02:15 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199905091912.MAA06832@flamingo.McKusick.COM> Date: Sun, 09 May 1999 13:02:15 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Kirk McKusick Subject: Re: Disappearing/Reappearing Files... (fwd) Cc: current@freebsd.org, Julian Elischer Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kirk McKusick wrote: > The changes that I added to soft updates two days ago only kick in > when the soft dependency memory limit is hit. This certainly should > not be happening at system startup, and on any machine with more > than 64Mb of memory, almost never. In my case it looks like your changes weren't the problem. I've had a failure without soft updates, and I'm fairly confident that it's a HW problem at this point. (I've only had the machine for a few days.) 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 Sun May 9 13:17: 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 C2A0B15271 for ; Sun, 9 May 1999 13:16:59 -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 QAA14501 for ; Sun, 9 May 1999 16:15:00 -0400 (EDT) Date: Sun, 9 May 1999 16:14:58 -0400 (EDT) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: kernel.old 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 thinking about Peter Wemm's recent change to the kernel Makefile, making a way to install multiple kernels without fragging your last known good kernel, and it got me to thinking, scragging kernel.old, now that we have good kld's, isn't the only way to find yourself well and truly screwed if your new kernel decides it's shy. If your new /modules directory has some incompatibilities with your old kernel, well, you aren't going to be able to save yourself by booting kernel.old. Something on the order of modules.old is going to need to be implemented. Seeing as the modules build isn't in the same part of the (logical) world as the kernel, well, this is somewhat more complicated than it would otherwise be. Is there any chance of the installation of modules being made the responsibility of the kernel Makefile, and not src/modules/Makefile.* ? If that were true, then the kernel installation could be tied to modules installation, and the rotation of the kernel could be extended to rotation of the modules directory. Ideally, I'd want the entire build of modules to be in that Makefile, but I guess that's dreaming. Think about it, it makes some sense, tho, doesn't it? ----------------------------+----------------------------------------------- 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 (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 13:26:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id B5FBA14F93 for ; Sun, 9 May 1999 13:26:35 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id WAA10185; Sun, 9 May 1999 22:26:33 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id WAA21920; Sun, 9 May 1999 22:26:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel.old In-reply-to: Your message of "Sun, 09 May 1999 16:14:58 EDT." Date: Sun, 09 May 1999 22:26:26 +0200 Message-ID: <21918.926281586@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Chuck Robe y writes: >Something on the order of modules.old is going to need to >be implemented. Not to mention /boot/kernel.old.config ... I think you are seeing -current as the norm. You shouldn't. Under -stable the modules should (tm) continue to work since there are not made API changes in -stable. -- 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 Sun May 9 13:58:54 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 1E4EC15638; Sun, 9 May 1999 13:58:45 -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 VAA37867; Sun, 9 May 1999 21:58:40 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 9 May 1999 21:58:40 +0100 (BST) From: Doug Rabson To: Khaled Daham Cc: freebsd-alpha@freebsd.org, freebsd-current@freebsd.org Subject: Re: de driver problem 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, 9 May 1999, Khaled Daham wrote: > Hello folks > > I cvsupped,made world, built a kernel today and from now on the de > interfaces only comes up in 100BaseTX, what causes it not to negotiate ? > My Apr_29 kernel doesnt behave like this. > > The link lamp flickered like hell so it was quite a nice atmosphere for > awhile , but i got tired of it :) > > /Khaled, Telia Network Services > > Mail: khaled@telia.net > Cell: 070-6785492 > Work: 08-4567281 > > :hacker: /n./ [originally, someone who makes furniture with an axe] Some tulip boards in alpha systems don't autonegociate properly so the SRM has a way of forcing them to a particular mode. A change was made recently to respect the SRM setting instead of using autoneg. The variable is typically called ewa0_mode. To find the right setting, type >>>set ewa0_mode from the SRM prompt and it will give you a list of settings. Choose one, then type e.g.: >>>set ewa0_mode Twisted-Pair -- 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 Sun May 9 14:18:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 5F9E9151E5 for ; Sun, 9 May 1999 14:18:34 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id WAA13390; Sun, 9 May 1999 22:15:20 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA10725; Sun, 9 May 1999 22:14:58 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199905092114.WAA10725@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: chris@calldei.com Cc: Chuck Robey , current@FreeBSD.ORG Subject: Re: ppp is totally broken In-reply-to: Your message of "Sat, 08 May 1999 22:34:10 CDT." <19990508223410.A1526@holly.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 May 1999 22:14:57 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > I'm using the 3.1R PPP right now, until the problem is > resolved. I'm sending a problem report, as well. It should be resolved now. A NULL mbuf value is valid - it just means that there's nothing in it. I changed fsm_Input() with the last commits, and didn't notice the MBUF_CTOP(bp) calls that you pointed out :-( MBUF_CTOP is now more robust, as are all the fsm functions and mbuf_Prepend() (which would have died when doing protocol rejects). > -- > Chris Costello > RAM DISK is not an installation procedure! -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 14:21:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 1A3F51563F for ; Sun, 9 May 1999 14:21:31 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.1) id OAA13348; Sun, 9 May 1999 14:18:11 -0700 (PDT) (envelope-from obrien) Message-ID: <19990509141811.A13330@nuxi.com> Date: Sun, 9 May 1999 14:18:11 -0700 From: "David O'Brien" To: Poul-Henning Kamp , Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel.old Reply-To: obrien@NUXI.com References: <21918.926281586@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <21918.926281586@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, May 09, 1999 at 10:26:26PM +0200 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Something on the order of modules.old is going to need to > >be implemented. > > Not to mention /boot/kernel.old.config ... > > I think you are seeing -current as the norm. You shouldn't. Under > -stable the modules should (tm) continue to work since there are not > made API changes in -stable. BUT we shouldn't make it easy for our developers (who do need to run -CURRENT) to kill themselves. Our development time is limited, and recovering from a bum kernel can be a PITA in some situations, so lets not waste our development time when we don't need to. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 14:24:45 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 38AA0151E5 for ; Sun, 9 May 1999 14:24:42 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA29830; Sun, 9 May 1999 15:23:50 -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 PAA47930; Sun, 9 May 1999 15:24:14 -0600 (MDT) Message-Id: <199905092124.PAA47930@harmony.village.org> To: Poul-Henning Kamp Subject: Re: HEADS UP: bdevsw has changed its character Cc: Peter Wemm , Greg Lehey , FreeBSD current users In-reply-to: Your message of "Sun, 09 May 1999 10:20:45 +0200." <19224.926238045@critter.freebsd.dk> References: <19224.926238045@critter.freebsd.dk> Date: Sun, 09 May 1999 15:24:14 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19224.926238045@critter.freebsd.dk> Poul-Henning Kamp writes: : In general any commit to sys/kern/* or sys/sys/* should make you pay : a LOT of attention. Also, when the number of commits in these areas has been as high as it has been lately, one should think twice before updating... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 14:44:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 1736D15168 for ; Sun, 9 May 1999 14:44:36 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA12727 for freebsd-current@FreeBSD.ORG; Sun, 9 May 1999 23:44:33 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 0FA668849; Sun, 9 May 1999 20:07:39 +0200 (CEST) (envelope-from roberto) Date: Sun, 9 May 1999 20:07:39 +0200 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: config(8) changes and i4b Message-ID: <19990509200739.A8341@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current Users' list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5307 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone very -CURRENT and running i4b ? I just upgraded to the new config syntax and it seems that it doesn't grok pseudo-devices with numbers in the name correctly... With this config(8) works but some dependencies are not generated and "make" fails. -=-=- # Q.921 / layer 2 - i4b passive cards D channel handling pseudo-device "i4bq921" # Q.931 / layer 3 - i4b passive cards D channel handling pseudo-device "i4bq931" # layer 4 - i4b common passive and active card handling pseudo-device "i4b pseudo-device "i4btrc" 4 pseudo-device "i4bctl" pseudo-device "i4brbch" 4 pseudo-device "i4btel" 2 pseudo-device "i4bipr" 4 pseudo-device "i4bisppp" 4 -=-=- -=-=- loading kernel.debug i4b_l2.o: In function `i4b_dl_data_req': /sys/compile/KELTIA_T/../../i4b/layer2/i4b_l2.c(.text+0x16f): undefined reference to `i4b_Dfreembuf' i4b_l2.o: In function `i4b_l2_unit_init': /sys/compile/KELTIA_T/../../i4b/layer2/i4b_l2.c(.text+0x2aa): undefined reference to `i4b_Dfreembuf' i4b_l2.o: In function `i4b_ph_data_ind': /sys/compile/KELTIA_T/../../i4b/layer2/i4b_l2.c(.text+0x5b2): undefined reference to `i4b_Dfreembuf' i4b_l2fsm.o: In function `F_AE01': /sys/compile/KELTIA_T/../../i4b/layer2/i4b_l2fsm.c(.text+0x609): undefined reference to `i4b_Dcleanifq' i4b_l2fsm.o: In function `F_AE05': /sys/compile/KELTIA_T/../../i4b/layer2/i4b_l2fsm.c(.text+0x64d): undefined reference to `i4b_Dcleanifq' i4b_l2fsm.o: In function `F_AE06': ... -=-=- Without the "" around the names, config(8) complains with "Syntax error". Any idea ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 15: 1:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.10]) by hub.freebsd.org (Postfix) with ESMTP id 7688B14D95 for ; Sun, 9 May 1999 15:01:18 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: by server.amis.net (Postfix, from userid 66) id DC4E6D5D8F; Mon, 10 May 1999 00:01:16 +0200 (CEST) Received: by gold.amis.net (Postfix, from userid 1000) id 99FD949; Sun, 9 May 1999 23:58:44 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id 8C29A1E2B; Sun, 9 May 1999 23:58:44 +0200 (CEST) Date: Sun, 9 May 1999 23:58:44 +0200 (CEST) From: Blaz Zupan To: Ollivier Robert Cc: FreeBSD Current Users' list Subject: Re: config(8) changes and i4b In-Reply-To: <19990509200739.A8341@keltia.freenix.fr> 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, 9 May 1999, Ollivier Robert wrote: > Anyone very -CURRENT and running i4b ? I just upgraded to the new config > syntax and it seems that it doesn't grok pseudo-devices with numbers in the > name correctly... I'm running a kernel from yesterday, patched with i4b 0.80. > With this config(8) works but some dependencies are not generated and "make" > fails. It works for me. Try removing your kernel compile directory. > Without the "" around the names, config(8) complains with "Syntax error". Yes, this is a known bug in config. But with the quotes it works for me just fine. Blaz Zupan, blaz@amis.net, http://www.herbie.amis.net Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 15: 6:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from nomad.dataplex.net (nomad.dataplex.net [216.140.184.132]) by hub.freebsd.org (Postfix) with ESMTP id 4E99C14D95 for ; Sun, 9 May 1999 15:06:13 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.2/8.9.3) with ESMTP id RAA83100; Sun, 9 May 1999 17:02:57 -0500 (CDT) (envelope-from rkw@dataplex.net) X-Authentication-Warning: nomad.dataplex.net: rkw owned process doing -bs Date: Sun, 9 May 1999 17:02:57 -0500 (CDT) From: Richard Wackerbarth Reply-To: rkw@dataplex.net To: Poul-Henning Kamp Cc: Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: kernel.old In-Reply-To: <21918.926281586@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 I wish :-( It seems that some people think that it is OK to make changes to stable even though those changes break things which used to work. IMHO, branches of the kernel SHOULD be like shared libraries. (It is OK to ADD previously absent features or CORRECT internal errors, but NOT OK to delete features or change API's) On Sun, 9 May 1999, Poul-Henning Kamp wrote: > I think you are seeing -current as the norm. You shouldn't. Under > -stable the modules should (tm) continue to work since there are not > made API changes in -stable. Personally, I think that we should treat kernels just like another library. They export an API (sysctl) that libc, et. al. uses and another API that the kernel modules use. Any change that "breaks" code which is compliant with those API's belongs in a new release branch. PERIOD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 15:17:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id CCAD715105 for ; Sun, 9 May 1999 15:17:27 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id AAA38348; Mon, 10 May 1999 00:16:08 +0200 (CEST) Message-Id: <199905092216.AAA38348@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: Ollivier Robert Cc: freebsd-current@freebsd.org Subject: Re: config(8) changes and i4b Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 09 May 1999 20:07:39 +0200." <19990509200739.A8341@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 May 1999 00:16:08 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert writes: >Anyone very -CURRENT and running i4b ? I just upgraded to the new config >syntax and it seems that it doesn't grok pseudo-devices with numbers in the >name correctly... > >With this config(8) works but some dependencies are not generated and "make" >fails. >-=-=- ># Q.921 / layer 2 - i4b passive cards D channel handling >pseudo-device "i4bq921" > ># Q.931 / layer 3 - i4b passive cards D channel handling >pseudo-device "i4bq931" > ># layer 4 - i4b common passive and active card handling >pseudo-device "i4b ^ is there really a " missing here ? sorry, not yet because config is changing so quickly at the moment. All I can say is that i4b_Dfreembuf is located in layer2/i4b_mbuf.c. You could always add it manually to Makefile until config starts working again ;-) --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 15:21:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from web119.yahoomail.com (web119.yahoomail.com [205.180.60.120]) by hub.freebsd.org (Postfix) with SMTP id 7DE53151E8 for ; Sun, 9 May 1999 15:21:40 -0700 (PDT) (envelope-from valsho@yahoo.com) Message-ID: <19990509222310.4427.rocketmail@web119.yahoomail.com> Received: from [147.226.112.101] by web119.yahoomail.com; Sun, 09 May 1999 15:23:10 PDT Date: Sun, 9 May 1999 15:23:10 -0700 (PDT) From: Valentin Shopov Subject: 4.0-19990509-CURRENT upgrade To: current@freebsd.org 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 running 4.0-19990503-CURRENT. In my case, freebsd swap is on /dev/wd0s3b (3-th partition) I'm trying to upgrade to last 4.0-0509-current. I got error msg: Unable to make device node for /dev/wd0s3b in /dev! The creation of filesystems will be aborted. On DEBUG screen I got: DEBUG: MakeDev: Unknown major/minor for devtype 0s3b Val _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 16: 2:47 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 6AF0614EE2 for ; Sun, 9 May 1999 16:02:45 -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 TAA20817 for ; Sun, 9 May 1999 19:02:45 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA02641; Sun, 9 May 1999 19:02:14 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id TAA89568 for freebsd-current@freebsd.org; Sun, 9 May 1999 19:02:14 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905092302.TAA89568@bb01f39.unx.sas.com> Subject: -current make world failure (compat22) To: freebsd-current@freebsd.org Date: Sun, 9 May 1999 19:02:14 -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, The following is error related to compat22 is causing a make release to fail... Has mtree been updated approriately? thanks! John ===> lib/compat/compat22 cd /usr/src/lib/compat/compat22 ; make install DESTDIR=/R/stage/trees/compat22 SHARED=copies install -c -o root -g wheel -m 444 libalias.so.2.4 libc.so.3.1 libc_r.so.3.0 libcalendar.so.2.0 libcom_err.so.2.0 libcurses.so.2.0 libdialog.so.3.1 libedit.so.2.0 libf2c.so.2.0 libftpio.so.4.0 libg++.so.4.0 libgmp.so.3.0 libgnuregex.so.2.0 libipx.so.2.0 libkvm.so.2.0 libm.so.2.0 libmp.so.3.0 libmytinfo.so.2.0 libncurses.so.3.1 libopie.so.2.0 libpcap.so.2.2 libreadline.so.3.0 librpcsvc.so.2.0 libscrypt.so.2.0 libscsi.so.2.0 libskey.so.2.0 libss.so.2.0 libstdc++.so.2.0 libtelnet.so.2.0 libtermcap.so.2.1 libutil.so.2.2 libvgl.so.1.0 libxpg4.so.2.0 libz.so.2.0 /R/stage/trees/compat22/usr/lib/compat/aout usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 And looking at /R /snap/release/R/stage/trees %ls bin compat20 des games manpages catpages compat21 dict info proflibs compat1x compat3x doc krb compat22 doesn't seem to exist... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 17: 9:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 38B5514F52 for ; Sun, 9 May 1999 17:09:44 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA30398; Mon, 10 May 1999 09:39:41 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA17870; Mon, 10 May 1999 09:40:24 +0930 Date: Mon, 10 May 1999 09:40:23 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Tomer Weller Cc: Maxim Sobolev , freebsd-current@FreeBSD.ORG Subject: Re: KDE problems with -current. In-Reply-To: <37358778.313847F2@i.am> 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, 9 May 1999, Tomer Weller wrote: > Nope. Well, is root.o truncated or otherwise corrupted? Are you seeing any other filesystem problems on this machine? Did you crash/reboot during the build? Kris > Maxim Sobolev wrote: > > > Tomer Weller wrote: > > > > > re -lXext -lqt -lX11 -lkdeui -lkdecore -lXext -lqt -lX11 > > > root.o: file not recognized: File truncated > > > > Maybe you are building ports over NFS - some time ago NFS client code on -CURRENT was broken, however now it seems to be fixed. > > > > Sincerely, > > > > Maxim > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > ====================================== > 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 > ----- "That suit's sharper than a page of Oscar Wilde witticisms that's been rolled up into a point, sprinkled with lemon juice and jabbed into someone's eye" "Wow, that's sharp!" - Ace Rimmer and the Cat, _Red Dwarf_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 17:29:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A4EB915018 for ; Sun, 9 May 1999 17:29:04 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.1) id RAA17301; Sun, 9 May 1999 17:29:01 -0700 (PDT) (envelope-from obrien) Message-ID: <19990509172901.A17286@nuxi.com> Date: Sun, 9 May 1999 17:29:01 -0700 From: "David O'Brien" To: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: -current make world failure (compat22) Reply-To: obrien@NUXI.com References: <199905092302.TAA89568@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905092302.TAA89568@bb01f39.unx.sas.com>; from John W. DeBoskey on Sun, May 09, 1999 at 07:02:14PM -0400 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The following is error related to compat22 is causing a make release > to fail... Has mtree been updated approriately? A grep in /usr/src/etc/mtree/* shows there is no special handling for compat?? dists. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 19: 4:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 720C414C97 for ; Sun, 9 May 1999 19:04:44 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 00A021F72 for ; Mon, 10 May 1999 10:04:40 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: HEADS UP: config(8) changes.. Date: Mon, 10 May 1999 10:04:40 +0800 From: Peter Wemm Message-Id: <19990510020443.00A021F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is late, but a few hours ago, phk chopped out some old stuff from config(8) and removed some backwards compatability warnings. A summary of the changes: If you had old "tty", "bio", "net", "cam" flags, these are obsolete and will now cause a syntax error rather than a warning. If you had old "vector xxxintr", it will now cause a syntax error rather than a warning. Most people would have been getting these warnings for a month or so and will have taken them out already. 'config kernel root on xx0' is gone and will cause a (non-fatal) error. The old config line is mostly no longer required. I say mostly, because there are some circumstances where people used it to change the default kernel name or force a different root device to the boot device. Forcing a different root device can be done with the following (in the config file itself, or in /etc/make.conf): options ROOTDEVICE=\"wd0s1e\" If you want to call your kernel something else, try this in the config file: makeoptions KERNEL=vmunix Or use add 'KERNEL=vmunix' to /etc/make.conf, or whatever. This will compile the kernel called "vmunix" and install it as /vmunix and deal with /vmunix.old etc. The KERNEL option has pretty much been working for some time now, although it wasn't "discovered" until now. What does this mean for -current users? Not a lot.. The average user can just delete the config line entirely and forget about it. The old defunct keywords need to be deleted (bio, net, tty, vector etc). It should be noted that config(8) is destined to die sooner or later and almost certainly never make it to a release branch. Removal of the port/irq/iomem/drq etc keywords is on the agenda, but it's not clear if they will go completely away since we need a way to run without loader(8) if possible. The Alpha build is (still) broken... (BTW; Don't shoot the messenger, I didn't delete it. But I do happen to think it's basically OK, apart from the loss of 'config vmunix' - that should be fairly easy to remap if a lot of people are going to be affected. Remember, even with remapping, the config lines would need an edit.) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 19:10:15 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 0AAA1152E6 for ; Sun, 9 May 1999 19:10:10 -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 LAA15111; Mon, 10 May 1999 11:40:04 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA41964; Mon, 10 May 1999 11:40:02 +0930 (CST) Date: Mon, 10 May 1999 11:40:02 +0930 From: Greg Lehey To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: config(8) changes.. Message-ID: <19990510114002.V22791@freebie.lemis.com> References: <19990510020443.00A021F72@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990510020443.00A021F72@spinner.netplex.com.au>; from Peter Wemm on Mon, May 10, 1999 at 10:04:40AM +0800 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 Monday, 10 May 1999 at 10:04:40 +0800, Peter Wemm wrote: > It should be noted that config(8) is destined to die sooner or later and > almost certainly never make it to a release branch. I suppose this makes it almost bearable. What's coming in its place? 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 May 9 19:15:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 1D6CF152B5 for ; Sun, 9 May 1999 19:15:29 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40548>; Mon, 10 May 1999 12:00:30 +1000 Date: Mon, 10 May 1999 12:15:09 +1000 From: Peter Jeremy Subject: Re: HEADS UP: config(8) changes.. To: current@FreeBSD.ORG Message-Id: <99May10.120030est.40548@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: >If you had old "vector xxxintr", it will now cause a syntax error rather than >a warning. What is the new method of specifying a non-standard interrupt function? I have some code (currently on 2.x, but I was hoping to be able to move it) where I have different interrupt functions within the same driver. I could use a single interrupt handler, but it would mean either additional latency or overhead, which I'd like to avoid. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 19:44:57 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 7FCBF15519 for ; Sun, 9 May 1999 19:44:53 -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 MAA22533; Mon, 10 May 1999 12:44:52 +1000 Date: Mon, 10 May 1999 12:44:52 +1000 From: Bruce Evans Message-Id: <199905100244.MAA22533@godzilla.zeta.org.au> To: current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au Subject: Re: HEADS UP: config(8) changes.. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>If you had old "vector xxxintr", it will now cause a syntax error rather than >>a warning. > >What is the new method of specifying a non-standard interrupt >function? I have some code (currently on 2.x, but I was hoping to be >able to move it) where I have different interrupt functions within the >same driver. I could use a single interrupt handler, but it would >mean either additional latency or overhead, which I'd like to avoid. The driver has to know which one(s) to attach. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 19:48:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id D705314E5A for ; Sun, 9 May 1999 19:48:29 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 4A1AC1F72 for ; Mon, 10 May 1999 10:48:25 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Correction: HEADS UP: config(8) changes.. In-reply-to: Your message of "Mon, 10 May 1999 10:04:40 +0800." <19990510020443.00A021F72@spinner.netplex.com.au> Date: Mon, 10 May 1999 10:48:25 +0800 From: Peter Wemm Message-Id: <19990510024827.4A1AC1F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > If you had old "tty", "bio", "net", "cam" flags, these are obsolete and will > now cause a syntax error rather than a warning. > > If you had old "vector xxxintr", it will now cause a syntax error rather than > a warning. This is wrong, the warnings are just the same as before. > 'config kernel root on xx0' is gone and will cause a (non-fatal) error. 'config kernelname' (eg: config vmunix) has been tweaked to translate it into a makeoptions KERNEL=kernelname. > The old config line is mostly no longer required. I say mostly, because > there are some circumstances where people used it to change the default > kernel name or force a different root device to the boot device. > > Forcing a different root device can be done with the following (in the config > file itself, or in /etc/make.conf): > options ROOTDEVICE=\"wd0s1e\" Corretion.. ROOTDEVNAME.. Also, should be possible to tweak a translation in for this too so that 'root on foo' gets translated into: options ROOTDEVNAME=\"foo\" I haven't done it because I could think of a zillion better things to do than fight with lex/yacc. :-] (like fix the Alpha build) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 20:41:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.direct.ca (cheddar.direct.ca [199.60.229.16]) by hub.freebsd.org (Postfix) with ESMTP id 242B21525B for ; Sun, 9 May 1999 20:41:22 -0700 (PDT) (envelope-from wassman@direct.ca) Received: from vic-53-0264.direct.ca ([216.66.129.160] helo=sorack) by cheddar.direct.ca with smtp (Exim 2.02 #20) id 10ggvN-0007hG-00 for current@freebsd.org; Sun, 9 May 1999 20:40:13 -0700 From: Seamus Wassman To: current@freebsd.org Subject: SPAM Date: Sun, 9 May 1999 20:31:00 -0700 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99050920354700.00176@sorack> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was quite surprised the First Time I got SPAM through this mailing list, I thought for sure there would be someone to moderate it so that no garbage gets through, I personally find it quite offensive to get SPAM on a help based mailing list, I have been thinking that maybe this list should have someone moderating it. Maybe I am way out of line, but I thought I would say my peice. -- Seamus Wassman Sparhawk@sparhawk.bc.ca http://www.sparhawk.bc.ca ICQ#: 7682151 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 20:57:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.cgocable.net (mail.cgocable.net [24.226.1.11]) by hub.freebsd.org (Postfix) with ESMTP id A1EFC152E7 for ; Sun, 9 May 1999 20:57:38 -0700 (PDT) (envelope-from rjp@datais.com) Received: from datais.com (cgowave-53-151.cgocable.net [24.226.53.151]) by mail.cgocable.net (8.9.3/8.9.3) with ESMTP id XAA28598 for ; Sun, 9 May 1999 23:56:41 -0400 (EDT) Message-ID: <37365957.A7B743BE@datais.com> Date: Sun, 09 May 1999 23:58:15 -0400 From: RJ Pauloski Reply-To: rjp@datais.com Organization: The Datacom Network X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 9 21:48:53 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 96CF114F33 for ; Sun, 9 May 1999 21:48:49 -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 AAA51440 for ; Mon, 10 May 1999 00:48:56 -0400 (EDT) Date: Mon, 10 May 1999 00:48:55 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@freebsd.org Subject: 3DNow! support? 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 Is anyone planning on upgrading the binutils gas to a later version so that we can get 3DNow! support? I'd like to use it, but I can't seem to get binutils to work right manually. Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 Sun May 9 22:58:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 714381574B for ; Sun, 9 May 1999 22:58:09 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id HAA02769 for freebsd-current@freebsd.org; Mon, 10 May 1999 07:58:07 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id A0BAB8837; Mon, 10 May 1999 07:39:42 +0200 (CEST) (envelope-from roberto) Date: Mon, 10 May 1999 07:39:42 +0200 From: Ollivier Robert To: freebsd-current@freebsd.org Subject: Re: config(8) changes and i4b Message-ID: <19990510073942.A5062@keltia.freenix.fr> Mail-Followup-To: freebsd-current@freebsd.org References: <19990509200739.A8341@keltia.freenix.fr> <199905092216.AAA38348@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: <199905092216.AAA38348@peedub.muc.de>; from Gary Jennejohn on Mon, May 10, 1999 at 12:16:08AM +0200 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5307 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Gary Jennejohn: > >pseudo-device "i4b > ^ is there really a " missing here ? Oops. That was the error, shame on me for not seeing it. The bad thing is that config(8) never complained about that error :-( -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #71: Sun May 9 20:16:32 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 1:54:46 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 E97F714F94 for ; Mon, 10 May 1999 01:54:43 -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 JAA51678; Mon, 10 May 1999 09:54:49 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 10 May 1999 09:54:49 +0100 (BST) From: Doug Rabson To: Peter Jeremy Cc: current@freebsd.org Subject: Re: HEADS UP: config(8) changes.. In-Reply-To: <99May10.120030est.40548@border.alcanet.com.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 Mon, 10 May 1999, Peter Jeremy wrote: > Peter Wemm wrote: > >If you had old "vector xxxintr", it will now cause a syntax error rather than > >a warning. > > What is the new method of specifying a non-standard interrupt > function? I have some code (currently on 2.x, but I was hoping to be > able to move it) where I have different interrupt functions within the > same driver. I could use a single interrupt handler, but it would > mean either additional latency or overhead, which I'd like to avoid. Use the flags in the driver to select. -- 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 Mon May 10 1:55: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 5894D14D65 for ; Mon, 10 May 1999 01:55:33 -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 JAA51690; Mon, 10 May 1999 09:55:47 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 10 May 1999 09:55:47 +0100 (BST) From: Doug Rabson To: Brian Feldman Cc: current@freebsd.org Subject: Re: 3DNow! support? 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, 10 May 1999, Brian Feldman wrote: > Is anyone planning on upgrading the binutils gas to a later version so that we > can get 3DNow! support? I'd like to use it, but I can't seem to get binutils > to work right manually. I will update binutils when/if 2.9.2 comes out. -- 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 Mon May 10 3:40: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 0478114C39 for ; Mon, 10 May 1999 03:40:11 -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 GAA56693; Mon, 10 May 1999 06:40:09 -0400 (EDT) Date: Mon, 10 May 1999 06:40:09 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Doug Rabson Cc: current@FreeBSD.ORG Subject: Re: 3DNow! support? 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, 10 May 1999, Doug Rabson wrote: > On Mon, 10 May 1999, Brian Feldman wrote: > > > Is anyone planning on upgrading the binutils gas to a later version so that we > > can get 3DNow! support? I'd like to use it, but I can't seem to get binutils > > to work right manually. > > I will update binutils when/if 2.9.2 comes out. Great! I look forward to that. > > -- > 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 > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 Mon May 10 5:16:51 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 F3A5515462 for ; Mon, 10 May 1999 05:16:41 -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 IAA25432; Mon, 10 May 1999 08:14:35 -0400 (EDT) Date: Mon, 10 May 1999 08:14:35 -0400 (EDT) From: Chuck Robey To: Seamus Wassman Cc: current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: <99050920354700.00176@sorack> 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, 9 May 1999, Seamus Wassman wrote: > I was quite surprised the First Time I got SPAM through this mailing > list, I thought for sure there would be someone to moderate it so > that no garbage gets through, I personally find it quite offensive > to get SPAM on a help based mailing list, I have been thinking that > maybe this list should have someone moderating it. Maybe I am way > out of line, but I thought I would say my peice. Are you aware of the traffic on these lists? Adding a moderator would be a job requiring at least several hours a day, and would add hours worth of delay to the lists. Jonothan, our postmaster, is pretty darn good at maintaining our kill file, so folks don't usually get 2 chances to spam us. > > -- > Seamus Wassman > Sparhawk@sparhawk.bc.ca > http://www.sparhawk.bc.ca > ICQ#: 7682151 > > > 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 (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 5:24:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 8E4BE15495 for ; Mon, 10 May 1999 05:24:49 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup3-25.iptelecom.net.ua [212.42.69.216]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id PAA08916 for ; Mon, 10 May 1999 15:25:34 +0300 (EEST) Message-ID: <3736D049.3EF8FB33@altavista.net> Date: Mon, 10 May 1999 15:25:46 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: World breakage related to svr4 module Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On the -CURRENT cvsup'ed two hours ago: ===> sys/modules/svr4 echo "#define COMPAT_43 1" > opt_compat.h @ -> /usr/src/sys machine -> /usr/src/sys/i386/include touch opt_vmpage.h sh /usr/src/sys/modules/svr4/../../kern/vnode_if.sh /usr/src/sys/modules/svr4/../../kern/vnode_if.src cc -c -O2 -pipe -march=pentium -mpentium -DKERNEL -DCOMPAT_SVR4 -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/svr4 -I/usr/obj/usr/src/sys/modules/svr4/@ -I/usr/obj/usr/src/tmp/usr/include -UKERNEL /usr/src/sys/modules/svr4/../../i386/svr4/svr4_genassym.c cc -static -O2 -pipe -march=pentium -mpentium -DKERNEL -DCOMPAT_SVR4 -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/svr4 -I/usr/obj/usr/src/sys/modules/svr4/@ -I/usr/obj/usr/src/tmp/usr/include -o svr4_genassym svr4_genassym.o cc -O2 -pipe -march=pentium -mpentium -DKERNEL -DCOMPAT_SVR4 -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/svr4 -I/usr/obj/usr/src/sys/modules/svr4/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/svr4/../../svr4/svr4_sysent.c cc -O2 -pipe -march=pentium -mpentium -DKERNEL -DCOMPAT_SVR4 -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/svr4 -I/usr/obj/usr/src/sys/modules/svr4/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/svr4/../../svr4/svr4_sysvec.c cc -O2 -pipe -march=pentium -mpentium -DKERNEL -DCOMPAT_SVR4 -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/svr4 -I/usr/obj/usr/src/sys/modules/svr4/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c /usr/src/sys/modules/svr4/../../svr4/svr4_sysent.c:29: warning: cast discards `volatile' from pointer target type cc -O2 -pipe -march=pentium -mpentium -DKERNEL -DCOMPAT_SVR4 -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/svr4 -I/usr/obj/usr/src/sys/modules/svr4/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/svr4/../../svr4/svr4_signal.c /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c:233: parse error before `svr4_execsw' /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c:233: warning: type defaults to `int' in declaration of `svr4_execsw' /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c:233: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c:233: warning: excess elements in scalar initializer after `svr4_execsw' /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c:233: warning: data definition has no type or storage class cc -O2 -pipe -march=pentium -mpentium -DKERNEL -DCOMPAT_SVR4 -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/svr4 -I/usr/obj/usr/src/sys/modules/svr4/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/svr4/../../svr4/svr4_fcntl.c *** Error code 1 1 error To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 5:30: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id A362F15100 for ; Mon, 10 May 1999 05:29:53 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id OAA28467; Mon, 10 May 1999 14:27:39 +0200 (CEST) Date: Mon, 10 May 1999 14:27:01 +0200 From: Stefan Bethke To: Mike Smith Cc: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: m_get(M_WAIT, ...) _can_ return NULL ? Message-ID: <986828.3135335221@d225.promo.de> In-Reply-To: <199905081823.LAA01001@dingo.cdrom.com> Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > I engaged in part of a sweep of this sort with Andrzej a while back, > but he never committed any of the changes. I'm not quite sure why. I've stumbled across this some time ago. See http://www.freebsd.org/cgi/getmsg.cgi?fetch=3D569013+573412+/usr/local/www/= db /text/1998/freebsd-current/19980830.freebsd-current for the code affected (at least in September 1998), and http://www.freebsd.org/cgi/getmsg.cgi?fetch=3D189411+200939+/usr/local/www/= db /text/1998/freebsd-current/19980809.freebsd-current for a possible "fix". It was rejected by Garrett (I don't quite remeber why) but might be helpful for anyone who likes to get into this. Stefan -- M=FChlendamm 12 | Voice +49-40-256848, +49-177-3504009 D-22089 Hamburg | e-mail: stefan.bethke@hanse.de Germany | stb@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 May 10 5:48:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 8612B1553B for ; Mon, 10 May 1999 05:48:15 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 23C6E1F72; Mon, 10 May 1999 20:48:13 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Maxim Sobolev Cc: current@freebsd.org Subject: Re: World breakage related to svr4 module In-reply-to: Your message of "Mon, 10 May 1999 15:25:46 +0300." <3736D049.3EF8FB33@altavista.net> Date: Mon, 10 May 1999 20:48:12 +0800 From: Peter Wemm Message-Id: <19990510124813.23C6E1F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > On the -CURRENT cvsup'ed two hours ago: > cc -O2 -pipe -march=pentium -mpentium -DKERNEL -DCOMPAT_SVR4 -DKERNEL > -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- > -I/usr/obj/usr/src/sys/modules/svr4 > -I/usr/obj/usr/src/sys/modules/svr4/@ -I/usr/obj/usr/src/tmp/usr/include > -c /usr/src/sys/modules/svr4/../../svr4/svr4_signal.c > /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c:233: parse error > before `svr4_execsw' ^^^^^^^^^^^^^^^^^^^^ Ack, fixed.. (How embarresing... :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 5:58: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 948931554B for ; Mon, 10 May 1999 05:57:57 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id OAA10538; Mon, 10 May 1999 14:57:51 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 32B0AD21A; Mon, 10 May 1999 14:57:51 +0200 (CEST) Message-ID: <19990510145751.A429@enst.fr> Date: Mon, 10 May 1999 14:57:51 +0200 From: Pierre Beyssac To: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: m_get(M_WAIT, ...) _can_ return NULL ? References: <199905081332.PAA07452@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905081332.PAA07452@labinfo.iet.unipi.it>; from Luigi Rizzo on Sat, May 08, 1999 at 03:32:33PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 08, 1999 at 03:32:33PM +0200, Luigi Rizzo wrote: > m = m_get(M_WAIT, ...) > m->m_len = something. > > looking at the code, it seems that m_get() _can_ return a NULL pointer > even if one specifies M_WAIT. > > Could this be a potential weakness, and in this case, how shuld we go > and fix it -- by making m_get never return if there is no memory, > or by hunting all such occurrences of the code ? It's a well-known problem, it's a potential weakness, there are several pending PRs related to this (quick search from the subject, probably several more I didn't find): kern/9883 kern/10872 As Alfred said, this has been discussed several times on the lists, and IIRC the conclusion was that it's not easy to fix the code everywhere. It seemed best not to make m_get() wait, because it can result in unexpected blockings (classical starvation problem). I'd be willing to give it a look, but don't expect it to be 100% solved anytime soon. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 6:19:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 57D8C15130 for ; Mon, 10 May 1999 06:19:26 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id GAA21148 for ; Mon, 10 May 1999 06:19:25 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id GAA19914 for ; Mon, 10 May 1999 06:19:24 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id GAA23237 for current@freebsd.org; Mon, 10 May 1999 06:19:23 -0700 (PDT) Date: Mon, 10 May 1999 06:19:23 -0700 (PDT) From: Don Lewis Message-Id: <199905101319.GAA23237@salsa.gv.tsc.tdk.com> To: current@freebsd.org Subject: patch for descriptor leak caused by KKIS.05051999.003b exploit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could someone give the attached patch a try in -current? It fixes the file descriptor leak that the KKIS.05051999.003b exploit causes. This fix seems to work fine in -stable. I'd like to commit it to the current tree and merge it into -stable before the 3.2 code freeze. Index: uipc_usrreq.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_usrreq.c,v retrieving revision 1.43 diff -u -u -r1.43 uipc_usrreq.c --- uipc_usrreq.c 1999/04/28 11:37:07 1.43 +++ uipc_usrreq.c 1999/05/09 23:50:45 @@ -367,6 +367,9 @@ unp_shutdown(unp); } + if (control && error != 0) + unp_dispose(control); + release: if (control) m_freem(control); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 6:35:25 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 B9EEA15130; Mon, 10 May 1999 06:35:20 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id PAA42215; Mon, 10 May 1999 15:35:19 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905101335.PAA42215@freebsd.dk> Subject: vgl-990112.tgz anybody got it still ?? To: current@freebsd.org, hackers@freebsd.org Date: Mon, 10 May 1999 15:35:19 +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 I lost that file due to fatfingering a cleanup :) I can see that several people has downloaded it from my ftp-site so does anybody still have it, and could mail/ftp me a copy ?? 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 Mon May 10 7:44:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (Postfix) with ESMTP id F06E715B38 for ; Mon, 10 May 1999 07:44:05 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id HAA09971; Mon, 10 May 1999 07:43:33 -0700 (PDT) Message-ID: <3736F068.A0C36528@seattleu.edu> Date: Mon, 10 May 1999 07:42:48 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: tosha after CAM changes References: <199905081900.NAA64562@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm, so you did a make world? > > I assume you mean "cdcontrol" above, and not "cdrecord". You can't pause, > play, etc., cds with cdrecord. cdcontrol uses the ioctl interface to the > cd driver, and so it shouldn't be affected. yes :( > Well, can you send me the output of the following commands: > > find /usr/include/cam -print |xargs ident /usr/include/cam: /usr/include/cam/scsi: /usr/include/cam/scsi/scsi_all.h: $Id: scsi_all.h,v 1.6 1998/12/05 22:10:14 mjacob Exp $ /usr/include/cam/scsi/scsi_cd.h: /usr/include/cam/scsi/scsi_ch.h: $NetBSD: scsi_changer.h,v 1.11 1998/02/13 08:28:32 enami Exp $ /usr/include/cam/scsi/scsi_da.h: $Id: scsi_da.h,v 1.2 1998/09/18 22:33:59 ken Exp $ /usr/include/cam/scsi/scsi_message.h: /usr/include/cam/scsi/scsi_pass.h: $Id: scsi_pass.h,v 1.2 1999/05/06 20:16:07 ken Exp $ /usr/include/cam/scsi/scsi_pt.h: $Id: scsi_pt.h,v 1.1 1998/09/15 06:36:34 gibbs Exp $ /usr/include/cam/scsi/scsi_sa.h: $Id: scsi_sa.h,v 1.4 1999/02/05 07:19:23 mjacob Exp $ /usr/include/cam/scsi/scsi_targetio.h: $Id: scsi_targetio.h,v 1.2 1999/03/05 23:25:11 gibbs Exp $ /usr/include/cam/cam.h: $Id: cam.h,v 1.2 1999/04/07 22:57:48 gibbs Exp $ /usr/include/cam/cam_ccb.h: $Id: cam_ccb.h,v 1.5 1999/05/06 20:15:57 ken Exp $ /usr/include/cam/cam_conf.h: $Id: cam_conf.h,v 1.1 1998/09/15 06:33:23 gibbs Exp $ /usr/include/cam/cam_debug.h: $Id: cam_debug.h,v 1.3 1998/12/05 23:55:48 mjacob Exp $ /usr/include/cam/cam_extend.h: $Id: cam_extend.h,v 1.1 1998/09/15 06:33:23 gibbs Exp $ /usr/include/cam/cam_periph.h: $Id: cam_periph.h,v 1.3 1998/10/22 22:16:48 ken Exp $ /usr/include/cam/cam_queue.h: $Id: cam_queue.h,v 1.4 1999/04/19 21:26:08 gibbs Exp $ /usr/include/cam/cam_sim.h: $Id: cam_sim.h,v 1.2 1999/05/06 20:15:59 ken Exp $ /usr/include/cam/cam_xpt.h: $Id: cam_xpt.h,v 1.1 1998/09/15 06:33:23 gibbs Exp $ /usr/include/cam/cam_xpt_periph.h: $Id: cam_xpt_periph.h,v 1.1 1998/09/15 06:33:23 gibbs Exp $ /usr/include/cam/cam_xpt_sim.h: $Id: cam_xpt_sim.h,v 1.3 1999/03/05 23:18:56 gibbs Exp $ > ls -la /usr/lib/libcam* -r--r--r-- 1 root wheel 55890 May 7 19:39 /usr/lib/libcam.a lrwxr-xr-x 1 root wheel 11 May 7 19:39 /usr/lib/libcam.so -> libcam.so.2 -r--r--r-- 1 root wheel 54350 May 7 19:39 /usr/lib/libcam.so.2 There you go. -- Eric Hodel hodeleri@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 8: 4:42 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 A5B4B14CEB for ; Mon, 10 May 1999 08:04:40 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id JAA76406; Mon, 10 May 1999 09:04:05 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905101504.JAA76406@panzer.plutotech.com> Subject: Re: tosha after CAM changes In-Reply-To: <3736F068.A0C36528@seattleu.edu> from Eric Hodel at "May 10, 1999 7:42:48 am" To: hodeleri@seattleu.edu (Eric Hodel) Date: Mon, 10 May 1999 09:04:05 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eric Hodel wrote... > > Hmm, so you did a make world? > > > > I assume you mean "cdcontrol" above, and not "cdrecord". You can't pause, > > play, etc., cds with cdrecord. cdcontrol uses the ioctl interface to the > > cd driver, and so it shouldn't be affected. > > yes :( > > > Well, can you send me the output of the following commands: > > > > find /usr/include/cam -print |xargs ident Well, these look right: > /usr/include/cam/scsi/scsi_pass.h: > $Id: scsi_pass.h,v 1.2 1999/05/06 20:16:07 ken Exp $ [ ... ] > /usr/include/cam/cam_ccb.h: > $Id: cam_ccb.h,v 1.5 1999/05/06 20:15:57 ken Exp $ And so does this: > > ls -la /usr/lib/libcam* > > -r--r--r-- 1 root wheel 55890 May 7 19:39 /usr/lib/libcam.a > lrwxr-xr-x 1 root wheel 11 May 7 19:39 /usr/lib/libcam.so -> > libcam.so.2 > -r--r--r-- 1 root wheel 54350 May 7 19:39 /usr/lib/libcam.so.2 So I'm a little confused here. Does camcontrol work? Try this: camcontrol devlist camcontrol tur -n da -u 0 -v If that works, can you try compiling tosha again? Is anyone else having problems? 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 Mon May 10 8:11:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 500C215335 for ; Mon, 10 May 1999 08:11:38 -0700 (PDT) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from mars.rz.uni-sb.de (mars.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.8.8/8.8.7/8.7.7) with ESMTP id RAA2481383; Mon, 10 May 1999 17:10:43 +0200 (CST) Received: from work.net.local (maxtnt-140.telip.uni-sb.de [134.96.71.11]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id RAA18211; Mon, 10 May 1999 17:10:42 +0200 (CST) Received: from Vodix.CS.Uni-SB.de (localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id RAA73390; Mon, 10 May 1999 17:10:21 +0200 (CEST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199905101510.RAA73390@work.net.local> Date: Mon, 10 May 1999 17:10:20 +0200 (CEST) From: A.Leidinger@Wurzelausix.CS.Uni-SB.de Subject: Re: tosha after CAM changes To: ken@plutotech.com Cc: hodeleri@seattleu.edu, freebsd-current@FreeBSD.ORG In-Reply-To: <199905101504.JAA76406@panzer.plutotech.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 May, Kenneth D. Merry wrote: >> /usr/include/cam/scsi/scsi_pass.h: >> $Id: scsi_pass.h,v 1.2 1999/05/06 20:16:07 ken Exp $ (137) root@ttyp3 # ident /usr/include/cam/scsi/scsi_pass.h /usr/include/cam/scsi/scsi_pass.h: $Id: scsi_pass.h,v 1.2 1999/05/06 20:16:07 ken Exp $ >> > ls -la /usr/lib/libcam* >> >> -r--r--r-- 1 root wheel 55890 May 7 19:39 /usr/lib/libcam.a >> lrwxr-xr-x 1 root wheel 11 May 7 19:39 /usr/lib/libcam.so -> >> libcam.so.2 >> -r--r--r-- 1 root wheel 54350 May 7 19:39 /usr/lib/libcam.so.2 (138) root@ttyp3 # ls -la /usr/lib/libcam* -r--r--r-- 1 root wheel 60110 7 Mai 20:18 /usr/lib/libcam.a lrwxr-xr-x 1 root wheel 11 7 Mai 20:18 /usr/lib/libcam.so -> libcam.so.2 -r--r--r-- 1 root wheel 58702 7 Mai 20:18 /usr/lib/libcam.so.2 > Is anyone else having problems? tosha recompiled some hours ago: (134) root@ttyp3 # tosha -i -d /dev/cd1c Device: /dev/cd1c -- "PIONEER" "CD-ROM DR-U16S" "1.01" track playing start end raw size mp3 size # of track number time sector sector in bytes 128 kbps frames type --------------------------------------------------------------------- 1 4:10'27 0 18776 44163504 4006595 9585 audio ... Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 10:31:16 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 0AAF81586E; Mon, 10 May 1999 10:31:15 -0700 (PDT) From: "Jonathan M. Bresler" To: wassman@direct.ca Cc: current@freebsd.org In-reply-to: <99050920354700.00176@sorack> (message from Seamus Wassman on Sun, 9 May 1999 20:31:00 -0700) Subject: Re: SPAM Message-Id: <19990510173115.0AAF81586E@hub.freebsd.org> Date: Mon, 10 May 1999 10:31:15 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Seamus Wassman > Date: Sun, 9 May 1999 20:31:00 -0700 > > I was quite surprised the First Time I got SPAM through this mailing list, I > thought for sure there would be someone to moderate it so that no garbage gets > through, I personally find it quite offensive to get SPAM on a help based > mailing list, I have been thinking that maybe this list should have someone > moderating it. Maybe I am way out of line, but I thought I would say my > peice. you are not out of line. ;) with volunteers, we could moderate the list(s). mail transfer would be slower as we wait for the moderator(s) to approve each piece of email. if we use more than one moderator per list, the time-sequence of email would be lost....we would get some very strange threads...could be enteraining. the amount of spam we get is very little. its easy to delte a couple messages. i do not believe it is worthwhile ot moderate the lists. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 10:31:44 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 F3CE71586E for ; Mon, 10 May 1999 10:31:42 -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 NAA11757 for ; Mon, 10 May 1999 13:31:41 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA03759; Mon, 10 May 1999 13:31:11 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id NAA22327 for freebsd-current@freebsd.org; Mon, 10 May 1999 13:31:11 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905101731.NAA22327@bb01f39.unx.sas.com> Subject: One last make world problem (imgact_svr4.c) To: freebsd-current@freebsd.org Date: Mon, 10 May 1999 13:31:10 -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, It looks like most of the compilation problems from the last few days have been cleaned up pretty well... The last one I'm seeing now is: cc -nostdinc -O -pipe -DKERNEL -DCOMPAT_SVR4 -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/svr4 -I/usr/obj/usr/src/sys/modules/svr4/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c:233: parse error before `svr4_execsw' /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c:233: warning: type defaults to `int' in declaration of `svr4_execsw' /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c:233: warning: initialization makes integer from pointer without a cast /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c:233: warning: excess elements in scalar initializer after `svr4_execsw' /usr/src/sys/modules/svr4/../../svr4/imgact_svr4.c:233: warning: data definition has no type or storage class *** Error code 1 I don't see any mods to code for the type or initializer via cvsweb, and my tree is only a few hours out of date. I tend to forget, this is against the 4.0 sources. Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 11:31:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-gw2adm.rcsntx.swbell.net (mail-gw2.rcsntx.swbell.net [151.164.30.52]) by hub.freebsd.org (Postfix) with ESMTP id 99AA914C1E for ; Mon, 10 May 1999 11:31:19 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ppp-207-193-13-87.hstntx.swbell.net [207.193.13.87]) by mail-gw2adm.rcsntx.swbell.net (8.8.5/8.8.5) with ESMTP id NAA14131; Mon, 10 May 1999 13:31:04 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id NAA26158; Mon, 10 May 1999 13:32:01 -0500 (CDT) (envelope-from chris) Date: Mon, 10 May 1999 13:31:49 -0500 From: Chris Costello To: Brian Somers Cc: chris@calldei.com, Chuck Robey , current@FreeBSD.ORG Subject: Re: ppp is totally broken Message-ID: <19990510133149.I22538@holly.dyndns.org> Reply-To: chris@calldei.com References: <19990508223410.A1526@holly.dyndns.org> <199905092114.WAA10725@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.1i In-Reply-To: <199905092114.WAA10725@keep.lan.Awfulhak.org>; from Brian Somers on Sun, May 09, 1999 at 10:14:57PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, May 9, 1999, Brian Somers wrote: > [.....] > > I'm using the 3.1R PPP right now, until the problem is > > resolved. I'm sending a problem report, as well. > > It should be resolved now. A NULL mbuf value is valid - it just > means that there's nothing in it. I changed fsm_Input() with the Wouldn't it be better for *bp to be NULL instead of bp? > last commits, and didn't notice the MBUF_CTOP(bp) calls that you > pointed out :-( I hadn't looked into MBUF_CTOP, else I would have had enough of a grasp of the actual problem-causing code to at least find out what the problem was, if not fix it. > > MBUF_CTOP is now more robust, as are all the fsm functions and > mbuf_Prepend() (which would have died when doing protocol rejects). > > > -- > > Chris Costello > > RAM DISK is not an installation procedure! > > -- > Brian > > Don't _EVER_ lose your sense of humour ! > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Chris Costello Expert systems are built to embody the knowledge of human experts. - Kulawiec To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 12:52:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (Postfix) with ESMTP id 9D3CE14F4D for ; Mon, 10 May 1999 12:52:12 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id MAA25050; Mon, 10 May 1999 12:51:36 -0700 (PDT) Message-ID: <3737389C.A43DB3E@seattleu.edu> Date: Mon, 10 May 1999 12:50:52 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: tosha after CAM changes References: <199905101504.JAA76406@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > So I'm a little confused here. Does camcontrol work? Try this: > > camcontrol devlist camcontrol: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device > camcontrol tur -n da -u 0 -v camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed cam_lookup_pass: Inappropriate ioctl for device perhaps deleting and resupping is in order? -- Eric Hodel hodeleri@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13: 1:31 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 EA79415C31 for ; Mon, 10 May 1999 13:01:17 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id OAA78016; Mon, 10 May 1999 14:00:30 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905102000.OAA78016@panzer.plutotech.com> Subject: Re: tosha after CAM changes In-Reply-To: <3737389C.A43DB3E@seattleu.edu> from Eric Hodel at "May 10, 1999 12:50:52 pm" To: hodeleri@seattleu.edu (Eric Hodel) Date: Mon, 10 May 1999 14:00:30 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eric Hodel wrote... > "Kenneth D. Merry" wrote: > > So I'm a little confused here. Does camcontrol work? Try this: > > > > camcontrol devlist > > camcontrol: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for > device > > > camcontrol tur -n da -u 0 -v > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > cam_lookup_pass: Inappropriate ioctl for device > > perhaps deleting and resupping is in order? It looks like you may not have the kernel side of the changes. When was your kernel compiled? You may indeed want to cvsup again. 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 Mon May 10 13:15:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 9F5E2151FC; Mon, 10 May 1999 13:14:58 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA57830; Mon, 10 May 1999 22:14:57 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id WAA03760; Mon, 10 May 1999 22:14:56 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905102014.WAA03760@greenpeace.grondar.za> To: "Jonathan M. Bresler" Cc: current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: Your message of " Mon, 10 May 1999 10:31:15 MST." <19990510173115.0AAF81586E@hub.freebsd.org> References: <19990510173115.0AAF81586E@hub.freebsd.org> Date: Mon, 10 May 1999 22:14:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jonathan M. Bresler" wrote: > with volunteers, we could moderate the list(s). mail transfer > would be slower as we wait for the moderator(s) to approve each piece > of email. if we use more than one moderator per list, the > time-sequence of email would be lost....we would get some very > strange threads...could be enteraining. Have you ever considered only allowing list members to post, or are there difficulties that make this impossible? > the amount of spam we get is very little. its easy to delte a > couple messages. i do not believe it is worthwhile ot moderate the > lists. Do you have any stats of "accepted mail" vs "rejected mail" vs SPAM? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:21:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (Postfix) with ESMTP id C576414D9B for ; Mon, 10 May 1999 13:21:33 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id NAA02468; Mon, 10 May 1999 13:21:00 -0700 (PDT) Message-ID: <37373F80.8C55254B@seattleu.edu> Date: Mon, 10 May 1999 13:20:16 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: "freebsd-current@FreeBSD.ORG" Subject: Re: tosha after CAM changes References: <199905102000.OAA78016@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > > Eric Hodel wrote... > > "Kenneth D. Merry" wrote: > > > So I'm a little confused here. Does camcontrol work? Try this: > > > > > > camcontrol devlist > > > > camcontrol: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for > > device > > > > > camcontrol tur -n da -u 0 -v > > > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > cam_lookup_pass: Inappropriate ioctl for device > > > > perhaps deleting and resupping is in order? > > It looks like you may not have the kernel side of the changes. When was > your kernel compiled? > > You may indeed want to cvsup again. I'll do that and tell you the results. -- Eric Hodel hodeleri@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:22:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id B16BC15757; Mon, 10 May 1999 13:22:27 -0700 (PDT) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id PAA10332; Mon, 10 May 1999 15:22:28 -0500 (CDT) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id PAA10328; Mon, 10 May 1999 15:22:25 -0500 (CDT) Message-ID: <036401be9b22$d35b4540$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Jonathan M. Bresler" , "Mark Murray" Cc: Subject: Re: SPAM Date: Mon, 10 May 1999 15:22:26 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A spammer could simply become a list member and then SPAM. They won't care if they are removed once they have perpetrated their abuse. Tom Veldhouse veldy@visi.com -----Original Message----- From: Mark Murray To: Jonathan M. Bresler Cc: current@FreeBSD.ORG Date: Monday, May 10, 1999 3:17 PM Subject: Re: SPAM >"Jonathan M. Bresler" wrote: >> with volunteers, we could moderate the list(s). mail transfer >> would be slower as we wait for the moderator(s) to approve each piece >> of email. if we use more than one moderator per list, the >> time-sequence of email would be lost....we would get some very >> strange threads...could be enteraining. > >Have you ever considered only allowing list members to post, or are >there difficulties that make this impossible? > >> the amount of spam we get is very little. its easy to delte a >> couple messages. i do not believe it is worthwhile ot moderate the >> lists. > >Do you have any stats of "accepted mail" vs "rejected mail" vs SPAM? > >M >-- >Mark Murray >Join the anti-SPAM movement: http://www.cauce.org > > >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 Mon May 10 13:25:46 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 E4F1614DDF; Mon, 10 May 1999 13:25:28 -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 QAA15319; Mon, 10 May 1999 16:25:05 -0400 (EDT) (envelope-from wollman) Date: Mon, 10 May 1999 16:25:05 -0400 (EDT) From: Garrett Wollman Message-Id: <199905102025.QAA15319@khavrinen.lcs.mit.edu> To: Mark Murray Cc: "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: <199905102014.WAA03760@greenpeace.grondar.za> References: <19990510173115.0AAF81586E@hub.freebsd.org> <199905102014.WAA03760@greenpeace.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Have you ever considered only allowing list members to post, or are > there difficulties that make this impossible? Yes, there are. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:28:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id C33D515575; Mon, 10 May 1999 13:28:16 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA57871; Mon, 10 May 1999 22:28:13 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id WAA03970; Mon, 10 May 1999 22:28:11 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905102028.WAA03970@greenpeace.grondar.za> To: "Thomas T. Veldhouse" Cc: "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: Your message of " Mon, 10 May 1999 15:22:26 EST." <036401be9b22$d35b4540$236319ac@w142844.carlson.com> References: <036401be9b22$d35b4540$236319ac@w142844.carlson.com> Date: Mon, 10 May 1999 22:28:10 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Thomas T. Veldhouse" wrote: > A spammer could simply become a list member and then SPAM. They won't care > if they are removed once they have perpetrated their abuse. Yes, but is stops the scrape 'n spammers who get the easy-to-reach addresses off the web page. The subscribed spammers at least have a verified email address, which is too easy to whack for the amount of trouble they went to. Spammers go fo massive bulk; subscribing to mailing lists doesn't fit the profile for the majority of them. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:29:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 1427E14DDF; Mon, 10 May 1999 13:29:20 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA57882; Mon, 10 May 1999 22:29:17 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id WAA03995; Mon, 10 May 1999 22:29:17 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905102029.WAA03995@greenpeace.grondar.za> To: Garrett Wollman Cc: "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: Your message of " Mon, 10 May 1999 16:25:05 -0400." <199905102025.QAA15319@khavrinen.lcs.mit.edu> References: <19990510173115.0AAF81586E@hub.freebsd.org> <199905102014.WAA03760@greenpeace.grondar.za> <199905102025.QAA15319@khavrinen.lcs.mit.edu> Date: Mon, 10 May 1999 22:29:16 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > < said: > > > Have you ever considered only allowing list members to post, or are > > there difficulties that make this impossible? > > Yes, there are. Content-free answer. Please elaborate? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:30: 7 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 3BB6A152CE; Mon, 10 May 1999 13:30:02 -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 QAA48468; Mon, 10 May 1999 16:27:45 -0400 (EDT) Date: Mon, 10 May 1999 16:27:45 -0400 (EDT) From: Chuck Robey To: Mark Murray Cc: "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: <199905102014.WAA03760@greenpeace.grondar.za> 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, 10 May 1999, Mark Murray wrote: > "Jonathan M. Bresler" wrote: > > with volunteers, we could moderate the list(s). mail transfer > > would be slower as we wait for the moderator(s) to approve each piece > > of email. if we use more than one moderator per list, the > > time-sequence of email would be lost....we would get some very > > strange threads...could be enteraining. > > Have you ever considered only allowing list members to post, or are > there difficulties that make this impossible? There might be some resistance to this for all lists, but how about just, say, current and committers? Hackers == maybe? I don't think anyone on current or committers will complain. > > > the amount of spam we get is very little. its easy to delte a > > couple messages. i do not believe it is worthwhile ot moderate the > > lists. > > Do you have any stats of "accepted mail" vs "rejected mail" vs SPAM? > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > > 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 (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:32:10 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 8890615BDF; Mon, 10 May 1999 13:32:05 -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 QAA48480; Mon, 10 May 1999 16:29:54 -0400 (EDT) Date: Mon, 10 May 1999 16:29:54 -0400 (EDT) From: Chuck Robey To: "Thomas T. Veldhouse" Cc: "Jonathan M. Bresler" , Mark Murray , current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: <036401be9b22$d35b4540$236319ac@w142844.carlson.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, 10 May 1999, Thomas T. Veldhouse wrote: > A spammer could simply become a list member and then SPAM. They won't care > if they are removed once they have perpetrated their abuse. The could, but most wouldn't, wouldn't even know how. It wouldn't be a sure cure, but it would sure help. Don't do it on newbies type lists, like -questions or -newbies, even multimedia gets a lot of newbies. Current and committers would be good candidates. > > Tom Veldhouse > veldy@visi.com > > -----Original Message----- > From: Mark Murray > To: Jonathan M. Bresler > Cc: current@FreeBSD.ORG > Date: Monday, May 10, 1999 3:17 PM > Subject: Re: SPAM > > > >"Jonathan M. Bresler" wrote: > >> with volunteers, we could moderate the list(s). mail transfer > >> would be slower as we wait for the moderator(s) to approve each piece > >> of email. if we use more than one moderator per list, the > >> time-sequence of email would be lost....we would get some very > >> strange threads...could be enteraining. > > > >Have you ever considered only allowing list members to post, or are > >there difficulties that make this impossible? > > > >> the amount of spam we get is very little. its easy to delte a > >> couple messages. i do not believe it is worthwhile ot moderate the > >> lists. > > > >Do you have any stats of "accepted mail" vs "rejected mail" vs SPAM? > > > >M > >-- > >Mark Murray > >Join the anti-SPAM movement: http://www.cauce.org > > > > > >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 > ----------------------------+----------------------------------------------- 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 (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:36:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id E5B0115B4D; Mon, 10 May 1999 13:36:06 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA57915; Mon, 10 May 1999 22:36:03 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id WAA04081; Mon, 10 May 1999 22:35:59 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905102035.WAA04081@greenpeace.grondar.za> To: Chuck Robey Cc: "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: Your message of " Mon, 10 May 1999 16:27:45 -0400." References: Date: Mon, 10 May 1999 22:35:58 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > Have you ever considered only allowing list members to post, or are > > there difficulties that make this impossible? > > There might be some resistance to this for all lists, but how about > just, say, current and committers? Hackers == maybe? I can imagine that there could be resistance; I just want to know what the reasons are. Perhaps there is a solution that could be constructed. I have been hugely sucessful in getting my owm mailbox cleaned up. At one stage I was receiving 50-70 spams _a_day_; it is now about 5 a week and dropping. I had to get pretty fascist, but my false-positive is very low (maybe 7 in total). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:36:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 6DD6015CCC for ; Mon, 10 May 1999 13:36:26 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA09474; Mon, 10 May 1999 22:34:07 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA46629; Sun, 9 May 1999 23:13:16 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905092113.XAA46629@yedi.iaf.nl> Subject: Re: kernel.old In-Reply-To: from Chuck Robey at "May 9, 1999 4:14:58 pm" To: chuckr@picnic.mat.net (Chuck Robey) Date: Sun, 9 May 1999 23:13:16 +0200 (CEST) Cc: freebsd-current@FreeBSD.org X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Chuck Robey wrote ... > I was thinking about Peter Wemm's recent change to the kernel Makefile, > making a way to install multiple kernels without fragging your last > known good kernel, and it got me to thinking, scragging kernel.old, now > that we have good kld's, isn't the only way to find yourself well and > truly screwed if your new kernel decides it's shy. Shy enough to hide on the swap device after a panic ;-) ? Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:37: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id A29D115D7C; Mon, 10 May 1999 13:36:26 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA09472; Mon, 10 May 1999 22:34:06 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA46622; Sun, 9 May 1999 23:11:48 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905092111.XAA46622@yedi.iaf.nl> Subject: Re: de driver problem In-Reply-To: from Doug Rabson at "May 9, 1999 9:58:40 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Sun, 9 May 1999 23:11:48 +0200 (CEST) Cc: khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.org, freebsd-current@FreeBSD.org X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Doug Rabson wrote ... > On Sun, 9 May 1999, Khaled Daham wrote: > > > Hello folks > > > > I cvsupped,made world, built a kernel today and from now on the de > > interfaces only comes up in 100BaseTX, what causes it not to negotiate ? > > My Apr_29 kernel doesnt behave like this. > > > > The link lamp flickered like hell so it was quite a nice atmosphere for > > awhile , but i got tired of it :) > > > > /Khaled, Telia Network Services > > > > Mail: khaled@telia.net > > Cell: 070-6785492 > > Work: 08-4567281 > > > > :hacker: /n./ [originally, someone who makes furniture with an axe] > > Some tulip boards in alpha systems don't autonegociate properly so the SRM > has a way of forcing them to a particular mode. A change was made recently Recently... I think it's been there for a couple of years. > to respect the SRM setting instead of using autoneg. The variable is > typically called ewa0_mode. To find the right setting, type > > >>>set ewa0_mode > > from the SRM prompt and it will give you a list of settings. Choose one, > then type e.g.: > > >>>set ewa0_mode Twisted-Pair Keep in mind that older SRMs that understand the older Tulip 10/100Mbit chips (21140 IRRC) might not recognise the new ones (is that the 21143?) Bit me once.. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:47:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (Postfix) with ESMTP id 4A35115183 for ; Mon, 10 May 1999 13:47:06 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with SMTP id NAA06806 for ; Mon, 10 May 1999 13:46:58 -0700 Message-ID: <001801be9b26$8a063e00$0d787880@apex.tapang> From: "Carlos C. Tapang" To: Subject: Some Linux news from Client Server News Date: Mon, 10 May 1999 13:49:03 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The first item is of interest to FreeBSD. Somebody should suggest to Mindcraft to include FreeBSD in the "Death Match". The last item is about Ken Thompson thrashing Linux. --Carlos Linux Watch: Mindcraft Proposes Linux-NT Death Match; Microsoft Accepts the Challenge Mindcraft, in an attempt to salvage its reputation after publishing a Microsoft-funded test in which NT trashed Linux, has invited Linus Torvalds, Red Hat or anyone they choose to try to prove that Linux can outperform NT Server in what it's calling an "Open Benchmark" shootout. Microsoft has already said it will risk the challenge. The event, if it comes off, could be way more fun than anything this side of the antitrust trial. It's put up or shut up time, boys. In the controversial tests paid for by Microsoft Mindcraft declared NT to be 3.7x faster than Linux as a web server and to have 2.5x the performance as a file server. The fact that Microsoft funded the tests and that the admission was buried on page 16 of the 20-page final report (CSN No 296) set the Linux community off. The implication, and in some cases outright accusation, was that Mindcraft rigged the tests for its patron and played pawn to the mighty Microsoft marketing machine. "Mindcraft's honesty and name have been impugned," the testing house said, citing interviews with Torvalds in publications ranging from ABCnews.com to Linux Today and Salon. In particular, the Linux community was outraged by statements in Mindcraft's report that it had attempted to find the best ways to tune Linux using the standard forms of Linux support - web sites, newsgroup pleas for help and the like. It said the response was negligible. In what Mindcraft now calls an "Open Benchmark Invitation," it says that it's willing to have Torvalds choose anyone he wants to help it tune Linux, the Samba middleware and Apache web server used in its benchmarks. Red Hat, likewise, was invited to send anyone it wants to serve as Linux experts. The Linux experts can load the software and run the tests themselves if they wish. Microsoft, it said, is welcome to send its NT experts to do the same. It also carefully stated in bold text in its invitation that Mindcraft will bear all of its own expenses for the new tests, and that it will run them "at any mutually agreeable test site." Microsoft seems pretty confident. It's volunteered to turn over its own test labs for the shoot-out, the same facility where Mindcraft made its original and now-notorious findings. That location was a bit of an eye opener unknown before. The lab offer pretty much answers the question of whether Redmond plans to have its hotshot tuning experts on hand. The only direct response from the Linux community so far has come from developer Jeremy Allison, said to be the brains behind Samba, who refused to participate unless Mindcraft tests using NT clients rather than the Win9x clients it's been using so far. In an e-mail to Mindcraft he said that Samba works better with NT clients, NT better with Win9x. Mindcraft also said that it's re-run the tests on its own using Linux tuning tips that Torvalds and open source people provided. It refuses to divulge the new results until after the new tests are run, and added that the shootout tests will be run on the same hardware that it used for its own re-test. Mindcraft has set strict ground rules for the tests, which are published on its web site, but has given Linux three chance to prove its case. The Linux world gets to run a set of benchmarks using the tunes, patches and bug fixes that Mindcraft had at its disposal when it ran the second set of tests. Then it can add whatever patches and bug fixes it would like from either the Red Hat or the open source kernel.org web sites as long as they were available on April 20 when Mindcraft started its tests, but it still has to be the Linux 2.2.6 that Mindcraft tested. Finally, the Linux experts can run a set of optional tests using any Linux kernel, Apache version, Samba version, patches and bug fixes posted on the web at the start of the Open Benchmark test. There's no mention of whether Microsoft is allowed or even wants to test Windows 2000 beta 3. Linux Watch: Linuxcare Gets El Primo Backer Kleiner Perkins, the famed VC, has made its Linux bet, putting its money into Linuxcare, the San Francisco-based Linux support house. Unfortunately, nobody's saying how big the bet is but they've imported ex-IBMer Fernand Sarrat to be CEO. Sarrat has lately been at Cylink, the security and cryptography firm as president and CEO. Before that he was at IBM for 23 years, lastly at general manager, network centric computing marketing and services, which was heavy on Internet-delivered solutions. Former Linuxcare CEO Arthur Tyde has given way to Sarrat and will stay on as executive VP, focusing on operations and external relations. Kleiner along with Sand Hill Group, who's coughing up fewer bucks, are providing Linuxcare's first round. Kleiner is putting its general partner Ted Schlein on the Linuxcare board. Linux Watch: Unix Co-Creator Trashes Linux Ken Thompson, the co-creator of Unix, thinks Linux will be a short-term phenomenon. He calls the operating system "unreliable" and sees its surge in popularity as more an anti-Microsoft backlash than anything else. Thompson, still a researcher at Lucent's Bell Labs where Unix was born, lambasts Linux in the current issue of the IEEE's online magazine, Computer. "I view Linux as something that's not Microsoft - a backlash against Microsoft, no more and no less. I don't think it will be very successful in the long run," he told Computer. Linux creator Linus Torvalds called Thompson "extremely misguided." Thompson also questions how effective the open source concept is."I've looked at the source and there are pieces that are good and pieces that are not. A whole bunch of random people have contributed to this source, and the quality varies drastically," he said. "My experience and some of my friends' experience is that Linux is quite unreliable. Microsoft is really unreliable but Linux is worse. In a non-PC environment, it just won't hold up. If you're using it on a single box, that's one thing. But if you want to use Linux in firewalls, gateways, embedded systems and so on, it has a long way to go." Carlos C. Tapang http://www.genericwindows.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:50:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from oldnews.quick.net (unknown [207.212.170.1]) by hub.freebsd.org (Postfix) with ESMTP id 30FEB14C1A; Mon, 10 May 1999 13:50:07 -0700 (PDT) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id NAA24917; Mon, 10 May 1999 13:49:46 -0700 (PDT) Date: Mon, 10 May 1999 13:49:45 -0700 (PDT) From: "Steven P. Donegan" To: Mark Murray Cc: Chuck Robey , "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: <199905102035.WAA04081@greenpeace.grondar.za> 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 have received more email today related to SPAM than I have actual SPAM in the last month+ What has triggered this solution looking for a problem? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:51:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 8031614FBA; Mon, 10 May 1999 13:51:17 -0700 (PDT) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id AAA14397; Tue, 11 May 1999 00:47:55 +0400 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.3/8.9.1) with ESMTP id AAA05565; Tue, 11 May 1999 00:50:46 +0400 (MSD) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199905102050.AAA05565@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: SPAM In-reply-to: Your message of "Mon, 10 May 1999 16:27:45 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 May 1999 00:50:45 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > "Jonathan M. Bresler" wrote: > > > with volunteers, we could moderate the list(s). mail transfer > > > would be slower as we wait for the moderator(s) to approve each piece > > > of email. if we use more than one moderator per list, the > > > time-sequence of email would be lost....we would get some very > > > strange threads...could be enteraining. > > > > Have you ever considered only allowing list members to post, or are > > there difficulties that make this impossible? I suggest following approach: moderate only mail that lack the mailing list name in To: or Cc: headers. It is far from ideal, but I think would work reasonably well. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:57:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from jane.lfn.org (ops.lfn.org [209.16.92.6]) by hub.freebsd.org (Postfix) with SMTP id 4B64F15B3E for ; Mon, 10 May 1999 13:57:16 -0700 (PDT) (envelope-from caj@lfn.org) Received: (qmail 27672 invoked by uid 100); 10 May 1999 20:57:04 -0000 Date: Mon, 10 May 1999 15:57:04 -0500 (CDT) From: Craig Johnston To: "Thomas T. Veldhouse" Cc: "Jonathan M. Bresler" , Mark Murray , current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: <036401be9b22$d35b4540$236319ac@w142844.carlson.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, 10 May 1999, Thomas T. Veldhouse wrote: > A spammer could simply become a list member and then SPAM. They won't care > if they are removed once they have perpetrated their abuse. I think most won't bother. Probably a good number of them are mailing automatically to a list of mailing lists. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 13:59:56 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 8C03B14EA9; Mon, 10 May 1999 13:59:37 -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 QAA15633; Mon, 10 May 1999 16:59:22 -0400 (EDT) (envelope-from wollman) Date: Mon, 10 May 1999 16:59:22 -0400 (EDT) From: Garrett Wollman Message-Id: <199905102059.QAA15633@khavrinen.lcs.mit.edu> To: Mark Murray Cc: "Thomas T. Veldhouse" , "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: <199905102028.WAA03970@greenpeace.grondar.za> References: <036401be9b22$d35b4540$236319ac@w142844.carlson.com> <199905102028.WAA03970@greenpeace.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Yes, but is stops the scrape 'n spammers who get the easy-to-reach > addresses off the web page. It also stops perfectly legitimate users who are subscribed to a local mailing-list exploder, read the lists through Usenet, or for other reasons are subscribed with a different address from the one or ones they use to post. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 14: 9:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (Postfix) with ESMTP id 7B7F91556B for ; Mon, 10 May 1999 14:09:32 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:20999 "EHLO vangelderen.org" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with ESMTP id <8281-10584>; Mon, 10 May 1999 23:09:18 +0200 Message-ID: <37374B07.3DD3D0A8@vangelderen.org> Date: Mon, 10 May 1999 23:09:27 +0200 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.51 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dmitrij Tejblum Cc: "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: SPAM References: <199905102050.AAA05565@tejblum.dnttm.rssi.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitrij Tejblum wrote: > > > > "Jonathan M. Bresler" wrote: > > > > with volunteers, we could moderate the list(s). mail > > > > transfer would be slower as we wait for the moderator(s) > > > > to approve each piece of email. if we use more than one > > > > moderator per list, the time-sequence of email would be > > > > lost....we would get some very strange threads...could be > > > > enteraining. > > > > > > Have you ever considered only allowing list members to > > > post, or are there difficulties that make this impossible? > > I suggest following approach: moderate only mail that lack the > mailing list name in To: or Cc: headers. It is far from ideal, > but I think would work reasonably well. May I humbly suggest that we stop this discussion until spam becomes a real problem on this list? So far this thread has generated more noise than all spam that slipped trough to the list in the past year. Jonathan is doing an awful job, please give him credit for stopping the vast majority of spam messages and let this thread die. Cheers, Jeroen -- Jeroen C. van Gelderen - jeroen@vangelderen.org - 0xC33EDFDE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 14:13: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 1618914C19; Mon, 10 May 1999 14:13:10 -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 RAA49083; Mon, 10 May 1999 17:10:38 -0400 (EDT) Date: Mon, 10 May 1999 17:10:38 -0400 (EDT) From: Chuck Robey To: Garrett Wollman Cc: Mark Murray , "Thomas T. Veldhouse" , "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: <199905102059.QAA15633@khavrinen.lcs.mit.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 On Mon, 10 May 1999, Garrett Wollman wrote: > < said: > > > Yes, but is stops the scrape 'n spammers who get the easy-to-reach > > addresses off the web page. > > It also stops perfectly legitimate users who are subscribed to a local > mailing-list exploder, read the lists through Usenet, or for other > reasons are subscribed with a different address from the one or ones > they use to post. Garrett's points are why I sugggested that it would not be a useable approach for -questions, newbies, and mabye hackers, 'cause they all get a fair amount of posts like what Garrett describes. Current and committers do NOT get such an audience, and the argument doesn't hold for those lists, which do get spammed. > > -GAWollman > > > > 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 (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 14:24:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (Postfix) with ESMTP id 8821614C19; Mon, 10 May 1999 14:24:25 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id JAA16240; Tue, 11 May 1999 09:24:21 +1200 (NZST) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.3/8.9.2) id JAA63093; Tue, 11 May 1999 09:24:01 +1200 (NZST) (envelope-from jabley) Date: Tue, 11 May 1999 09:24:00 +1200 From: Joe Abley To: Mark Murray Cc: Garrett Wollman , "Jonathan M. Bresler" , current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: SPAM Message-ID: <19990511092400.A63076@clear.co.nz> References: <19990510173115.0AAF81586E@hub.freebsd.org> <199905102014.WAA03760@greenpeace.grondar.za> <199905102025.QAA15319@khavrinen.lcs.mit.edu> <199905102029.WAA03995@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199905102029.WAA03995@greenpeace.grondar.za>; from Mark Murray on Mon, May 10, 1999 at 10:29:16PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 10, 1999 at 10:29:16PM +0200, Mark Murray wrote: > Garrett Wollman wrote: > > < said: > > > > > Have you ever considered only allowing list members to post, or are > > > there difficulties that make this impossible? > > > > Yes, there are. > > Content-free answer. Please elaborate? You might like to check the mailing list archives. This has been discussed to death many, many times. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 14:28:52 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 A620414C19; Mon, 10 May 1999 14:28:34 -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 WAA58821; Mon, 10 May 1999 22:28:49 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 10 May 1999 22:28:49 +0100 (BST) From: Doug Rabson To: Wilko Bulte Cc: khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: de driver problem In-Reply-To: <199905092111.XAA46622@yedi.iaf.nl> 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, 9 May 1999, Wilko Bulte wrote: > As Doug Rabson wrote ... > > On Sun, 9 May 1999, Khaled Daham wrote: > > > > > Hello folks > > > > > > I cvsupped,made world, built a kernel today and from now on the de > > > interfaces only comes up in 100BaseTX, what causes it not to negotiate ? > > > My Apr_29 kernel doesnt behave like this. > > > > > > The link lamp flickered like hell so it was quite a nice atmosphere for > > > awhile , but i got tired of it :) > > > > > > /Khaled, Telia Network Services > > > > > > Mail: khaled@telia.net > > > Cell: 070-6785492 > > > Work: 08-4567281 > > > > > > :hacker: /n./ [originally, someone who makes furniture with an axe] > > > > Some tulip boards in alpha systems don't autonegociate properly so the SRM > > has a way of forcing them to a particular mode. A change was made recently > > Recently... I think it's been there for a couple of years. Maybe you are remembering a NetBSD change? We just started doing the same thing in FreeBSD recently. > > > to respect the SRM setting instead of using autoneg. The variable is > > typically called ewa0_mode. To find the right setting, type > > > > >>>set ewa0_mode > > > > from the SRM prompt and it will give you a list of settings. Choose one, > > then type e.g.: > > > > >>>set ewa0_mode Twisted-Pair > > Keep in mind that older SRMs that understand the older Tulip 10/100Mbit > chips (21140 IRRC) might not recognise the new ones (is that the 21143?) > > Bit me once.. Yeah. That must be why my 164lx won't netboot. -- 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 Mon May 10 14:38:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 2024514F49 for ; Mon, 10 May 1999 14:37:44 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA12104; Mon, 10 May 1999 23:21:53 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA01357; Mon, 10 May 1999 22:58:57 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905102058.WAA01357@yedi.iaf.nl> Subject: Re: tosha after CAM changes In-Reply-To: <199905102000.OAA78016@panzer.plutotech.com> from "Kenneth D. Merry" at "May 10, 1999 2: 0:30 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Mon, 10 May 1999 22:58:57 +0200 (CEST) Cc: hodeleri@seattleu.edu, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Kenneth D. Merry wrote ... > Eric Hodel wrote... > > "Kenneth D. Merry" wrote: > > > So I'm a little confused here. Does camcontrol work? Try this: > > > > > > camcontrol devlist > > > > camcontrol: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for > > device > > > > > camcontrol tur -n da -u 0 -v > > > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > cam_lookup_pass: Inappropriate ioctl for device > > > > perhaps deleting and resupping is in order? > > It looks like you may not have the kernel side of the changes. When was > your kernel compiled? > > You may indeed want to cvsup again. I had the same phenomenon here. cvsup && buildworld && installworld && make clean tosha ; make tosha fixed it. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 15:30:40 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 C641B150BA for ; Mon, 10 May 1999 15:30:32 -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 PAA76264 for freebsd-current@freebsd.org; Mon, 10 May 1999 15:26:51 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199905102226.PAA76264@troutmask.apl.washington.edu> Subject: major/minor cleanup breakage To: freebsd-current@freebsd.org Date: Mon, 10 May 1999 15:26:51 -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 Peter, Poul, cvsup from cvsup2 at 1215 pst 10 may 99. make buildworld yields (wrapped to <80 char lines) ===> usr.sbin/i4b/isdnmonitor cc -O2 -pipe -DDEBUG -I/usr/obj/usr/src/tmp/usr/include -c \ /usr/src/usr.sbin/i4b/isdnmonitor/main.c gzip -cn /usr/src/usr.sbin/i4b/isdnmonitor/isdnmonitor.8 > isdnmonitor.8.gz /usr/src/usr.sbin/i4b/isdnmonitor/main.c:103: `major' redeclared as different\ kind of symbol /usr/obj/usr/src/tmp/usr/include/sys/types.h:114: previous declaration of \ `major' /usr/src/usr.sbin/i4b/isdnmonitor/main.c:104: `minor' redeclared as different \ kind of symbol /usr/obj/usr/src/tmp/usr/include/sys/types.h:108: previous declaration of \ `minor' {standard input}: Assembler messages: {standard input}:1519: Fatal error: Symbol minor already defined. *** Error code 1 1 error This patch might fix the problem. -- Steve --- main.c.orig Mon May 10 15:24:29 1999 +++ main.c Mon May 10 15:25:20 1999 @@ -100,8 +100,8 @@ static int sub_state = 0; static int sub_state_count = 0; -static int major = 0; -static int minor = 0; +static int isdn_major = 0; +static int isdn_minor = 0; static int nctrl = 0; static u_int32_t rights = 0; @@ -450,13 +450,13 @@ { case 0: /* initial data */ - major = I4B_GET_2B(msg, I4B_MON_IDATA_VERSMAJOR); - minor = I4B_GET_2B(msg, I4B_MON_IDATA_VERSMINOR); + isdn_major = I4B_GET_2B(msg, I4B_MON_IDATA_VERSMAJOR); + isdn_minor = I4B_GET_2B(msg, I4B_MON_IDATA_VERSMINOR); nctrl = I4B_GET_2B(msg, I4B_MON_IDATA_NUMCTRL); rights = I4B_GET_4B(msg, I4B_MON_IDATA_CLACCESS); printf("remote protocol version is %02d.%02d, %d controller(s) found, our rights = %x\n", - major, minor, nctrl, rights); + isdn_major, isdn_minor, nctrl, rights); if (nctrl > 0) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 15:46:23 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 44CFB15183 for ; Mon, 10 May 1999 15:46:19 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id QAA78933; Mon, 10 May 1999 16:45:39 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905102245.QAA78933@panzer.plutotech.com> Subject: Re: tosha after CAM changes In-Reply-To: <199905102058.WAA01357@yedi.iaf.nl> from Wilko Bulte at "May 10, 1999 10:58:57 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Mon, 10 May 1999 16:45:39 -0600 (MDT) Cc: hodeleri@seattleu.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote... > As Kenneth D. Merry wrote ... > > Eric Hodel wrote... > > > "Kenneth D. Merry" wrote: > > > > So I'm a little confused here. Does camcontrol work? Try this: > > > > > > > > camcontrol devlist > > > > > > camcontrol: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for > > > device > > > > > > > camcontrol tur -n da -u 0 -v > > > > > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > > cam_lookup_pass: Inappropriate ioctl for device > > > > > > perhaps deleting and resupping is in order? > > > > It looks like you may not have the kernel side of the changes. When was > > your kernel compiled? > > > > You may indeed want to cvsup again. > > I had the same phenomenon here. cvsup && buildworld && installworld && make > clean tosha ; make tosha fixed it. I fully expected that you would have to recompile tosha. His problem was, I think, that he did a buildworld/installworld and then rebuilt and reinstalled tosha, but it didn't work. As far as I can tell, he probably has bogus kernel sources, since camcontrol didn't work either. 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 Mon May 10 15:55:39 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 57C6B15183; Mon, 10 May 1999 15:55:38 -0700 (PDT) From: "Jonathan M. Bresler" To: mark@grondar.za Cc: current@FreeBSD.ORG In-reply-to: <199905102014.WAA03760@greenpeace.grondar.za> (message from Mark Murray on Mon, 10 May 1999 22:14:56 +0200) Subject: Re: SPAM Message-Id: <19990510225538.57C6B15183@hub.freebsd.org> Date: Mon, 10 May 1999 15:55:38 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Delivered-To: jmb@hub.freebsd.org > Cc: current@FreeBSD.ORG > References: <19990510173115.0AAF81586E@hub.freebsd.org> > Date: Mon, 10 May 1999 22:14:56 +0200 > From: Mark Murray > > "Jonathan M. Bresler" wrote: > > with volunteers, we could moderate the list(s). mail transfer > > would be slower as we wait for the moderator(s) to approve each piece > > of email. if we use more than one moderator per list, the > > time-sequence of email would be lost....we would get some very > > strange threads...could be enteraining. > > Have you ever considered only allowing list members to post, or are > there difficulties that make this impossible? yes...i have. that policy may be appropriate for some of the lists, but it is certainly not appropriate for -questions, -newbies and some others. a person could subscribe and then spam. not likely but possible. > > couple messages. i do not believe it is worthwhile ot moderate the > > lists. > > Do you have any stats of "accepted mail" vs "rejected mail" vs SPAM? used to keep track, but lost interest...didnt seem to be much information there. spam seems to come in waves. these days, for the freebsd-mailing lists at least, sems to be more like ripples ;) jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 15:58:18 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id BE02715183; Mon, 10 May 1999 15:58:17 -0700 (PDT) From: "Jonathan M. Bresler" To: wollman@khavrinen.lcs.mit.edu Cc: mark@grondar.za, current@FreeBSD.ORG In-reply-to: <199905102025.QAA15319@khavrinen.lcs.mit.edu> (message from Garrett Wollman on Mon, 10 May 1999 16:25:05 -0400 (EDT)) Subject: Re: SPAM Message-Id: <19990510225817.BE02715183@hub.freebsd.org> Date: Mon, 10 May 1999 15:58:17 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > < said: > > > Have you ever considered only allowing list members to post, or are > > there difficulties that make this impossible? > > Yes, there are. > i forgot to mention that such a policy creates a single "allowed" address per user...not good. jmb > -GAWollman > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 16: 2:50 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id BCB95155C3; Mon, 10 May 1999 16:02:35 -0700 (PDT) From: "Jonathan M. Bresler" To: donegan@quick.net Cc: mark@grondar.za, chuckr@picnic.mat.net, current@FreeBSD.ORG In-reply-to: (donegan@quick.net) Subject: Re: SPAM Message-Id: <19990510230235.BCB95155C3@hub.freebsd.org> Date: Mon, 10 May 1999 16:02:35 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Mon, 10 May 1999 13:49:45 -0700 (PDT) > From: "Steven P. Donegan" > > I have received more email today related to SPAM than I have actual SPAM > in the last month+ What has triggered this solution looking for a problem? > that is an eloquent statement of the situat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 16:10:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa17-44.ix.netcom.com [207.93.156.44]) by hub.freebsd.org (Postfix) with ESMTP id 6206E14C9A for ; Mon, 10 May 1999 16:10:34 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id QAA12094; Mon, 10 May 1999 16:10:32 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Mon, 10 May 1999 16:10:32 -0700 (PDT) Message-Id: <199905102310.QAA12094@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: freebsd-current@FreeBSD.ORG Subject: Make -j12 world Failed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running 4.0-current SMP as of Apr 29. I cvsup'ed this morning and at about 0950, started 'make -j12 world > log.file'. I returned to find the machine frozen and the console blank. Pressing a key resulted in a high-pitched squeal and no other response. Could not ping the machine. Power-cycled to clear. I extracted some error messages from /var/log/messages and have attached dmesg. Make world stopped in the midst of making man pages. There were no errors reported in the log file. At 1020 this morning, there was an "object inconsistant state: RPC: 1, RC: 0" message that repeated many times. The machine had been up for a week. I restarted make -j12 world and will build a new kernel, if make world is successful. tomdean ===== from /var/log/messages ========================== ... May 9 22:56:54 celebris /kernel: da1 at ncr0 bus 0 target 1 lun 0 May 9 22:56:54 celebris /kernel: da1: Fixed Direct Access SCSI-2 device May 9 22:56:54 celebris /kernel: da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled May 9 22:56:54 celebris /kernel: da1: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) May 9 22:56:54 celebris /kernel: changing root device to da1s1a May 9 22:56:57 celebris lpd[169]: restarted May 10 09:39:22 celebris su: tomdean to root on /dev/ttyp0 May 10 10:20:28 celebris /kernel: object inconsistant state: RPC: 1, RC: 0 May 10 10:21:03 celebris last message repeated 57 times May 10 10:23:04 celebris last message repeated 82 times May 10 10:23:11 celebris last message repeated 3 times May 10 15:49:41 celebris /kernel: Copyright (c) 1992-1999 The FreeBSD Project. May 10 15:49:41 celebris /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 May 10 15:49:41 celebris /kernel: The Regents of the University of California. All rights reserved. May 10 15:49:41 celebris /kernel: FreeBSD 4.0-CURRENT #0: Thu Apr 29 16:25:13 PDT 1999 May 10 15:49:41 celebris /kernel: tomdean@celebris:/usr/src/sys/compile/CELEBRIS-SMP May 10 15:49:41 celebris /kernel: Timecounter "i8254" frequency 1193182 Hz May 10 15:49:41 celebris /kernel: CPU: Pentium/P54C (586-class CPU) May 10 15:49:41 celebris /kernel: Origin = "GenuineIntel" Id = 0x525 Stepping=5 May 10 15:49:41 celebris /kernel: Features=0x3bf May 10 15:49:41 celebris /kernel: real memory = 100663296 (98304K bytes) ... ===== dmesg ================ 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 Apr 29 16:25:13 PDT 1999 tomdean@celebris:/usr/src/sys/compile/CELEBRIS-SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x3bf real memory = 100663296 (98304K bytes) avail memory = 94916608 (92692K bytes) Programming 16 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02c0000. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 ncr0: at device 1.0 on pci0 ncr0: interrupting at irq 11 isab0: at device 2.0 on pci0 de0: at device 8.0 on pci0 de0: interrupting at irq 10 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db isa0: on motherboard fdc0: interrupting at irq 6 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 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: PC87334 chipset (PS2/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppc0: interrupting at irq 7 Intel Pentium detected, installing workaround for F00F bug APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 10 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! (probe6:ncr0:0:6:0): COMMAND FAILED (6 ff) @0xc09ebe00. (probe5:ncr0:0:5:0): COMMAND FAILED (6 ff) @0xc09e9400. (probe4:ncr0:0:4:0): COMMAND FAILED (6 ff) @0xc09e9a00. (probe3:ncr0:0:3:0): COMMAND FAILED (6 ff) @0xc09e8000. (probe2:ncr0:0:2:0): COMMAND FAILED (6 ff) @0xc09e8600. (probe1:ncr0:0:1:0): COMMAND FAILED (6 ff) @0xc09e8c00. (probe0:ncr0:0:0:0): COMMAND FAILED (6 ff) @0xc09c5200. da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: cd present [271780 x 2048 byte records] da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 1029MB (2109376 512 byte sectors: 255H 63S/T 131C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) changing root device to da1s1a WARNING: / was not properly dismounted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 17:42:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from hydrogen.fircrest.net (metriclient-2.uoregon.edu [128.223.172.2]) by hub.freebsd.org (Postfix) with ESMTP id B4523151C9; Mon, 10 May 1999 17:42:29 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.fircrest.net (8.9.1/8.8.7) id RAA06683; Mon, 10 May 1999 17:42:02 -0700 (PDT) Message-ID: <19990510174202.29832@hydrogen.nike.efn.org> Date: Mon, 10 May 1999 17:42:02 -0700 From: John-Mark Gurney To: Chuck Robey Cc: "Thomas T. Veldhouse" , "Jonathan M. Bresler" , Mark Murray , current@FreeBSD.ORG Subject: Re: SPAM References: <036401be9b22$d35b4540$236319ac@w142844.carlson.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Chuck Robey on Mon, May 10, 1999 at 04:29:54PM -0400 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey scribbled this message on May 10: > On Mon, 10 May 1999, Thomas T. Veldhouse wrote: > > > A spammer could simply become a list member and then SPAM. They won't care > > if they are removed once they have perpetrated their abuse. > > The could, but most wouldn't, wouldn't even know how. It wouldn't be > a sure cure, but it would sure help. Don't do it on newbies type lists, > like -questions or -newbies, even multimedia gets a lot of newbies. > Current and committers would be good candidates. there are a couple MAJOR problems with doing that to committers: a) I don't use my jmg@freebsd.org account to send mail, I'd have to do that, as just simply being a commiter gets your freebsd account subscribed to cvs-committers. I wondered why I was getting double commit messages when I became a committer, till I realized this and unsubscribed from cvs-all. b) If a normal user responds to mail to cvs-all, us committers wouldn't get the response as their reply would be dropped because they aren't on cvs-committers, but everyone else on cvs-* would get the reply. I have only recieved 61 spam messages so far since the begining of the year, this includes the dups to multiple mailing lists and myself. This is about one every other day, and considering most are dups, that isn't even two a week... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 18:16:18 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 48A4F1508D; Mon, 10 May 1999 18:16:15 -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 TAA16055; Mon, 10 May 1999 19:36:24 -0400 (EDT) (envelope-from wollman) Date: Mon, 10 May 1999 19:36:24 -0400 (EDT) From: Garrett Wollman Message-Id: <199905102336.TAA16055@khavrinen.lcs.mit.edu> To: Chuck Robey Cc: Garrett Wollman , Mark Murray , "Thomas T. Veldhouse" , "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: SPAM In-Reply-To: References: <199905102059.QAA15633@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > a fair amount of posts like what Garrett describes. Current and > committers do NOT get such an audience, and the argument doesn't hold > for those lists, Yes they do. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 19:13:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 1EF4715DB6 for ; Mon, 10 May 1999 19:12:35 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: by eagle.phc.igs.net (Postfix, from userid 1003) id 9B1401886; Mon, 10 May 1999 21:11:47 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by eagle.phc.igs.net (Postfix) with SMTP id 95CA513; Mon, 10 May 1999 21:11:47 +0000 (GMT) Date: Mon, 10 May 1999 21:11:47 +0000 (GMT) From: eagle To: Chuck Robey Cc: "Thomas T. Veldhouse" , "Jonathan M. Bresler" , Mark Murray , current@FreeBSD.ORG Subject: Re: SPAM 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, 10 May 1999, Chuck Robey wrote: > On Mon, 10 May 1999, Thomas T. Veldhouse wrote: > > > A spammer could simply become a list member and then SPAM. They won't care > > if they are removed once they have perpetrated their abuse. > > The could, but most wouldn't, wouldn't even know how. It wouldn't be > a sure cure, but it would sure help. Don't do it on newbies type lists, > like -questions or -newbies, even multimedia gets a lot of newbies. > Current and committers would be good candidates. So you got some spam from the mailing list, so you generate a few hundred more emails about the spam, i'm being spammed by anti spam email :) Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 19:14: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id CB63714DAA; Mon, 10 May 1999 19:13:55 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id CAA08686; Tue, 11 May 1999 02:13:19 GMT Message-Id: <199905110213.CAA08686@chandra.eatell.msr.prug.or.jp> To: Peter Wemm Cc: Nick Hibma , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Mon, 10 May 1999 22:32:11 +0800." <19990510143213.E2FD91F72@spinner.netplex.com.au> Date: Tue, 11 May 1999 11:13:18 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was thinking of doing this, the same as alpm and intpm: > > case 0x: > #if NUHCI > 0 > return NULL; > #else > return "VIA blah USB controller"; > #endif It depends on old-config, so poor mechanism. newconfig already implimented best match probe/attach. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 May 10 19:20:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail0.atl.bellsouth.net (mail0.atl.bellsouth.net [205.152.0.27]) by hub.freebsd.org (Postfix) with ESMTP id 530FD14BD5 for ; Mon, 10 May 1999 19:20:37 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-69-179.atl.bellsouth.net [209.214.69.179]) by mail0.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id WAA16142; Mon, 10 May 1999 22:19:52 -0400 (EDT) Received: from wghicks (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id WAA02239; Mon, 10 May 1999 22:21:49 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199905110221.WAA02239@bellsouth.net> To: Doug Rabson Cc: Brian Feldman , current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: 3DNow! support? In-reply-to: Your message of "Mon, 10 May 1999 09:55:47 BST." Date: Mon, 10 May 1999 22:21:49 -0400 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is anyone planning on upgrading the binutils gas to a later version > > so that we can get 3DNow! support? I'd like to use it, but I can't > > seem to get binutils to work right manually. > I will update binutils when/if 2.9.2 comes out. I've seen some post-2.9.1 patches from the Debian folks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 21: 2: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 161361516C for ; Mon, 10 May 1999 21:01:54 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (unknown [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 90BB7224 for ; Tue, 11 May 1999 04:01:52 +0000 (GMT) Date: Tue, 11 May 1999 08:01:52 +0400 (MSD) From: oZZ!!! To: freebsd-current@FreeBSD.org Subject: Tonight make world failed at isdnmonitor... 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! Makeworld failed at isdnmonitor: ===> usr.sbin/i4b/isdnmonitor cc -Os -pipe -mpentium -DDEBUG -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/i4b/isdn monitor/main.c /usr/src/usr.sbin/i4b/isdnmonitor/main.c:103: `major' redeclared as different kind of symbol /usr/obj/usr/src/tmp/usr/include/sys/types.h:114: previous declaration of `major' /usr/src/usr.sbin/i4b/isdnmonitor/main.c:104: `minor' redeclared as different kind of symbol /usr/obj/usr/src/tmp/usr/include/sys/types.h:108: previous declaration of `minor' {standard input}: Assembler messages: {standard input}:1510: Fatal error: Symbol minor already defined. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Any idea? Rgdz, Sergey Osokin aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 21: 8:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 3513314FE4 for ; Mon, 10 May 1999 21:07:59 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: by eagle.phc.igs.net (Postfix, from userid 1003) id 774701886; Mon, 10 May 1999 23:07:06 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by eagle.phc.igs.net (Postfix) with SMTP id 722BF1C; Mon, 10 May 1999 23:07:06 +0000 (GMT) Date: Mon, 10 May 1999 23:07:06 +0000 (GMT) From: eagle To: oZZ!!! Cc: freebsd-current@FreeBSD.ORG Subject: Re: Tonight make world failed at isdnmonitor... 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 Tue, 11 May 1999, oZZ!!! wrote: > > Hello! > Makeworld failed at isdnmonitor: > > ===> usr.sbin/i4b/isdnmonitor > cc -Os -pipe -mpentium -DDEBUG -I/usr/obj/usr/src/tmp/usr/include -c > /usr/src/usr.sbin/i4b/isdn > monitor/main.c > /usr/src/usr.sbin/i4b/isdnmonitor/main.c:103: `major' redeclared as > different kind of symbol > /usr/obj/usr/src/tmp/usr/include/sys/types.h:114: previous declaration of > `major' > /usr/src/usr.sbin/i4b/isdnmonitor/main.c:104: `minor' redeclared as > different kind of symbol > /usr/obj/usr/src/tmp/usr/include/sys/types.h:108: previous declaration of > `minor' > {standard input}: Assembler messages: > {standard input}:1510: Fatal error: Symbol minor already defined. > *** Error code 1 tell phk thanks this ones related to his changes to types.h as well Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 21:18:41 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 6FD1014FE4 for ; Mon, 10 May 1999 21:18: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 NAA22295 for ; Tue, 11 May 1999 13:48:34 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA66832 for FreeBSD-current@FreeBSD.ORG; Tue, 11 May 1999 13:48:32 +0930 (CST) Date: Tue, 11 May 1999 13:48:31 +0930 From: Greg Lehey To: FreeBSD current users Subject: Panic unloading klds? Message-ID: <19990511134831.D65965@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i 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 In a new kernel, I can no longer unload the Vinum kld: I get a panic in module_release: Program received signal SIGSEGV, Segmentation fault. 0xc014460e in module_release (mod=0xc0f5a600) at ../../kern/kern_module.c:163 163 TAILQ_REMOVE(&mod->file->modules, mod, flink); (kgdb) bt #0 0xc014460e in module_release (mod=0xc0f5a600) at ../../kern/kern_module.c:163 #1 0xc0144f6e in linker_file_unload (file=0xc0f5c300) at ../../kern/kern_linker.c:443 #2 0xc0145525 in kldunload (p=0xc68a3260, uap=0xc6df5f90) at ../../kern/kern_linker.c:734 #3 0xc021fab6 in syscall (frame=) at ../../i386/i386/trap.c:1066 #4 0xc02122e0 in Xint0x80_syscall () #5 0x80484de in ?? () #6 0x8048414 in ?? () #7 0x80480e9 in ?? () (kgdb) f 0 #0 0xc014460e in module_release (mod=0xc0f5a600) at ../../kern/kern_module.c:163 163 TAILQ_REMOVE(&mod->file->modules, mod, flink); I haven't had time to completely eliminate the possibility that it's a problem with Vinum, but it looks unlikely. Has anybody else seen this? Has anybody else unloaded klds from a -CURRENT of the last 3 days or so without seeing this? 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 Mon May 10 21:45:32 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 E43C515899 for ; Mon, 10 May 1999 21:45:30 -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 VAA10383; Mon, 10 May 1999 21:48:18 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199905110448.VAA10383@troutmask.apl.washington.edu> Subject: Re: Tonight make world failed at isdnmonitor... In-Reply-To: from oZZ!!! at "May 11, 1999 08:01:52 am" To: osa@etrust.ru (oZZ!!!) Date: Mon, 10 May 1999 21:48:18 -0700 (PDT) Cc: 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 sent a patch for this about 8 hours ago. No one seems to read -current. oZZ!!! wrote: > > Hello! > Makeworld failed at isdnmonitor: > > ===> usr.sbin/i4b/isdnmonitor > cc -Os -pipe -mpentium -DDEBUG -I/usr/obj/usr/src/tmp/usr/include -c > /usr/src/usr.sbin/i4b/isdn > monitor/main.c > /usr/src/usr.sbin/i4b/isdnmonitor/main.c:103: `major' redeclared as > different kind of symbol > /usr/obj/usr/src/tmp/usr/include/sys/types.h:114: previous declaration of > `major' > /usr/src/usr.sbin/i4b/isdnmonitor/main.c:104: `minor' redeclared as > different kind of symbol > /usr/obj/usr/src/tmp/usr/include/sys/types.h:108: previous declaration of > `minor' > {standard input}: Assembler messages: > {standard input}:1510: Fatal error: Symbol minor already defined. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > Any idea? > > Rgdz, > Sergey Osokin aka oZZ, > osa@etrust.ru > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 23: 6:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 802AF1590D for ; Mon, 10 May 1999 23:06:25 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id PAA20713; Tue, 11 May 1999 15:03:45 +0900 (JST) Message-ID: <3737B5AB.353025AB@newsguy.com> Date: Tue, 11 May 1999 13:44:27 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Chuck Robey Cc: Mark Murray , "Thomas T. Veldhouse" , current@FreeBSD.ORG Subject: Re: SPAM References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > Garrett's points are why I sugggested that it would not be a useable > approach for -questions, newbies, and mabye hackers, 'cause they all get > a fair amount of posts like what Garrett describes. Current and > committers do NOT get such an audience, and the argument doesn't hold > for those lists, which do get spammed. 1) It *DOES* hold for committers, since it's closed subscription. For example, Matthew Dillon would be left out. 2) It *DOES* hold for -current, since many committers find it's signal/noise ratio too low. For instance, Robert Nordier (the boot guy). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 10 23:30:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id D1B9314F4B for ; Mon, 10 May 1999 23:30:41 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id HAA27137; Tue, 11 May 1999 07:20:03 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id HAA34245; Tue, 11 May 1999 07:19:31 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199905110619.HAA34245@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: chris@calldei.com Cc: Brian Somers , Chuck Robey , current@FreeBSD.ORG Subject: Re: ppp is totally broken In-reply-to: Your message of "Mon, 10 May 1999 13:31:49 CDT." <19990510133149.I22538@holly.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 May 1999 07:19:28 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, May 9, 1999, Brian Somers wrote: > > [.....] > > > I'm using the 3.1R PPP right now, until the problem is > > > resolved. I'm sending a problem report, as well. > > > > It should be resolved now. A NULL mbuf value is valid - it just > > means that there's nothing in it. I changed fsm_Input() with the > > Wouldn't it be better for *bp to be NULL instead of bp? bp is a ``struct mbuf *''. *bp (a struct mbuf) can't be NULL. [.....] > -- > Chris Costello > Expert systems are built to embody the knowledge of human experts. - Kulawiec -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 0:14: 4 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 2189215902 for ; Tue, 11 May 1999 00:14:01 -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 IAA90306; Tue, 11 May 1999 08:14:24 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 11 May 1999 08:14:24 +0100 (BST) From: Doug Rabson To: W Gerald Hicks Cc: Brian Feldman , current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net.demon.co.uk Subject: Re: 3DNow! support? In-Reply-To: <199905110221.WAA02239@bellsouth.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 Mon, 10 May 1999, W Gerald Hicks wrote: > > > Is anyone planning on upgrading the binutils gas to a later version > > > so that we can get 3DNow! support? I'd like to use it, but I can't > > > seem to get binutils to work right manually. > > > I will update binutils when/if 2.9.2 comes out. > > I've seen some post-2.9.1 patches from the Debian folks... > I'm waiting for the official gnu release. -- 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 Tue May 11 0:21:52 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 95FEE158AA; Tue, 11 May 1999 00:21:49 -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 IAA90331; Tue, 11 May 1999 08:21:37 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 11 May 1999 08:21:37 +0100 (BST) From: Doug Rabson To: NAKAGAWA Yoshihisa Cc: Peter Wemm , Nick Hibma , current@freebsd.org Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905110213.CAA08686@chandra.eatell.msr.prug.or.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 Tue, 11 May 1999, NAKAGAWA Yoshihisa wrote: > > I was thinking of doing this, the same as alpm and intpm: > > > > case 0x: > > #if NUHCI > 0 > > return NULL; > > #else > > return "VIA blah USB controller"; > > #endif > > It depends on old-config, so poor mechanism. newconfig already > implimented best match probe/attach. And a very useful mechanism it is. Which is why I implemented priority ordered probes in -current. -- 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 Tue May 11 0:59:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id CDFB715938 for ; Tue, 11 May 1999 00:59:30 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: by eagle.phc.igs.net (Postfix, from userid 1003) id 02A52188B; Tue, 11 May 1999 02:58:54 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by eagle.phc.igs.net (Postfix) with SMTP id DB2461C; Tue, 11 May 1999 02:58:54 +0000 (GMT) Date: Tue, 11 May 1999 02:58:54 +0000 (GMT) From: eagle To: Steve Kargl Cc: oZZ!!! , freebsd-current@FreeBSD.ORG Subject: Re: Tonight make world failed at isdnmonitor... In-Reply-To: <199905110448.VAA10383@troutmask.apl.washington.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 On Mon, 10 May 1999, Steve Kargl wrote: > I sent a patch for this about 8 hours ago. No one seems > to read -current. well it still is broken and i must of missed that patch somewhere in my mail, 3:58 a.m east coast time tuesday 11 rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 1:13:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 6C5C315120 for ; Tue, 11 May 1999 01:13:13 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id SAA21580 for current@freebsd.org; Tue, 11 May 1999 18:24:18 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905110824.SAA21580@cimlogic.com.au> Subject: ROOTDEVNAME changes break MFS_ROOT only kernels To: current@freebsd.org Date: Tue, 11 May 1999 18:24:18 +1000 (EST) 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 Prior to the ROOTDEVNAME changes, I used to build embedded kernels with MFS_ROOT and MFS_ROOT_SIZE options, plus the config line as: config foo root on wd0 but _without_ any disk devices or disk controllers. The "root on wd0" on the config line was to satisfy the config(8) syntax, but was overriden by the use of MFS_ROOT AFAIK. After the ROOTDEVNAME changes, the kernel always tries to mount a root file system from a _device_ regardless of the MFS_ROOT option. Such a kernel will always panic with: "error 6: panic: cannot mount root (2)". FWIW, this is the kernel config file for an embedded kernel (called gizmo): # # GIZMO -- A little gizmo thingy. # machine "i386" cpu "I386_CPU" ident GENERIC maxusers 2 options MATH_EMULATE # Support for x87 emulation options INET # InterNETworking options MFS # Memory filesystem options "COMPAT_43" # Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE # Allow users to grab the console options FAILSAFE # Be conservative options MFS_ROOT # Use a memory file system as root. options MFS_ROOT_SIZE=2048 # Space for MFS root filesystem. options INIT_PATH="/gizmo" config gizmo controller isa0 device npx0 at nexus? port IO_NPX irq 13 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device ed0 at isa? port 0x300 irq 11 iomem 0xd8000 pseudo-device loop pseudo-device ether Nice and simple, but after the ROOTDEVNAME changes, it cannot work. Sulk. The ROOTDEVNAME stuff needs to be fixed to allow this. Local disks and disk controllers should be optional. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 1:33:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcsext.hcs.de (hcsext.hcs.de [194.123.40.2]) by hub.freebsd.org (Postfix) with SMTP id 6352715940 for ; Tue, 11 May 1999 01:33:11 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1493 bytes) by hcsext.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Tue, 11 May 1999 10:33:11 +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 m10h7yQ-0000e7C; Tue, 11 May 99 10:33 METDST Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: Tonight make world failed at isdnmonitor... In-Reply-To: from eagle at "May 11, 99 02:58:54 am" To: freebsd-current@FreeBSD.ORG Date: Tue, 11 May 1999 10:33:10 +0200 (METDST) 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: 684 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I sent a patch for this about 8 hours ago. No one seems > > to read -current. > well it still is broken and i must of missed that patch somewhere in my > mail, > > 3:58 a.m east coast time tuesday 11 just read mail, tested Steves fix, committed. 10:23 am central european summer time tuesday 11 The world is round and needs 24 hours to rotate once. ;-) 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 Tue May 11 3:15:19 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 1D5AD15BF6; Tue, 11 May 1999 03:15:15 -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 MAA30302; Tue, 11 May 1999 12:15:08 +0200 (CEST) (envelope-from des) To: Chuck Robey Cc: Garrett Wollman , Mark Murray , "Thomas T. Veldhouse" , "Jonathan M. Bresler" , current@FreeBSD.ORG Subject: Re: SPAM References: From: Dag-Erling Smorgrav Date: 11 May 1999 12:15:07 +0200 In-Reply-To: Chuck Robey's message of "Mon, 10 May 1999 17:10:38 -0400 (EDT)" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey writes: > Garrett's points are why I sugggested that it would not be a useable > approach for -questions, newbies, and mabye hackers, 'cause they all get > a fair amount of posts like what Garrett describes. Current and > committers do NOT get such an audience, and the argument doesn't hold > for those lists, which do get spammed. Oh no? I regularly send mail to -current and -committers from at least three different addresses, none of which are subscribed. Listen up. We've been through this before. We all agreed it wouldn't work. If you wanna know why, search the archives instead of making the problem considerably worse by starting (and fueling) threads such as this. 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 Tue May 11 3:25: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [36.118.0.70]) by hub.freebsd.org (Postfix) with ESMTP id BE3F9159C0; Tue, 11 May 1999 03:25:03 -0700 (PDT) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.9.3/8.9.1) id DAA01705; Tue, 11 May 1999 03:23:57 -0700 (PDT) Date: Tue, 11 May 1999 03:23:57 -0700 (PDT) From: Bob Vaughan Message-Id: <199905111023.DAA01705@tantivy.stanford.edu> To: chuckr@picnic.mat.net, des@flood.ping.uio.no Subject: Re: SPAM Cc: current@FreeBSD.ORG, jmb@hub.freebsd.org, mark@grondar.za, veldy@visi.com, wollman@khavrinen.lcs.mit.edu In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG here's an idea.. why not have two addresses for the list. the first would be the public address, and would be restricted to subscribers. the second would be a non-published address, which would be unrestricted, and would feed the published list via a side door. only the first list would be open for subscriptions. -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org | P.O. Box 9792, Stanford, Ca 94309-9792 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 5:28:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 503641590E for ; Tue, 11 May 1999 05:28:10 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id C870E1F72; Tue, 11 May 1999 20:28:07 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: eagle Cc: oZZ!!! , freebsd-current@FreeBSD.ORG Subject: Re: Tonight make world failed at isdnmonitor... In-reply-to: Your message of "Mon, 10 May 1999 23:07:06 GMT." Date: Tue, 11 May 1999 20:28:07 +0800 From: Peter Wemm Message-Id: <19990511122808.C870E1F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ===> usr.sbin/i4b/isdnmonitor > > cc -Os -pipe -mpentium -DDEBUG -I/usr/obj/usr/src/tmp/usr/include -c > > /usr/src/usr.sbin/i4b/isdn > > monitor/main.c > > /usr/src/usr.sbin/i4b/isdnmonitor/main.c:103: `major' redeclared as > > different kind of symbol > > /usr/obj/usr/src/tmp/usr/include/sys/types.h:114: previous declaration of > > `major' > > /usr/src/usr.sbin/i4b/isdnmonitor/main.c:104: `minor' redeclared as > > different kind of symbol > > /usr/obj/usr/src/tmp/usr/include/sys/types.h:108: previous declaration of > > `minor' > > {standard input}: Assembler messages: > > {standard input}:1510: Fatal error: Symbol minor already defined. > > *** Error code 1 > > tell phk thanks this ones related to his changes to types.h as well phk has another patch in the pipeline right now that fixes this (ie: major() etc become macros again in userlant.) I'd have jumped in and tweaked types.h to fix this particular problem, but that would be just adding more deltas to dead-end code. I think phk was planning a checkpoint commit sometime shortly. If he gets delayed, I'll give types.h a tweak to avoid the problems and to buy some time. Please remember, this is -current, we've got to expect things to be broken every so often - but on the other hand, staying broken for too long is an inconvenience for the developers who -current is intended for. > Rob Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 7:19:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 55CAD14F2C; Tue, 11 May 1999 07:19:24 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id PAA26575; Tue, 11 May 1999 15:54:08 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA01002; Mon, 10 May 1999 23:55:31 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905102155.XAA01002@yedi.iaf.nl> Subject: Re: de driver problem In-Reply-To: from Doug Rabson at "May 10, 1999 10:28:49 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Mon, 10 May 1999 23:55:31 +0200 (CEST) Cc: khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.org, freebsd-current@FreeBSD.org X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Doug Rabson wrote ... > On Sun, 9 May 1999, Wilko Bulte wrote: > > > As Doug Rabson wrote ... > > > On Sun, 9 May 1999, Khaled Daham wrote: > > > > > > > Hello folks > > > > > > > > I cvsupped,made world, built a kernel today and from now on the de > > > > > > Some tulip boards in alpha systems don't autonegociate properly so the SRM > > > has a way of forcing them to a particular mode. A change was made recently > > > > Recently... I think it's been there for a couple of years. > > Maybe you are remembering a NetBSD change? We just started doing the same > thing in FreeBSD recently. Oops I was confusing things with another email about the messages the driver spits out on dma not keeping up. > > > to respect the SRM setting instead of using autoneg. The variable is > > > typically called ewa0_mode. To find the right setting, type > > > > > > >>>set ewa0_mode > > > > > > from the SRM prompt and it will give you a list of settings. Choose one, > > > then type e.g.: > > > > > > >>>set ewa0_mode Twisted-Pair > > > > Keep in mind that older SRMs that understand the older Tulip 10/100Mbit > > chips (21140 IRRC) might not recognise the new ones (is that the 21143?) > > > > Bit me once.. > > Yeah. That must be why my 164lx won't netboot. Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit only) worked just dandy. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 7:27:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (mvo-ca18-15.ix.netcom.com [207.93.156.143]) by hub.freebsd.org (Postfix) with ESMTP id B4D0E15F36 for ; Tue, 11 May 1999 07:27:15 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id HAA39426; Tue, 11 May 1999 07:27:12 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Tue, 11 May 1999 07:27:12 -0700 (PDT) Message-Id: <199905111427.HAA39426@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: freebsd-current@freebsd.org Subject: Make World Fails - minor and major conflict Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running -current SMP as of last week. I cvsup'ed last night and started a 'Make -j12 world'. tomdean ===> usr.sbin/i4b/isdnmonitor cc -O2 -m486 -pipe -DDEBUG -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/i4b/isdnmonitor/main.c gzip -cn /usr/src/usr.sbin/i4b/isdnmonitor/isdnmonitor.8 > isdnmonitor.8.gz /usr/src/usr.sbin/i4b/isdnmonitor/main.c:103: `major' redeclared as different kind of symbol /usr/obj/usr/src/tmp/usr/include/sys/types.h:114: previous declaration of `major' /usr/src/usr.sbin/i4b/isdnmonitor/main.c:104: `minor' redeclared as different kind of symbol /usr/obj/usr/src/tmp/usr/include/sys/types.h:108: previous declaration of `minor' {standard input}: Assembler messages: {standard input}:1519: Fatal error: Symbol minor already defined. *** Error code 1 1 error *** 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 *** 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 Tue May 11 7:38: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 8B7BA14DF8 for ; Tue, 11 May 1999 07:37:59 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: by eagle.phc.igs.net (Postfix, from userid 1003) id A4DEE18B2; Tue, 11 May 1999 09:37:30 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by eagle.phc.igs.net (Postfix) with SMTP id 83DAB14; Tue, 11 May 1999 09:37:30 +0000 (GMT) Date: Tue, 11 May 1999 09:37:29 +0000 (GMT) From: eagle To: Hellmuth Michaelis Cc: freebsd-current@FreeBSD.ORG Subject: Re: Tonight make world failed at isdnmonitor... 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 Tue, 11 May 1999, Hellmuth Michaelis wrote: > > > > I sent a patch for this about 8 hours ago. No one seems > > > to read -current. > > well it still is broken and i must of missed that patch somewhere in my > > mail, > > > > 3:58 a.m east coast time tuesday 11 > > just read mail, tested Steves fix, committed. > > 10:23 am central european summer time tuesday 11 > > The world is round and needs 24 hours to rotate once. ;-) > > hellmuth O.k. I admit it i've been an ass over changing the names of 2 variables in what was it 8 lines of code. rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 8: 5:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id B449815044 for ; Tue, 11 May 1999 08:05:25 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: by eagle.phc.igs.net (Postfix, from userid 1003) id 5595C18B2; Tue, 11 May 1999 10:04:57 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by eagle.phc.igs.net (Postfix) with SMTP id 5058514; Tue, 11 May 1999 10:04:57 +0000 (GMT) Date: Tue, 11 May 1999 10:04:57 +0000 (GMT) From: eagle To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: Make World Fails - minor and major conflict In-Reply-To: <199905111427.HAA39426@ix.netcom.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 Tue, 11 May 1999, Thomas Dean wrote: > I am running -current SMP as of last week. > > I cvsup'ed last night and started a 'Make -j12 world'. > cvsup again that should fix it. if it doesnt add my or anything else for that matter, to all occurances of the variable minor and major in that file. Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 9:16:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id D439C154F4; Tue, 11 May 1999 09:15:22 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA25904; Tue, 11 May 1999 12:14:59 -0400 From: Bill Paul Message-Id: <199905111614.MAA25904@skynet.ctr.columbia.edu> Subject: Anybody actually using gigabit ethernet? To: current@freebsd.org, stable@freebsd.org Date: Tue, 11 May 1999 12:14:56 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1950 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm wondering if anybody out there has actually done any experimentation with gigabit ethernet boards using the Alteon Tigon driver. I know that it works on my hardware, but it's nice to actually have some feedback from people so that I know if it's actually working worth a damn. So far I have not heard a peep out of anybody, other than a couple of people who were nice enough to help out with some driver testing, and that was months ago. I usually consider this a good thing, because it means that at least nobody is complaining. But when people ask me "hey Bill, how well do these boards work with FreeBSD?" all I can tell them is that they seem to work okay in my limited test environment. This does not exactly provide a lot of motivation to go out and buy some gigabit ethernet cards. Also, I only have access to a limited selection of cards (I have a 3Com and a Netgear board, and others have tested AceNIC boards) so I don't know for sure if some of the ones that I claim to support actually work. (I don't have any reason to believe they won't, but Murphy's Law applies.) I also don't have access to a gigabit switch, so my testing is limited to blasting traffic between two hosts through a fiber patch. So, if anybody is actually using a Tigon-based gigabit board with STABLE or CURRENT, let me know. Is it working reliably? Is performance good? Is it bad? Inquiring minds want to know. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 9:26:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw.aa.net [206.125.75.16]) by hub.freebsd.org (Postfix) with ESMTP id 6269C14BEE; Tue, 11 May 1999 09:26:15 -0700 (PDT) (envelope-from dennis.glatting@software-munitions.com) Received: from localhost (dennisg@localhost) by btw.plaintalk.bellevue.wa.us (8.9.3/8.9.3) with ESMTP id JAA32528; Tue, 11 May 1999 09:25:36 -0700 (PDT) Date: Tue, 11 May 1999 09:25:35 -0700 (PDT) From: Dennis Glatting To: Bill Paul Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Anybody actually using gigabit ethernet? In-Reply-To: <199905111614.MAA25904@skynet.ctr.columbia.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 In reading your message I felt compelled to ask you a question. Are you using gb end-to-end? That probably isn't a good idea because in TCP the sequence numbers can wrap within timeout periods and the data stream become undetectably (from a TCP perspective) corrupt. -- Dennis Glatting Copyright (c) 1999 Software Munitions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 9:39:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 78C2415406; Tue, 11 May 1999 09:38:31 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA25952; Tue, 11 May 1999 12:38:26 -0400 From: Bill Paul Message-Id: <199905111638.MAA25952@skynet.ctr.columbia.edu> Subject: Re: Anybody actually using gigabit ethernet? To: dennis.glatting@software-munitions.com (Dennis Glatting) Date: Tue, 11 May 1999 12:38:23 -0400 (EDT) Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: from "Dennis Glatting" at May 11, 99 09:25:35 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1414 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Dennis Glatting had to walk into mine and say: > In reading your message I felt compelled to ask you a question. Are > you using gb end-to-end? That probably isn't a good idea because in > TCP the sequence numbers can wrap within timeout periods and the data > stream become undetectably (from a TCP perspective) corrupt. You didn't read what I said. I don't have a gigabit ethernet switch. I only have cards. Therefore the *only* way I can test the operation of the driver and adapters is to connect two machines with gigabit cards back to back with a patch cable. This automatically implies 'using gb end-to-end.' As for corruption due to TCP sequence number wrapping, I don't know what to tell you. I never noticed such behavior in my tests, but that's why I'm asking for feedback from other people. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 9:44: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 1EAC9155B1; Tue, 11 May 1999 09:44:22 -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 SAA26851; Tue, 11 May 1999 18:44:05 +0200 (MET DST) Date: Tue, 11 May 1999 18:43:57 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Bill Paul Cc: stable@freebsd.org, FreeBSD current mailing list Subject: Feedback on new drivers (was: Re: Anybody actually using gigabit ethernet?) In-Reply-To: <199905111614.MAA25904@skynet.ctr.columbia.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 There should be a more general mechanism for this. I have the same problem with the USB stuff. 100+ people on the usb-bsd mailing list and only answers to directed questions. What about, like 'HEADS-UP', a 'FEEDBACK: ' message that should invite people to send 'it works' messages. And maybe provide a template of commands to cut and paste. Something like: (echo it works for me uname -a ident dmesg | grep '^' ) | mail -s "" person@address assuming that people are too lazy to type things in themselves. Cheers, Nick On Tue, 11 May 1999, Bill Paul wrote: > I'm wondering if anybody out there has actually done any experimentation > with gigabit ethernet boards using the Alteon Tigon driver. I know that > it works on my hardware, but it's nice to actually have some feedback > from people so that I know if it's actually working worth a damn. So > far I have not heard a peep out of anybody, other than a couple of people > who were nice enough to help out with some driver testing, and that > was months ago. > > I usually consider this a good thing, because it means that at least > nobody is complaining. But when people ask me "hey Bill, how well do > these boards work with FreeBSD?" all I can tell them is that they seem > to work okay in my limited test environment. This does not exactly > provide a lot of motivation to go out and buy some gigabit ethernet > cards. > > Also, I only have access to a limited selection of cards (I have a 3Com > and a Netgear board, and others have tested AceNIC boards) so I don't > know for sure if some of the ones that I claim to support actually > work. (I don't have any reason to believe they won't, but Murphy's > Law applies.) I also don't have access to a gigabit switch, so my > testing is limited to blasting traffic between two hosts through a > fiber patch. > > So, if anybody is actually using a Tigon-based gigabit board with > STABLE or CURRENT, let me know. Is it working reliably? Is performance > good? Is it bad? Inquiring minds want to know. > > -Bill > > -- > ============================================================================= > -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu > Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research > Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City > ============================================================================= > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" > ============================================================================= > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 9:47:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from narcissus.net (narcissus.net [209.73.230.146]) by hub.freebsd.org (Postfix) with ESMTP id 6E7BE158B7; Tue, 11 May 1999 09:47:50 -0700 (PDT) (envelope-from ben@narcissus.net) Received: by narcissus.net (Postfix, from userid 1000) id D00FE1A0; Tue, 11 May 1999 12:38:58 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by narcissus.net (Postfix) with SMTP id C11F813F; Tue, 11 May 1999 12:38:58 -0400 (EDT) Date: Tue, 11 May 1999 12:38:58 -0400 (EDT) From: Snob Art Genre Reply-To: Snob Art Genre To: Dennis Glatting Cc: Bill Paul , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Anybody actually using gigabit ethernet? 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 Tue, 11 May 1999, Dennis Glatting wrote: > In reading your message I felt compelled to ask you a question. Are > you using gb end-to-end? That probably isn't a good idea because in > TCP the sequence numbers can wrap within timeout periods and the data > stream become undetectably (from a TCP perspective) corrupt. Isn't that adequately covered by the PAWS extension from RFC 1323? Ben @narcissus.net -- finally To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 9:51:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 031C915B7F for ; Tue, 11 May 1999 09:51:39 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 8449 invoked by uid 1001); 11 May 1999 16:51:37 +0000 (GMT) To: wpaul@skynet.ctr.columbia.edu Cc: dennis.glatting@software-munitions.com, current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Anybody actually using gigabit ethernet? From: sthaug@nethelp.no In-Reply-To: Your message of "Tue, 11 May 1999 12:38:23 -0400 (EDT)" References: <199905111638.MAA25952@skynet.ctr.columbia.edu> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 11 May 1999 18:51:37 +0200 Message-ID: <8447.926441497@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You didn't read what I said. I don't have a gigabit ethernet switch. > I only have cards. Therefore the *only* way I can test the operation > of the driver and adapters is to connect two machines with gigabit > cards back to back with a patch cable. This automatically implies 'using > gb end-to-end.' > > As for corruption due to TCP sequence number wrapping, I don't know > what to tell you. I never noticed such behavior in my tests, but that's > why I'm asking for feedback from other people. The obvious answer to the TCP sequence number problem is RFC 1323. I assume anybody who wants to use gigabit Ethernet over significant distances *will* use RFC 1323, if they are interested in any performance at all. Otherwise the 64 kbyte window will kill you. As for me, I have tested the driver with Netgear cards. Works great here, I got 470 Mbps (effective application to application) with ttcp, running back to back on a PII-350 and a Celeron 300A (overclocked to 337, thus PCI bus clocked at 37.5 Mhz). The limit in my case is clearly the CPU. However I did *not* see any better performance when I turned on jumbo frames. Next I'll put one card in an old PPro-200 and see what I can get from that. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 10:11:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id D8A8C14DA6; Tue, 11 May 1999 10:11:46 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 74BC81F72; Wed, 12 May 1999 01:11:43 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Snob Art Genre Cc: Dennis Glatting , Bill Paul , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Anybody actually using gigabit ethernet? In-reply-to: Your message of "Tue, 11 May 1999 12:38:58 -0400." Date: Wed, 12 May 1999 01:11:43 +0800 From: Peter Wemm Message-Id: <19990511171145.74BC81F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Snob Art Genre wrote: > On Tue, 11 May 1999, Dennis Glatting wrote: > > > In reading your message I felt compelled to ask you a question. Are > > you using gb end-to-end? That probably isn't a good idea because in > > TCP the sequence numbers can wrap within timeout periods and the data > > stream become undetectably (from a TCP perspective) corrupt. > > Isn't that adequately covered by the PAWS extension from RFC 1323? Well, maybe it would, but.... [1:09am]~src/etc-111# grep tcp_ext defaults/rc.conf tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). It's off by default. :-( Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 10:13:34 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 D1D8115D63 for ; Tue, 11 May 1999 10:12:46 -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 NAA25750; Tue, 11 May 1999 13:12:35 -0400 (EDT) (envelope-from wollman) Date: Tue, 11 May 1999 13:12:35 -0400 (EDT) From: Garrett Wollman Message-Id: <199905111712.NAA25750@khavrinen.lcs.mit.edu> To: sthaug@nethelp.no Cc: wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG Subject: Re: Anybody actually using gigabit ethernet? In-Reply-To: <8447.926441497@verdi.nethelp.no> References: <199905111638.MAA25952@skynet.ctr.columbia.edu> <8447.926441497@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < As for me, I have tested the driver with Netgear cards. Works great here, > I got 470 Mbps (effective application to application) with ttcp, running > back to back on a PII-350 and a Celeron 300A (overclocked to 337, thus PCI > bus clocked at 37.5 Mhz). The limit in my case is clearly the CPU. However > I did *not* see any better performance when I turned on jumbo > frames. I'm buying one of these cards today ($319.99 from NECX) and will stick it into a machine here on our new Gigabit backbone. I'm particularly interested to test out the VLAN support, since my Secret Plan is to have this one machine serve as the DHCP server for the whole Lab (17 subnets). -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 Tue May 11 10:41:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from narcissus.net (narcissus.net [209.73.230.146]) by hub.freebsd.org (Postfix) with ESMTP id 9551214D87; Tue, 11 May 1999 10:41:21 -0700 (PDT) (envelope-from ben@narcissus.net) Received: by narcissus.net (Postfix, from userid 1000) id C78A4190; Tue, 11 May 1999 13:32:31 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by narcissus.net (Postfix) with SMTP id B9AAE18E; Tue, 11 May 1999 13:32:31 -0400 (EDT) Date: Tue, 11 May 1999 13:32:31 -0400 (EDT) From: Snob Art Genre To: Peter Wemm Cc: Dennis Glatting , Bill Paul , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Anybody actually using gigabit ethernet? In-Reply-To: <19990511171145.74BC81F72@spinner.netplex.com.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 Wed, 12 May 1999, Peter Wemm wrote: > > Isn't that adequately covered by the PAWS extension from RFC 1323? > > Well, maybe it would, but.... > > [1:09am]~src/etc-111# grep tcp_ext defaults/rc.conf > tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). > > It's off by default. :-( IMO that's a good thing, because for some reason, the RFC 1323 extensions break a lot of older terminal servers. Ben @narcissus.net -- finally To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 10:45:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 76A5B14D87 for ; Tue, 11 May 1999 10:45:55 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Tue, 11 May 1999 10:45:54 -0700 From: "David Schwartz" To: "Snob Art Genre" , "Peter Wemm" Cc: "Dennis Glatting" , "Bill Paul" , Subject: RE: Anybody actually using gigabit ethernet? Date: Tue, 11 May 1999 10:45:53 -0700 Message-ID: <000101be9bd6$1de3fd60$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > IMO that's a good thing, because for some reason, the RFC 1323 > extensions break a lot of older terminal servers. One could argue that it's more accurate to state that the terminal servers break RFC1323, but alas the effect is the same. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 11:14:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id D2D3915003; Tue, 11 May 1999 11:14:24 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.2/8.8.8) id TAA77827; Tue, 11 May 1999 19:13:48 +0100 (BST) (envelope-from joe) Date: Tue, 11 May 1999 19:13:47 +0100 From: Josef Karthauser To: Peter Wemm Cc: Snob Art Genre , Dennis Glatting , Bill Paul , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Anybody actually using gigabit ethernet? Message-ID: <19990511191347.C33364@pavilion.net> References: <19990511171145.74BC81F72@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990511171145.74BC81F72@spinner.netplex.com.au>; from Peter Wemm on Wed, May 12, 1999 at 01:11:43AM +0800 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 12, 1999 at 01:11:43AM +0800, Peter Wemm wrote: > Snob Art Genre wrote: > > On Tue, 11 May 1999, Dennis Glatting wrote: > > > > > In reading your message I felt compelled to ask you a question. Are > > > you using gb end-to-end? That probably isn't a good idea because in > > > TCP the sequence numbers can wrap within timeout periods and the data > > > stream become undetectably (from a TCP perspective) corrupt. > > > > Isn't that adequately covered by the PAWS extension from RFC 1323? > > Well, maybe it would, but.... > > [1:09am]~src/etc-111# grep tcp_ext defaults/rc.conf > tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). No.. it's _on_ by default. (YES to disallow.) Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 11:18:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from nsx.cybersites.com (unknown [207.92.123.4]) by hub.freebsd.org (Postfix) with ESMTP id 0A6D015003; Tue, 11 May 1999 11:18:35 -0700 (PDT) (envelope-from cyouse@cybersites.com) Received: from localhost (cyouse@localhost) by nsx.cybersites.com (8.9.2/8.9.2) with ESMTP id OAA13535; Tue, 11 May 1999 14:13:41 -0400 (EDT) (envelope-from cyouse@cybersites.com) X-Authentication-Warning: nsx.cybersites.com: cyouse owned process doing -bs Date: Tue, 11 May 1999 14:13:41 -0400 (EDT) From: Chuck Youse To: Josef Karthauser Cc: Peter Wemm , Snob Art Genre , Dennis Glatting , Bill Paul , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Anybody actually using gigabit ethernet? In-Reply-To: <19990511191347.C33364@pavilion.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 Where did you learn to read? Chuck Youse Director of Systems cyouse@cybersites.com On Tue, 11 May 1999, Josef Karthauser wrote: > On Wed, May 12, 1999 at 01:11:43AM +0800, Peter Wemm wrote: > > tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). > > No.. it's _on_ by default. (YES to disallow.) > > Joe > -- > Josef Karthauser FreeBSD: How many times have you booted today? > Technical Manager Viagra for your server (http://www.uk.freebsd.org) > Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 11:23:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 9F289159F9; Tue, 11 May 1999 11:23:21 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA20434; Tue, 11 May 1999 20:23:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA01371; Tue, 11 May 1999 20:23:15 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Chuck Youse Cc: Josef Karthauser , Peter Wemm , Snob Art Genre , Dennis Glatting , Bill Paul , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Anybody actually using gigabit ethernet? In-reply-to: Your message of "Tue, 11 May 1999 14:13:41 EDT." Date: Tue, 11 May 1999 20:23:15 +0200 Message-ID: <1369.926446995@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Isn't it more appropriate to ask where he didn't learn to read ? :-) Poul-Henning In message , Chuc k Youse writes: > >Where did you learn to read? > >Chuck Youse >Director of Systems >cyouse@cybersites.com > > >On Tue, 11 May 1999, Josef Karthauser wrote: > >> On Wed, May 12, 1999 at 01:11:43AM +0800, Peter Wemm wrote: > >> > tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). >> >> No.. it's _on_ by default. (YES to disallow.) >> >> Joe >> -- >> Josef Karthauser FreeBSD: How many times have you booted today? >> Technical Manager Viagra for your server (http://www.uk.freebsd.org) >> Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-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 Tue May 11 11:41:39 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 7200B15145; Tue, 11 May 1999 11:41:34 -0700 (PDT) (envelope-from spud@i.am) Received: from Tomer.DrugsAreGood.org (RAS6-p3.hfa.netvision.net.il [62.0.147.131]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id VAA28959; Tue, 11 May 1999 21:41:26 +0300 (IDT) From: Tomer Weller To: freebsd-hardware@FreeBSD.Org, FreeBSD Current Subject: Scanners Date: Tue, 11 May 1999 21:24:35 +0300 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99051121261500.00272@Tomer.DrugsAreGood.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i got a new UMAX Atrsa 1220P scanner, i have no idea how to configure this in FreeBSD or Linux (or if i even can), im on 4.0-CURRENT. ====================================== 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 Tue May 11 11:44:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id CAECD150F0 for ; Tue, 11 May 1999 11:44:21 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id B0CA718D0; Tue, 11 May 1999 20:44:26 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id ADC7A49C3; Tue, 11 May 1999 20:44:26 +0200 (CEST) Date: Tue, 11 May 1999 20:44:26 +0200 (CEST) From: Andrzej Bialecki To: Peter Wemm Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current In-Reply-To: <19990507213959.BFB0E1F72@spinner.netplex.com.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 Sat, 8 May 1999, Peter Wemm wrote: > It's interesting that the ANSI emulation in loader(8) is good enough to do > full-screen displays. It still seems to make sense to move userconfig-like > functionality into the pre-kernel stages including moving config(8)'s hints > to a loaded and parsed file. Forth, bah.. :-] Heh... To tell you the truth, that was my initial dream which prompted me to start writing it. It could be done now, really... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 12:10:42 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 610BE14BEE; Tue, 11 May 1999 12:10:14 -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 UAA01458; Tue, 11 May 1999 20:10:04 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 11 May 1999 20:10:04 +0100 (BST) From: Doug Rabson To: Wilko Bulte Cc: khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: de driver problem In-Reply-To: <199905102155.XAA01002@yedi.iaf.nl> 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, 10 May 1999, Wilko Bulte wrote: > > > > Yeah. That must be why my 164lx won't netboot. > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit > only) worked just dandy. That reminds me. Does your Alpine still work after the new-bus stuff? I wasn't sure I hadn't broken it when I changed the apecs driver. -- 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 Tue May 11 12:44:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id B17B214FF9 for ; Tue, 11 May 1999 12:44:47 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id VAA02675 for ; Tue, 11 May 1999 21:39:42 +0200 (CEST) Message-Id: <199905111939.VAA02675@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@freebsd.org Subject: the new config and booting From: Gary Jennejohn Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 May 1999 21:39:42 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I switched to the new config(8) today, where the ``config kernel root on..'' line is no longer tolerated in the config file. I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't necessary before. I know I can probably put something into /boot/ to automate this. Just thought I'd report my (negative) experience. -------- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 12:57: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id B87CE15DD6 for ; Tue, 11 May 1999 12:56:22 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id VAA20823; Tue, 11 May 1999 21:56:20 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id VAA01725; Tue, 11 May 1999 21:56:19 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Gary Jennejohn Cc: freebsd-current@FreeBSD.ORG Subject: Re: the new config and booting In-reply-to: Your message of "Tue, 11 May 1999 21:39:42 +0200." <199905111939.VAA02675@peedub.muc.de> Date: Tue, 11 May 1999 21:56:19 +0200 Message-ID: <1723.926452579@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905111939.VAA02675@peedub.muc.de>, Gary Jennejohn writes: >I switched to the new config(8) today, where the ``config kernel root on..'' >line is no longer tolerated in the config file. > >I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't >necessary before. > >I know I can probably put something into /boot/ to automate this. >Just thought I'd report my (negative) experience. What's your config ? It sounds like the boot code isn't telling the kernel the right thing... I belive it picks the bootmajor from the type field in the disklabel. (right Mike ?) So do you have a IDE/ATA disk labeled as SCSI by any chance ? -- 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 Tue May 11 14:32:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 5EC2F14BF6; Tue, 11 May 1999 14:32:32 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id A9D7A1F72; Wed, 12 May 1999 05:32:28 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: NAKAGAWA Yoshihisa , Nick Hibma , current@freebsd.org Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Tue, 11 May 1999 08:21:37 +0100." Date: Wed, 12 May 1999 05:32:28 +0800 From: Peter Wemm Message-Id: <19990511213230.A9D7A1F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > On Tue, 11 May 1999, NAKAGAWA Yoshihisa wrote: > > > > I was thinking of doing this, the same as alpm and intpm: > > > > > > case 0x: > > > #if NUHCI > 0 > > > return NULL; > > > #else > > > return "VIA blah USB controller"; > > > #endif > > > > It depends on old-config, so poor mechanism. newconfig already > > implimented best match probe/attach. > > And a very useful mechanism it is. Which is why I implemented priority > ordered probes in -current. For the sake of the thread, this got committed a day or two ago, and these hacks have been replaced with a low priority match. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 14:34:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 0BB3E14C91 for ; Tue, 11 May 1999 14:34:07 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA15553 for freebsd-current@FreeBSD.ORG; Tue, 11 May 1999 23:34:04 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 6EA3D8837; Tue, 11 May 1999 19:37:58 +0200 (CEST) (envelope-from roberto) Date: Tue, 11 May 1999 19:37:58 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Tonight make world failed at isdnmonitor... Message-ID: <19990511193758.A18951@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: ; from Hellmuth Michaelis on Tue, May 11, 1999 at 10:33:10AM +0200 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5307 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Hellmuth Michaelis: > hellmuth BTW do you plan to import i4b 0.80 into CURRENT ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #71: Sun May 9 20:16:32 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 15: 9:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id AACAA15250 for ; Tue, 11 May 1999 15:09:40 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id RAA18123 for current@freebsd.org; Tue, 11 May 1999 17:09:38 -0500 (CDT) From: Kevin Day Message-Id: <199905112209.RAA18123@home.dragondata.com> Subject: Incorrect memory sizes reported To: current@freebsd.org Date: Tue, 11 May 1999 17:09:36 -0500 (CDT) 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 I'm not sure if this is related to the bug I found in 3.1, regarding mmaping devices, then forking, but with my -current NFS server: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 139 root 2 0 257M 452K select 0:00 0.00% 0.00% rpc.statd 257M? :) ps shows similar info... Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 15:13: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 3300B15500 for ; Tue, 11 May 1999 15:13:04 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Tue, 11 May 1999 15:13:02 -0700 From: "David Schwartz" To: "Kevin Day" , Subject: RE: Incorrect memory sizes reported Date: Tue, 11 May 1999 15:13:02 -0700 Message-ID: <000101be9bfb$6fd43f70$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <199905112209.RAA18123@home.dragondata.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is normal. It's using a lot of virtual memory. Fortunately, virtual memory is cheap. DS > I'm not sure if this is related to the bug I found in 3.1, > regarding mmaping > devices, then forking, but with my -current NFS server: > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 139 root 2 0 257M 452K select 0:00 0.00% 0.00% rpc.statd > > 257M? :) ps shows similar info... > > > Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 15:18:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 5DF66159F8 for ; Tue, 11 May 1999 15:18:28 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id RAA18856; Tue, 11 May 1999 17:18:13 -0500 (CDT) From: Kevin Day Message-Id: <199905112218.RAA18856@home.dragondata.com> Subject: Re: Incorrect memory sizes reported In-Reply-To: <000101be9bfb$6fd43f70$021d85d1@whenever.youwant.to> from David Schwartz at "May 11, 1999 3:13: 2 pm" To: davids@webmaster.com (David Schwartz) Date: Tue, 11 May 1999 17:18:12 -0500 (CDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This is normal. It's using a lot of virtual memory. Fortunately, virtual > memory is cheap. > > DS > > > I'm not sure if this is related to the bug I found in 3.1, > > regarding mmaping > > devices, then forking, but with my -current NFS server: > > > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > > 139 root 2 0 257M 452K select 0:00 0.00% 0.00% rpc.statd > > > > 257M? :) ps shows similar info... > > > > > > Kevin > > Ok, I stand corrected then.... I hadn't seen this before... 2.2.8: root 14127 0.0 0.1 176 492 ?? Ss 5:14PM 0:00.00 rpc.statd 3.1: root 853 0.0 0.7 172 416 ?? Ss 7:18AM 0:00.00 rpc.statd There still is the issue I described a while back that would make children show negative numbers in 'size' though, that i can confirm isn't sucking that much VM. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 15:20:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (Postfix) with ESMTP id 0CBD115903 for ; Tue, 11 May 1999 15:20:20 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with SMTP id PAA04682; Tue, 11 May 1999 15:20:15 -0700 Message-ID: <008901be9bfc$bdd50230$0d787880@apex.tapang> From: "Carlos C. Tapang" To: "Jordan K. Hubbard" Cc: Subject: Re: FBSDBOOT.EXE Date: Tue, 11 May 1999 15:22:22 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF. If anybody else needs it, please let me know and I'll see what I can do for you. ps. I had to use my old Microsoft Visual C++ (ver 1.5) to do this modification. Carlos C. Tapang http://www.genericwindows.com -----Original Message----- From: Jordan K. Hubbard To: Carlos C. Tapang Cc: freebsd-current@FreeBSD.ORG Date: Saturday, May 01, 1999 5:54 PM Subject: Re: FBSDBOOT.EXE >> Is there anybody out there working on upgrading fbsdboot.exe so that it can >> recognize ELF? > >I believe that fbsdboot.exe has, instead, simply been retired. Sorry >I don't have better news than this. > >- Jordan > > >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 May 11 15:26:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id DC9F015903 for ; Tue, 11 May 1999 15:26:05 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 172D71F73 for ; Wed, 12 May 1999 06:26:02 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: problem with dev_t changes and pageout.. Date: Wed, 12 May 1999 06:26:02 +0800 From: Peter Wemm Message-Id: <19990511222604.172D71F73@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like something has come unstuck: Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 fault virtual address = 0x28 fault code = supervisor read, page not present instruction pointer = 0x8:0xc017bb67 stack pointer = 0x10:0xc5d97de4 frame pointer = 0x10:0xc5d97df0 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 = 2 (pagedaemon) interrupt mask = net bio cam <- SMP: XXX kernel: type 12 trap, code=0 Stopped at spec_strategy+0x93: movl 0x28(%edx),%eax ^^^^^^^^^^^ %edx = null db> trace spec_strategy(c5d97e1c) at spec_strategy+0x93 swap_pager_putpages(c02904fc,c5d97ecc,2,0,c5d97e60) at swap_pager_putpages+0x3e1 default_pager_putpages(c02904fc,c5d97ecc,2,0,c5d97e60) at default_pager_putpages+0x17 vm_pageout_flush(c5d97ecc,2,0,c5d97eb0,c02182cf) at vm_pageout_flush+0x91 vm_pageout_clean(c04d6b60,80000000,c013e290,2000,c5d97f78) at vm_pageout_clean+0x1f1 vm_pageout_scan(80000000,c02789c0,c02789c0,c5d97fac,c013e2c3) at vm_pageout_scan+0x45e vm_pageout(c5d8fdf7,c0255500,c02789c0,c020c640,c020c748) at vm_pageout+0x221 kproc_start(c02789c0) at kproc_start+0x33 fork_trampoline(10b8a0,d88e0000,18b8c08e,8e000000,24448be0) at fork_trampoline+0x30 db> ps pid proc addr uid ppid pgrp flag stat wmesg wchan cmd 438 c680da40 c6818000 495 282 277 000004 3 biord c332d9c0 p4d 437 c5d8c340 c6802000 433 417 415 004084 3 piperd c6760660 tee 436 c680dd00 c6810000 433 417 415 004004 3 biord c33626f8 p4 418 c680dba0 c6815000 433 415 415 004084 3 piperd c6760700 mail 417 c680de60 c680e000 433 415 415 004084 3 wait c680de60 sh [..] The offending line in spec_strategy is: (*bdevsw(bp->b_dev)->d_strategy)(bp); d_strategy was null.. I'm still looking. (I think this is the first time the box paged out since booting a few hours ago, it's got 128M, but p4d has got a lot of stuff to deal with and can hit a vsize of 70MB or so.) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 16: 4:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 274B7151F7 for ; Tue, 11 May 1999 16:04:28 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id WAA18582; Tue, 11 May 1999 22:56:33 +0200 From: Luigi Rizzo Message-Id: <199905112056.WAA18582@labinfo.iet.unipi.it> Subject: Nt source licenses... To: current@freebsd.org Date: Tue, 11 May 1999 22:56:33 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1402 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, maybe i am the last one in the world to know, but were you guys aware of this: http://research.microsoft.com/programs/NTSrcLicInfo.htm Microsoft makes Windows NT source code available to universities and other "not-for-profit" research institutions at no charge. Currently, there are over 55 universities and government agencies with source licenses. ... I still have to check the exact conditions though. The above web page says this: Features of the license * No cost * Intellectual property created with the use of NT source code is owned by the researcher. * Source licensees can share source or other source-based work with other NT Source licensees. * Source is licensed to the requesting organization, not individuals to insure broad internal access. * No employment restrictions as the result of viewing or using the source. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) http://www.iet.unipi.it/~luigi/ngc99/ ==== First International Workshop on Networked Group Communication ==== -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 16:35:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id AFC68159BD; Tue, 11 May 1999 16:35:51 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id BAA24181; Wed, 12 May 1999 01:29:30 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id BAA04028; Wed, 12 May 1999 01:01:07 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905112301.BAA04028@yedi.iaf.nl> Subject: Re: de driver problem In-Reply-To: from Doug Rabson at "May 11, 1999 8:10: 4 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 12 May 1999 01:01:07 +0200 (CEST) Cc: khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Doug Rabson wrote ... > On Mon, 10 May 1999, Wilko Bulte wrote: > > > > > > > Yeah. That must be why my 164lx won't netboot. > > > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit > > only) worked just dandy. > > That reminds me. Does your Alpine still work after the new-bus stuff? I > wasn't sure I hadn't broken it when I changed the apecs driver. My Alpine is on a not so current -current, but it is rebuilding world now. Stay tuned, I can probably tell you more tomorrow. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 18:12: 2 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 7F78A14CA2 for ; Tue, 11 May 1999 18:12:01 -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 SAA02741; Tue, 11 May 1999 18:09:51 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905120109.SAA02741@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Gary Jennejohn Cc: freebsd-current@freebsd.org Subject: Re: the new config and booting In-reply-to: Your message of "Tue, 11 May 1999 21:39:42 +0200." <199905111939.VAA02675@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 May 1999 18:09:51 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I switched to the new config(8) today, where the ``config kernel root on..'' > line is no longer tolerated in the config file. > > I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't > necessary before. > > I know I can probably put something into /boot/ to automate this. > Just thought I'd report my (negative) experience. Can you tell us what it's trying to mount vs. what it should be mounting? I'm in the process of rewriting parts of this code again to fix the mess that's been made of it. I'm not sure I'll get all the way, but in conjunction with some small changes in the loader it *should* make problems like yours history. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 18:45:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from gidgate.gid.co.uk (gidgate.gid.co.uk [193.123.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E5A8150E7 for ; Tue, 11 May 1999 18:45:13 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.8.8/8.8.7) id CAA24250; Wed, 12 May 1999 02:44:24 +0100 (BST) (envelope-from rb) Message-Id: <3.0.6.32.19990512024422.0081e210@192.168.255.1> X-Sender: rbmail@192.168.255.1 X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 12 May 1999 02:44:22 +0100 To: "Carlos C. Tapang" From: Bob Bishop Subject: Re: FBSDBOOT.EXE Cc: current@freebsd.org In-Reply-To: <008901be9bfc$bdd50230$0d787880@apex.tapang> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 15:22 11/05/99 -0700, you wrote: >Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF. >If anybody else needs it, please let me know and I'll see what I can do for >you. I'm going to have a use for it RSN >ps. I had to use my old Microsoft Visual C++ (ver 1.5) to do this >modification. Ick. I was hoping for a 32bit build at least, although I suppose it doesn't matter much. Will you be posting diffs? -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 19: 4:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 3AD52151F7; Tue, 11 May 1999 19:04:40 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id CAA09868; Wed, 12 May 1999 02:04:13 GMT Message-Id: <199905120204.CAA09868@chandra.eatell.msr.prug.or.jp> To: Peter Wemm Cc: Doug Rabson , Nick Hibma , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Wed, 12 May 1999 05:32:28 +0800." <19990511213230.A9D7A1F72@spinner.netplex.com.au> Date: Wed, 12 May 1999 11:04:12 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For the sake of the thread, this got committed a day or two ago, and these > hacks have been replaced with a low priority match. Why do you use another mechanism of 4.4BSD ? Don't loss time and loss inter-operability between other BSDs. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 May 11 19:20:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (Postfix) with ESMTP id F332314E04 for ; Tue, 11 May 1999 19:20:13 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id TAA29616; Tue, 11 May 1999 19:19:38 -0700 (PDT) Message-ID: <3738E510.BFC40FC0@seattleu.edu> Date: Tue, 11 May 1999 19:18:56 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: tosha after CAM changes References: <199905102245.QAA78933@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I must have missed a step making world, so everything works just fine now. Thanks for the concern. -- Eric Hodel hodeleri@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 20:52: 8 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 9BFC61585B for ; Tue, 11 May 1999 20:52:05 -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 XAA18494; Tue, 11 May 1999 23:52:02 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA17831; Tue, 11 May 1999 23:51:32 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id XAA24516; Tue, 11 May 1999 23:51:32 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905120351.XAA24516@bb01f39.unx.sas.com> Subject: /usr/src/release/Makefile patch To: jkh@zippy.cdrom.com Date: Tue, 11 May 1999 23:51:32 -0400 (EDT) Cc: freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Could you please consider the following patch to /usr/src/release/Makefile? It may not be entirely correct, but it allows a 'cd /usr/src/release && make release' to run to completion. In the kernel makefile, 'kernel' is not a target, ${KERNEL} is, and ${KERNEL} has the value 'GENERIC'. Comments welcome! Thanks! John # $Id: Makefile,v 1.482 1999/05/09 17:00:04 obrien Exp $ --- /snap/release/usr/src/release/Makefile~ Tue May 11 23:50:52 1999 +++ /snap/release/usr/src/release/Makefile Tue May 11 23:43:49 1999 @@ -634,9 +634,9 @@ @rm -f ${RD}/kernels/${KERNEL} @cd ${.CURDIR}/../sys/${MACHINE_ARCH}/conf && config ${KERNEL} @cd ${.CURDIR}/../sys/compile/${KERNEL} && \ - make depend && \ - make kernel && \ - cp kernel ${RD}/kernels/${KERNEL} + make depend && pwd && \ + make ${KERNEL} && \ + cp ${KERNEL} ${RD}/kernels/${KERNEL} # # --==## Put a filesystem into a BOOTMFS kernel ##==-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 20:54:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 8182914BCF for ; Tue, 11 May 1999 20:54:20 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id DAA09999; Wed, 12 May 1999 03:27:45 GMT Message-Id: <199905120327.DAA09999@chandra.eatell.msr.prug.or.jp> To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Tue, 11 May 1999 22:55:50 -0400." <199905120255.WAA28347@khavrinen.lcs.mit.edu> Date: Wed, 12 May 1999 12:27:45 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Because 4.4BSD got it wrong. It has always been the belief of the > FreeBSD Project's management that 4.4's totally-static configuration No! 4.4BSD mechanism is good. Newconfig already support dynamic configuration and *good* module support (not yet merge newconfig CVS). > mechanism was unacceptable -- else we would have used it years ago. It is not formal core decision. > Our policy in all areas has been that we'd rather do the Right Thing > than follow the crowd. new-bus is wrong way. You are misunderstanding 4.4BSD mechanism. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 May 11 22:40:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx.nsu.ru (mx.nsu.ru [193.124.215.71]) by hub.freebsd.org (Postfix) with ESMTP id 5261814F20 for ; Tue, 11 May 1999 22:38:48 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from iclub.nsu.ru (fjoe@iclub.nsu.ru [193.124.222.66]) by mx.nsu.ru (8.9.1/8.9.0) with ESMTP id MAA14146; Wed, 12 May 1999 12:35:51 +0700 (NOVST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.8.5) with ESMTP id MAA15772; Wed, 12 May 1999 12:35:38 +0700 (NSS) Date: Wed, 12 May 1999 12:35:38 +0700 (NSS) From: Max Khon To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: Incorrect memory sizes reported In-Reply-To: <199905112209.RAA18123@home.dragondata.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 hi, there! On Tue, 11 May 1999, Kevin Day wrote: > I'm not sure if this is related to the bug I found in 3.1, regarding mmaping > devices, then forking, but with my -current NFS server: > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 139 root 2 0 257M 452K select 0:00 0.00% 0.00% rpc.statd > > 257M? :) ps shows similar info... got the same on -stable machine (built 28 Apr) about a week ago /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 11 22:40:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx.nsu.ru (mx.nsu.ru [193.124.215.71]) by hub.freebsd.org (Postfix) with ESMTP id 7A71115BF4 for ; Tue, 11 May 1999 22:40:42 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from iclub.nsu.ru (fjoe@iclub.nsu.ru [193.124.222.66]) by mx.nsu.ru (8.9.1/8.9.0) with ESMTP id MAA15131; Wed, 12 May 1999 12:39:19 +0700 (NOVST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.8.5) with ESMTP id MAA15863; Wed, 12 May 1999 12:38:53 +0700 (NSS) Date: Wed, 12 May 1999 12:38:53 +0700 (NSS) From: Max Khon To: "Carlos C. Tapang" Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE In-Reply-To: <008901be9bfc$bdd50230$0d787880@apex.tapang> 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, there! On Tue, 11 May 1999, Carlos C. Tapang wrote: > Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF. > If anybody else needs it, please let me know and I'll see what I can do for > you. > ps. I had to use my old Microsoft Visual C++ (ver 1.5) to do this > modification. where can I get the diffs or binaries? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 0:12:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from callisto.geotec.net (callisto.geotec.net [208.244.246.5]) by hub.freebsd.org (Postfix) with ESMTP id B9C6515B8A for ; Wed, 12 May 1999 00:12:39 -0700 (PDT) (envelope-from chebon@geotec.net) Received: from geotec.net (apogee.geotec.net [208.244.246.24]) by callisto.geotec.net (Post.Office MTA v3.5.3 release 223 ID# 0-60637U8000L800S0V35) with ESMTP id net for ; Wed, 12 May 1999 02:24:45 -0500 Message-ID: <37392A89.9FC6A1FD@geotec.net> Date: Wed, 12 May 1999 02:15:22 -0500 From: chebon X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.ORG Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe me please =) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 0:13: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcsext.hcs.de (hcsext.hcs.de [194.123.40.2]) by hub.freebsd.org (Postfix) with SMTP id 136DF15313 for ; Wed, 12 May 1999 00:12:59 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1322 bytes) by hcsext.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Wed, 12 May 1999 09:12:58 +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 m10hTCL-0000fMC; Wed, 12 May 99 09:12 METDST Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: Tonight make world failed at isdnmonitor... In-Reply-To: <19990511193758.A18951@keltia.freenix.fr> from Ollivier Robert at "May 11, 99 07:37:58 pm" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Wed, 12 May 1999 09:12:57 +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: 445 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the keyboard of Ollivier Robert: > BTW do you plan to import i4b 0.80 into CURRENT ? Yes, when it has settled a bit. 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 Wed May 12 0:13: 7 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 1538C15DF5 for ; Wed, 12 May 1999 00:13:03 -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 IAA18815 for ; Wed, 12 May 1999 08:13:11 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 12 May 1999 08:13:11 +0100 (BST) From: Doug Rabson To: current@freebsd.org Subject: Debugging uthreads 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 put an initial version of my hack for debugging FreeBSD user threads with gdb up on http://www.freebsd.org/~dfr/uthread.diff. Comments would be appreciated. -- 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 Wed May 12 0:19:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (Postfix) with ESMTP id CD26215267 for ; Wed, 12 May 1999 00:19:07 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by mail4.aracnet.com (8.9.1/8.9.0) with SMTP id AAA21075; Wed, 12 May 1999 00:18:36 -0700 Message-ID: <003101be9c47$f2007580$0d787880@apex.tapang> From: "Carlos C. Tapang" To: "Max Khon" Cc: "Jordan K. Hubbard" , Subject: Re: FBSDBOOT.EXE Date: Wed, 12 May 1999 00:20:42 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The binary is now available by anonymous ftp at ftp.genericwindows.com in the pub directory. If you have problems, please email me directly. Carlos C. Tapang http://www.genericwindows.com -----Original Message----- From: Max Khon To: Carlos C. Tapang Cc: Jordan K. Hubbard ; freebsd-current@FreeBSD.ORG Date: Tuesday, May 11, 1999 10:45 PM Subject: Re: FBSDBOOT.EXE >hi, there! > >On Tue, 11 May 1999, Carlos C. Tapang wrote: > >> Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF. >> If anybody else needs it, please let me know and I'll see what I can do for >> you. >> ps. I had to use my old Microsoft Visual C++ (ver 1.5) to do this >> modification. > >where can I get the diffs or binaries? > >/fjoe > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 0:41:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 106E9152C4; Wed, 12 May 1999 00:41:33 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id JAA08878; Wed, 12 May 1999 09:26:46 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id JAA09042; Wed, 12 May 1999 09:33:06 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905120733.JAA09042@yedi.iaf.nl> Subject: Re: de driver problem In-Reply-To: <199905112301.BAA04028@yedi.iaf.nl> from Wilko Bulte at "May 12, 1999 1: 1: 7 am" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Wed, 12 May 1999 09:33:06 +0200 (CEST) Cc: dfr@nlsystems.com, khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Wilko Bulte wrote ... > As Doug Rabson wrote ... > > On Mon, 10 May 1999, Wilko Bulte wrote: > > > > > > > > > > Yeah. That must be why my 164lx won't netboot. > > > > > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit > > > only) worked just dandy. > > > > That reminds me. Does your Alpine still work after the new-bus stuff? I > > wasn't sure I hadn't broken it when I changed the apecs driver. > > My Alpine is on a not so current -current, but it is rebuilding world now. > Stay tuned, I can probably tell you more tomorrow. Bah.. Extracting pod2man (with variable substitutions) cd ext/B; miniperl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib Makefile.PL LINKTYPE=dynamic INSTALLDIRS=perl PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl LIBS="-lperl" INSTALLMAN3DIR=/usr/obj/usr/src/tmp/usr/share/perl/man3 INST_LIB=/usr/obj/usr/src/gnu/usr.bin/perl/perl/build/B INST_ARCHLIB=/usr/obj/usr/src/gnu/usr.bin/perl/perl/build/B ; make -B config PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl Writing Makefile for DynaLoader ==> Your Makefile has been rebuilt. <== ==> Please rerun the make command. <== false false: not found *** Error code 1 This is -current as of last Sunday. I'll resup tonight to see if it got fixed in the meantime Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 0:42:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id A426D1529B for ; Wed, 12 May 1999 00:42:17 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id RAA25621; Wed, 12 May 1999 17:53:25 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905120753.RAA25621@cimlogic.com.au> Subject: Re: Debugging uthreads In-Reply-To: from Doug Rabson at "May 12, 1999 8:13:11 am" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 12 May 1999 17:53:24 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > I've put an initial version of my hack for debugging FreeBSD user threads > with gdb up on http://www.freebsd.org/~dfr/uthread.diff. Comments would be > appreciated. Is the uniqueid really necessary when the address of the thread structure is already unique within the process address space? After all, that's what the thread ID is (a pointer to the malloc'd memory). I have the feeling that there needs to be some way to discover if the version of gdb being used is compatible with the version of libc_r that the program is linked against. Otherwise we end up with a similar problem to the all too familiar "struct proc size mismatch". -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 1: 4:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 3CC8014D18 for ; Wed, 12 May 1999 01:04:12 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id KAA23726 for ; Wed, 12 May 1999 10:04:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id KAA03696 for ; Wed, 12 May 1999 10:04:09 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: simple (but important) task for junior kernel hacker From: Poul-Henning Kamp Date: Wed, 12 May 1999 10:04:09 +0200 Message-ID: <3694.926496249@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't have time just now to attend this particular detail, which manifests itself by swapinfo/pstat -p showing "/dev/(null)" for device name. The problem in short is that libkvm:kvm_getswapinfo.c has it's fingers in the kernels memory and pulls out a dev_t without knowing how to (and it shouldn't be taught this!) convert it to a udev_t. The Right Way to solve this problem is to rewrite libkvm:kvm_getswapinfo.c to pick up the information using some (for this purpose constructed) sysctl variables (sysctlbyname(3) please!), and let the kernel convert the dev_t to udev_t before passing it out to userland. So for any aspiring kernel hackers out there: have at it. Patches accepted. In general libkvm should not grovel around in a running kernel but only use sysctlbyname(3). -- 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 Wed May 12 1: 9:26 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 E2C4B14EEF for ; Wed, 12 May 1999 01:08:57 -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 JAA62503; Wed, 12 May 1999 09:08:45 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 12 May 1999 09:08:45 +0100 (BST) From: Doug Rabson To: John Birrell Cc: current@freebsd.org Subject: Re: Debugging uthreads In-Reply-To: <199905120753.RAA25621@cimlogic.com.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 Wed, 12 May 1999, John Birrell wrote: > Doug Rabson wrote: > > I've put an initial version of my hack for debugging FreeBSD user threads > > with gdb up on http://www.freebsd.org/~dfr/uthread.diff. Comments would be > > appreciated. > > Is the uniqueid really necessary when the address of the thread structure > is already unique within the process address space? After all, that's > what the thread ID is (a pointer to the malloc'd memory). > > I have the feeling that there needs to be some way to discover if the > version of gdb being used is compatible with the version of libc_r that > the program is linked against. Otherwise we end up with a similar > problem to the all too familiar "struct proc size mismatch". I didn't want to use the address since it might cause confusion if a thread was freed and then the memory was re-allocated to create a new thread. I thought about the versioning but I don't think it will be a problem in practice since both uthread and gdb will generally be built by a single 'make world'. -- 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 Wed May 12 1:15:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id C9F1514C12 for ; Wed, 12 May 1999 01:15:44 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id SAA25753; Wed, 12 May 1999 18:27:04 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905120827.SAA25753@cimlogic.com.au> Subject: Re: Debugging uthreads In-Reply-To: from Doug Rabson at "May 12, 1999 9: 8:45 am" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 12 May 1999 18:27:03 +1000 (EST) Cc: jb@cimlogic.com.au, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > I didn't want to use the address since it might cause confusion if a > thread was freed and then the memory was re-allocated to create a new > thread. Good reason. > I thought about the versioning but I don't think it will be a problem in > practice since both uthread and gdb will generally be built by a single > 'make world'. But libc_r isn't linked into anything during a 'make world'. It is only linked to 3rd party applications. So, although libc_r and gdb are in sync at the end of a 'make world', any statically linked applications will be out-of-sync (if an internal change has been made to libc_r). I'm not sure there is an easy solution to this. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 1:25:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id 8E0FB14C12 for ; Wed, 12 May 1999 01:25:27 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id KAA03627; Wed, 12 May 1999 10:23:01 +0200 (CEST) Message-Id: <199905120823.KAA03627@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: freebsd-current@freebsd.org Subject: Re: the new config and booting Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 12 May 1999 03:09:51 +0200." <199905120109.SAA02741@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 1999 10:23:01 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: >> I switched to the new config(8) today, where the ``config kernel root on..'' >> line is no longer tolerated in the config file. >> >> I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't >> necessary before. >> >> I know I can probably put something into /boot/ to automate this. >> Just thought I'd report my (negative) experience. > >Can you tell us what it's trying to mount vs. what it should be >mounting? > >I'm in the process of rewriting parts of this code again to fix the >mess that's been made of it. I'm not sure I'll get all the way, but in >conjunction with some small changes in the loader it *should* make >problems like yours history. > Sorry, all I see is the panic message. As I wrote in another mail, the loader sees the floppy as DISK A and the SCSI disk as DISK B. But then again, it saw that before. Since I'm leaving shortly on a trip and won't be back for 2 weeks I won't be able to pursue this further. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 1:28:12 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 B368215331 for ; Wed, 12 May 1999 01:28: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 JAA90368; Wed, 12 May 1999 09:28:00 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 12 May 1999 09:28:00 +0100 (BST) From: Doug Rabson To: John Birrell Cc: current@freebsd.org Subject: Re: Debugging uthreads In-Reply-To: <199905120827.SAA25753@cimlogic.com.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 Wed, 12 May 1999, John Birrell wrote: > Doug Rabson wrote: > > I didn't want to use the address since it might cause confusion if a > > thread was freed and then the memory was re-allocated to create a new > > thread. > > Good reason. > > > I thought about the versioning but I don't think it will be a problem in > > practice since both uthread and gdb will generally be built by a single > > 'make world'. > > But libc_r isn't linked into anything during a 'make world'. It is only > linked to 3rd party applications. So, although libc_r and gdb are in > sync at the end of a 'make world', any statically linked applications > will be out-of-sync (if an internal change has been made to libc_r). > I'm not sure there is an easy solution to this. Other gdb thread debugging systems tend to export a set of variables from the thread library which describe the important offsets in the thread structure e.g. _debug_pthread_status_offset, _debug_pthread_foo_offset etc. If you think there will be a real problem, I could do this I guess. -- 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 Wed May 12 1:30:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id D472414C12 for ; Wed, 12 May 1999 01:30:51 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id SAA25827; Wed, 12 May 1999 18:42:11 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905120842.SAA25827@cimlogic.com.au> Subject: Re: Debugging uthreads In-Reply-To: from Doug Rabson at "May 12, 1999 9:28: 0 am" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 12 May 1999 18:42:11 +1000 (EST) Cc: jb@cimlogic.com.au, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > Other gdb thread debugging systems tend to export a set of variables from > the thread library which describe the important offsets in the thread > structure e.g. _debug_pthread_status_offset, _debug_pthread_foo_offset > etc. > > If you think there will be a real problem, I could do this I guess. Maybe we should just isolate the things that gdb is allowed to look at and document them as "cast in stone". -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 1:31:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id 5AA5215D22 for ; Wed, 12 May 1999 01:31:02 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id KAA03605; Wed, 12 May 1999 10:17:26 +0200 (CEST) Message-Id: <199905120817.KAA03605@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: freebsd-current@freebsd.org, garyj@peedub.muc.de Subject: Re: the new config and booting Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 11 May 1999 21:56:19 +0200." <1723.926452579@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 1999 10:17:26 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: >In message <199905111939.VAA02675@peedub.muc.de>, Gary Jennejohn writes: >>I switched to the new config(8) today, where the ``config kernel root on..'' >>line is no longer tolerated in the config file. >> >>I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't >>necessary before. >> >>I know I can probably put something into /boot/ to automate this. >>Just thought I'd report my (negative) experience. > >What's your config ? It sounds like the boot code isn't telling the >kernel the right thing... > >I belive it picks the bootmajor from the type field in the >disklabel. (right Mike ?) > >So do you have a IDE/ATA disk labeled as SCSI by any chance ? > no, it's a "dangerously dedicated" SCSI disk. the loader shows the floppy as DISK A and the SCSI disk as DISK B. I have to admit that I still have old boot blocks on the disk, but as I said, it worked OK before. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 1:34:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 6032D152D8; Wed, 12 May 1999 01:34:14 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: by eagle.phc.igs.net (Postfix, from userid 1003) id F3A9B189D; Wed, 12 May 1999 03:33:44 +0000 (GMT) Date: Wed, 12 May 1999 03:33:44 +0000 From: Robert Garrett To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: simple (but important) task for junior kernel hacker Message-ID: <19990512033344.E21016@phc.igs.net> References: <3694.926496249@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <3694.926496249@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 May 1999 at 10:04:09 +0200, Poul-Henning Kamp wrote: > > I don't have time just now to attend this particular detail, which > manifests itself by swapinfo/pstat -p showing "/dev/(null)" for > device name. > > The problem in short is that libkvm:kvm_getswapinfo.c has it's > fingers in the kernels memory and pulls out a dev_t without knowing > how to (and it shouldn't be taught this!) convert it to a udev_t. > > The Right Way to solve this problem is to rewrite libkvm:kvm_getswapinfo.c > to pick up the information using some (for this purpose constructed) > sysctl variables (sysctlbyname(3) please!), and let the kernel convert > the dev_t to udev_t before passing it out to userland. > > So for any aspiring kernel hackers out there: have at it. Patches > accepted. > > In general libkvm should not grovel around in a running kernel but > only use sysctlbyname(3). > > -- the only place in the entire libkvm where a dev_t is used is kvm_proc.c line 230 this particular section completely looses me Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 1:38:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id B5DD3152D8 for ; Wed, 12 May 1999 01:38:46 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id KAA23942; Wed, 12 May 1999 10:38:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id KAA03918; Wed, 12 May 1999 10:38:42 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Robert Garrett Cc: current@FreeBSD.ORG Subject: Re: simple (but important) task for junior kernel hacker In-reply-to: Your message of "Wed, 12 May 1999 03:33:44 -0000." <19990512033344.E21016@phc.igs.net> Date: Wed, 12 May 1999 10:38:41 +0200 Message-ID: <3916.926498321@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990512033344.E21016@phc.igs.net>, Robert Garrett writes: >On Wed, 12 May 1999 at 10:04:09 +0200, Poul-Henning Kamp wrote: >> >> I don't have time just now to attend this particular detail, which >> manifests itself by swapinfo/pstat -p showing "/dev/(null)" for >> device name. >> >> The problem in short is that libkvm:kvm_getswapinfo.c has it's >> fingers in the kernels memory and pulls out a dev_t without knowing >> how to (and it shouldn't be taught this!) convert it to a udev_t. >> >> The Right Way to solve this problem is to rewrite libkvm:kvm_getswapinfo.c >> to pick up the information using some (for this purpose constructed) >> sysctl variables (sysctlbyname(3) please!), and let the kernel convert >> the dev_t to udev_t before passing it out to userland. >> >> So for any aspiring kernel hackers out there: have at it. Patches >> accepted. >> >> In general libkvm should not grovel around in a running kernel but >> only use sysctlbyname(3). >> >> -- >the only place in the entire libkvm where a dev_t is used is >kvm_proc.c line 230 this particular section completely looses me There is a dev_t passed out to pstat -s in a datastructure. -- 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 Wed May 12 1:42:16 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 7474B152D8 for ; Wed, 12 May 1999 01:41:44 -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 2.12 #1) id 10hUa2-00009t-00; Wed, 12 May 1999 10:41:30 +0200 From: Sheldon Hearn To: Gary Jennejohn Cc: freebsd-current@freebsd.org Subject: Re: the new config and booting In-reply-to: Your message of "Tue, 11 May 1999 21:39:42 +0200." <199905111939.VAA02675@peedub.muc.de> Date: Wed, 12 May 1999 10:41:30 +0200 Message-ID: <612.926498490@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 May 1999 21:39:42 +0200, Gary Jennejohn wrote: > I switched to the new config(8) today, where the ``config kernel root on..'' > line is no longer tolerated in the config file. As a workaround, try the following, taken directly from LINT options ROOTDEVNAME=\"da0s2e\" Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 1:46: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 1CABA14C12 for ; Wed, 12 May 1999 01:46:00 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: by eagle.phc.igs.net (Postfix, from userid 1003) id 0017B189D; Wed, 12 May 1999 03:45:29 +0000 (GMT) Date: Wed, 12 May 1999 03:45:29 +0000 From: Robert Garrett To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: simple (but important) task for junior kernel hacker Message-ID: <19990512034529.A5516@phc.igs.net> References: <19990512033344.E21016@phc.igs.net> <3916.926498321@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <3916.926498321@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 May 1999 at 10:38:41 +0200, Poul-Henning Kamp wrote: > In message <19990512033344.E21016@phc.igs.net>, Robert Garrett writes: > >On Wed, 12 May 1999 at 10:04:09 +0200, Poul-Henning Kamp wrote: > >> > >> I don't have time just now to attend this particular detail, which > >> manifests itself by swapinfo/pstat -p showing "/dev/(null)" for > >> device name. > >> > >> The problem in short is that libkvm:kvm_getswapinfo.c has it's > >> fingers in the kernels memory and pulls out a dev_t without knowing > >> how to (and it shouldn't be taught this!) convert it to a udev_t. > >> > >> The Right Way to solve this problem is to rewrite libkvm:kvm_getswapinfo.c > >> to pick up the information using some (for this purpose constructed) > >> sysctl variables (sysctlbyname(3) please!), and let the kernel convert > >> the dev_t to udev_t before passing it out to userland. > >> > >> So for any aspiring kernel hackers out there: have at it. Patches > >> accepted. > >> > >> In general libkvm should not grovel around in a running kernel but > >> only use sysctlbyname(3). > >> > >> -- > >the only place in the entire libkvm where a dev_t is used is > >kvm_proc.c line 230 this particular section completely looses me > > There is a dev_t passed out to pstat -s in a datastructure. Right and thats where it comes from kvm_proc.c is responsible for dealing with pstat at least the way I read that file Rob > > -- > 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 Wed May 12 1:48:56 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 2CF6D15C88 for ; Wed, 12 May 1999 01:48:48 -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 JAA04897; Wed, 12 May 1999 09:48:43 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 12 May 1999 09:48:43 +0100 (BST) From: Doug Rabson To: John Birrell Cc: current@freebsd.org Subject: Re: Debugging uthreads In-Reply-To: <199905120842.SAA25827@cimlogic.com.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 Wed, 12 May 1999, John Birrell wrote: > Doug Rabson wrote: > > Other gdb thread debugging systems tend to export a set of variables from > > the thread library which describe the important offsets in the thread > > structure e.g. _debug_pthread_status_offset, _debug_pthread_foo_offset > > etc. > > > > If you think there will be a real problem, I could do this I guess. > > Maybe we should just isolate the things that gdb is allowed to look at > and document them as "cast in stone". That would work. I think I only need uniqueid, sig_saved, saved_sigcontext, saved_jmpbuf, state and nxt. If those guys were lumped up at the start of struct pthread (possibly in another struct so that gdb doesn't need to know sizeof(struct pthread)) and marked appropriately then the debugger interface would be quite stable. -- 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 Wed May 12 1:50: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 806A215D7E for ; Wed, 12 May 1999 01:49:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id KAA24027; Wed, 12 May 1999 10:49:56 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id KAA03985; Wed, 12 May 1999 10:49:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Robert Garrett Cc: current@FreeBSD.ORG Subject: Re: simple (but important) task for junior kernel hacker In-reply-to: Your message of "Wed, 12 May 1999 03:45:29 -0000." <19990512034529.A5516@phc.igs.net> Date: Wed, 12 May 1999 10:49:53 +0200 Message-ID: <3983.926498993@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990512034529.A5516@phc.igs.net>, Robert Garrett writes: >> There is a dev_t passed out to pstat -s in a datastructure. > >Right and thats where it comes from kvm_proc.c is responsible for >dealing with pstat at least the way I read that file pstat >-s< is what we're talking about right now. -- 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 Wed May 12 1:54:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx.nsu.ru (mx.nsu.ru [193.124.215.71]) by hub.freebsd.org (Postfix) with ESMTP id F2C231503E for ; Wed, 12 May 1999 01:54:21 -0700 (PDT) (envelope-from semen@iclub.nsu.ru) Received: from iclub.nsu.ru (semen@iclub.nsu.ru [193.124.222.66]) by mx.nsu.ru (8.9.1/8.9.0) with ESMTP id PAA20286; Wed, 12 May 1999 15:51:15 +0700 (NOVST) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.9.3/8.8.5) with ESMTP id PAA21326; Wed, 12 May 1999 15:51:15 +0700 (NSS) Date: Wed, 12 May 1999 15:51:15 +0700 (NSS) From: Ustimenko Semen To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: Nt source licenses... In-Reply-To: <199905112056.WAA18582@labinfo.iet.unipi.it> 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, On Tue, 11 May 1999, Luigi Rizzo wrote: > Hi, > maybe i am the last one in the world to know, but were you guys aware > of this: > > http://research.microsoft.com/programs/NTSrcLicInfo.htm > > Microsoft makes Windows NT source code available to universities > and other "not-for-profit" research institutions at no charge. > Currently, there are over 55 universities and government agencies > with source licenses. > ... > > I still have to check the exact conditions though. The above web page > says this: > > Features of the license > > * No cost > * Intellectual property created with the use of NT source code is > owned by the researcher. > * Source licensees can share source or other source-based work > with other NT Source licensees. > * Source is licensed to the requesting organization, not individuals > to insure broad internal access. > * No employment restrictions as the result of viewing or using the > source. > Are we going to get this license? I am interested in NTFS source code a lot... P.S. What's happening with MS? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 1:55:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id BEF5A1503E for ; Wed, 12 May 1999 01:55:44 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id TAA25926; Wed, 12 May 1999 19:07:01 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905120907.TAA25926@cimlogic.com.au> Subject: Re: Debugging uthreads In-Reply-To: from Doug Rabson at "May 12, 1999 9:48:43 am" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 12 May 1999 19:07:01 +1000 (EST) Cc: jb@cimlogic.com.au, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > That would work. I think I only need uniqueid, sig_saved, > saved_sigcontext, saved_jmpbuf, state and nxt. If those guys were lumped > up at the start of struct pthread (possibly in another struct so that gdb > doesn't need to know sizeof(struct pthread)) and marked appropriately then > the debugger interface would be quite stable. I'd be inclined to add the magic number too, because it gives a hint as to whether the structure refers to a valid thread. If the thread is destroyed, the magic number is trashed. I think it is worth adding a new header file defining such a structure. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 1:59:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 38C47153B6 for ; Wed, 12 May 1999 01:59:24 -0700 (PDT) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id MAA76923 for ; Wed, 12 May 1999 12:59:23 +0400 (MSD) (envelope-from camel@avias.com) From: Ilya Naumov Reply-To: camel@avias.com To: current@FreeBSD.ORG Date: Wed, 12 May 1999 12:52:40 +0400 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99051212592200.00491@camel.avias.com> Content-Transfer-Encoding: 8bit Subject: X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG running FreeBSD 4.0-CURRENT i have encountered the following problems: 1. something is wrong with psm0 driver. my Genius NewScroll PS/2 mouse works well, but in random moment when i touch the mouse kernel starts to write to the system log the following. Apr 29 11:55:58 camel /kernel: psmintr: out of sync (00c8 != 0008). Apr 29 11:55:58 camel /kernel: psmintr: out of sync (00c0 != 0008). when it happens, mouse cursor moves, but buttons do not work. only reboot solves this problem. this bug doesn't appear with Microsoft and Hewlett-Packard mice. my string in my kernel config related to mouse is device psm0 at atkbdc? irq 12 and kernel detects the mouse as psm0: on atkbdc0 psm0: model NetMouse, device ID 0 psm0: interrupting at irq 12 2. i cannot start X Window + KDE wirh new kernel. the system just reboots when i start X. everything is ok with older (Tue May 11 16:17:50 MSD 1999) kernel. 3. i don't think that it is really a bug, but it's just interesting for me. during bootup process my kernel writes the following message: Bad SMBIOS table checksum! so, what is SMBIOS table and why its checksum is bad? :) -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 2: 0:41 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 C6C7F15B73 for ; Wed, 12 May 1999 02:00:37 -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 KAA06483; Wed, 12 May 1999 10:00:10 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 12 May 1999 10:00:10 +0100 (BST) From: Doug Rabson To: John Birrell Cc: current@freebsd.org Subject: Re: Debugging uthreads In-Reply-To: <199905120907.TAA25926@cimlogic.com.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 Wed, 12 May 1999, John Birrell wrote: > Doug Rabson wrote: > > That would work. I think I only need uniqueid, sig_saved, > > saved_sigcontext, saved_jmpbuf, state and nxt. If those guys were lumped > > up at the start of struct pthread (possibly in another struct so that gdb > > doesn't need to know sizeof(struct pthread)) and marked appropriately then > > the debugger interface would be quite stable. > > I'd be inclined to add the magic number too, because it gives a hint > as to whether the structure refers to a valid thread. If the thread > is destroyed, the magic number is trashed. > > I think it is worth adding a new header file defining such a structure. Ok, I'll see about updating my patch along these lines and I'll post up another one in a day or two. -- 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 Wed May 12 2: 1:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id 0C8AC15B73 for ; Wed, 12 May 1999 02:01:37 -0700 (PDT) (envelope-from soda@sra.co.jp) Received: from srapc288.sra.co.jp (sraihd [202.32.10.5]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id SAA06454; Wed, 12 May 1999 18:01:36 +0900 (JST) Received: (from soda@localhost) by srapc288.sra.co.jp (8.8.8/3.4W-sra) id SAA04493; Wed, 12 May 1999 18:01:35 +0900 (JST) Date: Wed, 12 May 1999 18:01:35 +0900 (JST) From: Noriyuki Soda Message-Id: <199905120901.SAA04493@srapc288.sra.co.jp> To: current@FreeBSD.ORG Cc: soda@sra.co.jp In-reply-to: Doug Rabson's message of Tue, 11 May 1999 08:21:37 +0100 (BST) Subject: Re: cvs commit: src/sys/pci pcisupport.c Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NOTE: Please Cc: soda@sra.co.jp, I am not subscribing this mailing list, because I am a NetBSD user. :-) > > It depends on old-config, so poor mechanism. newconfig already > > implimented best match probe/attach. > > And a very useful mechanism it is. Which is why I implemented priority > ordered probes in -current. Hmm, I thought this cannot be done correctly on new-bus, because the new-bus kicks match/attach routine from SYSINIT(). It is apparent that this fails in dynamic configuration case, because a potencial candidate of drivers which is dynamically loaded first always matches. This behaviour can not be called as "best match", but "first match". :-) Of course, dynamic configuration of newconfig solves this problem. Was this behaviour of the new-bus changed in -current ? BTW, there are many fundamental design flaws in new-bus, so I don't think new-bus is comparable with newconfig, yet, even if priority probe is implemented. For example: - newconfig can cope with both static configuration and dynamic configuration. new-bus can handle dynamic configuration only. This is because critical information for configuration is represented in C source internally. e.g. The bus/device hierarchy information is embedded in DRIVER_MODULE() on new-bus. On newconfig, such information is represented externally in "files" file. Thus the information can be used in both static and dynamic configuration case. As a result, newconfig can support same configuration syntax in both static and dynamic configuration, the new-bus never can do it. - new-bus cannot support on-demand device driver loading, dynamic configuration for newconfig can do it, though. This is because new-bus doesn't have the way to represent meta information like a mapping from device name to driver filename. If new-bus have this, there is no need to specifiy "kldload if_fxp", but just say "I need fxp0", then configuration framework can automatically load fxp driver, if it is not loaded yet. This is how configuration works in both newconfig and even oldconfig (look at static kernel configuration file for oldconfig, there is the line "device fxp0" which demands fxp driver to be loaded). The way to specify a driver to be linked on new-bus is retrogression to the age before 4.0BSD (4.0BSD introduced oldconfig and it was released on 1980 :-)). Why does a user have to specify file name instead of device name? Mmmm, perhaps do new-bus people believe MS-DOSism or Linuxism? :-) The way on new-bus will cause compatibility problem when OS is upgraded, because the implementation (filename) may be changed between versions and versions. - new-bus heavily depends on oldconfig which is known to be obsolete and machine dependent (look at usr.sbin/config/config.y, there are many definitions which depends on ISA bus, e.g. PORT, IOMEM, IOSIZE, ... newconfig can defines such attributes dynamically on demand.), and lacks many features which newconfig already has. e.g. - configruration hint which can be accessed from static configuration - bus/device hierarchy information which can be accessed from static configuration - inter module dependency information based on module attributes. new-bus completely lacks this feature, and depends on oldconfig about this. - mapping information from device name to object file name. new-bus completely lacks this feature, and depends on old config about this. Therefore, FreeBSD eventually will have to choose one of the following candidates: [a] gives up static configuration. But this doesn't solve the following problems: - at least console driver should be linked statically, unless you statically link this, you cannot get the error about dynamic loading critical drivers. :-) - in some applications, static configuration is good enough and dynamic configuration is merely overkill. FreeBSD will not cope with these applications better. Furthermore, this doesn't solves the problems about inter module dependency and mapping information from device name to object filename. [b] uses ugly kluge like hardcoding to solve the problems which already solved by the newconfig cleanly. [c] reinvents features which already implemented on the newconfig. This is exactly NIH problem, and means FreeBSD loses compatibility with *BSDs (FreeBSD becomes non-BSD). Note that newconfig is genuine feature of 4.4BSD, and 4.4BSD red daemon books already said that after the system is completely booted, 4.4BSD (i.e. newconfig) cannot load device drivers.... These problems are all well understood and EASY TO FIX. in page 502. As this shows, it is apparent that newconfig can cope with dynamic configuration, why do new-bus people thought that newconfig cannot deal with dynamic configuration, and reinvent configuration framework? It is obvious that they do not know about newconfig enough, (their terminology like "ivar" shows this fact). [d] shifts the all the problems to users (e.g. see compatibility problem mentioned above) All of above facts are already told to one of the FreeBSD core members, just before core members officialy decided to choose new-bus. I do not know why core members decide new-bus, though. P.S. It seems FreeBSD already start to choose [b]. Please look at changes in revision 1.67 of sys/i386/isa/npx.c. It hardcodes magic number 13, instead of the value gotton from configuration framework. It is interesting that even this doesn't use #define NPXIRQ 13. :-) This reminds me another ugly kluge in sys/pccard/i82365.h: #define PCIC_INDEX_0 0x3E0 #define PCIC_INDEX_1 (PCIC_INDEX_0 + 2) This is the way what some clever FreeBSD people saids "right" to Nakagawa-san, though Nakagawa-san never agreed that it is right, and rather likes the newconfig way like below: pcic0 at isa? port 0x3e0 pcic1 at isa? port 0x3e2 pcic* at pci? pcic* at isapnp? It is apparent which is better and cleaner for me. But perhaps you do not agree with me. :-) -- soda@sra.co.jp Software Research Associates, Inc., Japan (Noriyuki Soda) Advanced Technology Group. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 2: 4:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 81FBD15B73 for ; Wed, 12 May 1999 02:04:14 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id TAA25980; Wed, 12 May 1999 19:15:33 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905120915.TAA25980@cimlogic.com.au> Subject: Re: Debugging uthreads In-Reply-To: from Doug Rabson at "May 12, 1999 10: 0:10 am" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 12 May 1999 19:15:33 +1000 (EST) Cc: jb@cimlogic.com.au, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > Ok, I'll see about updating my patch along these lines and I'll post up > another one in a day or two. One more thing... the states are subject to change, probably with new states being added. It is important to check that the state number is within the range that gdb was compiled against (the states probably should be in the common header) and if the state number is out of that range, just display the number. Then we just need to ensure we add new states at the end. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 2:19:23 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 7B87E15315 for ; Wed, 12 May 1999 02:19:19 -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 KAA07901; Wed, 12 May 1999 10:19:08 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 12 May 1999 10:19:01 +0100 (BST) From: Doug Rabson To: John Birrell Cc: current@freebsd.org Subject: Re: Debugging uthreads In-Reply-To: <199905120915.TAA25980@cimlogic.com.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 Wed, 12 May 1999, John Birrell wrote: > Doug Rabson wrote: > > Ok, I'll see about updating my patch along these lines and I'll post up > > another one in a day or two. > > One more thing... the states are subject to change, probably with new > states being added. It is important to check that the state number is > within the range that gdb was compiled against (the states probably > should be in the common header) and if the state number is out of > that range, just display the number. Then we just need to ensure we > add new states at the end. I think the only state which I need to know about is PS_DEAD. If we marked dead threads in the public struct it might simplify things. -- 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 Wed May 12 2:24:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 57AB215E57 for ; Wed, 12 May 1999 02:24:31 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id TAA26050; Wed, 12 May 1999 19:34:47 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905120934.TAA26050@cimlogic.com.au> Subject: Re: Debugging uthreads In-Reply-To: from Doug Rabson at "May 12, 1999 10:19: 1 am" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 12 May 1999 19:34:46 +1000 (EST) Cc: jb@cimlogic.com.au, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > I think the only state which I need to know about is PS_DEAD. If we marked > dead threads in the public struct it might simplify things. You use PS_RUNNING too. We could just tie down those two as PS_DEAD = 0 and PS_RUNNING = 1. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 2:24:50 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 0F8FF15DF2 for ; Wed, 12 May 1999 02:23:59 -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 KAA19969; Wed, 12 May 1999 10:23:45 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 12 May 1999 10:23:45 +0100 (BST) From: Doug Rabson To: Noriyuki Soda Cc: current@freebsd.org Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905120901.SAA04493@srapc288.sra.co.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 Wed, 12 May 1999, Noriyuki Soda wrote: > NOTE: Please Cc: soda@sra.co.jp, I am not subscribing this mailing > list, because I am a NetBSD user. :-) > > > > It depends on old-config, so poor mechanism. newconfig already > > > implimented best match probe/attach. > > > > And a very useful mechanism it is. Which is why I implemented priority > > ordered probes in -current. > > Hmm, I thought this cannot be done correctly on new-bus, because > the new-bus kicks match/attach routine from SYSINIT(). It is apparent > that this fails in dynamic configuration case, because a potencial > candidate of drivers which is dynamically loaded first always matches. > This behaviour can not be called as "best match", but "first match". :-) > Of course, dynamic configuration of newconfig solves this problem. > > Was this behaviour of the new-bus changed in -current ? Yes. > BTW, there are many fundamental design flaws in new-bus, so I don't > think new-bus is comparable with newconfig, yet, even if priority > probe is implemented. For example: I'm not going to reply to these points as I suspect it will lead to a pointless flame thread. I would prefer to discuss these issues in person at Usenix. -- 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 Wed May 12 2:26:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id 4FA4C15A8A for ; Wed, 12 May 1999 02:26:49 -0700 (PDT) (envelope-from soda@sra.co.jp) Received: from srasvf.sra.co.jp (srasvf [133.137.28.2]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id SAA08288; Wed, 12 May 1999 18:26:48 +0900 (JST) Received: from srapc342.sra.co.jp (srapc342 [133.137.28.111]) by srasvf.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id SAA04455; Wed, 12 May 1999 18:26:35 +0900 (JST) Received: (from soda@localhost) by srapc342.sra.co.jp (8.8.8/3.4W-sra) id SAA19601; Wed, 12 May 1999 18:26:45 +0900 (JST) Date: Wed, 12 May 1999 18:26:45 +0900 (JST) From: Noriyuki Soda Message-Id: <199905120926.SAA19601@srapc342.sra.co.jp> To: dfr@nlsystems.com Subject: Re: cvs commit: src/sys/pci pcisupport.c Cc: current@freebsd.org, soda@sra.co.jp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > BTW, there are many fundamental design flaws in new-bus, so I don't > > think new-bus is comparable with newconfig, yet, even if priority > > probe is implemented. For example: > > I'm not going to reply to these points as I suspect it will lead to a > pointless flame thread. I would prefer to discuss these issues in person > at Usenix. I agree that this is better way to solve the conflicts between new-bus and newconfig. Although I wondered why FreeBSD's core decide to choose new-bus before Usenix. -- soda@sra.co.jp Software Research Associates, Inc., Japan (Noriyuki Soda) Advanced Technology Group. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 2:34:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 92CAC14BD3 for ; Wed, 12 May 1999 02:34:06 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id VAA11048; Wed, 12 May 1999 21:34:04 +1200 (NZST) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.3/8.9.2) id VAA66351; Wed, 12 May 1999 21:33:45 +1200 (NZST) (envelope-from jabley) Date: Wed, 12 May 1999 21:33:44 +1200 From: Joe Abley To: freebsd-current@freebsd.org Cc: jabley@clear.co.nz Subject: has the 3.2 branch happened? Message-ID: <19990512213344.A64308@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (he asked :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 3: 2:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 22CD614D67; Wed, 12 May 1999 03:02:54 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.2/8.8.8) id KAA86935; Wed, 12 May 1999 10:58:49 +0100 (BST) (envelope-from joe) Date: Wed, 12 May 1999 10:58:49 +0100 From: Josef Karthauser To: Poul-Henning Kamp Cc: Chuck Youse , Peter Wemm , Snob Art Genre , Dennis Glatting , Bill Paul , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Anybody actually using gigabit ethernet? Message-ID: <19990512105849.A71991@pavilion.net> References: <1369.926446995@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <1369.926446995@critter.freebsd.dk>; from Poul-Henning Kamp on Tue, May 11, 1999 at 08:23:15PM +0200 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 11, 1999 at 08:23:15PM +0200, Poul-Henning Kamp wrote: > > Isn't it more appropriate to ask where he didn't learn to read ? :-) > Ok. ok. thanks for the abuse :) > > > >> > tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). > > So we're agreed that this is confusing no? Couldn't it read: tcp_extensions="NO" # Switch RFC1323 extensions on? That way I'd understand it however awake I was :) Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 3: 7:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from voyage.coolfitch.ie (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id ED13714F1A for ; Wed, 12 May 1999 03:07:45 -0700 (PDT) (envelope-from steveo@iol.ie) Received: from voyage.coolfitch.ie (localhost [127.0.0.1]) by voyage.coolfitch.ie (8.9.3/8.9.2) with ESMTP id LAA00635; Wed, 12 May 1999 11:00:28 +0100 (IST) (envelope-from steveo@iol.ie) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <99051212592200.00491@camel.avias.com> Date: Wed, 12 May 1999 11:00:27 +0100 (IST) From: "Steve O'Hara-Smith" To: Ilya Naumov Subject: RE: Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-May-99 Ilya Naumov wrote: > > running FreeBSD 4.0-CURRENT i have encountered the following > problems: > > 1. something is wrong with psm0 driver. my Genius NewScroll PS/2 > mouse works > well, but in random moment when i touch the mouse kernel starts to > write to the > system log the following. > > Apr 29 11:55:58 camel /kernel: psmintr: out of sync (00c8 != 0008). > Apr 29 11:55:58 camel /kernel: psmintr: out of sync (00c0 != 0008). > > when it happens, mouse cursor moves, but buttons do not work. only > reboot solves this problem. this bug doesn't appear with Microsoft > and > Hewlett-Packard mice. If you are using moused then a killall -HUP moused can often solve this sort of problem without a reboot. ---------------------------------- E-Mail: Steve O'Hara-Smith Date: 12-May-99 Time: 10:59:13 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 3:15:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from neophyte.h4x0rz.za.org (neophyte.h4x0rz.za.org [206.49.228.8]) by hub.freebsd.org (Postfix) with ESMTP id E140C14EDF for ; Wed, 12 May 1999 03:15:34 -0700 (PDT) (envelope-from andrew@neophyte.h4x0rz.za.org) Received: from localhost (andrew@localhost) by neophyte.h4x0rz.za.org (8.9.3/8.9.2) with ESMTP id MAA02508 for ; Wed, 12 May 1999 12:17:04 +0200 (SAST) (envelope-from andrew@neophyte.h4x0rz.za.org) Date: Wed, 12 May 1999 12:17:03 +0200 (SAST) From: vortexia To: current@freebsd.org Subject: Re: simple (but important) task for junior kernel hacker In-Reply-To: <3983.926498993@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 Hrmmm have any commits been made on this one yet? The reason Im asking is that as of about 2am my time last night I cvsupped to 4.0-CURRENT and I cant build, it dies on libkvm. It claims the error exists in /usr/src/sys/sys/vnode.h, exact error message as follows: In file included from /usr/src/lib/libkvm/kvm_getswapinfo.c:22: /usr/src/lib/libkvm/../../sys/sys/vnode.h:186: parse error before `udev_t' /usr/src/lib/libkvm/../../sys/sys/vnode.h:186: warning: no semicolon at end of struct or union /usr/src/lib/libkvm/../../sys/sys/vnode.h:191: parse error before `:' cc -nostdinc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm/../../sys -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libkvm/kvm_proc.c -o kvm_proc.o cc -fpic -DPIC -nostdinc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm/../../sys -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libkvm/kvmproc.c -o kvm_proc.So *** Error code 1 *** Error code 1 2 errors (I think this is right, I had to type it out but I think I got it ok). Any ideas? Cheers Andrew On Wed, 12 May 1999, Poul-Henning Kamp wrote: > In message <19990512034529.A5516@phc.igs.net>, Robert Garrett writes: > > >> There is a dev_t passed out to pstat -s in a datastructure. > > > >Right and thats where it comes from kvm_proc.c is responsible for > >dealing with pstat at least the way I read that file > > pstat >-s< is what we're talking about right now. > > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 3:17:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 1591D1506E for ; Wed, 12 May 1999 03:17:25 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id GAA08837; Wed, 12 May 1999 06:16:46 -0400 (EDT) Date: Wed, 12 May 1999 06:16:46 -0400 (EDT) From: Daniel Eischen Message-Id: <199905121016.GAA08837@pcnet1.pcnet.com> To: dfr@nlsystems.com, jb@cimlogic.com.au Subject: Re: Debugging uthreads Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell wrote: > Doug Rabson wrote: > > Other gdb thread debugging systems tend to export a set of variables from > > the thread library which describe the important offsets in the thread > > structure e.g. _debug_pthread_status_offset, _debug_pthread_foo_offset > > etc. > > > If you think there will be a real problem, I could do this I guess. > > Maybe we should just isolate the things that gdb is allowed to look at > and document them as "cast in stone". Why don't we make a libc_r_db and provide the necessary interfaces to gdb from that instead of having gdb know about uthread internals? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 3:18:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 2F88C1506E for ; Wed, 12 May 1999 03:18:40 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id MAA24497; Wed, 12 May 1999 12:18:36 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id MAA04380; Wed, 12 May 1999 12:18:24 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: vortexia Cc: current@FreeBSD.ORG Subject: Re: simple (but important) task for junior kernel hacker In-reply-to: Your message of "Wed, 12 May 1999 12:17:03 +0200." Date: Wed, 12 May 1999 12:18:24 +0200 Message-ID: <4378.926504304@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I fixed that a few hours ago. In message , v ortexia writes: >Hrmmm have any commits been made on this one yet? The reason Im asking is >that as of about 2am my time last night I cvsupped to 4.0-CURRENT and I >cant build, it dies on libkvm. > >It claims the error exists in /usr/src/sys/sys/vnode.h, exact error >message as follows: > >In file included from /usr/src/lib/libkvm/kvm_getswapinfo.c:22: >/usr/src/lib/libkvm/../../sys/sys/vnode.h:186: parse error before `udev_t' >/usr/src/lib/libkvm/../../sys/sys/vnode.h:186: warning: no semicolon at >end of struct or union >/usr/src/lib/libkvm/../../sys/sys/vnode.h:191: parse error before `:' >cc -nostdinc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm/../../sys >-I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libkvm/kvm_proc.c -o >kvm_proc.o >cc -fpic -DPIC -nostdinc -O -pipe -DLIBC_SCCS >-I/usr/src/lib/libkvm/../../sys -I/usr/obj/usr/src/tmp/usr/include -c >/usr/src/lib/libkvm/kvmproc.c -o kvm_proc.So >*** Error code 1 >*** Error code 1 >2 errors > >(I think this is right, I had to type it out but I think I got it ok). > >Any ideas? > >Cheers > >Andrew > > On Wed, 12 May 1999, Poul-Henning Kamp wrote: > >> In message <19990512034529.A5516@phc.igs.net>, Robert Garrett writes: >> >> >> There is a dev_t passed out to pstat -s in a datastructure. >> > >> >Right and thats where it comes from kvm_proc.c is responsible for >> >dealing with pstat at least the way I read that file >> >> pstat >-s< is what we're talking about right now. >> >> -- >> 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 >> > > > >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 Wed May 12 3:22:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 8354B1506E for ; Wed, 12 May 1999 03:22:09 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id UAA26267; Wed, 12 May 1999 20:32:56 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199905121032.UAA26267@cimlogic.com.au> Subject: Re: Debugging uthreads In-Reply-To: <199905121016.GAA08837@pcnet1.pcnet.com> from Daniel Eischen at "May 12, 1999 6:16:46 am" To: eischen@vigrid.com (Daniel Eischen) Date: Wed, 12 May 1999 20:32:56 +1000 (EST) Cc: dfr@nlsystems.com, jb@cimlogic.com.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen wrote: > Why don't we make a libc_r_db and provide the necessary interfaces to > gdb from that instead of having gdb know about uthread internals? It would still mean that gdb would be linked to the uthread internals which may not match the version of libc_r that the 3rd party program was linked against. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 3:23:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id 1407415125 for ; Wed, 12 May 1999 03:23:19 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id MAA04511; Wed, 12 May 1999 12:22:35 +0200 (CEST) Date: Wed, 12 May 1999 12:21:56 +0200 From: Stefan Bethke To: Andrzej Bialecki Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current Message-ID: <64131.3135500516@d225.promo.de> In-Reply-To: Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > On Sat, 8 May 1999, Peter Wemm wrote: > >> It's interesting that the ANSI emulation in loader(8) is good enough to >> do full-screen displays. It still seems to make sense to move >> userconfig-like functionality into the pre-kernel stages including >> moving config(8)'s hints to a loaded and parsed file. Forth, bah.. :-] > > Heh... To tell you the truth, that was my initial dream which prompted = me > to start writing it. It could be done now, really... Right at this moment, I would like to have a simple boot menu: I have both -stable and -current on a single drive (different partitions), and I'd = like to select which to boot with a single key stroke. Any pointer on Forth literature/web pages would be appreciated, especially if it's not the ANSI standard (I've looked at it, and it is that: a standard, not a reference manual or a tutorial). My Forth knowledge is rather rusty, I realised... last time I remember I was sitting in front of my Apple II clone about 15 years ago. Stefan -- M=FChlendamm 12 | Voice +49-40-256848, +49-177-3504009 D-22089 Hamburg | e-mail: stefan.bethke@hanse.de Germany | stb@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 May 12 3:36:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 74B4715270 for ; Wed, 12 May 1999 03:36:10 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id GAA10411; Wed, 12 May 1999 06:35:31 -0400 (EDT) Date: Wed, 12 May 1999 06:35:31 -0400 (EDT) From: Daniel Eischen Message-Id: <199905121035.GAA10411@pcnet1.pcnet.com> To: eischen@vigrid.com, jb@cimlogic.com.au Subject: Re: Debugging uthreads Cc: current@FreeBSD.ORG, dfr@nlsystems.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell wrote: > Daniel Eischen wrote: > > Why don't we make a libc_r_db and provide the necessary interfaces to > > gdb from that instead of having gdb know about uthread internals? > > It would still mean that gdb would be linked to the uthread internals > which may not match the version of libc_r that the 3rd party program > was linked against. OK, but it still seems more appropriate to have uthread debugging internals known somewhere other than in GDB. It seems more obvious to have to modify libc_r_db when libc_r changes than to know to update the gdb sources. If threads had versioning information as well as trying to set certain attributes in stone, then libc_r_db could be made to be backwards compatible with older thread libraries. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 3:50:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id DAB4B150C5 for ; Wed, 12 May 1999 03:50:37 -0700 (PDT) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id OAA81307; Wed, 12 May 1999 14:50:23 +0400 (MSD) (envelope-from camel@avias.com) From: Ilya Naumov Reply-To: camel@avias.com To: current@FreeBSD.ORG Subject: RE: problem with NewScroll Mouse, etc Date: Wed, 12 May 1999 14:42:25 +0400 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: Cc: "Steve O'Hara-Smith" MIME-Version: 1.0 Message-Id: <99051214502200.06507@camel.avias.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We , 12 may 1999, Steve O'Hara-Smith wrote: > > 1. something is wrong with psm0 driver. my Genius NewScroll PS/2 > > mouse works > > well, but in random moment when i touch the mouse kernel starts to > > write to the > > system log the following. > > > > Apr 29 11:55:58 camel /kernel: psmintr: out of sync (00c8 != 0008). > > Apr 29 11:55:58 camel /kernel: psmintr: out of sync (00c0 != 0008). > > > > when it happens, mouse cursor moves, but buttons do not work. only > > reboot solves this problem. even full restart of moused doesn't help. very strange bug. NewScroll seems to be fully compatible with Microsoft PS/2 mouse protocol, and a problem with it appears under FreeBSD only. -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 5:44:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-spool.is.co.za (mail-spool.is.co.za [196.4.160.4]) by hub.freebsd.org (Postfix) with ESMTP id 9C17815D01 for ; Wed, 12 May 1999 05:43:21 -0700 (PDT) (envelope-from geoffr@is.co.za) Received: from admin.is.co.za (admin.is.co.za [196.23.0.9]) by mail-spool.is.co.za (8.8.8/IShub#3) with ESMTP id OAA12975 for ; Wed, 12 May 1999 14:46:03 +0200 Received: from isjhbex01.is.co.za (isjhbex01.is.co.za [196.26.1.16]) by admin.is.co.za (8.8.6/8.7.3/ISsubsidiary#1) with ESMTP id OAA01864 for ; Wed, 12 May 1999 14:43:14 +0200 (GMT) Received: by isjhbex01.is.co.za with Internet Mail Service (5.5.2232.9) id ; Wed, 12 May 1999 14:36:03 +0200 Message-ID: <3D5EC7D2992BD211A95600A0C9CE047F0308D99F@isjhbex01.is.co.za> From: Geoff Rehmet To: "'current@freebsd.org'" Subject: Today's kernel crashes on starting X Date: Wed, 12 May 1999 14:35:54 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently running into a problem, that when I start my system, it spontaneously reboots when starting X. Has anyone else run into this? -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geoffr@is.co.za URL: http://www.is.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 5:53:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id 2094414FA8 for ; Wed, 12 May 1999 05:53:43 -0700 (PDT) (envelope-from erik@habatech.no) Received: from freebsd.habatech.no ([62.92.133.2]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id OAA08729; Wed, 12 May 1999 14:52:26 +0200 (CEST) (envelope-from erik@habatech.no) From: erik@habatech.no Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 12 May 1999 14:59:10 +0200 (CEST) Reply-To: erik@habatech.no Organization: Habatech AS To: Ustimenko Semen Subject: Re: Nt source licenses... Cc: current@FreeBSD.ORG, Luigi Rizzo Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-May-99 Ustimenko Semen wrote: > > Are we going to get this license? I am interested in NTFS > source code a lot... > > P.S. What's happening with MS? > They have got a virus. I think they're calling it Open Source... They're fighting really hard to get rid of it, but these things can happen from time to time :) -- --------------------------------+---------------------------------------+ Erik H. Bakke, Habatech AS | To be or not to be... | E-Mail: erik@habatech.no | Is simply a question of binary logic. | Consultancy, Development, Sales | | --------------------------------+---------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 6: 1:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (pauling.research.devcon.net [212.15.193.194]) by hub.freebsd.org (Postfix) with ESMTP id 3EF0D14BFE for ; Wed, 12 May 1999 06:01:52 -0700 (PDT) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id PAA00509 for ; Wed, 12 May 1999 15:01:51 +0200 (CEST) (envelope-from cc@devcon.net) X-Authentication-Warning: pauling.research.devcon.net: cc owned process doing -bs Date: Wed, 12 May 1999 15:01:51 +0200 (CEST) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: current@freebsd.org Subject: vinum broken?? 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, Does anyone else experience problems with the current kernel release and vinum? I've compiled a new kernel along with a make world today. After rebooting vinum did not start: "/dev/vinum/Control: invalid operation..." Any suggestions? regards, Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 6:37:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id 96B2314F34 for ; Wed, 12 May 1999 06:37:44 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id PAA11289; Wed, 12 May 1999 15:37:41 +0200 (CEST) (envelope-from des) To: current@freebsd.org Subject: DMA problems with IBM DeskStar drive Organization: Yes! Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 12 May 1999 15:37:40 +0200 Message-ID: Lines: 344 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a brand new 10 GB IBM UltrStar (DTTA-371010) which is causing me some pains. If I boot with flags 0x80ff, everything works fine: wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): , 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 on isa0 wdc1: unit 0 (wd2): , 32-bit, multi-block-16 wd2: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S but heavy disk access slows the machine to a crawl, as can be expected from any device that does heavy PIO. If I try to boot with flags 0xa0ff to enable DMA, however, this is what I get: wdc0 at port 0x1f0-0x1f7 irq 14 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 wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc1 at port 0x170-0x177 irq 15 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 wd2: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 [...] Considering FFS root f/s. changing root device to wd0s4a changing root device to wd0a start_init: trying /sbin/init wd0: DMA failure, DMA status 5 wd0: DMA failure, DMA status 5 wd0: DMA failure, DMA status 5 wd0: DMA failure, DMA status 5 wd2s1: type 0xa5, start 0, end = 4124735, size 4124736 : OK xl0: selecting BNC port, half duplex wd0: DMA failure, DMA status 5 wd0: DMA failure, DMA status 5 wd0: DMA failure, DMA status 5 wd0: DMA failure, DMA status 5 and a *lot* more of those. Nothing bad seems to hapen (no fs corruption or anything). In fact, I managed to recompile a kernel while this was going on. The Seagate disk (wd2) causes no trouble at all, DMA or no DMA. The problem occurs in both -STABLE and -CURRENT. I've attached a complete kernel config and verbose boot log. DES -- Dag-Erling Smorgrav - des@yes.no # Kernel configuration for des.follo.net machine i386 cpu I586_CPU cpu I686_CPU ident DES maxusers 32 makeoptions DEBUG=-g options COMPAT_43 options FFS options FFS_ROOT options ICMP_BANDLIM options INCLUDE_CONFIG_FILE options INET options IPFIREWALL options IPFIREWALL_VERBOSE options KTRACE options PROCFS options SOFTUPDATES options SYSVMSG options SYSVSEM options SYSVSHM options UCONSOLE options USERCONFIG options VESA options VISUAL_USERCONFIG options VM86 config kernel root on wd0 controller isa0 controller pci0 controller pnp0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 controller wdc0 at isa? port IO_WD1 irq 14 controller wdc1 at isa? port IO_WD2 irq 15 disk wd0 at wdc0 drive 0 flags 0xa0ff disk wd2 at wdc1 drive 0 flags 0xa0ff controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? options MSGBUF_SIZE=32768 options SC_HISTORY_SIZE=1024 device npx0 at nexus? port IO_NPX irq 13 device apm0 at isa? device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device ppc0 at isa? port? irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device xl0 pseudo-device loop pseudo-device ether pseudo-device tun 4 pseudo-device bpfilter 4 pseudo-device pty 64 pseudo-device vn 4 device pcm0 at isa? port? irq 5 drq 1 flags 0x0 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: Sun May 9 19:00:44 CEST 1999 root@des.follo.net:/usr/src/sys/compile/DES Calibrating clock(s) ... TSC clock: 350799158 Hz, i8254 clock: 1193196 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping=12 Features=0x8021bf Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 128M bytes Write Allocate 15-16M bytes: Enable real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x00281000 - 0x07ff7fff, 131559424 bytes (32119 pages) sio0: system console avail memory = 128118784 (125116K bytes) Found BIOS32 Service Directory header at 0xc00f9b80 Entry = 0xf0530 (0xc00f0530) Rev = 0 Len = 1 PCI BIOS entry at 0x560 DMI header at 0xc00f5490 Version 2.0 Table at 0xf54aa, 31 entries, 990 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fcfb0 Preloaded elf kernel "kernel" at 0xc0268000. VESA: information block 56 45 53 41 00 02 a5 72 00 c0 01 00 00 00 22 00 00 01 80 00 03 01 ba 72 00 c0 c1 72 00 c0 ca 72 00 c0 00 01 01 01 02 01 03 01 05 01 07 01 08 01 09 01 0a 01 0b 01 0c 01 10 01 11 01 12 01 13 01 VESA: 25 mode(s) found Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] Called nullpnp_probe with tag 0x00000001, type 0xf0008c0e Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 port 0x0220 0x0300 0x0388 0x0000 irq 10:0 drq 1:0 en 1 port 0x0220 0x0300 0x0388 0x0000 irq 10:0 drq 1:0 en 1 pcm1 (SB16pnp sn 0xffffffff) at 0x220-0x22f irq 10 drq 1 flags 0x10 on isa pci_open(1): mode 1 addr port (0x0cf8) is 0x80010000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=154110b9) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 1400812397 bytes/sec bzero() bandwidth = 132380195 bytes/sec apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard found-> vendor=0x10b9, dev=0x1541, revid=0x04 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 1, range 32, base e0000000, size 26 found-> vendor=0x10b9, dev=0x5243, revid=0x04 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x10b9, dev=0x7101, revid=0x00 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x10b9, dev=0x1533, revid=0xc3 class=06-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x10b7, dev=0x9001, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[0]: type 4, range 32, base 0000d800, size 6 found-> vendor=0x10b9, dev=0x5229, revid=0xc1 class=01-01-8a, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=0 map[0]: type 4, range 32, base 0000d400, size 4 pci0: on pcib0 chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 found-> vendor=0x102b, dev=0x0521, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 3, range 32, base e7000000, size 24 map[1]: type 1, range 32, base df800000, size 14 map[2]: type 1, range 32, base df000000, size 23 pci1: on pcib1 chip1: at device 3.0 on pci0 isab0: at device 7.0 on pci0 xl0: <3Com 3c900-COMBO Etherlink XL> irq 12 at device 11.0 on pci0 xl0: Ethernet address: 00:60:08:cf:a8:e4 xl0: media options word: e138 xl0: found 10baseT xl0: found AUI xl0: found BNC xl0: selecting 10baseT transceiver, half duplex bpf: xl0 attached ide_pci0: irq 0 at device 15.0 on pci0 ide_pci: busmaster 0 status: a4 from port: 0000d402 ide_pci: ide0:0 has been configured for DMA by BIOS ide_pci: busmaster 1 status: a4 from port: 0000d40a ide_pci: ide1:0 has been configured for DMA by BIOS devclass_alloc_unit: apm0 already exists, using next available unit number 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): , DMA, 32-bit, multi-block-16 wd0: 9641MB (19746720 sectors), 19590 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc1 at port 0x170-0x177 irq 15 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 wd2: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 atkbdc0: at port 0x60 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0067 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. vga0: on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VESA: v2.0, 8192k memory, flags:0x1, mode table:0xc0226a22 (1000022) VESA: Matrox Graphics Inc. VESA: Matrox VESA: MGA-G200 VESA: 00 sc0: on isa0 sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 mss_probe: no address supplied, try default 0x530 mss_detect error, busy still set (0xff) sb_probe: no address supplied, try defaults (0x220,0x240) device at 0x220 already attached as unit 1 BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. IP packet filtering initialized, divert disabled, rule-based forwarding disabled, unlimited logging bpf: tun0 attached bpf: tun1 attached bpf: tun2 attached bpf: tun3 attached bpf: lo0 attached Considering FFS root f/s. changing root device to wd0s4a changing root device to wd0a start_init: trying /sbin/init wd0: DMA failure, DMA status 5 wd0: DMA failure, DMA status 5 wd0: DMA failure, DMA status 5 wd0: DMA failure, DMA status 5 wd2s1: type 0xa5, start 0, end = 4124735, size 4124736 : OK xl0: selecting BNC port, half duplex wd0: DMA failure, DMA status 5 wd0: DMA failure, DMA status 5 wd0: DMA failure, DMA status 5 wd0: DMA failure, DMA status 5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 6:41:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id C3F3F14CBA for ; Wed, 12 May 1999 06:41:45 -0700 (PDT) (envelope-from soda@sra.co.jp) Received: from srasvf.sra.co.jp (srasvf [133.137.28.2]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id WAA17486; Wed, 12 May 1999 22:41:33 +0900 (JST) Received: from srapc342.sra.co.jp (srapc342 [133.137.28.111]) by srasvf.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id WAA05835; Wed, 12 May 1999 22:41:16 +0900 (JST) Received: (from soda@localhost) by srapc342.sra.co.jp (8.8.8/3.4W-sra) id WAA22134; Wed, 12 May 1999 22:41:28 +0900 (JST) Date: Wed, 12 May 1999 22:41:28 +0900 (JST) Message-Id: <199905121341.WAA22134@srapc342.sra.co.jp> From: Noriyuki Soda To: "Rick Whitesel" Cc: "Noriyuki Soda" , Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <008501be9c7c$51a38020$d3e4b38c@xyplex.com> References: <199905120901.SAA04493@srapc288.sra.co.jp> <008501be9c7c$51a38020$d3e4b38c@xyplex.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Wed, 12 May 1999 09:35:36 -0400, "Rick Whitesel" said: > In general I believe that dynamic configuration of the system is > extremely useful to both the development community and the user > community. The development community has a much easier time if they > can load / unload drivers. As for the users, my rule of thumb is > that a computer should never ask a human the answer to a question > that it can find out for itself. I think this is especially true for > configuration information. In addition, the need for dynamic system > (re)configuration will only increase as features like PCI hot swap > become the standard. Of course, I completely agree with you. The reason I prefer newconfig is it actually can support dynamic configuration better than the new-bus. All features which new-bus has can be implemented on newconfig, too. And, more. (See the description about on-demand dynamic loading in my previous post.) Furthremore, newconfig does static configuration better than the new-bus, and newconfig has a option which removes dynamic configuration entirely from kernel. New-bus apparently doesn't have this option. So, which is flexible ? :-) -- soda@sra.co.jp Software Research Associates, Inc., Japan (Noriyuki Soda) Advanced Technology Group. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 6:42:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id 726F414E96 for ; Wed, 12 May 1999 06:42:23 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id JAA18940; Wed, 12 May 1999 09:28:53 -0400 (EDT) Message-ID: <008501be9c7c$51a38020$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: "Noriyuki Soda" , Cc: References: <199905120901.SAA04493@srapc288.sra.co.jp> Subject: Re: cvs commit: src/sys/pci pcisupport.c Date: Wed, 12 May 1999 09:35:36 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: While I confess to not having the whole picture here, I do, of course, have an opinion. In general I believe that dynamic configuration of the system is extremely useful to both the development community and the user community. The development community has a much easier time if they can load / unload drivers. As for the users, my rule of thumb is that a computer should never ask a human the answer to a question that it can find out for itself. I think this is especially true for configuration information. In addition, the need for dynamic system (re)configuration will only increase as features like PCI hot swap become the standard. Rick Whitesel Scientist NBase-Xyplex Eml: rwhitesel@nbase-xyplex.com "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 ----- Original Message ----- From: Noriyuki Soda To: Cc: Sent: Wednesday, May 12, 1999 5:01 AM Subject: Re: cvs commit: src/sys/pci pcisupport.c NOTE: Please Cc: soda@sra.co.jp, I am not subscribing this mailing list, because I am a NetBSD user. :-) > > It depends on old-config, so poor mechanism. newconfig already > > implimented best match probe/attach. > > And a very useful mechanism it is. Which is why I implemented priority > ordered probes in -current. Hmm, I thought this cannot be done correctly on new-bus, because the new-bus kicks match/attach routine from SYSINIT(). It is apparent that this fails in dynamic configuration case, because a potencial candidate of drivers which is dynamically loaded first always matches. This behaviour can not be called as "best match", but "first match". :-) Of course, dynamic configuration of newconfig solves this problem. Was this behaviour of the new-bus changed in -current ? BTW, there are many fundamental design flaws in new-bus, so I don't think new-bus is comparable with newconfig, yet, even if priority probe is implemented. For example: - newconfig can cope with both static configuration and dynamic configuration. new-bus can handle dynamic configuration only. This is because critical information for configuration is represented in C source internally. e.g. The bus/device hierarchy information is embedded in DRIVER_MODULE() on new-bus. On newconfig, such information is represented externally in "files" file. Thus the information can be used in both static and dynamic configuration case. As a result, newconfig can support same configuration syntax in both static and dynamic configuration, the new-bus never can do it. - new-bus cannot support on-demand device driver loading, dynamic configuration for newconfig can do it, though. This is because new-bus doesn't have the way to represent meta information like a mapping from device name to driver filename. If new-bus have this, there is no need to specifiy "kldload if_fxp", but just say "I need fxp0", then configuration framework can automatically load fxp driver, if it is not loaded yet. This is how configuration works in both newconfig and even oldconfig (look at static kernel configuration file for oldconfig, there is the line "device fxp0" which demands fxp driver to be loaded). The way to specify a driver to be linked on new-bus is retrogression to the age before 4.0BSD (4.0BSD introduced oldconfig and it was released on 1980 :-)). Why does a user have to specify file name instead of device name? Mmmm, perhaps do new-bus people believe MS-DOSism or Linuxism? :-) The way on new-bus will cause compatibility problem when OS is upgraded, because the implementation (filename) may be changed between versions and versions. - new-bus heavily depends on oldconfig which is known to be obsolete and machine dependent (look at usr.sbin/config/config.y, there are many definitions which depends on ISA bus, e.g. PORT, IOMEM, IOSIZE, ... newconfig can defines such attributes dynamically on demand.), and lacks many features which newconfig already has. e.g. - configruration hint which can be accessed from static configuration - bus/device hierarchy information which can be accessed from static configuration - inter module dependency information based on module attributes. new-bus completely lacks this feature, and depends on oldconfig about this. - mapping information from device name to object file name. new-bus completely lacks this feature, and depends on old config about this. Therefore, FreeBSD eventually will have to choose one of the following candidates: [a] gives up static configuration. But this doesn't solve the following problems: - at least console driver should be linked statically, unless you statically link this, you cannot get the error about dynamic loading critical drivers. :-) - in some applications, static configuration is good enough and dynamic configuration is merely overkill. FreeBSD will not cope with these applications better. Furthermore, this doesn't solves the problems about inter module dependency and mapping information from device name to object filename. [b] uses ugly kluge like hardcoding to solve the problems which already solved by the newconfig cleanly. [c] reinvents features which already implemented on the newconfig. This is exactly NIH problem, and means FreeBSD loses compatibility with *BSDs (FreeBSD becomes non-BSD). Note that newconfig is genuine feature of 4.4BSD, and 4.4BSD red daemon books already said that after the system is completely booted, 4.4BSD (i.e. newconfig) cannot load device drivers.... These problems are all well understood and EASY TO FIX. in page 502. As this shows, it is apparent that newconfig can cope with dynamic configuration, why do new-bus people thought that newconfig cannot deal with dynamic configuration, and reinvent configuration framework? It is obvious that they do not know about newconfig enough, (their terminology like "ivar" shows this fact). [d] shifts the all the problems to users (e.g. see compatibility problem mentioned above) All of above facts are already told to one of the FreeBSD core members, just before core members officialy decided to choose new-bus. I do not know why core members decide new-bus, though. P.S. It seems FreeBSD already start to choose [b]. Please look at changes in revision 1.67 of sys/i386/isa/npx.c. It hardcodes magic number 13, instead of the value gotton from configuration framework. It is interesting that even this doesn't use #define NPXIRQ 13. :-) This reminds me another ugly kluge in sys/pccard/i82365.h: #define PCIC_INDEX_0 0x3E0 #define PCIC_INDEX_1 (PCIC_INDEX_0 + 2) This is the way what some clever FreeBSD people saids "right" to Nakagawa-san, though Nakagawa-san never agreed that it is right, and rather likes the newconfig way like below: pcic0 at isa? port 0x3e0 pcic1 at isa? port 0x3e2 pcic* at pci? pcic* at isapnp? It is apparent which is better and cleaner for me. But perhaps you do not agree with me. :-) -- soda@sra.co.jp Software Research Associates, Inc., Japan (Noriyuki Soda) Advanced Technology Group. 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 Wed May 12 6:43:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 9F35D14CBA for ; Wed, 12 May 1999 06:43:46 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA25596; Wed, 12 May 1999 15:43:43 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id PAA05217; Wed, 12 May 1999 15:43:39 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive In-reply-to: Your message of "12 May 1999 15:37:40 +0200." Date: Wed, 12 May 1999 15:43:38 +0200 Message-ID: <5215.926516618@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just got a 18GB "22GXP" model from IBM and saw the same thing on my -stable box. >start_init: trying /sbin/init >wd0: DMA failure, DMA status 5 >wd0: DMA failure, DMA status 5 >wd0: DMA failure, DMA status 5 >wd0: DMA failure, DMA status 5 -- 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 Wed May 12 6:51:18 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 3EB4C15092 for ; Wed, 12 May 1999 06:51:15 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id PAA51235; Wed, 12 May 1999 15:51:12 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905121351.PAA51235@freebsd.dk> Subject: Re: DMA problems with IBM DeskStar drive In-Reply-To: from Dag-Erling Smorgrav at "May 12, 1999 3:37:40 pm" To: des@yes.no (Dag-Erling Smorgrav) Date: Wed, 12 May 1999 15:51:12 +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 Dag-Erling Smorgrav wrote: > I have a brand new 10 GB IBM UltrStar (DTTA-371010) which is causing > me some pains. If I boot with flags 0x80ff, everything works fine: Hmm, I have one of those, it works wonderfully with my ata driver... So try to use that instead, it should work 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 Wed May 12 6:59:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 0B1D614CBA for ; Wed, 12 May 1999 06:59:39 -0700 (PDT) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id GAA28770; Wed, 12 May 1999 06:59:04 -0700 (PDT) (envelope-from mantar@pacbell.net) Message-Id: <4.2.0.37.19990512065411.00a362c0@216.101.162.50> X-Sender: null@216.101.162.50 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.37 (Beta) Date: Wed, 12 May 1999 06:59:03 -0700 To: Geoff Rehmet , "'current@freebsd.org'" From: Manfred Antar Subject: Re: Today's kernel crashes on starting X In-Reply-To: <3D5EC7D2992BD211A95600A0C9CE047F0308D99F@isjhbex01.is.co.z a> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:35 PM 5/12/99 +0200, Geoff Rehmet wrote: >I'm currently running into a problem, that when I start my system, >it spontaneously reboots when starting X. Has anyone else run into >this? I had the same thing happen last night, after building a new kernel and rebooting. I had to go back to a kernel made yesterday morning to get a working machine. No debugger or anything just automatic reboot. INTEL PR440FX motherboard SMP with DPT controller Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 7: 2:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 56CD915CFF for ; Wed, 12 May 1999 07:02:09 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id QAA25719; Wed, 12 May 1999 16:02:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id QAA05308; Wed, 12 May 1999 16:02:05 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Soren Schmidt Cc: des@yes.no (Dag-Erling Smorgrav), current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive In-reply-to: Your message of "Wed, 12 May 1999 15:51:12 +0200." <199905121351.PAA51235@freebsd.dk> Date: Wed, 12 May 1999 16:02:05 +0200 Message-ID: <5306.926517725@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905121351.PAA51235@freebsd.dk>, Soren Schmidt writes: >It seems Dag-Erling Smorgrav wrote: >> I have a brand new 10 GB IBM UltrStar (DTTA-371010) which is causing >> me some pains. If I boot with flags 0x80ff, everything works fine: > >Hmm, I have one of those, it works wonderfully with my ata driver... >So try to use that instead, it should work then... Try disabling "ultra DMA" in the BIOS, that seems to have worked for me on my IBM-DJNA-371800 drive. (Jordan: We may want to put something in the README about this in 3.2!) -- 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 Wed May 12 7:11:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id 14E3F15D4C for ; Wed, 12 May 1999 07:11:46 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id QAA54928; Wed, 12 May 1999 16:10:11 +0200 (CEST) (envelope-from des) To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive References: <199905121351.PAA51235@freebsd.dk> Organization: Yes! Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 12 May 1999 16:10:11 +0200 In-Reply-To: Soren Schmidt's message of "Wed, 12 May 1999 15:51:12 +0200 (CEST)" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt writes: > Hmm, I have one of those, it works wonderfully with my ata driver... > So try to use that instead, it should work then... I'll try that. OBTW, the following comment in LINT is a little weird: # You only need one "controller ata0" for it to find all # PCI devices on modern machines. DES -- Dag-Erling Smorgrav - des@yes.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 7:14: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id D2C1B15CF6 for ; Wed, 12 May 1999 07:14:02 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id QAA55072; Wed, 12 May 1999 16:10:28 +0200 (CEST) (envelope-from des) To: Poul-Henning Kamp Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive References: <5306.926517725@critter.freebsd.dk> Organization: Yes! Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 12 May 1999 16:10:28 +0200 In-Reply-To: Poul-Henning Kamp's message of "Wed, 12 May 1999 16:02:05 +0200" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > Try disabling "ultra DMA" in the BIOS, that seems to have worked for > me on my IBM-DJNA-371800 drive. Thanks, I'll try that if the ata driver doesn't work. DES -- Dag-Erling Smorgrav - des@yes.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 7:15:53 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 8EC8915CD1 for ; Wed, 12 May 1999 07:15:39 -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 PAA00580; Wed, 12 May 1999 15:15:25 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 12 May 1999 15:15:24 +0100 (BST) From: Doug Rabson To: Daniel Eischen Cc: jb@cimlogic.com.au, current@FreeBSD.ORG Subject: Re: Debugging uthreads In-Reply-To: <199905121035.GAA10411@pcnet1.pcnet.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 Wed, 12 May 1999, Daniel Eischen wrote: > John Birrell wrote: > > Daniel Eischen wrote: > > > Why don't we make a libc_r_db and provide the necessary interfaces to > > > gdb from that instead of having gdb know about uthread internals? > > > > It would still mean that gdb would be linked to the uthread internals > > which may not match the version of libc_r that the 3rd party program > > was linked against. > > OK, but it still seems more appropriate to have uthread debugging > internals known somewhere other than in GDB. It seems more obvious > to have to modify libc_r_db when libc_r changes than to know to > update the gdb sources. > > If threads had versioning information as well as trying to set > certain attributes in stone, then libc_r_db could be made to > be backwards compatible with older thread libraries. GDB's needs are rather simple. It needs to know the current thread, be able to enumerate all threads, and access the saved register set of a non-current thread. I don't want to over-engineer the thing given that writing the gdb side of things was actually pretty simple. -- 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 Wed May 12 7:18:17 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 2DC3D14DCA for ; Wed, 12 May 1999 07:18:11 -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 PAA00584; Wed, 12 May 1999 15:17:59 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 12 May 1999 15:17:59 +0100 (BST) From: Doug Rabson To: John Birrell Cc: current@freebsd.org Subject: Re: Debugging uthreads In-Reply-To: <199905120934.TAA26050@cimlogic.com.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 Wed, 12 May 1999, John Birrell wrote: > Doug Rabson wrote: > > I think the only state which I need to know about is PS_DEAD. If we marked > > dead threads in the public struct it might simplify things. > > You use PS_RUNNING too. We could just tie down those two as PS_DEAD = 0 > and PS_RUNNING = 1. Ah. I thought I had changed that. The use of PS_RUNNING in store_registers is bogus, it should be checking against _thread_run. The whole function get_thread_info is pretty bogus too and it is never called by gdb as far as I can tell. -- 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 Wed May 12 7:41:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from kirk.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id 8F44D15D06 for ; Wed, 12 May 1999 07:41:24 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem15.masternet.it [194.184.65.25]) by kirk.giovannelli.it (8.9.3/8.9.2) with SMTP id OAA01678 for ; Wed, 12 May 1999 14:41:12 GMT (envelope-from gmarco@giovannelli.it) Message-Id: <4.1.19990512161629.00960080@194.184.65.4> X-Sender: gmarco@194.184.65.4 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 12 May 1999 16:39:08 +0200 To: current@freebsd.org From: Gianmarco Giovannelli Subject: panic ! panic ! panic ! Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After make world this morning I received this panic : Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0155ca4 stack pointer = 0x10:0xc6864d64 frame pointer = 0x10:0xc6864d78 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume , IOPL=0 current process = 374 (screen-3.7.6) interrupt mask = tty trap number = 12 panic: page fault I receive this panic with "screen", but before I kept this box resetting itself trying to enter in X... and I was trying Xfree 3.3.3.1 (recompiled and reinstalled) SVGA, Metrolink and Xaccel 5.0 . But I could not seen the panic probably due to X loading. Here are some infos : 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: Wed May 12 13:03:16 CEST 1999 root@gmarco.eclipse.org:/usr/src/sys/compile/GMARCO Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 400911064 Hz CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 127868928 (124872K bytes) Preloaded elf kernel "kernel" at 0xc02ae000. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: CTL00c5 [0xc5008c0e] Serial 0x1a3b72f5 Comp ID: PNPb02f [0x2fb0d041] 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 vga-pci0: irq 11 at device 0.0 on pci1 isab0: at device 4.0 on pci0 chip1: at device 4.1 on pci0 chip2: at device 4.3 on pci0 ahc0: irq 14 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs de0: irq 10 at device 10.0 on pci0 de0: 21041 [10Mb/s] pass 1.1 de0: address 00:40:05:36:7a:72 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 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port de0: enabling 10baseT port Waiting 3 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers changing root device to da0s1a da2 at ahc0 bus 0 target 2 lun 0 da2: Removable Direct Access SCSI-2 device da2: 3.300MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Kernel file : ######## Identification ####### machine "i386" cpu "I686_CPU" ident GMARCO maxusers 32 ######### Misc Options ######## options INET options FFS options NFS options PROCFS options FFS_ROOT options "COMPAT_43" options SCSI_DELAY=3000 options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG options SOFTUPDATES options SYSVSHM options SYSVSEM options SYSVMSG ######### Controllers ########## controller isa0 controller pci0 controller pnp0 ######### Floppy Disk ########### controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 ######### Scsi subsystem ######## controller ahc0 controller scbus0 device da0 device sa0 device cd0 ########## Keyboard and screen ### controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? ######### Fpu #################### device npx0 at nexus? port IO_NPX irq 13 ########## Serials Devs ######### device sio0 at isa? port IO_COM1 irq 4 device sio1 at isa? port IO_COM2 irq 3 ########### Par bus ############### device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 device lpt0 at ppbus? ########### Ether ################# device de0 ########### Luigi's drivers ####### device pcm0 at isa? port 0x220 irq ? drq ? flags 0x15 ########## Misc Device ############## pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip #################################### The box work normally with other tasks, but keep resetting if trying to enter in X or launching screen . Perhaps other things make it reset, but I don't find them till now ... Have I miss some "HEADS UP" ? Is it a fault only mine ? Thanks.... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 7:52:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id 1C85315D76 for ; Wed, 12 May 1999 07:52:00 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem15.masternet.it [194.184.65.25]) by scotty.masternet.it (8.9.3/8.9.2) with SMTP id QAA13949; Wed, 12 May 1999 16:43:48 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990512164034.00963f10@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 12 May 1999 16:41:40 +0200 To: Manfred Antar , Geoff Rehmet , "'current@freebsd.org'" From: Gianmarco Giovannelli Subject: Re: Today's kernel crashes on starting X In-Reply-To: <4.2.0.37.19990512065411.00a362c0@216.101.162.50> References: <3D5EC7D2992BD211A95600A0C9CE047F0308D99F@isjhbex01.is.co.z a> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12/05/99, Manfred Antar wrote: >At 02:35 PM 5/12/99 +0200, Geoff Rehmet wrote: >>I'm currently running into a problem, that when I start my system, >>it spontaneously reboots when starting X. Has anyone else run into >>this? >I had the same thing happen last night, after building a new kernel and >rebooting. >I had to go back to a kernel made yesterday morning to get a >working machine. No debugger or anything just automatic reboot. >INTEL PR440FX motherboard SMP with DPT controller I had the same problem here.... also the program "screen" crashes happily... see my msg subj: panic ! Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 7:54: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from kirk.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id 94C6315D6A for ; Wed, 12 May 1999 07:53:51 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem15.masternet.it [194.184.65.25]) by kirk.giovannelli.it (8.9.3/8.9.2) with SMTP id OAA01697 for ; Wed, 12 May 1999 14:53:46 GMT (envelope-from gmarco@giovannelli.it) Message-Id: <4.1.19990512164444.01268a20@194.184.65.4> X-Sender: gmarco@194.184.65.4 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 12 May 1999 16:51:41 +0200 To: current@freebsd.org From: Gianmarco Giovannelli Subject: Sometimes again SCSI don't finish to boot Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In 4.0-current sometimes the box will froze again after the : "Waiting 3 seconds for SCSI devices to settle" then nothing happens. It was a thing happened also in early 1999, before the branch in 4.0-current and 3.1 stable, if I remember well. Any others experience such behaviour ? Here is again (part of) my infos: FreeBSD 4.0-CURRENT #0: Wed May 12 13:03:16 CEST 1999 root@gmarco.eclipse.org:/usr/src/sys/compile/GMARCO Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 400911064 Hz CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 127868928 (124872K bytes) Preloaded elf kernel "kernel" at 0xc02ae000. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 11 at device 0.0 on pci1 isab0: at device 4.0 on pci0 chip1: at device 4.1 on pci0 chip2: at device 4.3 on pci0 ahc0: irq 14 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs [...] Waiting 3 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers changing root device to da0s1a da2 at ahc0 bus 0 target 2 lun 0 da2: Removable Direct Access SCSI-2 device da2: 3.300MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Kernel file : ######## Identification ####### machine "i386" cpu "I686_CPU" ident GMARCO maxusers 32 ######### Misc Options ######## options INET options FFS options NFS options PROCFS options FFS_ROOT options "COMPAT_43" options SCSI_DELAY=3000 options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG options SOFTUPDATES options SYSVSHM options SYSVSEM options SYSVMSG ######### Controllers ########## controller isa0 controller pci0 controller pnp0 ######### Floppy Disk ########### controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 ######### Scsi subsystem ######## controller ahc0 controller scbus0 device da0 device sa0 device cd0 ########## Keyboard and screen ### controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? ######### Fpu #################### device npx0 at nexus? port IO_NPX irq 13 ########## Serials Devs ######### device sio0 at isa? port IO_COM1 irq 4 device sio1 at isa? port IO_COM2 irq 3 ########### Par bus ############### device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 device lpt0 at ppbus? ########### Ether ################# device de0 ########### Luigi's drivers ####### device pcm0 at isa? port 0x220 irq ? drq ? flags 0x15 ########## Misc Device ############## pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip #################################### Sorry for the double posting of kernel and dmesg file (I also posted in my previous message about crashes). Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 7:56: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id 0B38715D56 for ; Wed, 12 May 1999 07:55:57 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id KAA20307; Wed, 12 May 1999 10:53:33 -0400 (EDT) Message-ID: <003001be9c88$2669b620$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: "Noriyuki Soda" Cc: "Noriyuki Soda" , References: <199905120901.SAA04493@srapc288.sra.co.jp><008501be9c7c$51a38020$d3e4b38c@xyplex.com> <199905121341.WAA22134@srapc342.sra.co.jp> Subject: Re: cvs commit: src/sys/pci pcisupport.c Date: Wed, 12 May 1999 11:00:18 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: Since newconfig appears technically superior, what are the issues that are hindering its acceptance? Rick Whitesel ----- Original Message ----- From: Noriyuki Soda To: Rick Whitesel Cc: Noriyuki Soda ; Sent: Wednesday, May 12, 1999 9:41 AM Subject: Re: cvs commit: src/sys/pci pcisupport.c >>>>> On Wed, 12 May 1999 09:35:36 -0400, "Rick Whitesel" said: > In general I believe that dynamic configuration of the system is > extremely useful to both the development community and the user > community. The development community has a much easier time if they > can load / unload drivers. As for the users, my rule of thumb is > that a computer should never ask a human the answer to a question > that it can find out for itself. I think this is especially true for > configuration information. In addition, the need for dynamic system > (re)configuration will only increase as features like PCI hot swap > become the standard. Of course, I completely agree with you. The reason I prefer newconfig is it actually can support dynamic configuration better than the new-bus. All features which new-bus has can be implemented on newconfig, too. And, more. (See the description about on-demand dynamic loading in my previous post.) Furthremore, newconfig does static configuration better than the new-bus, and newconfig has a option which removes dynamic configuration entirely from kernel. New-bus apparently doesn't have this option. So, which is flexible ? :-) -- soda@sra.co.jp Software Research Associates, Inc., Japan (Noriyuki Soda) Advanced Technology Group. 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 Wed May 12 8: 6:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 4E099152F4 for ; Wed, 12 May 1999 08:05:25 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA12106; Wed, 12 May 1999 11:05:23 -0400 (EDT) (envelope-from luoqi) Date: Wed, 12 May 1999 11:05:23 -0400 (EDT) From: Luoqi Chen Message-Id: <199905121505.LAA12106@lor.watermarkgroup.com> To: current@FreeBSD.ORG, gmarco@giovannelli.it Subject: Re: panic ! panic ! panic ! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After make world this morning I received this panic : > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x14 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0155ca4 > stack pointer = 0x10:0xc6864d64 > frame pointer = 0x10:0xc6864d78 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume , IOPL=0 > current process = 374 (screen-3.7.6) > interrupt mask = tty > trap number = 12 > panic: page fault > > I receive this panic with "screen", but before I kept this box resetting > itself trying to enter in X... and I was trying Xfree 3.3.3.1 (recompiled > and reinstalled) SVGA, Metrolink and Xaccel 5.0 . But I could not seen the > panic probably due to X loading. > Could you show us the symbols around the faulting instruction at 0xc0155ca4? It would be even better if you have a crash dump and the gdb backtrace. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 8: 9:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.NET (sj-dsl-9-161-065.dspeed.net [209.249.161.65]) by hub.freebsd.org (Postfix) with ESMTP id 12E1615B79; Wed, 12 May 1999 08:09:48 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dns.MexComUSA.NET (8.9.3/8.9.1) with ESMTP id IAA88458; Wed, 12 May 1999 08:09:29 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <373999B8.FB2D0990@MexComUSA.net> Date: Wed, 12 May 1999 08:09:44 -0700 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Tomer Weller Cc: freebsd-hardware@FreeBSD.ORG, FreeBSD Current Subject: Re: Scanners References: <99051121261500.00272@Tomer.DrugsAreGood.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tomer Weller wrote: > i got a new UMAX Atrsa 1220P scanner, i have no idea how to configure this in > FreeBSD or Linux (or if i even can), im on 4.0-CURRENT. > ====================================== > 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 Have you tried /usr/ports/graphics/sane? ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 8:13:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from kirk.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id 8AAAD14D8C for ; Wed, 12 May 1999 08:13:46 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem15.masternet.it [194.184.65.25]) by kirk.giovannelli.it (8.9.3/8.9.2) with SMTP id PAA01728; Wed, 12 May 1999 15:13:26 GMT (envelope-from gmarco@giovannelli.it) Message-Id: <4.1.19990512170919.009a20d0@194.184.65.4> X-Sender: gmarco@194.184.65.4 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 12 May 1999 17:11:18 +0200 To: Luoqi Chen From: Gianmarco Giovannelli Subject: Re: panic ! panic ! panic ! Cc: current@freebsd.org In-Reply-To: <199905121505.LAA12106@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12/05/99, you wrote: >> >Could you show us the symbols around the faulting instruction at 0xc0155ca4? >It would be even better if you have a crash dump and the gdb backtrace. Pardon, but I am not be able to figure by myself what you asked to me... If you can explain me step by step in a newbie way I can do everything ... The crashes is easily reproducible... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 8:18: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 421DE14DC1 for ; Wed, 12 May 1999 08:17:56 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id RAA26056; Wed, 12 May 1999 17:17:55 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id RAA05600; Wed, 12 May 1999 17:17:49 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Rick Whitesel" Cc: "Noriyuki Soda" , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Wed, 12 May 1999 11:00:18 EDT." <003001be9c88$2669b620$d3e4b38c@xyplex.com> Date: Wed, 12 May 1999 17:17:49 +0200 Message-ID: <5598.926522269@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <003001be9c88$2669b620$d3e4b38c@xyplex.com>, "Rick Whitesel" writes : >Hi: > Since newconfig appears technically superior, what are the issues that >are hindering its acceptance? That we want to have no "config" at all. -- 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 Wed May 12 8:25:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id B809614C12 for ; Wed, 12 May 1999 08:25:46 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id RAA13872 for ; Wed, 12 May 1999 17:25:45 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 51E85D226; Wed, 12 May 1999 17:25:44 +0200 (CEST) Message-ID: <19990512172544.A440@enst.fr> Date: Wed, 12 May 1999 17:25:44 +0200 From: Pierre Beyssac To: freebsd-current@freebsd.org Subject: mbuf starvation Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to plug some of the holes not checking for mbuf shortage. In particular, there are the following unchecked calls to MGET and friends in /sys/kern/uipc_socket.c:sosend() (see patches below). Would anyone mind if I commit these? I won't be able to commit these before next Sunday evening, so if anyone deems these to be useful, he's welcome to commit before then. Another big problem is that there's a check in m_retry and friends that panics when falling short of mbufs! I really believe this does more harm than good, because it prevents correct calling code (checking for NULL mbuf pointers) from exiting gracefully with ENOBUFS... These could most certainly help with 3.2-RELEASE too. Same problem, I won't be able to do anything more before Sunday. --- uipc_socket.c.orig Wed May 5 16:48:57 1999 +++ uipc_socket.c Wed May 12 16:55:27 1999 @@ -497,15 +497,27 @@ } else do { if (top == 0) { MGETHDR(m, M_WAIT, MT_DATA); + if (m == 0) { + error = ENOBUFS; + goto release; + } mlen = MHLEN; m->m_pkthdr.len = 0; m->m_pkthdr.rcvif = (struct ifnet *)0; } else { MGET(m, M_WAIT, MT_DATA); + if (m == 0) { + error = ENOBUFS; + goto release; + } mlen = MLEN; } if (resid >= MINCLSIZE) { MCLGET(m, M_WAIT); + if (m == 0) { + error = ENOBUFS; + goto release; + } if ((m->m_flags & M_EXT) == 0) goto nopages; mlen = MCLBYTES; @@ -617,6 +629,8 @@ flags = 0; if (flags & MSG_OOB) { m = m_get(M_WAIT, MT_DATA); + if (m == 0) + return (ENOBUFS); error = (*pr->pr_usrreqs->pru_rcvoob)(so, m, flags & MSG_PEEK); if (error) goto bad; --- uipc_mbuf.c.orig Fri Apr 30 12:33:50 1999 +++ uipc_mbuf.c Wed May 12 17:05:02 1999 @@ -263,10 +263,7 @@ if (m != NULL) { mbstat.m_wait++; } else { - if (i == M_DONTWAIT) - mbstat.m_drops++; - else - panic("Out of mbuf clusters"); + mbstat.m_drops++; } return (m); } @@ -291,10 +288,7 @@ if (m != NULL) { mbstat.m_wait++; } else { - if (i == M_DONTWAIT) - mbstat.m_drops++; - else - panic("Out of mbuf clusters"); + mbstat.m_drops++; } return (m); } -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 8:25:57 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 4F58014F3B for ; Wed, 12 May 1999 08:25:49 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id IAA23097; Wed, 12 May 1999 08:25:26 -0700 Date: Wed, 12 May 1999 08:25:25 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Gianmarco Giovannelli Cc: current@FreeBSD.ORG Subject: Re: Sometimes again SCSI don't finish to boot In-Reply-To: <4.1.19990512164444.01268a20@194.184.65.4> 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 > ahc0: irq 14 at device 6.0 on pci0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > [...] > Waiting 3 seconds for SCSI devices to settle > sa0 at ahc0 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 3.300MB/s transfers > changing root device to da0s1a > da2 at ahc0 bus 0 target 2 lun 0 > da2: Removable Direct Access SCSI-2 device > da2: 3.300MB/s transfers > da2: Attempt to query device size failed: NOT READY, Medium not present > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing > Enabled > da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing > Enabled > da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) you've got two Ultra mode devices (disks) on the same bus as a Async mode device (the tape drive). In theory it's possible to mix Ultra and non-ultra devices and I have certainly done so, but you might want to try your setup without the tape drive attached. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 8:42:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id C952615336 for ; Wed, 12 May 1999 08:42:22 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id AAA00575; Thu, 13 May 1999 00:38:26 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: phk@critter.freebsd.dk Cc: rwhitesel@nbase-xyplex.com, soda@sra.co.jp, current@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: cvs commit: src/sys/pci pcisupport.c From: Tomoaki NISHIYAMA In-Reply-To: <5598.926522269@critter.freebsd.dk> References: <5598.926522269@critter.freebsd.dk> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990513003825D.tomoaki@moss.nibb.ac.jp> Date: Thu, 13 May 1999 00:38:25 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 26 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Poul-Henning Kamp Subject: Re: cvs commit: src/sys/pci pcisupport.c Date: Wed, 12 May 1999 17:17:49 +0200 Message-ID: <5598.926522269@critter.freebsd.dk> phk> In message <003001be9c88$2669b620$d3e4b38c@xyplex.com>, "Rick Whitesel" writes phk> : phk> >Hi: phk> > Since newconfig appears technically superior, what are the issues that phk> >are hindering its acceptance? phk> phk> That we want to have no "config" at all. That is too short an answer. What is the definition of "config"? Why do you want to remove it? Newconfig people is in agreement that old config should be removed. But newconfig is a different thing. Newconfig should be satisfactory for the purpose you remove the old config. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 8:45:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.promo.de (mail.Promo.DE [194.45.188.65]) by hub.freebsd.org (Postfix) with ESMTP id A03B314C59 for ; Wed, 12 May 1999 08:44:24 -0700 (PDT) (envelope-from stefan.bethke@hanse.de) Received: from d225.promo.de (d225.Promo.DE [194.45.188.225]) by mail.promo.de (8.8.8/8.8.8) with ESMTP id RAA06808; Wed, 12 May 1999 17:44:10 +0200 (CEST) Date: Wed, 12 May 1999 17:43:27 +0200 From: Stefan Bethke To: Pierre Beyssac Cc: freebsd-current@FreeBSD.ORG Subject: Re: mbuf starvation Message-ID: <803947.3135519807@d225.promo.de> In-Reply-To: <19990512172544.A440@enst.fr> Originator-Info: login-id=stefan; server=mail X-Mailer: Mulberry (MacOS) [1.4.2, s/n U-301178] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pierre Beyssac wrote: > Another big problem is that there's a check in m_retry and friends > that panics when falling short of mbufs! I really believe this does > more harm than good, because it prevents correct calling code > (checking for NULL mbuf pointers) from exiting gracefully with > ENOBUFS... I've discussed this with Garett back in September. The reason is quite simple: unless all cases of not checking for a NULL pointer returned are fixed (or instrumented with a panic), it is better to fail with a panic than with some obscure problem later on. Stefan -- M=FChlendamm 12 | Voice +49-40-256848, +49-177-3504009 D-22089 Hamburg | e-mail: stefan.bethke@hanse.de Germany | stb@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 May 12 8:45:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 13F2115B79 for ; Wed, 12 May 1999 08:45:49 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id RAA26177; Wed, 12 May 1999 17:45:48 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id RAA05758; Wed, 12 May 1999 17:45:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Tomoaki NISHIYAMA Cc: rwhitesel@nbase-xyplex.com, soda@sra.co.jp, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Thu, 13 May 1999 00:38:25 +0900." <19990513003825D.tomoaki@moss.nibb.ac.jp> Date: Wed, 12 May 1999 17:45:45 +0200 Message-ID: <5756.926523945@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >phk> > Since newconfig appears technically superior, what are the issues that >phk> >are hindering its acceptance? >phk> >phk> That we want to have no "config" at all. > >That is too short an answer. No, it is complete and to the point. >What is the definition of "config"? config(8) >Why do you want to remove it? Why should we, as a 3rd millenium OS need a static config tool ? Tell me which future technology we will need to handle which will require static config ? We are working on FreeBSD as a OS for the future, not for the past. -- 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 Wed May 12 8:49:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 9D21315179 for ; Wed, 12 May 1999 08:49:07 -0700 (PDT) (envelope-from geoff@rucus.ru.ac.za) Received: (qmail 78033 invoked by uid 268); 12 May 1999 15:48:54 -0000 Message-ID: <19990512154854.78032.qmail@rucus.ru.ac.za> Subject: Re: panic ! panic ! panic ! In-Reply-To: <199905121505.LAA12106@lor.watermarkgroup.com> from Luoqi Chen at "May 12, 1999 11: 5:23 am" To: luoqi@watermarkgroup.com (Luoqi Chen) Date: Wed, 12 May 1999 17:48:54 +0200 (SAST) Cc: current@freebsd.org Reply-To: "Geoff Rehmet" From: "Geoff Rehmet" 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 Luoqi Chen writes : I'm trying to get a crash dump myself, but the kernel I have right now, is screwing up my keyboard, and I cannot even log in! I will try again. Geoff. > > After make world this morning I received this panic : > > > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0x14 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xc0155ca4 > > stack pointer = 0x10:0xc6864d64 > > frame pointer = 0x10:0xc6864d78 > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL0, pres 1, def32 1, gran 1 > > processor eflags = interrupt enabled, resume , IOPL=0 > > current process = 374 (screen-3.7.6) > > interrupt mask = tty > > trap number = 12 > > panic: page fault > > > > I receive this panic with "screen", but before I kept this box resetting > > itself trying to enter in X... and I was trying Xfree 3.3.3.1 (recompiled > > and reinstalled) SVGA, Metrolink and Xaccel 5.0 . But I could not seen the > > panic probably due to X loading. > > > Could you show us the symbols around the faulting instruction at 0xc0155ca4? > It would be even better if you have a crash dump and the gdb backtrace. > > -lq > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Geoff Rehmet, The Internet Solution geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 8:56: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 4E5EB14FA4 for ; Wed, 12 May 1999 08:56:03 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id RAA26231; Wed, 12 May 1999 17:56:02 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id RAA05819; Wed, 12 May 1999 17:55:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Geoff Rehmet" Cc: luoqi@watermarkgroup.com (Luoqi Chen), current@FreeBSD.ORG Subject: Re: panic ! panic ! panic ! In-reply-to: Your message of "Wed, 12 May 1999 17:48:54 +0200." <19990512154854.78032.qmail@rucus.ru.ac.za> Date: Wed, 12 May 1999 17:55:59 +0200 Message-ID: <5817.926524559@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At least put DDB in your kernel, type "trace" when it panics and tell us what it says. In message <19990512154854.78032.qmail@rucus.ru.ac.za>, "Geoff Rehmet" writes: >Luoqi Chen writes : > >I'm trying to get a crash dump myself, but the kernel I have >right now, is screwing up my keyboard, and I cannot even log >in! >I will try again. > >Geoff. >> > After make world this morning I received this panic : >> > >> > Fatal trap 12: page fault while in kernel mode >> > fault virtual address = 0x14 >> > fault code = supervisor read, page not present >> > instruction pointer = 0x8:0xc0155ca4 >> > stack pointer = 0x10:0xc6864d64 >> > frame pointer = 0x10:0xc6864d78 >> > code segment = base 0x0, limit 0xfffff, type 0x1b >> > = DPL0, pres 1, def32 1, gran 1 >> > processor eflags = interrupt enabled, resume , IOPL=0 >> > current process = 374 (screen-3.7.6) >> > interrupt mask = tty >> > trap number = 12 >> > panic: page fault >> > >> > I receive this panic with "screen", but before I kept this box resetting >> > itself trying to enter in X... and I was trying Xfree 3.3.3.1 (recompiled >> > and reinstalled) SVGA, Metrolink and Xaccel 5.0 . But I could not seen the >> > panic probably due to X loading. >> > >> Could you show us the symbols around the faulting instruction at 0xc0155ca4? >> It would be even better if you have a crash dump and the gdb backtrace. >> >> -lq >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> > > >-- >Geoff Rehmet, >The Internet Solution >geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org >tel: +27-83-292-5800 > > >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 Wed May 12 9: 2:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-spool.is.co.za (mail-spool.is.co.za [196.4.160.4]) by hub.freebsd.org (Postfix) with ESMTP id C430014FA4 for ; Wed, 12 May 1999 09:02:04 -0700 (PDT) (envelope-from geoffr@is.co.za) Received: from admin.is.co.za (admin.is.co.za [196.23.0.9]) by mail-spool.is.co.za (8.8.8/IShub#3) with ESMTP id SAA01454; Wed, 12 May 1999 18:04:49 +0200 Received: from isjhbex01.is.co.za (isjhbex01.is.co.za [196.26.1.16]) by admin.is.co.za (8.8.6/8.7.3/ISsubsidiary#1) with ESMTP id SAA17471; Wed, 12 May 1999 18:02:00 +0200 (GMT) Received: by isjhbex01.is.co.za with Internet Mail Service (5.5.2232.9) id ; Wed, 12 May 1999 17:54:50 +0200 Message-ID: <3D5EC7D2992BD211A95600A0C9CE047F0308D9A5@isjhbex01.is.co.za> From: Geoff Rehmet To: "'Poul-Henning Kamp'" , Geoff Rehmet Cc: luoqi@watermarkgroup.com, current@FreeBSD.ORG Subject: RE: panic ! panic ! panic ! Date: Wed, 12 May 1999 17:54:11 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Only one problem with that - screen and keyboard are not responding when it panics. I'm hoping that I will be able to get a dump which I can look at post mortem. I'm going to try again though. The kernel I have at the moment is totally messing up my keyboard, and I cannot even get a single user login! Geoff. > -----Original Message----- > From: Poul-Henning Kamp [mailto:phk@critter.freebsd.dk] > Sent: 12 May 1999 05:56 > To: Geoff Rehmet > Cc: luoqi@watermarkgroup.com; current@FreeBSD.ORG > Subject: Re: panic ! panic ! panic ! > > > > At least put DDB in your kernel, type "trace" when it > panics and tell us what it says. > > In message <19990512154854.78032.qmail@rucus.ru.ac.za>, > "Geoff Rehmet" writes: > >Luoqi Chen writes : > > > >I'm trying to get a crash dump myself, but the kernel I have > >right now, is screwing up my keyboard, and I cannot even log > >in! > >I will try again. > > > >Geoff. > >> > After make world this morning I received this panic : > >> > > >> > Fatal trap 12: page fault while in kernel mode > >> > fault virtual address = 0x14 > >> > fault code = supervisor read, page not present > >> > instruction pointer = 0x8:0xc0155ca4 > >> > stack pointer = 0x10:0xc6864d64 > >> > frame pointer = 0x10:0xc6864d78 > >> > code segment = base 0x0, limit 0xfffff, type 0x1b > >> > = DPL0, pres 1, def32 1, gran 1 > >> > processor eflags = interrupt enabled, resume , IOPL=0 > >> > current process = 374 (screen-3.7.6) > >> > interrupt mask = tty > >> > trap number = 12 > >> > panic: page fault > >> > > >> > I receive this panic with "screen", but before I kept > this box resetting > >> > itself trying to enter in X... and I was trying Xfree > 3.3.3.1 (recompiled > >> > and reinstalled) SVGA, Metrolink and Xaccel 5.0 . But I > could not seen the > >> > panic probably due to X loading. > >> > > >> Could you show us the symbols around the faulting > instruction at 0xc0155ca4? > >> It would be even better if you have a crash dump and the > gdb backtrace. > >> > >> -lq > >> > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-current" in the body of the message > >> > > > > > >-- > >Geoff Rehmet, > >The Internet Solution > >geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org > >tel: +27-83-292-5800 > > > > > >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 Wed May 12 9: 5: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id C14AE151B7 for ; Wed, 12 May 1999 09:04:59 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id SAA16299; Wed, 12 May 1999 18:04:57 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 61B1ED226; Wed, 12 May 1999 18:04:57 +0200 (CEST) Message-ID: <19990512180457.A2829@enst.fr> Date: Wed, 12 May 1999 18:04:57 +0200 From: Pierre Beyssac To: Stefan Bethke Cc: freebsd-current@FreeBSD.ORG Subject: Re: mbuf starvation References: <19990512172544.A440@enst.fr> <803947.3135519807@d225.promo.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <803947.3135519807@d225.promo.de>; from Stefan Bethke on Wed, May 12, 1999 at 05:43:27PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 12, 1999 at 05:43:27PM +0200, Stefan Bethke wrote: > I've discussed this with Garett back in September. The reason is quite > simple: unless all cases of not checking for a NULL pointer returned are > fixed (or instrumented with a panic), it is better to fail with a panic > than with some obscure problem later on. Yes, I would agree in the general case, but in that particular case the reasonning is flawed: you panic every time, while there are many cases that currently are handled gracefully by the caller. In other words, you don't leave any choice to the caller. That's bad. IHMO it's not even a good thing in general because mbuf starvations can and _will_ happen as a normal condition, not because of bugs but because of high resource use. It can have its uses for debugging purposes, as a compilation option. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 9:19:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 0E19114C14 for ; Wed, 12 May 1999 09:19:42 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id A8FE818D0; Wed, 12 May 1999 18:19:49 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id A61FF49CE; Wed, 12 May 1999 18:19:49 +0200 (CEST) Date: Wed, 12 May 1999 18:19:49 +0200 (CEST) From: Andrzej Bialecki To: Stefan Bethke Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current In-Reply-To: <64131.3135500516@d225.promo.de> 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, 12 May 1999, Stefan Bethke wrote: > Any pointer on Forth literature/web pages would be appreciated, especially > if it's not the ANSI standard (I've looked at it, and it is that: a > standard, not a reference manual or a tutorial). My Forth knowledge is > rather rusty, I realised... last time I remember I was sitting in front of > my Apple II clone about 15 years ago. "Real-Time Forth" could be good for beginners... It's on the web somewhere. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 9:20:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 742FA15233 for ; Wed, 12 May 1999 09:20:19 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id BAA00719; Thu, 13 May 1999 01:16:38 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: phk@critter.freebsd.dk Cc: rwhitesel@nbase-xyplex.com, soda@sra.co.jp, current@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: cvs commit: src/sys/pci pcisupport.c From: Tomoaki NISHIYAMA In-Reply-To: <5756.926523945@critter.freebsd.dk> References: <5756.926523945@critter.freebsd.dk> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990513011637Y.tomoaki@moss.nibb.ac.jp> Date: Thu, 13 May 1999 01:16:37 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Poul-Henning Kamp Subject: Re: cvs commit: src/sys/pci pcisupport.c Date: Wed, 12 May 1999 17:45:45 +0200 Message-ID: <5756.926523945@critter.freebsd.dk> phk> phk> >phk> > Since newconfig appears technically superior, what are the issues that phk> >phk> >are hindering its acceptance? phk> >phk> phk> >phk> That we want to have no "config" at all. phk> > phk> >That is too short an answer. phk> phk> No, it is complete and to the point. phk> phk> >What is the definition of "config"? phk> phk> config(8) phk> phk> >Why do you want to remove it? phk> phk> Why should we, as a 3rd millenium OS need a static config tool ? Newconfig is a *dynamic* configuration tool. Replacing the old config with newconfig is sufficient for your reason to remove config. Why do you refuse newconfig if it is a better framework for dynamic configuration? -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 9:37:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id 0FE7214BF8 for ; Wed, 12 May 1999 09:37:11 -0700 (PDT) (envelope-from soda@sra.co.jp) Received: from srasvf.sra.co.jp (srasvf [133.137.28.2]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id BAA23388; Thu, 13 May 1999 01:33:00 +0900 (JST) Received: from srapc342.sra.co.jp (srapc342 [133.137.28.111]) by srasvf.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id BAA06267; Thu, 13 May 1999 01:32:45 +0859 (JST) Received: (from soda@localhost) by srapc342.sra.co.jp (8.8.8/3.4W-sra) id BAA23027; Thu, 13 May 1999 01:32:56 +0900 (JST) Date: Thu, 13 May 1999 01:32:56 +0900 (JST) Message-Id: <199905121632.BAA23027@srapc342.sra.co.jp> From: Noriyuki Soda To: Poul-Henning Kamp Cc: Tomoaki NISHIYAMA , rwhitesel@nbase-xyplex.com, soda@sra.co.jp, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <5756.926523945@critter.freebsd.dk> References: <19990513003825D.tomoaki@moss.nibb.ac.jp> <5756.926523945@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Wed, 12 May 1999 17:45:45 +0200, Poul-Henning Kamp said: >> What is the definition of "config"? > config(8) >> Why do you want to remove it? > Why should we, as a 3rd millenium OS need a static config tool ? For example, - To specify the drivers which is linked statically to kernel. As I said earlier, you cannot link console driver dynamically, If you do this, you cannot get error message when dynamic linking of the console driver failed. - There should be a way to inform kernel about inter module dependency dynamically. config(8) converts this information to a file which is kernel readable format. - There should be a way to inform kernel about mapping from device name to driver filename dynamically. config(8) converts this information to a file which is kernel readable format. - To achieve better performance in both UP and SMP cases. Proper SMP implementation requires fine grained locking, though this increases performance penalty in UP case. (e.g. Solaris shows this problem.) Thus, the way to specify "options SMP" is needed to use (static) source level and compiler level optimization. This option should automatically select the appropriate sources which is compiled into kernel, according to the source is needed only in UP case, or only in SMP case, or both. This is what oldconfig and newconfig does. The new-bus doesn't have these features. > We are working on FreeBSD as a OS for the future, not for the past. Of course! We never should go back to the age of 1979 (i.e. before 4.0BSD). -- soda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 9:47:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id A2F0E14BF8 for ; Wed, 12 May 1999 09:47:25 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem18.masternet.it [194.184.65.28]) by scotty.masternet.it (8.9.3/8.9.2) with SMTP id SAA02075; Wed, 12 May 1999 18:43:25 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990512182248.009bda80@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 12 May 1999 18:41:15 +0200 To: Poul-Henning Kamp From: Gianmarco Giovannelli Subject: Re: panic ! panic ! panic ! Cc: current@freebsd.org In-Reply-To: <5817.926524559@critter.freebsd.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12/05/99, you wrote: > >At least put DDB in your kernel, type "trace" when it >panics and tell us what it says. Ok... it's a bit long ... (Tell me there isn't a command to write the trace output on a disk :-) After the panic make by "screen" ... >trace Stopped at ttyflush+0x48: movl 0x14(%eax), %eax ttyflush (c025f2a0,3,c02601e0,c025f2a0,80047410) at ttyflush+0x48 ttioctl(c025f2a0,80047410,c6860ee4,3,c6860e20) at ttioctl+0x4a9 ptyioctl(f700,80047410,c6860e04,c01de031,c6860e20,c6860eb0) at spec_ioctl+0x44 spec_vnoperate(c686e20,c6860eb0,c0172821,c6860e20,0) at spec_vnoperate+0x15 ufs_vnoperatespec(c6860e20,0,c0a44cc0,4,c6860f90) at ufs_vnoperatespec+0x15 vn_ioctl(c0a44cc0,80047410,c6860ee4,c5de94a0) at vn_ioctl+0xdd ioctl(c5de94a0,c6860f90,28113874,806df09,8073720) at ioctl+0x1ef syscall(2f,2f,2f,8073720,806df09) at syscall+0x126 Xint0x80_syscall() at Xint 0x80_syscall+0x30 A nightmare ! :-) Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 9:50:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from kirk.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id F361314BF8 for ; Wed, 12 May 1999 09:50:10 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem18.masternet.it [194.184.65.28]) by kirk.giovannelli.it (8.9.3/8.9.2) with SMTP id QAA01846; Wed, 12 May 1999 16:49:40 GMT (envelope-from gmarco@giovannelli.it) Message-Id: <4.1.19990512184348.009b4d70@194.184.65.4> X-Sender: gmarco@194.184.65.4 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 12 May 1999 18:47:32 +0200 To: Luoqi Chen From: Gianmarco Giovannelli Subject: Re: panic ! panic ! panic ! Cc: current@freebsd.org In-Reply-To: <199905121545.LAA12492@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12/05/99, you wrote: >Ok, what I'd like you to do is, run this command, > nm -n /kernel | more >the output is the list of symbols in the kernel sorted by their addresses >(the left-most column), page through the output, find symbols around the >address 0xc0155ca4, and send me those symbol names along with their addresses. c0154d2c T ptrace c0155244 T trace_req c0155250 T stopevent c01552ac t gcc2_compiled. c01552ac T rman_init c015534c T rman_manage_region c0155404 T rman_fini c015549c T rman_reserve_resource c015584c t int_rman_activate_resource c01558a4 T rman_activate_resource c01558bc T rman_await_resource c0155940 t int_rman_deactivate_resource c0155960 T rman_deactivate_resource c0155970 t int_rman_release_resource c0155b18 T rman_release_resource c0155b2c t gcc2_compiled. c0155b2c T soo_read c0155b50 T soo_write c0155b78 T soo_ioctl c0155cd8 T soo_poll c0155cf8 T soo_stat c0155d28 T soo_close c0155d4c t gcc2_compiled. c0155d4c T ipcperm c0155dd8 t gcc2_compiled. c0155dd8 t msginit c0155f3c T msgsys c0155f6c t msg_freehdr c0156010 T msgctl c01561f0 T msgget c015638c T msgsnd c015678c T msgrcv c0156aa0 t gcc2_compiled. c0156aa0 t seminit c0156b38 T semsys c0156b9c T semconfig c0156bfc t semu_alloc c0156cb4 t semundo_adjust c0156da8 t semundo_clear c0156e1c T __semctl c0157398 T semget c01575c4 T semop c0157988 T semexit c0157b00 t gcc2_compiled. c0157b00 t shm_find_segment_by_key but now the kernel is changed because I add options ddb so you are more interested in the old kernel that was up when the crahs happens : This is : c0154084 T shmctl c0154190 t shmget_existing c0154238 t shmget_allocate_segment c015442c T shmget c0154488 T shmsys c01544b8 T shmfork c0154538 T shmexit c0154598 t shminit c01545ec t gcc2_compiled. c01545ec T ttyopen c0154644 T ttyclose c01546c4 T ttyinput c0154df8 t ttyoutput c0154f5c T ttioctl c0155a70 T ttypoll c0155b1c T ttpoll c0155b50 t ttnread c0155b94 T ttywait c0155c34 t ttywflush c0155c5c T ttyflush c0155d68 T termioschars c0155d80 T ttychars c0155d94 T ttyblock c0155dd8 t ttyunblock c0155e1c T ttstart c0155e38 T ttylclose c0155e64 T ttymodem c0155f38 t ttypend c0155fa0 T ttread c0156560 T ttycheckoutq c015660c T ttwrite c01569a0 t ttyrub c0156b3c t ttyrubo c0156b78 t ttyretype c0156c54 t ttyecho c0156ce0 T ttwakeup c0156d30 T ttwwakeup c0156d9c T ttspeedtab c0156dc8 T ttsetwater c0156f40 T ttyinfo c0157100 t proc_compare c01571cc T tputchar c0157224 T ttysleep c0157260 t gcc2_compiled. c0157260 t ttcompatspeedtab c0157290 T ttsetcompat c0157484 T ttcompat c01576e8 t ttcompatgetflags c0157840 t ttcompatsetflags c015797c t ttcompatsetlflags c0157a9c t gcc2_compiled. c0157a9c T ldisc_register and the trace of ddb on panic (new kernel) generated by screen is : >trace Stopped at ttyflush+0x48: movl 0x14(%eax), %eax ttyflush (c025f2a0,3,c02601e0,c025f2a0,80047410) at ttyflush+0x48 ttioctl(c025f2a0,80047410,c6860ee4,3,c6860e20) at ttioctl+0x4a9 ptyioctl(f700,80047410,c6860e04,c01de031,c6860e20,c6860eb0) at spec_ioctl+0x44 spec_vnoperate(c686e20,c6860eb0,c0172821,c6860e20,0) at spec_vnoperate+0x15 ufs_vnoperatespec(c6860e20,0,c0a44cc0,4,c6860f90) at ufs_vnoperatespec+0x15 vn_ioctl(c0a44cc0,80047410,c6860ee4,c5de94a0) at vn_ioctl+0xdd ioctl(c5de94a0,c6860f90,28113874,806df09,8073720) at ioctl+0x1ef syscall(2f,2f,2f,8073720,806df09) at syscall+0x126 Xint0x80_syscall() at Xint 0x80_syscall+0x30 Hope it helps... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 9:57:16 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 7D42A14DF9 for ; Wed, 12 May 1999 09:57:12 -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 MAA00970; Wed, 12 May 1999 12:56:39 -0400 (EDT) (envelope-from wollman) Date: Wed, 12 May 1999 12:56:39 -0400 (EDT) From: Garrett Wollman Message-Id: <199905121656.MAA00970@khavrinen.lcs.mit.edu> To: Pierre Beyssac Cc: freebsd-current@FreeBSD.ORG Subject: mbuf starvation In-Reply-To: <19990512172544.A440@enst.fr> References: <19990512172544.A440@enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Another big problem is that there's a check in m_retry and friends > that panics when falling short of mbufs! I really believe this does > more harm than good, because it prevents correct calling code > (checking for NULL mbuf pointers) from exiting gracefully with > ENOBUFS... I think we need to think a bit more about the right semantics before making such a change. M_WAIT is supposed to mean `I am in process context and don't mind sleeping in order to get an mbuf, but there is too much locking going on inside the network stack to be able to safely sleep without serious risk of deadlock. This is the sort of application which would be ideal for Matt's `asleep' interface. Then, the code could back its way out of any locks and spls, safely wait for sufficient mbufs to be freed, and then retry. Even then, it's still possible to deadlock if one process hogs the entire mbuf pool. It may be necessary to incrementally penalize processes which do so. FWIW, the 4.3 code sleeps in a loop. -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 Wed May 12 10:29:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 542D515DD9 for ; Wed, 12 May 1999 10:28:51 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.1) id KAA32063; Wed, 12 May 1999 10:28:45 -0700 (PDT) (envelope-from obrien) Message-ID: <19990512102845.A32032@nuxi.com> Date: Wed, 12 May 1999 10:28:45 -0700 From: "David O'Brien" To: Edwin Culp , Tomer Weller Cc: FreeBSD Current Subject: Re: Scanners Reply-To: obrien@NUXI.com References: <99051121261500.00272@Tomer.DrugsAreGood.org> <373999B8.FB2D0990@MexComUSA.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <373999B8.FB2D0990@MexComUSA.net>; from Edwin Culp on Wed, May 12, 1999 at 08:09:44AM -0700 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > i got a new UMAX Atrsa 1220P scanner, i have no idea how to configure > > this in FreeBSD or Linux (or if i even can), im on 4.0-CURRENT. ..snip.. > Have you tried /usr/ports/graphics/sane? It doesn't build under 4.0-CURRENT. -- -- David (obrien@NUXI.com -or- obrien@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 May 12 10:34:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 330B914F80 for ; Wed, 12 May 1999 10:34:29 -0700 (PDT) (envelope-from camel@avias.com) Received: from CAMEL (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id VAA02446; Wed, 12 May 1999 21:34:00 +0400 (MSD) (envelope-from camel@avias.com) Date: Wed, 12 May 1999 21:33:14 +0400 From: Ilya Naumov X-Mailer: The Bat! (v1.32) UNREG / CD5BF9353B3B7091 Reply-To: Ilya Naumov X-Priority: 3 (Normal) Message-ID: <18898.990512@avias.com> To: Geoff Rehmet Cc: current@freebsd.org Subject: Re: Today's kernel crashes on starting X In-reply-To: <3D5EC7D2992BD211A95600A0C9CE047F0308D99F@isjhbex01.is.co.za> References: <3D5EC7D2992BD211A95600A0C9CE047F0308D99F@isjhbex01.is.co.za> 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 Hello Geoff, Wednesday, May 12, 1999, 4:35:54 PM, you wrote: GR> I'm currently running into a problem, that when I start my system, GR> it spontaneously reboots when starting X. Has anyone else run into GR> this? yes, i'm experiencing the same problem with today's (May, 12) kernels. Best regards, Ilya mailto:camel@avias.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 10:45: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 E947314C90 for ; Wed, 12 May 1999 10:45:10 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id KAA61714; Wed, 12 May 1999 10:45:06 -0700 (PDT) From: Archie Cobbs Message-Id: <199905121745.KAA61714@bubba.whistle.com> Subject: Re: has the 3.2 branch happened? In-Reply-To: <19990512213344.A64308@clear.co.nz> from Joe Abley at "May 12, 99 09:33:44 pm" To: jabley@clear.co.nz (Joe Abley) Date: Wed, 12 May 1999 10:45:06 -0700 (PDT) Cc: freebsd-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 Joe Abley writes: > (he asked :) As I understand it, 3.2 is simply a release tag on the already existing branch called RELENG_3 (aka 3.1-stable). So there will be no additional branch for 3.2, just a release tag: RELENG_3_2_0 or somesuch. -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 Wed May 12 10:51:23 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 57F7314EA8 for ; Wed, 12 May 1999 10:51:21 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id KAA61736; Wed, 12 May 1999 10:50:42 -0700 (PDT) From: Archie Cobbs Message-Id: <199905121750.KAA61736@bubba.whistle.com> Subject: Re: mbuf starvation In-Reply-To: <19990512172544.A440@enst.fr> from Pierre Beyssac at "May 12, 99 05:25:44 pm" To: beyssac@enst.fr (Pierre Beyssac) Date: Wed, 12 May 1999 10:50:42 -0700 (PDT) Cc: freebsd-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 Pierre Beyssac writes: > if (resid >= MINCLSIZE) { > MCLGET(m, M_WAIT); > + if (m == 0) { > + error = ENOBUFS; > + goto release; > + } > if ((m->m_flags & M_EXT) == 0) > goto nopages; > mlen = MCLBYTES; I think this part of the patch is useless. MCLGET() does not set m to NULL when it fails, it simply doesn't set the M_EXT flag. ...unless things have changed recently. -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 Wed May 12 11:12:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 273CC14FFC for ; Wed, 12 May 1999 11:12:51 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id NAA20472; Wed, 12 May 1999 13:12:06 -0500 (CDT) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id NAA91326; Wed, 12 May 1999 13:12:05 -0500 (CDT) Date: Wed, 12 May 1999 13:12:05 -0500 From: Alan Cox To: Bill Paul Cc: current@freebsd.org Subject: Re: Anybody actually using gigabit ethernet? Message-ID: <19990512131205.A91162@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I bought two of the cards in order to decide whether or not I wanted to use them in my research group's PII cluster. Right now, they're plugged into a 233MHz Pentium Pro and a 400Mhz K6-2 (using an Aladdin V-based board). I did a bunch of NFS testing over the gigabit link last week and didn't see any glitches. The only "problems" that I've seen are (1) the round-trip latency for small UDP packets is at least 50% higher than FastEthernet on the same hardware and (2) the round-trip latency is highly variable. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 11:15:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from pi.yip.org (yip.org [142.154.7.242]) by hub.freebsd.org (Postfix) with ESMTP id 0AA8C14FFC; Wed, 12 May 1999 11:15:14 -0700 (PDT) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.2/8.9.2) with ESMTP id OAA24334; Wed, 12 May 1999 14:15:12 -0400 (EDT) (envelope-from melange@yip.org) Date: Wed, 12 May 1999 14:15:12 -0400 (EDT) From: Bob K X-Sender: melange@localhost To: Christopher Michaels Cc: freebsd-current@freebsd.org Subject: RE: dots in usernames? In-Reply-To: <6C37EE640B78D2118D2F00A0C90FCB4401105899@site2s1> 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 Well, I did some reading through rfc821, and an email address is defined as follows: ::= "@" ::= | ::= | "." ^^^ ! ::= | ::= """ """ ::= "\" | "\" | | ::= | "\" ::= any one of the 128 ASCII characters, but not any or ::= any one of the 128 ASCII characters (no exceptions) ::= "<" | ">" | "(" | ")" | "[" | "]" | "\" | "." | "," | ";" | ":" | "@" """ | the control characters (ASCII codes 0 through 31 inclusive and 127) (the above from ftp://passaic.cs.miami.edu/pub/rfc/rfc821.txt) So if I've interpreted that right, .'s are indeed a legal part of the local-part of email addresses (addresses with dots in 'em are also used in various examples of that rfc); this would say to me that any mailer that can't handle dots in the username should be considered non-RFC compliant. I've bcc:'d freebsd-questions and cc:'d freebsd-current (which I'm not on, btw) as I think the discussion is now headed in that direction. People on -current: Just to recap, adduser (and rmuser) disallow .'s in usernames on FreeBSD-stable; passwd(5) cites that some mailers have problems with dots in usernames. However, they are becoming more common, and are a legal part of rfc821. So what are people's thoughts on allowing that in -current, and if there's no complaints, backporting it to -stable? It seems really really trivial... On Wed, 12 May 1999, Christopher Michaels wrote: > That would be the e-mail message that I had in memory when I sent my reply. > The way I see it, is if you've made the change and nothing's broken then why > not! I think most of the wariness if from an earlier day when dots actually > did break things. Now a days the mail software has to take into account > that there ARE email addresses with dots in them. > > Maybe someone else on this list is better qualified to answer your question > than I am, tho. > > I've noticed that most of the places that I've seen dots in user names are > on Microsoft mail servers and windows NT logins. I personally have never > seen them on a UNIX server. But again, just test it out and see what > breaks, if nothing breaks then I don't see a problem with it. > > -Chris > > Anyone out there want to chime in as to why there shouldn't be dots in user > names? > > > -----Original Message----- > > From: Bob K [SMTP:melange@yip.org] > > Sent: Tuesday, May 11, 1999 6:36 PM > > To: Christopher Michaels > > Cc: freebsd-questions@freebsd.org > > Subject: RE: dots in usernames? > > > > Hmm. I searched freebsd-questions, and all I could come up with was the > > following: > > > > ---- > > Date: Sun, 14 Mar 1999 21:39:39 +1000 > > From: Greg Black > > To: Shawn Ramsey > > Cc: Kelvin , > > freebsd-questions@FreeBSD.ORG > > Subject: Re: Question about login name > > Message-ID: <19990314113940.12057.qmail@alpha.comkey.com.au> > > > > [snip] > > > > It's also worth reading the man page for passwd(5), in > > particular the following partial paragraph: > > > > The login name must never begin with a hyphen (``-''); > > also, it is strongly suggested that neither upper-case > > characters nor dots (``.'') be part of the name, as this > > tends to confuse mailers. > > > > And then ask yourself if you really *need* to use this kind of > > login or if it's just something you'd like. If you don't really > > need it (and there must be very few reasons why you might), you > > would probably be better off not to do it. > > > > -- > > Greg Black > > ---- > > > > I'm just wondering how much of a problem this poses at this point; I'm > > seeing more and more email addresses with dots in the username (not to say > > that just because people do it means it's a good thing ;). Sendmail 8.9.2 > > certainly doesn't mind it, nor does Exim. Is there a list of mailers that > > don't like this? Is there perhaps a more appropriate forum to ask this > > sort of question? > > > > /me really should read manpages more often... > > > > On Tue, 11 May 1999, Christopher Michaels wrote: > > > > > My understanding of the situation is that you don't want dots in the > > > usernames because it tends to confuse mailer programs (mainly). > > > Unfortunately our web proxy isn't being very cooperative at work here > > today > > > and I can't lookup what I'm looking for in the archives. > > > > > > This was a top of discussion maybe a moth ago. > > > > > > -Chris > > > > > > > -----Original Message----- > > > > From: Bob K [SMTP:melange@yip.org] > > > > Sent: Tuesday, May 11, 1999 11:42 AM > > > > To: freebsd-questions@freebsd.org > > > > Subject: Re: dots in usernames? > > > > > > > > On Tue, 11 May 1999, Bob K wrote: > > > > > > > > > > will it break anything? I know I can add an alias; I'm just > > hoping to > > > > > > simplify things for the user in question. I suppose after doing > > that, > > > > a > > > > > > make world & rebuild of any ports using utmp would be in order? > > > > > > > > > > Just realized that a make world would not be in order, since I > > wouldn't > > > > > have changed any actual variables. Also, please cc: me in any > > replies, > > > > as > > > > > I'm not on the list. Thanks! > > > > > > > > Damn, sorry, forgot to mention that it's 3.1-19990323-STABLE. > > > > > > > > melange@yip.org - Mustard gas: The kids love it! > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > melange@yip.org - Mustard gas: The kids love it! > melange@yip.org - Mustard gas: The kids love it! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 11:18:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 2FBD7153D1 for ; Wed, 12 May 1999 11:18:14 -0700 (PDT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.9.3/8.9.3) id UAA39275; Wed, 12 May 1999 20:15:34 +0200 (SAT) (envelope-from reg) Date: Wed, 12 May 1999 20:15:34 +0200 From: Jeremy Lea To: obrien@NUXI.com Cc: Edwin Culp , Tomer Weller , FreeBSD Current Subject: Re: Scanners Message-ID: <19990512201534.A344@shale.csir.co.za> References: <99051121261500.00272@Tomer.DrugsAreGood.org> <373999B8.FB2D0990@MexComUSA.net> <19990512102845.A32032@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990512102845.A32032@nuxi.com>; from David O'Brien on Wed, May 12, 1999 at 10:28:45AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 12, 1999 at 10:28:45AM -0700, David O'Brien wrote: > > > i got a new UMAX Atrsa 1220P scanner, i have no idea how to configure > > > this in FreeBSD or Linux (or if i even can), im on 4.0-CURRENT. > ..snip.. > > > Have you tried /usr/ports/graphics/sane? > > It doesn't build under 4.0-CURRENT. Had to fix this a few days ago anyway... -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand | Never gonna be as big as Jesus, never gonna build a promised land | But that's, that's all right, OK with me..." -Audio Adrenaline diff -urN -x CVS /usr/ports.ref/graphics/sane/patches/patch-01 graphics/sane/patches/patch-01 --- /usr/ports.ref/graphics/sane/patches/patch-01 Sun Dec 6 11:37:28 1998 +++ graphics/sane/patches/patch-01 Wed May 12 19:53:21 1999 @@ -5,7 +5,7 @@ # Use test -z because SunOS4 sh mishandles braces in ${var-val}. # It thinks the first close brace ends the variable substitution. -test -z "$INSTALL_PROGRAM" && INSTALL_PROGRAM='${INSTALL}' -+test -z "$INSTALL_SCRIPT" && INSTALL_PROGRAM='${INSTALL}' ++test -z "$INSTALL_SCRIPT" && INSTALL_SCRIPT='${INSTALL}' test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644' diff -urN -x CVS /usr/ports.ref/graphics/sane/patches/patch-02 graphics/sane/patches/patch-02 --- /usr/ports.ref/graphics/sane/patches/patch-02 Tue May 26 10:17:59 1998 +++ graphics/sane/patches/patch-02 Wed May 12 19:56:24 1999 @@ -9,13 +9,12 @@ # Don't delete any intermediate files. .PRECIOUS: %-s.c %-s.lo %.lo dll-preload.c -@@ -94,16 +94,16 @@ +@@ -94,16 +94,13 @@ file=libsane-$${be}.so.$(V_MAJOR); \ lib=`grep dlname= libsane-$${be}.la | cut -f2 -d"'"`; \ - if test ! -f $${file} -a -n "$${lib}"; then \ +- if test ! -f $${file} -a -n "$${lib}"; then \ - ln -s $${lib} $${file}; \ -+ ln -sf $${lib} $${file}; \ - fi; \ +- fi; \ done rm -f $(libdir)/libsane.a $(libdir)/libsane.so \ $(libdir)/libsane.so.$(V_MAJOR)* diff -urN -x CVS /usr/ports.ref/graphics/sane/patches/patch-03 graphics/sane/patches/patch-03 --- /usr/ports.ref/graphics/sane/patches/patch-03 Wed Sep 16 23:37:56 1998 +++ graphics/sane/patches/patch-03 Wed May 12 19:52:36 1999 @@ -1,12 +0,0 @@ ---- backend/Makefile.in.orig Thu Sep 17 05:03:21 1998 -+++ backend/Makefile.in Thu Sep 17 05:16:13 1998 -@@ -93,9 +93,6 @@ - @list="$(ALL_BACKENDS)"; cd $(libsanedir) && for be in $$list; do \ - file=libsane-$${be}.so.$(V_MAJOR); \ - lib=`grep dlname= libsane-$${be}.la | cut -f2 -d"'"`; \ -- if test ! -f $${file} -a -n "$${lib}"; then \ -- ln -sf $${lib} $${file}; \ -- fi; \ - done - rm -f $(libdir)/libsane.a $(libdir)/libsane.so \ - $(libdir)/libsane.so.$(V_MAJOR)* diff -urN -x CVS /usr/ports.ref/graphics/sane/patches/patch-04 graphics/sane/patches/patch-04 --- /usr/ports.ref/graphics/sane/patches/patch-04 Thu Jan 28 23:31:39 1999 +++ graphics/sane/patches/patch-04 Wed May 12 19:58:04 1999 @@ -17,28 +17,28 @@ *) $echo "$modename: unknown library version type \`$version_type'" 1>&2 echo "Fatal configuration error. See the $PACKAGE docs for more information." 1>&2 ---- ltconfig.orig Tue Nov 24 17:04:26 1998 -+++ ltconfig Tue Nov 24 17:07:35 1998 -@@ -1123,10 +1123,21 @@ +--- ltconfig.orig Sun Nov 22 05:53:55 1998 ++++ ltconfig Wed May 12 19:57:19 1999 +@@ -777,7 +777,7 @@ + ;; + + # FreeBSD 3, at last, uses gcc -shared to do shared libraries. +- freebsd3*) ++ freebsd*) + archive_cmds='$CC -shared -o $lib$libobjs' + hardcode_libdir_flag_spec='-R$libdir' + hardcode_direct=yes +@@ -1123,10 +1123,10 @@ finish_eval='for lib in `ls $libdir/*.ixlibrary 2>/dev/null`; do libname=`$echo "X$lib" | $Xsed -e '\''s%^.*/\([^/]*\)\.ixlibrary$%\1%'\''`; test $rm /sys/libs/${libname}_ixlibrary.a; $show "(cd /sys/libs && $LN_S $lib ${libname}_ixlibrary.a)"; (cd /sys/libs && $LN_S $lib ${libname}_ixlibrary.a) || exit 1; done' ;; -freebsd2* | freebsd3*) -+freebsd2*) - version_type=sunos - library_names_spec='${libname}${release}.so.$versuffix $libname.so' - finish_cmds='PATH="$PATH:/sbin" ldconfig -m $libdir' -+ shlibpath_var=LD_LIBRARY_PATH -+ ;; -+ -+freebsd3* | freebsd4*) +- version_type=sunos ++freebsd*) + version_type=freebsd -+ library_names_spec='${libname}${release}.so.$versuffix $libname.so' -+ if [ $PORTOBJFORMAT = elf ]; then -+ finish_cmds='PATH="\$PATH:/sbin" OBJFORMAT="$PORTOBJFORMAT" ldconfig -m $libdir' -+ else -+ finish_cmds='PATH="\$PATH:/sbin" ldconfig -m $libdir' -+ fi + library_names_spec='${libname}${release}.so.$versuffix $libname.so' +- finish_cmds='PATH="$PATH:/sbin" ldconfig -m $libdir' ++ finish_cmds='PATH="\$PATH:/sbin" OBJFORMAT="'"$PORTOBJFORMAT"'" ldconfig -m $libdir' shlibpath_var=LD_LIBRARY_PATH ;; diff -urN -x CVS /usr/ports.ref/graphics/sane/patches/patch-07 graphics/sane/patches/patch-07 --- /usr/ports.ref/graphics/sane/patches/patch-07 Thu Jan 1 02:00:00 1970 +++ graphics/sane/patches/patch-07 Wed May 12 19:59:31 1999 @@ -0,0 +1,11 @@ +--- backend/abaton.c.orig Wed May 12 19:58:28 1999 ++++ backend/abaton.c Wed May 12 19:59:09 1999 +@@ -1113,7 +1113,7 @@ + + case OPT_Y_RESOLUTION: + if (s->val[OPT_PREVIEW].w || s->val[OPT_RESOLUTION_BIND].w) { +- s->val[OPT_X_RESOLUTION] = *(SANE_Word *)val; ++ s->val[OPT_X_RESOLUTION].w = *(SANE_Word *)val; + if (info) + *info |= SANE_INFO_RELOAD_OPTIONS; + } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 11:24:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 6EE38152E2 for ; Wed, 12 May 1999 11:24:18 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id LAA25988; Wed, 12 May 1999 11:24:16 -0700 (PDT) Date: Wed, 12 May 1999 11:24:16 -0700 (PDT) From: David Wolfskill Message-Id: <199905121824.LAA25988@pau-amma.whistle.com> To: ChrisMic@clientlogic.com, melange@yip.org Subject: RE: dots in usernames? Cc: freebsd-current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Wed, 12 May 1999 14:15:12 -0400 (EDT) >From: Bob K >People on -current: Just to recap, adduser (and rmuser) disallow .'s in >usernames on FreeBSD-stable; passwd(5) cites that some mailers have >problems with dots in usernames. However, they are becoming more common, >and are a legal part of rfc821. So what are people's thoughts on allowing >that in -current, and if there's no complaints, backporting it to -stable? >It seems really really trivial... Syntax for valid mailboxes need not correspond to (but should be a superset of, IMO) syntax for usernames. What's the problem you're trying to solve? Cheers, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 11:24:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 25D1914FFC; Wed, 12 May 1999 11:24:15 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id UAA63962; Wed, 12 May 1999 20:24:12 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id UAA04901; Wed, 12 May 1999 20:24:11 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905121824.UAA04901@greenpeace.grondar.za> To: Wilko Bulte Cc: dfr@nlsystems.com, khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: de driver problem In-Reply-To: Your message of " Wed, 12 May 1999 09:33:06 +0200." <199905120733.JAA09042@yedi.iaf.nl> References: <199905120733.JAA09042@yedi.iaf.nl> Date: Wed, 12 May 1999 20:24:10 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl > Writing Makefile for DynaLoader > ==> Your Makefile has been rebuilt. <== > ==> Please rerun the make command. <== > false > false: not found > *** Error code 1 I periodically see this one reported, and It is always repaired by the reporter making sure their tree is _really_ clean before doing a make world. "Really clean" means "make cleandir" _twice_, and complete removal of the contents of /usr/obj. _Then_ cvsup. I prefer to usr CVS checkout, as it shows all the differences and other turds in my source tree. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 11:33:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 8D30F1532D for ; Wed, 12 May 1999 11:33:04 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id UAA63981; Wed, 12 May 1999 20:33:01 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id UAA05194; Wed, 12 May 1999 20:33:00 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905121833.UAA05194@greenpeace.grondar.za> To: Bob K Cc: Christopher Michaels , freebsd-current@FreeBSD.ORG Subject: Re: dots in usernames? In-Reply-To: Your message of " Wed, 12 May 1999 14:15:12 -0400." References: Date: Wed, 12 May 1999 20:32:59 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob K wrote: > Well, I did some reading through rfc821, and an email address is defined > as follows: Email addresses != Usernames. What this suggests to me is that having an _alias_ (say) Mark.Murray to markmurray in /etc/aliases is OK. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 11:35:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from pi.yip.org (yip.org [142.154.7.242]) by hub.freebsd.org (Postfix) with ESMTP id 79AEB14C7F for ; Wed, 12 May 1999 11:35:50 -0700 (PDT) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.2/8.9.2) with ESMTP id OAA24522; Wed, 12 May 1999 14:35:47 -0400 (EDT) (envelope-from melange@yip.org) Date: Wed, 12 May 1999 14:35:47 -0400 (EDT) From: Bob K X-Sender: melange@localhost To: David Wolfskill Cc: ChrisMic@clientlogic.com, freebsd-current@FreeBSD.ORG Subject: RE: dots in usernames? In-Reply-To: <199905121824.LAA25988@pau-amma.whistle.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 Wed, 12 May 1999, David Wolfskill wrote: > >Date: Wed, 12 May 1999 14:15:12 -0400 (EDT) > >From: Bob K > > >People on -current: Just to recap, adduser (and rmuser) disallow .'s in > >usernames on FreeBSD-stable; passwd(5) cites that some mailers have > >problems with dots in usernames. However, they are becoming more common, > >and are a legal part of rfc821. So what are people's thoughts on allowing > >that in -current, and if there's no complaints, backporting it to -stable? > >It seems really really trivial... > > Syntax for valid mailboxes need not correspond to (but should be a > superset of, IMO) syntax for usernames. > > What's the problem you're trying to solve? I'm hoping to simplify things for my users so that they don't need to have a different email address from their username if they have a dot in the local-part. melange@yip.org - Mustard gas: The kids love it! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 11:41:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 2D77014FCB for ; Wed, 12 May 1999 11:41:02 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id NAA65917; Wed, 12 May 1999 13:40:35 -0500 (CDT) (envelope-from dan) Date: Wed, 12 May 1999 13:40:34 -0500 From: Dan Nelson To: Mark Murray Cc: Bob K , Christopher Michaels , freebsd-current@FreeBSD.ORG Subject: Re: dots in usernames? Message-ID: <19990512134034.A65753@dan.emsphone.com> References: <199905121833.UAA05194@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199905121833.UAA05194@greenpeace.grondar.za>; from "Mark Murray" on Wed May 12 20:32:59 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (May 12), Mark Murray said: > Bob K wrote: > > Well, I did some reading through rfc821, and an email address is > > defined as follows: > > Email addresses != Usernames. What this suggests to me is that having > an _alias_ (say) Mark.Murray to markmurray in /etc/aliases is OK. but, from the chown manpage: COMPATIBILITY Previous versions of the chown utility used the dot (`.') character to distinguish the group name. This has been changed to be a colon (`:') character so that user and group names may contain the dot character. So it sounds like the rest of the system is leaning toward allowing dots in usernames as well. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 11:42:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from pi.yip.org (yip.org [142.154.7.242]) by hub.freebsd.org (Postfix) with ESMTP id 38CCF15225 for ; Wed, 12 May 1999 11:42:23 -0700 (PDT) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.2/8.9.2) with ESMTP id OAA24589; Wed, 12 May 1999 14:42:10 -0400 (EDT) (envelope-from melange@yip.org) Date: Wed, 12 May 1999 14:42:09 -0400 (EDT) From: Bob K X-Sender: melange@localhost To: Mark Murray Cc: Christopher Michaels , freebsd-current@FreeBSD.ORG Subject: Re: dots in usernames? In-Reply-To: <199905121833.UAA05194@greenpeace.grondar.za> 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, 12 May 1999, Mark Murray wrote: > Bob K wrote: > > Well, I did some reading through rfc821, and an email address is defined > > as follows: > > Email addresses != Usernames. What this suggests to me is that having > an _alias_ (say) Mark.Murray to markmurray in /etc/aliases is OK. Sigh. Yes, I know. However, here's the reasoning behind not having dots in usernames according to passwd(5): The login name must never begin with a hyphen (``-''); also, it is strongly suggested that neither upper-case characters nor dots (``.'') be part of the name, as this tends to confuse mailers. ^^^^^^^^^^^^^^^^ Since any mailer that can't handle a dot in an email address that consists of login@host is not compliant with RFC 821, I'm thinking "Hey! Why not make the change?" I've tested it on my -stable system here, and so far there's been no incompatibilities (but then, I only tested a few things: see the original email I sent - which is the point of putting something in -current before stable :) melange@yip.org - Mustard gas: The kids love it! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 11:43: 3 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 B5FAF1530D for ; Wed, 12 May 1999 11:43:01 -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 UAA36364; Wed, 12 May 1999 20:42:50 +0200 (CEST) (envelope-from des) To: NAKAGAWA Yoshihisa Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c References: <199905120327.DAA09999@chandra.eatell.msr.prug.or.jp> From: Dag-Erling Smorgrav Date: 12 May 1999 20:42:49 +0200 In-Reply-To: NAKAGAWA Yoshihisa's message of "Wed, 12 May 1999 12:27:45 +0900" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NAKAGAWA Yoshihisa writes: > > mechanism was unacceptable -- else we would have used it years ago. > It is not formal core decision. On whose authority do you say that? Garrett is a core team member. > > Our policy in all areas has been that we'd rather do the Right Thing > > than follow the crowd. > new-bus is wrong way. You are misunderstanding 4.4BSD mechanism. Then explain to us why newbus is wrong and why the 4.4BSD scheme is right. 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 Wed May 12 11:54:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 22F4814BDB for ; Wed, 12 May 1999 11:54:46 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.3/8.9.0.Beta6) with ESMTP id OAA10047 for ; Wed, 12 May 1999 14:54:37 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.0.Beta6) with SMTP id OAA04894 for ; Wed, 12 May 1999 14:54:37 -0400 (EDT) Received: from localhost by rac1.wam.umd.edu (8.9.3/8.9.0.Beta6) with SMTP id OAA04887 for ; Wed, 12 May 1999 14:54:36 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Wed, 12 May 1999 14:54:36 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: X crashing under current 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 also am experiencing a kernel panic whenever I start X using today's kernel. Thanks Kenneth Culver Computer Science Major at the University of Maryland, College Park. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 12:15:24 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 E6B7414BE1 for ; Wed, 12 May 1999 12:15: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 MAA43938; Wed, 12 May 1999 12:12:54 -0700 (PDT) Date: Wed, 12 May 1999 12:12:54 -0700 (PDT) From: Julian Elischer To: Noriyuki Soda Cc: Rick Whitesel , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905121341.WAA22134@srapc342.sra.co.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 My personal opinion is that static configuration is a subset of dynamic configuration. The eventual aim is to have a kernel which is a very sparse skelaton, with very few services and drivers loaded (in fact possibly none). At boot time, the needed drivers and services are loaded and configured (by the loader possibly). A driver that is already linked in is treated exactly as if it had been loaded, except that the loading is not required.. In this view, a statically linked in module is really just a 'pre-loaded' module. it still needs to be initialised. In this view, config(8) is reduced to being used to specify the preloaded modules (though that may be done after compilation by an external linker/loader) and to specify debugging options. A utility could exist that takes a skelaton kernel, and a specified list of kld modules and creates a composite loadable kernel, in which some modules are already present. I will admit that I have only looked a small amount at the new config that NetBSD uses, but it seemed to me that it produced far too much static information. This infrastucture would be duplicated by a dynamic loading framework. why have two such frameworks? If newconfig has removed all static device framework from the kernel then it is going the way I envision things moving. If it still does what the NetBSD one did when I looked at it, and produces a statically compiled framework of child devices and parent nodes, then that is one of the things we are trying to get away from. julian On Wed, 12 May 1999, Noriyuki Soda wrote: > >>>>> On Wed, 12 May 1999 09:35:36 -0400, > "Rick Whitesel" said: > > > In general I believe that dynamic configuration of the system is > > extremely useful to both the development community and the user > > community. The development community has a much easier time if they > > can load / unload drivers. As for the users, my rule of thumb is > > that a computer should never ask a human the answer to a question > > that it can find out for itself. I think this is especially true for > > configuration information. In addition, the need for dynamic system > > (re)configuration will only increase as features like PCI hot swap > > become the standard. > > Of course, I completely agree with you. > > The reason I prefer newconfig is it actually can support dynamic > configuration better than the new-bus. All features which new-bus has > can be implemented on newconfig, too. And, more. (See the description > about on-demand dynamic loading in my previous post.) > > Furthremore, newconfig does static configuration better than the > new-bus, and newconfig has a option which removes dynamic configuration > entirely from kernel. New-bus apparently doesn't have this option. > > So, which is flexible ? :-) > -- > soda@sra.co.jp Software Research Associates, Inc., Japan > (Noriyuki Soda) Advanced Technology Group. > > > 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 Wed May 12 12:46: 4 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 1D08A153C4 for ; Wed, 12 May 1999 12:45:59 -0700 (PDT) (envelope-from spud@i.am) Received: from Tomer.DrugsAreGood.org (RAS8-p24.hfa.netvision.net.il [62.0.149.152]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id WAA00979; Wed, 12 May 1999 22:45:52 +0300 (IDT) From: Tomer Weller To: Edwin Culp Subject: Re: Scanners Date: Wed, 12 May 1999 20:09:55 +0300 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain Cc: FreeBSD Current References: <373999B8.FB2D0990@MexComUSA.net> MIME-Version: 1.0 Message-Id: <99051220113300.00299@Tomer.DrugsAreGood.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i tried it, i belive it's only for SCSI scanners, my UMAX 1220P is for the parallel port. On Wed, 12 May 1999, Edwin Culp wrote: > Have you tried /usr/ports/graphics/sane? > > ed -- ====================================== 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 Wed May 12 12:54:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from maildns.FSBDial.co.uk (maildns.fsbdial.co.uk [195.89.137.2]) by hub.freebsd.org (Postfix) with ESMTP id 6D99214F0C for ; Wed, 12 May 1999 12:54:31 -0700 (PDT) (envelope-from dlombardo@excite.com) Received: from [212.1.159.186] by maildns.freenet.co.uk (NTMail 4.30.0008/NT0619.00.8ceac940) with ESMTP id oqynfaaa for ; Wed, 12 May 1999 20:50:46 +0100 Message-ID: <3739DE0D.6CADC96E@excite.com> Date: Wed, 12 May 1999 21:01:17 +0100 From: Dean Lombardo Organization: University of Kent at Canterbury X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: Nt source licenses... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ustimenko Semen wrote: > > Hi, > > On Tue, 11 May 1999, Luigi Rizzo wrote: > > > Hi, > > maybe i am the last one in the world to know, but were you guys aware > > of this: > > > > http://research.microsoft.com/programs/NTSrcLicInfo.htm > > > > Microsoft makes Windows NT source code available to universities > > and other "not-for-profit" research institutions at no charge. > > Currently, there are over 55 universities and government agencies > > with source licenses. > > Are we going to get this license? I am interested in NTFS > source code a lot... > > P.S. What's happening with MS? Thanks for the info - I'll try to persuade my Uni to get a license... Shouldn't be much of a problem. :-) If no-one else wants it, I can always request it myself and get a signature of someone at UKC to back it up (or I can always sign "The Dean" :-) Dean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 13:19:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 9810014FCB for ; Wed, 12 May 1999 13:19:17 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA01979; Wed, 12 May 1999 20:56:16 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01226; Wed, 12 May 1999 20:43:45 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905121843.UAA01226@yedi.iaf.nl> Subject: Re: Sometimes again SCSI don't finish to boot In-Reply-To: <4.1.19990512164444.01268a20@194.184.65.4> from Gianmarco Giovannelli at "May 12, 1999 4:51:41 pm" To: gmarco@giovannelli.it (Gianmarco Giovannelli) Date: Wed, 12 May 1999 20:43:45 +0200 (CEST) Cc: current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Gianmarco Giovannelli wrote ... > > In 4.0-current sometimes the box will froze again after the : > "Waiting 3 seconds for SCSI devices to settle" > then nothing happens. > It was a thing happened also in early 1999, before the branch in > 4.0-current and 3.1 stable, if I remember well. > > Any others experience such behaviour ? > Here is again (part of) my infos: > > FreeBSD 4.0-CURRENT #0: Wed May 12 13:03:16 CEST 1999 > root@gmarco.eclipse.org:/usr/src/sys/compile/GMARCO > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 400911064 Hz > CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x651 Stepping=1 > Features=0x183f9ff PAT,PSE36,MMX,FXSR> > real memory = 134217728 (131072K bytes) > avail memory = 127868928 (124872K bytes) > Preloaded elf kernel "kernel" at 0xc02ae000. > Pentium Pro MTRR support enabled, default memory type is uncacheable > Probing for PnP devices: > pcib0: on motherboard > pci0: on pcib0 > chip0: at device 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vga-pci0: irq 11 at device 0.0 on pci1 > isab0: at device 4.0 on pci0 > chip1: at device 4.1 on pci0 > chip2: at device 4.3 on pci0 > ahc0: irq 14 at device 6.0 on pci0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > [...] > Waiting 3 seconds for SCSI devices to settle > sa0 at ahc0 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 3.300MB/s transfers > changing root device to da0s1a > da2 at ahc0 bus 0 target 2 lun 0 > da2: Removable Direct Access SCSI-2 device Have you tried this without the ZIP drive? I've heared from people they sometimes cause grief. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 13:19:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id DFC2314FCB for ; Wed, 12 May 1999 13:19:17 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA01976; Wed, 12 May 1999 20:56:15 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA00838; Wed, 12 May 1999 20:04:00 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905121804.UAA00838@yedi.iaf.nl> Subject: Re: Nt source licenses... In-Reply-To: from "erik@habatech.no" at "May 12, 1999 2:59:10 pm" To: erik@habatech.no Date: Wed, 12 May 1999 20:04:00 +0200 (CEST) Cc: semen@iclub.nsu.ru, current@FreeBSD.ORG, luigi@labinfo.iet.unipi.it X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As erik@habatech.no wrote ... > > On 12-May-99 Ustimenko Semen wrote: > > > > Are we going to get this license? I am interested in NTFS > > source code a lot... > > > > P.S. What's happening with MS? > > > They have got a virus. I think they're calling it Open Source... Na... it's called US Dept of Justice I guess ;-) > They're fighting really hard to get rid of it, but these things can happen > from time to time :) Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 13:34:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C503F14C21 for ; Wed, 12 May 1999 13:34:17 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA88116; Wed, 12 May 1999 13:34:05 -0700 (PDT) (envelope-from dillon) Date: Wed, 12 May 1999 13:34:05 -0700 (PDT) From: Matthew Dillon Message-Id: <199905122034.NAA88116@apollo.backplane.com> To: Garrett Wollman Cc: Pierre Beyssac , freebsd-current@FreeBSD.ORG Subject: Re: mbuf starvation References: <19990512172544.A440@enst.fr> <199905121656.MAA00970@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I think we need to think a bit more about the right semantics before :making such a change. M_WAIT is supposed to mean `I am in process :context and don't mind sleeping in order to get an mbuf, but there is :too much locking going on inside the network stack to be able to :safely sleep without serious risk of deadlock. : :This is the sort of application which would be ideal for Matt's :`asleep' interface. Then, the code could back its way out of any :locks and spls, safely wait for sufficient mbufs to be freed, and then :retry. Even then, it's still possible to deadlock if one process hogs :the entire mbuf pool. It may be necessary to incrementally penalize :processes which do so. : :FWIW, the 4.3 code sleeps in a loop. : :-GAWollman Doing something like this is exactly what was intented for asleep(). The code is not entirely complete, though. Basically the idea is to use asleep() in situations where the system might block but does not normally block in order to avoid both deadlocks and unnecessary code serialization ( due to holding a lock through a blocking situation ). This becomes critically important in SMP models where most of the locks you hold are spinlocks rather then scheduler locks. asleep() allows a subroutine deep in the call stack to specify an asynchronous blocking condition and then return a temporary failure up through the ranks. At the top level, the scheduler sees and acts upon the asynchronous blocking condition. Higher level routines do not need to understand what condition is being blocked on, only that there is some condition being blocked on. With the current model, higher level routines have to assume that lower level routines may block which complicates matters greatly. -Matt Matthew Dillon :-- :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 : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 13:48: 0 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 49B92154AF; Wed, 12 May 1999 13:47:59 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA65762; Wed, 12 May 1999 13:48:02 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: nik@freebsd.org Cc: current@freebsd.org Subject: Someone blew up the handbook again. Date: Wed, 12 May 1999 13:48:02 -0700 Message-ID: <65758.926542082@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /usr/local/bin/jade -V html-manifest -ioutput.html -c /usr/doc/share/sgml/catal og -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sg ml/docbook/3.0/catalog -c /usr/local/share/sgml/jade/catalog -d /usr/doc/share/ sgml/freebsd.dsl -t sgml handbook.sgml /usr/local/bin/jade:install/chapter.sgml:279:13:E: character data is not allowed Should I just turn NODOC on for the -current snapshot builds? The problem is that I'm not getting *any* -current (or releng3, for that matter) snapshots out at releng3.freebsd.org and current.freebsd.org because on the days when src isn't broken, the handbook is and that kills the builds just as effectively. :-( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 13:48: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id EE2C7153FF; Wed, 12 May 1999 13:47:39 -0700 (PDT) (envelope-from rgrimes@gndrsh.aac.dev.com) Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.9.3/8.9.3) id NAA03768; Wed, 12 May 1999 13:44:30 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199905122044.NAA03768@gndrsh.aac.dev.com> Subject: Re: de driver problem In-Reply-To: <199905121824.UAA04901@greenpeace.grondar.za> from Mark Murray at "May 12, 1999 08:24:10 pm" To: mark@grondar.za (Mark Murray) Date: Wed, 12 May 1999 13:44:30 -0700 (PDT) Cc: wilko@yedi.iaf.nl (Wilko Bulte), dfr@nlsystems.com, khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, 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 > Wilko Bulte wrote: > > PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl > > Writing Makefile for DynaLoader > > ==> Your Makefile has been rebuilt. <== > > ==> Please rerun the make command. <== > > false > > false: not found > > *** Error code 1 > > I periodically see this one reported, and It is always repaired > by the reporter making sure their tree is _really_ clean before > doing a make world. "Really clean" means "make cleandir" _twice_, This indicates to me, the original author of ``cleandir'', that something has broken the functionality that it had. This something is more than likely the removal of code similiar to: cd /usr/obj/{.CURDIR}; chflags -R noschg tmp; rm -rf *; before the equiv of: cd {.CURDIR}; ${make} clean > and complete removal of the contents of /usr/obj. _Then_ cvsup. > I prefer to usr CVS checkout, as it shows all the differences and > other turds in my source tree. If ``make cleandir'' is leaving some cruft in any form behind anyplace in the build tree things are broken. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 13:48:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 287731550F for ; Wed, 12 May 1999 13:48:35 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA88350; Wed, 12 May 1999 13:48:13 -0700 (PDT) (envelope-from dillon) Date: Wed, 12 May 1999 13:48:13 -0700 (PDT) From: Matthew Dillon Message-Id: <199905122048.NAA88350@apollo.backplane.com> To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: problem with dev_t changes and pageout.. References: <19990511222604.172D71F73@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe whoever committed the supposedly innocuous dev_t changes should back it out. Just a thought. -Matt Matthew Dillon : :It looks like something has come unstuck: : :Fatal trap 12: page fault while in kernel mode :mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 :fault virtual address = 0x28 :fault code = supervisor read, page not present :instruction pointer = 0x8:0xc017bb67 :stack pointer = 0x10:0xc5d97de4 :frame pointer = 0x10:0xc5d97df0 :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 = 2 (pagedaemon) :interrupt mask = net bio cam <- SMP: XXX :kernel: type 12 trap, code=0 :Stopped at spec_strategy+0x93: movl 0x28(%edx),%eax : ^^^^^^^^^^^ %edx = null :db> trace :spec_strategy(c5d97e1c) at spec_strategy+0x93 :swap_pager_putpages(c02904fc,c5d97ecc,2,0,c5d97e60) at swap_pager_putpages+0x3e1 :default_pager_putpages(c02904fc,c5d97ecc,2,0,c5d97e60) at default_pager_putpages+0x17 :vm_pageout_flush(c5d97ecc,2,0,c5d97eb0,c02182cf) at vm_pageout_flush+0x91 :vm_pageout_clean(c04d6b60,80000000,c013e290,2000,c5d97f78) at vm_pageout_clean+0x1f1 :vm_pageout_scan(80000000,c02789c0,c02789c0,c5d97fac,c013e2c3) at vm_pageout_scan+0x45e :vm_pageout(c5d8fdf7,c0255500,c02789c0,c020c640,c020c748) at vm_pageout+0x221 :kproc_start(c02789c0) at kproc_start+0x33 :fork_trampoline(10b8a0,d88e0000,18b8c08e,8e000000,24448be0) at fork_trampoline+0x30 :db> ps : pid proc addr uid ppid pgrp flag stat wmesg wchan cmd : 438 c680da40 c6818000 495 282 277 000004 3 biord c332d9c0 p4d : 437 c5d8c340 c6802000 433 417 415 004084 3 piperd c6760660 tee : 436 c680dd00 c6810000 433 417 415 004004 3 biord c33626f8 p4 : 418 c680dba0 c6815000 433 415 415 004084 3 piperd c6760700 mail : 417 c680de60 c680e000 433 415 415 004084 3 wait c680de60 sh :[..] : :The offending line in spec_strategy is: : (*bdevsw(bp->b_dev)->d_strategy)(bp); : :d_strategy was null.. I'm still looking. : :(I think this is the first time the box paged out since booting a few hours :ago, it's got 128M, but p4d has got a lot of stuff to deal with and can hit :a vsize of 70MB or so.) : :Cheers, :-Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 13:48:43 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 466C815E23 for ; Wed, 12 May 1999 13:48:40 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id QAA72725 for current@freebsd.org; Wed, 12 May 1999 16:48:39 -0400 (EDT) (envelope-from mi) Message-Id: <199905122048.QAA72725@misha.cisco.com> Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: from Dag-Erling Smorgrav at "May 12, 1999 08:42:49 pm" To: current@freebsd.org Date: Wed, 12 May 1999 16:48:39 -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 Dag-Erling Smorgrav once wrote: As an outside observer, who does not understand most (all?) of the differences involved, I must say, this will have to be an unfairly "uphill" explanation. Because, using the style exemplified by PHK today, the newconfig people could say something like: > Then explain to us why newbus is wrong * newbus is too far in the future and too dynamic (as opposed to PHK's statement, the (new)config is too old and too static -- no details) > and why the 4.4BSD scheme is right. * newconfig(8) (as opposed to PHK's ``config(8)'') "We want the FreeBSD to keep the stability and ... it has today". I'm not arguing with PHK here (nor anyone else), I'm just saying the brevity is not always a virtue... And for me, who reads -current mostly to keep the grip on the FreeBSD's directions and currents (hey!), this brief responses are NOT informative at all. Should they be? I'm not sure, but usually people taking a stand try to make themselves clear to all/most of the audience... Another mailing came through today was a lot more informative, though... Perhaps, the newbus vs. newconfig discussion can be summarized to both sides' satisfaction offline and then presented to the rest of the world? Or, the core team may just say: "Because we said so" (which I think was already done once) and stop discussing this... Respectfully, -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 13:59: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 446F41504D; Wed, 12 May 1999 13:58:43 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA64286; Wed, 12 May 1999 22:58:41 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id WAA05984; Wed, 12 May 1999 22:58:37 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905122058.WAA05984@greenpeace.grondar.za> To: "Jordan K. Hubbard" Cc: nik@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Someone blew up the handbook again. In-Reply-To: Your message of " Wed, 12 May 1999 13:48:02 MST." <65758.926542082@zippy.cdrom.com> References: <65758.926542082@zippy.cdrom.com> Date: Wed, 12 May 1999 22:58:34 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > Should I just turn NODOC on for the -current snapshot builds? The problem > is that I'm not getting *any* -current (or releng3, for that matter) > snapshots out at releng3.freebsd.org and current.freebsd.org because > on the days when src isn't broken, the handbook is and that kills the > builds just as effectively. :-( Freeze the bastard as well :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 14: 5:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id 4CF3B1504D for ; Wed, 12 May 1999 14:05:45 -0700 (PDT) (envelope-from soda@sra.co.jp) Received: from srasvf.sra.co.jp (srasvf [133.137.28.2]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id GAA01682; Thu, 13 May 1999 06:05:41 +0900 (JST) Received: from srapc342.sra.co.jp (srapc342 [133.137.28.111]) by srasvf.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id GAA08139; Thu, 13 May 1999 06:05:23 +0900 (JST) Received: (from soda@localhost) by srapc342.sra.co.jp (8.8.8/3.4W-sra) id GAA00338; Thu, 13 May 1999 06:05:34 +0900 (JST) Date: Thu, 13 May 1999 06:05:34 +0900 (JST) Message-Id: <199905122105.GAA00338@srapc342.sra.co.jp> From: Noriyuki Soda To: Julian Elischer Cc: Noriyuki Soda , Rick Whitesel , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: References: <199905121341.WAA22134@srapc342.sra.co.jp> Mime-Version: 1.0 (generated by tm-edit 7.47) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Wed, 12 May 1999 12:12:54 -0700 (PDT), Julian Elischer said: > The eventual aim is to have a kernel which is a very sparse skelaton, > with very few services and drivers loaded (in fact possibly none). This is also aim of newconfig, although console driver should be linked statically at least. Also, newconfig is aiming to provide freedom to choose whether a driver is linked dynamically or statically. > At boot time, the needed drivers and services are loaded and configured > (by the loader possibly). A driver that is already linked in is treated > exactly as if it had been loaded, except that the loading is not > required.. In this view, a statically linked in module is really just a > 'pre-loaded' module. it still needs to be initialised. Yes. This is what newconfig on dynamic configuration does. But SYSINIT() of drivers is NOP in newconfig. Configuration framework does know all necessary operation to do, thus, there is nothing to do in SYSINIT(). Note that this is one of the key points to achieve best match policy for driver selection. > In this view, config(8) is reduced to being used to specify the preloaded > modules (though that may be done after compilation by an external > linker/loader) and to specify debugging options. A utility could exist > that takes a skelaton kernel, and a specified list of kld modules and > creates a composite loadable kernel, in which some modules are already > present. These modules should be specified by device name, or by feature name (i.e. attributes), oldconfig and newconfig use this model. But new-bus doesn't. It doesn't use device name and doesn't have the feature like the attributes of old/newconfig. It merely uses modules' filenames to specify modules which should be linked. This is one of the points what I think the new-bus is wrong. All configuration information should be specified by specification (device names and attribute names), not implementation (module filename). This is critical point to achieve on-demand dynamic loading and better compatibility. > I will admit that I have only looked a small amount at the new config that > NetBSD uses, but it seemed to me that it produced far too much static > information. IMHO, that's wrong. What newconfig produces is only what really needed. If you think there is unnecessary information, probably it means that you don't really understand the usage of the information, yet. > This infrastucture would be duplicated by a dynamic loading framework. This is wrong. The newconfig uses same information and same framework on both static and dynamic configuration. There is no duplication. > why have two such frameworks? No. The newconfig is unified framework for both static and dynamic configuration. If a driver is static configurated, it's "struct cfdata" is generated by config(8), and it will be parsed by configuration framework (kern/subr_autconf.c). If a driver is dynamically configured, then kernel generated "struct cfdata" is used instead. Thus, there is no duplicated information between static and dynamic configuration in newconfig. Both configurations use same "struct cfdata". The only difference is whether the generator of "struct cfdata" is config(8) or kernel. Do you call this duplication? Then you might not really understand what the configuration is, yet. Only config(8) reads "files" file (i.e. meta information) and it converts the information to binary format for kernel. So, there is no duplication about meta information parser. Yes, there is duplication about parser of configuration hint. But if you imagined that there is no need to implement the parser of configuration hint on userland. Then that's completely wrong. If config(8) doesn't have the parser of configuration hint, then you cannot determine which modules should be linked statically. The reason why new-bus doesn't have this duplication is new-bus doesn't have static configuration ability and it depends on oldconfig about static configuration. Actually, the one which has two framework is not newconfig, but new-bus. New-bus have it's own configuration framework for dynamic configuration and depends on oldconfig framework for static configuration. These frameworks are completely different, and as soon as you'd like to remove oldconfig, real problem of new-bus appears. As I said earlier, eventually new-bus will have to choose one of the following ways: [a] gives up static configuration. [b] uses ugly kluge (e.g. oldconfig remains forever). [c] reinvents features which already implemented on the newconfig. I'm not sure which is the way of the new-bus, in this point, though. > If newconfig has removed all static device framework from the kernel then > it is going the way I envision things moving. If it still does what the > NetBSD one did when I looked at it, and produces a statically compiled > framework of child devices and parent nodes, then that is one of the > things we are trying to get away from. This is completely misunderstanding. The "struct cfdata" can be generated via both static and dynamic way. There is no "static device framework" in newconfig from the first since 4.4BSD. Note that the structure of the parent vector and locator vector are changed from NetBSD's format. But this is well known problem (cgd already mentioned this several years ago), and doesn't affect any device drivers. Only configuration engine (kern/subr_autoconf.c) should be slightly modified. And it is quite trivial. This is what 4.4BSD red daemon book said that "all well understood and easy to fix". Do you deny this description of the daemon book ? -- soda@sra.co.jp Software Research Associates, Inc., Japan (Noriyuki Soda) Advanced Technology Group. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 14:21:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from tardis.perspectives.net (unknown [63.66.225.69]) by hub.freebsd.org (Postfix) with ESMTP id 4813A14CB4 for ; Wed, 12 May 1999 14:21:30 -0700 (PDT) (envelope-from jerry.alexandratos@perspectives.net) Received: from localhost ([127.0.0.1] helo=tardis.perspectives.net) by tardis.perspectives.net with esmtp (Exim 2.12 #1) id 10hgR0-000AyG-00; Wed, 12 May 1999 17:20:58 -0400 To: mi@aldan.algebra.com Cc: current@freebsd.org Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: Message from Mikhail Teterin of "Wed, 12 May 1999 16:48:39 EDT." <199905122048.QAA72725@misha.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <42168.926544057.1@tardis.perspectives.net> Date: Wed, 12 May 1999 17:20:57 -0400 From: Jerry Alexandratos Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin says: : : Perhaps, the newbus vs. newconfig discussion can be summarized to both : sides' satisfaction offline and then presented to the rest of the world? But didn't this already happen. I seem to recall a round of discussions that went on a week before the new-bus switch. The entire discussion ran around in circles with both sides discussing the technical merits of their implementation and both sides pointing out the problems in the other's implementation. Check the archives for the all the messages. My personal opinion? Well, I've been looking at the newconfig stuff and I think that they weakened their cause by not following -current. I've been trying the stuff out since they announced. But it does me no good to try and use it if it's out of sync with userland. Hey, I don't feel like looking at "proc size mismatch" messages. 8) I think the real shame is that both sides have good ideas and a lot of the newconfig stuff could work with newbus. However, instead of pooling our resources we've divided them and drawn a line in the sand. And I can't say that I personally feel that all of the questioning e-mails that have been going around the past day make me any more sympathetic to the newconfig cause. Core made a decision. Let's follow it. And before anyone throws any of that "it's not traditional" stuff out, please remember that no other BSD is using a boot loader like ours, NetBSD dropped Mach-VM for UVM, etc, etc, etc... My real fear is that this causes a rift which will lead to a split like the Net/OpenBSD one. At that point, both sides lose. --Jerry name: Jerry Alexandratos || Open-Source software isn't a phone: 302.521.1018 || matter of life or death... email: jalexand@perspectives.net || ...It's much more important || than that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 14:24:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id B01A315275 for ; Wed, 12 May 1999 14:24:11 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40371>; Thu, 13 May 1999 07:09:13 +1000 Date: Thu, 13 May 1999 07:24:03 +1000 From: Peter Jeremy Subject: Re: Nt source licenses... To: semen@iclub.nsu.ru Cc: current@FreeBSD.ORG Message-Id: <99May13.070913est.40371@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ustimenko Semen wrote: >On Tue, 11 May 1999, Luigi Rizzo wrote: ... >> http://research.microsoft.com/programs/NTSrcLicInfo.htm >> >> Microsoft makes Windows NT source code available to universities >> and other "not-for-profit" research institutions at no charge. ... >P.S. What's happening with MS? Could be that someone at M$ has been studying the history of Unix. I'm not sure it'll work though - NT is somewhat more complex (and presumably more difficult to understand) than Sixth Edition Unix. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 14:31:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 57B2514C42 for ; Wed, 12 May 1999 14:31:15 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id OAA14094; Wed, 12 May 1999 14:28:28 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199905122128.OAA14094@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy Cc: semen@iclub.nsu.ru, current@FreeBSD.ORG Subject: Re: Nt source licenses... In-reply-to: Your message of "Thu, 13 May 1999 07:24:03 +1000." <99May13.070913est.40371@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 1999 14:28:28 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG MS is trying desperatly to fight off and contained Linux and I am not sure that Microsoft will succeed -- Amancio Hasty hasty@star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 14:32:25 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 B6BE014DD4 for ; Wed, 12 May 1999 14:32:23 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA65951; Wed, 12 May 1999 14:27:53 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Poul-Henning Kamp Cc: Soren Schmidt , des@yes.no (Dag-Erling Smorgrav), current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive In-reply-to: Your message of "Wed, 12 May 1999 16:02:05 +0200." <5306.926517725@critter.freebsd.dk> Date: Wed, 12 May 1999 14:27:53 -0700 Message-ID: <65947.926544473@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Try disabling "ultra DMA" in the BIOS, that seems to have worked for > me on my IBM-DJNA-371800 drive. > > (Jordan: We may want to put something in the README about this in 3.2!) I'd welcome suggestions as to what the text should look like; I'm still unclear as to what exactly the problem us. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 14:43:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 6F7AA14BE0 for ; Wed, 12 May 1999 14:43:04 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id XAA27586; Wed, 12 May 1999 23:43:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id XAA07210; Wed, 12 May 1999 23:42:55 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: problem with dev_t changes and pageout.. In-reply-to: Your message of "Wed, 12 May 1999 13:48:13 PDT." <199905122048.NAA88350@apollo.backplane.com> Date: Wed, 12 May 1999 23:42:55 +0200 Message-ID: <7208.926545375@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe everybody should read to the end of their mailboxes before they come forward with baseless and unfounded snide remarks. And I never said they were "innocuous". This is Current mind you. Poul-Henning In message <199905122048.NAA88350@apollo.backplane.com>, Matthew Dillon writes: > Maybe whoever committed the supposedly innocuous dev_t changes should > back it out. > > Just a thought. > > -Matt > Matthew Dillon > >: >:It looks like something has come unstuck: >: >:Fatal trap 12: page fault while in kernel mode >:mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 >:fault virtual address = 0x28 >:fault code = supervisor read, page not present >:instruction pointer = 0x8:0xc017bb67 >:stack pointer = 0x10:0xc5d97de4 >:frame pointer = 0x10:0xc5d97df0 >: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 = 2 (pagedaemon) >:interrupt mask = net bio cam <- SMP: XXX >:kernel: type 12 trap, code=0 >:Stopped at spec_strategy+0x93: movl 0x28(%edx),%eax >: ^^^^^^^^^^^ %edx = null >:db> trace >:spec_strategy(c5d97e1c) at spec_strategy+0x93 >:swap_pager_putpages(c02904fc,c5d97ecc,2,0,c5d97e60) at swap_pager_putpages+0x3e1 >:default_pager_putpages(c02904fc,c5d97ecc,2,0,c5d97e60) at default_pager_putpages+0x17 >:vm_pageout_flush(c5d97ecc,2,0,c5d97eb0,c02182cf) at vm_pageout_flush+0x91 >:vm_pageout_clean(c04d6b60,80000000,c013e290,2000,c5d97f78) at vm_pageout_clean+0x1f1 >:vm_pageout_scan(80000000,c02789c0,c02789c0,c5d97fac,c013e2c3) at vm_pageout_scan+0x45e >:vm_pageout(c5d8fdf7,c0255500,c02789c0,c020c640,c020c748) at vm_pageout+0x221 >:kproc_start(c02789c0) at kproc_start+0x33 >:fork_trampoline(10b8a0,d88e0000,18b8c08e,8e000000,24448be0) at fork_trampoline+0x30 >:db> ps >: pid proc addr uid ppid pgrp flag stat wmesg wchan cmd >: 438 c680da40 c6818000 495 282 277 000004 3 biord c332d9c0 p4d >: 437 c5d8c340 c6802000 433 417 415 004084 3 piperd c6760660 tee >: 436 c680dd00 c6810000 433 417 415 004004 3 biord c33626f8 p4 >: 418 c680dba0 c6815000 433 415 415 004084 3 piperd c6760700 mail >: 417 c680de60 c680e000 433 415 415 004084 3 wait c680de60 sh >:[..] >: >:The offending line in spec_strategy is: >: (*bdevsw(bp->b_dev)->d_strategy)(bp); >: >:d_strategy was null.. I'm still looking. >: >:(I think this is the first time the box paged out since booting a few hours >:ago, it's got 128M, but p4d has got a lot of stuff to deal with and can hit >:a vsize of 70MB or so.) >: >:Cheers, >:-Peter > > > >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 Wed May 12 14:44: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id BA67214BE0 for ; Wed, 12 May 1999 14:44:05 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id XAA27592; Wed, 12 May 1999 23:44:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id XAA07221; Wed, 12 May 1999 23:44:01 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Wed, 12 May 1999 16:48:39 EDT." <199905122048.QAA72725@misha.cisco.com> Date: Wed, 12 May 1999 23:44:01 +0200 Message-ID: <7219.926545441@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905122048.QAA72725@misha.cisco.com>, Mikhail Teterin writes: >Or, the core team may just say: "Because we said so" (which I think was >already done once) and stop discussing this... We did I think. -- 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 Wed May 12 14:45:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 6FF2A14D25 for ; Wed, 12 May 1999 14:45:54 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id XAA27614; Wed, 12 May 1999 23:45:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id XAA07257; Wed, 12 May 1999 23:45:50 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jordan K. Hubbard" Cc: Soren Schmidt , des@yes.no (Dag-Erling Smorgrav), current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive In-reply-to: Your message of "Wed, 12 May 1999 14:27:53 PDT." <65947.926544473@zippy.cdrom.com> Date: Wed, 12 May 1999 23:45:50 +0200 Message-ID: <7255.926545550@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <65947.926544473@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> Try disabling "ultra DMA" in the BIOS, that seems to have worked for >> me on my IBM-DJNA-371800 drive. >> >> (Jordan: We may want to put something in the README about this in 3.2!) > >I'd welcome suggestions as to what the text should look like; I'm >still unclear as to what exactly the problem us. :) So am I. I think the problem is that the wd.c based DMA stuff doesn't support ultra-DMA, and unless you tell your BIOS to no do ultra-DMA it will barf up a printf for each transfer to the device. How to write things like this in a README file has repeatedly been proven to be beyond my capabilities. -- 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 Wed May 12 14:53:45 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 76B3214F54 for ; Wed, 12 May 1999 14:53:41 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA66047; Wed, 12 May 1999 14:53:31 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Noriyuki Soda Cc: dfr@nlsystems.com, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Wed, 12 May 1999 18:26:45 +0900." <199905120926.SAA19601@srapc342.sra.co.jp> Date: Wed, 12 May 1999 14:53:31 -0700 Message-ID: <66043.926546011@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I agree that this is better way to solve the conflicts between new-bus > and newconfig. Although I wondered why FreeBSD's core decide to choose > new-bus before Usenix. We didn't choose it "before USENIX" as if it were somehow part of the objective to get this feature in before a public event, it simply came up that Peter had the time to actually integrate new-bus from the Alpha platform to the x86 and it was deemed desirable to have the SAME bus configuration code for both architectures. I don't see how any engineer in his right mind could argue that it made sense to have two, active and shipping ports to different architectures, each with its own bus code. Whether new-bus or newconfig is "better" was really, honestly not the issue so much as were the following two bullet points: 1. Does this bring the alpha and x86 architecture ports into better alignment so that any future permutations can be more easily brought across and/or simply shared between the two platforms? 2. Have we had a good history of communications between the people doing new-bus vs our history of communication with the newconfig people? The latter point is actually *really important* since we've already learned that having totally separate groups who talk to us maybe once a month (if even that often) is just not a workable strategy for the long term and often causes more confusion for our users than it actually helps the project. We talk to Doug Rabson on a practically daily basis on a wide variety of issues whereas the only real communication I've seen from you has been during this conflict. Before that, I had no idea that a Noriyuki Soda even existed. :-) This project essentially lives and dies by the strength of its "ties" to various developers. Given the fact that one body of code came from someone whom I *knew* we could work with, given a long history of working with them, and the other body of code came from someone who really only became known to myself and the rest of core when we saw your paper submission for USENIX (which I'm looking forward to attending, as I'm sure are many others in this discussion), well, it really wasn't a hard decision to make at all. Given the same set of factors, we'd make the very same decision today. To try and put it another way, I've seen a lot of arguing about the technical merits of the two systems but very little arguing about how to solve the HUMAN FACTORS aspect of this situation which are really and truly what led up to the core team's decision. I've also called for greater communication between the two groups and so far all I've seen is a lot of arguing and expressions of general annoyance from Japan - that is NOT communication! Proper communication involves regular discussion about incremental improvements to the code base and how best to carry them out, biting off problems in small chunks and dealing with each completely before moving on to the next. Simply wandering off with the entire problem for 6 months and working on it in isolation DOES NOT WORK and we've proven this again and again. It only leads precisely to the situation we have here now with newconfig and also PAO. To put the problem in a larger context, people often ask me what all the FreeBSD people in Japan are working on and it's a point of eternal embarassment to me that I usually have to say "I honestly have no idea." Many of the various developers in Japan really don't go much out of their way to let me or core in general know what's going on (though there are some notable exceptions) and it's like working in a company where a major part of it is entirely off-site and never calls you on the phone; anyone who's actually worked in such an environment knows exactly what I'm talking about and can appreciate the frustration of not knowing what a good chunk of your organization is up to. We really really really need to fix this if we're to avoid further repetitions of this kind of thing and that's why I'm flying to Tokyo at the end of this month to talk with you guys - we're clearly not communicating adequately and I'm willing to do what I can, including physically relocating myself on a periodic basis, to fix it from this side. What are you doing to fix it on yours? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 15: 2:51 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 9AC5E15086 for ; Wed, 12 May 1999 15:02:43 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA66109; Wed, 12 May 1999 15:02:18 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Gianmarco Giovannelli Cc: Luoqi Chen , current@FreeBSD.ORG Subject: Re: panic ! panic ! panic ! In-reply-to: Your message of "Wed, 12 May 1999 17:11:18 +0200." <4.1.19990512170919.009a20d0@194.184.65.4> Date: Wed, 12 May 1999 15:02:18 -0700 Message-ID: <66106.926546538@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Pardon, but I am not be able to figure by myself what you asked to me... > If you can explain me step by step in a newbie way I can do everything ... > The crashes is easily reproducible... No offense, but are you sure you should even be running -current? A certain amount of skill in doing such diagnosis is generally considered mandatory for people running it, even though many people who shouldn't be doing so for that reason still do it. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 15: 8:52 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 74D1F15086 for ; Wed, 12 May 1999 15:08:50 -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 PAA01488; Wed, 12 May 1999 15:03:06 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905122203.PAA01488@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Gary Jennejohn Cc: Poul-Henning Kamp , freebsd-current@freebsd.org, garyj@peedub.muc.de Subject: Re: the new config and booting In-reply-to: Your message of "Wed, 12 May 1999 10:17:26 +0200." <199905120817.KAA03605@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 1999 15:03:06 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > no, it's a "dangerously dedicated" SCSI disk. That's never a good start. > the loader shows the floppy as DISK A and the SCSI disk as DISK B. Are you sure it lists the SCSI disk as B and not C? If it's showing up as B your BIOS is doing funny stuff. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 15:10:35 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 8D3FD14F54 for ; Wed, 12 May 1999 15:10:33 -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 PAA01534; Wed, 12 May 1999 15:09:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905122209.PAA01534@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Noriyuki Soda Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Wed, 12 May 1999 18:01:35 +0900." <199905120901.SAA04493@srapc288.sra.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 1999 15:09:05 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > NOTE: Please Cc: soda@sra.co.jp, I am not subscribing this mailing > list, because I am a NetBSD user. :-) > > > > It depends on old-config, so poor mechanism. newconfig already > > > implimented best match probe/attach. > > > > And a very useful mechanism it is. Which is why I implemented priority > > ordered probes in -current. > > Hmm, I thought this cannot be done correctly on new-bus, because > the new-bus kicks match/attach routine from SYSINIT(). It is apparent > that this fails in dynamic configuration case, because a potencial > candidate of drivers which is dynamically loaded first always matches. > This behaviour can not be called as "best match", but "first match". :-) > Of course, dynamic configuration of newconfig solves this problem. It would appear that you don't understand the problem, as no configuration technique can telepathically determine in advance which new drivers you are going to load. > BTW, there are many fundamental design flaws in new-bus, so I don't > think new-bus is comparable with newconfig, yet, even if priority > probe is implemented. For example: > > - newconfig can cope with both static configuration and dynamic > configuration. new-bus can handle dynamic configuration only. > > This is because critical information for configuration is > represented in C source internally. e.g. The bus/device > hierarchy information is embedded in DRIVER_MODULE() on > new-bus. > On newconfig, such information is represented externally > in "files" file. Thus the information can be used in > both static and dynamic configuration case. > As a result, newconfig can support same configuration > syntax in both static and dynamic configuration, > the new-bus never can do it. This is actually a major defect in the newconfig design; if the kernel doesn't already know about a device when it is built, it can never support it. > The way on new-bus will cause compatibility problem when > OS is upgraded, because the implementation (filename) may > be changed between versions and versions. This is a transient implementation issue, the obsolecesnce of which is already manifest in the plans that have been laid for a device identifier to module to file lookup with the translation data _outside_ the kernel. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 15:15:44 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 2F175153C4 for ; Wed, 12 May 1999 15:15:36 -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 PAA52113; Wed, 12 May 1999 15:13:54 -0700 (PDT) Date: Wed, 12 May 1999 15:13:53 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: problem with dev_t changes and pageout.. In-Reply-To: <199905122048.NAA88350@apollo.backplane.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 now now :-) On Wed, 12 May 1999, Matthew Dillon wrote: > Maybe whoever committed the supposedly innocuous dev_t changes should > back it out. > > Just a thought. > > -Matt > Matthew Dillon > > : > :It looks like something has come unstuck: > : > :Fatal trap 12: page fault while in kernel mode > :mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 > :fault virtual address = 0x28 > :fault code = supervisor read, page not present > :instruction pointer = 0x8:0xc017bb67 > :stack pointer = 0x10:0xc5d97de4 > :frame pointer = 0x10:0xc5d97df0 > :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 = 2 (pagedaemon) > :interrupt mask = net bio cam <- SMP: XXX > :kernel: type 12 trap, code=0 > :Stopped at spec_strategy+0x93: movl 0x28(%edx),%eax > : ^^^^^^^^^^^ %edx = null > :db> trace > :spec_strategy(c5d97e1c) at spec_strategy+0x93 > :swap_pager_putpages(c02904fc,c5d97ecc,2,0,c5d97e60) at swap_pager_putpages+0x3e1 > :default_pager_putpages(c02904fc,c5d97ecc,2,0,c5d97e60) at default_pager_putpages+0x17 > :vm_pageout_flush(c5d97ecc,2,0,c5d97eb0,c02182cf) at vm_pageout_flush+0x91 > :vm_pageout_clean(c04d6b60,80000000,c013e290,2000,c5d97f78) at vm_pageout_clean+0x1f1 > :vm_pageout_scan(80000000,c02789c0,c02789c0,c5d97fac,c013e2c3) at vm_pageout_scan+0x45e > :vm_pageout(c5d8fdf7,c0255500,c02789c0,c020c640,c020c748) at vm_pageout+0x221 > :kproc_start(c02789c0) at kproc_start+0x33 > :fork_trampoline(10b8a0,d88e0000,18b8c08e,8e000000,24448be0) at fork_trampoline+0x30 > :db> ps > : pid proc addr uid ppid pgrp flag stat wmesg wchan cmd > : 438 c680da40 c6818000 495 282 277 000004 3 biord c332d9c0 p4d > : 437 c5d8c340 c6802000 433 417 415 004084 3 piperd c6760660 tee > : 436 c680dd00 c6810000 433 417 415 004004 3 biord c33626f8 p4 > : 418 c680dba0 c6815000 433 415 415 004084 3 piperd c6760700 mail > : 417 c680de60 c680e000 433 415 415 004084 3 wait c680de60 sh > :[..] > : > :The offending line in spec_strategy is: > : (*bdevsw(bp->b_dev)->d_strategy)(bp); > : > :d_strategy was null.. I'm still looking. > : > :(I think this is the first time the box paged out since booting a few hours > :ago, it's got 128M, but p4d has got a lot of stuff to deal with and can hit > :a vsize of 70MB or so.) > : > :Cheers, > :-Peter > > > > 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 Wed May 12 15:24:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id EA4DC153C4 for ; Wed, 12 May 1999 15:24:16 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id E2DDA1F58; Thu, 13 May 1999 06:24:12 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Noriyuki Soda Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Wed, 12 May 1999 18:01:35 +0900." <199905120901.SAA04493@srapc288.sra.co.jp> Date: Thu, 13 May 1999 06:24:12 +0800 From: Peter Wemm Message-Id: <19990512222414.E2DDA1F58@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Noriyuki Soda wrote: > NOTE: Please Cc: soda@sra.co.jp, I am not subscribing this mailing > list, because I am a NetBSD user. :-) Aha! Now a few things are starting to make sense... > > > It depends on old-config, so poor mechanism. newconfig already > > > implimented best match probe/attach. > > > > And a very useful mechanism it is. Which is why I implemented priority > > ordered probes in -current. > > Hmm, I thought this cannot be done correctly on new-bus, because > the new-bus kicks match/attach routine from SYSINIT(). It is apparent This has *never* been the case. All that the SYSINIT() system is used for is *registering* the drivers with the configuration engine. The actual configuration happens much later, in the i386 case the initial configuration is run from root_bus_configure() in i386/autoconf.c. > that this fails in dynamic configuration case, because a potencial > candidate of drivers which is dynamically loaded first always matches. > This behaviour can not be called as "best match", but "first match". :-) > Of course, dynamic configuration of newconfig solves this problem. > > Was this behaviour of the new-bus changed in -current ? Yes. Originally, the new-bus routines, apon finding a device, would "offer" it to the child drivers one at a time, and the first one that succeeded it's probe would then have it allocated to it. Now it uses a priority mechanism and the best-match driver wins. > BTW, there are many fundamental design flaws in new-bus, so I don't > think new-bus is comparable with newconfig, yet, even if priority > probe is implemented. For example: > > - newconfig can cope with both static configuration and dynamic > configuration. new-bus can handle dynamic configuration only. > > This is because critical information for configuration is > represented in C source internally. e.g. The bus/device > hierarchy information is embedded in DRIVER_MODULE() on > new-bus. > On newconfig, such information is represented externally > in "files" file. Thus the information can be used in > both static and dynamic configuration case. > As a result, newconfig can support same configuration > syntax in both static and dynamic configuration, > the new-bus never can do it. Obviously there is some confusion over terminology or some misunderstanding somewhere, because we have been through this what seems like at least half a dozen times in private mail, and got nowhere at all. It seems to me that the basic difference is: We do not *want* static hardcoded configuration to be compiled into the kernel if at all possible. That requires kernel recompiles to simply change things like a port number for a ne2000 clone card. At the moment, our interim code means that things like 'ed0 goes at port 0x300, irq 11' etc is compiled in via the hints table, but we want that moved out into /boot/isa.conf or something like that ASAP and have loader(8) preload it for the kernel. That means that changing the configuration of a statically compiled kernel does not require a recompile or reconfigure. Most (but not all) of the mechanisms are in place to have this done totally dynamically from loader. For example, if you put this in your kernel config file: device ed0 in -current, you can then add this to /boot/userconfig_script: port ed0 0x300 irq ed0 11 iomem ed0 0xd0000 .. and when the kernel boots, it will probe for ed0 on the isa bus, as well as attach to pci devices. (I have not actually tried this, I do not expect problems though). Abusing userconfig for this is a bit horrible though and is limited in it's capabilities. Everything else is in 4.0-current dynamic. Yes, there are weaknesses still, but that is because it isn't quite finished and is evolving still. As an example, it is not possible to hardwire (for example) de4 on some particular pci slot. This is an implementation problem, not a design problem. isa uses the mechanism already, and pci could too if anybody wanted it enough to write a handful of lines of code. > - new-bus cannot support on-demand device driver loading, > dynamic configuration for newconfig can do it, though. > > This is because new-bus doesn't have the way to represent meta > information like a mapping from device name to driver filename. > If new-bus have this, there is no need to specifiy > "kldload if_fxp", but just say "I need fxp0", then configuration > framework can automatically load fxp driver, if it is not > loaded yet. This is how configuration works in both newconfig > and even oldconfig (look at static kernel configuration file > for oldconfig, there is the line "device fxp0" which demands > fxp driver to be loaded). File names shouldn't be in the kernel. You should not have to precompile a kernel to know that 'if_fxp' is loadable for some pci device id.. how can you do this with a 3rd party binary driver? For what it's worth, I *hate* the newconfig way: ==== 2) To load/unload drivers, in /dev directory, do mknod config c 80 0 For example, to load `ne3 at pci0 dev ? func ?', do, dconfig --load --driver=ne --unit=3 --bus=pci --busunit=0 \ --locator=-1,-1 --flags=0 To unload, dconfig --unload --driver=ne --unit=3 --bus=pci --busunit=0 \ --locator=-1,-1 --flags=0 To load/unload `ne4 at isa0 iobase 0x280 irq 9' do, dconfig --load --driver=ne --unit=4 --bus=isa --busunit=0 \ --locator=640,0,0,0,9,-1,-1,0,1,0 --flags=0 dconfig --unload --driver=ne --unit=4 --bus=isa --busunit=0 --locator=640,0,0,0,9,-1,-1,0,1,0 --flags=0 ==== What on earth is the locator stuff for? Why can't you use plain text? How does 'iobase 0x280' become '640,0,0,0,9,-1,-1,0,1,0'?? > - new-bus heavily depends on oldconfig which is known to be obsolete > and machine dependent (look at usr.sbin/config/config.y, there are Machine dependent? The only thing machine dependent about config(8) is that for the "alpha" machine, it uses files.alpha, while for "i386", it uses "files.i386". There is *NOTHING LEFT* that is machine dependent. > many definitions which depends on ISA bus, e.g. PORT, IOMEM, IOSIZE, > ... newconfig can defines such attributes dynamically on demand.), > and lacks many features which newconfig already has. > > e.g. > - configruration hint which can be accessed from > static configuration We already do this, from the ioconf.c on a recent build: struct config_resource fdc0_resources[] = { { "at", RES_STRING, { (long)"isa" }}, { "port", RES_INT, { IO_FD1 }}, { "drq", RES_INT, { 2 }}, { "irq", RES_INT, { 6 }}, }; #define fdc0_count 4 This is a bit of a hack at the moment and is just used to initialize the runtime resource database where the hints are kept. > - bus/device hierarchy information which can be accessed > from static configuration This is not required to be in a config program, the drivers know it. > All of above facts are already told to one of the FreeBSD core > members, just before core members officialy decided to choose new-bus. > I do not know why core members decide new-bus, though. config.new was rejected years ago. The 4.4BSD config.new was static, device/bus/etc relationships were compiled into the kernel statically and not extendable. I realize you are busy rewriting config.new into newconfig and dconfig, but those are *not* 4.4BSD any more. > It seems FreeBSD already start to choose [b]. Please look at changes > in revision 1.67 of sys/i386/isa/npx.c. It hardcodes magic number 13, > instead of the value gotton from configuration framework. It is > interesting that even this doesn't use #define NPXIRQ 13. :-) Since it seems to bother you so much, I will add the four missing lines of code should somebody wish to break PC compatability. > This reminds me another ugly kluge in sys/pccard/i82365.h: > #define PCIC_INDEX_0 0x3E0 > #define PCIC_INDEX_1 (PCIC_INDEX_0 + 2) > This is the way what some clever FreeBSD people saids "right" to > Nakagawa-san, though Nakagawa-san never agreed that it is right, and > rather likes the newconfig way like below: > pcic0 at isa? port 0x3e0 > pcic1 at isa? port 0x3e2 > pcic* at pci? > pcic* at isapnp? > It is apparent which is better and cleaner for me. But perhaps you do > not agree with me. :-) I prefer just: device pcic0 at isa? port 0x3e0 device pcic1 at isa? port 0x3e2 in a static kernel config file, or: pcic0 port 0x3e0 pcic1 port 0x3e2 in /boot/isa.conf. Or: # sethint pcic0 at isa port 0x3e0 # sethint pcic1 at isa port 0x3e2 # kldload pcic.ko .. to load pcic to look at isapnp, pci and those two isa ports. or: # kldload pcic.ko .. to load pcic and look at pci and isapnp if present. If the driver writer decides there is a significant amount of code in bus dependent modules that it is worth splitting pcic.ko itno pcic_isa.ko, pcic_pci.ko, pcic_pnp.ko and pcic_common.ko, then this works best: # kldload pcic_pci.ko .. to load the pci and common parts, and cause a reprobe. Note that loader(8) looks at the bios PNP and PCI lists and will likely use a table to preload likely drivers based on the device id's it's found. This won't be perfect since loader(8) won't easily be able to run the match routines from the .ko files in the pre-kernel execution environment, but newconfig wouldn't be able to do this either since the newconfig match routines are compiled into the drivers too. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 15:36: 1 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 10930153C4 for ; Wed, 12 May 1999 15:35:59 -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 PAA01663; Wed, 12 May 1999 15:29:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905122229.PAA01663@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Noriyuki Soda Cc: Poul-Henning Kamp , Tomoaki NISHIYAMA , rwhitesel@nbase-xyplex.com, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Thu, 13 May 1999 01:32:56 +0900." <199905121632.BAA23027@srapc342.sra.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 1999 15:29:52 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Why should we, as a 3rd millenium OS need a static config tool ? > > For example, > > - To specify the drivers which is linked statically to kernel. > As I said earlier, you cannot link console driver dynamically, > If you do this, you cannot get error message when dynamic > linking of the console driver failed. This presumes you don't have a fallback console driver. If you look at the current console driver architecture, you'll see that it's not too difficult to do this, nor would it be too difficult to componentise the various console driver components and simply link-time aggregate them. > - There should be a way to inform kernel about inter module dependency > dynamically. config(8) converts this information to a file which is > kernel readable format. This is _the_ fundamental defect (as opposed to merely shortcoming) with newconfig. If I want to use a vendor-supplied driver module, I must first generate a kernel that knows about it. This is not "dynamic" by any definition of the word. KLD should (but does not, yet) obtain this information from the module as it is loaded. This is not a flaw in the KLD design, only its implementation. > - There should be a way to inform kernel about mapping from device > name to driver filename dynamically. config(8) converts this > information to a file which is kernel readable format. This is a task for a PnP ID:module mapping database. See eg. sys/boot/common/pnpdata. It should most definitely _not_ be inside the kernel. > - To achieve better performance in both UP and SMP cases. > Proper SMP implementation requires fine grained locking, though this > increases performance penalty in UP case. (e.g. Solaris shows this > problem.) Thus, the way to specify "options SMP" is needed to use > (static) source level and compiler level optimization. > This option should automatically select the appropriate sources > which is compiled into kernel, according to the source is needed > only in UP case, or only in SMP case, or both. This is what > oldconfig and newconfig does. This is, again, defective reasoning. For a usable dynamic architecture, loadable modules need to be compiled to support both UP and SMP architectures simultaneously. Thus the locking primitives need to be conditionalised at _runtime_. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 15:43:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (Postfix) with ESMTP id 92F6814C14 for ; Wed, 12 May 1999 15:43:49 -0700 (PDT) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id AAA11182; Thu, 13 May 1999 00:36:18 +0200 (CEST) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199905122236.AAA11182@ocean.campus.luth.se> Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905122209.PAA01534@dingo.cdrom.com> from Mike Smith at "May 12, 99 03:09:05 pm" To: mike@smith.net.au (Mike Smith) Date: Thu, 13 May 1999 00:36:18 +0200 (CEST) Cc: soda@sra.co.jp, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 According to Mike Smith: > This is actually a major defect in the newconfig design; if the kernel > doesn't already know about a device when it is built, it can never > support it. That would be so lovely, with a DEVFS too: Plug your Cool card into your pcmcia slot, and get the message on the sytem console that an unknown pcmcia card called "Cool", made by CoolMakers, Inc. Damn... not even a generic driver wanted this card. Pull the card out and go for the web: # ftp ftp.a.cool.thing.com ftp> get cool.tgz --> Downloading file. ftp> quit --> Good bye. # install_driver cool.tgz --> Adding driver to driver database, and installing /modules/cool.ko! And at this point the kernel has not loaded the driver, but just been told there's a new driver around and for what cards and vendors it works, etc. This is done by a library call, or something, which does adds the driver to the database, and a syscall to update the kernel's already loaded database, or to get it to reload the database. Plug the card in again, and the kernel loads in cool.ko and probes the card, and created a /dev/cool, and everything works just fine. No reboot, no recompile, nada. *purr* /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 15:52:39 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 5C9AF14BFF for ; Wed, 12 May 1999 15:52:36 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.2/8.9.1) id SAA73553 for current@freebsd.org; Wed, 12 May 1999 18:52:36 -0400 (EDT) (envelope-from mi) Message-Id: <199905122252.SAA73553@misha.cisco.com> Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905122229.PAA01663@dingo.cdrom.com> from Mike Smith at "May 12, 1999 03:29:52 pm" To: current@freebsd.org Date: Wed, 12 May 1999 18:52:36 -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 Mike Smith once wrote: > For a usable dynamic architecture, loadable modules need to be > compiled to support both UP and SMP architectures simultaneously. Thus > the locking primitives need to be conditionalised at _runtime_. What about kldload /modules/up/whatever.ko and kldload /modules/smp/whatever.ko and even kldload /debug-modules/up/whatever.ko [...] -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 15:55:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 5B0FD14DDC for ; Wed, 12 May 1999 15:55:32 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id D2D311F58; Thu, 13 May 1999 06:55:28 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Mikael Karpberg Cc: mike@smith.net.au (Mike Smith), soda@sra.co.jp, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Thu, 13 May 1999 00:36:18 +0200." <199905122236.AAA11182@ocean.campus.luth.se> Date: Thu, 13 May 1999 06:55:28 +0800 From: Peter Wemm Message-Id: <19990512225530.D2D311F58@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikael Karpberg wrote: > According to Mike Smith: > > This is actually a major defect in the newconfig design; if the kernel > > doesn't already know about a device when it is built, it can never > > support it. > > That would be so lovely, with a DEVFS too: > > Plug your Cool card into your pcmcia slot, and get the message on > the sytem console that an unknown pcmcia card called "Cool", made > by CoolMakers, Inc. Damn... not even a generic driver wanted this card. > Pull the card out and go for the web: > > # ftp ftp.a.cool.thing.com > ftp> get cool.tgz > --> Downloading file. > ftp> quit > --> Good bye. > # install_driver cool.tgz > --> Adding driver to driver database, and installing /modules/cool.ko! > > And at this point the kernel has not loaded the driver, but just > been told there's a new driver around and for what cards and vendors > it works, etc. This is done by a library call, or something, which > does adds the driver to the database, and a syscall to update the > kernel's already loaded database, or to get it to reload the database. > > Plug the card in again, and the kernel loads in cool.ko and probes the > card, and created a /dev/cool, and everything works just fine. No reboot, > no recompile, nada. *purr* This is exactly the way new-bus works. You merely load the driver, and the configuration engine reruns the probe for unclaimed devices on smart busses automatically. Of course, kicking off a generic driver when a more specific driver is loaded is a different problem... I have not looked to see if this is supported. It should not be a significant problem if it is not yet implemented. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 16:15: 7 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 CCC3D15D9A for ; Wed, 12 May 1999 16:15:02 -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 QAA01911; Wed, 12 May 1999 16:13:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905122313.QAA01911@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mi@aldan.algebra.com Cc: current@freebsd.org Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Wed, 12 May 1999 18:52:36 EDT." <199905122252.SAA73553@misha.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 1999 16:13:01 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith once wrote: > > > For a usable dynamic architecture, loadable modules need to be > > compiled to support both UP and SMP architectures simultaneously. Thus > > the locking primitives need to be conditionalised at _runtime_. > > What about > > kldload /modules/up/whatever.ko > and > kldload /modules/smp/whatever.ko > > and even > > kldload /debug-modules/up/whatever.ko > [...] This is just too painful for words. If people _really_ want to do this, you'd put all of the drivers into one .ko file and only partially link it (ie. just link the one module). But I do not think we want this at all; the obvious selectors so far are: - UP vs. SMP - BPF - Invariants That's eight versions of eg. a network driver already. I cut off BPF as an issue a little while back by putting stubs for the BPF routines into the kernel when BPF isn't actually built; we want to do the same things for the other functionality types. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 16:18: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id EB09C1585B for ; Wed, 12 May 1999 16:18:04 -0700 (PDT) (envelope-from soda@sra.co.jp) Received: from srasvf.sra.co.jp (srasvf [133.137.28.2]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id IAA04040; Thu, 13 May 1999 08:17:58 +0900 (JST) Received: from srapc342.sra.co.jp (srapc342 [133.137.28.111]) by srasvf.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id IAA08376; Thu, 13 May 1999 08:17:43 +0900 (JST) Received: (from soda@localhost) by srapc342.sra.co.jp (8.8.8/3.4W-sra) id IAA00977; Thu, 13 May 1999 08:17:52 +0900 (JST) Date: Thu, 13 May 1999 08:17:52 +0900 (JST) Message-Id: <199905122317.IAA00977@srapc342.sra.co.jp> From: Noriyuki Soda To: "Jordan K. Hubbard" Cc: Noriyuki Soda , dfr@nlsystems.com, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <66043.926546011@zippy.cdrom.com> References: <199905120926.SAA19601@srapc342.sra.co.jp> <66043.926546011@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Wed, 12 May 1999 14:53:31 -0700, "Jordan K. Hubbard" said: >> I agree that this is better way to solve the conflicts between new-bus >> and newconfig. Although I wondered why FreeBSD's core decide to choose >> new-bus before Usenix. > We didn't choose it "before USENIX" as if it were somehow part of the > objective to get this feature in before a public event, it simply came > up that Peter had the time to actually integrate new-bus from the > Alpha platform to the x86 This doesn't answer my wondering. The core members can safely postpone the decision after Usenix, because all of core members must know that both new-bus people and newconfig people will come to Freenix track. Who is the chair of Freeunix track ? :-) > Whether new-bus or newconfig is "better" was really, honestly not > the issue so much as were the following two bullet points: Quite interesting. This means that FreeBSD doesn't choose technology by it's design, but by which spokes loudly. I definitely say that this is worst way to design software. > 1. Does this bring the alpha and x86 architecture ports into better > alignment so that any future permutations can be more easily > brought across and/or simply shared between the two platforms? BSD/OS, NetBSD and OpenBSD are all based on newconfig on various architectures. FreeBSD/alpha is directly derived from NetBSD/alpha and NetBSD/alpha is based on newconfig. And at the time when the decision is made, FreeBSD/i386 and FreeBSD/pc98 are already converted to newconfig. So this is definitely is not the reason. > 2. Have we had a good history of communications between the people > doing new-bus vs our history of communication with the newconfig > people? Have you ever asked to newconfig people? No, no one of core members who takes charge of kernel part contacted to newconfig people, ever. Only one communication is held between one of core members who is actually new-bus one, and newconfig people. And this is requested by newconfig people, not by one of core members. Note that there are core members who supports new-bus, everytime this issue is raised between core, new-bus people can reply about this, newconfig people never have that chance. If you'll make offical decision, always you can call both people, and can hear both opinion. But this is never done. > The latter point is actually *really important* since we've already > learned that having totally separate groups who talk to us maybe once > a month (if even that often) is just not a workable strategy for the > long term and often causes more confusion for our users than it > actually helps the project. > We talk to Doug Rabson on a practically daily basis on a wide > variety of issues whereas the only real communication I've seen from > you has been during this conflict. And did you call one of the newconfig people? No. The contact address of newconfig people is already publically announced, but no one of core who takes charge of kernel part contacted to the address. We contacted to the one of core who takes charge of kernel part, and talked all problem about new-bus, before the decision is made. So, which does effort of communication ? > Before that, I had no idea that a Noriyuki Soda even existed. :-) Actually I am not a FreeBSD person, but one of observers of newconfig project. Some of you does know that my name is listed in NetBSD contributer's list. Although I send-pr'ed to FreeBSD sometimes. This is the reason I never posted to this mailing list. The reason I posted now is I am disgusted in FUD about technical points of newconfig. (I don't really care non technical points.) All of core should know about the benefit of the newconfig, because we already talked about it to one of the core when the decision is made. The reason why real newconfig people doesn't appears here is that there is language barrier. How did you think about Nakagawa-san's English? Do you know the pain about writing English when he knows his English is actually quite broken? (Yes, my English is broken, too. But probably I am a person who don't know what is disgrace. This is rare character and not thought good in Japan.) Can you write Japanese ? If no, why do you blame the one who cannot write English. Actually they will write English, if one of the core asked it. But no one of core request it, ever. So why no one never stops the FUD like the later postings ? > To try and put it another way, I've seen a lot of arguing about the > technical merits of the two systems but very little arguing about how > to solve the HUMAN FACTORS aspect of this situation which are really > and truly what led up to the core team's decision. I've also called > for greater communication between the two groups and so far all I've > seen is a lot of arguing and expressions of general annoyance from > Japan - that is NOT communication! Please point out the "general annoyance from Japan". If you read it carefully, you can find the technical point is correct. The problem of representation is caused by language barrier, not by the annoyance. > Proper communication involves regular discussion about incremental > improvements to the code base and how best to carry them out, biting > off problems in small chunks and dealing with each completely before > moving on to the next. Simply wandering off with the entire problem > for 6 months and working on it in isolation DOES NOT WORK and we've > proven this again and again. It only leads precisely to the situation > we have here now with newconfig and also PAO. Then you don't know about language barrier. Please learn Japanese, and write/speak Japanese, then you can find why the voice from Japan is not enough. Actually Japan is the country where FreeBSD most succeeded. There are over 50 books in Japan which includes "FreeBSD" in it's title. This is not joke. And this is the result of Hosokawa-san, Nakagawa-san, Kato-san and many other Japanese people's effort. > To put the problem in a larger context, people often ask me what all > the FreeBSD people in Japan are working on and it's a point of eternal > embarassment to me that I usually have to say "I honestly have no > idea." Why don't ask Japanese people, then? Why don't you going to learn Japanese? We all Japanese tries to learn English, though there is big barrier between English language and Japanese language. > We really really really need to fix this if we're to avoid > further repetitions of this kind of thing and that's why I'm flying to > Tokyo at the end of this month to talk with you guys - we're clearly > not communicating adequately and I'm willing to do what I can, > including physically relocating myself on a periodic basis, to fix it > from this side. This is wellcome, of course. > What are you doing to fix it on yours? :-) We've done our best, why don't you know our effort ? -- soda@sra.co.jp Software Research Associates, Inc., Japan (Noriyuki Soda) Advanced Technology Group. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 16:23:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from imap.ncsa.es (imap.ncsa.es [194.179.50.6]) by hub.freebsd.org (Postfix) with ESMTP id CE3951585B; Wed, 12 May 1999 16:23:08 -0700 (PDT) (envelope-from jesusr@freebsd.org) Received: from kk (modem224-103.ncsa.es [195.77.224.103]) by imap.ncsa.es (8.9.3/8.9.1) with SMTP id BAA35350; Thu, 13 May 1999 01:23:06 +0200 (CEST) Message-ID: <006101be9cce$c80c5500$67e04dc3@kk> From: "Jesus Rodriguez" To: , "Jordan K. Hubbard" Cc: Subject: RE: Someone blew up the handbook again. Date: Thu, 13 May 1999 01:25:52 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >/usr/local/bin/jade -V html-manifest -ioutput.html -c /usr/doc/share/sgml/catal >og -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sg >ml/docbook/3.0/catalog -c /usr/local/share/sgml/jade/catalog -d /usr/doc/share/ >sgml/freebsd.dsl -t sgml handbook.sgml >/usr/local/bin/jade:install/chapter.sgml:279:13:E: character data is not allowed > >Should I just turn NODOC on for the -current snapshot builds? The problem >is that I'm not getting *any* -current (or releng3, for that matter) >snapshots out at releng3.freebsd.org and current.freebsd.org because >on the days when src isn't broken, the handbook is and that kills the >builds just as effectively. :-( Handbook builds for me at freefall with no problem: % make DOC_PREFIX=/home/jesusr/cvs/doc /usr/local/bin/jade -V html-manifest -ioutput.html -c /home/jesusr/cvs/doc/shar e/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/lo cal/share/sgml/docbook/3.0/catalog -c /usr/local/share/sgml/jade/catalog -d /ho me/jesusr/cvs/doc/share/sgml/freebsd.dsl -t sgml handbook.sgml tidy -i -m -f /dev/null *.html *** Error code 1 (ignored) % JesusR. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 16:27:11 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 67A7715AF2 for ; Wed, 12 May 1999 16:26:43 -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 IAA03181; Thu, 13 May 1999 08:56:31 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id IAA15085; Thu, 13 May 1999 08:56:16 +0930 (CST) Date: Thu, 13 May 1999 08:56:15 +0930 From: Greg Lehey To: Christian Carstensen Cc: current@FreeBSD.ORG Subject: Re: vinum broken?? Message-ID: <19990513085615.U89091@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 Christian Carstensen on Wed, May 12, 1999 at 03:01:51PM +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, 12 May 1999 at 15:01:51 +0200, Christian Carstensen wrote: > > Hi, > > Does anyone else experience problems with the current kernel release > and vinum? > I've compiled a new kernel along with a make world today. After rebooting > vinum did not start: "/dev/vinum/Control: invalid operation..." > Any suggestions? I did have a glitch in vinumparser.c. Make sure you have revision 1.10 of that file. If you do (it's the latest of all revision), send me some more details of your configuration and when the error occurs. 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 May 12 16:28:28 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 4A0D815A2D for ; Wed, 12 May 1999 16:28:20 -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 IAA03203; Thu, 13 May 1999 08:58:05 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id IAA15120; Thu, 13 May 1999 08:58:05 +0930 (CST) Date: Thu, 13 May 1999 08:58:04 +0930 From: Greg Lehey To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive Message-ID: <19990513085803.V89091@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 Dag-Erling Smorgrav on Wed, May 12, 1999 at 03:37:40PM +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, 12 May 1999 at 15:37:40 +0200, Dag-Erling Smorgrav wrote: > I have a brand new 10 GB IBM UltrStar (DTTA-371010) which is causing > me some pains. If I boot with flags 0x80ff, everything works fine: > > wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 > wdc0: unit 0 (wd0): , 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 on isa0 > wdc1: unit 0 (wd2): , 32-bit, multi-block-16 > wd2: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S What chip set are you using? 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 May 12 16:28:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id 6337415DFA for ; Wed, 12 May 1999 16:28:41 -0700 (PDT) (envelope-from soda@sra.co.jp) Received: from srasvf.sra.co.jp (srasvf [133.137.28.2]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id IAA04186; Thu, 13 May 1999 08:28:34 +0900 (JST) Received: from srapc342.sra.co.jp (srapc342 [133.137.28.111]) by srasvf.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id IAA08390; Thu, 13 May 1999 08:28:18 +0900 (JST) Received: (from soda@localhost) by srapc342.sra.co.jp (8.8.8/3.4W-sra) id IAA01375; Thu, 13 May 1999 08:28:28 +0900 (JST) Date: Thu, 13 May 1999 08:28:28 +0900 (JST) Message-Id: <199905122328.IAA01375@srapc342.sra.co.jp> From: Noriyuki Soda To: Mike Smith Cc: Noriyuki Soda , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905122209.PAA01534@dingo.cdrom.com> References: <199905120901.SAA04493@srapc288.sra.co.jp> <199905122209.PAA01534@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Wed, 12 May 1999 15:09:05 -0700, Mike Smith said: > It would appear that you don't understand the problem, as no > configuration technique can telepathically determine in advance which > new drivers you are going to load. Apparently you misunderstand newconfig. :-) There is compiled format of "files" file which path is known by kernel. >> - newconfig can cope with both static configuration and dynamic >> configuration. new-bus can handle dynamic configuration only. > This is actually a major defect in the newconfig design; if the kernel > doesn't already know about a device when it is built, it can never > support it. Apparently you misunderstand newconfig, too. :-) See above. >> The way on new-bus will cause compatibility problem when >> OS is upgraded, because the implementation (filename) may >> be changed between versions and versions. > This is a transient implementation issue, the obsolecesnce of which is > already manifest in the plans that have been laid for a device > identifier to module to file lookup with the translation data _outside_ > the kernel. In other words, that is not compatible with the BSD way where FreeBSD and BSDI and NetBSD and OpenBSD already probed. It is actually true that FreeBSD becomes Linux. -- soda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 16:38:14 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 7374315AF2 for ; Wed, 12 May 1999 16:38:13 -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 QAA02085; Wed, 12 May 1999 16:35:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905122335.QAA02085@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Noriyuki Soda Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Thu, 13 May 1999 08:28:28 +0900." <199905122328.IAA01375@srapc342.sra.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 1999 16:35:42 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>>>> On Wed, 12 May 1999 15:09:05 -0700, Mike Smith said: > > > It would appear that you don't understand the problem, as no > > configuration technique can telepathically determine in advance which > > new drivers you are going to load. > > Apparently you misunderstand newconfig. :-) > There is compiled format of "files" file which path is known by > kernel. Aha. And the kernel has to read this file? How does it read it if it's loading eg. the disk driver that it will be using to read the disk? Why does the information have to be in this file? Why not put it in the drivers themselves? > >> The way on new-bus will cause compatibility problem when > >> OS is upgraded, because the implementation (filename) may > >> be changed between versions and versions. > > > This is a transient implementation issue, the obsolecesnce of which is > > already manifest in the plans that have been laid for a device > > identifier to module to file lookup with the translation data _outside_ > > the kernel. > > In other words, that is not compatible with the BSD way where FreeBSD > and BSDI and NetBSD and OpenBSD already probed. There is no "BSD way" anymore. The "BSD way" was developed to support Unibus on the early Vax systems. It's not clear to you that newbus does draw on ideas from newconfig. But newbus is a lot more than _just_ a new set of names for the probe/ configuration functions; it's a complete driver interface architecture. Newconfig is a good semi-static semi-dynamic configuration framework, but that's all it is. > It is actually true that FreeBSD becomes Linux. This is a childish troll, especially coming from you. If for no other reason, this is an excellent reason _not_ to be working with your team. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 16:40:42 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 361B615AF2 for ; Wed, 12 May 1999 16:40:40 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA66831; Wed, 12 May 1999 16:39:40 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Noriyuki Soda Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Thu, 13 May 1999 08:28:28 +0900." <199905122328.IAA01375@srapc342.sra.co.jp> Date: Wed, 12 May 1999 16:39:40 -0700 Message-ID: <66827.926552380@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is actually true that FreeBSD becomes Linux. Comments like this will only ensure that you wind up in kill files, mine included. They add nothing to the discussion. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 16:44:42 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 F38C715AF2 for ; Wed, 12 May 1999 16:44:32 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id BAA18955; Thu, 13 May 1999 01:43:14 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905122343.BAA18955@freebsd.dk> Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905122335.QAA02085@dingo.cdrom.com> from Mike Smith at "May 12, 1999 4:35:42 pm" To: mike@smith.net.au (Mike Smith) Date: Thu, 13 May 1999 01:43:14 +0200 (CEST) Cc: soda@sra.co.jp, mike@smith.net.au, 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 Mike Smith wrote: > > > It is actually true that FreeBSD becomes Linux. > > This is a childish troll, especially coming from you. If for no other > reason, this is an excellent reason _not_ to be working with your team. Oh boy... Could we end this now please ?? We've made our decision, and thats it, period, end of story. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 16:48: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id DA6E115463 for ; Wed, 12 May 1999 16:47:56 -0700 (PDT) (envelope-from soda@sra.co.jp) Received: from srasvf.sra.co.jp (srasvf [133.137.28.2]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id IAA04564; Thu, 13 May 1999 08:47:51 +0900 (JST) Received: from srapc342.sra.co.jp (srapc342 [133.137.28.111]) by srasvf.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id IAA08418; Thu, 13 May 1999 08:47:34 +0900 (JST) Received: (from soda@localhost) by srapc342.sra.co.jp (8.8.8/3.4W-sra) id IAA01507; Thu, 13 May 1999 08:47:46 +0900 (JST) Date: Thu, 13 May 1999 08:47:46 +0900 (JST) Message-Id: <199905122347.IAA01507@srapc342.sra.co.jp> From: Noriyuki Soda To: "Jordan K. Hubbard" Cc: Noriyuki Soda , Mike Smith , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <66827.926552380@zippy.cdrom.com> References: <199905122328.IAA01375@srapc342.sra.co.jp> <66827.926552380@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It is actually true that FreeBSD becomes Linux. > Comments like this will only ensure that you wind up in kill files, > mine included. They add nothing to the discussion. I see, sorry. -- soda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 16:50:25 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 4F89F15463 for ; Wed, 12 May 1999 16:50:19 -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 QAA55658; Wed, 12 May 1999 16:47:33 -0700 (PDT) Date: Wed, 12 May 1999 16:47:32 -0700 (PDT) From: Julian Elischer To: Noriyuki Soda Cc: "Jordan K. Hubbard" , dfr@nlsystems.com, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905122317.IAA00977@srapc342.sra.co.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 ok, here is a reason for all this... It has benn a common thought among the FreeBSD people I have spoken too (and that's nearly all of the main developers, INCLUDING bill Jolitz) that with cheaper RAM and better organosed busses teh way to go is towards removing all static devoce information from the kernel, so that new device drivers are loaded completely dynamically. We are living in a world where NT is the competition. You do not recompile NT to add a device. Nor should you have to recompile FreeBSD to add a device. We want the distributed FreeBSD binary kernel skelaton to work with a driver that was written fro hardware that was built after the skelaton was compiled. This requires that the kernle have NO (NONE, ZIP, NADA, 0) information about the driver compiled into it. This is true as well for BUS types. If someone writes a VMEbus module it should be loadable to the kernel with no recompile, and after that all VME bus devices for which tere is a driver should be usabel once their drivers are loaded. The config.new(8) was evaluated a long time ago and rejected. Not because it was worse than config (.old) but because it was NOT SUFFICIENTLY BETTER. If we did the work to convert to config.new then that would be wasted effort, because we would then have to discard config.new and all it's changes when we got to the next step. It was decided (not officially, but effectively enough) that it would be just as easy to go directly to where we want to get from old config as from new config, so that itermediate step of config.new is wasted effort. We are planning on dicarding (mostly) config(.old) as well, but at least we have not needed to do a lot ofo work on it. NetBSD people have not the same stated aim of completely eliminating config, so for them it made more sense to migrate to config.new. From The FreeBSD perspective config.any is an evolutionalry dead end. It should only be used for 5% of all systems, where people are experimenting with features. The aim is to have the skelaton for a particular release be completely suitable for nearly all users, and have it taylored for particular systems by the linking in of dynamic .ko files as needed. THe diference between out definition of 'dynamic' an dyour definition of 'dynamic' is that in our definition the driver may not yet have been imagined at compile time for the kernel. I the newconfig(TM) world you need to know about the device, even if you don't have the driver present. We consider this a vital feature. Any system that does not support this will NOT be considered for FreeBSD. I have watched this discussion for a while and it seens that this concept has somehow not been understood by the newconfig people. I believe it is because we have not specified enough what our defintion of 'dynamic' is. It must also apply to new BUS type modules as well. The present new-bus code still has some prior knowledge for some devices and bus types. These are to be eliminated as we progress, so you should not think of these when you try understand new-bus. julian On Thu, 13 May 1999, Noriyuki Soda wrote: > >>>>> On Wed, 12 May 1999 14:53:31 -0700, > "Jordan K. Hubbard" said: > > >> I agree that this is better way to solve the conflicts between new-bus > >> and newconfig. Although I wondered why FreeBSD's core decide to choose > >> new-bus before Usenix. > > > We didn't choose it "before USENIX" as if it were somehow part of the > > objective to get this feature in before a public event, it simply came > > up that Peter had the time to actually integrate new-bus from the > > Alpha platform to the x86 > > This doesn't answer my wondering. The core members can safely postpone > the decision after Usenix, because all of core members must know that > both new-bus people and newconfig people will come to Freenix track. > Who is the chair of Freeunix track ? :-) > > > Whether new-bus or newconfig is "better" was really, honestly not > > the issue so much as were the following two bullet points: > > Quite interesting. This means that FreeBSD doesn't choose technology > by it's design, but by which spokes loudly. I definitely say that this > is worst way to design software. > > > 1. Does this bring the alpha and x86 architecture ports into better > > alignment so that any future permutations can be more easily > > brought across and/or simply shared between the two platforms? > > BSD/OS, NetBSD and OpenBSD are all based on newconfig on various > architectures. FreeBSD/alpha is directly derived from NetBSD/alpha and > NetBSD/alpha is based on newconfig. > And at the time when the decision is made, FreeBSD/i386 and > FreeBSD/pc98 are already converted to newconfig. > > So this is definitely is not the reason. > > > 2. Have we had a good history of communications between the people > > doing new-bus vs our history of communication with the newconfig > > people? > > Have you ever asked to newconfig people? > No, no one of core members who takes charge of kernel part contacted > to newconfig people, ever. > Only one communication is held between one of core members who is > actually new-bus one, and newconfig people. And this is requested by > newconfig people, not by one of core members. > > Note that there are core members who supports new-bus, everytime this > issue is raised between core, new-bus people can reply about this, > newconfig people never have that chance. > > If you'll make offical decision, always you can call both people, and > can hear both opinion. But this is never done. > > > The latter point is actually *really important* since we've already > > learned that having totally separate groups who talk to us maybe once > > a month (if even that often) is just not a workable strategy for the > > long term and often causes more confusion for our users than it > > actually helps the project. > > > We talk to Doug Rabson on a practically daily basis on a wide > > variety of issues whereas the only real communication I've seen from > > you has been during this conflict. > > And did you call one of the newconfig people? No. > The contact address of newconfig people is already publically > announced, but no one of core who takes charge of kernel part > contacted to the address. > > We contacted to the one of core who takes charge of kernel part, and > talked all problem about new-bus, before the decision is made. > > So, which does effort of communication ? > > > Before that, I had no idea that a Noriyuki Soda even existed. :-) > > Actually I am not a FreeBSD person, but one of observers of newconfig > project. Some of you does know that my name is listed in NetBSD > contributer's list. Although I send-pr'ed to FreeBSD sometimes. > This is the reason I never posted to this mailing list. > > The reason I posted now is I am disgusted in FUD about technical > points of newconfig. (I don't really care non technical points.) > All of core should know about the benefit of the newconfig, because we > already talked about it to one of the core when the decision is made. > > The reason why real newconfig people doesn't appears here is > that there is language barrier. > How did you think about Nakagawa-san's English? > Do you know the pain about writing English when he knows his > English is actually quite broken? > (Yes, my English is broken, too. But probably I am a person who don't > know what is disgrace. This is rare character and not thought good in > Japan.) > > Can you write Japanese ? > If no, why do you blame the one who cannot write English. > Actually they will write English, if one of the core asked it. But no > one of core request it, ever. > > So why no one never stops the FUD like the later postings ? > > > To try and put it another way, I've seen a lot of arguing about the > > technical merits of the two systems but very little arguing about how > > to solve the HUMAN FACTORS aspect of this situation which are really > > and truly what led up to the core team's decision. I've also called > > for greater communication between the two groups and so far all I've > > seen is a lot of arguing and expressions of general annoyance from > > Japan - that is NOT communication! > > Please point out the "general annoyance from Japan". > If you read it carefully, you can find the technical point is correct. > The problem of representation is caused by language barrier, not by > the annoyance. > > > Proper communication involves regular discussion about incremental > > improvements to the code base and how best to carry them out, biting > > off problems in small chunks and dealing with each completely before > > moving on to the next. Simply wandering off with the entire problem > > for 6 months and working on it in isolation DOES NOT WORK and we've > > proven this again and again. It only leads precisely to the situation > > we have here now with newconfig and also PAO. > > Then you don't know about language barrier. > Please learn Japanese, and write/speak Japanese, then you can find why > the voice from Japan is not enough. > > Actually Japan is the country where FreeBSD most succeeded. > There are over 50 books in Japan which includes "FreeBSD" in it's title. > This is not joke. > > And this is the result of Hosokawa-san, Nakagawa-san, Kato-san and > many other Japanese people's effort. > > > To put the problem in a larger context, people often ask me what all > > the FreeBSD people in Japan are working on and it's a point of eternal > > embarassment to me that I usually have to say "I honestly have no > > idea." > > Why don't ask Japanese people, then? > Why don't you going to learn Japanese? > > We all Japanese tries to learn English, though there is big barrier > between English language and Japanese language. > > > We really really really need to fix this if we're to avoid > > further repetitions of this kind of thing and that's why I'm flying to > > Tokyo at the end of this month to talk with you guys - we're clearly > > not communicating adequately and I'm willing to do what I can, > > including physically relocating myself on a periodic basis, to fix it > > from this side. > > This is wellcome, of course. > > > What are you doing to fix it on yours? :-) > > We've done our best, why don't you know our effort ? > -- > soda@sra.co.jp Software Research Associates, Inc., Japan > (Noriyuki Soda) Advanced Technology Group. > > > 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 Wed May 12 16:50:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id 5C9A415A0E for ; Wed, 12 May 1999 16:50:16 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id SAA47321 for freebsd-current@freebsd.org; Wed, 12 May 1999 18:50:15 -0500 (CDT) (envelope-from bob) Date: Wed, 12 May 1999 18:50:15 -0500 From: Bob Willcox To: current list Subject: Substitute for "dumps on" specification in kernel config file Message-ID: <19990512185015.A47237@luke.pmr.com> Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there an alternative way of specifying where system dumps are to go similar to the now obsolete: config kernel root on da0s1 dumps on da0s1b line? I am experiencing a panic on a recently cvsuped -current kernel and need to get a crash dump during boot (prior to dumpon being executed). Thanks, Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 16:57:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 497BE15DD4 for ; Wed, 12 May 1999 16:57:04 -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 RAA00635; Wed, 12 May 1999 17:56:19 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA02805; Wed, 12 May 1999 17:56:19 -0600 Date: Wed, 12 May 1999 17:56:19 -0600 Message-Id: <199905122356.RAA02805@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Julian Elischer Cc: Noriyuki Soda , "Jordan K. Hubbard" , dfr@nlsystems.com, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: References: <199905122317.IAA00977@srapc342.sra.co.jp> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > NetBSD people have not the same stated aim of completely eliminating > config, so for them it made more sense to migrate to config.new. I think it's also safe to say that because of NetBSD's interest in supporting 'older' hardware, it would be suicide to use a truly dynamic scheme since much of the old hardware doesn't have the necessary capabilities to do dynamic configuration. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 16:59:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from hydrogen.fircrest.net (metriclient-2.uoregon.edu [128.223.172.2]) by hub.freebsd.org (Postfix) with ESMTP id 3C6C515E0D for ; Wed, 12 May 1999 16:59:46 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.fircrest.net (8.9.1/8.8.7) id QAA27851; Wed, 12 May 1999 16:59:07 -0700 (PDT) Message-ID: <19990512165906.57576@hydrogen.nike.efn.org> Date: Wed, 12 May 1999 16:59:06 -0700 From: John-Mark Gurney To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: the new config and booting References: <199905120817.KAA03605@peedub.muc.de> <199905122203.PAA01488@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199905122203.PAA01488@dingo.cdrom.com>; from Mike Smith on Wed, May 12, 1999 at 03:03:06PM -0700 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith scribbled this message on May 12: > > > > no, it's a "dangerously dedicated" SCSI disk. > > That's never a good start. well, I wonder if other people have noticed this also, but if you don't have a previous boot loader installed (like windows/dos) the ONLY way to install onto a machine is TO use a dangerously dedicated mode... I did a couple installs using normal slices and standard MBR, and when the machine restarted, I got the "Operating System Missing" error... the only way I was able to install on the system was to use dangerous dedicated mode... I've seen this happen a couple times w/ 3.0-R and 3.1-19990328-STABLE IIRC... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 16:59:59 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 7D8F115E48 for ; Wed, 12 May 1999 16:59:50 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id QAA25113; Wed, 12 May 1999 16:59:15 -0700 Date: Wed, 12 May 1999 16:59:15 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nate Williams Cc: Julian Elischer , Noriyuki Soda , "Jordan K. Hubbard" , dfr@nlsystems.com, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905122356.RAA02805@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 > > NetBSD people have not the same stated aim of completely eliminating > > config, so for them it made more sense to migrate to config.new. > > I think it's also safe to say that because of NetBSD's interest in > supporting 'older' hardware, it would be suicide to use a truly dynamic > scheme since much of the old hardware doesn't have the necessary > capabilities to do dynamic configuration. Yeah, like a sparcstation-1. It really can't do dynamic reconfiguration at all. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 17: 5:22 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 85F8E15507 for ; Wed, 12 May 1999 17:05:17 -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 UAA06806; Wed, 12 May 1999 20:05:03 -0400 (EDT) (envelope-from wollman) Date: Wed, 12 May 1999 20:05:03 -0400 (EDT) From: Garrett Wollman Message-Id: <199905130005.UAA06806@khavrinen.lcs.mit.edu> To: Noriyuki Soda Cc: "Jordan K. Hubbard" , dfr@nlsystems.com, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905122317.IAA00977@srapc342.sra.co.jp> References: <199905120926.SAA19601@srapc342.sra.co.jp> <66043.926546011@zippy.cdrom.com> <199905122317.IAA00977@srapc342.sra.co.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Have you ever asked to newconfig people? > No, no one of core members who takes charge of kernel part contacted > to newconfig people, ever. It's your responsibility to communicate with us, not the other way around. The only way for your views to be even considered is for you to make them known BEFORE the die is cast. I can't speak for any of the other developers, but I personally get 200-400 messages a day, and unless you speak up and -- most importantly -- inform everyone REGULARLY of the progess you make, your views will not be considered. > Note that there are core members who supports new-bus, everytime this > issue is raised between core, new-bus people can reply about this, > newconfig people never have that chance. The issue hasn't been raised in -core. Doug built the system, and refined it in FreeBSD/alpha with encouragement from many of us. Last November, I set up a public mailing-list, announced it to the world several times, and used it to coordinate the further development. Peter and I developed the i386 part of the mechanism long after the Alpha side was well-entrenched. Peter and Doug continue to enhance it. The only discussion -core ever had on the topic was ``ok, when should we bring this into current?''. Once those milestones were met -- about four days, as I recall -- we threw the switch. By that time, a de facto decision had long since been made, since it's a well-known principle of volunteer projects that the people who do the work (like Doug with the Alpha port) are the ones who really make the decisions, by choosing which projects to spend their time on. > We contacted to the one of core who takes charge of kernel part, and > talked all problem about new-bus, before the decision is made. There is no such person as ``the one of core who takes charge of kernel part''. -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 Wed May 12 17: 8:40 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 1254815EB3 for ; Wed, 12 May 1999 17:08:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA02337; Wed, 12 May 1999 17:06:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905130006.RAA02337@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John-Mark Gurney Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: the new config and booting In-reply-to: Your message of "Wed, 12 May 1999 16:59:06 PDT." <19990512165906.57576@hydrogen.nike.efn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 1999 17:06:03 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith scribbled this message on May 12: > > > > > > no, it's a "dangerously dedicated" SCSI disk. > > > > That's never a good start. > > well, I wonder if other people have noticed this also, but if you don't > have a previous boot loader installed (like windows/dos) the ONLY way > to install onto a machine is TO use a dangerously dedicated mode... This is quite untrue. I do a lot of installs to virgin systems on a wide range of hardware, and I haven't encountered any situations where DD has been necessary in a long time. OTOH, I have met many where DD would be fatal. > I did a couple installs using normal slices and standard MBR, and when > the machine restarted, I got the "Operating System Missing" error... > the only way I was able to install on the system was to use dangerous > dedicated mode... I've seen this happen a couple times w/ 3.0-R and > 3.1-19990328-STABLE IIRC... The determining factors here are the BIOS on your system and the geometries that you've set for them in your system's setup. If you manually match the system geometry to the BSD geometry, or your BIOS is smart enough to check the disk geometry and match it, you'll be fine. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 17:11: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 40B9115284 for ; Wed, 12 May 1999 17:11: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 JAA03430; Thu, 13 May 1999 09:41:09 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA15398; Thu, 13 May 1999 09:40:53 +0930 (CST) Date: Thu, 13 May 1999 09:40:53 +0930 From: Greg Lehey To: Gianmarco Giovannelli Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: panic ! panic ! panic ! Message-ID: <19990513094053.Z89091@freebie.lemis.com> References: <5817.926524559@critter.freebsd.dk> <4.1.19990512182248.009bda80@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <4.1.19990512182248.009bda80@194.184.65.4>; from Gianmarco Giovannelli on Wed, May 12, 1999 at 06:41:15PM +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, 12 May 1999 at 18:41:15 +0200, Gianmarco Giovannelli wrote: > At 12/05/99, you wrote: >> >> At least put DDB in your kernel, type "trace" when it >> panics and tell us what it says. > > Ok... it's a bit long ... (Tell me there isn't a command to write the trace > output on a disk :-) You should have a kernel built with the -g option, and have enabled dumps. Then you can analyse the dump at your leisure, and you'll also get more information. There's a section in the handbook about 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 Wed May 12 17:12:29 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 1C1A415E8D for ; Wed, 12 May 1999 17:12:19 -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 RAA56590; Wed, 12 May 1999 17:08:11 -0700 (PDT) Date: Wed, 12 May 1999 17:08:10 -0700 (PDT) From: Julian Elischer To: Noriyuki Soda Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905122328.IAA01375@srapc342.sra.co.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 Thu, 13 May 1999, Noriyuki Soda wrote: > > It is actually true that FreeBSD becomes Linux. > It is truely unfortunate that it comes to this.. however it has always been to me a source of great frustration to me that Linus was able to implement a driver framework that allows a very dynamic loading of modules and drivers. FreeBSD is designing the next logical step beyond this. Config.new is a stepping stone in an evolution. In our case we have pretty much all decided that the 'goal' for this next phase of evolution is the complete dynamic configuration of the kernel. The old "BSD way" was simply a step in the evolutionary chain. There is nothing inherrently 'right' about it. It reflects the limitations of the technology at that time. config.new did not change the level of the technology, but rather, re-arrange it a bit. The newconfig crew have made improvements to config.new to better support dynamic loading, but after a lot of discussions (face to face in many cases) the statements have been agreed by nearly all the FreeBSD people involved. 1/ a module that is pre-loaded should be treated the same as one that is 'post' loaded as much as possble. 2/ A module should not rely on any prior knowledge of it's existance to function correctly. 3/ A module should be able to supply it's own default configuration information, and also be able to access additional information that may be availabel at load time. 4/ The loadable module may implement an entirely new class of modules (e.g. a new bus type) of which there was no previous knowledge. 5/(not agreed by all) In a perfect world, /dev/ entries would reflect reality, and the sysctl name space would also do so. 6/ all the usual desirable aspects of loadable modules (e.g. unloadability) apply. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 17:12:31 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 1880D15E8B for ; Wed, 12 May 1999 17:12:18 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA67069; Wed, 12 May 1999 17:12:05 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Noriyuki Soda Cc: dfr@nlsystems.com, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Thu, 13 May 1999 08:17:52 +0900." <199905122317.IAA00977@srapc342.sra.co.jp> Date: Wed, 12 May 1999 17:12:05 -0700 Message-ID: <67065.926554325@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This doesn't answer my wondering. The core members can safely postpone > the decision after Usenix, because all of core members must know that > both new-bus people and newconfig people will come to Freenix track. I'm not sure this was adequate reason to postpone the decision either, and like I said, Peter had the time to do it and it wasn't clear when he was next going to have the time again. In a volunteer project, you have to sometimes move when people are ready to move or you'll miss your window of opportunity. > Quite interesting. This means that FreeBSD doesn't choose technology > by it's design, but by which spokes loudly. I definitely say that this > is worst way to design software. No, it doesn't mean that, it means that assessing technology isn't JUST a question of looking at code since code, by its very nature, changes rapidly - if you cannot see that then this conversation is likely to be just about as productive as arguing with a first-year high school student on the subject. Evaluating technology is a question of deciding which code is both superior AND has the best longevity, longevity being a more difficult equation which combines the history of the developers involved and how effective your communications with them are. In this case, I don't believe communications are effective and that kills newconfig just as thoroughly as having the code be a total mess; I think I've pointed this out several times now. > Have you ever asked to newconfig people? > No, no one of core members who takes charge of kernel part contacted > to newconfig people, ever. As I told you before, I didn't even know you *existed* until I saw your paper. How am I supposed to contact you guys if I don't even know you're alive? There are presently over 5 billion people on the planet and I can't call each and every one of them regularly to find out whether or not they're working on FreeBSD. :) The time for you guys to have contacted core (or, even better, -hackers) to let us know of your existence was back when you started your project, not at the point where you were so far along that papers were being published. Don't expect people to contact YOU since, as I've said, people generally don't even know you exist until you tell them. > Note that there are core members who supports new-bus, everytime this > issue is raised between core, new-bus people can reply about this, > newconfig people never have that chance. You don't "get" chances in this business, you MAKE chances. :) > Can you write Japanese ? > If no, why do you blame the one who cannot write English. I'm very fortunate to have had my mother tongue chosen as the defacto international language of computer science and don't think I don't realize my degree of good fortune. Had Japanese or French been chosen instead, you may rest assured that I'd have put the time necessary into learning those languages as well. I'm certainly capable of learning a foreign language when and if it's necessary, don't think I'm an english bigot here or anything (sprechen Sie Deutsch? :), but I'm also a realist and if the prevailing language of communication is language X then I expect everyone concerned to just learn language X and I don't particularly care how difficult it is, Just Do It and don't whine about it is my motto. To be more specific, I expect you and anyone else in Japan who wishes to communicate with an international audience to learn english and, should I ever live in Japan and need to speak frequently with Japanese speakers, you may rest assured that I'll learn Japanese, however hard that process might be. We're supposed to be intelligent people here and if we can't learn to speak others languages if and as necessary then maybe we're not as intelligent as we think. :-) > Please point out the "general annoyance from Japan". I have seen a lot of arguing about technical merits and decisions made by the core team, but I have yet to see any constructive comments about fixing the communication problems which led to this decision. Focusing on the negative and not the positive counts for "general annoyance" in my book since people generally don't do that unless they're annoyed. I'm sure your command of english is not so deficient that you're unable to make positive suggestions - I thought Japanese people had more cultural difficulty in saying "no" than in saying "yes" :-) > Then you don't know about language barrier. > Please learn Japanese, and write/speak Japanese, then you can find why > the voice from Japan is not enough. See above. > Actually Japan is the country where FreeBSD most succeeded. > There are over 50 books in Japan which includes "FreeBSD" in it's title. > This is not joke. I know, I've been to Akihabara and I've even taken pictures of the books in question (http://www.freebsd.org/~jkh/japan/report/dayfive-books.jpg). Don't think that I underestimate the importance of the Japanese market - if I did, do you think I'd be taking time out *right before USENIX* to fly over there for 3 days and Jet lag myself all to hell? I don't think so. :-) > Why don't ask Japanese people, then? > Why don't you going to learn Japanese? I'll be there shortly to do the first. The second is unnecessary since, as I've already pointed out, the international language here for this kind of communication is english, not Japanese. This is not restricted to computer science, by the way, so it's not like we're being uniquely unfair about this. If you want to be an aircraft pilot, for instance, you're back to the very same problem. The international language of aviation is english, and even when you're flying in Japan, you can speak Japanese to the tower all you like, and sometimes they'll even answer in Japanese, but you'll still get written up in the safety report for endangering all the other pilots in the air who NEEDED to hear and understand what you were saying. If you're saying in Japanese to the tower that you're on final approach to runway 25 and the Mexico Airlines flight behind you, who happens to think that HE has clearance for the same runway and can't understand your radio traffic, is going for the same thing, he's got no chance to say "wait, he's on final for 25 right? That's MY runway! Crap, I'm about to run into this guy!" The fact that your native languages might be Japanese and Spanish, respectively, makes no difference. You have to find some common ground if you want to prevent accidents, and in both general aviation and these mailing lists, that common ground is English. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 17:16:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from xena.cs.waikato.ac.nz (xena.cs.waikato.ac.nz [130.217.241.20]) by hub.freebsd.org (Postfix) with ESMTP id A1E3214E53 for ; Wed, 12 May 1999 17:16:29 -0700 (PDT) (envelope-from joerg@xena.cs.waikato.ac.nz) Received: from lucy.cs.waikato.ac.nz (joerg@lucy.cs.waikato.ac.nz [130.217.241.12]) by xena.cs.waikato.ac.nz (8.9.3/8.9.3) with ESMTP id MAA08796; Thu, 13 May 1999 12:16:20 +1200 (NZST) Received: (from joerg@localhost) by lucy.cs.waikato.ac.nz (8.8.8+Sun/8.8.8) id MAA29640; Thu, 13 May 1999 12:16:18 +1200 (NZST) Date: Thu, 13 May 1999 12:16:17 +1200 From: Joerg Micheel To: Mike Smith Cc: John-Mark Gurney , freebsd-current@freebsd.org, joerg@cs.waikato.ac.nz Subject: Re: the new config and booting Message-ID: <19990513121617.B25283@cs.waikato.ac.nz> References: <19990512165906.57576@hydrogen.nike.efn.org> <199905130006.RAA02337@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199905130006.RAA02337@dingo.cdrom.com>; from Mike Smith on Wed, May 12, 1999 at 05:06:03PM -0700 Organization: SCMS, The University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... drained by Solaris 7 SPARC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike, On Wed, May 12, 1999 at 05:06:03PM -0700, Mike Smith wrote: > > well, I wonder if other people have noticed this also, but if you don't > > have a previous boot loader installed (like windows/dos) the ONLY way > > to install onto a machine is TO use a dangerously dedicated mode... > > This is quite untrue. I do a lot of installs to virgin systems on a > wide range of hardware, and I haven't encountered any situations where > DD has been necessary in a long time. OTOH, I have met many where DD > would be fatal. Virgin systems is not virgin disks. If you buy a complete PC, this bootloader from Redmonton is already on the disk. I had similiar problems a while back and unless someone has explicitely looked after this, it still persits. Just my 2 Pfennige, Joerg -- Joerg B. Micheel Email: Waikato Applied Network Dynamics Phone: +64 7 8384794 The University of Waikato, SCMS Fax: +64 7 8384155 Private Bag 3105 Pager: +64 868 38222 Hamilton, New Zealand Plan: TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 17:24:24 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 4218F1510F for ; Wed, 12 May 1999 17:24:12 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id TAA13856; Wed, 12 May 1999 19:23:39 -0500 (CDT) Date: Wed, 12 May 1999 19:23:39 -0500 From: "Matthew D. Fuller" To: Joerg Micheel Cc: Mike Smith , John-Mark Gurney , freebsd-current@FreeBSD.ORG Subject: Re: the new config and booting Message-ID: <19990512192339.E21989@futuresouth.com> References: <19990512165906.57576@hydrogen.nike.efn.org> <199905130006.RAA02337@dingo.cdrom.com> <19990513121617.B25283@cs.waikato.ac.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990513121617.B25283@cs.waikato.ac.nz>; from Joerg Micheel on Thu, May 13, 1999 at 12:16:17PM +1200 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 13, 1999 at 12:16:17PM +1200, a little birdie told me that Joerg Micheel remarked > > Virgin systems is not virgin disks. If you buy a complete PC, this > bootloader from Redmonton is already on the disk. I had similiar > problems a while back and unless someone has explicitely looked > after this, it still persits. I just last night did a full install onto a set of fresh virgin disks in a fresh virgin system (all bought component-at-a-time) without using DD. -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller MF4839 http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 17:37:44 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 50C9114C9B for ; Wed, 12 May 1999 17:37:42 -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 RAA02533; Wed, 12 May 1999 17:34:36 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905130034.RAA02533@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joerg Micheel Cc: Mike Smith , John-Mark Gurney , freebsd-current@freebsd.org Subject: Re: the new config and booting In-reply-to: Your message of "Thu, 13 May 1999 12:16:17 +1200." <19990513121617.B25283@cs.waikato.ac.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 1999 17:34:36 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, May 12, 1999 at 05:06:03PM -0700, Mike Smith wrote: > > > well, I wonder if other people have noticed this also, but if you don't > > > have a previous boot loader installed (like windows/dos) the ONLY way > > > to install onto a machine is TO use a dangerously dedicated mode... > > > > This is quite untrue. I do a lot of installs to virgin systems on a > > wide range of hardware, and I haven't encountered any situations where > > DD has been necessary in a long time. OTOH, I have met many where DD > > would be fatal. > > Virgin systems is not virgin disks. If you buy a complete PC, this > bootloader from Redmonton is already on the disk. I had similiar > problems a while back and unless someone has explicitely looked > after this, it still persits. I am not a complete idiot, and when I say "virgin" system, I mean it. I'm quite aware of your problem. I outlined several solutions to it in the previous message, and elaborated on them in the handbook update I wrote about DD mode. I'm always looking for better ways of dealing with this problem; DD mode is not one however. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 17:49: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 0047014C9B for ; Wed, 12 May 1999 17:48:57 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id KAA25989; Thu, 13 May 1999 10:16:20 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199905130046.KAA25989@gizmo.internode.com.au> Subject: Re: cvs commit: src/sys/pci pcisupport.c To: karpen@ocean.campus.luth.se (Mikael Karpberg) Date: Thu, 13 May 1999 10:16:20 +0930 (CST) Cc: mike@smith.net.au, soda@sra.co.jp, current@FreeBSD.ORG In-Reply-To: <199905122236.AAA11182@ocean.campus.luth.se> from "Mikael Karpberg" at May 13, 99 00:36:18 am 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 Mikael Karpberg wrote: > That would be so lovely, with a DEVFS too: > Plug your Cool card into your pcmcia slot, and get the message on > the sytem console that an unknown pcmcia card called "Cool", made > by CoolMakers, Inc. Damn... not even a generic driver wanted this card. > Pull the card out and go for the web: > # ftp ftp.a.cool.thing.com > ftp> get cool.tgz > --> Downloading file. Pah. kldload http://www.cool.com/drivers/freebsd/cool.ko Perhaps kld modules should have some kind of signature verification to support such a thing. That'd be so great. The FreeBSD installation floppy could delay most device probes until after you've set up networking (so you'd need some network drivers on the floppy) then grab all the latest versions of the other drivers it wants to complete the install from www.freebsd.org... - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 17:52:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from nomad.dataplex.net (nomad.dataplex.net [216.140.184.132]) by hub.freebsd.org (Postfix) with ESMTP id AABCA14CFD for ; Wed, 12 May 1999 17:52:25 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.2/8.9.3) with ESMTP id TAA01499; Wed, 12 May 1999 19:44:07 -0500 (CDT) (envelope-from rkw@dataplex.net) X-Authentication-Warning: nomad.dataplex.net: rkw owned process doing -bs Date: Wed, 12 May 1999 19:44:07 -0500 (CDT) From: Richard Wackerbarth Reply-To: rkw@dataplex.net To: Mike Smith Cc: Noriyuki Soda , Poul-Henning Kamp , Tomoaki NISHIYAMA , rwhitesel@nbase-xyplex.com, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905122229.PAA01663@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 Wed, 12 May 1999, Mike Smith wrote: > > This option should automatically select the appropriate sources > > which is compiled into kernel, according to the source is needed > > only in UP case, or only in SMP case, or both. This is what > > oldconfig and newconfig does. > > This is, again, defective reasoning. > > For a usable dynamic architecture, loadable modules need to be compiled > to support both UP and SMP architectures simultaneously. Thus the > locking primitives need to be conditionalised at _runtime_. Or, alternately, at load time by choosing the appropriate subsystem to match the hardware. It is clearly possible to arrange that lowest-common-denominator code is initially loaded and then replaced with a configuration optimized version. The "configuration" at compile time is in the Makefile to cause, when appropriate, the various versions to be compiled from common code. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 18:25:49 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 EA76714C15 for ; Wed, 12 May 1999 18:25:44 -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 KAA03757 for ; Thu, 13 May 1999 10:55:42 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA17651 for FreeBSD-current@FreeBSD.ORG; Thu, 13 May 1999 10:55:42 +0930 (CST) Date: Thu, 13 May 1999 10:55:42 +0930 From: Greg Lehey To: FreeBSD current users Subject: HEADS UP: Vinum broken in -CURRENT Message-ID: <19990513105542.D89091@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i 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 I've just had some convincing reports that Vinum in current doesn't work at the moment. This is almost certainly something to do with the change in the representation of device numbers, and it's something I've been half expecting, but I don't have time to look at it this week. If you're using Vinum, please wait until next week before updating your configuration. Sorry about the trouble 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 May 12 18:53:21 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 E3A7114F58 for ; Wed, 12 May 1999 18:53:18 -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 VAA98712; Wed, 12 May 1999 21:50:24 -0400 (EDT) Date: Wed, 12 May 1999 21:50:24 -0400 (EDT) From: Chuck Robey To: Noriyuki Soda Cc: "Jordan K. Hubbard" , dfr@nlsystems.com, current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905122317.IAA00977@srapc342.sra.co.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 Thu, 13 May 1999, Noriyuki Soda wrote: > This doesn't answer my wondering. The core members can safely postpone > the decision after Usenix, because all of core members must know that > both new-bus people and newconfig people will come to Freenix track. > Who is the chair of Freeunix track ? :-) > > > Whether new-bus or newconfig is "better" was really, honestly not > > the issue so much as were the following two bullet points: > > Quite interesting. This means that FreeBSD doesn't choose technology > by it's design, but by which spokes loudly. I definitely say that this > is worst way to design software. I have to comment on this, it's too outrageous. Several times in the past, folks have written in and asked, if they wrote some particular piece of software, would it get committed. They said that it was a large undertaking, and that they wouldn't undertake it, unless there was general agreement beforehand about it. This has always had one response. No. We don't give apriori blank check agreement to stuff like that, because we don't know which way it's going to go, and if the final product isn't going where the developers (which means generally core, but not completely) then it's gong to be rejected. This has caused bad feelings sometimes, but it's stopped some folks from trying to hi-jack FreeBSD, and force it to go where one person wants it to go; it forces FreeBSD to be a group decision. So, how do big projects get done, then? The first point being brought up is true, no one wants to invest hugely in a project, just to see the work rejected. The way we get around that is by communicating, regularly and thoroughly, about the design and implementation of the project. Good communications means that we don't get into fights, and FreeBSD goes where the group wants it to go, not where some small set of interests want to hi-jack it. I am NOT saying that you or your group want to hijack anything, but the process DOES stop folks from doing that, and it's in fact already stopped that from happening more than once in my memory. Communications is a good thing, not something to be embarrassed about. Describing communications as "by which spokes loudly" is missing the point. Loudness hasn't the least to do with it. Regularity and clarity, getting the message across, is what's important. That is where your group has misunderstood the process. By going off on your own, and doing all that coding without any input, you established a reputation for not being willing to work together. Someone with a proven track record of communicating regularly was chosen. Not from a technical standpoint, but from a managerial standpoint, why does this surprise you? Don't offer technical arguments, this is not a technical issue. ----------------------------+----------------------------------------------- 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 (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 19: 7:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id A73B714C88 for ; Wed, 12 May 1999 19:07:48 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Wed, 12 May 1999 19:07:47 -0700 From: "David Schwartz" To: "Chuck Robey" Cc: Subject: RE: cvs commit: src/sys/pci pcisupport.c Date: Wed, 12 May 1999 19:07:47 -0700 Message-ID: <000101be9ce5$6561baa0$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have to comment on this, it's too outrageous. Several times in the > past, folks have written in and asked, if they wrote some particular > piece of software, would it get committed. They said that it was a > large undertaking, and that they wouldn't undertake it, unless there was > general agreement beforehand about it. There is a big difference between a general agreement that some feature or other is a "good thing" and a blank check of approval for code changes. These seem to get confused all the time. One example of this problem, in the opposite direction of the one you mentioned, is the old, "If you think that's such a good idea, why don't you code it and submit it?" This is equally unhelpful. If it's a bad idea, why should anyone code it? If it's a code idea, why does it matter who codes it, as long as it's coded well? DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 19:12:30 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 7E5D414C88 for ; Wed, 12 May 1999 19:12:25 -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 KAA10057 for ; Thu, 13 May 1999 10:11:41 +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 KAA23985 for ; Thu, 13 May 1999 10:12:23 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id KAA27892; Thu, 13 May 1999 10:12:22 +0800 Message-Id: <199905130212.KAA27892@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Some interrupt bogons still around. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 May 1999 10:12:22 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG An old 486 of mine still cant see its IDE driver with versions of ata-all.c later than 1.8, and my soundcard (PAS16) still doesn't seem to generate interrupts since the nexus stuff went in. 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 Wed May 12 19:23:27 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 1C3C514DAF for ; Wed, 12 May 1999 19:23:18 -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 WAA98801; Wed, 12 May 1999 22:20:57 -0400 (EDT) Date: Wed, 12 May 1999 22:20:57 -0400 (EDT) From: Chuck Robey To: David Schwartz Cc: current@FreeBSD.ORG Subject: RE: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <000101be9ce5$6561baa0$021d85d1@whenever.youwant.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, 12 May 1999, David Schwartz wrote: > > > I have to comment on this, it's too outrageous. Several times in the > > past, folks have written in and asked, if they wrote some particular > > piece of software, would it get committed. They said that it was a > > large undertaking, and that they wouldn't undertake it, unless there was > > general agreement beforehand about it. > > There is a big difference between a general agreement that some feature or > other is a "good thing" and a blank check of approval for code changes. > These seem to get confused all the time. > > One example of this problem, in the opposite direction of the one you > mentioned, is the old, "If you think that's such a good idea, why don't you > code it and submit it?" This is equally unhelpful. If it's a bad idea, why > should anyone code it? If it's a code idea, why does it matter who codes it, > as long as it's coded well? Because if it's a day of coding, you should just do it. If it's a 3 month project, you don't waste such time, and you should communicate it. The time factor is judged by folks who code for a living, and maybe it's a little high, but not too bad. I haven't seen this rule misapplied, but it's possible some may think so; they are most likely mis-estimating the scope of the work involved. I have a 3 day project in mind; I'm just going to code it (once I get finished with classes in 2 weeks); if it gets turned down, I'm a big boy, I'll get over it. If it was longer, I would bore you all with it. It's not, and I won't. ----------------------------+----------------------------------------------- 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 (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 19:27:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 2E82314C25 for ; Wed, 12 May 1999 19:27:35 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Wed, 12 May 1999 19:27:35 -0700 From: "David Schwartz" To: "Chuck Robey" Cc: Subject: RE: cvs commit: src/sys/pci pcisupport.c Date: Wed, 12 May 1999 19:27:34 -0700 Message-ID: <000001be9ce8$291f3790$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Because if it's a day of coding, you should just do it. If it's a 3 > month project, you don't waste such time, and you should communicate it. > The time factor is judged by folks who code for a living, and maybe it's > a little high, but not too bad. I haven't seen this rule misapplied, > but it's possible some may think so; they are most likely mis-estimating > the scope of the work involved. Believe it or not, good ideas can even come from people who can't code at all, and the ideas are just as good. Slapping these people down just ensures they don't contribute in the future. Now if their ideas genuinely are bad, you are more than welcome to slap them down as much as you wish. If that means they don't contribute more bad ideas in the future, so much the better. Heck, it even may save you the idea of having to explain why the bad idea is, in fact, bad. But "if it's such a good idea, why don't you code it?" doesn't fall into any of these categories. It's one of those "that's what you think" type arguments that serves as an excuse to ignore the merits of the other side's case. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 19:40: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 491E615221 for ; Wed, 12 May 1999 19:39:59 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id CAA11000; Thu, 13 May 1999 02:38:30 GMT Message-Id: <199905130238.CAA11000@chandra.eatell.msr.prug.or.jp> To: Dag-Erling Smorgrav Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "12 May 1999 20:42:49 +0200." Date: Thu, 13 May 1999 11:38:29 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On whose authority do you say that? Garrett is a core team member. I heard from Asami-san, Any voting not yet for new-bus. After that, "new-bus patch" merge is decided. new-bus merge is core decision, but "drop static configration", ... these are not yet voted. > Then explain to us why newbus is wrong and why the 4.4BSD scheme is > right. Because, you are misunderstanding 4.4BSD scheme (and newconfig). -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 May 12 19:59:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 871551528F for ; Wed, 12 May 1999 19:59:00 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id VAA11540 for current@freebsd.org; Wed, 12 May 1999 21:58:59 -0500 (CDT) From: Kevin Day Message-Id: <199905130258.VAA11540@home.dragondata.com> Subject: -current page fault at 0xdeadc0de To: current@freebsd.org Date: Wed, 12 May 1999 21:58:59 -0500 (CDT) 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 I had two systems reboot at nearly the same time. (30 seconds apart), and are completely unrelated. One system was running 2.2.8, and my core file presents me with this: su-2.02# gdb -k GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc. (kgdb) exec-file kernel.0 (kgdb) symbol-file kernel.0.debug Reading symbols from kernel.0.debug...done. (kgdb) core-file vmcore.0 IdlePTD 24a000 current pcb at 202bfc #0 0x14 in ?? () (kgdb) bt #0 0x14 in ?? () #1 0x34000004 in ?? () Cannot access memory at address 0x7205c76a. Were things just trashed, or am I doing something wrong? The other system was running -current, and gives me: su-2.02# gdb -k GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc. (kgdb) exec-file kernel.2 (kgdb) symbol-file kernel.2.debug Reading symbols from kernel.2.debug...done. (kgdb) core-file vmcore.2 IdlePTD 3096576 initial pcb at 27ea40 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xdeadc0de fault code = supervisor read, page not present instruction pointer = 0x8:0xdeadc0de stack pointer = 0x10:0xcb4adec0 frame pointer = 0x10:0xcb4adefc 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 = 40969 (eggdrop) interrupt mask = trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0xdeadc126 fault code = supervisor read, page not present instruction pointer = 0x8:0xc018e3d8 stack pointer = 0x10:0xcb4ad91c frame pointer = 0x10:0xcb4ad93c 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 = 40969 (eggdrop) interrupt mask = trap number = 12 panic: page fault dumping to dev 20001, offset 467137 dump 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:288 288 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:288 #1 0xc0145755 in panic () at ../../kern/kern_shutdown.c:450 #2 0xc020e9e2 in trap_fatal (frame=0xcb4ad8dc, eva=3735929126) at ../../i386/i386/trap.c:917 #3 0xc020e695 in trap_pfault (frame=0xcb4ad8dc, usermode=0, eva=3735929126) at ../../i386/i386/trap.c:810 #4 0xc020e2d7 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = 0, tf_ebp = -884287172, tf_isp = -884287224, tf_ebx = 16384, tf_edx = -559038242, tf_ecx = -1059309536, tf_eax = -1053816960, tf_trapno = 12, tf_err = 0, tf_eip = -1072110632, tf_cs = 8, tf_eflags = 66182, tf_esp = -1062703744, tf_ss = -911937724}) at ../../i386/i386/trap.c:436 (kgdb) Not exactly a lot to go on... Mean anything to anyone? Any more info I can provide? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 20:12:16 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 0D77914DAB for ; Wed, 12 May 1999 20:12:14 -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 WAA18061; Wed, 12 May 1999 22:35:07 -0500 (EST) Date: Wed, 12 May 1999 22:35:06 -0500 (EST) From: Alfred Perlstein To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@FreeBSD.ORG Subject: Re: Some interrupt bogons still around. In-Reply-To: <199905130212.KAA27892@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 On Thu, 13 May 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > An old 486 of mine still cant see its IDE driver with versions of ata-all.c > later than 1.8, and my soundcard (PAS16) still doesn't seem to generate > interrupts since the nexus stuff went in. my stock SB16 + freebsd+x11amp hasn't worked right since newbus. sound skips quite a bit. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 20:19:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (Postfix) with ESMTP id C8F2D14F8F for ; Wed, 12 May 1999 20:19:33 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from william (usr1-43.cybcon.com [205.147.75.44]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id UAA01480 for ; Wed, 12 May 1999 20:19:32 -0700 (PDT) From: "William Woods" To: "FreeBSD Current" Subject: current on a laptop... Date: Wed, 12 May 1999 20:19:20 -0700 Message-ID: <000001be9cef$64202e60$2c4b93cd@william> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am haveing a bear of a time getting pcmcia cards to work in 3.1-Stable and was wondering how well current performs with these.....I have current running on a few desktop systems here so running it is no prob......reccomendations? William To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 21:49:39 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 68EB314BE1 for ; Wed, 12 May 1999 21:49: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 OAA04435 for ; Thu, 13 May 1999 14:19:33 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA30408 for FreeBSD-current@FreeBSD.ORG; Thu, 13 May 1999 14:19:23 +0930 (CST) Date: Thu, 13 May 1999 14:19:23 +0930 From: Greg Lehey To: FreeBSD current users Subject: Repeated I/O errors in 3.2-BETA Message-ID: <19990513141923.K89091@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i 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 I've had a couple of these in a 3.2-BETA box today: May 13 14:11:51 daemon /kernel: spec_getpages: I/O read failure: (error code=16) May 13 14:11:57 daemon /kernel: size: 65536, resid: 65536, a_count: 65536, valid: 0x0 May 13 14:11:57 daemon /kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 16 After that, the system is effectively dead. This is the same system I normally run -CURRENT on, so it's not specifically a hardware error. It's a pity that the message doesn't specify the device, but I assume it has to be the swap partition. There aren't any other error messages. error appears to be bp->b_error, which means it's an EBUSY, which is puzzling enough as it is. 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 May 12 21:54:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id 6244914BE1 for ; Wed, 12 May 1999 21:54:13 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem10.masternet.it [194.184.65.20]) by scotty.masternet.it (8.9.3/8.9.2) with SMTP id GAA07999; Thu, 13 May 1999 06:53:59 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990513062307.016d0f10@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 13 May 1999 06:51:42 +0200 To: "Jordan K. Hubbard" From: Gianmarco Giovannelli Subject: stay -current without skill in debugging (was: panic !) Cc: current@freebsd.org In-Reply-To: <66106.926546538@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12/05/99, you wrote: >> Pardon, but I am not be able to figure by myself what you asked to me... >> If you can explain me step by step in a newbie way I can do everything ... >> The crashes is easily reproducible... > >No offense, but are you sure you should even be running -current? A >certain amount of skill in doing such diagnosis is generally >considered mandatory for people running it, even though many people >who shouldn't be doing so for that reason still do it. :) No offense surely, but I have been running -current in this (and others with Libretto too) box since 2.2-current, in true, without too much trouble, and I am survived to a lots of nasty things in the meantime. I have reinstalled this box from cdrom only a couple of time. because I usually use cvsup (and make world) to stay in sync (my cvs tree is at 194.184.65.3 , cvsup.masternet.it). I don't know too much (nothing !?) of kernel debugging, but I have learn surely in these years how survive in case of the most common problems with it (-current). Let's say I am learning how to become an hacker, but I do it very slowly, even if I am confident for the future :-) and so for the moment my function is still only "bug advisor" :-) Thanks for your kind reply. Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 21:56:58 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 505E314BE1 for ; Wed, 12 May 1999 21:56:57 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA68091; Wed, 12 May 1999 21:56:53 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Gianmarco Giovannelli Cc: current@freebsd.org Subject: Re: stay -current without skill in debugging (was: panic !) In-reply-to: Your message of "Thu, 13 May 1999 06:51:42 +0200." <4.1.19990513062307.016d0f10@194.184.65.4> Date: Wed, 12 May 1999 21:56:53 -0700 Message-ID: <68087.926571413@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No offense surely, but I have been running -current in this (and others > with Libretto too) box since 2.2-current, in true, without too much > trouble, and I am survived to a lots of nasty things in the meantime. I This only constitutes a confession on your part that you've survived by pure luck up to now, I'm afraid. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 22:23:55 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 D58EE14D91 for ; Wed, 12 May 1999 22:23:50 -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 OAA04518; Thu, 13 May 1999 14:53:48 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA30757; Thu, 13 May 1999 14:53:47 +0930 (CST) Date: Thu, 13 May 1999 14:53:46 +0930 From: Greg Lehey To: "Jordan K. Hubbard" Cc: Gianmarco Giovannelli , current@FreeBSD.ORG Subject: Re: stay -current without skill in debugging (was: panic !) Message-ID: <19990513145345.L89091@freebie.lemis.com> References: <4.1.19990513062307.016d0f10@194.184.65.4> <68087.926571413@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <68087.926571413@zippy.cdrom.com>; from Jordan K. Hubbard on Wed, May 12, 1999 at 09:56:53PM -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, 12 May 1999 at 21:56:53 -0700, Jordan K. Hubbard wrote: >> No offense surely, but I have been running -current in this (and others >> with Libretto too) box since 2.2-current, in true, without too much >> trouble, and I am survived to a lots of nasty things in the meantime. I > > This only constitutes a confession on your part that you've survived > by pure luck up to now, I'm afraid. :-) It's certainly not because of the helping hands that have been extended to him. 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 May 12 22:27:56 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 3F94714D91 for ; Wed, 12 May 1999 22:27:52 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA68430; Wed, 12 May 1999 22:27:38 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Greg Lehey Cc: Gianmarco Giovannelli , current@FreeBSD.ORG Subject: Re: stay -current without skill in debugging (was: panic !) In-reply-to: Your message of "Thu, 13 May 1999 14:53:46 +0930." <19990513145345.L89091@freebie.lemis.com> Date: Wed, 12 May 1999 22:27:38 -0700 Message-ID: <68427.926573258@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's certainly not because of the helping hands that have been > extended to him. -current doesn't come with seat belts or air bags. If you're looking for a helping hand rather than a ranger combat course where people just boot you in the ass whenever you fall into the mud, go next door to -stable please. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 22:28: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 CB105155BD for ; Wed, 12 May 1999 22:28:32 -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 OAA04559 for ; Thu, 13 May 1999 14:58:31 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA30806 for FreeBSD-current@FreeBSD.ORG; Thu, 13 May 1999 14:58:31 +0930 (CST) Date: Thu, 13 May 1999 14:58:31 +0930 From: Greg Lehey To: FreeBSD current users Subject: Solved: Repeated I/O errors in 3.2-BETA Message-ID: <19990513145831.A30789@freebie.lemis.com> References: <19990513141923.K89091@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990513141923.K89091@freebie.lemis.com>; from Greg Lehey on Thu, May 13, 1999 at 02:19:23PM +0930 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 Thursday, 13 May 1999 at 14:19:23 +0930, Greg Lehey wrote: > I've had a couple of these in a 3.2-BETA box today: > > May 13 14:11:51 daemon /kernel: spec_getpages: I/O read failure: (error code=16) > May 13 14:11:57 daemon /kernel: size: 65536, resid: 65536, a_count: 65536, valid: 0x0 > May 13 14:11:57 daemon /kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 16 > > After that, the system is effectively dead. This is the same system I > normally run -CURRENT on, so it's not specifically a hardware error. > It's a pity that the message doesn't specify the device, but I assume > it has to be the swap partition. There aren't any other error > messages. error appears to be bp->b_error, which means it's an EBUSY, > which is puzzling enough as it is. Well, it looks as if it's a dying disk. Sorry for the false alarm. 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 May 12 22:29:50 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 767CC155B0 for ; Wed, 12 May 1999 22:29:38 -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 XAA42247; Wed, 12 May 1999 23:28:40 -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 XAA26354; Wed, 12 May 1999 23:29:10 -0600 (MDT) Message-Id: <199905130529.XAA26354@harmony.village.org> To: Noriyuki Soda Subject: Re: cvs commit: src/sys/pci pcisupport.c Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 12 May 1999 18:01:35 +0900." <199905120901.SAA04493@srapc288.sra.co.jp> References: <199905120901.SAA04493@srapc288.sra.co.jp> Date: Wed, 12 May 1999 23:29:10 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905120901.SAA04493@srapc288.sra.co.jp> Noriyuki Soda writes: : This reminds me another ugly kluge in sys/pccard/i82365.h: : #define PCIC_INDEX_0 0x3E0 : #define PCIC_INDEX_1 (PCIC_INDEX_0 + 2) : This is the way what some clever FreeBSD people saids "right" to : Nakagawa-san, though Nakagawa-san never agreed that it is right, and : rather likes the newconfig way like below: : pcic0 at isa? port 0x3e0 : pcic1 at isa? port 0x3e2 : pcic* at pci? : pcic* at isapnp? : It is apparent which is better and cleaner for me. But perhaps you do : not agree with me. :-) This is a horrible kludge (eg what is in FreeBSD right now is bogus and truely evil). I like the way that newconfig attaches things, which is why I'm currently reworking the pccard code. Actually, I'd rather junk most/all of the code that is there now. The code was good for the time, but now it has been overtaken by events. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 22:44:58 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 D3A9614C57 for ; Wed, 12 May 1999 22:44:56 -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 XAA42276; Wed, 12 May 1999 23:43:59 -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 XAA26417; Wed, 12 May 1999 23:44:30 -0600 (MDT) Message-Id: <199905130544.XAA26417@harmony.village.org> To: mi@aldan.algebra.com Subject: Re: cvs commit: src/sys/pci pcisupport.c Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 12 May 1999 16:48:39 EDT." <199905122048.QAA72725@misha.cisco.com> References: <199905122048.QAA72725@misha.cisco.com> Date: Wed, 12 May 1999 23:44:30 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905122048.QAA72725@misha.cisco.com> Mikhail Teterin writes: : Perhaps, the newbus vs. newconfig discussion can be summarized to both : sides' satisfaction offline and then presented to the rest of the world? It is my impression that the language barrier has made this discussion harder to follow. In all the discussions I've seen, both here and elsewhere, it seems like the two sides are talking past one another. That's one reason I really like Doug's idea for a meeting at Usenix (sadly, I'm unable to attend). This isn't a simple issue, and there are many subtle advantages and disadvantages to both systems which are hard to convey in email... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 12 23:46:32 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 1E95615437 for ; Wed, 12 May 1999 23:46:28 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA42355; Thu, 13 May 1999 00:45:31 -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 AAA26543; Thu, 13 May 1999 00:46:02 -0600 (MDT) Message-Id: <199905130646.AAA26543@harmony.village.org> To: "William Woods" Subject: Re: current on a laptop... Cc: "FreeBSD Current" In-reply-to: Your message of "Wed, 12 May 1999 20:19:20 PDT." <000001be9cef$64202e60$2c4b93cd@william> References: <000001be9cef$64202e60$2c4b93cd@william> Date: Thu, 13 May 1999 00:46:01 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <000001be9cef$64202e60$2c4b93cd@william> "William Woods" writes: : I am haveing a bear of a time getting pcmcia cards to work in 3.1-Stable and : was wondering how well current performs with these..... Hmmm. I don't think that -current will help, and may even hurt. What kind of laptop? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 0: 3:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id D4FEC14D8D for ; Thu, 13 May 1999 00:03:02 -0700 (PDT) (envelope-from geoff@rucus.ru.ac.za) Received: (qmail 64117 invoked by uid 268); 13 May 1999 07:03:04 -0000 Message-ID: <19990513070304.64116.qmail@rucus.ru.ac.za> Subject: Re: X crashing under current In-Reply-To: from Kenneth Wayne Culver at "May 12, 1999 2:54:36 pm" To: culverk@wam.umd.edu (Kenneth Wayne Culver) Date: Thu, 13 May 1999 09:03:04 +0200 (SAST) Cc: current@freebsd.org Reply-To: "Geoff Rehmet" From: "Geoff Rehmet" 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 Kenneth Wayne Culver writes : > I also am experiencing a kernel panic whenever I start X using today's > kernel. Thanks > > After powering off and on again, I am now able to get a new kernel up, but now it boots happily, so I have no crash dumps, no traces, nothing to show for my story. I re-CVSuped this morning, and am now working again. (Trust me not to enable crash dumps when I installed my system - back in the old days, it was default!!!!) Anyhow, I'm now waiting to catch the bastard when it falls! Geoff. -- Geoff Rehmet, The Internet Solution geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 0:10:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id F335414F53 for ; Thu, 13 May 1999 00:10:08 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id JAA65517; Thu, 13 May 1999 09:10:06 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id JAA08253; Thu, 13 May 1999 09:10:05 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905130710.JAA08253@greenpeace.grondar.za> To: "William Woods" Cc: "FreeBSD Current" Subject: Re: current on a laptop... In-Reply-To: Your message of " Wed, 12 May 1999 20:19:20 MST." <000001be9cef$64202e60$2c4b93cd@william> References: <000001be9cef$64202e60$2c4b93cd@william> Date: Thu, 13 May 1999 09:10:04 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "William Woods" wrote: > I am haveing a bear of a time getting pcmcia cards to work in 3.1-Stable and > was wondering how well current performs with these.....I have current > running on a few desktop systems here so running it is no > prob......reccomendations? If you have no problem dealing with the ups-and-downs of CURRENT, then go for it. It is working very nicely on my Libretto 110CT. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 0:27:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 1FE2D14F53 for ; Thu, 13 May 1999 00:27:40 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id QAA02355; Thu, 13 May 1999 16:27:12 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: peter@netplex.com.au Cc: soda@sra.co.jp, current@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: cvs commit: src/sys/pci pcisupport.c From: Tomoaki NISHIYAMA In-Reply-To: <19990512222414.E2DDA1F58@spinner.netplex.com.au> References: <19990512222414.E2DDA1F58@spinner.netplex.com.au> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990513162711O.tomoaki@moss.nibb.ac.jp> Date: Thu, 13 May 1999 16:27:11 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 45 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Peter Wemm Subject: Re: cvs commit: src/sys/pci pcisupport.c Date: Thu, 13 May 1999 06:24:12 +0800 Message-ID: <19990512222414.E2DDA1F58@spinner.netplex.com.au> peter> What on earth is the locator stuff for? Why can't you use plain text? peter> How does 'iobase 0x280' become '640,0,0,0,9,-1,-1,0,1,0'?? This should be changed in the future. I would say for this point "Yes, there are weaknesses still, but that is because it isn't quite finished and is evolving still." I don't think it impossible to make it work dconfig load "ne4 at isa0 iobase 0x280 irq 9" dconfig unload ne4 We have just made it work, before making it look cool. peter> I prefer just: peter> device pcic0 at isa? port 0x3e0 peter> device pcic1 at isa? port 0x3e2 peter> in a static kernel config file, or: peter> pcic0 port 0x3e0 peter> pcic1 port 0x3e2 peter> in /boot/isa.conf. Or: peter> # sethint pcic0 at isa port 0x3e0 peter> # sethint pcic1 at isa port 0x3e2 peter> # kldload pcic.ko peter> .. to load pcic to look at isapnp, pci and those two isa ports. or: peter> # kldload pcic.ko peter> .. to load pcic and look at pci and isapnp if present. peter> peter> If the driver writer decides there is a significant amount of code in peter> bus dependent modules that it is worth splitting pcic.ko itno pcic_isa.ko, peter> pcic_pci.ko, pcic_pnp.ko and pcic_common.ko, then this works best: peter> # kldload pcic_pci.ko peter> .. to load the pci and common parts, and cause a reprobe. Yes, it does seem cool. But don't you think it even better to simply tell the system that I want pcic on pci not knowing the filename (whether it was split into three files, or just one file)? # dconfig load pcic? at pci? -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 0:51:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id DD83314D5B for ; Thu, 13 May 1999 00:51:12 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id QAA02437; Thu, 13 May 1999 16:50:59 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: jkh@zippy.cdrom.com Cc: soda@sra.co.jp, dfr@nlsystems.com, current@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: cvs commit: src/sys/pci pcisupport.c From: Tomoaki NISHIYAMA In-Reply-To: <67065.926554325@zippy.cdrom.com> References: <67065.926554325@zippy.cdrom.com> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990513165059Z.tomoaki@moss.nibb.ac.jp> Date: Thu, 13 May 1999 16:50:59 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 38 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Jordan K. Hubbard" Subject: Re: cvs commit: src/sys/pci pcisupport.c Date: Wed, 12 May 1999 17:12:05 -0700 Message-ID: <67065.926554325@zippy.cdrom.com> jkh> I have seen a lot of arguing about technical merits and decisions made jkh> by the core team, but I have yet to see any constructive comments jkh> about fixing the communication problems which led to this decision. I think the best way to fix the communication problem is to discuss on the technical merits, to understand what you think and to make you understand what we think. If the explanation of the code is too short ask questions what is not understood. jkh> Evaluating technology is a jkh> question of deciding which code is both superior AND has the best jkh> longevity, longevity being a more difficult equation which combines jkh> the history of the developers involved and how effective your jkh> communications with them are. In this case, I don't believe jkh> communications are effective and that kills newconfig just as jkh> thoroughly as having the code be a total mess; I think I've pointed jkh> this out several times now. Yes, longevity is an important thing. But it is not only the matter of communication, but it depends on the fundamental design, and on what principle the code is written. Once you understand the fundamental design and the principle it is based on, you will be able to develop them further. Thus we want you understand the design and principle of newconfig, through the code and discussion. You can decide to merge them after understanding the principle. It's not a good idea to reject something without understanding, as to merge something without understanding. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 2:42:30 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 57A2315498 for ; Thu, 13 May 1999 02:42:26 -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 KAA01525; Thu, 13 May 1999 10:41:23 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Thu, 13 May 1999 10:41:23 +0100 (BST) From: Doug Rabson To: Noriyuki Soda Cc: current@freebsd.org Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905120926.SAA19601@srapc342.sra.co.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 Wed, 12 May 1999, Noriyuki Soda wrote: > > > BTW, there are many fundamental design flaws in new-bus, so I don't > > > think new-bus is comparable with newconfig, yet, even if priority > > > probe is implemented. For example: > > > > I'm not going to reply to these points as I suspect it will lead to a > > pointless flame thread. I would prefer to discuss these issues in person > > at Usenix. > > I agree that this is better way to solve the conflicts between new-bus > and newconfig. Although I wondered why FreeBSD's core decide to choose > new-bus before Usenix. As I suspected, a massive flamewar has happened while I've been away. I don't think I have anything to add to what has been said (and I certainly don't want to continue a flamewar). Can people please just drop the subject until after Usenix. This kind of flamewar is too upsetting (to me anyway) and just makes it harder to have a useful face-to-face discussion. -- 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 Thu May 13 2:44:58 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 4296A15498 for ; Thu, 13 May 1999 02:44:55 -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 MAA18139; Thu, 13 May 1999 12:44:47 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 34DC21F73; Thu, 13 May 1999 12:44:49 +0300 (EEST) Date: Thu, 13 May 1999 12:44:49 +0300 From: Vallo Kallaste To: Gianmarco Giovannelli Cc: current@FreeBSD.ORG Subject: Re: panic ! panic ! panic ! Message-ID: <19990513124449.B11458@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <5817.926524559@critter.freebsd.dk> <4.1.19990512182248.009bda80@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <4.1.19990512182248.009bda80@194.184.65.4>; from Gianmarco Giovannelli on Wed, May 12, 1999 at 06:41:15PM +0200 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 12, 1999 at 06:41:15PM +0200, Gianmarco Giovannelli wrote: > Ok... it's a bit long ... (Tell me there isn't a command to write the trace > output on a disk :-) > > After the panic make by "screen" ... > >trace > Stopped at ttyflush+0x48: movl 0x14(%eax), %eax [chop] > A nightmare ! :-) You can enable serial console for one of your serial ports, preferably sio0 (COM1) and boot with -h (check /usr/src/sys/i386/conf/LINT). Then you can capture all such things if you have null-modem cable connected to another computer and some terminal program running on the port the cable is connected. Otherwise you can use true terminal. Default connection speed is 9600 bps and no extraordinary settings, 8N1. -- 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 Thu May 13 3:26:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from mhub2.tc.umn.edu (mhub2.tc.umn.edu [128.101.131.42]) by hub.freebsd.org (Postfix) with ESMTP id 822AF15371 for ; Thu, 13 May 1999 03:26:21 -0700 (PDT) (envelope-from adkin003@tc.umn.edu) Received: from pub56k-17-128.dialup.umn.edu by mhub2.tc.umn.edu; Thu, 13 May 1999 05:25:57 -0500 Date: Thu, 13 May 1999 05:25:54 -0500 (CDT) From: dave adkins To: Geoff Rehmet Cc: "'current@freebsd.org'" Subject: Re: Today's kernel crashes on starting X In-Reply-To: <3D5EC7D2992BD211A95600A0C9CE047F0308D99F@isjhbex01.is.co.za> 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, 12 May 1999, Geoff Rehmet wrote: > Date: Wed, 12 May 1999 14:35:54 +0200 > From: Geoff Rehmet > To: "'current@freebsd.org'" > Subject: Today's kernel crashes on starting X > > I'm currently running into a problem, that when I start my system, > it spontaneously reboots when starting X. Has anyone else run into > this? > > -- > Geoff Rehmet, The Internet Solution - Infrastructure > tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 > email: geoffr@is.co.za > URL: http://www.is.co.za > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > I think it's the recent dev_t changes causing problems. I haven't tracked it any further. Try changing: #define DEVT_FACIST 1 in kern/kern_conf.c to #undef DEVT_FACIST It has fixed my X crash. dave adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 4: 6:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id E4B1C14CC1 for ; Thu, 13 May 1999 04:06:24 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id NAA02041 for ; Thu, 13 May 1999 13:06:23 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id NAA09461 for ; Thu, 13 May 1999 13:06:19 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: make world croaks in perl ?? From: Poul-Henning Kamp Date: Thu, 13 May 1999 13:06:19 +0200 Message-ID: <9459.926593579@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anybody but me seeing this ? ===> gnu/usr.bin/perl ===> gnu/usr.bin/perl/libperl ===> gnu/usr.bin/perl/miniperl sh config_h.sh Extracting config.h (with variable substitutions) cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/p erl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/i nclude -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/miniperlm ain.c cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/p erl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/i nclude -static -o miniperl miniperlmain.o -lperl -lm -lcrypt ===> gnu/usr.bin/perl/perl make: don't know how to make writemain.sh. Stop *** Error code 2 -- 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 May 13 4: 9: 4 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 A4E2B14DA2 for ; Thu, 13 May 1999 04:08:55 -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 2.12 #1) id 10htM9-000HVL-00; Thu, 13 May 1999 13:08:49 +0200 From: Sheldon Hearn To: Geoff Rehmet Cc: "'current@freebsd.org'" Subject: Re: Today's kernel crashes on starting X In-reply-to: Your message of "Wed, 12 May 1999 14:35:54 +0200." <3D5EC7D2992BD211A95600A0C9CE047F0308D99F@isjhbex01.is.co.za> Date: Thu, 13 May 1999 13:08:49 +0200 Message-ID: <67290.926593729@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 May 1999 14:35:54 +0200, Geoff Rehmet wrote: > I'm currently running into a problem, that when I start my system, > it spontaneously reboots when starting X. Has anyone else run into > this? Hi Geoff, I notice you've had a lot of responses confirming similar problems with recent kernels, so I thought the following might be useful to you. I used sources supped around 07H00 GMT 12/05/99 and have not seen the problem you describe. Therefore, you'll probably need to provide more details on your kernel configuration. You may also want to look for clues in /etc/messages and .xsession-errors etc. Perhaps you'll be able to find something that you have in common with the other folks having hassles. Later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 4:13:58 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 1F77D14CC1 for ; Thu, 13 May 1999 04:13:53 -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 2.12 #1) id 10htOB-000HWj-00; Thu, 13 May 1999 13:10:55 +0200 From: Sheldon Hearn To: Dag-Erling Smorgrav Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive In-reply-to: Your message of "12 May 1999 16:10:11 +0200." Date: Thu, 13 May 1999 13:10:55 +0200 Message-ID: <67376.926593855@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12 May 1999 16:10:11 +0200, Dag-Erling Smorgrav wrote: > OBTW, the following comment in LINT is a little weird: > > # You only need one "controller ata0" for it to find all > # PCI devices on modern machines. *chuckle* My misreading of that comment led me to remove all my atadisk* devices, resulting in a "can't mount root" panic on reboot. :-) I admit, I came up with a particularly stupid interpretation, but it's poorly worded nonetheless. Later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 4:18: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 4F0A114CC1 for ; Thu, 13 May 1999 04:17:52 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id NAA02181; Thu, 13 May 1999 13:17:50 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id NAA09506; Thu, 13 May 1999 13:17:41 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Sheldon Hearn Cc: Geoff Rehmet , "'current@freebsd.org'" Subject: Re: Today's kernel crashes on starting X In-reply-to: Your message of "Thu, 13 May 1999 13:08:49 +0200." <67290.926593729@axl.noc.iafrica.com> Date: Thu, 13 May 1999 13:17:41 +0200 Message-ID: <9504.926594261@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think the fix to the device-pager earlier today may have take care of this one (Many thanks to luoqi!) Poul-Henning In message <67290.926593729@axl.noc.iafrica.com>, Sheldon Hearn writes: > > >On Wed, 12 May 1999 14:35:54 +0200, Geoff Rehmet wrote: > >> I'm currently running into a problem, that when I start my system, >> it spontaneously reboots when starting X. Has anyone else run into >> this? > >Hi Geoff, > >I notice you've had a lot of responses confirming similar problems with >recent kernels, so I thought the following might be useful to you. > >I used sources supped around 07H00 GMT 12/05/99 and have not seen the >problem you describe. Therefore, you'll probably need to provide more >details on your kernel configuration. You may also want to look for >clues in /etc/messages and .xsession-errors etc. > >Perhaps you'll be able to find something that you have in common with >the other folks having hassles. > >Later, >Sheldon. > > >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 May 13 5:15:33 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 3AFD814DD9 for ; Thu, 13 May 1999 05:15:27 -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 2.12 #1) id 10huO0-000Hgz-00; Thu, 13 May 1999 14:14:48 +0200 From: Sheldon Hearn To: Gianmarco Giovannelli Cc: "Jordan K. Hubbard" , current@freebsd.org Subject: Re: stay -current without skill in debugging (was: panic !) In-reply-to: Your message of "Thu, 13 May 1999 06:51:42 +0200." <4.1.19990513062307.016d0f10@194.184.65.4> Date: Thu, 13 May 1999 14:14:47 +0200 Message-ID: <68012.926597687@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 May 1999 06:51:42 +0200, Gianmarco Giovannelli wrote: > Let's say I am learning how to become an hacker, but I do it very slowly, > even if I am confident for the future :-) and so for the moment my function > is still only "bug advisor" :-) Hi Gianmarco, Since you're learning, you will probably find the FreeBSD Handbook chapter on Kernel Debugging most useful. Also, Greg Lehey posted a cute HOWTO on taking panic dumps. I think the details are included in the handbook chapter I've suggested, but I'd suggest starting with his message, and then hitting the handbook if you don't understand it (you did say you're learning, after all). You can get Greg's HOWTO at (all on one line, no breaks): http://www.freebsd.org/cgi/getmsg.cgi?fetch=615265+0+archive/1999/freebsd-hackers/19990321.freebsd-hackers I'm sure you understand why Jordan responded the way he did, since you've been involved with CURRENT for so long. :-) Later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 5:48:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id B1B4514C48; Thu, 13 May 1999 05:48:22 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id OAA10194; Thu, 13 May 1999 14:08:32 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id OAA12011; Thu, 13 May 1999 14:13:32 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905131213.OAA12011@yedi.iaf.nl> Subject: Re: de driver problem In-Reply-To: <199905121824.UAA04901@greenpeace.grondar.za> from Mark Murray at "May 12, 1999 8:24:10 pm" To: mark@grondar.za (Mark Murray) Date: Thu, 13 May 1999 14:13:32 +0200 (CEST) Cc: dfr@nlsystems.com, khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Mark Murray wrote ... > Wilko Bulte wrote: > > PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl > > Writing Makefile for DynaLoader > > ==> Your Makefile has been rebuilt. <== > > ==> Please rerun the make command. <== > > false > > false: not found > > *** Error code 1 > > I periodically see this one reported, and It is always repaired > by the reporter making sure their tree is _really_ clean before > doing a make world. "Really clean" means "make cleandir" _twice_, > and complete removal of the contents of /usr/obj. _Then_ cvsup. > I prefer to usr CVS checkout, as it shows all the differences and > other turds in my source tree. Unfortunately: Extracting pod2man (with variable substitutions) cd ext/B; miniperl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib Makefile.PL LINKTYPE=dynamic INSTALLDIRS=perl PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl LIBS="-lperl" INSTALLMAN3DIR=/usr/obj/usr/src/tmp/usr/share/perl/man3 INST_LIB=/usr/obj/usr/src/gnu/usr.bin/perl/perl/build/B INST_ARCHLIB=/usr/obj/usr/src/gnu/usr.bin/perl/perl/build/B ; make -B config PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl Writing Makefile for DynaLoader ==> Your Makefile has been rebuilt. <== ==> Please rerun the make command. <== false false: not found *** Error code 1 even after rm -rf /usr/obj | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 5:48:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 5F36514D3E; Thu, 13 May 1999 05:48:22 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id OAA10195; Thu, 13 May 1999 14:08:33 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA04213; Thu, 13 May 1999 00:02:25 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905122202.AAA04213@yedi.iaf.nl> Subject: Re: de driver problem In-Reply-To: <199905122044.NAA03768@gndrsh.aac.dev.com> from "Rodney W. Grimes" at "May 12, 1999 1:44:30 pm" To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Thu, 13 May 1999 00:02:25 +0200 (CEST) Cc: mark@grondar.za, dfr@nlsystems.com, khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Rodney W. Grimes wrote ... > > Wilko Bulte wrote: > > > PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl > > > Writing Makefile for DynaLoader > > > ==> Your Makefile has been rebuilt. <== > > > ==> Please rerun the make command. <== > > > false > > > false: not found > > > *** Error code 1 > > > > I periodically see this one reported, and It is always repaired > > by the reporter making sure their tree is _really_ clean before > > doing a make world. "Really clean" means "make cleandir" _twice_, > > This indicates to me, the original author of ``cleandir'', that > something has broken the functionality that it had. This something > is more than likely the removal of code similiar to: > > cd /usr/obj/{.CURDIR}; chflags -R noschg tmp; rm -rf *; > > before the equiv of: > cd {.CURDIR}; ${make} clean > > > and complete removal of the contents of /usr/obj. _Then_ cvsup. > > I prefer to usr CVS checkout, as it shows all the differences and > > other turds in my source tree. > > If ``make cleandir'' is leaving some cruft in any form behind anyplace > in the build tree things are broken. Sounds very reasonable to me. Running the same command twice to get things really clean sounds suspicious ;-) In any case: I'm rebuilding now after a cvsup && chflags -R noschg /usr/obj/* && rm -rf /usr/obj/* We'll see what happens next. | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 6:43:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id AF16C14D4C for ; Thu, 13 May 1999 06:43:43 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-14-21.camtech.net.au [203.55.242.149]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id XAA09678; Thu, 13 May 1999 23:18:23 +0930 (CST) Message-ID: <373AD739.6D8C3038@camtech.com.au> Date: Thu, 13 May 1999 23:14:25 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: camel@avias.com Cc: current@FreeBSD.ORG, "Steve O'Hara-Smith" , Kazutaka YOKOTA Subject: Re: problem with NewScroll Mouse, etc References: <99051214502200.06507@camel.avias.com> Content-Type: multipart/mixed; boundary="------------6E317355829FE554859AFF70" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------6E317355829FE554859AFF70 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Moused and XFree86 3.3.3.1 dont support a particular new type of mouse. This is the PS/2 Intellimouse clone. (I'm note sure if 'real' MicroSoft Intellimice work ??). My mouse is such a clone and behaves the same as you are saying but works fine under Windows 95 with the PS/2 mouse driver. Someone who was interested in this when I complained about my mouse was Kazutaka Yokota who replied to me with the attached message. Ilya Naumov wrote: > > We , 12 may 1999, Steve O'Hara-Smith wrote: > > > > 1. something is wrong with psm0 driver. my Genius NewScroll PS/2 > > > mouse works > > > well, but in random moment when i touch the mouse kernel starts to > > > write to the > > > system log the following. > > > > > > Apr 29 11:55:58 camel /kernel: psmintr: out of sync (00c8 != 0008). > > > Apr 29 11:55:58 camel /kernel: psmintr: out of sync (00c0 != 0008). > > > > > > when it happens, mouse cursor moves, but buttons do not work. only > > > reboot solves this problem. > > even full restart of moused doesn't help. very strange bug. NewScroll seems to > be fully compatible with Microsoft PS/2 mouse protocol, and a problem with it > appears under FreeBSD only. > > -- > > sincerely, > ilya naumov (at work) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------6E317355829FE554859AFF70 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Received: by goliath (mbox thyerm) (with Cubic Circle's cucipop (v1.22 1998/04/11) Sun Apr 4 22:22:55 1999) X-From_: yokota@zodiac.mech.utsunomiya-u.ac.jp Sun Apr 4 21:49 CST 1999 Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id VAA16372 for ; Sun, 4 Apr 1999 21:49:50 +0930 (CST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:qeFa0aSmh8Yl69iIivs2SrX+YtpZdNr/@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id VAA12954 for ; Sun, 4 Apr 1999 21:14:12 +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 VAA13332; Sun, 4 Apr 1999 21:17:45 +0900 (JST) Message-Id: <199904041217.VAA13332@zodiac.mech.utsunomiya-u.ac.jp> To: thyerm@camtech.com.au cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: My mouse wont work properly. In-reply-to: Your message of "Sun, 04 Apr 1999 21:30:22 +0930." References: Date: Sun, 04 Apr 1999 21:17:44 +0900 From: Kazutaka YOKOTA Content-Type: text >I recently bought a PS/2 mouse that claims to be an Intellimouse (PS/2) >clone. It has two normal buttons and a roller wheel (that is the third >button as well). > >Anyway, this doesn't work with moused (which I know is based on the >XFree86 mouse code), and it doesn't work with XFree86 3.3.3.1 either. Well, moused was originally based on XFree86 code. However, the other way round is the case these days; XFree86 mouse code is based on moused code :-) >In both cases the application (moused or X) seems to think it is clicking >the left mouse button several times whenever I move the mouse up the >screen (Down the screen seems fine). > >The mouse is called "Laser Smart" (I think its made in China). > >Any ideas on how I can make this work ? > >My kernel probes it as: >psm0: model IntelliMouse, device ID 3 The mouse is certainly claiming to be IntelliMouse... Please carry out the following test and send me the result. 1. Become root. 2. Kill moused if it is running. 3. Capture the rest of the experiment by the `script' command. script _file_name_to_save_output_ 4. Run moused in the debug mode. moused -d -f -p /dev/psm0 -l 2 5. Don't move mouse, but click buttons in turn. You should see status output from moused. 6. Then, move mouse and turn it wheel. 7. Stop moused by hitting ^C. 8. Stop the script command by typing `exit'. Kazu --------------6E317355829FE554859AFF70-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 7:15:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-gw3adm.rcsntx.swbell.net (mail-gw3.rcsntx.swbell.net [151.164.30.53]) by hub.freebsd.org (Postfix) with ESMTP id A2EAF1501D; Thu, 13 May 1999 07:15:14 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ppp-207-193-13-90.hstntx.swbell.net [207.193.13.90]) by mail-gw3adm.rcsntx.swbell.net (8.8.5/8.8.5) with ESMTP id JAA10494; Thu, 13 May 1999 09:15:07 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id JAA19142; Thu, 13 May 1999 09:16:36 -0500 (CDT) (envelope-from chris) Date: Thu, 13 May 1999 09:16:35 -0500 From: Chris Costello To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: make world croaks in perl ?? Message-ID: <19990513091635.A18958@holly.dyndns.org> Reply-To: chris@calldei.com References: <9459.926593579@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.2i In-Reply-To: <9459.926593579@critter.freebsd.dk>; from Poul-Henning Kamp on Thu, May 13, 1999 at 01:06:19PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 13, 1999, Poul-Henning Kamp wrote: > ===> gnu/usr.bin/perl/perl > make: don't know how to make writemain.sh. Stop > *** Error code 2 "Me Too." Last night, probably around 11:30 PM CST, I found that error message waiting for me. -- Chris Costello What this country needs is a good five-cent microcomputer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 7:36:27 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 A88AC14C57 for ; Thu, 13 May 1999 07:36:10 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:AskTI5v2HAi8hVX38MJEbJ+hBGiywcim@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id XAA06547; Thu, 13 May 1999 23:35:17 +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 XAA01582; Thu, 13 May 1999 23:39:08 +0900 (JST) Message-Id: <199905131439.XAA01582@zodiac.mech.utsunomiya-u.ac.jp> To: camel@avias.com Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp In-reply-to: Your message of "Wed, 12 May 1999 12:52:40 +0400." <99051212592200.00491@camel.avias.com> References: <99051212592200.00491@camel.avias.com> Date: Thu, 13 May 1999 23:39:07 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >running FreeBSD 4.0-CURRENT i have encountered the following >problems: > >1. something is wrong with psm0 driver. my Genius NewScroll PS/2 mouse works ~~~~~~~~~~~~~~~~ Is this a different product than "NetScroll" or "NetMouse" from Genius? >well, but in random moment when i touch the mouse kernel starts to write to th >e >system log the following. > >Apr 29 11:55:58 camel /kernel: psmintr: out of sync (00c8 != 0008). >Apr 29 11:55:58 camel /kernel: psmintr: out of sync (00c0 != 0008). > >when it happens, mouse cursor moves, but buttons do not work. only >reboot solves this problem. this bug doesn't appear with Microsoft and >Hewlett-Packard mice. Hmm, if the mouse cursor moves, I would rather expect the left and right buttons work too. The roller or other switch which represent "Z" motion or "scroll" motion won't be detected, though... Anyway, there appears to be some sort of protocol mismatch. Would you please carry out the following test and send me the result, so that I can diagnose our problem? 1. Add the following lines to your kernel configuration files and rebuild the kernel. options PSM_DEBUG=2 options KBDIO_DEBUG=2 2. When booting the new kernel please give the -v option to get detailed reports during the system boot process. 3. Please send me the output from `dmesg' command after the system is fully up. (Please give the entire output :-) 4. Switch to an empty vty. Become root. 5. Kill `moused' if it is already running. 6. Capture the rest of the experiment by the `script' command. script _file_name_to_save_output_ 7. Run moused in the debug mode. moused -d -f -p /dev/psm0 -l 2 8. Don't move mouse, but click buttons in turn. You should see status output from moused. 9. Then, move mouse and turn its wheel. 10. Stop moused by hitting ^C. Then, Stop the script command by typing `exit'. By the way, is the power management enabled in your BIOS? Do you include the apm driver in your kernel? Does the problem occur after the system is resumed from system suspend or sleep mode by any chance? Do you use some sort of "console switch" in order to share a keyboard and a mouse among more than one computers? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 8:24:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from io.dyn.ez-ip.net (h24-66-174-118.xx.wave.shaw.ca [24.66.174.118]) by hub.freebsd.org (Postfix) with ESMTP id 9D25514DBB for ; Thu, 13 May 1999 08:24:41 -0700 (PDT) (envelope-from jake@io.dyn.ez-ip.net) Received: from io.dyn.ez-ip.net (jake@localhost [127.0.0.1]) by io.dyn.ez-ip.net (8.9.3/8.9.3) with ESMTP id IAA16651 for ; Thu, 13 May 1999 08:25:14 -0700 (PDT) (envelope-from jake@io.dyn.ez-ip.net) Message-Id: <199905131525.IAA16651@io.dyn.ez-ip.net> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: Some interrupt bogons still around. In-reply-to: Your message of "Wed, 12 May 1999 22:35:06 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 May 1999 08:25:14 -0700 From: Jake Burkholder Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > my stock SB16 + freebsd+x11amp hasn't worked right since newbus. > > sound skips quite a bit. > > > I noticed the same thing. /usr/ports/audio/gqmpeg is a nice player which uses mpg123 as the backend; it plays fine. I think it may have just have something to do with x11amp, which should probably be considered a bogon itself. All other sources of sound work fine, like fxtv. (I have the same sound card as you; pcm driver.) Jake -- Linux - Zealotry taken over the Edge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 8:55:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-185-206.res.iastate.edu (friley-185-206.res.iastate.edu [129.186.185.206]) by hub.freebsd.org (Postfix) with ESMTP id 9B2AC14DB6 for ; Thu, 13 May 1999 08:55:12 -0700 (PDT) (envelope-from cc@137.org) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by friley-185-206.res.iastate.edu (Postfix) with ESMTP id D321437; Thu, 13 May 1999 09:55:10 -0600 (CST) Received: from friley-185-205.res.iastate.edu (localhost [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id 44B75FD; Thu, 13 May 1999 10:55:10 -0500 (CDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Jake Burkholder Cc: current@FreeBSD.ORG Subject: Re: Some interrupt bogons still around. In-reply-to: Your message of "Thu, 13 May 1999 08:25:14 PDT." <199905131525.IAA16651@io.dyn.ez-ip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 May 1999 10:55:10 -0500 From: Chris Csanady Message-Id: <19990513155510.44B75FD@friley-185-205.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> my stock SB16 + freebsd+x11amp hasn't worked right since newbus. >> >> sound skips quite a bit. >> >> >> > >I noticed the same thing. /usr/ports/audio/gqmpeg is a nice player >which uses mpg123 as the backend; it plays fine. I think it may have >just have something to do with x11amp, which should probably be considered >a bogon itself. All other sources of sound work fine, like fxtv. Really? mpg123 and fxtv are broke for me. Have you tried using fxtv to capture audio and then play it back? I haven't tried it in a while, but they both acted like x11amp with regard to the "skipping." x11amp still does not work right for me though.. This is on different audio hardware as well.. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 9:16:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 8176714D25 for ; Thu, 13 May 1999 09:16:49 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id SAA05694 for ; Thu, 13 May 1999 18:16:48 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id SAA10244 for ; Thu, 13 May 1999 18:16:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Cc: current@FreeBSD.ORG Subject: Re: make world croaks in perl ?? In-reply-to: Your message of "Thu, 13 May 1999 13:06:19 +0200." <9459.926593579@critter.freebsd.dk> Date: Thu, 13 May 1999 18:16:44 +0200 Message-ID: <10242.926612204@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm, double make cleandir fixed it. Could a conveniently located perl wizard try to figure out what this is tripping over and fix the build ? In message <9459.926593579@critter.freebsd.dk>, Poul-Henning Kamp writes: > >Is anybody but me seeing this ? > >===> gnu/usr.bin/perl >===> gnu/usr.bin/perl/libperl >===> gnu/usr.bin/perl/miniperl >sh config_h.sh >Extracting config.h (with variable substitutions) >cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/p >erl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/i >nclude -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/miniperlm >ain.c >cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/p >erl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/i >nclude -static -o miniperl miniperlmain.o -lperl -lm -lcrypt >===> gnu/usr.bin/perl/perl >make: don't know how to make writemain.sh. Stop >*** Error code 2 > > >-- >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 > -- 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 May 13 9:26:55 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 5622C15207 for ; Thu, 13 May 1999 09:26:47 -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 JAA72703; Thu, 13 May 1999 09:26:10 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199905131626.JAA72703@troutmask.apl.washington.edu> Subject: Re: make world croaks in perl ?? In-Reply-To: <10242.926612204@critter.freebsd.dk> from Poul-Henning Kamp at "May 13, 1999 06:16:44 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Thu, 13 May 1999 09:26:10 -0700 (PDT) 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 It doesn't fix it here, but "dt" committed a fix to a Makefile in the Perl tree. This might actually fix the problem. I'm rebuilding now to see. Poul-Henning Kamp wrote: > > Hmm, double make cleandir fixed it. > > Could a conveniently located perl wizard try to figure out what > this is tripping over and fix the build ? > > In message <9459.926593579@critter.freebsd.dk>, Poul-Henning Kamp writes: > > > >Is anybody but me seeing this ? > > > >===> gnu/usr.bin/perl > >===> gnu/usr.bin/perl/libperl > >===> gnu/usr.bin/perl/miniperl > >sh config_h.sh > >Extracting config.h (with variable substitutions) > >cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/p > >erl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/i > >nclude -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/miniperlm > >ain.c > >cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/p > >erl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/i > >nclude -static -o miniperl miniperlmain.o -lperl -lm -lcrypt > >===> gnu/usr.bin/perl/perl > >make: don't know how to make writemain.sh. Stop > >*** Error code 2 > > > > > >-- > >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 > > > > -- > 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 > -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 9:34:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from garbo.lodgenet.com (garbo.lodgenet.com [204.124.122.252]) by hub.freebsd.org (Postfix) with ESMTP id E527C14C47 for ; Thu, 13 May 1999 09:34:12 -0700 (PDT) (envelope-from erich@lodgenet.com) Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.122.30]) by garbo.lodgenet.com (8.9.3/8.9.3) with ESMTP id LAA15831; Thu, 13 May 1999 11:34:09 -0500 (CDT) Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.9.3/8.8.5) with ESMTP id LAA22844; Thu, 13 May 1999 11:29:53 -0500 (CDT) Message-Id: <199905131629.LAA22844@jake.lodgenet.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jake Burkholder Cc: current@FreeBSD.ORG, erich@lodgenet.com Subject: Re: Some interrupt bogons still around. In-reply-to: Your message of "Thu, 13 May 1999 08:25:14 PDT." <199905131525.IAA16651@io.dyn.ez-ip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 May 1999 11:29:53 -0500 From: "Eric L. Hernes" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jake Burkholder writes: >> >> my stock SB16 + freebsd+x11amp hasn't worked right since newbus. mine either, 'til I switched from pcm back to the voxware stuff. Then it magically worked ok. > >I noticed the same thing. /usr/ports/audio/gqmpeg is a nice player >which uses mpg123 as the backend; it plays fine. I think it may have >just have something to do with x11amp, which should probably be considered >a bogon itself. All other sources of sound work fine, like fxtv. A lot of other mp3 decoders worked OK, but x11amp didn't. I spend some time looking at x11amp in and out plugins. The in/out parts of x11amp ain't exactly textbook threaded code ;-) mostly spinloops and sleeps :( I half re-wrote the OSS plugin with real cond-vars and mutexes, but still skipped... Then I tried the old voxware code, and now it only skips when the process is CPU starved. I could prolly fix that by giving the process a slight rtprio... but it hasn't been irritating enough yet. > >Jake >-- >Linux - Zealotry taken over the Edge > > Eric -- Eric L. Hernes erich@lodgenet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 10:20:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id EB554152B9; Thu, 13 May 1999 10:20:16 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.1) id KAA16364; Thu, 13 May 1999 10:20:09 -0700 (PDT) (envelope-from obrien) Message-ID: <19990513102009.A16239@nuxi.com> Date: Thu, 13 May 1999 10:20:09 -0700 From: "David O'Brien" To: Wilko Bulte Cc: freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: de driver problem Reply-To: obrien@NUXI.com References: <199905122044.NAA03768@gndrsh.aac.dev.com> <199905122202.AAA04213@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905122202.AAA04213@yedi.iaf.nl>; from Wilko Bulte on Thu, May 13, 1999 at 12:02:25AM +0200 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If ``make cleandir'' is leaving some cruft in any form behind anyplace > > in the build tree things are broken. > > Sounds very reasonable to me. Running the same command twice to get > things really clean sounds suspicious ;-) Let me explain ``make cleandir'' then. *IF* you have a /usr/obj/usr/src/ tree, then ``make cleandir'' will clean that tree out. Thus if somehow you have junk in /usr/src/, it will not get cleaned out. On the second run of ``make cleandir'' it will notice that /usr/obj/ is empty and assume you were building "in-place" and clean out /usr/src/. cd /usr/src ; make cleandir ; make cleandir solves weird build problems much of the time. -- -- David (obrien@NUXI.com -or- obrien@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 May 13 12:17:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 6A93014DCB; Thu, 13 May 1999 12:17:42 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id VAA66572; Thu, 13 May 1999 21:17:39 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id VAA09869; Thu, 13 May 1999 21:17:38 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905131917.VAA09869@greenpeace.grondar.za> To: Wilko Bulte Cc: dfr@nlsystems.com, khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: de driver problem In-Reply-To: Your message of " Thu, 13 May 1999 14:13:32 +0200." <199905131213.OAA12011@yedi.iaf.nl> References: <199905131213.OAA12011@yedi.iaf.nl> Date: Thu, 13 May 1999 21:17:37 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > I periodically see this one reported, and It is always repaired > > by the reporter making sure their tree is _really_ clean before > > doing a make world. "Really clean" means "make cleandir" _twice_, > > and complete removal of the contents of /usr/obj. _Then_ cvsup. > > I prefer to usr CVS checkout, as it shows all the differences and > > other turds in my source tree. > > Unfortunately: OK - script the _whole_ thing, and put it somewhere I can get it. DO NOT MAIL IT TO ME! I want to see all the commands you type, and also the contents of your /etc/make.conf. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 13: 3: 8 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 630D114D7F for ; Thu, 13 May 1999 13:03:01 -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 QAA31581; Thu, 13 May 1999 16:02:49 -0400 (EDT) Date: Thu, 13 May 1999 16:02:48 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive 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 That's funny, my system is pretty much the EXACT same as yours, and DMA does not get enabled for my Seagate 6.4GB UDMA2 drive. Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 May 13 13:40:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from november.jaded.net (november.jaded.net [209.90.128.250]) by hub.freebsd.org (Postfix) with ESMTP id 4A63E14C1D for ; Thu, 13 May 1999 13:40:53 -0700 (PDT) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id QAA26430 for freebsd-current@freebsd.org; Thu, 13 May 1999 16:47:21 -0400 (EDT) Date: Thu, 13 May 1999 16:47:20 -0400 From: Dan Moschuk To: freebsd-current@freebsd.org Subject: Berkeley DB 1.85 --> 2.0 Message-ID: <19990513164720.A26399@trinsec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of curiosity, is there a reason we are still using Berkeley DB v1.85 as apposed to v2? --Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 13:50:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 3284014CC6 for ; Thu, 13 May 1999 13:50:20 -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 OAA10363; Thu, 13 May 1999 14:50:10 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA07674; Thu, 13 May 1999 14:50:10 -0600 Date: Thu, 13 May 1999 14:50:10 -0600 Message-Id: <199905132050.OAA07674@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Dan Moschuk Cc: freebsd-current@FreeBSD.ORG Subject: Re: Berkeley DB 1.85 --> 2.0 In-Reply-To: <19990513164720.A26399@trinsec.com> References: <19990513164720.A26399@trinsec.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Out of curiosity, is there a reason we are still using Berkeley DB v1.85 as > apposed to v2? The new copyright is 'less free'. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 13:50:53 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 AFE8915261 for ; Thu, 13 May 1999 13:50:29 -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 QAA10438; Thu, 13 May 1999 16:50:17 -0400 (EDT) (envelope-from wollman) Date: Thu, 13 May 1999 16:50:17 -0400 (EDT) From: Garrett Wollman Message-Id: <199905132050.QAA10438@khavrinen.lcs.mit.edu> To: Dan Moschuk Cc: freebsd-current@FreeBSD.ORG Subject: Berkeley DB 1.85 --> 2.0 In-Reply-To: <19990513164720.A26399@trinsec.com> References: <19990513164720.A26399@trinsec.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Out of curiosity, is there a reason we are still using Berkeley DB v1.85 as > apposed to v2? Yes. v2 has an unfriendly license. -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 Thu May 13 14: 9:54 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 1F89714E09 for ; Thu, 13 May 1999 14:09:52 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA71100; Thu, 13 May 1999 14:09:47 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Dan Moschuk Cc: freebsd-current@FreeBSD.ORG Subject: Re: Berkeley DB 1.85 --> 2.0 In-reply-to: Your message of "Thu, 13 May 1999 16:47:20 EDT." <19990513164720.A26399@trinsec.com> Date: Thu, 13 May 1999 14:09:47 -0700 Message-ID: <71096.926629787@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Out of curiosity, is there a reason we are still using Berkeley DB v1.85 as > apposed to v2? Yeah, the license for v2 is too stringent for our requirements. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 14:47:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 6B4D415206; Thu, 13 May 1999 14:45:08 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.2/8.9.2) id VAA76957; Thu, 13 May 1999 21:53:32 +0100 (BST) (envelope-from nik) Date: Thu, 13 May 1999 21:53:32 +0100 From: Nik Clayton To: "Jordan K. Hubbard" Cc: nik@freebsd.org, current@freebsd.org Subject: Re: Someone blew up the handbook again. Message-ID: <19990513215332.A76346@catkin.nothing-going-on.org> References: <65758.926542082@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <65758.926542082@zippy.cdrom.com>; from Jordan K. Hubbard on Wed, May 12, 1999 at 01:48:02PM -0700 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 12, 1999 at 01:48:02PM -0700, Jordan K. Hubbard wrote: > /usr/local/bin/jade -V html-manifest -ioutput.html -c /usr/doc/share/sgml/catal > og -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sg > ml/docbook/3.0/catalog -c /usr/local/share/sgml/jade/catalog -d /usr/doc/share/ > sgml/freebsd.dsl -t sgml handbook.sgml > /usr/local/bin/jade:install/chapter.sgml:279:13:E: character data is not allowed > > Should I just turn NODOC on for the -current snapshot builds? No objection from me. I imagine that testing the FDP stuff isn't a major priority for people tracking -current. N -- There's some milk in the fridge about to go off. . . and there it goes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 15:53:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 1698A14C98 for ; Thu, 13 May 1999 15:52:55 -0700 (PDT) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id CAA25834; Fri, 14 May 1999 02:51:15 +0400 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.3/8.9.1) with ESMTP id CAA02073; Fri, 14 May 1999 02:54:39 +0400 (MSD) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199905132254.CAA02073@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Steve Kargl Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), current@FreeBSD.ORG Subject: Re: make world croaks in perl ?? In-reply-to: Your message of "Thu, 13 May 1999 09:26:10 PDT." <199905131626.JAA72703@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 May 1999 02:54:39 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yup, this is supposed to fix the problem, that I introduced a day before. The problem was 'make -jN'-depended. Sorry for the inconvinience. BTW, I hope there will be no 'Your makefile has been rebuilt' failures anymore. Dima Steve Kargl wrote: > It doesn't fix it here, but "dt" committed a fix to a Makefile > in the Perl tree. This might actually fix the problem. I'm > rebuilding now to see. > > Poul-Henning Kamp wrote: > > > > Hmm, double make cleandir fixed it. > > > > Could a conveniently located perl wizard try to figure out what > > this is tripping over and fix the build ? > > > > In message <9459.926593579@critter.freebsd.dk>, Poul-Henning Kamp writes: > > > > > >Is anybody but me seeing this ? > > > > > >===> gnu/usr.bin/perl > > >===> gnu/usr.bin/perl/libperl > > >===> gnu/usr.bin/perl/miniperl > > >sh config_h.sh > > >Extracting config.h (with variable substitutions) > > >cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/p > > >erl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/i > > >nclude -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/miniperlm > > >ain.c > > >cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/p > > >erl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/i > > >nclude -static -o miniperl miniperlmain.o -lperl -lm -lcrypt > > >===> gnu/usr.bin/perl/perl > > >make: don't know how to make writemain.sh. Stop > > >*** Error code 2 > > > > > > > > >-- > > >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 > > > > > > > -- > > 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 > > > > > -- > Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 16:20:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id DA21C14E76 for ; Thu, 13 May 1999 16:20:31 -0700 (PDT) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem01.masternet.it [194.184.65.11]) by scotty.masternet.it (8.9.3/8.9.2) with SMTP id BAA03989; Fri, 14 May 1999 01:15:43 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990514011159.01bc1590@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 14 May 1999 01:13:36 +0200 To: Poul-Henning Kamp , Sheldon Hearn From: Gianmarco Giovannelli Subject: Re: Today's kernel crashes on starting X Cc: Geoff Rehmet , "'current@freebsd.org'" In-Reply-To: <9504.926594261@critter.freebsd.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 13/05/99, Poul-Henning Kamp wrote: > >I think the fix to the device-pager earlier today may have take >care of this one (Many thanks to luoqi!) Here it continues to panic with screen, same errors of yesterday... I'll try with X right now but I think it is the same story... :-) Cvsupped and maked world this afternoon (CEST). Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 16:49:56 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 DA3FA14EF3 for ; Thu, 13 May 1999 16:49:51 -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 JAA08559; Fri, 14 May 1999 09:19:50 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA66751; Fri, 14 May 1999 09:19:49 +0930 (CST) Date: Fri, 14 May 1999 09:19:48 +0930 From: Greg Lehey To: Brian Feldman Cc: Dag-Erling Smorgrav , current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive Message-ID: <19990514091948.D89091@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 Brian Feldman on Thu, May 13, 1999 at 04:02:48PM -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 Thursday, 13 May 1999 at 16:02:48 -0400, Brian Feldman wrote: > That's funny, my system is pretty much the EXACT same as yours, and DMA does not > get enabled for my Seagate 6.4GB UDMA2 drive. Did you set the flags? 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 Thu May 13 16:56: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 B7D4A150D6 for ; Thu, 13 May 1999 16:56:37 -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 TAA35275; Thu, 13 May 1999 19:52:17 -0400 (EDT) Date: Thu, 13 May 1999 19:52:17 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Jordan K. Hubbard" Cc: Poul-Henning Kamp , Soren Schmidt , Dag-Erling Smorgrav , current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive In-Reply-To: <65947.926544473@zippy.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 Wed, 12 May 1999, Jordan K. Hubbard wrote: > > Try disabling "ultra DMA" in the BIOS, that seems to have worked for > > me on my IBM-DJNA-371800 drive. > > > > (Jordan: We may want to put something in the README about this in 3.2!) > > I'd welcome suggestions as to what the text should look like; I'm > still unclear as to what exactly the problem us. :) > I'd also be interested to know how you plan on describing disabling UDMA, since I don't see that option in my AMIBIOS. > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 May 13 17:20:59 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 C52B8151DD for ; Thu, 13 May 1999 17:20:52 -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 2.12 #1) id 10i5fM-00004e-00; Fri, 14 May 1999 02:17:28 +0200 From: Sheldon Hearn To: Gianmarco Giovannelli Cc: Poul-Henning Kamp , Geoff Rehmet , "'current@freebsd.org'" Subject: Re: Today's kernel crashes on starting X In-reply-to: Your message of "Fri, 14 May 1999 01:13:36 +0200." <4.1.19990514011159.01bc1590@194.184.65.4> Date: Fri, 14 May 1999 02:17:28 +0200 Message-ID: <287.926641048@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 May 1999 01:13:36 +0200, Gianmarco Giovannelli wrote: > Here it continues to panic with screen, same errors of yesterday... I'll > try with X right now but I think it is the same story... :-) > Cvsupped and maked world this afternoon (CEST). Well guesss what? I'm seeing panics too, after suggesting that everything was cool and froody. :-) I don't have to start X, I get a panic as soon as I try to mount_mfs -- 100% reproducible. Someone else posted a backtrace, the one that incriminates checkalias(), I think? 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 May 13 17:31:47 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 6A4241532C for ; Thu, 13 May 1999 17:31:01 -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 UAA24072 for ; Thu, 13 May 1999 20:31:01 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA12829; Thu, 13 May 1999 20:30:30 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id UAA52635 for freebsd-current@freebsd.org; Thu, 13 May 1999 20:30:30 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905140030.UAA52635@bb01f39.unx.sas.com> Subject: make release failure (/usr/src/release/Makefile) To: freebsd-current@freebsd.org Date: Thu, 13 May 1999 20:30:30 -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 sent the following patch a few days ago... If this is working for everyone else and not me, I'd love to know what I'm doing wrong. perl5 ../../kern/makedevops.pl -h ../../pci/pci_if.m rm -f .newdep mkdep -a -f .newdep -O -Wall -Wredundant-decls -Wnested-externs ....... rm -f .depend mv -f .newdep .depend make: don't know how to make kernel. Stop *** Error code 2 by applying the patch below and running /snap/release/mk via chroot the process finishes correctly. Thanks! John > Hi, > > Could you please consider the following patch to > /usr/src/release/Makefile? It may not be entirely correct, > but it allows a 'cd /usr/src/release && make release' to > run to completion. In the kernel makefile, 'kernel' > is not a target, ${KERNEL} is, and ${KERNEL} has the value > 'GENERIC'. > > Comments welcome! > > Thanks! > John > # $Id: Makefile,v 1.482 1999/05/09 17:00:04 obrien Exp $ - --- /snap/release/usr/src/release/Makefile~ Tue May 11 23:50:52 1999 +++ /snap/release/usr/src/release/Makefile Tue May 11 23:43:49 1999 @@ -634,9 +634,9 @@ @rm -f ${RD}/kernels/${KERNEL} @cd ${.CURDIR}/../sys/${MACHINE_ARCH}/conf && config ${KERNEL} @cd ${.CURDIR}/../sys/compile/${KERNEL} && \ - - make depend && \ - - make kernel && \ - - cp kernel ${RD}/kernels/${KERNEL} + make depend && pwd && \ + make ${KERNEL} && \ + cp ${KERNEL} ${RD}/kernels/${KERNEL} # # --==## Put a filesystem into a BOOTMFS kernel ##==-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 18:21:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.rz.uni-karlsruhe.de (nz40.rz.uni-karlsruhe.de [129.13.197.4]) by hub.freebsd.org (Postfix) with ESMTP id A4C7214F65 for ; Thu, 13 May 1999 18:21:23 -0700 (PDT) (envelope-from un1i@rz.uni-karlsruhe.de) Received: from rz114s1.rz.uni-karlsruhe.de (un1i@rz114s1-197.rz.uni-karlsruhe.de [129.13.197.190]) by mailgate.rz.uni-karlsruhe.de with esmtp (Exim 2.04 #3) id 10i6f7-0005x8-00; Fri, 14 May 1999 03:21:17 +0200 Received: from un1i by rz114s1.rz.uni-karlsruhe.de with local (Exim 2.12 #1) id 10i6f6-0005HT-00; Fri, 14 May 1999 03:21:16 +0200 Message-ID: <19990514032116.A19700@rz.uni-karlsruhe.de> Date: Fri, 14 May 1999 03:21:16 +0200 From: Philipp Mergenthaler To: dave adkins Cc: current@FreeBSD.ORG Subject: Re: Today's kernel crashes on starting X References: <3D5EC7D2992BD211A95600A0C9CE047F0308D99F@isjhbex01.is.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from dave adkins on Thu, May 13, 1999 at 05:25:54AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 13, 1999 at 05:25:54AM -0500, dave adkins wrote: > > I think it's the recent dev_t changes causing problems. > I haven't tracked it any further. > > Try changing: > > #define DEVT_FACIST 1 > > in kern/kern_conf.c to > > #undef DEVT_FACIST > > It has fixed my X crash. > dave adkins This also fixes the panic that I got with mfs_mount: (with "options MFS" in the config file, 'cvsup'ed at May 13th 19:43 UTC) Fatal trap 12: page fault while inkernel mode fault virtual address = 0x9d19fd34 fault code = supervisor read, page not present instruction pointer = 0x8:0xc016f7a0 stack pointer = 0x10:0xc494cd68 frame pointer = 0x10:0xc494cd94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, Rres 1,def 32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 38 (mount_mfs) interrupt mask = kernel: type 12 trap, code: 0 stopped at checkalias+0x150: movl cdevsw(%eax), %edx db> trace checkalias(c4478980, ff00, 0) at checkalias+0x150 mfs_mount(c08a3e00, bfbfde98, bfbfd7ac, c494cea0, c44804c0) at mfs_mount+0x132 mount(c44804c0, c494cf80,0,80691e0,2000) at mount+0x50e syscall(2f,2f,2f,2000,80691e0) at syscall+0x182 Xint0x80_syscall() at Xint0x80_syscall+0x30 Bye, Philipp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 18:38:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa16-36.ix.netcom.com [207.93.148.164]) by hub.freebsd.org (Postfix) with ESMTP id B5F93152FC for ; Thu, 13 May 1999 18:38:30 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id SAA07432; Thu, 13 May 1999 18:38:27 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Thu, 13 May 1999 18:38:27 -0700 (PDT) Message-Id: <199905140138.SAA07432@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: freebsd-current@FreeBSD.ORG Subject: egcs, libstdc++, libg++, Class Library Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I missed something, again. What is the current and near-future status of Class Libraries? libg++ is not updated. libstdc++ has some classes 'if 0'-ed out. I have a project that uses the string class and iostream. I cannot build it with -current as of Apr 11. Is the solution to get and install libg++? Or, is there a near-term fix for the egcs package? tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 18:55:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id A720A14D90; Thu, 13 May 1999 18:55:15 -0700 (PDT) (envelope-from rgrimes@gndrsh.aac.dev.com) Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.9.3/8.9.3) id SAA10510; Thu, 13 May 1999 18:54:54 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199905140154.SAA10510@gndrsh.aac.dev.com> Subject: Re: de driver problem In-Reply-To: <19990513102009.A16239@nuxi.com> from "David O'Brien" at "May 13, 1999 10:20:09 am" To: obrien@NUXI.com Date: Thu, 13 May 1999 18:54:53 -0700 (PDT) Cc: wilko@yedi.iaf.nl (Wilko Bulte), freebsd-alpha@FreeBSD.ORG, 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 > > > If ``make cleandir'' is leaving some cruft in any form behind anyplace > > > in the build tree things are broken. > > > > Sounds very reasonable to me. Running the same command twice to get > > things really clean sounds suspicious ;-) > > Let me explain ``make cleandir'' then. Perhaps you missed the ``as the original author of make cleandir'' in my posting. I wrote it in the days of the 386BSD patchkit. I _know_ what it was meant to do, and it is _NOT_ doing what it is suppose to do!!! > *IF* you have a /usr/obj/usr/src/ tree, then ``make cleandir'' will clean > that tree out. Thus if somehow you have junk in /usr/src/, it will not > get cleaned out. On the second run of ``make cleandir'' it will notice > that /usr/obj/ is empty and assume you were building "in-place" and clean > out /usr/src/. This is what is happening now, it is not what should be happening. The orignal ``make cleandir'' would clean both the object tree and the source tree of all remanants of any files created by any and all make commands. The brokenness occured when the obj symlinks where removed from the src tree and cleandir was rewritten. > > cd /usr/src ; make cleandir ; make cleandir > > solves weird build problems much of the time. BROKEN! Thats all I have to say. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 19:17:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id DEA1914D90 for ; Thu, 13 May 1999 19:17:26 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id WAA29252; Thu, 13 May 1999 22:17:23 -0400 (EDT) (envelope-from luoqi) Date: Thu, 13 May 1999 22:17:23 -0400 (EDT) From: Luoqi Chen Message-Id: <199905140217.WAA29252@lor.watermarkgroup.com> To: adkin003@tc.umn.edu, un1i@rz.uni-karlsruhe.de Subject: Re: Today's kernel crashes on starting X Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This also fixes the panic that I got with mfs_mount: > (with "options MFS" in the config file, 'cvsup'ed at May 13th 19:43 UTC) > > Fatal trap 12: page fault while inkernel mode > fault virtual address = 0x9d19fd34 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc016f7a0 > stack pointer = 0x10:0xc494cd68 > frame pointer = 0x10:0xc494cd94 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, Rres 1,def 32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL=0 > current process = 38 (mount_mfs) > interrupt mask = > kernel: type 12 trap, code: 0 > stopped at checkalias+0x150: movl cdevsw(%eax), %edx > > db> trace > checkalias(c4478980, ff00, 0) at checkalias+0x150 > mfs_mount(c08a3e00, bfbfde98, bfbfd7ac, c494cea0, c44804c0) at mfs_mount+0x132 > mount(c44804c0, c494cf80,0,80691e0,2000) at mount+0x50e > syscall(2f,2f,2f,2000,80691e0) at syscall+0x182 > Xint0x80_syscall() at Xint0x80_syscall+0x30 > > Bye, Philipp > This was due to a kludge in mfs implementation. Try change NUMCDEV in kern_conf.c to 255. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 19:18:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D296D14C26 for ; Thu, 13 May 1999 19:18:13 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.1) id TAA25901; Thu, 13 May 1999 19:18:08 -0700 (PDT) (envelope-from obrien) Message-ID: <19990513191808.A25831@nuxi.com> Date: Thu, 13 May 1999 19:18:08 -0700 From: "David O'Brien" To: Thomas Dean , freebsd-current@FreeBSD.ORG Subject: Re: egcs, libstdc++, libg++, Class Library Reply-To: obrien@NUXI.com References: <199905140138.SAA07432@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905140138.SAA07432@ix.netcom.com>; from Thomas Dean on Thu, May 13, 1999 at 06:38:27PM -0700 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The new ISO Standard C++ is upon you! Rejoice! > libg++ is not updated. libg++ is *dead*. Its has mostly been superseded by the STL. See http://egcs.cygus.com/ and the G++ FAQ for details. For those that absolutely need some of the libg++ classes, you can download libstdc++-2.8.1.1.tar.gz the will work with EGCS 1.1.2 / GCC 2.8.1 from ftp://egcs.cygnus.com/pub/egcs/infrastructure/ (or maybe also prep.ai.mit.edu) > libstdc++ has some classes 'if 0'-ed out. What from the ISO standard is missing from libstdc++? > I have a project that uses the string class and iostream. Whose string class? C++ string classes are even better than standards -- everybody's got one so there's so many to choose from (and of course none of their API's match). > Or, is there a near-term fix for the egcs package? There is no fix for the EGCS package as it isn't broken. -- -- David (obrien@NUXI.com -or- obrien@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 May 13 19:21:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 71AF315351 for ; Thu, 13 May 1999 19:21:38 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.1) id TAA25917; Thu, 13 May 1999 19:21:32 -0700 (PDT) (envelope-from obrien) Message-ID: <19990513192132.B25831@nuxi.com> Date: Thu, 13 May 1999 19:21:32 -0700 From: "David O'Brien" To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: Today's kernel crashes on starting X Reply-To: obrien@NUXI.com References: <199905140217.WAA29252@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905140217.WAA29252@lor.watermarkgroup.com>; from Luoqi Chen on Thu, May 13, 1999 at 10:17:23PM -0400 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 13, 1999 at 10:17:23PM -0400, Luoqi Chen wrote: > > This also fixes the panic that I got with mfs_mount: > > (with "options MFS" in the config file, 'cvsup'ed at May 13th 19:43 UTC) ..snip.. > This was due to a kludge in mfs implementation. Try change NUMCDEV in > kern_conf.c to 255. Are you saying that there is a bug in the mfs implementation and a fix will be commited soon? (and change NUMCDEV until then) Or are you saying, the mfs implementation is now considered correct (but there are some kludges in there) and that changing NUMCDEV in kern_conf.c to 255 is the perminate fix? -- -- David (obrien@NUXI.com -or- obrien@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 May 13 19:27: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 014AA15300 for ; Thu, 13 May 1999 19:27:06 -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 WAA38749; Thu, 13 May 1999 22:26:48 -0400 (EDT) Date: Thu, 13 May 1999 22:26:48 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Greg Lehey Cc: Dag-Erling Smorgrav , current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive In-Reply-To: <19990514091948.D89091@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 Fri, 14 May 1999, Greg Lehey wrote: > On Thursday, 13 May 1999 at 16:02:48 -0400, Brian Feldman wrote: > > That's funny, my system is pretty much the EXACT same as yours, and DMA does not > > get enabled for my Seagate 6.4GB UDMA2 drive. > > Did you set the flags? Of course, 0xa0ffa0ff on both controllers. All that has been tried. ATA does work with my UDMA drives, but lacking a dump function is insufficient for my purpouses. > > 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 > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 May 13 19:32:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.visi.com (baal.visi.com [209.98.98.3]) by hub.freebsd.org (Postfix) with ESMTP id 899DB15300 for ; Thu, 13 May 1999 19:32:07 -0700 (PDT) (envelope-from veldy@visi.com) Received: from isis.visi.com (veldy@isis.visi.com [209.98.98.8]) by mail.visi.com (8.8.8/8.7.5) with ESMTP id VAA22875; Thu, 13 May 1999 21:32:06 -0500 (CDT) Posted-Date: Thu, 13 May 1999 21:32:06 -0500 (CDT) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id VAA24226; Thu, 13 May 1999 21:32:06 -0500 (CDT) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Thu, 13 May 1999 21:32:06 -0500 (CDT) From: "Thomas T. Veldhouse" To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: egcs, libstdc++, libg++, Class Library In-Reply-To: <199905140138.SAA07432@ix.netcom.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 Have you tried using the C++ standard way? It works. #include #include using namespace std; Of course, there are many times you won't want to include the entire namespace. Tom Veldhouse veldy@visi.com On Thu, 13 May 1999, Thomas Dean wrote: > I think I missed something, again. > > What is the current and near-future status of Class Libraries? > > libg++ is not updated. libstdc++ has some classes 'if 0'-ed out. > > I have a project that uses the string class and iostream. I cannot > build it with -current as of Apr 11. > > Is the solution to get and install libg++? Or, is there a near-term > fix for the egcs package? > > tomdean > > > 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 Thu May 13 20:46:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.rz.uni-karlsruhe.de (nz40.rz.uni-karlsruhe.de [129.13.197.4]) by hub.freebsd.org (Postfix) with ESMTP id ECCEE14C06 for ; Thu, 13 May 1999 20:46:42 -0700 (PDT) (envelope-from un1i@rz.uni-karlsruhe.de) Received: from rz114s1.rz.uni-karlsruhe.de (un1i@rz114s1-197.rz.uni-karlsruhe.de [129.13.197.190]) by mailgate.rz.uni-karlsruhe.de with esmtp (Exim 2.04 #3) id 10i8vm-00028J-00; Fri, 14 May 1999 05:46:38 +0200 Received: from un1i by rz114s1.rz.uni-karlsruhe.de with local (Exim 2.12 #1) id 10i8vm-0005jC-00; Fri, 14 May 1999 05:46:38 +0200 Message-ID: <19990514054637.A21841@rz.uni-karlsruhe.de> Date: Fri, 14 May 1999 05:46:37 +0200 From: Philipp Mergenthaler To: Luoqi Chen Cc: current@freebsd.org Subject: Re: Today's kernel crashes on starting X References: <199905140217.WAA29252@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905140217.WAA29252@lor.watermarkgroup.com>; from Luoqi Chen on Thu, May 13, 1999 at 10:17:23PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This also fixes the panic that I got with mfs_mount: > > (with "options MFS" in the config file, 'cvsup'ed at May 13th 19:43 UTC) > > > > Fatal trap 12: page fault while inkernel mode > > fault virtual address = 0x9d19fd34 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xc016f7a0 [...] > > current process = 38 (mount_mfs) [...] > > db> trace > > checkalias(c4478980, ff00, 0) at checkalias+0x150 > > mfs_mount(c08a3e00, bfbfde98, bfbfd7ac, c494cea0, c44804c0) at mfs_mount+0x132 > > mount(c44804c0, c494cf80,0,80691e0,2000) at mount+0x50e > This was due to a kludge in mfs implementation. Try change NUMCDEV in > kern_conf.c to 255. > -lq Ok, with this fix MFS works (with "#define DEVT_FASCIST 1" in kern_conf.c). Bye, Philipp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 13 23:24:53 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 177A714BF7; Thu, 13 May 1999 23:24:42 -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 PAA09947; Fri, 14 May 1999 15:54:41 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA95316; Fri, 14 May 1999 15:54:39 +0930 (CST) Date: Fri, 14 May 1999 15:54:38 +0930 From: Greg Lehey To: FreeBSD Questions Cc: FreeBSD current users Subject: Re: Build failure under 3.1-STABLE Message-ID: <19990514155438.T89091@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i 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 Somebody sent a message to -questions today about trying "make world" under 3.1-STABLE, but the make died in modules/vinum. Unfortunately, I accidentally deleted the message, so I can't remember who it was. I've checked this out, and I think I can safely say: 1. There's nothing wrong with the build in 3.2-BETA (there is currently no -STABLE branch). 2. I recognize the error messages, though: they come from a small window in 4.0-CURRENT. Vinum is currently broken in -CURRENT since a number of commits to low-level were made. I'm going to take a look, and it should be fixed soon. In the meantime, "make world" no longer tries to build the Vinum kld module. This suggests to me that the originator of the message doesn't realize it, but he's tracking -CURRENT, not -STABLE. If you don't know how to fix that, post another question. 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 Fri May 14 1:13:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id AF0571551F for ; Fri, 14 May 1999 01:13:37 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id KAA04829; Fri, 14 May 1999 10:13:25 +0200 (CEST) (envelope-from des) To: Greg Lehey Cc: Dag-Erling Smorgrav , current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive References: <19990513085803.V89091@freebie.lemis.com> Organization: Yes! Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 14 May 1999 10:13:25 +0200 In-Reply-To: Greg Lehey's message of "Thu, 13 May 1999 08:58:04 +0930" Message-ID: Lines: 81 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey writes: > What chip set are you using? Aladdin (it's a Super Socket 7 motherboard): 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 #1: Wed May 12 17:34:21 CEST 1999 root@des.follo.net:/usr/src/sys/compile/DES Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping=12 Features=0x8021bf real memory = 134217728 (131072K bytes) sio0: system console avail memory = 128090112 (125088K bytes) Preloaded elf kernel "kernel" at 0xc026f000. Preloaded splash_image_data "/boot/splash.pcx" at 0xc026f09c. Preloaded elf module "splash_pcx.ko" at 0xc026f0ec. Probing for PnP devices: CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0xffffffff) at 0x220-0x22f irq 10 drq 1 flags 0x10 on isa npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 11 at device 0.0 on pci1 chip1: at device 3.0 on pci0 isab0: at device 7.0 on pci0 xl0: <3Com 3c900-COMBO Etherlink XL> irq 12 at device 11.0 on pci0 xl0: Ethernet address: 00:60:08:cf:a8:e4 xl0: selecting 10baseT transceiver, half duplex 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 devclass_alloc_unit: apm0 already exists, using next available unit number 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 on isa0 atkbd0: irq 1 on atkbdc0 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> 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: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 IP packet filtering initialized, divert disabled, rule-based forwarding disabled, unlimited logging ata0: master: settting up UDMA2 mode on Aladdin chip OK ad0: ATA-4 disk at ata0 as master ad0: 9641MB (19746720 sectors), 19590 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 31 depth queue, DMA mode ata1: master: settting up UDMA2 mode on Aladdin chip OK ad1: ATA-2 disk at ata1 as master ad1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 0 depth queue, DMA mode changing root device to wd0s4a changing root device to wd0a xl0: selecting BNC port, half duplex DES -- Dag-Erling Smorgrav - des@yes.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 1:18:32 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 7A4DD1551F for ; Fri, 14 May 1999 01:18:25 -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 KAA41943; Fri, 14 May 1999 10:18:16 +0200 (CEST) (envelope-from des) To: NAKAGAWA Yoshihisa Cc: Dag-Erling Smorgrav , Garrett Wollman , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c References: <199905130238.CAA11000@chandra.eatell.msr.prug.or.jp> From: Dag-Erling Smorgrav Date: 14 May 1999 10:18:14 +0200 In-Reply-To: NAKAGAWA Yoshihisa's message of "Thu, 13 May 1999 11:38:29 +0900" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NAKAGAWA Yoshihisa writes: > > Then explain to us why newbus is wrong and why the 4.4BSD scheme is > > right. > Because, you are misunderstanding 4.4BSD scheme (and newconfig). This is pointless. All you're doing is pointing your finger and screaming "It's not right! It's not fair!" without saying anything of actual value. 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 Fri May 14 1:19:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 6EE181551F for ; Fri, 14 May 1999 01:19:40 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id DAA05339 for current@freebsd.org; Fri, 14 May 1999 03:19:40 -0500 (CDT) From: Kevin Day Message-Id: <199905140819.DAA05339@home.dragondata.com> Subject: Alladdin IDE slow? To: current@freebsd.org Date: Fri, 14 May 1999 03:19:40 -0500 (CDT) 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 I'm using an Alladin chipset in a -current machine... CPU: AMD-K6(tm) 3D processor (337.19-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf real memory = 134217728 (131072K bytes) avail memory = 126808064 (123836K bytes) 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 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 ata0: master: settting up UDMA2 mode on Aladdin chip OK ad0: ATA-3 disk at ata0 as master ad0: 3079MB (6306048 sectors), 6256 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 ata0: slave: settting up UDMA2 mode on Aladdin chip OK ad1: ATA-3 disk at ata0 as slave ad1: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 0 depth queue, DMA mode ata1: master: settting up UDMA2 mode on Aladdin chip OK ad2: ATA-3 disk at ata1 as master ad2: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ata1: slave: settting up UDMA2 mode on Aladdin chip OK ad3: ATA-4 disk at ata1 as slave ad3: 16479MB (33750864 sectors), 33483 cyls, 16 heads, 63 S/T, 512 B/S ad3: piomode=4, dmamode=2, udmamode=2 ad3: 16 secs/int, 0 depth queue, DMA mode ad3 is the one getting the heaviest use, from me... However, I notice a few things from when I went to the ata driver, from a 3.1 kernel using the wd0 driver. The drive is now much slower... While I don't have numbers either way, this system acts as a nfs server. Not only are the NFS clients acting slower after my switch, but nearly all my nfsd's are sitting in biord or biowr now, where before they were usually idle. Also, the IDE LED on the case/motherboard is now acting kinda erratic. I can hear the HD doing accesses when the light is off, and at times the light seems to stay on for 2-3 seconds, when there's no activity. (This didn't happen under wd0)... Is this a case of DMA just not working well for me, or is there a magic flag I'm missing? This is -current from about a week ago. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 1:40:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (Postfix) with ESMTP id 54D5714C2B for ; Fri, 14 May 1999 01:40:24 -0700 (PDT) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@FreeBSD.ORG; Fri, 14 May 1999 10:40:22 +0200 (MET DST) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.3/8.9.3) id GAA00562 for freebsd-current@FreeBSD.ORG; Fri, 14 May 1999 06:40:48 +0200 (CEST) (envelope-from tanis) Date: Fri, 14 May 1999 06:40:48 +0200 From: German Tischler To: freebsd-current@FreeBSD.ORG Subject: Re: egcs, libstdc++, libg++, Class Library Message-ID: <19990514064048.A549@gaspode.franken.de> References: <199905140138.SAA07432@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Thomas T. Veldhouse on Thu, May 13, 1999 at 09:32:06PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 13, 1999 at 09:32:06PM -0500, Thomas T. Veldhouse wrote: > Have you tried using the C++ standard way? It works. > > #include > #include > > using namespace std; > > Of course, there are many times you won't want to include the entire > namespace. You don't need to. EGCS is still buggy with namespaces because namespace std is on by default. -- German Tischler tanis@gaspode.franken.de tanis@cip.informatik.uni-wuerzburg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 1:58:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 9974814D27 for ; Fri, 14 May 1999 01:58:47 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id IAA13038; Fri, 14 May 1999 08:57:19 GMT Message-Id: <199905140857.IAA13038@chandra.eatell.msr.prug.or.jp> To: Dag-Erling Smorgrav Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "14 May 1999 10:18:14 +0200." Date: Fri, 14 May 1999 17:57:18 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is pointless. All you're doing is pointing your finger and > screaming "It's not right! It's not fair!" without saying anything of > actual value. OK OK, you are right. I have language barrier, so I can't explain well. I talk other newconfig member, one of member, Furuta-san will go to Usenix and presentation of newconfig paper. After Usenix, still misunderstanding is exist, argument again. I will become to explain if needed. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 May 14 2: 9:30 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 9776215431 for ; Fri, 14 May 1999 02:09:27 -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 LAA42053; Fri, 14 May 1999 11:09:20 +0200 (CEST) (envelope-from des) To: NAKAGAWA Yoshihisa Cc: Dag-Erling Smorgrav , Garrett Wollman , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c References: <199905140857.IAA13038@chandra.eatell.msr.prug.or.jp> From: Dag-Erling Smorgrav Date: 14 May 1999 11:09:19 +0200 In-Reply-To: NAKAGAWA Yoshihisa's message of "Fri, 14 May 1999 17:57:18 +0900" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NAKAGAWA Yoshihisa writes: > OK OK, you are right. I have language barrier, so I can't explain > well. I talk other newconfig member, one of member, Furuta-san > will go to Usenix and presentation of newconfig paper. Any chance of getting a preview of that paper? Is it, or will it be, available on the Web? DES (who won't make it to Usenix this year...) -- 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 Fri May 14 2:36:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 4469C15511 for ; Fri, 14 May 1999 02:36:27 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id JAA13117; Fri, 14 May 1999 09:35:01 GMT Message-Id: <199905140935.JAA13117@chandra.eatell.msr.prug.or.jp> To: Dag-Erling Smorgrav Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "14 May 1999 11:09:19 +0200." Date: Fri, 14 May 1999 18:34:55 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Any chance of getting a preview of that paper? Is it, or will it be, > available on the Web? I don't know, probably the paper not yet available on Web. Please ask to Furuta-san. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 May 14 2:40:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B2FF8154FF for ; Fri, 14 May 1999 02:40:27 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id SAA21896; Fri, 14 May 1999 18:40:17 +0900 (JST) Message-ID: <373BEACA.47B5E5DF@newsguy.com> Date: Fri, 14 May 1999 18:20:10 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c References: <199905122252.SAA73553@misha.cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > > Mike Smith once wrote: > > > For a usable dynamic architecture, loadable modules need to be > > compiled to support both UP and SMP architectures simultaneously. Thus > > the locking primitives need to be conditionalised at _runtime_. > > What about > > kldload /modules/up/whatever.ko > and > kldload /modules/smp/whatever.ko > > and even > > kldload /debug-modules/up/whatever.ko > [...] Horrible kludges. Things should just work. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 2:41: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 3DBD814E2A; Fri, 14 May 1999 02:40:54 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id SAA21792; Fri, 14 May 1999 18:39:52 +0900 (JST) Message-ID: <373BDC51.94DAEF2F@newsguy.com> Date: Fri, 14 May 1999 17:18:25 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Wilko Bulte Cc: "Rodney W. Grimes" , mark@grondar.za, dfr@nlsystems.com, khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: de driver problem References: <199905122202.AAA04213@yedi.iaf.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > Sounds very reasonable to me. Running the same command twice to get > things really clean sounds suspicious ;-) > > In any case: I'm rebuilding now after a cvsup && chflags -R noschg > /usr/obj/* && rm -rf /usr/obj/* > > We'll see what happens next. Nothing will happen, I suppose. The idea of running clean twice is that the first one will remove /usr/obj, and the second will remove .o files in the *source* tree. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 2:41:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id DB53215489; Fri, 14 May 1999 02:41:39 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id SAA21753; Fri, 14 May 1999 18:39:34 +0900 (JST) Message-ID: <373BDBED.3AE1742@newsguy.com> Date: Fri, 14 May 1999 17:16:45 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Rodney W. Grimes" Cc: Mark Murray , Wilko Bulte , dfr@nlsystems.com, khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: de driver problem References: <199905122044.NAA03768@gndrsh.aac.dev.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" wrote: > > > I periodically see this one reported, and It is always repaired > > by the reporter making sure their tree is _really_ clean before > > doing a make world. "Really clean" means "make cleandir" _twice_, > > This indicates to me, the original author of ``cleandir'', that > something has broken the functionality that it had. This something > is more than likely the removal of code similiar to: > > cd /usr/obj/{.CURDIR}; chflags -R noschg tmp; rm -rf *; > > before the equiv of: > cd {.CURDIR}; ${make} clean > > > and complete removal of the contents of /usr/obj. _Then_ cvsup. > > I prefer to usr CVS checkout, as it shows all the differences and > > other turds in my source tree. > > If ``make cleandir'' is leaving some cruft in any form behind anyplace > in the build tree things are broken. Not really. The problem results from people doing subtree makes (including cleans), which results in .o files in the source tree instead of the object tree. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 2:50:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id E8EA5155FB for ; Fri, 14 May 1999 02:50:08 -0700 (PDT) (envelope-from furuta@sra.co.jp) Received: from ext105.sra.co.jp (ext105 [133.137.20.200]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with SMTP id SAA10072 for ; Fri, 14 May 1999 18:50:07 +0900 (JST) Received: by ext105.sra.co.jp; id AA15933; Fri, 14 May 1999 18:50:06 +0900 To: des@flood.ping.uio.no Cc: y-nakaga@nwsl.mesh.ad.jp, wollman@khavrinen.lcs.mit.edu, current@freebsd.org Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: Your message of "14 May 1999 11:09:19 +0200" References: X-Mailer: Mew version 1.92.4 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990514185006V.furuta@sra.co.jp> Date: Fri, 14 May 1999 18:50:06 +0900 From: Atsushi Furuta X-Dispatcher: imput version 980905(IM100) Lines: 14 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> In article , Dag-Erling Smorgrav writes: > Any chance of getting a preview of that paper? Is it, or will it be, > available on the Web? Nakagawa-san slightly misunderstands. I have no time to write full paper, so I have already submitted presentation slide. Instead of it, I will also write speech draft of the presentation, and will place anywhere before the talk. Please wait. -- furuta@sra.co.jp (Atsushi Furuta) Advanced Technology Group. Software Research Associates, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 5:29: 5 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 12D33154B6 for ; Fri, 14 May 1999 05:28:57 -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 2.12 #1) id 10iH4f-0000pk-00; Fri, 14 May 1999 14:28:21 +0200 From: Sheldon Hearn To: Matthew Thyer Cc: camel@avias.com, current@FreeBSD.ORG, "Steve O'Hara-Smith" , Kazutaka YOKOTA Subject: Re: problem with NewScroll Mouse, etc In-reply-to: Your message of "Thu, 13 May 1999 23:14:25 +0930." <373AD739.6D8C3038@camtech.com.au> Date: Fri, 14 May 1999 14:28:21 +0200 Message-ID: <3207.926684901@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 13 May 1999 23:14:25 +0930, Matthew Thyer wrote: > This is the PS/2 Intellimouse clone. (I'm note sure if 'real' > MicroSoft Intellimice work ??). Mine does under CURRENT. 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 May 14 5:38:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 5C032154B6 for ; Fri, 14 May 1999 05:38:21 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA18895; Fri, 14 May 1999 21:37:50 +0900 (JST) Message-ID: <373BFBB9.194C91BC@newsguy.com> Date: Fri, 14 May 1999 19:32:25 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Stefan Bethke Cc: Andrzej Bialecki , Peter Wemm , current@FreeBSD.ORG Subject: Re: somebody has broken sysctlbyname() in -current References: <64131.3135500516@d225.promo.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan Bethke wrote: > > Any pointer on Forth literature/web pages would be appreciated, especially > if it's not the ANSI standard (I've looked at it, and it is that: a > standard, not a reference manual or a tutorial). My Forth knowledge is > rather rusty, I realised... last time I remember I was sitting in front of > my Apple II clone about 15 years ago. A number of documents, including tutorials, can be found starting at www.forth.org. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 5:38:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 526801562D for ; Fri, 14 May 1999 05:38:45 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA19038; Fri, 14 May 1999 21:38:32 +0900 (JST) Message-ID: <373C0CFD.7D9D3775@newsguy.com> Date: Fri, 14 May 1999 20:46:05 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: NAKAGAWA Yoshihisa Cc: Dag-Erling Smorgrav , Garrett Wollman , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c References: <199905130238.CAA11000@chandra.eatell.msr.prug.or.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NAKAGAWA Yoshihisa wrote: > > > Then explain to us why newbus is wrong and why the 4.4BSD scheme is > > right. > > Because, you are misunderstanding 4.4BSD scheme (and newconfig). The *GOAL* here is the following: You bought a computer with the super-ultra-new Microsoft (tm) Microsoft Bus (tm), for which you bought the latest and greatest device X. Now, you want device X to work. Your FreeBSD 4.5 doesn't know about Microsoft Bus, much less about device X. As it happens, this Microsoft Bus is actually mounted through USB, which happens to be available through an CardBus device, which is actually mounted on a PCI card providing the bus. What you *must* achieve is the following: cd /modules fetch http://www.microsoft.com/FreeBSD/drivers/yeah.sure./msbus.ko fetch http://www.company.x.com/drivers/deviceX/x.ko kldload x results in the msbus being loaded on demand, located and mounted across the assorted bridges, and device X driver then getting loaded, having it's resources automatically set up, and becoming available for use. No kernel recompiling of file editing can be added to above sequence, and other files should be kept to the minimum possible (strictly -- if it can be done with less, it should be done with less). The newconfig opponents fear that one must edit some file to add the information that x must be mounted over msbus, or even worse (such as kernel recompiling). If you can show that the four lines above would suffice in newconfig, you got a winner. Feel free to change the kldload x to dconfig x if you like, but 'dconfig x "at msbus"' will not be well received. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 5:39: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A954E1558A for ; Fri, 14 May 1999 05:38:59 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA18961; Fri, 14 May 1999 21:38:08 +0900 (JST) Message-ID: <373C07D6.F8ACE796@newsguy.com> Date: Fri, 14 May 1999 20:24:06 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: John-Mark Gurney Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: the new config and booting References: <199905120817.KAA03605@peedub.muc.de> <199905122203.PAA01488@dingo.cdrom.com> <19990512165906.57576@hydrogen.nike.efn.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John-Mark Gurney wrote: > > I did a couple installs using normal slices and standard MBR, and when > the machine restarted, I got the "Operating System Missing" error... > the only way I was able to install on the system was to use dangerous > dedicated mode... I've seen this happen a couple times w/ 3.0-R and > 3.1-19990328-STABLE IIRC... Standard MBR? How about using booteasy/boot0 instead? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 5:39:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 4BCE0154B6 for ; Fri, 14 May 1999 05:39:08 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA19021; Fri, 14 May 1999 21:38:29 +0900 (JST) Message-ID: <373C09EF.E3B0D4F2@newsguy.com> Date: Fri, 14 May 1999 20:33:03 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: David Schwartz Cc: Chuck Robey , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c References: <000001be9ce8$291f3790$021d85d1@whenever.youwant.to> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Schwartz wrote: > > Believe it or not, good ideas can even come from people who can't code at > all, and the ideas are just as good. Slapping these people down just ensures > they don't contribute in the future. > > Now if their ideas genuinely are bad, you are more than welcome to slap > them down as much as you wish. If that means they don't contribute more bad > ideas in the future, so much the better. Heck, it even may save you the idea > of having to explain why the bad idea is, in fact, bad. > > But "if it's such a good idea, why don't you code it?" doesn't fall into > any of these categories. It's one of those "that's what you think" type > arguments that serves as an excuse to ignore the merits of the other side's > case. Well, it would help if the people who can't code wouldn't so often make bad suggestions and then keep trying someone else to implement them even when the people who *can* code tells them it's a bad idea, and they just won't take that for an answer. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 5:41: 9 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 D6129155F6 for ; Fri, 14 May 1999 05:41:03 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id HAA26832; Fri, 14 May 1999 07:39:29 -0500 (CDT) Date: Fri, 14 May 1999 07:39:29 -0500 From: "Matthew D. Fuller" To: Sheldon Hearn Cc: Gianmarco Giovannelli , "'current@freebsd.org'" Subject: Re: Today's kernel crashes on starting X Message-ID: <19990514073929.A26478@futuresouth.com> References: <4.1.19990514011159.01bc1590@194.184.65.4> <287.926641048@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <287.926641048@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, May 14, 1999 at 02:17:28AM +0200 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 14, 1999 at 02:17:28AM +0200, a little birdie told me that Sheldon Hearn remarked > > > On Fri, 14 May 1999 01:13:36 +0200, Gianmarco Giovannelli wrote: > > > Here it continues to panic with screen, same errors of yesterday... I'll > > try with X right now but I think it is the same story... :-) > > Cvsupped and maked world this afternoon (CEST). > > Well guesss what? I'm seeing panics too, after suggesting that > everything was cool and froody. :-) > > I don't have to start X, I get a panic as soon as I try to mount_mfs > -- 100% reproducible. Someone else posted a backtrace, the one that > incriminates checkalias(), I think? I have one here with sources cvsup'd around 4am (CDT) today (as in, ~4 hours ago). Start X, start up screen in an xterm, and *bing*. However, I strut my skill in manpiluating DDB while staring at a frozen X session ;> Here's some quickies from kgdb: Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 0c000000 fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0162490 stack pointer = 0x10:0xcb271d4c frame pointer = 0x10:0xcb271d60 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 = 570 (screen-3.7.6) interrupt mask = tty <- SMP: XXX panic: from debugger mp_lock = 01000003; cpuid = 1; lapic.id = 0c000000 boot() called on cpu#1 (kgdb) where #0 0xc014f350 in boot () #1 0xc014f6ed in panic () #2 0xc012c899 in db_panic () #3 0xc012c839 in db_command () #4 0xc012c8fe in db_command_loop () #5 0xc012ea5f in db_trap () #6 0xc0213982 in kdb_trap () #7 0xc02265c2 in trap_fatal () #8 0xc0226259 in trap_pfault () #9 0xc0225ecf in trap () #10 0xc0162490 in ttyflush () #11 0xc0161bf1 in ttioctl () #12 0xc01650fe in ptyioctl () #13 0xc0181ad0 in spec_ioctl () #14 0xc01812f1 in spec_vnoperate () #15 0xc01f64c9 in ufs_vnoperatespec () #16 0xc017c045 in vn_ioctl () #17 0xc015b73f in ioctl () #18 0xc0226886 in syscall () #19 0xc02143a5 in Xint0x80_syscall () Unfortunately, it seems to be not giving me symbols. I'll try recompiling it with makeoptions=-g and see if I can't pull up one more good panic/dump real quick. -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller MF4839 http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 5:55:51 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 16BAB14D84 for ; Fri, 14 May 1999 05:55:45 -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 2.12 #1) id 10iHUW-0002Pi-00; Fri, 14 May 1999 14:55:04 +0200 From: Sheldon Hearn To: "Matthew D. Fuller" Cc: Gianmarco Giovannelli , "'current@freebsd.org'" Subject: Re: Today's kernel crashes on starting X In-reply-to: Your message of "Fri, 14 May 1999 07:39:29 EST." <19990514073929.A26478@futuresouth.com> Date: Fri, 14 May 1999 14:55:04 +0200 Message-ID: <9281.926686504@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 May 1999 07:39:29 EST, "Matthew D. Fuller" wrote: > I have one here with sources cvsup'd around 4am (CDT) today (as in, > ~4 hours ago). Start X, start up screen in an xterm, and *bing*. > However, I strut my skill in manpiluating DDB while staring at a > frozen X session ;> Unfortunately, I'm using Soren's new ATA* driver, so I can't get crashdumps. Copying panics and backtraces is a PIAWUTA, as you can well imagine. 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 May 14 6:11:37 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 2CB8314D84 for ; Fri, 14 May 1999 06:11:32 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id IAA28401; Fri, 14 May 1999 08:10:53 -0500 (CDT) Date: Fri, 14 May 1999 08:10:53 -0500 From: "Matthew D. Fuller" To: Sheldon Hearn Cc: Gianmarco Giovannelli , "'current@freebsd.org'" Subject: Panic with screen w/info (was Re: Today's kernel crashes on starting X) Message-ID: <19990514081052.A27823@futuresouth.com> References: <19990514073929.A26478@futuresouth.com> <9281.926686504@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <9281.926686504@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, May 14, 1999 at 02:55:04PM +0200 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, this apparently doesn't involve X, only screen. (X may still be broken/flaky, but this doesn't involve it specifically) This time I just ran screen on a vty, and *poof* ------ Looking at the trace below, does this look like a (if not the) problem? #10 0xc0162490 in ttyflush (tp=0xc029dc20, rw=3) at ../../kern/tty.c:1192 1192 (*devsw(tp->t_dev)->d_stop)(tp, rw); (kgdb) print tp $1 = (struct tty *) 0xc30010b2 (kgdb) print tp->t_dev Cannot access memory at address 0xc300110a. ------ I can keep this trace and compile tree around for a good while, just let me know what to poke at and I'll prod it. Panic msg and trace below. ------ Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 0c000000 fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0162490 stack pointer = 0x10:0xcb1c9d4c frame pointer = 0x10:0xcb1c9d60 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 = 372 (screen-3.7.6) interrupt mask = tty <- SMP: XXX panic: from debugger mp_lock = 01000003; cpuid = 1; lapic.id = 0c000000 boot() called on cpu#1 #0 boot (howto=256) at ../../kern/kern_shutdown.c:288 #1 0xc014f6ed in panic (fmt=0xc0253514 "from debugger") at ../../kern/kern_shutdown.c:451 #2 0xc012c899 in db_panic (addr=-1072290672, have_addr=0, count=-1, modif=0xcb1c9bc8 "") at ../../ddb/db_command.c:434 #3 0xc012c839 in db_command (last_cmdp=0xc027e870, cmd_table=0xc027e6d0, aux_cmd_tablep=0xc029ac78) at ../../ddb/db_command.c:334 #4 0xc012c8fe in db_command_loop () at ../../ddb/db_command.c:456 #5 0xc012ea5f in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #6 0xc0213982 in kdb_trap (type=12, code=0, regs=0xcb1c9d0c) at ../../i386/i386/db_interface.c:157 #7 0xc02265c2 in trap_fatal (frame=0xcb1c9d0c, eva=20) at ../../i386/i386/trap.c:912 #8 0xc0226259 in trap_pfault (frame=0xcb1c9d0c, usermode=0, eva=20) at ../../i386/i386/trap.c:810 #9 0xc0225ecf in trap (frame={tf_fs = -2147483624, tf_es = -1054801904, tf_ds = 16777232, tf_edi = -2147483648, tf_esi = 3, tf_ebp = -887317152, tf_isp = -887317192, tf_ebx = -1070998496, tf_edx = 0, tf_ecx = 16777217, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1072290672, tf_cs = 8, tf_eflags = 66178, tf_esp = -1070998496, tf_ss = 3}) at ../../i386/i386/trap.c:436 #10 0xc0162490 in ttyflush (tp=0xc029dc20, rw=3) at ../../kern/tty.c:1192 #11 0xc0161bf1 in ttioctl (tp=0xc029dc20, cmd=2147775504, data=0xcb1c9ecc, flag=3) at ../../kern/tty.c:803 #12 0xc01650fe in ptyioctl (dev=0xf700, cmd=2147775504, data=0xcb1c9ecc "\003", flag=3, p=0xc9d9ea20) at ../../kern/tty_pty.c:740 #13 0xc0181ad0 in spec_ioctl (ap=0xcb1c9e08) at ../../miscfs/specfs/spec_vnops.c:441 #14 0xc01812f1 in spec_vnoperate (ap=0xcb1c9e08) at ../../miscfs/specfs/spec_vnops.c:129 #15 0xc01f64c9 in ufs_vnoperatespec (ap=0xcb1c9e08) at ../../ufs/ufs/ufs_vnops.c:2327 #16 0xc017c045 in vn_ioctl (fp=0xc1196bc0, com=2147775504, data=0xcb1c9ecc "\003", p=0xc9d9ea20) at vnode_if.h:395 #17 0xc015b73f in ioctl (p=0xc9d9ea20, uap=0xcb1c9f80) at ../../kern/sys_generic.c:564 #18 0xc0226886 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134697096, tf_esi = 134672224, tf_ebp = -1077951692, tf_isp = -887316524, tf_ebx = 672221300, tf_edx = 134697128, tf_ecx = 6, tf_eax = 54, tf_trapno = 12, tf_err = 2, tf_eip = 671965400, tf_cs = 31, tf_eflags = 582, tf_esp = -1077951716, tf_ss = 47}) at ../../i386/i386/trap.c:1066 #19 0xc02143a5 in Xint0x80_syscall () ------ -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller MF4839 http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 6:17:55 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 B50F914DB9 for ; Fri, 14 May 1999 06:17:51 -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 PAA42884; Fri, 14 May 1999 15:17:24 +0200 (CEST) (envelope-from des) To: Ilya Naumov Cc: Geoff Rehmet , current@FreeBSD.ORG Subject: Re: Today's kernel crashes on starting X References: <3D5EC7D2992BD211A95600A0C9CE047F0308D99F@isjhbex01.is.co.za> <18898.990512@avias.com> From: Dag-Erling Smorgrav Date: 14 May 1999 15:17:23 +0200 In-Reply-To: Ilya Naumov's message of "Wed, 12 May 1999 21:33:14 +0400" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ilya Naumov writes: > GR> I'm currently running into a problem, that when I start my system, > GR> it spontaneously reboots when starting X. Has anyone else run into > GR> this? > yes, i'm experiencing the same problem with today's (May, 12) kernels. Me three. The box freezes solid before switching to graphics mode. Didn't have time to grab relevant info as this is my home box and I was late for work. 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 Fri May 14 7: 7:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from kirk.giovannelli.it (kirk.giovannelli.it [194.184.65.4]) by hub.freebsd.org (Postfix) with ESMTP id 7ABC51537C for ; Fri, 14 May 1999 07:07:03 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem00.masternet.it [194.184.65.10]) by kirk.giovannelli.it (8.9.3/8.9.2) with SMTP id OAA04569 for ; Fri, 14 May 1999 14:06:57 GMT (envelope-from gmarco@giovannelli.it) Message-Id: <4.1.19990514142618.009a10c0@194.184.65.4> X-Sender: gmarco@194.184.65.4 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 14 May 1999 14:36:58 +0200 To: current@freebsd.org From: Gianmarco Giovannelli Subject: panic still here ... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This morning after cvsupping I made a world again, but "screen" continue to go in panics. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc685bd64 stack pointer = 0x10:0xc685bd64 frame pointer = 0x10:0xc685bd78 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume , IOPL=0 current process = 374 (screen-3.7.6) interrupt mask = tty kernel : type 12 trap, code 0 Stopped at ttyflush+0x48: movl 0x14(%eax), %eax It is identical at yesterday panics ... Please test also to your system. I'd like to know I am the only it happened to :-) Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 8:11:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 4720B15427 for ; Fri, 14 May 1999 08:11:11 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup2-57.iptelecom.net.ua [212.42.68.248]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id SAA03449 for ; Fri, 14 May 1999 18:12:44 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id SAA61493 for ; Fri, 14 May 1999 18:10:59 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <373C3D02.2B20CBC2@altavista.net> Date: Fri, 14 May 1999 18:10:58 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: New ATA driver still can't attach to ISA controllers Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Soren, Do you remember that currently your famous driver (after new-bus announcement) don't probed on ISA hardwsre (in my case Toshiba CDX445)? Sincerely, Maxim     To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 8:18: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.sitaranetworks.com (apollo.sitaranetworks.com [199.103.141.105]) by hub.freebsd.org (Postfix) with ESMTP id 2825F1511B for ; Fri, 14 May 1999 08:17:58 -0700 (PDT) (envelope-from john@loverso.southborough.ma.us) Message-ID: <373C3E17.66362795@loverso.southborough.ma.us> Date: Fri, 14 May 1999 11:15:35 -0400 From: "John R. LoVerso" MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: Berkeley DB 1.85 --> 2.0 References: <19990513164720.A26399@trinsec.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of course, DB 2 is still available as an easily installed port/package. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 8:21:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from deep-thought.demos.su (deep-thought.demos.su [194.87.1.76]) by hub.freebsd.org (Postfix) with ESMTP id 529AD1511B for ; Fri, 14 May 1999 08:21:35 -0700 (PDT) (envelope-from ache@deep-thought.demos.su) Received: (from ache@localhost) by deep-thought.demos.su (8.9.3/8.9.3) id TAA42780; Fri, 14 May 1999 19:21:24 +0400 (MSD) (envelope-from ache) Date: Fri, 14 May 1999 19:21:23 +0400 From: "Andrey A. Chernov" To: "John R. LoVerso" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Berkeley DB 1.85 --> 2.0 Message-ID: <19990514192123.A42749@nagual.pp.ru> References: <19990513164720.A26399@trinsec.com> <373C3E17.66362795@loverso.southborough.ma.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <373C3E17.66362795@loverso.southborough.ma.us>; from john@loverso.southborough.ma.us on Fri, May 14, 1999 at 11:15:35AM -0400 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 14, 1999 at 11:15:35AM -0400, John R. LoVerso wrote: > Of course, DB 2 is still available as an easily installed port/package. Not so easily, it conflict with libc's DB in subtle but harmful manner. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 8:41:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 47F3014C3D for ; Fri, 14 May 1999 08:41:44 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id RAA27281 for ; Fri, 14 May 1999 17:41:43 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma027279; Fri, 14 May 99 17:41:43 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id RAA08328 for ; Fri, 14 May 1999 17:41:42 +0200 (MET DST) Received: (qmail 35459 invoked by uid 666); 14 May 1999 15:42:03 -0000 Date: Fri, 14 May 1999 17:42:03 +0200 From: Jos Backus To: freebsd-current@FreeBSD.ORG Subject: Re: Berkeley DB 1.85 --> 2.0 Message-ID: <19990514174203.A35400@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990513164720.A26399@trinsec.com> <373C3E17.66362795@loverso.southborough.ma.us> <19990514192123.A42749@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990514192123.A42749@nagual.pp.ru>; from Andrey A. Chernov on Fri, May 14, 1999 at 07:21:23PM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 14, 1999 at 07:21:23PM +0400, Andrey A. Chernov wrote: > Not so easily, it conflict with libc's DB in subtle but harmful manner. Talking about upgrades: people on the mutt-dev list say our (outdated) ncurses is to blame for not dealing properly with SIGWINCH. Newer versions (4.2 at least) are said to get it right. Would installing the ncurses port be able to cause similar problems? Just wondering... -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 9:17:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D724714CEF for ; Fri, 14 May 1999 09:17:27 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.1) id JAA28823; Fri, 14 May 1999 09:17:24 -0700 (PDT) (envelope-from obrien) Message-ID: <19990514091724.A28816@nuxi.com> Date: Fri, 14 May 1999 09:17:24 -0700 From: "David O'Brien" To: Jos Backus , freebsd-current@FreeBSD.ORG Subject: Re: Berkeley DB 1.85 --> 2.0 Reply-To: obrien@NUXI.com References: <19990513164720.A26399@trinsec.com> <373C3E17.66362795@loverso.southborough.ma.us> <19990514192123.A42749@nagual.pp.ru> <19990514174203.A35400@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990514174203.A35400@hal.mpn.cp.philips.com>; from Jos Backus on Fri, May 14, 1999 at 05:42:03PM +0200 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Talking about upgrades: people on the mutt-dev list say our (outdated) ncurses > is to blame for not dealing properly with SIGWINCH. Works fine with libslang. > Newer versions (4.2 at least) are said to get it right. Would > installing the ncurses port be able to cause similar problems? Mutt will resize Ok with the Ncurses port. However, it is a huge library. libslang is much smaller. -- -- David (obrien@NUXI.com -or- obrien@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 May 14 9:41:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 1ED1D14E0B for ; Fri, 14 May 1999 09:41:42 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id SAA13772 for ; Fri, 14 May 1999 18:41:41 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma013770; Fri, 14 May 99 18:41:41 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id SAA23174 for ; Fri, 14 May 1999 18:41:40 +0200 (MET DST) Received: (qmail 35871 invoked by uid 666); 14 May 1999 16:42:01 -0000 Date: Fri, 14 May 1999 18:42:01 +0200 From: Jos Backus To: freebsd-current@FreeBSD.ORG Subject: Re: Berkeley DB 1.85 --> 2.0 Message-ID: <19990514184201.A35822@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990513164720.A26399@trinsec.com> <373C3E17.66362795@loverso.southborough.ma.us> <19990514192123.A42749@nagual.pp.ru> <19990514174203.A35400@hal.mpn.cp.philips.com> <19990514091724.A28816@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990514091724.A28816@nuxi.com>; from David O'Brien on Fri, May 14, 1999 at 09:17:24AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 14, 1999 at 09:17:24AM -0700, David O'Brien wrote: > Works fine with libslang. Indeed it does. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 10: 5:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.digitalselect.net (mail.digitalselect.net [216.181.1.6]) by hub.freebsd.org (Postfix) with ESMTP id 9C13314D34 for ; Fri, 14 May 1999 10:05:11 -0700 (PDT) (envelope-from adhir@forumone.com) Received: from digitalselect ([216.181.56.84]) by mail.digitalselect.net (8.8.7/8.8.7) with SMTP id NAA28958; Fri, 14 May 1999 13:02:44 -0400 Reply-To: From: "Alok K. Dhir" To: "Brian Feldman" , "Jordan K. Hubbard" Cc: "Poul-Henning Kamp" , "Soren Schmidt" , "Dag-Erling Smorgrav" , Subject: RE: DMA problems with IBM DeskStar drive Date: Fri, 14 May 1999 13:04:49 -0400 Message-ID: <001101be9e2b$dfebafa0$5438b5d8@net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look for that setting in the SCSI BIOS.... > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Brian Feldman > Sent: Thursday, May 13, 1999 7:52 PM > To: Jordan K. Hubbard > Cc: Poul-Henning Kamp; Soren Schmidt; Dag-Erling Smorgrav; > current@FreeBSD.ORG > Subject: Re: DMA problems with IBM DeskStar drive > > > On Wed, 12 May 1999, Jordan K. Hubbard wrote: > > > > Try disabling "ultra DMA" in the BIOS, that seems to have worked for > > > me on my IBM-DJNA-371800 drive. > > > > > > (Jordan: We may want to put something in the README about > this in 3.2!) > > > > I'd welcome suggestions as to what the text should look like; I'm > > still unclear as to what exactly the problem us. :) > > > > I'd also be interested to know how you plan on describing > disabling UDMA, since > I don't see that option in my AMIBIOS. > > > - Jordan > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Brian Feldman _ __ ___ ____ ___ ___ ___ > green@unixhelp.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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 10: 6:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id 630441544A for ; Fri, 14 May 1999 10:06:30 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id TAA08212; Fri, 14 May 1999 19:06:20 +0200 (CEST) (envelope-from des) To: Cc: "Brian Feldman" , "Jordan K. Hubbard" , "Poul-Henning Kamp" , "Soren Schmidt" , "Dag-Erling Smorgrav" , Subject: Re: DMA problems with IBM DeskStar drive References: <001101be9e2b$dfebafa0$5438b5d8@net> Organization: Yes! Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 14 May 1999 19:06:20 +0200 In-Reply-To: "Alok K. Dhir"'s message of "Fri, 14 May 1999 13:04:49 -0400" Message-ID: Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alok K. Dhir" writes: > Look for that setting in the SCSI BIOS.... I think not. DES -- Dag-Erling Smorgrav - des@yes.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 10:14: 5 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 6ADFC14DF2 for ; Fri, 14 May 1999 10:14:03 -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 NAA52876; Fri, 14 May 1999 13:09:49 -0400 (EDT) Date: Fri, 14 May 1999 13:09:48 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Dag-Erling Smorgrav Cc: adhir@forumone.com, "Jordan K. Hubbard" , Poul-Henning Kamp , Soren Schmidt , current@FreeBSD.ORG Subject: Re: DMA problems with IBM DeskStar drive 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 14 May 1999, Dag-Erling Smorgrav wrote: > "Alok K. Dhir" writes: > > Look for that setting in the SCSI BIOS.... > > I think not. I think not too. EIDE drives tend to not mess with SCSI too much... > > DES > -- > Dag-Erling Smorgrav - des@yes.no > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 Fri May 14 10:17:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id CB6CC14DF2 for ; Fri, 14 May 1999 10:17:38 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id NAA06110; Fri, 14 May 1999 13:17:32 -0400 (EDT) (envelope-from luoqi) Date: Fri, 14 May 1999 13:17:32 -0400 (EDT) From: Luoqi Chen Message-Id: <199905141717.NAA06110@lor.watermarkgroup.com> To: fullermd@futuresouth.com, sheldonh@uunet.co.za Subject: Re: Panic with screen w/info (was Re: Today's kernel crashes on starting X) Cc: current@FreeBSD.ORG, gmarco@scotty.masternet.it Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that screen was trying to flush the master pty, before the slave tty was even open. We were lucky that this didn't crash our machines before the dev_t changes, it only caused the console to be flushed instead. But after the dev_t changes, it is fatal. Try this fix (band-aid only, better fix should involve checking of TS_OPEN bit), Index: tty_pty.c =================================================================== RCS file: /home/ncvs/src/sys/kern/tty_pty.c,v retrieving revision 1.57 diff -u -r1.57 tty_pty.c --- tty_pty.c 1999/05/08 06:39:43 1.57 +++ tty_pty.c 1999/05/14 16:51:58 @@ -336,6 +336,7 @@ tp = &pt_tty[minor(dev)]; if (tp->t_oproc) return (EIO); + tp->t_dev = dev; tp->t_oproc = ptsstart; #ifdef sun4c tp->t_stop = ptsstop; -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 10:19: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.digitalselect.net (mail.digitalselect.net [216.181.1.6]) by hub.freebsd.org (Postfix) with ESMTP id 92E3A14D34 for ; Fri, 14 May 1999 10:18:49 -0700 (PDT) (envelope-from adhir@forumone.com) Received: from digitalselect ([216.181.56.84]) by mail.digitalselect.net (8.8.7/8.8.7) with SMTP id NAA30736; Fri, 14 May 1999 13:18:10 -0400 Reply-To: From: "Alok K. Dhir" To: "Brian Feldman" , "Dag-Erling Smorgrav" Cc: "Jordan K. Hubbard" , "Poul-Henning Kamp" , "Soren Schmidt" , Subject: RE: DMA problems with IBM DeskStar drive Date: Fri, 14 May 1999 13:20:14 -0400 Message-ID: <001201be9e2e$076caf00$5438b5d8@net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry - I spaced. I read 'UltraSCSI', not 'UltraDMA'. *sheepish grin* Al > -----Original Message----- > From: Brian Feldman [mailto:green@unixhelp.org] > Sent: Friday, May 14, 1999 1:10 PM > To: Dag-Erling Smorgrav > Cc: adhir@forumone.com; Jordan K. Hubbard; Poul-Henning Kamp; Soren > Schmidt; current@FreeBSD.ORG > Subject: Re: DMA problems with IBM DeskStar drive > > > On 14 May 1999, Dag-Erling Smorgrav wrote: > > > "Alok K. Dhir" writes: > > > Look for that setting in the SCSI BIOS.... > > > > I think not. > > I think not too. EIDE drives tend to not mess with SCSI too much... > > > > > DES > > -- > > Dag-Erling Smorgrav - des@yes.no > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Brian Feldman _ __ ___ ____ ___ ___ ___ > green@unixhelp.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 Fri May 14 10:33:28 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 C363214E66 for ; Fri, 14 May 1999 10:33:25 -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 KAA00886; Fri, 14 May 1999 10:29:35 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905141729.KAA00886@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Matthew D. Fuller" Cc: Sheldon Hearn , Gianmarco Giovannelli , "'current@freebsd.org'" Subject: Re: Panic with screen w/info (was Re: Today's kernel crashes on starting X) In-reply-to: Your message of "Fri, 14 May 1999 08:10:53 CDT." <19990514081052.A27823@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 May 1999 10:29:35 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This looks a lot like the "I didn't use 'config -r' to generate my latest kernel build tree" problem. > Well, this apparently doesn't involve X, only screen. > (X may still be broken/flaky, but this doesn't involve it specifically) > This time I just ran screen on a vty, and *poof* > > ------ > Looking at the trace below, does this look like a (if not the) problem? > #10 0xc0162490 in ttyflush (tp=0xc029dc20, rw=3) at ../../kern/tty.c:1192 > 1192 (*devsw(tp->t_dev)->d_stop)(tp, rw); > (kgdb) print tp > $1 = (struct tty *) 0xc30010b2 > (kgdb) print tp->t_dev > Cannot access memory at address 0xc300110a. > ------ > > I can keep this trace and compile tree around for a good while, just let > me know what to poke at and I'll prod it. Panic msg and trace below. > > ------ > Fatal trap 12: page fault while in kernel mode > mp_lock = 01000002; cpuid = 1; lapic.id = 0c000000 > fault virtual address = 0x14 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0162490 > stack pointer = 0x10:0xcb1c9d4c > frame pointer = 0x10:0xcb1c9d60 > 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 = 372 (screen-3.7.6) > interrupt mask = tty <- SMP: XXX > panic: from debugger > mp_lock = 01000003; cpuid = 1; lapic.id = 0c000000 > boot() called on cpu#1 > > > #0 boot (howto=256) at ../../kern/kern_shutdown.c:288 > #1 0xc014f6ed in panic (fmt=0xc0253514 "from debugger") at > ../../kern/kern_shutdown.c:451 > #2 0xc012c899 in db_panic (addr=-1072290672, have_addr=0, count=-1, > modif=0xcb1c9bc8 "") > at ../../ddb/db_command.c:434 > #3 0xc012c839 in db_command (last_cmdp=0xc027e870, cmd_table=0xc027e6d0, > > aux_cmd_tablep=0xc029ac78) at ../../ddb/db_command.c:334 > #4 0xc012c8fe in db_command_loop () at ../../ddb/db_command.c:456 > #5 0xc012ea5f in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 > #6 0xc0213982 in kdb_trap (type=12, code=0, regs=0xcb1c9d0c) > at ../../i386/i386/db_interface.c:157 > #7 0xc02265c2 in trap_fatal (frame=0xcb1c9d0c, eva=20) at > ../../i386/i386/trap.c:912 > #8 0xc0226259 in trap_pfault (frame=0xcb1c9d0c, usermode=0, eva=20) > at ../../i386/i386/trap.c:810 > #9 0xc0225ecf in trap (frame={tf_fs = -2147483624, tf_es = -1054801904, > tf_ds = 16777232, > tf_edi = -2147483648, tf_esi = 3, tf_ebp = -887317152, tf_isp = > -887317192, > tf_ebx = -1070998496, tf_edx = 0, tf_ecx = 16777217, tf_eax = 0, > tf_trapno = 12, > tf_err = 0, tf_eip = -1072290672, tf_cs = 8, tf_eflags = 66178, > tf_esp = -1070998496, > tf_ss = 3}) at ../../i386/i386/trap.c:436 > #10 0xc0162490 in ttyflush (tp=0xc029dc20, rw=3) at ../../kern/tty.c:1192 > #11 0xc0161bf1 in ttioctl (tp=0xc029dc20, cmd=2147775504, > data=0xcb1c9ecc, flag=3) > at ../../kern/tty.c:803 > #12 0xc01650fe in ptyioctl (dev=0xf700, cmd=2147775504, data=0xcb1c9ecc > "\003", flag=3, > p=0xc9d9ea20) at ../../kern/tty_pty.c:740 > #13 0xc0181ad0 in spec_ioctl (ap=0xcb1c9e08) at > ../../miscfs/specfs/spec_vnops.c:441 > #14 0xc01812f1 in spec_vnoperate (ap=0xcb1c9e08) at > ../../miscfs/specfs/spec_vnops.c:129 > #15 0xc01f64c9 in ufs_vnoperatespec (ap=0xcb1c9e08) at > ../../ufs/ufs/ufs_vnops.c:2327 > #16 0xc017c045 in vn_ioctl (fp=0xc1196bc0, com=2147775504, > data=0xcb1c9ecc "\003", > p=0xc9d9ea20) at vnode_if.h:395 > #17 0xc015b73f in ioctl (p=0xc9d9ea20, uap=0xcb1c9f80) at > ../../kern/sys_generic.c:564 > #18 0xc0226886 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = 134697096, > tf_esi = 134672224, tf_ebp = -1077951692, tf_isp = -887316524, > tf_ebx = 672221300, > tf_edx = 134697128, tf_ecx = 6, tf_eax = 54, tf_trapno = 12, tf_err > = 2, > tf_eip = 671965400, tf_cs = 31, tf_eflags = 582, tf_esp = > -1077951716, tf_ss = 47}) > at ../../i386/i386/trap.c:1066 > #19 0xc02143a5 in Xint0x80_syscall () > ------ > > > > -- > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* > | Matthew Fuller MF4839 http://www.over-yonder.net/ | > * fullermd@futuresouth.com fullermd@over-yonder.net * > | UNIX Systems Administrator Specializing in FreeBSD | > * FutureSouth Communications ISPHelp ISP Consulting * > | "The only reason I'm burning my candle at both ends, | > * is because I haven't figured out how to light the * > | middle yet" | > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 10:36:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 1B645151A2 for ; Fri, 14 May 1999 10:36:42 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id NAA06376; Fri, 14 May 1999 13:36:41 -0400 (EDT) (envelope-from luoqi) Date: Fri, 14 May 1999 13:36:41 -0400 (EDT) From: Luoqi Chen Message-Id: <199905141736.NAA06376@lor.watermarkgroup.com> To: fullermd@futuresouth.com, sheldonh@uunet.co.za Subject: Re: Panic with screen w/info (was Re: Today's kernel crashes on starting X) Cc: current@FreeBSD.ORG, gmarco@scotty.masternet.it Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems that screen was trying to flush the master pty, before the slave > tty was even open. We were lucky that this didn't crash our machines before > the dev_t changes, it only caused the console to be flushed instead. But > after the dev_t changes, it is fatal. Try this fix (band-aid only, better > fix should involve checking of TS_OPEN bit), > Here's the better fix, please let me know if it works, Index: tty_pty.c =================================================================== RCS file: /home/ncvs/src/sys/kern/tty_pty.c,v retrieving revision 1.57 diff -u -r1.57 tty_pty.c --- tty_pty.c 1999/05/08 06:39:43 1.57 +++ tty_pty.c 1999/05/14 17:32:33 @@ -674,8 +674,7 @@ tp->t_lflag &= ~EXTPROC; } return(0); - } else - if (devsw(dev)->d_open == ptcopen) + } else if (devsw(dev)->d_open == ptcopen) { switch (cmd) { case TIOCGPGRP: @@ -711,7 +710,16 @@ pti->pt_flags &= ~PF_REMOTE; ttyflush(tp, FREAD|FWRITE); return (0); + } + + /* + * The rest of the ioctls shouldn't be called until + * the slave is open. (Should we return an error?) + */ + if ((tp->t_state & TS_ISOPEN) == 0) + return (0); + switch (cmd) { #ifdef COMPAT_43 case TIOCSETP: case TIOCSETN: @@ -735,6 +743,7 @@ ttyinfo(tp); return(0); } + } error = (*linesw[tp->t_line].l_ioctl)(tp, cmd, data, flag, p); if (error == ENOIOCTL) error = ttioctl(tp, cmd, data, flag); -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 11:24:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 7D49214CD5 for ; Fri, 14 May 1999 11:24:27 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id OAA06861; Fri, 14 May 1999 14:24:26 -0400 (EDT) (envelope-from luoqi) Date: Fri, 14 May 1999 14:24:26 -0400 (EDT) From: Luoqi Chen Message-Id: <199905141824.OAA06861@lor.watermarkgroup.com> To: obrien@NUXI.com Subject: Re: Today's kernel crashes on starting X Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This was due to a kludge in mfs implementation. Try change NUMCDEV in > > kern_conf.c to 255. > > Are you saying that there is a bug in the mfs implementation and a fix > will be commited soon? (and change NUMCDEV until then) > > Or are you saying, the mfs implementation is now considered correct (but > there are some kludges in there) and that changing NUMCDEV in kern_conf.c > to 255 is the perminate fix? > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > This is a fundamental problem with mfs' design, mfs steals bdev major 255 for its private use. One thing we could do is to have mfs legally acquire this major number, i.e., setup a devsw structure and register with device conf system. This problem probably would go away after we have a fully functional DEVFS. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 11:44:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id BBF7214D10 for ; Fri, 14 May 1999 11:44:10 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA21535; Fri, 14 May 1999 20:44:00 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA14183; Fri, 14 May 1999 20:43:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Luoqi Chen Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: Today's kernel crashes on starting X In-reply-to: Your message of "Fri, 14 May 1999 14:24:26 EDT." <199905141824.OAA06861@lor.watermarkgroup.com> Date: Fri, 14 May 1999 20:43:53 +0200 Message-ID: <14181.926707433@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905141824.OAA06861@lor.watermarkgroup.com>, Luoqi Chen writes: >> > This was due to a kludge in mfs implementation. Try change NUMCDEV in >> > kern_conf.c to 255. >> >> Are you saying that there is a bug in the mfs implementation and a fix >> will be commited soon? (and change NUMCDEV until then) >> >> Or are you saying, the mfs implementation is now considered correct (but >> there are some kludges in there) and that changing NUMCDEV in kern_conf.c >> to 255 is the perminate fix? >> >> -- >> -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) >> >This is a fundamental problem with mfs' design, mfs steals bdev major 255 for >its private use. One thing we could do is to have mfs legally acquire this >major number, i.e., setup a devsw structure and register with device conf >system. This problem probably would go away after we have a fully functional >DEVFS. I would prefer if somebody would make MFS register a devsw* entry now, because that would also work if/when DEVFS comes to town... -- 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 Fri May 14 12:12:18 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 9135414E18 for ; Fri, 14 May 1999 12:12:13 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id OAA21292; Fri, 14 May 1999 14:11:52 -0500 (CDT) Date: Fri, 14 May 1999 14:11:52 -0500 From: "Matthew D. Fuller" To: Luoqi Chen Cc: sheldonh@uunet.co.za, current@FreeBSD.ORG, gmarco@scotty.masternet.it Subject: Re: Panic with screen w/info (was Re: Today's kernel crashes on starting X) Message-ID: <19990514141151.B21020@futuresouth.com> References: <199905141736.NAA06376@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199905141736.NAA06376@lor.watermarkgroup.com>; from Luoqi Chen on Fri, May 14, 1999 at 01:36:41PM -0400 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 14, 1999 at 01:36:41PM -0400, a little birdie told me that Luoqi Chen remarked > Here's the better fix, please let me know if it works, I won't be in a position to crash this box again until tomorrow, but I'll give it a whirl then. Thanks. > Index: tty_pty.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/tty_pty.c,v > retrieving revision 1.57 > diff -u -r1.57 tty_pty.c > --- tty_pty.c 1999/05/08 06:39:43 1.57 > +++ tty_pty.c 1999/05/14 17:32:33 > @@ -674,8 +674,7 @@ > tp->t_lflag &= ~EXTPROC; > } > return(0); > - } else > - if (devsw(dev)->d_open == ptcopen) > + } else if (devsw(dev)->d_open == ptcopen) { > switch (cmd) { > > case TIOCGPGRP: > @@ -711,7 +710,16 @@ > pti->pt_flags &= ~PF_REMOTE; > ttyflush(tp, FREAD|FWRITE); > return (0); > + } > + > + /* > + * The rest of the ioctls shouldn't be called until > + * the slave is open. (Should we return an error?) > + */ > + if ((tp->t_state & TS_ISOPEN) == 0) > + return (0); > > + switch (cmd) { > #ifdef COMPAT_43 > case TIOCSETP: > case TIOCSETN: > @@ -735,6 +743,7 @@ > ttyinfo(tp); > return(0); > } > + } > error = (*linesw[tp->t_line].l_ioctl)(tp, cmd, data, flag, p); > if (error == ENOIOCTL) > error = ttioctl(tp, cmd, data, flag); -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller MF4839 http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 12:25:12 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 E05D514CB6 for ; Fri, 14 May 1999 12:25:09 -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 MAA14736; Fri, 14 May 1999 12:21:33 -0700 (PDT) Date: Fri, 14 May 1999 12:21:32 -0700 (PDT) From: Julian Elischer To: Luoqi Chen Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: Today's kernel crashes on starting X In-Reply-To: <199905141824.OAA06861@lor.watermarkgroup.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, 14 May 1999, Luoqi Chen wrote: > > > This was due to a kludge in mfs implementation. Try change NUMCDEV in > > > kern_conf.c to 255. > > > > Are you saying that there is a bug in the mfs implementation and a fix > > will be commited soon? (and change NUMCDEV until then) > > > > Or are you saying, the mfs implementation is now considered correct (but > > there are some kludges in there) and that changing NUMCDEV in kern_conf.c > > to 255 is the perminate fix? > > > > -- > > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > > This is a fundamental problem with mfs' design, mfs steals bdev major 255 for > its private use. One thing we could do is to have mfs legally acquire this > major number, i.e., setup a devsw structure and register with device conf > system. This problem probably would go away after we have a fully functional > DEVFS. Actually this problem is the one that makes DEVFS explode.. It does an alias lookup on it's 'dummy' vnode and since teh sytem has been switched to use devfs routines for everything, some of it's assumptions are not longer true.. > > -lq > > > 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 May 14 12:30:46 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 422F714CB6 for ; Fri, 14 May 1999 12:30:43 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA16976; Fri, 14 May 1999 21:30:40 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905141930.VAA16976@freebsd.dk> Subject: Re: New ATA driver still can't attach to ISA controllers In-Reply-To: <373C3D02.2B20CBC2@altavista.net> from Maxim Sobolev at "May 14, 1999 6:10:58 pm" To: sobomax@altavista.net Date: Fri, 14 May 1999 21:30:40 +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 Maxim Sobolev wrote: >Dear Soren, > >Do you remember that currently your famous driver (after new-bus >announcement) don't probed on ISA hardwsre (in my case Toshiba CDX445)? > Yes, and I have the patches right here, I just need to test it a bit more and get the time to commit it (hopefully this weekend). -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 May 14 12:34:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.goti.net (mail.goti.net [208.156.60.71]) by hub.freebsd.org (Postfix) with ESMTP id DFFD214CB6 for ; Fri, 14 May 1999 12:34:21 -0700 (PDT) (envelope-from drosehn@goti.net) Received: from [192.168.1.8] [38.26.183.139] by mail.goti.net with ESMTP (SMTPD32-5.01) id ABBE2F38014A; Fri, 14 May 1999 15:38:38 EDT Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosehn@mail.goti.net (Unverified) Message-Id: In-Reply-To: References: <199905112056.WAA18582@labinfo.iet.unipi.it> Date: Fri, 14 May 1999 15:35:52 -0400 To: Ustimenko Semen , Luigi Rizzo From: Garance A Drosehn Subject: Re: Nt source licenses... Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote: > Are we going to get this license? I am interested in NTFS > source code a lot... I would be very careful about getting an NT source license if your intention is to write NTFS support for some other operating system. Microsoft is not doing this licensing for the benefit of mankind, they are doing it to attract college-type users to sticking with WinNT over open-source unixes. The last thing we need is some code from WinNT which causes us to be sued by Microsoft... --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer (MIME & NeXTmail capable) Rensselaer Polytechnic Institute; Troy NY USA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 12:37:43 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 1290914CB6 for ; Fri, 14 May 1999 12:37:38 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA17009; Fri, 14 May 1999 21:37:24 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905141937.VAA17009@freebsd.dk> Subject: Re: Alladdin IDE slow? In-Reply-To: <199905140819.DAA05339@home.dragondata.com> from Kevin Day at "May 14, 1999 3:19:40 am" To: toasty@home.dragondata.com (Kevin Day) Date: Fri, 14 May 1999 21:37:24 +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 Kevin Day wrote: > > I'm using an Alladin chipset in a -current machine... > > ad3 is the one getting the heaviest use, from me... However, I notice a few > things from when I went to the ata driver, from a 3.1 kernel using the wd0 > driver. > > The drive is now much slower... While I don't have numbers either way, this > system acts as a nfs server. Not only are the NFS clients acting slower > after my switch, but nearly all my nfsd's are sitting in biord or biowr now, > where before they were usually idle. > > Also, the IDE LED on the case/motherboard is now acting kinda erratic. I can > hear the HD doing accesses when the light is off, and at times the light > seems to stay on for 2-3 seconds, when there's no activity. (This didn't > happen under wd0)... > > Is this a case of DMA just not working well for me, or is there a magic flag > I'm missing? This is -current from about a week ago. Hmm, this sounds stange, I have a noard here with the Alladin on it on which I did the support for the ata driver, it works just fine for me at least... -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 May 14 12:46:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from xap.xyplex.com (xap.xyplex.com [140.179.130.200]) by hub.freebsd.org (Postfix) with ESMTP id 5716114D82 for ; Fri, 14 May 1999 12:46:21 -0700 (PDT) (envelope-from rwhitesel@nbase-xyplex.com) Received: from pcrlw (pcrlw.xyplex.com [140.179.228.211]) by xap.xyplex.com (8.8.5/8.7.3) with SMTP id PAA17610; Fri, 14 May 1999 15:36:42 -0400 (EDT) Message-ID: <000f01be9e42$0b999fc0$d3e4b38c@xyplex.com> From: "Rick Whitesel" To: "Soren Schmidt" Cc: References: <199905141930.VAA16976@freebsd.dk> Subject: Re: New ATA driver still can't attach to ISA controllers Date: Fri, 14 May 1999 15:43:30 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 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 Hi: I just wanted to say that I really appreciate the work you have/are doing. The disk drive performance under IDE is very important for the practical use of FreeBSD. Thank you! Rick Whitesel Scientist NBase-Xyplex Eml: rwhitesel@nbase-xyplex.com "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 ----- Original Message ----- From: Soren Schmidt To: Cc: Sent: Friday, May 14, 1999 3:30 PM Subject: Re: New ATA driver still can't attach to ISA controllers It seems Maxim Sobolev wrote: >Dear Soren, > >Do you remember that currently your famous driver (after new-bus >announcement) don't probed on ISA hardwsre (in my case Toshiba CDX445)? > Yes, and I have the patches right here, I just need to test it a bit more and get the time to commit it (hopefully this weekend). -Søren 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 May 14 15:34:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 50BB614CB6 for ; Fri, 14 May 1999 15:34:41 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40359>; Sat, 15 May 1999 08:19:41 +1000 Date: Sat, 15 May 1999 08:34:33 +1000 From: Peter Jeremy Subject: Inlining ucmpdi2 et al To: current@FreeBSD.ORG Message-Id: <99May15.081941est.40359@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A recent commit by "Justin T. Gibbs" : > Nuke ucmpdi2.c from i386/libkern to serve as a reminder that switch > statements on 64bit values generate poor code. Looking thru libkern, many of the functions shouldn't be there since gcc should be generating in-line code. I believe the following are (or should be) superfluous: adddi3.c anddi3.c ashldi3.c ashrdi3.c cmpdi2.c iordi3.c lshldi3.c lshrdi3.c negdi2.c notdi2.c subdi3.c ucmpdi2.c udivdi3.c umoddi3.c xordi3.c I know gcc-2.8.1 had a bug relating to cmpdi2. It seems the fix didn't make it into egcs. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 16: 9:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (Postfix) with ESMTP id D715D1564A for ; Fri, 14 May 1999 16:09:38 -0700 (PDT) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id DAA14661; Sat, 15 May 1999 03:05:58 +0400 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.3/8.9.1) with ESMTP id DAA01957; Sat, 15 May 1999 03:09:29 +0400 (MSD) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199905142309.DAA01957@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Andrey A. Chernov" Cc: "John R. LoVerso" , freebsd-current@FreeBSD.ORG Subject: Re: Berkeley DB 1.85 --> 2.0 In-reply-to: Your message of "Fri, 14 May 1999 19:21:23 +0400." <19990514192123.A42749@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 May 1999 03:09:28 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > On Fri, May 14, 1999 at 11:15:35AM -0400, John R. LoVerso wrote: > > Of course, DB 2 is still available as an easily installed port/package. > > Not so easily, it conflict with libc's DB in subtle but harmful manner. Only if it is configured with --enable-compat185. Just Don't Do That. (Yep, the port do it, and for this reason I consider it broken). Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 16:15:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 49D4514FFF for ; Fri, 14 May 1999 16:15:14 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup3-12.iptelecom.net.ua [212.42.69.203]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id CAA09441 for ; Sat, 15 May 1999 02:16:56 +0300 (EEST) Message-ID: <373CAED8.AC9377DA@altavista.net> Date: Sat, 15 May 1999 02:16:40 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Solved: NPX code reports negative i586_bzero() bandwidth References: <3735833E.1B1011B4@altavista.net> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > i586_bzero() bandwidth = -2082577916 bytes/sec > bzero() bandwidth = 184877056 bytes/sec It seems that on a fast machines with a lot of cache long type is not sufficient to print i586_bzero bandwith values in bytes/s (in my case it was slightly overruned). Following is the patch: --- npx.c.orig Sat May 15 01:14:13 1999 +++ npx.c Sat May 15 02:01:51 1999 @@ -696,8 +696,8 @@ if (usec <= 0) usec = 1; if (bootverbose) - printf("%s bandwidth = %ld bytes/sec\n", - funcname, (long)(BUFSIZE * (int64_t)1000000 / usec)); + printf("%s bandwidth = %ld Kbytes/sec\n", + funcname, (long)(BUFSIZE * (int64_t)1000000 / (1024*usec))); free(buf, M_TEMP); return (usec); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 17:34:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.25]) by hub.freebsd.org (Postfix) with ESMTP id AC3B814E6C for ; Fri, 14 May 1999 17:34:48 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id TAA01092; Fri, 14 May 1999 19:34:45 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 14 May 1999 19:34:43 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: current@freebsd.org Subject: stable snap for smp? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14140.48742.126448.712700@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If anyone has applied reasonable stress to a recent MP kernel, preferrably with X, VESA, VM86, and found it stable, do please report on your last cvs update time: I, for one, would very much like to isolate a fairly stable post-newbus world. Presumably this would be helpful to other readers as well, it being so much easier to bounce between worlds which are more nearly contemporaneous. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 18:13: 0 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 D14B814D63 for ; Fri, 14 May 1999 18:12: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 LAA05294; Sat, 15 May 1999 11:12:54 +1000 Date: Sat, 15 May 1999 11:12:54 +1000 From: Bruce Evans Message-Id: <199905150112.LAA05294@godzilla.zeta.org.au> To: current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au Subject: Re: Inlining ucmpdi2 et al Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Looking thru libkern, many of the functions shouldn't be there since >gcc should be generating in-line code. I believe the following are >(or should be) superfluous: adddi3.c anddi3.c ashldi3.c ashrdi3.c >cmpdi2.c iordi3.c lshldi3.c lshrdi3.c negdi2.c notdi2.c subdi3.c >ucmpdi2.c udivdi3.c umoddi3.c xordi3.c We leave all these out (of files.i386) for i386's, but they might be necessary for another arch, and *cmpdi2.c turn out to be not quite superfluous. >I know gcc-2.8.1 had a bug relating to cmpdi2. It seems the fix didn't >make it into egcs. The one for comparison in 64-bit signed divisions seems to be fixed, but there is another for 64-bit case comparisons. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 18:38: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 5BD7E14EE3 for ; Fri, 14 May 1999 18:38:39 -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 LAA15873; Sat, 15 May 1999 11:08:36 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA39507; Sat, 15 May 1999 11:08:35 +0930 (CST) Date: Sat, 15 May 1999 11:08:34 +0930 From: Greg Lehey To: Gianmarco Giovannelli Cc: current@FreeBSD.ORG Subject: Re: panic still here ... Message-ID: <19990515110834.J89091@freebie.lemis.com> References: <4.1.19990514142618.009a10c0@194.184.65.4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <4.1.19990514142618.009a10c0@194.184.65.4>; from Gianmarco Giovannelli on Fri, May 14, 1999 at 02:36:58PM +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 Friday, 14 May 1999 at 14:36:58 +0200, Gianmarco Giovannelli wrote: > > This morning after cvsupping I made a world again, but "screen" continue to > go in panics. > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x14 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc685bd64 > stack pointer = 0x10:0xc685bd64 > frame pointer = 0x10:0xc685bd78 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume , IOPL=0 > current process = 374 (screen-3.7.6) > interrupt mask = tty > kernel : type 12 trap, code 0 > Stopped at ttyflush+0x48: movl 0x14(%eax), %eax > > It is identical at yesterday panics ... > Please test also to your system. I'd like to know I am the only it happened > to :-) The real thing to do here is to take a dump and see where it's happening. There's a description in the handbook. Contact me if you have trouble. 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 Fri May 14 19: 5:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (ykh28DS24.kng.mesh.ad.jp [133.205.214.24]) by hub.freebsd.org (Postfix) with ESMTP id 157D515469 for ; Fri, 14 May 1999 19:05:21 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id QAA13434; Fri, 14 May 1999 16:22:48 GMT Message-Id: <199905141622.QAA13434@chandra.eatell.msr.prug.or.jp> To: "Daniel C. Sobral" Cc: Dag-Erling Smorgrav , Garrett Wollman , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Fri, 14 May 1999 20:46:05 JST." <373C0CFD.7D9D3775@newsguy.com> Date: Sat, 15 May 1999 01:22:47 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You bought a computer with the super-ultra-new Microsoft (tm) > Microsoft Bus (tm), for which you bought the latest and greatest > device X. It is extremely vulgar joke. I doubt your character. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 May 14 19:41:32 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 A6E9A151EB for ; Fri, 14 May 1999 19:41:28 -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 MAA11478; Sat, 15 May 1999 12:41:25 +1000 Date: Sat, 15 May 1999 12:41:25 +1000 From: Bruce Evans Message-Id: <199905150241.MAA11478@godzilla.zeta.org.au> To: jdp@polstra.com, peter@netplex.com.au Subject: Re: Heads up! config(8) changes.. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In old mail, John Polstra wrote: >In article <19990424190901.D3A791F58@spinner.netplex.com.au>, >Peter Wemm wrote: >> ... >> So: things like: >> device sio1 at isa? tty port "IO_COM2" tty irq 3 >> become: >> device sio1 at isa? port IO_COM2 irq3 > >What do you do about the "ppc" device? Formerly, it needed to be "net >irq ..." if the "plip" device was going to be used, but "tty irq ..." >otherwise. Which one did you pick? tty was picked (see isa_compat.h). Also, support for the hack of setting net_imask = tty_imask if slip is configured went away, so slip now has the same problems as plip. I think most of these problems can be avoided by configuring (kernel) ppp. ppp sets net_imask >= tty_imask, which is sufficient provided slip and plip call splimp() as required. Only cases where the masks change significantly after ppp is initialised are necessarily broken. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 21:22:59 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 6FD4A14C97 for ; Fri, 14 May 1999 21:22:57 -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 VAA18763; Fri, 14 May 1999 21:22:55 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id VAA03469; Fri, 14 May 1999 21:22:55 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199905150241.MAA11478@godzilla.zeta.org.au> Date: Fri, 14 May 1999 21:22:55 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Bruce Evans Subject: Re: Heads up! config(8) changes.. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > In old mail, John Polstra wrote: >> >>What do you do about the "ppc" device? Formerly, it needed to be "net >>irq ..." if the "plip" device was going to be used, but "tty irq ..." >>otherwise. Which one did you pick? > > tty was picked (see isa_compat.h). Also, support for the hack of > setting net_imask = tty_imask if slip is configured went away, so slip > now has the same problems as plip. I think most of these problems can be > avoided by configuring (kernel) ppp. ppp sets net_imask >= tty_imask, > which is sufficient provided slip and plip call splimp() as required. > Only cases where the masks change significantly after ppp is initialised > are necessarily broken. It seems to me that all this spl hackery would be better avoided, through a userland approach that used the tun device or something similar. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 21:46: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtprtp (smtprtp.NortelNetworks.com [192.122.117.66]) by hub.freebsd.org (Postfix) with ESMTP id 700C314E6F for ; Fri, 14 May 1999 21:45:53 -0700 (PDT) (envelope-from atrens@nortelnetworks.com) Received: from zcars01t by smtprtp; Sat, 15 May 1999 00:43:03 -0400 Received: from hcarp00g.ca.nortel.com by zcars01t; Sat, 15 May 1999 00:42:20 -0400 Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.9.3/8.7.3) with ESMTP id AAA72763; Sat, 15 May 1999 00:43:19 -0400 (EDT) Date: Sat, 15 May 1999 00:43:19 -0400 (EDT) From: "Andrew Atrens" Reply-To: "Andrew Atrens" To: Soren Schmidt Cc: Rick Whitesel , current Subject: Re: New ATA driver still can't attach to ISA controllers In-Reply-To: <000f01be9e42$0b999fc0$d3e4b38c@xyplex.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, 14 May 1999, Rick Whitesel wrote: > I just wanted to say that I really appreciate the work you have/are > doing. The disk drive performance under IDE is very important for the > practical use of FreeBSD. > > Thank you! I second that - thank you ! Andrew. -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 21:47: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 77AE514E6F for ; Fri, 14 May 1999 21:46:55 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id NAA06746; Sat, 15 May 1999 13:46:02 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: y-nakaga@nwsl.mesh.ad.jp Cc: dcs@newsguy.com, des@flood.ping.uio.no, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Cc: soda@sra.co.jp Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: cvs commit: src/sys/pci pcisupport.c From: Tomoaki NISHIYAMA In-Reply-To: <199905141622.QAA13434@chandra.eatell.msr.prug.or.jp> References: <199905141622.QAA13434@chandra.eatell.msr.prug.or.jp> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990515134601P.tomoaki@moss.nibb.ac.jp> Date: Sat, 15 May 1999 13:46:01 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 14 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: NAKAGAWA Yoshihisa y-nakaga> > You bought a computer with the super-ultra-new Microsoft (tm) y-nakaga> > Microsoft Bus (tm), for which you bought the latest and greatest y-nakaga> > device X. y-nakaga> y-nakaga> It is extremely vulgar joke. I doubt your character. No, I don't think this is a joke, but a serious situation. We should stick on technical problem if we continue to discuss. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 14 23:42:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 837EB14E27 for ; Fri, 14 May 1999 23:42:07 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id IAA00227; Sat, 15 May 1999 08:42:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id IAA18435; Sat, 15 May 1999 08:41:56 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: Luoqi Chen , obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: Today's kernel crashes on starting X In-reply-to: Your message of "Fri, 14 May 1999 12:21:32 PDT." Date: Sat, 15 May 1999 08:41:56 +0200 Message-ID: <18433.926750516@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Julian Elischer writes: > >On Fri, 14 May 1999, Luoqi Chen wrote: > >> > > This was due to a kludge in mfs implementation. Try change NUMCDEV in >> > > kern_conf.c to 255. >> > >> > Are you saying that there is a bug in the mfs implementation and a fix >> > will be commited soon? (and change NUMCDEV until then) >> > >> > Or are you saying, the mfs implementation is now considered correct (but >> > there are some kludges in there) and that changing NUMCDEV in kern_conf.c >> > to 255 is the perminate fix? >> > >> > -- >> > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) >> > >> This is a fundamental problem with mfs' design, mfs steals bdev major 255 for >> its private use. One thing we could do is to have mfs legally acquire this >> major number, i.e., setup a devsw structure and register with device conf >> system. This problem probably would go away after we have a fully functional >> DEVFS. > >Actually this problem is the one that makes DEVFS explode.. >It does an alias lookup on it's 'dummy' vnode and since teh sytem has been >switched to use devfs routines for everything, some of it's >assumptions are not longer true.. I don't expect the current DEVFS prototype to be indicative of how our real DEVFS will work. -- 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 May 15 1: 0: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 422CA14C9D for ; Sat, 15 May 1999 01:00:01 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id QAA19076; Sat, 15 May 1999 16:59:51 +0900 (JST) Message-ID: <373D27FB.D34161C6@newsguy.com> Date: Sat, 15 May 1999 16:53:31 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Tomoaki NISHIYAMA Cc: y-nakaga@nwsl.mesh.ad.jp, des@flood.ping.uio.no, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG, soda@sra.co.jp Subject: Re: cvs commit: src/sys/pci pcisupport.c References: <199905141622.QAA13434@chandra.eatell.msr.prug.or.jp> <19990515134601P.tomoaki@moss.nibb.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tomoaki NISHIYAMA wrote: > > From: NAKAGAWA Yoshihisa > y-nakaga> > You bought a computer with the super-ultra-new Microsoft (tm) > y-nakaga> > Microsoft Bus (tm), for which you bought the latest and greatest > y-nakaga> > device X. > y-nakaga> > y-nakaga> It is extremely vulgar joke. I doubt your character. > > No, I don't think this is a joke, but a serious situation. > We should stick on technical problem if we continue to discuss. I replied to this in private, but, for the record, it was not a joke. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 1:29:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (Postfix) with ESMTP id CF78E14C9D for ; Sat, 15 May 1999 01:28:47 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id UAA00923; Sat, 15 May 1999 20:28:45 +1200 (NZST) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.3/8.9.2) id UAA09892; Sat, 15 May 1999 20:28:45 +1200 (NZST) (envelope-from jabley) Date: Sat, 15 May 1999 20:28:45 +1200 From: Joe Abley To: freebsd-current@freebsd.org Cc: jabley@clear.co.nz Subject: ftp.nz.freebsd.org Message-ID: <19990515202845.B9762@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, CLEAR is operating a pretty full mirror of ftp.freebsd.org:/pub/FreeBSD/ at ftp.clear.net.nz:/pub/FreeBSD/. Dan Langille has kindly made ftp.nz.freebsd.org a CNAME to ftp.clear.net.nz to make this easier to find. Just thought I'd mention it -- I haven't done a clean install for a long time, so I don't know whether ftp.nz.freebsd.org is given explicitly as an option for network installs. But if it isn't, it might be good to put it in. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 4:27:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 992AE14DEC for ; Sat, 15 May 1999 04:27:37 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id NAA12069; Sat, 15 May 1999 13:27:27 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Sat, 15 May 1999 13:27:27 +0200 (CEST) From: Leif Neland To: Bob Fayne Cc: freebsd-current@FreeBSD.ORG Subject: Skip fail under current, was: Re: VPN betwwen Windows 9x Clients and FreeBSD Firewall In-Reply-To: <4.1.19990427201132.00a47cd0@dnsdata.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 Tue, 27 Apr 1999, Bob Fayne wrote: > At 05:40 PM 4/27/99, you wrote: > >I am looking for a firewall/VPN solution that will allow our company > >personnel to connect to the corporate network using there Win95 laptops and > >a Dynamic IP address from there ISP, when they are out traveling or working > >from home. > > Try the SKIP port. > > http://skip.incog.com. The 40-bit Win95 client is free, and 56/128 clients > are available from Sun. > It won't compile under current. freebsd/skip_es.c breaks at if (suser(p->p_ucred, &p->p_acflag )) { This won't compile, because suser only has one parameter. Trying blindly to change it to: if (suser(p->p_ucred)) { Makes it compile (it has lots of warnings though), but gives a panic when trying to load skip.ko Leif Neland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 4:33:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id BAEE0150F5 for ; Sat, 15 May 1999 04:33:25 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id NAA07943; Sat, 15 May 1999 13:33:24 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id NAA19504; Sat, 15 May 1999 13:33:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Leif Neland Cc: Bob Fayne , freebsd-current@FreeBSD.ORG Subject: Re: Skip fail under current, was: Re: VPN betwwen Windows 9x Clients and FreeBSD Firewall In-reply-to: Your message of "Sat, 15 May 1999 13:27:27 +0200." Date: Sat, 15 May 1999 13:33:16 +0200 Message-ID: <19502.926767996@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Leif Nel and writes: >It won't compile under current. >freebsd/skip_es.c breaks at > > if (suser(p->p_ucred, &p->p_acflag )) { > >This won't compile, because suser only has one parameter. > >Trying blindly to change it to: > > if (suser(p->p_ucred)) { Better yet, read the manpage for suser(9) and change it to: if (suser(p)) { -- 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 May 15 4:51:55 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 266F615049 for ; Sat, 15 May 1999 04:51:52 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id EAA00560; Sat, 15 May 1999 04:52:40 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "John W. DeBoskey" Cc: freebsd-current@freebsd.org Subject: Re: /usr/src/release/Makefile patch In-reply-to: Your message of "Tue, 11 May 1999 23:51:32 EDT." <199905120351.XAA24516@bb01f39.unx.sas.com> Date: Sat, 15 May 1999 04:52:40 -0700 Message-ID: <556.926769160@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Could you please consider the following patch to > /usr/src/release/Makefile? It may not be entirely correct, > but it allows a 'cd /usr/src/release && make release' to > run to completion. In the kernel makefile, 'kernel' > is not a target, ${KERNEL} is, and ${KERNEL} has the value > 'GENERIC'. Sorry, I was swamped with 3.2 stuff. Done! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 4:55:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with ESMTP id 53FA414D03 for ; Sat, 15 May 1999 04:55:33 -0700 (PDT) (envelope-from gjvc@extremis.demon.co.uk) Received: (from gjvc@localhost) by extremis.demon.co.uk (8.9.3/8.9.1) id LAA65534 for freebsd-current@freebsd.org; Sat, 15 May 1999 11:55:42 GMT (envelope-from gjvc) Date: Sat, 15 May 1999 11:55:42 +0000 From: George Cox To: freebsd-current@freebsd.org Subject: screen panics -current Message-ID: <19990515115540.B65473@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i X-Operating-System: FreeBSD extremis.demon.co.uk 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, this is just a quick note to anyone more knowledgable than me. screen 3.7.6 panics a current kernel. -- [gjvc] "We're not laughing at you; we're laughing with you." "But I'm not laughing." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 5:41: 5 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 E157914D03 for ; Sat, 15 May 1999 05:40:57 -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 IAA73146; Sat, 15 May 1999 08:38:33 -0400 (EDT) Date: Sat, 15 May 1999 08:38:33 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Andrew Atrens Cc: Soren Schmidt , Rick Whitesel , current Subject: Re: New ATA driver still can't attach to ISA controllers 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, 15 May 1999, Andrew Atrens wrote: > > On Fri, 14 May 1999, Rick Whitesel wrote: > > > I just wanted to say that I really appreciate the work you have/are > > doing. The disk drive performance under IDE is very important for the > > practical use of FreeBSD. > > > > Thank you! > > > I second that - thank you ! Heck, I'll third that! Now my wish list includes spelling correction (settting? heh, I have the patch at home), a d_dump_t, and possibly getting afd working, but that's not very much. This driver's already wonderful, without some of the last things I want, and is so FAST! > > > Andrew. > > -- > +-- > | Andrew Atrens Nortel Networks, Ottawa, Canada. | > | All opinions expressed are my own, not those of any employer. | > --+ > Heller's Law: The first myth of management is that it exists. > Johnson's Corollary: Nobody really knows what is going on > anywhere within the organization. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 Sat May 15 6:45:22 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 3176314D61 for ; Sat, 15 May 1999 06:45:14 -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 JAA12663; Sat, 15 May 1999 09:42:11 -0400 (EDT) Date: Sat, 15 May 1999 09:42:10 -0400 (EDT) From: Chuck Robey To: "Daniel C. Sobral" Cc: Tomoaki NISHIYAMA , y-nakaga@nwsl.mesh.ad.jp, des@flood.ping.uio.no, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG, soda@sra.co.jp Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <373D27FB.D34161C6@newsguy.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 Sat, 15 May 1999, Daniel C. Sobral wrote: > Tomoaki NISHIYAMA wrote: > > > > From: NAKAGAWA Yoshihisa > > y-nakaga> > You bought a computer with the super-ultra-new Microsoft (tm) > > y-nakaga> > Microsoft Bus (tm), for which you bought the latest and greatest > > y-nakaga> > device X. > > y-nakaga> > > y-nakaga> It is extremely vulgar joke. I doubt your character. > > > > No, I don't think this is a joke, but a serious situation. > > We should stick on technical problem if we continue to discuss. > > I replied to this in private, but, for the record, it was not a > joke. I understand it wasn't a joke, but it *was* funny, and he wasn't abusing things. I don't think it's too fair to jump on him over it (you didn't, Daniel). A little humor is allowed, as long as things are kept in proportion, right? Enough. ----------------------------+----------------------------------------------- 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 (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 7: 7:44 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 3D5CD14DEC for ; Sat, 15 May 1999 07:07:40 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id QAA20755; Sat, 15 May 1999 16:06:25 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905151406.QAA20755@freebsd.dk> Subject: Re: New ATA driver still can't attach to ISA controllers In-Reply-To: from Brian Feldman at "May 15, 1999 8:38:33 am" To: green@unixhelp.org (Brian Feldman) Date: Sat, 15 May 1999 16:06:25 +0200 (CEST) Cc: atrens@nortelnetworks.com, rwhitesel@nbase-xyplex.com, 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 Brian Feldman wrote: > On Sat, 15 May 1999, Andrew Atrens wrote: > > > > > On Fri, 14 May 1999, Rick Whitesel wrote: > > > > > I just wanted to say that I really appreciate the work you have/are > > > doing. The disk drive performance under IDE is very important for the > > > practical use of FreeBSD. > > > > > > Thank you! > > > > > > I second that - thank you ! > > Heck, I'll third that! Now my wish list includes spelling correction (settting? heh, I have the > patch at home), a d_dump_t, and possibly getting afd working, but that's not very much. This > driver's already wonderful, without some of the last things I want, and is so FAST! Well, thanks for all the flowers, positive feedback like that is what makes this project rolling you know... I've finally got my hands on a LS120 drive yesterday (boy those are rare here) but I havn't had time to hook it up yet though, so there is hope :) And I'll even promise you a dump routine, just not how soon I'll be able to do it, time is sparse currently... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 7:12:44 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 CB41514DEC for ; Sat, 15 May 1999 07:12:41 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id QAA20769; Sat, 15 May 1999 16:12:23 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905151412.QAA20769@freebsd.dk> Subject: Re: Alladdin IDE slow? In-Reply-To: from Kenneth Wayne Culver at "May 15, 1999 9:51: 6 am" To: culverk@wam.umd.edu (Kenneth Wayne Culver) Date: Sat, 15 May 1999 16:12:22 +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 Kenneth Wayne Culver wrote: > > > > Hmm, this sounds stange, I have a noard here with the Alladin on it on > > which I did the support for the ata driver, it works just fine for me > > at least... > > > Actually, I am having the same sort of problem.. With all the flags set > properly in the wd driver, I get about 11MBps, with ata, I can only get > about 6. Hmm, I get: test# dd if=/dev/rad2 of=/dev/null bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 7.936770 secs (13211621 bytes/sec) On this: chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 chip1: at device 3.0 on pci0 isab0: at device 7.0 on pci0 vga-pci0: irq 10 at device 10.0 on pci0 ata-pci0: irq 0 at device 15.0 on pci0 ta-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ata0: master: settting up WDMA2 mode on Aladdin chip OK ad0: ATA-? disk at ata0 as master ad0: 3681MB (7539840 sectors), 7480 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=-1 ad0: 16 secs/int, 0 depth queue, DMA mode ata1: master: settting up UDMA2 mode on Aladdin chip OK ad2: ATA-4 disk at ata1 as master ad2: 9641MB (19746720 sectors), 19590 cyls, 16 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ad2: 16 secs/int, 31 depth queue, DMA mode -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 7:49:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 93F8F14FF1; Sat, 15 May 1999 07:49:32 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id QAA29347; Sat, 15 May 1999 16:05:26 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id LAA56827; Sat, 15 May 1999 11:26:31 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905150926.LAA56827@yedi.iaf.nl> Subject: Re: de driver problem In-Reply-To: from Doug Rabson at "May 11, 1999 8:10: 4 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Sat, 15 May 1999 11:26:31 +0200 (CEST) Cc: khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Doug Rabson wrote ... > On Mon, 10 May 1999, Wilko Bulte wrote: > > > > > > > Yeah. That must be why my 164lx won't netboot. > > > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit > > only) worked just dandy. > > That reminds me. Does your Alpine still work after the new-bus stuff? I > wasn't sure I hadn't broken it when I changed the apecs driver. After a buildworld of yesterday's -current and a new kernel things work just fine. As an added bonus the serial console seems to work better. It used to be very slow, looks like that is gone. If you want more info you'll have to wait a bit, I'll be offline for a week. Wilko | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 7:50: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id 6792215238 for ; Sat, 15 May 1999 07:49:57 -0700 (PDT) (envelope-from soda@sra.co.jp) Received: from srasvf.sra.co.jp (srasvf [133.137.28.2]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id XAA20345; Sat, 15 May 1999 23:49:52 +0900 (JST) Received: from srapc342.sra.co.jp (srapc342 [133.137.28.111]) by srasvf.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id XAA00663; Sat, 15 May 1999 23:49:37 +0900 (JST) Received: (from soda@localhost) by srapc342.sra.co.jp (8.8.8/3.4W-sra) id XAA25692; Sat, 15 May 1999 23:49:46 +0900 (JST) Date: Sat, 15 May 1999 23:49:46 +0900 (JST) Message-Id: <199905151449.XAA25692@srapc342.sra.co.jp> From: Noriyuki Soda To: Doug Rabson Cc: Noriyuki Soda , current@freebsd.org Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: References: <199905120926.SAA19601@srapc342.sra.co.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Thu, 13 May 1999 10:41:23 +0100 (BST), Doug Rabson said: > As I suspected, a massive flamewar has happened while I've been away. I > don't think I have anything to add to what has been said (and I certainly > don't want to continue a flamewar). > Can people please just drop the subject until after Usenix. This kind of > flamewar is too upsetting (to me anyway) and just makes it harder to have > a useful face-to-face discussion. As I said earlier, I agree with you. About human factor, I think face to face communication is best way to solve problem. But about technical issues, I'd like to reply in public place, because both the message from Julian (*1) and the message from Daniel (*2) showed typical misunderstanding about newconfig. The goal they showed is also the goal of the dynamic configuration of newconfig from the beggining. I'd like to show how it will be achieved by newconifg. Could you permit me to answer technical issues in -hackers as Daniel adviced ? Or, -current is better about the questions which is posted to -current ? Other possibility is newconfig mailig list (anyone can subscribe it and it's archive can be accessed from WWW), or postponement until after Usenix. How do you think? (*1) Date: Wed, 12 May 1999 17:08:10 -0700 (PDT) From: Julian Elischer Subject: Re: cvs commit: src/sys/pci pcisupport.c Message-ID: (*2) From: "Daniel C. Sobral" Subject: Re: cvs commit: src/sys/pci pcisupport.c Date: Fri, 14 May 1999 20:46:05 +0900 Message-ID: <373C0CFD.7D9D3775@newsguy.com> -- soda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 7:55:27 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 AF10815051; Sat, 15 May 1999 07:55:00 -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 PAA41604; Sat, 15 May 1999 15:55:22 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 15 May 1999 15:55:22 +0100 (BST) From: Doug Rabson To: Wilko Bulte Cc: khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: de driver problem In-Reply-To: <199905150926.LAA56827@yedi.iaf.nl> 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, 15 May 1999, Wilko Bulte wrote: > As Doug Rabson wrote ... > > On Mon, 10 May 1999, Wilko Bulte wrote: > > > > > > > > > > Yeah. That must be why my 164lx won't netboot. > > > > > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit > > > only) worked just dandy. > > > > That reminds me. Does your Alpine still work after the new-bus stuff? I > > wasn't sure I hadn't broken it when I changed the apecs driver. > > After a buildworld of yesterday's -current and a new kernel things > work just fine. As an added bonus the serial console seems to work better. > It used to be very slow, looks like that is gone. > > If you want more info you'll have to wait a bit, I'll be offline for > a week. Thats good. The slow serial sounds like it used to be polling (i.e. sio interrupts weren't getting through). -- 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 May 15 7:58:11 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 5498014BEF for ; Sat, 15 May 1999 07:58:06 -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 PAA41608; Sat, 15 May 1999 15:58:01 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 15 May 1999 15:58:01 +0100 (BST) From: Doug Rabson To: Noriyuki Soda Cc: current@freebsd.org Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <199905151449.XAA25692@srapc342.sra.co.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 Sat, 15 May 1999, Noriyuki Soda wrote: > >>>>> On Thu, 13 May 1999 10:41:23 +0100 (BST), > Doug Rabson said: > > > As I suspected, a massive flamewar has happened while I've been away. I > > don't think I have anything to add to what has been said (and I certainly > > don't want to continue a flamewar). > > > Can people please just drop the subject until after Usenix. This kind of > > flamewar is too upsetting (to me anyway) and just makes it harder to have > > a useful face-to-face discussion. > > As I said earlier, I agree with you. > About human factor, I think face to face communication is best way to > solve problem. > > But about technical issues, I'd like to reply in public place, > because both the message from Julian (*1) and the message from > Daniel (*2) showed typical misunderstanding about newconfig. > The goal they showed is also the goal of the dynamic configuration of > newconfig from the beggining. I'd like to show how it will be achieved > by newconifg. > > Could you permit me to answer technical issues in -hackers as Daniel > adviced ? > Or, -current is better about the questions which is posted to -current ? > > Other possibility is newconfig mailig list (anyone can subscribe it > and it's archive can be accessed from WWW), or postponement until > after Usenix. I would like to postpone until after Usenix. I'm sure that we will be able to sort out any technical misunderstandings there which will make it possible to have a reasonable public discussion. -- 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 May 15 8:21:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id D3F9714F87 for ; Sat, 15 May 1999 08:21:14 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA02925; Sat, 15 May 1999 11:21:13 -0400 (EDT) (envelope-from luoqi) Date: Sat, 15 May 1999 11:21:13 -0400 (EDT) From: Luoqi Chen Message-Id: <199905151521.LAA02925@lor.watermarkgroup.com> To: freebsd-current@FreeBSD.ORG, gjvc@extremis.demon.co.uk Subject: Re: screen panics -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, this is just a quick note to anyone more knowledgable than me. > > screen 3.7.6 panics a current kernel. > > > -- > [gjvc] "We're not laughing at you; we're laughing with you." > "But I'm not laughing." > I committed a fix yesterday afternoon, could you cvsup and try again? -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 8:26:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id C201F14D99 for ; Sat, 15 May 1999 08:25:33 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 3804 invoked by uid 1008); 15 May 1999 15:25:30 -0000 Message-ID: <19990515152530.3802.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: freebsd-current@freebsd.org Subject: PR 10570 - patch Date: Sat, 15 May 1999 23:25:30 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I sent in a patch to PR 10570 a couple days ago, after quite a bit of testing (and catching up on email while changing countries..) So, if someone wants to commit the patch.. Thanks (and it took too long, i know..) adrian -- Adrian Chadd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 8:38: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id 69FA314C2A for ; Sat, 15 May 1999 08:38:04 -0700 (PDT) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id TAA03217; Sat, 15 May 1999 19:37:59 +0400 (MSD) (envelope-from mishania) Date: Sat, 15 May 1999 19:37:59 +0400 From: "Mikhail A. Sokolov" To: George Cox Cc: freebsd-current@freebsd.org Subject: Re: screen panics -current Message-ID: <19990515193759.A3086@demos.su> References: <19990515115540.B65473@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19990515115540.B65473@extremis.demon.co.uk>; from George Cox on Sat, May 15, 1999 at 11:55:42AM +0000 X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 15, 1999 at 11:55:42AM +0000, George Cox wrote: # Well, this is just a quick note to anyone more knowledgable than me. # # screen 3.7.6 panics a current kernel. to add a little bit: when the kernel has SMP enabled. at least here, checked 3 machines. -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 8:56:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (Postfix) with ESMTP id 4F9D6151AB for ; Sat, 15 May 1999 08:56:42 -0700 (PDT) (envelope-from soda@sra.co.jp) Received: from srasvf.sra.co.jp (srasvf [133.137.28.2]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id AAA21925; Sun, 16 May 1999 00:55:46 +0900 (JST) Received: from srapc342.sra.co.jp (srapc342 [133.137.28.111]) by srasvf.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id AAA00802; Sun, 16 May 1999 00:55:30 +0900 (JST) Received: (from soda@localhost) by srapc342.sra.co.jp (8.8.8/3.4W-sra) id AAA25988; Sun, 16 May 1999 00:55:40 +0900 (JST) Date: Sun, 16 May 1999 00:55:40 +0900 (JST) Message-Id: <199905151555.AAA25988@srapc342.sra.co.jp> From: Noriyuki Soda To: Doug Rabson , Julian Elischer , "Daniel C. Sobral" Cc: Noriyuki Soda , current@freebsd.org Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: References: <199905151449.XAA25692@srapc342.sra.co.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Sat, 15 May 1999 15:58:01 +0100 (BST), Doug Rabson said: > I would like to postpone until after Usenix. I'm sure that we will be able > to sort out any technical misunderstandings there which will make it > possible to have a reasonable public discussion. OK, I'll postpone, then. Julian, Daniel, and other folks, is this OK for you? If you'd like to hear the answer now, please request us that we should reply to your question. We'll reply to you in newconfig mailing list (i.e. "To: you, Cc: newconfig") to avoid useless flame war. Note that the newconfig mailing list is truly open, anyone who is interested in newconfig approach can access the answer. The address of mailing list: newconfig@jp.freebsd.org The official WWW page: http://www.jp.freebsd.org/newconfig/ The way to subscribe (majordomo): http://www.jp.freebsd.org/newconfig/ml.html The mail archive of newconfig: http://home.jp.freebsd.org/mail-list/newconfig/ The mail archive of newconfig-jp (written in Japanese): http://home.jp.freebsd.org/mail-list/newconfig-jp/index.html.ja.jis (The traffic of newconfig mailing list is not much, because main discussion is currently done in newconfig-jp.) And, Dainel, I'm very sorry that one of us called your serious question joke. I know your question is serious, because what you said is also the goal for me from the beginning of dynamic configuration of newconfig. Perhaps we should answer to you in newconfig mailing list ("To: you, cc: newconfig). Is this OK for you? We have answer which satisfy your requirement. -- soda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 10:22: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt051nc7.san.rr.com (dt051nc7.san.rr.com [204.210.32.199]) by hub.freebsd.org (Postfix) with ESMTP id A40DE14BE9; Sat, 15 May 1999 10:22:01 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051nc7.san.rr.com (8.8.8/8.8.8) with ESMTP id KAA12807; Sat, 15 May 1999 10:22:00 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <373DAD38.7C739B3D@gorean.org> Date: Sat, 15 May 1999 10:22:00 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-BETA-0511 i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: [Fwd: Re: Anybody actually using gigabit ethernet?] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser wrote: > Couldn't it read: > tcp_extensions="NO" # Switch RFC1323 extensions on? How about: tcp_extensions="NO" # Set to Yes to turn on RFC1323 extensions That would match existing style and be a lot more clear. I can submit a PR if anyone thinks that's really necessary... Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 11:40: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from uop.cs.uop.edu (user163.pop2.cwia.com [209.142.32.163]) by hub.freebsd.org (Postfix) with ESMTP id B12A814F5F for ; Sat, 15 May 1999 11:40:04 -0700 (PDT) (envelope-from bford@uop.cs.uop.edu) Received: (from bford@localhost) by uop.cs.uop.edu (8.9.3/8.9.3) id LAA00776 for freebsd-current@freebsd.org; Sat, 15 May 1999 11:40:02 -0700 (PDT) (envelope-from bford) From: "Bret A. Ford" Message-Id: <199905151840.LAA00776@uop.cs.uop.edu> Subject: Different SCSI probe behavior To: freebsd-current@freebsd.org Date: Sat, 15 May 1999 11:40:01 -0700 (PDT) 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 This morning, I did an installworld and booted a new -current world and -current kernel (Sources from morning of Fri May 14th). I got the following messages during the SCSI probe: Waiting 10 seconds for SCSI devices to settle aha0: ahafetchtransinfo - Inquire Setup Info Failed (probe20:aha0:0:5:0): CCB 0xc553b450 - timed out (probe20:aha0:0:5:0): CCB 0xc553b450 - timed out aha0: No longer in timeout I'm not sure what to make of this. After a bit of a delay - 30 or so seconds, I don't quite recall how long - the system continued booting, normally the rest of the way, and seems to be functional. Do I need to update something for normal behavior? I've been following freebsd-current and cvs-all, though I might have missed something that would have clued me in. Here are my controllers: ahc0: at slot 4 on eisa0 ahc0: aic7770 >= Rev E, Wide Channel A, SCSI Id=7, 4/255 SCBs aha0 at ports 0x130-0x133 and 0x131-0x134 irq 11 drq 7 on isa0 aha0: AHA-1542C FW Rev. 0.1 (ID=44) SCSI Host Adapter, SCSI ID 7, 16 CCBs Here is my disk information: da3 at ahc0 bus 0 target 4 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 1013MB (2074880 512 byte sectors: 64H 32S/T 1013C) da1 at ahc0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15) da1: 8347MB (17096357 512 byte sectors: 255H 63S/T 1064C) da4 at ahc0 bus 0 target 5 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 1013MB (2074880 512 byte sectors: 64H 32S/T 1013C) da5 at ahc0 bus 0 target 6 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da5: 1013MB (2074880 512 byte sectors: 64H 32S/T 1013C) cda0 at aha0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 3.333MB/s transfers (3.333MHz, offset 8) da0: 496MB (1015812 512 byte sectors: 64H 32S/T 496C) cd0 at aha0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [261564 x 2048 byte records] da2 at aha0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 3.300MB/s transfers da2: 1910MB (3912172 512 byte sectors: 64H 32S/T 1910C) hanging root device to da0s1a cd9660: Joliet Extension To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 12:29:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from pleb.cs.uct.ac.za (pleb.cs.uct.ac.za [137.158.132.206]) by hub.freebsd.org (Postfix) with ESMTP id 05DDA14C9E for ; Sat, 15 May 1999 12:29:10 -0700 (PDT) (envelope-from khetan@link.freebsd.os.org.za) X-Disclaimer: Contents of this e-mail are the writer's opinion X-Disclaimer2: and may not be quoted, re-produced or forwarded X-Disclaimer3: (in part or whole) without the author's permission. Received: from localhost (khetan@localhost) by pleb.cs.uct.ac.za (8.9.3+3.2W/8.9.3) with SMTP id VAA05235; Sat, 15 May 1999 21:28:48 +0200 (SAT) (envelope-from khetan@link.freebsd.os.org.za) Date: Sat, 15 May 1999 21:28:48 +0200 (SAT) From: Khetan Gajjar X-Sender: khetan@pleb.cs.uct.ac.za Reply-To: Khetan Gajjar To: "Bret A. Ford" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Different SCSI probe behavior In-Reply-To: <199905151840.LAA00776@uop.cs.uop.edu> Message-ID: X-Mobile: +27 82 9907663 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, 15 May 1999, Bret A. Ford wrote: >Waiting 10 seconds for SCSI devices to settle >aha0: ahafetchtransinfo - Inquire Setup Info Failed >(probe20:aha0:0:5:0): CCB 0xc553b450 - timed out >(probe20:aha0:0:5:0): CCB 0xc553b450 - timed out >aha0: No longer in timeout I'm seeing the same thing, but for 3 of my devices on a chain with 4 devices. It takes quite long, but doesn't appear to do any damage or decrease functionality (so far that is). >Do I need to update something for normal behavior? I've been following >freebsd-current and cvs-all, though I might have missed something >that would have clued me in. I've seen Werner Losch discovering a problem with the aha driver in -stable, and he committed a fix for that. Is it possible for that fix to be MFS ? --- Khetan Gajjar (!kg1779) * khetan@iafrica.com ; khetan@os.org.za http://www.os.org.za/~khetan * Talk/Finger khetan@chain.freebsd.os.org.za FreeBSD enthusiast * http://www2.za.freebsd.org/ Security-wise, NT is a OS with a "kick me" sign taped to it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 12:34:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 81DA414C9E for ; Sat, 15 May 1999 12:34:17 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id WAA16948; Sat, 15 May 1999 22:33:15 +0300 (EEST) Date: Sat, 15 May 1999 22:33:15 +0300 (EEST) From: Narvi To: Garance A Drosehn Cc: Ustimenko Semen , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: Nt source licenses... 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, 14 May 1999, Garance A Drosehn wrote: > At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote: > > Are we going to get this license? I am interested in NTFS > > source code a lot... > > I would be very careful about getting an NT source license if > your intention is to write NTFS support for some other operating > system. Microsoft is not doing this licensing for the benefit of > mankind, they are doing it to attract college-type users to > sticking with WinNT over open-source unixes. > > The last thing we need is some code from WinNT which causes us > to be sued by Microsoft... > It would probably be very unwise for the project to get get the licence. However, considering that we support loadable filesystem modules, somebody adventurous enough can get the licence and write a (separate distributed, possibly even only as binary) module. Downloading a kld module from the net definately does not "taint" your mind. > --- > Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu > Senior Systems Programmer (MIME & NeXTmail capable) > Rensselaer Polytechnic Institute; Troy NY USA > Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 12:44:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 26C6514A2D for ; Sat, 15 May 1999 12:44:26 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id VAA24916 for ; Sat, 15 May 1999 21:44:25 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma024914; Sat, 15 May 99 21:44:25 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id VAA01722 for ; Sat, 15 May 1999 21:44:24 +0200 (MET DST) Received: (qmail 58963 invoked by uid 666); 15 May 1999 19:44:45 -0000 Date: Sat, 15 May 1999 21:44:45 +0200 From: Jos Backus To: freebsd-current@FreeBSD.ORG Subject: ``65536-byte tape record bigger than suplied buffer'' Message-ID: <19990515214445.A58913@hal.mpn.cp.philips.com> Reply-To: Jos Backus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fyi, With today's -current, while trying to restore some files from a recent (about 3 days ago) dump, I'm seeing: /kernel: (sa0:ahc0:0:3:0): 65536-byte tape record bigger than suplied buffer Oh, and mounting swap /tmp mfs rw,nosuid,nodev,-s=32768 0 0 panics the system with a double fault in mount_mfs, but that's another matter. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 12:50:28 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 3FB1914A2D for ; Sat, 15 May 1999 12:50:27 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id MAA03426; Sat, 15 May 1999 12:50:10 -0700 Date: Sat, 15 May 1999 12:50:10 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jos Backus Cc: freebsd-current@FreeBSD.ORG Subject: Re: ``65536-byte tape record bigger than suplied buffer'' In-Reply-To: <19990515214445.A58913@hal.mpn.cp.philips.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 > Fyi, > > With today's -current, while trying to restore some files from a recent (about > 3 days ago) dump, I'm seeing: > > /kernel: (sa0:ahc0:0:3:0): 65536-byte tape record bigger than suplied buffer This is because a bug was fixed that actually now correctly reports the problem. You've made this tape with a 64KB record. You need to give an argument to recover that understands this. > > Oh, and mounting > > swap /tmp mfs rw,nosuid,nodev,-s=32768 0 0 > > panics the system with a double fault in mount_mfs, but that's another matter. > I'll say, and I haven't seen that one and I use mfs all the time! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 12:58:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 41C0F14A2D for ; Sat, 15 May 1999 12:58:40 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial4-114.netcologne.de [195.14.233.114]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id VAA23755; Sat, 15 May 1999 21:58:34 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id VAA14199; Sat, 15 May 1999 21:58:47 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Sat, 15 May 1999 21:58:47 +0200 (CEST) Message-Id: <199905151958.VAA14199@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: freebsd-current@freebsd.org Subject: No sound (Ensoniq Audio PCI 1370) Reply-To: van.woerkom@netcologne.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear people, I get no sound anymore using the system built on Friday. As I saw same earlier reports here about problems with sound that were reported to be fixed, mine might be related to the card being a PCI one - ES1370 based genuine Ensoniq Audio PCI. Below follow dmesg output and kernel configuration. Regards, Marc P.S. Should something like this go into a pr? ------------------------------------------------------------------------------- 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 #1: Fri May 14 22:01:21 CEST 1999 marc@oranje.my.domain:/usr/src/sys/compile/ORANJE Calibrating clock(s) ... TSC clock: 300727714 Hz, i8254 clock: 1193364 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 300684204 Hz CPU: AMD-K6tm w/ multimedia extensions (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping=0 Features=0x8001bf Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 192M bytes Write Allocate 15-16M bytes: Enable Hardware Write Allocate Control: Disable real memory = 201326592 (196608K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002da000 - 0x0bff5fff, 198295552 bytes (48412 pages) sio0: system console avail memory = 193077248 (188552K bytes) Found BIOS32 Service Directory header at 0xc00faf50 Entry = 0xfb410 (0xc00fb410) Rev = 0 Len = 1 PCI BIOS entry at 0xb440 DMI header at 0xc00f5bb0 Version 2.0 Table at 0xf0800, 28 entries, 613 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fbfb0 Preloaded elf kernel "kernel" at 0xc02c1000. VESA: information block 56 45 53 41 00 03 00 01 00 01 01 00 00 00 22 00 00 01 40 00 01 62 07 01 00 01 0e 01 00 01 21 01 00 01 00 01 01 01 02 01 03 01 04 01 05 01 06 01 07 01 08 01 09 01 0a 01 0b 01 0c 01 0e 01 0f 01 VESA: 48 mode(s) found Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 No Plug-n-Play devices were found pci_open(1): mode 1 addr port (0x0cf8) is 0x8000ff08 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=55971039) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 58186896 bytes/sec bzero() bandwidth = 58349865 bytes/sec pcib0: on motherboard found-> vendor=0x1039, dev=0x5597, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1039, dev=0x5513, revid=0xd0 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=0 map[0]: type 4, range 32, base 000001f0, size 3 map[1]: type 4, range 32, base 000003f4, size 2 map[2]: type 4, range 32, base 00000170, size 3 map[3]: type 4, range 32, base 00000374, size 2 map[4]: type 4, range 32, base 00004000, size 4 found-> vendor=0x1000, dev=0x0001, revid=0x02 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[0]: type 4, range 32, base 00006300, size 8 map[1]: type 1, range 32, base e2001000, size 8 found-> vendor=0x1274, dev=0x5000, revid=0x00 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 4, range 32, base 00006400, size 6 found-> vendor=0x12d2, dev=0x0018, revid=0x10 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 1, range 32, base e0000000, size 24 map[1]: type 3, range 32, base e1000000, size 24 pci0: on pcib0 i4b_pci_probe: unknown PCI type 1435963449l! chip0: at device 0.0 on pci0 isab0: at device 1.0 on pci0 i4b_pci_probe: unknown PCI type 1427312697l! chip1: irq 0 at device 1.1 on pci0 i4b_pci_probe: unknown PCI type 69632l! ncr0: irq 15 at device 13.0 on pci0 ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo ncr0: single-ended, open drain IRQ driver es0: irq 11 at device 15.0 on pci0 pcm0: using I/O space register mapping at 0x6400 i4b_pci_probe: unknown PCI type 1577682l! vga-pci0: irq 10 at device 17.0 on pci0 isa0: on motherboard atkbdc0: at port 0x60 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 vga0: on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc026e542 (1000022) VESA: NVidia VESA: NVidia VESA: Riva 128 Eval Card VESA: Rev B1 sc0: on isa0 sc0: fb0 kbd0 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: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A mss_probe: no address supplied, try default 0x530 mss_detect error, busy still set (0xff) sb_probe: no address supplied, try defaults (0x220,0x240) isic0 at port 0xd80 irq 5 flags 0x3 on isa0 isic0: Teles S0/16.3 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x960) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x160, AddrB=0x560) ppc: parallel port found at 0x378 ppc: chipset forced to generic ppc0: SPP ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE/NIBBLE_ID/Extensibility Link Probing for PnP devices on ppbus0: ppbus0: PRINTER HP ENHANCED PCL5,PJL lpt0: on ppbus 0 lpt0: Interrupt-driven port BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. bpf: ppp0 attached new masks: bio c0080040, tty c0030892, net c00708b2 bpf: lo0 attached i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached bpf: isp0 attached bpf: isp1 attached bpf: isp2 attached bpf: isp3 attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) bpf: ipr0 attached bpf: ipr1 attached bpf: ipr2 attached bpf: ipr3 attached i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached Waiting 8 seconds for SCSI devices to settle ncr0: restart (scsi reset). (probe3:ncr0:0:3:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe3:ncr0:0:3:0): ILLEGAL REQUEST asc:24,0 (probe3:ncr0:0:3:0): Invalid field in CDB pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number 152716411644 pass0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled pass1 at ncr0 bus 0 target 1 lun 0 pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number F3645620 pass1: 10.000MB/s transfers (10.000MHz, offset 8) pass2 at ncr0 bus 0 target 2 lun 0 pass2: Fixed Direct Access SCSI-2 device pass2: Serial Number 5U5R1502 pass2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled pass3 at ncr0 bus 0 target 3 lun 0 pass3: Removable CD-ROM SCSI-2 device pass3: 10.000MB/s transfers (10.000MHz, offset 8) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number 152716411644 da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 2068MB (4235629 512 byte sectors: 255H 63S/T 263C) Considering MFS root f/s. No MFS image available as root f/s. (cd0:ncr0:0:3:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ncr0:0:3:0): NOT READY asc:3a,0 (cd0:ncr0:0:3:0): Medium not present cd0 at ncr0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present Considering FFS root f/s. changing root device to da0s2a da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number F3645620 da1: 10.000MB/s transfers (10.000MHz, offset 8) da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: Serial Number 5U5R1502 da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0s1: type 0x6, start 63, end = 424115, size 424053 : OK da0s2: type 0xa5, start 424116, end = 4232843, size 3808728 : OK start_init: trying /sbin/init da1s1: type 0x6, start 63, end = 2120579, size 2120517 : OK da1s2: type 0x5, start 2120580, end = 2968811, size 848232 : OK da1s3: type 0xa5, start 2968812, end = 8465687, size 5496876 : OK da1s5: type 0x6, start 2120643, end = 2968811, size 848169 : OK da1s2: raw partition size != slice size da1s2: start 2120580, end 2968811, size 848232 da1s2c: start 2120580, end 8465687, size 6345108 da1s2: truncating raw partition da1s2: rejecting partition in BSD label: it isn't entirely within the slice da1s2: start 2120580, end 2968811, size 848232 da1s2e: start 2775940, end 8465687, size 5689748 da2s1: type 0xa5, start 0, end = 3261194, size 3261195 : OK da2s1: type 0xa5, start 0, end = 3261194, size 3261195 : OK splash: image decoder found: daemon_saver (da0:ncr0:0:0:0): tagged openings now 8 i4b: unit 0, assigned TEI = 119 = 0x77 Linux-ELF exec handler installed no pcm units configured\^Hi4b-L1-timer4_expired: state = F3 Deactivated no pcm units configured\^Hi4b-L1-timer4_expired: state = F3 Deactivated ------------------------------------------------------------------------------- # # ORANJE - Heike & Marc # # # upgraded to 4.0-CURRENT, Apr 7th, 1999 # upgraded to 4.0-CURRENT, May 14th, 1999 # machine i386 ident ORANJE maxusers 10 # # Certain applications can grow to be larger than the 128M limit # that FreeBSD initially imposes. Below are some options to # allow that limit to grow to 256MB, and can be increased further # with changing the parameters. MAXDSIZ is the maximum that the # limit can be set to, and the DFLDSIZ is the default value for # the limit. You might want to set the default lower than the # max, and explicitly set the maximum with a shell command for processes # that regularly exceed the limit like INND. # options MAXDSIZ="(256*1024*1024)" options DFLDSIZ="(256*1024*1024)" # When this is set, be extra conservative in various parts of the kernel # and choose functionality over speed (on the widest variety of systems). options FAILSAFE # Options for the VM subsystem #options PQ_NOOPT # No coloring options PQ_LARGECACHE # color for 512k/16k cache #options PQ_HUGECACHE # color for 1024k/16k cache #cpu I386_CPU #cpu I486_CPU cpu I586_CPU cpu I686_CPU options CPU_WT_ALLOC # for AMD K5/K6/K6-2 options NO_MEMORY_HOLE # for AMD K6 options NO_F00F_HACK #options MATH_EMULATE #Support for x87 emulation options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] #options LKM #options USER_LDT # WINE needs this # # These three options provide support for System V Interface # Definition-style interprocess communication, in the form of shared # memory, semaphores, and message queues, respectively. # options SYSVSHM options SYSVSEM options SYSVMSG # # This option includes a MD5 routine in the kernel, this is used for # various authentication and privacy uses. # options MD5 # # Allow processes to switch to vm86 mode, as well as enabling direct # user-mode access to the I/O port space. This option is necessary for # the doscmd emulator to run. # options VM86 # # Enable the kernel debugger. # #options DDB # # Don't drop into DDB for a panic. Intended for unattended operation # where you may want to drop to DDB from the console, but still want # the machine to recover from a panic # #options DDB_UNATTENDED # # If using GDB remote mode to debug the kernel, there's a non-standard # extension to the remote protocol that can be used to use the serial # port as both the debugging port and the system console. It's non- # standard and you're on your own if you enable it. See also the # "remotechat" variables in the FreeBSD specific version of gdb. # #options GDB_REMOTE_CHAT # # KTRACE enables the system-call tracing facility ktrace(2). # #options KTRACE #kernel tracing # # The INVARIANTS option is used in a number of source files to enable # extra sanity checking of internal structures. This support is not # enabled by default because of the extra time it would take to check # for these conditions, which can only occur as a result of # programming errors. # options INVARIANTS # # The INVARIANT_SUPPORT option makes us compile in support for # verifying some of the internal structures. It is a prerequisite for # 'INVARIANTS', as enabling 'INVARIANTS' will make these functions be # called. The intent is that you can set 'INVARIANTS' for single # source files (by changing the source file or specifying it on the # command line) if you have 'INVARIANT_SUPPORT' enabled. # options INVARIANT_SUPPORT # # The DIAGNOSTIC option is used in a number of source files to enable # extra sanity checking of internal structures. This support is not # enabled by default because of the extra time it would take to check # for these conditions, which can only occur as a result of # programming errors. # #options DIAGNOSTIC # # PERFMON causes the driver for Pentium/Pentium Pro performance counters # to be compiled. See perfmon(4) for more information. # #options PERFMON # XXX - this doesn't belong here. # Allow ordinary users to take the console - this is useful for X. options UCONSOLE # XXX - this doesn't belong here either options USERCONFIG #boot -c editor #options INTRO_USERCONFIG #imply -c and show intro screen options VISUAL_USERCONFIG #visual boot -c editor options INET #InterNETworking # # Network interfaces: # The `loop' pseudo-device is MANDATORY when networking is enabled. # The `ether' pseudo-device provides generic code to handle # Ethernets; it is MANDATORY when a Ethernet device driver is # configured. # The 'fddi' pseudo-device provides generic code to support FDDI. # The `sppp' pseudo-device serves a similar role for certain types # of synchronous PPP links (like `cx', `ar'). # The `sl' pseudo-device implements the Serial Line IP (SLIP) service. # The `ppp' pseudo-device implements the Point-to-Point Protocol. # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. # The `disc' pseudo-device implements a minimal network interface, # which throws away all packets sent and never receives any. It is # included for testing purposes. # The `tun' pseudo-device implements the User Process PPP (iijppp) # # The PPP_BSDCOMP option enables support for compress(1) style entire # packet compression, the PPP_DEFLATE is for zlib/gzip style compression. # PPP_FILTER enables code for filtering the ppp data stream and selecting # events for resetting the demand dial activity timer - requires bpfilter. # See pppd(8) for more details. #pseudo-device ether #Generic Ethernet #pseudo-device fddi #Generic FDDI pseudo-device sppp #Generic Synchronous PPP pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter #pseudo-device disc #Discard device #pseudo-device tun 1 #Tunnel driver (user process ppp(8)) #pseudo-device sl 1 #Serial Line IP pseudo-device ppp 1 #Point-to-point protocol options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed #options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem # SCSI DEVICE CONFIGURATION controller scbus0 #base SCSI code #device ch0 #SCSI media changers device da0 #SCSI direct access devices (aka disks) device sa0 #SCSI tapes device cd0 #Only need one of these, the code dynamically grows #device od0 #SCSI optical disk device pass0 #CAM passthrough driver # The previous devices (ch, da, st, cd) are recognized by config. # config doesn't (and shouldn't) know about these newer ones, # so we have to specify that they are on a SCSI bus with the "at scbus?" # clause. #device pt0 at scbus? # SCSI processor type #device sctarg0 at scbus? # SCSI target # CAM OPTIONS: # debugging options: # -- NOTE -- If you specify one of the bus/target/lun options, you must # specify them all! # CAMDEBUG: When defined enables debugging macros # CAM_DEBUG_BUS: Debug the given bus. Use -1 to debug all busses. # CAM_DEBUG_TARGET: Debug the given target. Use -1 to debug all targets. # CAM_DEBUG_LUN: Debug the given lun. Use -1 to debug all luns. # CAM_DEBUG_FLAGS: OR together CAM_DEBUG_INFO, CAM_DEBUG_TRACE, # CAM_DEBUG_SUBTRACE, and CAM_DEBUG_CDB # # CAM_MAX_HIGHPOWER: Maximum number of concurrent high power (start unit) cmds # SCSI_NO_SENSE_STRINGS: When defined disables sense descriptions # SCSI_NO_OP_STRINGS: When defined disables opcode descriptions # SCSI_REPORT_GEOMETRY: Always report disk geometry at boot up instead # of only when booting verbosely. # SCSI_DELAY: The number of MILLISECONDS to freeze the SIM (scsi adapter) # queue after a bus reset, and the number of milliseconds to # freeze the device queue after a bus device reset. #options CAMDEBUG #options CAM_DEBUG_BUS=-1 #options CAM_DEBUG_TARGET=-1 #options CAM_DEBUG_LUN=-1 #options CAM_DEBUG_FLAGS="CAM_DEBUG_INFO|CAM_DEBUG_TRACE|CAM_DEBUG_CDB" #options CAM_MAX_HIGHPOWER=4 #options SCSI_NO_SENSE_STRINGS #options SCSI_NO_OP_STRINGS options SCSI_REPORT_GEOMETRY options SCSI_DELAY=8000 #Be pessimistic about Joe SCSI device # Options for the CAM CDROM driver: # CHANGER_MIN_BUSY_SECONDS: Guaranteed minimum time quantum for a changer LUN # CHANGER_MAX_BUSY_SECONDS: Maximum time quantum per changer LUN, only # enforced if there is I/O waiting for another LUN # The compiled in defaults for these variables are 2 and 10 seconds, # respectively. # # These can also be changed on the fly with the following sysctl variables: # kern.cam.cd.changer.min_busy_seconds # kern.cam.cd.changer.max_busy_seconds # #options CHANGER_MIN_BUSY_SECONDS=2 #options CHANGER_MAX_BUSY_SECONDS=10 # Options for the CAM sequential access driver: # SA_SPACE_TIMEOUT: Timeout for space operations, in minutes # SA_REWIND_TIMEOUT: Timeout for rewind operations, in minutes # SA_ERASE_TIMEOUT: Timeout for erase operations, in minutes #options "SA_SPACE_TIMEOUT=(60)" #options "SA_REWIND_TIMEOUT=(2*60)" #options "SA_ERASE_TIMEOUT=(4*60)" # Size of the kernel message buffer. Should be N * pagesize. options MSGBUF_SIZE=40960 # ISA and EISA devices: # # Mandatory ISA devices: isa, npx # controller isa0 controller pnp0 # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD # The AT keyboard device atkbd0 at atkbdc? irq 1 # PS/2 mouse #device psm0 at atkbdc? irq 12 # The video card driver. device vga0 at isa? port ? conflicts # To include support for VESA video modes options VESA # needs VM86 defined too!! # Splash screen at start up! Screen savers require this too. pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? #options MAXCONS=16 # number of virtual consoles #options SLOW_VGA # do byte-wide i/o's to TS and GDC regs #options STD8X16FONT # Compile font in #makeoptions STD8X16FONT=cp850 options SC_HISTORY_SIZE=200 # number of history buffer lines #options SC_DISABLE_REBOOT # disable reboot key sequence # # `flags' for sc0: # 0x01 Use a 'visual' bell # 0x02 Use a 'blink' cursor # 0x04 Use a 'underline' cursor # 0x06 Use a 'blinking underline' (destructive) cursor # 0x40 Make the bell quiet if it is rung in the backgroud vty. # # The Numeric Processing eXtension driver. This should be configured if # your machine has a math co-processor, unless the coprocessor is very # buggy. If it is not configured then you *must* configure math emulation # (see above). If both npx0 and emulation are configured, then only npx0 # is used (provided it works). device npx0 at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 # # `flags' for npx0: # 0x01 don't use the npx registers to optimize bcopy # 0x02 don't use the npx registers to optimize bzero # 0x04 don't use the npx registers to optimize copyin or copyout. # The npx registers are normally used to optimize copying and zeroing when # all of the following conditions are satisfied: # I586_CPU is an option # the cpu is an i586 (perhaps not a Pentium) # the probe for npx0 succeeds # INT 16 exception handling works. # Then copying and zeroing using the npx registers is normally 30-100% faster. # The flags can be used to control cases where it doesn't work or is slower. # Setting them at boot time using userconfig works right (the optimizations # are not used until later in the bootstrap when npx0 is attached). # # # `iosiz' for npx0: # This can be used instead of the MAXMEM option to set the memory size. If # it is nonzero, then it overrides both the MAXMEM option and the memory # size reported by the BIOS. Setting it at boot time using userconfig takes # effect on the next reboot after the change has been recorded in the kernel # binary (the size is used early in the boot before userconfig has a chance # to change it). # # # Standard floppy disk controllers and floppy tapes: `fdc', `fd', and `ft' # controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 options EXTRA_SIO=1 #number of extra sio ports to allocate # Luigi's snd code (use INSTEAD of snd0 and all VOXWARE drivers!). # You may also wish to enable the pnp controller with this, for pnp # sound cards. # device pcm0 at isa? port ? irq 10 drq 1 flags 0x0 # # PCI devices & PCI options: # # The main PCI bus device is `pci'. It provides auto-detection and # configuration support for all devices on the PCI bus, using either # configuration mode defined in the PCI specification. # # The `ncr' device provides support for the NCR 53C810 and 53C825 # self-contained SCSI host adapters. # controller pci0 controller ncr0 # ISDN4BSD section # # i4b passive ISDN cards support (isic - I4b Siemens Isdn Chipset driver) # note that the ``options'' and ``device'' lines must BOTH be defined ! # # Non-PnP Cards: # -------------- # # Teles S0/16.3 options TEL_S0_16_3 device isic0 at isa? port 0xd80 irq 5 flags 3 # ISDN Protocol Stack # ------------------- # # Q.921 / layer 2 - i4b passive cards D channel handling pseudo-device "i4bq921" # # Q.931 / layer 3 - i4b passive cards D channel handling pseudo-device "i4bq931" # # layer 4 - i4b common passive and active card handling pseudo-device "i4b" # # ISDN devices # ------------ # # userland driver to do ISDN tracing (for passive cards only) pseudo-device "i4btrc" 4 # # userland driver to control the whole thing pseudo-device "i4bctl" # # userland driver for access to raw B channel pseudo-device "i4brbch" 4 # # userland driver for telephony pseudo-device "i4btel" 2 # # network driver for IP over raw HDLC ISDN pseudo-device "i4bipr" 4 # enable VJ header compression detection for ipr i/f options IPR_VJ # # network driver for sync PPP over ISDN pseudo-device "i4bisppp" 4 # Parallel-Port Bus # # Parallel port bus support is provided by the `ppbus' device. # Multiple devices may be attached to the parallel port, devices # are automatically probed and attached when found. # # lpt Parallel Printer # plip Parallel network interface # ppi General-purpose I/O ("Geek Port") + IEEE1284 I/O # pps Pulse per second Timing Interface # lpbb Philips official parallel port I2C bit-banging interface # # Supported interfaces: # ppc ISA-bus parallel port interfaces. # # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 device lpt0 at ppbus? #device plip0 at ppbus? #device ppi0 at ppbus? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 13: 9:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 1B2B41540A for ; Sat, 15 May 1999 13:09:42 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id WAA26581 for ; Sat, 15 May 1999 22:09:41 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma026579; Sat, 15 May 99 22:09:41 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id WAA03333 for ; Sat, 15 May 1999 22:09:41 +0200 (MET DST) Received: (qmail 59158 invoked by uid 666); 15 May 1999 20:10:01 -0000 Date: Sat, 15 May 1999 22:10:01 +0200 From: Jos Backus To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: ``65536-byte tape record bigger than suplied buffer'' Message-ID: <19990515221001.A59122@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990515214445.A58913@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Matthew Jacob on Sat, May 15, 1999 at 12:50:10PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 15, 1999 at 12:50:10PM -0700, Matthew Jacob wrote: > You've made this tape with a 64KB record. You need to give an argument to > recover that understands this. Ahh ``-b 64'', I recall the discussion with Wilko Bulte a few days ago now. Sorry for the false alert :-/ > > panics the system with a double fault in mount_mfs, but that's another > > matter. > > I'll say, and I haven't seen that one and I use mfs all the time! Strange. It's quite repeatable with a make world and kernel of 3 hours ago. I've commented out the fstab entry for now. Maybe I should get a ddb trace... Thanks, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 13:13:41 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 CBDFF14C2E for ; Sat, 15 May 1999 13:13:39 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA03482; Sat, 15 May 1999 13:13:28 -0700 Date: Sat, 15 May 1999 13:13:27 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jos Backus Cc: freebsd-current@FreeBSD.ORG Subject: Re: ``65536-byte tape record bigger than suplied buffer'' In-Reply-To: <19990515221001.A59122@hal.mpn.cp.philips.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 Sat, May 15, 1999 at 12:50:10PM -0700, Matthew Jacob wrote: > > You've made this tape with a 64KB record. You need to give an argument to > > recover that understands this. > > Ahh ``-b 64'', I recall the discussion with Wilko Bulte a few days ago now. > Sorry for the false alert :-/ Let me know how it goes... > > > > panics the system with a double fault in mount_mfs, but that's another > > > matter. > > > > I'll say, and I haven't seen that one and I use mfs all the time! > > Strange. It's quite repeatable with a make world and kernel of 3 hours ago. > I've commented out the fstab entry for now. Maybe I should get a ddb trace... Well, I'll recheck mine... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 13:26:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 251CB14BD7 for ; Sat, 15 May 1999 13:26:28 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id WAA27647 for ; Sat, 15 May 1999 22:26:27 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma027645; Sat, 15 May 99 22:26:27 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id WAA04448 for ; Sat, 15 May 1999 22:26:27 +0200 (MET DST) Received: (qmail 59281 invoked by uid 666); 15 May 1999 20:26:47 -0000 Date: Sat, 15 May 1999 22:26:47 +0200 From: Jos Backus To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: ``65536-byte tape record bigger than suplied buffer'' Message-ID: <19990515222647.A59246@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990515221001.A59122@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Matthew Jacob on Sat, May 15, 1999 at 01:13:27PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 15, 1999 at 01:13:27PM -0700, Matthew Jacob wrote: > Let me know how it goes... Quite well, thank you :) jos:/home/jos# restore -ivb 64 Verify tape and initialize maps Dump date: Wed May 12 23:36:39 1999 Dumped from: the epoch Level 0 dump of / on jos.bugworks.com:/dev/da2s1a Label: none Extract directories from tape Initialize symbol table. restore > ls .: 2 ./ 6028 cdrom/ 384 home@ 16 root/ 2 ../ 34 compat@ 1018 kernel 6045 sbin/ 6124 .kde/ 3 dev/ 181 kernel.ok 4 stand/ 241 .profile 14 dist/ 1027 kernel.old 1022 sys@ 408 COPYRIGHT 6046 dos/ 6030 mnt/ 31 tmp/ 6029 bin/ 6019 etc/ 6047 modules/ 6016 usr/ 32 boot/ 6059 floppy/ 13 proc/ 6017 var/ restore > quit jos:/home/jos# > Well, I'll recheck mine... It'd be interesting to see if you (and others) can reproduce this too. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 13:32:20 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 88A6714BD7 for ; Sat, 15 May 1999 13:32:15 -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 PAA29938; Sat, 15 May 1999 15:56:05 -0500 (EST) Date: Sat, 15 May 1999 15:56:03 -0500 (EST) From: Alfred Perlstein To: "Mikhail A. Sokolov" Cc: George Cox , freebsd-current@FreeBSD.ORG Subject: Re: screen panics -current In-Reply-To: <19990515193759.A3086@demos.su> 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, 15 May 1999, Mikhail A. Sokolov wrote: > On Sat, May 15, 1999 at 11:55:42AM +0000, George Cox wrote: > # Well, this is just a quick note to anyone more knowledgable than me. > # > # screen 3.7.6 panics a current kernel. > > to add a little bit: when the kernel has SMP enabled. at least here, > checked 3 machines. Louqi patched it yesterday evening, try re-cvsup. -Alfred thanks Louqi! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 13:37:31 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 6734414BD7 for ; Sat, 15 May 1999 13:37:28 -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 PAA04698; Sat, 15 May 1999 15:59:17 -0500 (EST) Date: Sat, 15 May 1999 15:59:16 -0500 (EST) From: Alfred Perlstein To: Narvi Cc: Garance A Drosehn , Ustimenko Semen , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: Nt source licenses... 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, 15 May 1999, Narvi wrote: > > On Fri, 14 May 1999, Garance A Drosehn wrote: > > > At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote: > > > Are we going to get this license? I am interested in NTFS > > > source code a lot... > > > > I would be very careful about getting an NT source license if > > your intention is to write NTFS support for some other operating > > system. Microsoft is not doing this licensing for the benefit of > > mankind, they are doing it to attract college-type users to > > sticking with WinNT over open-source unixes. > > > > The last thing we need is some code from WinNT which causes us > > to be sued by Microsoft... > > > > It would probably be very unwise for the project to get get the licence. > > However, considering that we support loadable filesystem modules, somebody > adventurous enough can get the licence and write a (separate distributed, > possibly even only as binary) module. > > Downloading a kld module from the net definately does not "taint" your > mind. I'm unsure what the fuss is over, don't we have a kld to read NTFS already? Is there really anything special about NT that we NEED to learn that hasn't been done _better_ by Sun, SGI or Digital? :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 15:47:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from pinhead.parag.codegen.com (unknown [205.134.241.196]) by hub.freebsd.org (Postfix) with ESMTP id 392DF14F28 for ; Sat, 15 May 1999 15:47:16 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id PAA26839; Sat, 15 May 1999 15:47:12 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) To: alk@pobox.com Cc: current@FreeBSD.ORG Subject: Re: stable snap for smp? In-Reply-To: Message from Anthony Kimball of "Fri, 14 May 1999 19:34:43 CDT." <14140.48742.126448.712700@avalon.east> X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Date: Sat, 15 May 1999 15:47:12 -0700 Message-ID: <26835.926808432@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 May 1999 19:34:43 CDT, Anthony Kimball wrote: > >If anyone has applied reasonable stress to a recent MP kernel, >preferrably with X, VESA, VM86, and found it stable, do please report >on your last cvs update time: I, for one, would very much like to >isolate a fairly stable post-newbus world. Presumably this would be >helpful to other readers as well, it being so much easier to bounce >between worlds which are more nearly contemporaneous. I've been running 3.1-STABLE cvsup-ed on Sat May 8 at about 3:30am or thereabouts. It always starts up xdm, and my desktop is KDE, I use exmh and Netscape daily, used doscmd a couple of days ago to burn some EPROMs, used gimp and sane to scan and edit some photos, just completed a buildworld with -j4 of 3.2-STABLE, and always run setiathome (new version 1.1 just released). The system is a dual PII/300, 256Mb RAM, and 256Mb swap across two UW-SCSI disks. The only IDE peripheral is a CD-ROM, and it's still using the old acd/ATAPI driver. Soundblaster AWE64 card works just fine with Luigi's drivers. The only thing I don't have in the kernel is VESA as the machine always fires up xdm. I have the DDB code in as well INVARIANTS turned on. Nothing is dynamically loaded - I always build a custom kernel with everything I need in it to ease debugging and to be sure no module is out-of-date. (I used to be running 4.0-CURRENT but hit the already-mentioned strange lockup with no debug, no dump, and no clue. I had to get some pay-for work done so I backed up to 3.1-STABLE and it seems to be fine since.) Hope this helps. I intend to update to 3.2-STABLE today... -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 16:41:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from eh.est.is (eh.est.is [194.144.208.34]) by hub.freebsd.org (Postfix) with ESMTP id 9B80414D3D; Sat, 15 May 1999 16:41:25 -0700 (PDT) (envelope-from totii@est.is) Received: from toti.est.is (toti.est.is [194.144.208.241]) by eh.est.is (8.8.8/8.8.8) with ESMTP id XAA06828; Sat, 15 May 1999 23:48:16 GMT (envelope-from totii@est.is) Received: from est.is (asus.est.is [194.144.208.242]) by toti.est.is (8.9.3/8.9.1) with ESMTP id XAA18949; Sat, 15 May 1999 23:41:17 GMT (envelope-from totii@est.is) Message-ID: <373DF782.4F0CAA91@est.is> Date: Sat, 15 May 1999 23:38:58 +0100 From: Thordur Ivarsson Reply-To: thivars@est.is X-Mailer: Mozilla 4.08 [en] (Win98; I) MIME-Version: 1.0 To: chris@calldei.com Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: make world croaks in perl ?? References: <9459.926593579@critter.freebsd.dk> <19990513091635.A18958@holly.dyndns.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make buildworld fails here with: ===>/gnu/usr.bin/perl/perl find: build: No such file or directory find: build: No such file or directory mkdir: lib/auto: File exists *** Error code 1 Stop. Thordur Ivarsson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 17:13:52 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 3A43F150F3 for ; Sat, 15 May 1999 17:13:50 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id RAA04068; Sat, 15 May 1999 17:08:25 -0700 (PDT) From: Archie Cobbs Message-Id: <199905160008.RAA04068@bubba.whistle.com> Subject: Re: Skip fail under current, was: Re: VPN betwwen Windows 9x Clients and FreeBSD Firewall In-Reply-To: <19502.926767996@critter.freebsd.dk> from Poul-Henning Kamp at "May 15, 99 01:33:16 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sat, 15 May 1999 17:08:24 -0700 (PDT) Cc: leifn@neland.dk, bob@dnsdata.com, freebsd-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 Poul-Henning Kamp writes: > >It won't compile under current. > >freebsd/skip_es.c breaks at > > > > if (suser(p->p_ucred, &p->p_acflag )) { > > > >This won't compile, because suser only has one parameter. > > > >Trying blindly to change it to: > > > > if (suser(p->p_ucred)) { > > Better yet, read the manpage for suser(9) and change it to: > > if (suser(p)) { Thanks for noticing this. I'll fix it as soon as the ports freeze is over. For the sake of 3.x systems, I'll change it to this.. #if __FreeBSD_version < 400005 if (suser(p->p_ucred, &p->p_acflag )) { #else if (suser(p)) { #endif return (EPERM); } Poul, thanks for bumping __FreeBSD_version when the suser() changes went through :-) -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 Sat May 15 17:32:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id 4163314D39 for ; Sat, 15 May 1999 17:32:18 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 17221 invoked from network); 16 May 1999 00:32:18 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 16 May 1999 00:32:18 -0000 Date: Sat, 15 May 1999 19:32:17 -0500 (CDT) From: John Sconiers To: Narvi Cc: Garance A Drosehn , Ustimenko Semen , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: Nt source licenses... 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 would probably be very unwise for the project to get get the licence. > > However, considering that we support loadable filesystem modules, somebody > adventurous enough can get the licence and write a (separate distributed, > possibly even only as binary) module. > > Downloading a kld module from the net definately does not "taint" your > mind. > How has linux come up with thier NTFS support?? JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 18:56:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (ykh28DS21.kng.mesh.ad.jp [133.205.214.21]) by hub.freebsd.org (Postfix) with ESMTP id 245B814C87 for ; Sat, 15 May 1999 18:56:10 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id PAA17319; Sat, 15 May 1999 15:43:14 GMT Message-Id: <199905151543.PAA17319@chandra.eatell.msr.prug.or.jp> To: "Daniel C. Sobral" Cc: Tomoaki NISHIYAMA , des@flood.ping.uio.no, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG, soda@sra.co.jp Subject: Re: cvs commit: src/sys/pci pcisupport.c In-reply-to: Your message of "Sat, 15 May 1999 16:53:31 JST." <373D27FB.D34161C6@newsguy.com> Date: Sun, 16 May 1999 00:43:13 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I replied to this in private, but, for the record, it was not a > joke. Ok, I see your say. I feel inadequate metaphor and provocation form, so that message seemed vulgar joke. New-bus's goal is meaningful, but not only that one. Also newconfig is same. Difference between these is realization way. But I don't reply that message, I must become to cool. Probably other member of newconfig will reply. I keep quiet in a while. #I'm busy recently, and shocked by suddenly new-bus merge #happening (I think, its process is not fair). I was lost my head. #Also, one of stress cause is language barrier. English is hard #for me. It is my weak point. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 20:35:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles538.castles.com [208.214.165.102]) by hub.freebsd.org (Postfix) with ESMTP id 8B6B314C87 for ; Sat, 15 May 1999 20:35:45 -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 UAA03441; Sat, 15 May 1999 20:18:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905160318.UAA03441@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kevin Day Cc: current@freebsd.org Subject: Re: -current page fault at 0xdeadc0de In-reply-to: Your message of "Wed, 12 May 1999 21:58:59 CDT." <199905130258.VAA11540@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 May 1999 20:18:33 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I had two systems reboot at nearly the same time. (30 seconds apart), and > are completely unrelated. These both look like stack damage, actually. > One system was running 2.2.8, and my core file presents me with this: > > su-2.02# gdb -k > GDB is free software and you are welcome to distribute copies of it > under certain conditions; type "show copying" to see the conditions. > There is absolutely no warranty for GDB; type "show warranty" for details. > GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, > Inc. > (kgdb) exec-file kernel.0 > (kgdb) symbol-file kernel.0.debug > Reading symbols from kernel.0.debug...done. > (kgdb) core-file vmcore.0 > IdlePTD 24a000 > current pcb at 202bfc > #0 0x14 in ?? () > (kgdb) bt > #0 0x14 in ?? () > #1 0x34000004 in ?? () > Cannot access memory at address 0x7205c76a. > > Were things just trashed, or am I doing something wrong? Looks like a return from a function that's destroyed the stack. > > The other system was running -current, and gives me: ... > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xdeadc0de > fault code = supervisor read, page not present > instruction pointer = 0x8:0xdeadc0de Jump through vector in freed memory; someone has freed a region of memory and is still using it, or has freed a region of memory that was never obtained by malloc. > panic: page fault > syncing disks... > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xdeadc126 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc018e3d8 Whoops. You need DDB to track this; you're only going to get the trace for the second fault with gdb, which won't be at all illuminating I don't think. ... > #0 boot (howto=260) at ../../kern/kern_shutdown.c:288 > 288 dumppcb.pcb_cr3 = rcr3(); > (kgdb) bt > #0 boot (howto=260) at ../../kern/kern_shutdown.c:288 > #1 0xc0145755 in panic () at ../../kern/kern_shutdown.c:450 > #2 0xc020e9e2 in trap_fatal (frame=0xcb4ad8dc, eva=3735929126) > at ../../i386/i386/trap.c:917 > #3 0xc020e695 in trap_pfault (frame=0xcb4ad8dc, usermode=0, eva=3735929126) > at ../../i386/i386/trap.c:810 > #4 0xc020e2d7 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = > 0, > tf_esi = 0, tf_ebp = -884287172, tf_isp = -884287224, tf_ebx = 16384, > tf_edx = -559038242, tf_ecx = -1059309536, tf_eax = -1053816960, > tf_trapno = 12, tf_err = 0, tf_eip = -1072110632, tf_cs = 8, > tf_eflags = 66182, tf_esp = -1062703744, tf_ss = -911937724}) > at ../../i386/i386/trap.c:436 > (kgdb) Nope, not useful at all really. Look at the first trap message to see where the first one occurred, that'll at least give you a locality. Just out of curiosity, are either of these systems running with NCR controllers? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 20:56:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id C771C14C96 for ; Sat, 15 May 1999 20:56:31 -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 VAA13745; Sat, 15 May 1999 21:54:01 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA18027; Sat, 15 May 1999 21:54:00 -0600 Date: Sat, 15 May 1999 21:54:00 -0600 Message-Id: <199905160354.VAA18027@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Kevin Day , current@FreeBSD.ORG Subject: Re: -current page fault at 0xdeadc0de In-Reply-To: <199905160318.UAA03441@dingo.cdrom.com> References: <199905130258.VAA11540@home.dragondata.com> <199905160318.UAA03441@dingo.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 > > One system was running 2.2.8, and my core file presents me with this: ... > Just out of curiosity, are either of these systems running with NCR > controllers? In case you're fishing, I'm running 4 NCR equipped boxes (510 and 575) with FreeBSD 2.2.8-stable right now and have seen *NO* problems whatsoever. I've only *once* had a SCSI error on my system, and that was due to a bug that was somewhere other than the NCR driver. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 15 23:47: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-b.bcc.ac.uk (mail-b.bcc.ac.uk [144.82.100.22]) by hub.freebsd.org (Postfix) with ESMTP id 304B814C9F for ; Sat, 15 May 1999 23:47:01 -0700 (PDT) (envelope-from dlombardo@excite.com) Received: from medphys.ucl.ac.uk (actually host bach.medphys.ucl.ac.uk) by mail-b.bcc.ac.uk with SMTP (XT-PP) with ESMTP; Sun, 16 May 1999 07:46:50 +0100 Received: from marley.medphys (marley [128.40.233.29]) by medphys.ucl.ac.uk (8.8.8/8.8.8) with SMTP id HAA25338 for ; Sun, 16 May 1999 07:46:49 +0100 (BST) Received: from excite.com by marley.medphys (SMI-8.6/SMI-SVR4) id HAA13377; Sun, 16 May 1999 07:46:54 +0100 Message-ID: <373E69F2.5BFADB76@excite.com> Date: Sun, 16 May 1999 07:47:14 +0100 From: Dean Lombardo Organization: University of Kent at Canterbury X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: Nt source licenses... References: <199905112056.WAA18582@labinfo.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosehn wrote: > > At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote: > > Are we going to get this license? I am interested in NTFS > > source code a lot... > > I would be very careful about getting an NT source license if > your intention is to write NTFS support for some other operating > system. Microsoft is not doing this licensing for the benefit of > mankind, they are doing it to attract college-type users to > sticking with WinNT over open-source unixes. > > The last thing we need is some code from WinNT which causes us > to be sued by Microsoft... They can't sue - unless, of course, the code is copied verbatim (and it's not very likely to be, anyway). Otherwise, it shouldn't be any more illegal than reverse engineering the code, and several federal appeals courts have held that it is "fair use" to reverse engineer a program in order to examine and copy its ideas and any unprotected expression. Dean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 0:38: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id A52FC15199; Sun, 16 May 1999 00:37:53 -0700 (PDT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id JAA75624; Sun, 16 May 1999 09:37:50 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id JAA65945; Sun, 16 May 1999 09:37:49 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199905160737.JAA65945@greenpeace.grondar.za> To: thivars@est.is Cc: chris@calldei.com, Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: make world croaks in perl ?? Date: Sun, 16 May 1999 09:37:48 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Make buildworld fails here with: > > ===>/gnu/usr.bin/perl/perl > find: build: No such file or directory > find: build: No such file or directory > mkdir: lib/auto: File exists > *** Error code 1 Please look this one up in the archives. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 0:40:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 1657515199 for ; Sun, 16 May 1999 00:40:39 -0700 (PDT) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id JAA75634; Sun, 16 May 1999 09:40:23 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id JAA65973; Sun, 16 May 1999 09:40:22 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199905160740.JAA65973@greenpeace.grondar.za> To: NAKAGAWA Yoshihisa Cc: "Daniel C. Sobral" , Tomoaki NISHIYAMA , des@flood.ping.uio.no, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG, soda@sra.co.jp Subject: Re: cvs commit: src/sys/pci pcisupport.c Date: Sun, 16 May 1999 09:40:22 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > #I'm busy recently, and shocked by suddenly new-bus merge > #happening (I think, its process is not fair). I was lost my head. > #Also, one of stress cause is language barrier. English is hard > #for me. It is my weak point. Not a problem; most of us do not speak Japanese. :-) I am looking forward to hearing about newconfig from you folk at USENIX! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 2:36: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 5DFEF1501B for ; Sun, 16 May 1999 02:36:06 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id MAA20009; Sun, 16 May 1999 12:36:03 +0300 (EEST) Date: Sun, 16 May 1999 12:36:03 +0300 (EEST) From: Narvi To: Dean Lombardo Cc: current@FreeBSD.ORG Subject: Re: Nt source licenses... In-Reply-To: <373E69F2.5BFADB76@excite.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, 16 May 1999, Dean Lombardo wrote: > Garance A Drosehn wrote: > > > > At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote: > > > Are we going to get this license? I am interested in NTFS > > > source code a lot... > > > > I would be very careful about getting an NT source license if > > your intention is to write NTFS support for some other operating > > system. Microsoft is not doing this licensing for the benefit of > > mankind, they are doing it to attract college-type users to > > sticking with WinNT over open-source unixes. > > > > The last thing we need is some code from WinNT which causes us > > to be sued by Microsoft... > > > They can't sue - unless, of course, the code is copied verbatim (and They most definately *CAN* sue. I don't think "can't sue" is something that applies to the US in any way. > it's not very likely to be, anyway). Otherwise, it shouldn't be any > more illegal than reverse engineering the code, and several federal > appeals courts have held that it is "fair use" to reverse engineer a > program in order to examine and copy its ideas and any unprotected > expression. > But do we have the money to prove that? And if we do, wouldn't it be spend on better things? > Dean > Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 2:39:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id DD82F1501B for ; Sun, 16 May 1999 02:39:16 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id MAA20023; Sun, 16 May 1999 12:38:09 +0300 (EEST) Date: Sun, 16 May 1999 12:38:09 +0300 (EEST) From: Narvi To: Alfred Perlstein Cc: Garance A Drosehn , Ustimenko Semen , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: Nt source licenses... 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, 15 May 1999, Alfred Perlstein wrote: > On Sat, 15 May 1999, Narvi wrote: > > > > > On Fri, 14 May 1999, Garance A Drosehn wrote: > > > > > At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote: > > > > Are we going to get this license? I am interested in NTFS > > > > source code a lot... > > > > > > I would be very careful about getting an NT source license if > > > your intention is to write NTFS support for some other operating > > > system. Microsoft is not doing this licensing for the benefit of > > > mankind, they are doing it to attract college-type users to > > > sticking with WinNT over open-source unixes. > > > > > > The last thing we need is some code from WinNT which causes us > > > to be sued by Microsoft... > > > > > > > It would probably be very unwise for the project to get get the licence. > > > > However, considering that we support loadable filesystem modules, somebody > > adventurous enough can get the licence and write a (separate distributed, > > possibly even only as binary) module. > > > > Downloading a kld module from the net definately does not "taint" your > > mind. > > I'm unsure what the fuss is over, don't we have a kld to read NTFS already? > How about writing? > Is there really anything special about NT that we NEED to learn that > hasn't been done _better_ by Sun, SGI or Digital? :) > No, not really. > -Alfred > Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 3:45:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 3041D15199 for ; Sun, 16 May 1999 03:45:15 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial2-36.netcologne.de [194.8.195.36]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id MAA12915; Sun, 16 May 1999 12:45:13 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id MAA00902; Sun, 16 May 1999 12:34:14 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Sun, 16 May 1999 12:34:14 +0200 (CEST) Message-Id: <199905161034.MAA00902@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: toasty@home.dragondata.com Cc: current@FreeBSD.ORG In-reply-to: <199905130258.VAA11540@home.dragondata.com> (message from Kevin Day on Wed, 12 May 1999 21:58:59 -0500 (CDT)) Subject: Re: -current page fault at 0xdeadc0de Reply-To: van.woerkom@netcologne.de References: <199905130258.VAA11540@home.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > fault virtual address = 0xdeadc0de 0xdeadc0de - dead code? :-) Is this address a coincidence or a special crafted one? Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 3:47:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id DF18A15199 for ; Sun, 16 May 1999 03:47:49 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id MAA22306; Sun, 16 May 1999 12:47:48 +0200 (CEST) (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 MAA00546; Sun, 16 May 1999 12:47:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: van.woerkom@netcologne.de Cc: toasty@home.dragondata.com, current@FreeBSD.ORG Subject: Re: -current page fault at 0xdeadc0de In-reply-to: Your message of "Sun, 16 May 1999 12:34:14 +0200." <199905161034.MAA00902@oranje.my.domain> Date: Sun, 16 May 1999 12:47:44 +0200 Message-ID: <544.926851664@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905161034.MAA00902@oranje.my.domain>, Marc van Woerkom writes: >> fault virtual address = 0xdeadc0de > >0xdeadc0de - dead code? :-) > >Is this address a coincidence or a special crafted one? This is by intention: cd /sys/kern grep -i deadc0de * kern_malloc.c:#define WEIRD_ADDR 0xdeadc0de -- 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 Sun May 16 5:48:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-b.bcc.ac.uk (mail-b.bcc.ac.uk [144.82.100.22]) by hub.freebsd.org (Postfix) with ESMTP id 6DC0C152F3 for ; Sun, 16 May 1999 05:48:46 -0700 (PDT) (envelope-from dlombardo@excite.com) Received: from medphys.ucl.ac.uk (actually host bach.medphys.ucl.ac.uk) by mail-b.bcc.ac.uk with SMTP (XT-PP) with ESMTP; Sun, 16 May 1999 13:48:44 +0100 Received: from marley.medphys (marley [128.40.233.29]) by medphys.ucl.ac.uk (8.8.8/8.8.8) with SMTP id NAA00253 for ; Sun, 16 May 1999 13:48:42 +0100 (BST) Received: from excite.com by marley.medphys (SMI-8.6/SMI-SVR4) id NAA13581; Sun, 16 May 1999 13:48:48 +0100 Message-ID: <373EBEC5.D8B1E0E0@excite.com> Date: Sun, 16 May 1999 13:49:09 +0100 From: Dean Lombardo Organization: University of Kent at Canterbury X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: Nt source licenses... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Narvi wrote: > > On Sun, 16 May 1999, Dean Lombardo wrote: > > > Garance A Drosehn wrote: > > > > > > At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote: > > > > Are we going to get this license? I am interested in NTFS > > > > source code a lot... > > > > > > I would be very careful about getting an NT source license if > > > your intention is to write NTFS support for some other operating > > > system. Microsoft is not doing this licensing for the benefit of > > > mankind, they are doing it to attract college-type users to > > > sticking with WinNT over open-source unixes. > > > > > > The last thing we need is some code from WinNT which causes us > > > to be sued by Microsoft... > > > > They can't sue - unless, of course, the code is copied verbatim (and > > They most definately *CAN* sue. I don't think "can't sue" is something > that applies to the US in any way. OK - perhaps I should rephrase it - they *can* sue, but they are not very likely to do so without good reason. Do you really think that someone at Microsoft is going to compare FreeBSD's (OpenBSD's / NetBSD's / Linux's / etc / etc) implementations of NTFS with their own, with the only intention of discovering that some parts were derived from their code? Even if they did, how would they prove it unless the code was indeed identical to theirs? It's an unwinnable war. > But do we have the money to prove that? And considering that we don't, it's even less likely. Dean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 6: 4:10 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 C3CC3152F3 for ; Sun, 16 May 1999 06:04:07 -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 PAA51963; Sun, 16 May 1999 15:04:02 +0200 (CEST) (envelope-from des) To: Narvi Cc: Garance A Drosehn , Ustimenko Semen , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: Nt source licenses... References: From: Dag-Erling Smorgrav Date: 16 May 1999 15:04:00 +0200 In-Reply-To: Narvi's message of "Sat, 15 May 1999 22:33:15 +0300 (EEST)" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Narvi writes: > Downloading a kld module from the net definately does not "taint" your > mind. I thought 'tainted from reading source' argument had been shot dead during the USL vs Berkely suit? 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 Sun May 16 8:28:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id A6BC114DD3 for ; Sun, 16 May 1999 08:28:45 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-13-77.camtech.net.au [203.55.243.205]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id BAA10844; Mon, 17 May 1999 01:03:22 +0930 (CST) Message-ID: <373EE45E.2D407D51@camtech.com.au> Date: Mon, 17 May 1999 00:59:34 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Brian Feldman , "Jordan K. Hubbard" , current@FreeBSD.ORG, David Dawes Subject: Fixed my MAMEd sio problem. Was: Re: Doesn't anyone care about the broken sio ?? References: <3734FC84.95F31E3B@camtech.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just so you all know (the list included) how I have fixed my silo overflow problem which occurred while running xmame (and after I quit until I restarted the X server).... I have found the problem doesn't occur if I remove the following lines from the shell script I use to start xmame: xsetpointer Joystick sleep 1 xsetpointer pointer I was doing those three lines just before starting xmame to get the mouse pointer into the top left hand corner (my script also used vidtune to get the right resolution for each game). Since I have removed those lines it works fine. I can now download to my hearts content whilst playing some ancient game. (I'd like to know an easy way to move the mouse pointer though!) With those lines in the script I had to restart the X-server after using xmame or I'd get continuous silo overflows. FYI, the output of "xsetpointer -l" is: "keyboard" [XKeyboard] "pointer" [XPointer] "SWITCH" [XExtensionDevice] "Joystick" [XExtensionDevice] And as you can see from the XF86Config file in the message I'm replying to, I am loading several modules to use XExtension Devices and the PC joystick (which is compiled into my kernel): Load "xie.so" Load "pex5.so" Load "xf86Jstk.so" Matthew Thyer wrote: > > *** STOP PRESS *** I have just confirmed that restarting the X server > is enough to fix the problem. So my apologies to Bruce, -CURRENT > and the whole FreeBSD community in general for blaming sio. > > For the benefit of David Dawes, I'll quickly restate the problem: > Running xmame (from the ports collection) causes lots of silo overflows > with user mode ppp until I either restart the X server or reboot. > This occurs even after I exit xmame. This is all on FreeBSD-CURRENT but > has been happenning for months and is not newbus related. > > Thankyou Brian, you are the first to NOT reproduce the problem. > > Note that all my recent testing of this has been at 300 MHz so dont jump > on me when you see that I normally overclock at 450 MHz. > > So compare configuration: > > My X server is XFree86 3.3.3.1 (from ports) and I use the XF86_SVGA server. > My video card is an ET6000 "Jaton VIDEO-58P" with 2.25 MB RAM. > I run in 16 bit colour with KDE 1.1.1. > I run MAME with sound enabled and I'm NOT using Luigi's PCM driver but > rather the old driver (whats it called ??). > I have a new ABIT BX6 release 2.0 motherboard (with 16550s I assume). > I have an Intel Celeron 300a CPU which I normally run at 450 MHz (using > a 100 MHz memory bus speed instead of 66 MHz but when I run it at 300 > MHz it doesn't make any difference to this problem). > I have PC100 SD RAM with an EPROM. This RAM is rated at 7ns believe it > or not. > I'd like to be using Soren's ATAPI driver but it doesn't like my CD-ROM > drive so I'm using the normal wd driver with flags a0ffa0ff. > I'm using a KTX V.90 modem at 115000 baud. > I typically get 45333, 46667 or 48000 connections to my ISP. > I'm using a Microsoft serial mouse but am not using moused. > I do have a PS/2 intellimouse compatible mouse attached but only use it > when I'm on the darkside (In Windows 95) as it doesn't work with moused > or in XFree86. > My whole system has been re-compiled within the last 2 days (world, updated > /etc, kernel AND ALL ports [XFree86 3.3.3.1, kde 1.1.1 etc etc etc]) > > Kernel config file (MATTE), /etc/XF86Config file and dmesg output attached. > > I have one question about my kernel config: > How do I know when it's unsafe to use "options CPU_DISABLE_5X86_LSSER" ? > It would be good if the kernel disabled this option under those cases. > > My /etc/ppp/ppp.conf is: > > default: > set log chat connect phase > set device /dev/cuaa1 > set speed 115200 > allow users matt > deny lqr > deny chap > set timeout 0 > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATX4S95=47 OK-AT-OK \\dATDT\\T TIMEOUT 80 CONNECT" > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > > isp: > set phone ISPNUMBER > set login "TIMEOUT 10 sername:--sername: MYUSER ssword: MYPASS" > dial > > Brian Feldman wrote: > > > > On Sat, 8 May 1999, Jordan K. Hubbard wrote: > > > > > > I mailed a simple way to reproduce the serious brokeness of the > > > > serial port driver on my system and no one responds. > > > > > > > > What does this mean ? > > > > > > It means that nobody is probably willing to go bring up a MAME > > > environment just to test this. You need to isolate it to a more > > > minimal test case if you want people to jump on what could be a local > > > problem (some serial hardware is better behaved than others) or a > > > misbehaving X server (which is masking interrupts for too long; see > > > mailing list archives on this topic). The more complex your > > > reproduction case, in other words, the less likely it is that anyone > > > will respond to it. > > > > Hmm, so now you're the second to cite the possibility of X masking interrupts > > too long, eh? ;) Actually, I use MAME all the time, and this problem does NOT > > occur (XF86_SVGA on an S3 ViRGE/DX). Oh, user-ppp too of course. If I could > > have reproduced this problem, I would have replied. > > > > > > > > If you can say "here's a small stand-alone C program which hogs things > > > to the extent that the serial driver seriously overruns its buffers" > > > then it's likely that someone will be at least motivated to compile, > > > run and try it. If it involves running some esoteric application > > > which requires downloading data of questionable legality on top of it, > > > it's far less likely that anyone will even bother to look. > > > > MAME is a great piece of software, and in and of itself entirely legal; what > > problem do you have with it? > > > > > > > > - Jordan > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > Brian Feldman _ __ ___ ____ ___ ___ ___ > > green@unixhelp.org _ __ ___ | _ ) __| \ > > FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | > > http://www.freebsd.org _ |___)___/___/ > > -- > /=======================================================================\ > | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | > \=======================================================================/ > "If it is true that our Universe has a zero net value for all conserved > quantities, then it may simply be a fluctuation of the vacuum of some > larger space in which our Universe is imbedded. In answer to the > question of why it happened, I offer the modest proposal that our > Universe is simply one of those things which happen from time to time." > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 > > ---------------------------------------------------------------------------- > # $Id: MATTE,v 11.8 1999/05/08 11:04:00 +09:30 matt Exp $ > # based on: $Id: LINT,v 1.594 1999/05/06 18:08:23 peter Exp $ > # > machine i386 > ident "MATTE" > maxusers 20 > options INCLUDE_CONFIG_FILE # Include this file in kernel > config kernel root on wd0 > cpu I686_CPU > options CPU_DISABLE_5X86_LSSER # Dont use if you use memory mapped I/O device(s). > options CPU_FASTER_5X86_FPU # Faster FPU exception handler > options NO_F00F_HACK # Disable Pentium F00F hack > # COMPATIBILITY OPTIONS > options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] > options USER_LDT # Let processes manipulate their local descriptor table (needed for WINE) > options SYSVSHM # Enable SYSV style shared memory > options SYSVSEM # Enable SYSV style semaphores > options SYSVMSG # Enable SYSV style message queues > options MD5 # Include a MD5 routine in the kernel > options VM86 # Allow processes to switch to vm86 mode (needed for doscmd) > # DEBUGGING OPTIONS > options DDB # Enable the kernel debugger > #options INVARIANTS # Extra sanity checking (slower) > #options INVARIANT_SUPPORT # Include sanity checking functions > options UCONSOLE # Allow users to grab the console > options USERCONFIG # Boot -c editor > options VISUAL_USERCONFIG # Visual boot -c editor > # NETWORKING OPTIONS > options INET # Internet communications protocols > # Network interfaces: > pseudo-device ether # Generic Ethernet > pseudo-device loop # Network loopback device > pseudo-device tun 1 # Tunnel driver(user process ppp) > pseudo-device streams # SysVR4 STREAMS emulation > # FILESYSTEM OPTIONS > options FFS # Berkeley Fast Filesystem > options FFS_ROOT # FFS usable as root device > options NFS # Network Filesystem > options CD9660 # ISO 9660 Filesystem > options MFS # Memory Filesystem > options MSDOSFS # MSDOS Filesystem > options PROCFS # Process Filesystem > options NSWAPDEV=4 # Allow this many swap-devices > options SOFTUPDATES # SoftUpdates aka delayed writes > controller pci0 > controller ncr0 > options P1003_1B > options _KPOSIX_PRIORITY_SCHEDULING > options _KPOSIX_VERSION=199309L > # SCSI DEVICE CONFIGURATION (CAM SCSI) > controller scbus0 at ncr0 # Base SCSI code > disk da0 at scbus0 target 0 > disk da1 at scbus0 target 1 > disk da2 at scbus0 target 2 > disk da3 at scbus0 target 3 > disk da4 at scbus0 target 4 > disk da5 at scbus0 target 5 > disk da6 at scbus0 target 6 > options SCSI_DELAY=500 # Only wait 0.5 seconds for SCSI > # MISCELLANEOUS DEVICES AND OPTIONS > pseudo-device pty 64 # Pseudo ttys - can go as high as 256 > pseudo-device gzip # Exec gzipped a.out's > pseudo-device vn 4 # Vnode driver (turns a file into a device) > options MSGBUF_SIZE=81920 # Size of the kernel message buffer > # HARDWARE DEVICE CONFIGURATION > controller isa0 > options AUTO_EOI_1 # Save 0.7-1.25 usec for each interrupt > controller pnp0 # Enable PnP support in the kernel > controller atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 > device vga0 at isa? port ? conflicts > pseudo-device splash # Splash screen at start up! > device sc0 at isa? > options MAXCONS=12 # Number of virtual consoles > options SC_HISTORY_SIZE=800 # Number of history buffer lines > options VESA # Needs VM86 defined too!! > 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 > device wcd0 > controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff > disk wd0 at wdc0 drive 0 > controller wdc1 at isa? port IO_WD2 irq 15 flags 0xa0ffa0ff > controller fdc0 at isa? port IO_FD1 irq 6 drq 2 > disk fd0 at fdc0 drive 0 > device psm0 at atkbdc? irq 12 > device ppc0 at isa? port? irq 7 > controller ppbus0 > device lpt0 at ppbus? > device plip0 at ppbus? > device ppi0 at ppbus? > device sio0 at isa? port IO_COM1 irq 4 flags 0x10 > device sio1 at isa? port IO_COM2 irq 3 > options CONSPEED=38400 # Speed for serial console (default 9600) > device ed0 at isa? port 0x300 irq 9 iomem 0xd8000 > device apm0 at nexus? > controller smbus0 > controller intpm0 > device smb0 at smbus? > device joy0 at isa? port IO_GAME > #device pcm0 at isa? port? irq 5 drq 1 flags 0x15 > controller snd0 > device sb0 at isa? port 0x220 irq 5 drq 1 > device sbxvi0 at isa? drq 5 > device sbmidi0 at isa? port 0x330 > device opl0 at isa? port 0x388 > > ---------------------------------------------------------------------------- > # File generated by xf86config. > > # > # Copyright (c) 1995 by The XFree86 Project, Inc. > # > # Permission is hereby granted, free of charge, to any person obtaining a > # copy of this software and associated documentation files (the "Software"), > # to deal in the Software without restriction, including without limitation > # the rights to use, copy, modify, merge, publish, distribute, sublicense, > # and/or sell copies of the Software, and to permit persons to whom the > # Software is furnished to do so, subject to the following conditions: > # > # The above copyright notice and this permission notice shall be included in > # all copies or substantial portions of the Software. > # > # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR > # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, > # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL > # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, > # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF > # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE > # SOFTWARE. > # > # Except as contained in this notice, the name of the XFree86 Project shall > # not be used in advertising or otherwise to promote the sale, use or other > # dealings in this Software without prior written authorization from the > # XFree86 Project. > # > > # ********************************************************************** > # Refer to the XF86Config(4/5) man page for details about the format of > # this file. > # ********************************************************************** > > # ********************************************************************** > # Files section. This allows default font and rgb paths to be set > # ********************************************************************** > > Section "Files" > > # The location of the RGB database. Note, this is the name of the > # file minus the extension (like ".txt" or ".db"). There is normally > # no need to change the default. > > RgbPath "/usr/X11R6/lib/X11/rgb" > > # Multiple FontPath entries are allowed (which are concatenated together), > # as well as specifying multiple comma-separated entries in one FontPath > # command (or a combination of both methods) > # > # If you don't have a floating point coprocessor and emacs, Mosaic or other > # programs take long to start up, try moving the Type1 and Speedo directory > # to the end of this list (or comment them out). > # > > FontPath "/usr/X11R6/lib/X11/fonts/local/" > FontPath "/usr/X11R6/lib/X11/fonts/misc/" > FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" > FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" > FontPath "/usr/X11R6/lib/X11/fonts/Type1/" > FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" > FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" > FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" > > # For OSs that support Dynamically loaded modules, ModulePath can be > # used to set a search path for the modules. This is currently supported > # for Linux ELF, FreeBSD 2.x and NetBSD 1.x. The default path is shown > # here. > > # ModulePath "/usr/X11R6/lib/modules" > > EndSection > > # ********************************************************************** > # Module section -- this is an optional section which is used to specify > # which dynamically loadable modules to load. Dynamically loadable > # modules are currently supported only for Linux ELF, FreeBSD 2.x > # and NetBSD 1.x. Currently, dynamically loadable modules are used > # only for some extended input (XInput) device drivers. > # ********************************************************************** > # > Section "Module" > # > # Matt's extra modules: > Load "xie.so" > Load "pex5.so" > # > # This loads the module for the Joystick driver > # > Load "xf86Jstk.so" > # > EndSection > > # ********************************************************************** > # Server flags section. > # ********************************************************************** > > Section "ServerFlags" > > # Uncomment this to cause a core dump at the spot where a signal is > # received. This may leave the console in an unusable state, but may > # provide a better stack trace in the core dump to aid in debugging > > # NoTrapSignals > > # Uncomment this to disable the server abort sequence > # This allows clients to receive this key event. > > # DontZap > > # Uncomment this to disable the / mode switching > # sequences. This allows clients to receive these key events. > > # DontZoom > > # Uncomment this to disable tuning with the xvidtune client. With > # it the client can still run and fetch card and monitor attributes, > # but it will not be allowed to change them. If it tries it will > # receive a protocol error. > > # DisableVidModeExtension > > # Uncomment this to enable the use of a non-local xvidtune client. > > # AllowNonLocalXvidtune > > # Uncomment this to disable dynamically modifying the input device > # (mouse and keyboard) settings. > > # DisableModInDev > > # Uncomment this to enable the use of a non-local client to > # change the keyboard or mouse settings (currently only xset). > > # AllowNonLocalModInDev > > EndSection > > # ********************************************************************** > # Input devices > # ********************************************************************** > > # ********************************************************************** > # Keyboard section > # ********************************************************************** > > Section "Keyboard" > > Protocol "Standard" > > # when using XQUEUE, comment out the above line, and uncomment the > # following line > > # Protocol "Xqueue" > > AutoRepeat 500 5 > # Let the server do the NumLock processing. This should only be required > # when using pre-R6 clients > # ServerNumLock > > # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) > # Xleds 1 2 3 > > # To set the LeftAlt to Meta, RightAlt key to ModeShift, > # RightCtl key to Compose, and ScrollLock key to ModeLock: > > # LeftAlt Meta > # RightAlt ModeShift > # RightCtl Compose > # ScrollLock ModeLock > > # To disable the XKEYBOARD extension, uncomment XkbDisable. > > # XkbDisable > > # To customise the XKB settings to suit your keyboard, modify the > # lines below (which are the defaults). For example, for a non-U.S. > # keyboard, you will probably want to use: > # XkbModel "pc102" > # If you have a US Microsoft Natural keyboard, you can use: > # XkbModel "microsoft" > # > # Then to change the language, change the Layout setting. > # For example, a german layout can be obtained with: > # XkbLayout "de" > # or: > # XkbLayout "de" > # XkbVariant "nodeadkeys" > # > # If you'd like to switch the positions of your capslock and > # control keys, use: > # XkbOptions "ctrl:swapcaps" > > # These are the default XKB settings for XFree86 > # XkbRules "xfree86" > # XkbModel "pc101" > # XkbLayout "us" > # XkbVariant "" > # XkbOptions "" > > XkbKeymap "xfree86(us)" > > EndSection > > # ********************************************************************** > # Pointer section > # ********************************************************************** > > Section "Pointer" > Protocol "Microsoft" > Device "/dev/cuaa0" > > # When using XQUEUE, comment out the above two lines, and uncomment > # the following line. > > # Protocol "Xqueue" > > # Baudrate and SampleRate are only for some Logitech mice > # or for the AceCad tablets which require 9600 baud > > # BaudRate 9600 > # SampleRate 150 > > # Emulate3Buttons is an option for 2-button Microsoft mice > # Emulate3Timeout is the timeout in milliseconds (default is 50ms) > > Emulate3Buttons > # Emulate3Timeout 50 > > # ChordMiddle is an option for some 3-button Logitech mice > > # ChordMiddle > > EndSection > > # ********************************************************************** > # Xinput section -- this is optional and is required only if you > # are using extended input devices. This is for example only. Refer > # to the XF86Config man page for a description of the options. > # ********************************************************************** > # > Section "Xinput" > # SubSection "WacomStylus" > # Port "/dev/ttyS1" > # DeviceName "Wacom" > # EndSubSection > # SubSection "WacomCursor" > # Port "/dev/ttyS1" > # EndSubSection > # SubSection "WacomEraser" > # Port "/dev/ttyS1" > # EndSubSection > # > # SubSection "Elographics" > # Port "/dev/ttyS1" > # DeviceName "Elo" > # MinimumXPosition 300 > # MaximumXPosition 3500 > # MinimumYPosition 300 > # MaximumYPosition 3500 > # Screen 0 > # UntouchDelay 10 > # ReportDelay 10 > # EndSubSection > # > SubSection "Joystick" > Port "/dev/joy0" > DeviceName "Joystick" > TimeOut 10 > MinimumXPosition 100 > MaximumXPosition 1300 > MinimumYPosition 100 > MaximumYPosition 1100 > # CenterX 700 > # CenterY 600 > Delta 20 > EndSubSection > # > # The Mouse Subsection contains the same type of entries as the > # standard Pointer Section (see above), with the addition of the > # DeviceName entry. > # > # SubSection "Mouse" > # Port "/dev/mouse2" > # DeviceName "Second Mouse" > # Protocol "Logitech" > # EndSubSection > EndSection > > # ********************************************************************** > # Monitor section > # ********************************************************************** > > # Any number of monitor sections may be present > > Section "Monitor" > > Identifier "Crap Noel" > VendorName "KTX" > ModelName "SVGA Plus" > > # HorizSync is in kHz unless units are specified. > # HorizSync may be a comma separated list of discrete values, or a > # comma separated list of ranges of values. > # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S > # USER MANUAL FOR THE CORRECT NUMBERS. > > HorizSync 31.5-35.8 > > # HorizSync 30-64 # multisync > # HorizSync 31.5, 35.2 # multiple fixed sync frequencies > # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies > > # VertRefresh is in Hz unless units are specified. > # VertRefresh may be a comma separated list of discrete values, or a > # comma separated list of ranges of values. > # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S > # USER MANUAL FOR THE CORRECT NUMBERS. > > VertRefresh 60-95 > > # Modes can be specified in two formats. A compact one-line format, or > # a multi-line format. > > # These two are equivalent > > # ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace > > # Mode "1024x768i" > # DotClock 45 > # HTimings 1024 1048 1208 1264 > # VTimings 768 776 784 817 > # Flags "Interlace" > # EndMode > > # This is a set of standard mode timings. Modes that are out of monitor spec > # are automatically deleted by the server (provided the HorizSync and > # VertRefresh lines are correct), so there's no immediate need to > # delete mode timings (unless particular mode timings don't work on your > # monitor). With these modes, the best standard mode that your monitor > # and video card can support for a given resolution is automatically > # used. > > # 640x400 @ 70 Hz, 31.5 kHz hsync > Modeline "640x400" 25.175 640 664 760 800 400 409 411 450 > # 640x480 @ 60 Hz, 31.5 kHz hsync > Modeline "640x480" 25.175 640 664 760 800 480 491 493 525 > # 800x600 @ 56 Hz, 35.15 kHz hsync > ModeLine "800x600" 36 800 824 896 1024 600 601 603 625 > # 1024x768 @ 87 Hz interlaced, 35.5 kHz hsync > Modeline "1024x768" 44.9 1024 1048 1208 1264 768 776 784 817 Interlace > > # 640x400 @ 85 Hz, 37.86 kHz hsync > Modeline "640x400" 31.5 640 672 736 832 400 401 404 445 -HSync +VSync > # 640x480 @ 72 Hz, 36.5 kHz hsync > Modeline "640x480" 31.5 640 680 720 864 480 488 491 521 > # 640x480 @ 75 Hz, 37.50 kHz hsync > ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -HSync -VSync > # 800x600 @ 60 Hz, 37.8 kHz hsync > Modeline "800x600" 40 800 840 968 1056 600 601 605 628 +hsync +vsync > > # 640x480 @ 85 Hz, 43.27 kHz hsync > Modeline "640x400" 36 640 696 752 832 480 481 484 509 -HSync -VSync > # 1152x864 @ 89 Hz interlaced, 44 kHz hsync > ModeLine "1152x864" 65 1152 1168 1384 1480 864 865 875 985 Interlace > > # 800x600 @ 72 Hz, 48.0 kHz hsync > Modeline "800x600" 50 800 856 976 1040 600 637 643 666 +hsync +vsync > # 1024x768 @ 60 Hz, 48.4 kHz hsync > Modeline "1024x768" 65 1024 1032 1176 1344 768 771 777 806 -hsync -vsync > > # 640x480 @ 100 Hz, 53.01 kHz hsync > Modeline "640x480" 45.8 640 672 768 864 480 488 494 530 -HSync -VSync > # 1152x864 @ 60 Hz, 53.5 kHz hsync > Modeline "1152x864" 89.9 1152 1216 1472 1680 864 868 876 892 -HSync -VSync > # 800x600 @ 85 Hz, 55.84 kHz hsync > Modeline "800x600" 60.75 800 864 928 1088 600 616 621 657 -HSync -VSync > > # 1024x768 @ 70 Hz, 56.5 kHz hsync > Modeline "1024x768" 75 1024 1048 1184 1328 768 771 777 806 -hsync -vsync > # 1280x1024 @ 87 Hz interlaced, 51 kHz hsync > Modeline "1280x1024" 80 1280 1296 1512 1568 1024 1025 1037 1165 Interlace > > # 800x600 @ 100 Hz, 64.02 kHz hsync > Modeline "800x600" 69.65 800 864 928 1088 600 604 610 640 -HSync -VSync > # 1024x768 @ 76 Hz, 62.5 kHz hsync > Modeline "1024x768" 85 1024 1032 1152 1360 768 784 787 823 > # 1152x864 @ 70 Hz, 62.4 kHz hsync > Modeline "1152x864" 92 1152 1208 1368 1474 864 865 875 895 > # 1280x1024 @ 61 Hz, 64.2 kHz hsync > Modeline "1280x1024" 110 1280 1328 1512 1712 1024 1025 1028 1054 > > # 1024x768 @ 85 Hz, 70.24 kHz hsync > Modeline "1024x768" 98.9 1024 1056 1216 1408 768 782 788 822 -HSync -VSync > # 1152x864 @ 78 Hz, 70.8 kHz hsync > Modeline "1152x864" 110 1152 1240 1324 1552 864 864 876 908 > > # 1280x1024 @ 70 Hz, 74.59 kHz hsync > Modeline "1280x1024" 126.5 1280 1312 1472 1696 1024 1032 1040 1068 -HSync -VSync > # 1600x1200 @ 60Hz, 75.00 kHz hsync > Modeline "1600x1200" 162 1600 1664 1856 2160 1200 1201 1204 1250 +HSync +VSync > # 1152x864 @ 84 Hz, 76.0 kHz hsync > Modeline "1152x864" 135 1152 1464 1592 1776 864 864 876 908 > > # 1280x1024 @ 74 Hz, 78.85 kHz hsync > Modeline "1280x1024" 135 1280 1312 1456 1712 1024 1027 1030 1064 > > # 1024x768 @ 100Hz, 80.21 kHz hsync > Modeline "1024x768" 115.5 1024 1056 1248 1440 768 771 781 802 -HSync -VSync > # 1280x1024 @ 76 Hz, 81.13 kHz hsync > Modeline "1280x1024" 135 1280 1312 1416 1664 1024 1027 1030 1064 > > # 1600x1200 @ 70 Hz, 87.50 kHz hsync > Modeline "1600x1200" 189 1600 1664 1856 2160 1200 1201 1204 1250 -HSync -VSync > # 1152x864 @ 100 Hz, 89.62 kHz hsync > Modeline "1152x864" 137.65 1152 1184 1312 1536 864 866 885 902 -HSync -VSync > # 1280x1024 @ 85 Hz, 91.15 kHz hsync > Modeline "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +HSync +VSync > # 1600x1200 @ 75 Hz, 93.75 kHz hsync > Modeline "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +HSync +VSync > # 1600x1200 @ 85 Hz, 105.77 kHz hsync > Modeline "1600x1200" 220 1600 1616 1808 2080 1200 1204 1207 1244 +HSync +VSync > # 1280x1024 @ 100 Hz, 107.16 kHz hsync > Modeline "1280x1024" 181.75 1280 1312 1440 1696 1024 1031 1046 1072 -HSync -VSync > > # 1800x1440 @ 64Hz, 96.15 kHz hsync > ModeLine "1800X1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync > # 1800x1440 @ 70Hz, 104.52 kHz hsync > ModeLine "1800X1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync > > # 512x384 @ 78 Hz, 31.50 kHz hsync > Modeline "512x384" 20.160 512 528 592 640 384 385 388 404 -HSync -VSync > # 512x384 @ 85 Hz, 34.38 kHz hsync > Modeline "512x384" 22 512 528 592 640 384 385 388 404 -HSync -VSync > > # Low-res Doublescan modes > # If your chipset does not support doublescan, you get a 'squashed' > # resolution like 320x400. > > # 320x200 @ 70 Hz, 31.5 kHz hsync, 8:5 aspect ratio > Modeline "320x200" 12.588 320 336 384 400 200 204 205 225 Doublescan > # 320x240 @ 60 Hz, 31.5 kHz hsync, 4:3 aspect ratio > Modeline "320x240" 12.588 320 336 384 400 240 245 246 262 Doublescan > # 320x240 @ 72 Hz, 36.5 kHz hsync > Modeline "320x240" 15.750 320 336 384 400 240 244 246 262 Doublescan > # 400x300 @ 56 Hz, 35.2 kHz hsync, 4:3 aspect ratio > ModeLine "400x300" 18 400 416 448 512 300 301 302 312 Doublescan > # 400x300 @ 60 Hz, 37.8 kHz hsync > Modeline "400x300" 20 400 416 480 528 300 301 303 314 Doublescan > # 400x300 @ 72 Hz, 48.0 kHz hsync > Modeline "400x300" 25 400 424 488 520 300 319 322 333 Doublescan > # 480x300 @ 56 Hz, 35.2 kHz hsync, 8:5 aspect ratio > ModeLine "480x300" 21.656 480 496 536 616 300 301 302 312 Doublescan > # 480x300 @ 60 Hz, 37.8 kHz hsync > Modeline "480x300" 23.890 480 496 576 632 300 301 303 314 Doublescan > # 480x300 @ 63 Hz, 39.6 kHz hsync > Modeline "480x300" 25 480 496 576 632 300 301 303 314 Doublescan > # 480x300 @ 72 Hz, 48.0 kHz hsync > Modeline "480x300" 29.952 480 504 584 624 300 319 322 333 Doublescan > > EndSection > > # ********************************************************************** > # Graphics device section > # ********************************************************************** > > # Any number of graphics device sections may be present > > # Standard VGA Device: > > Section "Device" > Identifier "Generic VGA" > VendorName "Unknown" > BoardName "Unknown" > Chipset "generic" > > # VideoRam 256 > > # Clocks 25.2 28.3 > > EndSection > > # Sample Device for accelerated server: > > # Section "Device" > # Identifier "Actix GE32+ 2MB" > # VendorName "Actix" > # BoardName "GE32+" > # Ramdac "ATT20C490" > # Dacspeed 110 > # Option "dac_8_bit" > # Clocks 25.0 28.0 40.0 0.0 50.0 77.0 36.0 45.0 > # Clocks 130.0 120.0 80.0 31.0 110.0 65.0 75.0 94.0 > # EndSection > > # Sample Device for Hercules mono card: > > # Section "Device" > # Identifier "Hercules mono" > # EndSection > > # Device configured by xf86config: > > Section "Device" > Identifier "Jaton VIDEO-58P" > VendorName "Jaton" > BoardName "VIDEO-58P" > VideoRam 2304 > #videoram 2304 # 2.25 MB, when memory probe is incorrect > #Option "linear" # for linear mode at 8bpp > #Option "noaccel" # when problems with accelerator > #Option "power_saver" # enable VESA DPMS > #Option "pci_retry" # faster, but problematic for ISA DMA > #Option "hw_cursor" # Use hardware cursor (see docs for limitations) > #Option "xaa_no_color_exp" # When text (or bitmap) is not rendered correctly > # Insert Clocks lines here if appropriate > EndSection > > # ********************************************************************** > # Screen sections > # ********************************************************************** > > # The Colour SVGA server > > Section "Screen" > Driver "svga" > # Use Device "Generic VGA" for Standard VGA 320x200x256 > #Device "Generic VGA" > Device "Jaton VIDEO-58P" > DefaultColorDepth 16 > Monitor "Crap Noel" > Subsection "Display" > Depth 8 > # Omit the Modes line for the "Generic VGA" device > Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" > ViewPort 0 0 > # Use Virtual 320 200 for Generic VGA > EndSubsection > Subsection "Display" > Depth 16 > Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" > ViewPort 0 0 > EndSubsection > Subsection "Display" > Depth 24 > Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" > ViewPort 0 0 > EndSubsection > Subsection "Display" > Depth 32 > Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" > ViewPort 0 0 > EndSubsection > EndSection > > # The 16-color VGA server > > Section "Screen" > Driver "vga16" > Device "Generic VGA" > Monitor "Crap Noel" > Subsection "Display" > Modes "640x480" "800x600" > ViewPort 0 0 > Virtual 800 600 > EndSubsection > EndSection > > # The Mono server > > Section "Screen" > Driver "vga2" > Device "Generic VGA" > Monitor "Crap Noel" > Subsection "Display" > Modes "640x480" "800x600" > ViewPort 0 0 > Virtual 800 600 > EndSubsection > EndSection > > # The accelerated servers (S3, Mach32, Mach8, 8514, P9000, AGX, W32, Mach64) > > Section "Screen" > Driver "accel" > Device "Jaton VIDEO-58P" > Monitor "Crap Noel" > Subsection "Display" > Depth 8 > Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" > ViewPort 0 0 > EndSubsection > Subsection "Display" > Depth 16 > Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" > ViewPort 0 0 > EndSubsection > Subsection "Display" > Depth 24 > Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" > ViewPort 0 0 > EndSubsection > Subsection "Display" > Depth 32 > Modes "1024x768" "320x200" "320x240" "400x300" "512x384" "640x480" "800x600" > ViewPort 0 0 > EndSubsection > EndSection > > ---------------------------------------------------------------------------- > 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: Sat May 8 11:07:38 CST 1999 > root@localhost:/usr/src/sys/compile/MATTE > Timecounter "i8254" frequency 1193182 Hz > CPU: Celeron (300.68-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x660 Stepping=0 > Features=0x183f9ff > real memory = 67108864 (65536K bytes) > config> pnp 1 0 bios enable > sio0: system console > avail memory = 62124032 (60668K bytes) > Preloaded elf kernel "kernel" at 0xc02f4000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc02f409c. > Pentium Pro MTRR support enabled, default memory type is uncacheable > Probing for PnP devices: > CSN 1 Vendor ID: CTL0024 [0x24008c0e] Serial 0x100a1ec0 Comp ID: PNP0600 [0x0006d041] > npx0: on motherboard > npx0: INT 16 interface > apm0: on motherboard > apm: found APM BIOS version 1.2 > pcib0: on motherboard > pci0: on pcib0 > chip0: at device 0.0 on pci0 > chip1: at device 1.0 on pci0 > isab0: at device 7.0 on pci0 > ide_pci0: at device 7.1 on pci0 > chip2: at device 7.3 on pci0 > ncr0: at device 13.0 on pci0 > ncr0: interrupting at irq 7 > isa0: on motherboard > atkbdc0: at port 0x60 on isa0 > atkbd0: on atkbdc0 > atkbd0: interrupting at irq 1 > psm0: on atkbdc0 > psm0: model IntelliMouse, device ID 3 > psm0: interrupting at irq 12 > vga0: on isa0 > sc0: on isa0 > sc0: VGA color <12 virtual consoles, flags=0x0> > wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 > wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 > wd0: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S > wdc0: interrupting at irq 14 > wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 > wdc1: unit 1 (atapi): , removable, dma, iordis > wcd0: drive speed 4687KB/sec, 120KB cache > wcd0: supported read types: CD-R, CD-RW, CD-DA > wcd0: Audio: play, 255 volume levels > wcd0: Mechanism: ejectable tray > wcd0: Medium: no/blank disc inside, unlocked > wdc1: interrupting at irq 15 > fdc0: interrupting at irq 6 > 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 > sio0: interrupting at irq 4 > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > sio1: interrupting at irq 3 > ed0 at port 0x300-0x31f irq 9 on isa0 > ed0: address 00:00:e8:20:33:e8, type NE2000 (16 bit) > ed0: interrupting at irq 9 > joy0 at port 0x201 on isa0 > joy0: joystick > sb0 at port 0x220 irq 5 drq 1 on isa0 > snd0: > sb0: interrupting at irq 5 > sbxvi0 at drq 5 on isa0 > snd0: > sbmidi0 at port 0x330 on isa0 > snd0: > opl0 at port 0x388 on isa0 > snd0: > changing root device to wd0s2a -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 9:19:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 63EDE14A12 for ; Sun, 16 May 1999 09:19:53 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id SAA49192; Sun, 16 May 1999 18:19:46 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Sun, 16 May 1999 18:19:41 +0200 (CEST) From: Leif Neland To: Marc van Woerkom Cc: freebsd-current@FreeBSD.ORG Subject: Re: No sound (Ensoniq Audio PCI 1370) In-Reply-To: <199905151958.VAA14199@oranje.my.domain> 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, 15 May 1999, Marc van Woerkom wrote: > Dear people, > > I get no sound anymore using the system built on Friday. > > As I saw same earlier reports here about problems with sound > that were reported to be fixed, mine might be related to the card > being a PCI one - ES1370 based genuine Ensoniq Audio PCI. > > Below follow dmesg output and kernel configuration. > device pcm0 at isa? port ? irq 10 drq 1 flags 0x0 > > I have this: device pcm0 at nexus? port ? irq 10 drq 1 flags 0x0 ^^^^^^ Leif Neland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 9:21:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 9344D14A12 for ; Sun, 16 May 1999 09:21:11 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-12-70.camtech.net.au [203.55.242.70]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id BAA14357; Mon, 17 May 1999 01:56:02 +0930 (CST) Message-ID: <373EF0B7.60FE8868@camtech.com.au> Date: Mon, 17 May 1999 01:52:15 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Khetan Gajjar Cc: "Bret A. Ford" , freebsd-current@FreeBSD.ORG Subject: Re: Different SCSI probe behavior References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Every time I boot my -CURRENT system at work I get this problem. And for me its not recent, its been happening ever since the aha driver was finally converted to CAM I think (3 or 4 months I guess). I am using a 1542B with an old Wren drive and some other drive. (Wren 7G springs to mind but I cant be sure). A 1.5GB and a 1.8GB drive are all I have on the SCSI bus. I haven't mentioned it because it still works OK after the 30 or so second delay and I'm too busy at work to provide enough information and follow an email exchange (as I'm not on the lists at work anymore). Khetan Gajjar wrote: > > On Sat, 15 May 1999, Bret A. Ford wrote: > > >Waiting 10 seconds for SCSI devices to settle > >aha0: ahafetchtransinfo - Inquire Setup Info Failed > >(probe20:aha0:0:5:0): CCB 0xc553b450 - timed out > >(probe20:aha0:0:5:0): CCB 0xc553b450 - timed out > >aha0: No longer in timeout > > I'm seeing the same thing, but for 3 of my > devices on a chain with 4 devices. It takes quite long, > but doesn't appear to do any damage or decrease functionality > (so far that is). > > >Do I need to update something for normal behavior? I've been following > >freebsd-current and cvs-all, though I might have missed something > >that would have clued me in. > > I've seen Werner Losch discovering a problem with the aha > driver in -stable, and he committed a fix for that. > Is it possible for that fix to be MFS ? > --- > Khetan Gajjar (!kg1779) * khetan@iafrica.com ; khetan@os.org.za > http://www.os.org.za/~khetan * Talk/Finger khetan@chain.freebsd.os.org.za > FreeBSD enthusiast * http://www2.za.freebsd.org/ > Security-wise, NT is a OS with a "kick me" sign taped to it > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 9:41:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 506C714F37 for ; Sun, 16 May 1999 09:41:44 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id SAA20836 for ; Sun, 16 May 1999 18:41:43 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma020834; Sun, 16 May 99 18:41:43 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id SAA03653 for ; Sun, 16 May 1999 18:41:43 +0200 (MET DST) Received: (qmail 66521 invoked by uid 666); 16 May 1999 16:42:03 -0000 Date: Sun, 16 May 1999 18:42:03 +0200 From: Jos Backus To: current@FreeBSD.ORG Subject: MFS still hosed Message-ID: <19990516184203.A66381@hal.mpn.cp.philips.com> Reply-To: Jos Backus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With todays -current, mounting /tmp using swap /tmp mfs rw,nosuid,nodev,-s=32768 0 0 yields a Fatal trap 12: page fault while in kernel mode fault virtual address = 0x9d203590 fault code = supervisor read, page not present instruction pointer = 0x8:0xc016f30c stack pointer = 0x10:0xc5aa2d70 frame pointer = 0x10:0xc5aa2d9c code segment = base 0x0, limit 0xffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 362 (mount_mfs) Stopped at checkalias+0x13c: movl cdevsw(%eax),%eax %eax contains 0xdcfba6d0 This line in checkalias() in vfs_subr.c seems to be the culprit: 1488: 56 pushl %esi 1489: e8 fc ff ff ff call 148a 148e: 8b 04 85 00 00 movl 0x0(,%eax,4),%eax 1493: 00 00 1495: c1 e0 02 shll $0x2,%eax => 1498: 8b 80 00 00 00 movl 0x0(%eax),%eax 149d: 00 149e: 89 45 e4 movl %eax,0xffffffe4(%ebp) (I'm not sure yet which source line this section corresponds to :-) Anyone else seen this? -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 11:55:28 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 E86BF14D87 for ; Sun, 16 May 1999 11:55:25 -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 MAA53813; Sun, 16 May 1999 12:54:22 -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 MAA65805; Sun, 16 May 1999 12:55:41 -0600 (MDT) Message-Id: <199905161855.MAA65805@harmony.village.org> To: Khetan Gajjar Subject: Re: Different SCSI probe behavior Cc: "Bret A. Ford" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 15 May 1999 21:28:48 +0200." References: Date: Sun, 16 May 1999 12:55:41 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Khetan Gajjar writes: : On Sat, 15 May 1999, Bret A. Ford wrote: : : >Waiting 10 seconds for SCSI devices to settle : >aha0: ahafetchtransinfo - Inquire Setup Info Failed : >(probe20:aha0:0:5:0): CCB 0xc553b450 - timed out : >(probe20:aha0:0:5:0): CCB 0xc553b450 - timed out : >aha0: No longer in timeout : : I'm seeing the same thing, but for 3 of my : devices on a chain with 4 devices. It takes quite long, : but doesn't appear to do any damage or decrease functionality : (so far that is). : : >Do I need to update something for normal behavior? I've been following : >freebsd-current and cvs-all, though I might have missed something : >that would have clued me in. : : I've seen Werner Losch discovering a problem with the aha : driver in -stable, and he committed a fix for that. : Is it possible for that fix to be MFS ? Ahem, it is Warner Losh :-). There was a problem in -stable (and likely -current) for some aha cards. The ahafetchtransinfo routine is called at probe time, so if there are timeouts there and no where else they can be safely ignored, even if it is an irritation. I commited fixes to both -stable and -current for this problem, so you might want to try post a May 14 kernel. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 11:57:27 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 048D614E08 for ; Sun, 16 May 1999 11:57:24 -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 MAA53823; Sun, 16 May 1999 12:56:21 -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 MAA65831; Sun, 16 May 1999 12:57:40 -0600 (MDT) Message-Id: <199905161857.MAA65831@harmony.village.org> To: "Bret A. Ford" Subject: Re: Different SCSI probe behavior Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 15 May 1999 11:40:01 PDT." <199905151840.LAA00776@uop.cs.uop.edu> References: <199905151840.LAA00776@uop.cs.uop.edu> Date: Sun, 16 May 1999 12:57:40 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905151840.LAA00776@uop.cs.uop.edu> "Bret A. Ford" writes: : This morning, I did an installworld and booted a new -current : world and -current kernel (Sources from morning of Fri May 14th). : I got the following messages during the SCSI probe: : : Waiting 10 seconds for SCSI devices to settle : aha0: ahafetchtransinfo - Inquire Setup Info Failed : (probe20:aha0:0:5:0): CCB 0xc553b450 - timed out : (probe20:aha0:0:5:0): CCB 0xc553b450 - timed out : aha0: No longer in timeout : : I'm not sure what to make of this. After a bit of a delay - 30 or : so seconds, I don't quite recall how long - the system continued : booting, normally the rest of the way, and seems to be functional. : Do I need to update something for normal behavior? I've been following : freebsd-current and cvs-all, though I might have missed something : that would have clued me in. I've fixed this late Friday. You need aha.c 1.25 or newer in order to correct this problem. : ahc0: at slot 4 on eisa0 : ahc0: aic7770 >= Rev E, Wide Channel A, SCSI Id=7, 4/255 SCBs : aha0 at ports 0x130-0x133 and 0x131-0x134 irq 11 drq 7 on isa0 : aha0: AHA-1542C FW Rev. 0.1 (ID=44) SCSI Host Adapter, SCSI ID 7, 16 CCBs Intesting. My 1542C didn't show this behavior, but I have put the workaround in... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 11:58:49 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 BDDC714C9E for ; Sun, 16 May 1999 11:58:46 -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 MAA53830; Sun, 16 May 1999 12:57:43 -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 MAA65851; Sun, 16 May 1999 12:59:01 -0600 (MDT) Message-Id: <199905161859.MAA65851@harmony.village.org> To: Matthew Thyer Subject: Re: Different SCSI probe behavior Cc: Khetan Gajjar , "Bret A. Ford" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 May 1999 01:52:15 +0930." <373EF0B7.60FE8868@camtech.com.au> References: <373EF0B7.60FE8868@camtech.com.au> Date: Sun, 16 May 1999 12:59:01 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <373EF0B7.60FE8868@camtech.com.au> Matthew Thyer writes: : Every time I boot my -CURRENT system at work I get this problem. : And for me its not recent, its been happening ever since the aha : driver was finally converted to CAM I think (3 or 4 months I guess). : : I am using a 1542B with an old Wren drive and some other drive. : (Wren 7G springs to mind but I cant be sure). A 1.5GB and a 1.8GB : drive are all I have on the SCSI bus. : : I haven't mentioned it because it still works OK after the 30 or : so second delay and I'm too busy at work to provide enough : information and follow an email exchange (as I'm not on the lists : at work anymore). Please try the latest aha driver. Please do let me know if you see this on your machine at boot, as I've not seen it on mine. I'll do more testing of different aha cards shortly... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 12:46:14 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 B636214E7E for ; Sun, 16 May 1999 12:46:12 -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 MAA01570 for ; Sun, 16 May 1999 12:46:12 -0700 (PDT) (envelope-from eculp@MexComUSA.net) Message-ID: <373F2084.F9A29F9@MexComUSA.net> Date: Sun, 16 May 1999 12:46:12 -0700 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: KDE-1.1.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With a current as of yesterday morning, I just tried to upgrade to KDE-1.1.1 through ports kde11 and had the problem with libstdc++.so.3 and libstdc++.so.2 conflicts. Does anyone know an easy workaround? It seems to show up throught the kde package. Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 13:11: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles551.castles.com [208.214.165.115]) by hub.freebsd.org (Postfix) with ESMTP id DFE1A14BE9 for ; Sun, 16 May 1999 13:10:59 -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 MAA07783; Sun, 16 May 1999 12:55:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905161955.MAA07783@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bob Bishop Cc: "Carlos C. Tapang" , current@freebsd.org Subject: Re: FBSDBOOT.EXE In-reply-to: Your message of "Wed, 12 May 1999 02:44:22 BST." <3.0.6.32.19990512024422.0081e210@192.168.255.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 16 May 1999 12:55:56 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > At 15:22 11/05/99 -0700, you wrote: > >Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF. > >If anybody else needs it, please let me know and I'll see what I can do for > >you. > > I'm going to have a use for it RSN It doesn't work. Don't use it. You need to reboot the system to restore various vectors that DOS destroys. Please see the previous threads on this topic, especially anything from Robert Nordier. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 13:36:49 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 8C9E514BE9 for ; Sun, 16 May 1999 13:36:48 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id NAA22579; Sun, 16 May 1999 13:36:45 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Sun, 16 May 1999 13:36:44 -0700 (PDT) From: Doug White To: Jos Backus Cc: current@FreeBSD.ORG Subject: Re: MFS still hosed In-Reply-To: <19990516184203.A66381@hal.mpn.cp.philips.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, 16 May 1999, Jos Backus wrote: > With todays -current, mounting /tmp using > swap /tmp mfs rw,nosuid,nodev,-s=32768 0 0 > yields a > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x9d203590 I've been getting this for a week now. :( Luoqui Chen suggested bumping NUMCDEV in src/sys/kern/kern_conf.c to 255 to get around it, and a couple of people had success, including myself. I've filed PR kern/11737 with the fix. 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 Sun May 16 13:39:49 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 579C115159; Sun, 16 May 1999 13:39:48 -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 NAA28054; Sun, 16 May 1999 13:39:47 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA12109; Sun, 16 May 1999 13:39:47 -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: Sun, 16 May 1999 13:39:47 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: phk@freebsd.org Subject: sys/types.h rev. 1.33 breaks ps etc. on alpha Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Revision 1.33 of src/sys/types.h, which changed dev_t to a void * in the kernel, breaks ps and a bunch of other things on the alpha. Since dev_t now has a different size in the kernel than in userland, ps and friends get a "proc size mismatch". 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 Sun May 16 14:38:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 0C95014F8D for ; Sun, 16 May 1999 14:38:32 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id XAA12269; Sun, 16 May 1999 23:37:40 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Sun, 16 May 1999 23:37:40 +0200 (CEST) From: Leif Neland To: Mike Smith Cc: Bob Bishop , "Carlos C. Tapang" , current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE In-Reply-To: <199905161955.MAA07783@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 Sun, 16 May 1999, Mike Smith wrote: > > Hi, > > > > At 15:22 11/05/99 -0700, you wrote: > > >Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF. > > >If anybody else needs it, please let me know and I'll see what I can do for > > >you. > > > > I'm going to have a use for it RSN > > It doesn't work. Don't use it. You need to reboot the system to > restore various vectors that DOS destroys. Please see the previous > threads on this topic, especially anything from Robert Nordier. > > Well, it works for me. The only problem is that fbsdboot never returns, allowing win98 to clean up. Therefore win98 tries to start my "dos program" on each boot. Luckily I have C: accessible as /c, so I could edit autoexec.bat and config.sys Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 14:41:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 9EA5D14C91 for ; Sun, 16 May 1999 14:41:05 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id XAA21209 for ; Sun, 16 May 1999 23:41:04 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma021205; Sun, 16 May 99 23:41:04 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id XAA02046 for ; Sun, 16 May 1999 23:41:03 +0200 (MET DST) Received: (qmail 68465 invoked by uid 666); 16 May 1999 21:41:24 -0000 Date: Sun, 16 May 1999 23:41:24 +0200 From: Jos Backus To: Doug White Cc: current@FreeBSD.ORG Subject: Re: MFS still hosed Message-ID: <19990516234124.A68433@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990516184203.A66381@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Doug White on Sun, May 16, 1999 at 01:36:44PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, May 16, 1999 at 01:36:44PM -0700, Doug White wrote: > I've been getting this for a week now. :( Luoqui Chen suggested bumping > NUMCDEV in src/sys/kern/kern_conf.c to 255 to get around it, and a couple > of people had success, including myself. I'll do that then. Thanks! Groetjes, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 16:22:55 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 474C91518D for ; Sun, 16 May 1999 16:22:54 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id QAA75772; Sun, 16 May 1999 16:22:53 -0700 (PDT) From: Archie Cobbs Message-Id: <199905162322.QAA75772@bubba.whistle.com> Subject: Re: Nt source licenses... In-Reply-To: <373E69F2.5BFADB76@excite.com> from Dean Lombardo at "May 16, 99 07:47:14 am" To: dlombardo@excite.com (Dean Lombardo) Date: Sun, 16 May 1999 16:22:53 -0700 (PDT) Cc: 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 Dean Lombardo writes: > > At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote: > > > Are we going to get this license? I am interested in NTFS > > > source code a lot... > > > > I would be very careful about getting an NT source license if > > your intention is to write NTFS support for some other operating > > system. Microsoft is not doing this licensing for the benefit of > > mankind, they are doing it to attract college-type users to > > sticking with WinNT over open-source unixes. > > > > The last thing we need is some code from WinNT which causes us > > to be sued by Microsoft... > > They can't sue - unless, of course, the code is copied verbatim (and > it's not very likely to be, anyway). Otherwise, it shouldn't be any > more illegal than reverse engineering the code, and several federal > appeals courts have held that it is "fair use" to reverse engineer a > program in order to examine and copy its ideas and any unprotected > expression. You're forgetting about possible patent violations... -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 Sun May 16 17:15:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (Postfix) with ESMTP id A63F614C25 for ; Sun, 16 May 1999 17:15:26 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with SMTP id RAA08739; Sun, 16 May 1999 17:14:42 -0700 Message-ID: <00f401be9ffa$8e7204f0$0d787880@apex.tapang> From: "Carlos C. Tapang" To: "Bob Bishop" , "Mike Smith" Cc: Subject: Re: FBSDBOOT.EXE Date: Sun, 16 May 1999 17:16:44 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It doesn't work. Don't use it. You need to reboot the system to >restore various vectors that DOS destroys. Please see the previous >threads on this topic, especially anything from Robert Nordier. > The most relevant piece I can find from R. Nordier is the following: "The fbsdboot.exe program should probably be considered obsolete. It should (in theory) be possible to use it to load /boot/loader, which can then load the kernel, but there are various reasons this doesn't work too well." I have not tested the updated program with /boot/loader. /boot/loader does not help me because my root directory is in a memory file system, and I can not assume that my users will want to reformat their DOS drives or even repartition it. So all FreeBSD files are in the DOS file system. --Carlos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 17:23:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from gina.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 89BBC14BDB for ; Sun, 16 May 1999 17:23:44 -0700 (PDT) (envelope-from root@neland.dk) Received: from gina (gina [192.168.0.14]) by gina.neland.dk (8.9.3/8.9.3) with ESMTP id CAA00338 for ; Mon, 17 May 1999 02:24:07 +0200 (CEST) (envelope-from root@neland.dk) Date: Mon, 17 May 1999 02:24:06 +0200 (CEST) From: Leif Neland To: freebsd-current@freebsd.org Subject: rplayd: mixer not installed 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 At boot I get this message: /usr/local/sbin/rplayd: rplay_audio_get_volume: pcm mixer device not installed. However, /dev/mixer is installed, and works. I'm using current, Luiqi's pcm and a ESS soundcard. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 18:27:38 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 0B8F814FC7 for ; Sun, 16 May 1999 18:27:29 -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 LAA04147; Mon, 17 May 1999 11:27:23 +1000 Date: Mon, 17 May 1999 11:27:23 +1000 From: Bruce Evans Message-Id: <199905170127.LAA04147@godzilla.zeta.org.au> To: current@FreeBSD.ORG, dawes@rf900.physics.usyd.edu.au, green@unixhelp.org, jkh@zippy.cdrom.com, thyerm@camtech.com.au Subject: Re: Fixed my MAMEd sio problem. Was: Re: Doesn't anyone care about the broken sio ?? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Just so you all know (the list included) how I have fixed my silo >overflow problem which occurred while running xmame (and after I quit >until I restarted the X server).... > >I have found the problem doesn't occur if I remove the following lines >from the shell script I use to start xmame: > >xsetpointer Joystick >sleep 1 >xsetpointer pointer FreeBSD's joystick driver certainly causes silo overflows. It disables CPU interrupts and polls for 2 msec. For 16550 serial hardware, this may cause loss of 21 characters at 115200 bps (23 characters arriving in 2 msec less 2 characters of buffering provided by the 16550 fifo above the trigger level). If sio used a more conservative trigger level of 8, then then the loss would be limited to only 15 characters. >With those lines in the script I had to restart the X-server after >using xmame or I'd get continuous silo overflows. Closing the joystick device should also work. The joystick driver shouldn't disable CPU interrupts or mask clock interrupts. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 18:53:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from surreal.vrhost.com (unknown [216.25.158.22]) by hub.freebsd.org (Postfix) with ESMTP id 3F06C14FC7 for ; Sun, 16 May 1999 18:53:14 -0700 (PDT) (envelope-from gary@tbe.net) Received: from surreal.vrhost.com (surreal.vrhost.com [216.25.158.22]) by surreal.vrhost.com (Postfix) with SMTP id C666B3C9C for ; Sun, 16 May 1999 21:53:13 -0400 (EDT) Date: Sun, 16 May 1999 21:53:13 -0400 (EDT) From: "Gary D. Margiotta" X-Sender: gary@surreal.vrhost.com To: current@freebsd.org Subject: Building ports... 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 Heya... I apologize if this is a slight off topic question, but I think it might be related to -current... Just loaded a 3.1-STABLE box, and went to build a couple of ports. First it told me that I couldn't use the bsd.port.mk because it was too old. Fine, so I go and cvsup the current sources for /usr/share, and I do a make install in /usr/src/share/mk. The files install properly, and I go to the ports collection. I go into a number of ports, and try a 'make' an any given port. It then tells me the following: fetch: illegal option -- A So, it can't go out and grab the needed files to build the port. No big deal, I just go grab the source and make it manually. This is not a huge problem, but I'm just wondering what I've done wrong, or what I'm stupidly forgetting to add or do additionally... Any feedback would be great, TIA!!! ______________________________________________________________ -Gary Margiotta Voice: (973) 835-7855 TBE Internet Services Fax: (973) 835-4755 http://www.tbe.net E-Mail: gary@tbe.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 19:28:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles551.castles.com [208.214.165.115]) by hub.freebsd.org (Postfix) with ESMTP id C1BFA14C91 for ; Sun, 16 May 1999 19:28:30 -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 TAA09636; Sun, 16 May 1999 19:13:29 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905170213.TAA09636@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Carlos C. Tapang" Cc: "Bob Bishop" , "Mike Smith" , current@freebsd.org Subject: Re: FBSDBOOT.EXE In-reply-to: Your message of "Sun, 16 May 1999 17:16:44 PDT." <00f401be9ffa$8e7204f0$0d787880@apex.tapang> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 16 May 1999 19:13:26 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >It doesn't work. Don't use it. You need to reboot the system to > >restore various vectors that DOS destroys. Please see the previous > >threads on this topic, especially anything from Robert Nordier. > > > The most relevant piece I can find from R. Nordier is the following: > "The fbsdboot.exe program should probably be considered obsolete. It > should (in theory) be possible to use it to load /boot/loader, which > can then load the kernel, but there are various reasons this doesn't > work too well." These reasons were also expounded, and I did summarise them in another message on this thread. > I have not tested the updated program with /boot/loader. /boot/loader does > not help me because my root directory is in a memory file system, and I can > not assume that my users will want to reformat their DOS drives or even > repartition it. So all FreeBSD files are in the DOS file system. The loader won't help you because you are booting from under DOS, but the loader will boot the kernel just fine off a DOS filesystem. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 19:30: 0 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 F02EA14C91 for ; Sun, 16 May 1999 19:29:56 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id EAA00405; Mon, 17 May 1999 04:33:13 +0200 (CEST) To: current@FreeBSD.ORG Subject: zzz crashing in current OR inthand_remove not removing handlers properly Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 17 May 1999 04:33:12 +0200 Message-ID: <5lr9ogzaqf.fsf@assaris.sics.se> Lines: 106 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, on a -current from around a week ago `zzz' always managed to crash my machine. The relevant parts from the panic and the backtrace are included below. It seems that the cause of this was a stray interrupt was arriving after having unloaded the driver. For some reason it wasn't handled by isa_strayintr, and the reason for that was that inthand_remove didn't manage to remove the interrupt (and get it replaced by the stray function) correctly. After applying the patch at the end of this mail I can once again sleep my laptop succesfully. /assar ---------------------------------------------------------------------- from dmesg: ep0: utp/bnc[*UTP*] address 00:a0:24:af:cc:7e APM ioctl: cmd = 0x20005001 DEVICE_SUSPEND error 6, ignored Execute APM hook "pcm suspend handler." Called APM sound suspend hook for unit 0 Execute APM hook "Cirrus Logic PD672X." Execute APM hook "Cirrus Logic PD672X." ep0: unload Return IRQ=11 from the panic: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0256ff3 stack pointer = 0x10:0xc39a6cdc frame pointer = 0x10:0xc39a6ce4 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 = 951 (zzz) interrupt mask = net tty and the backtrace: #9 0xc02020ef in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = -2147483648, tf_ebp = -1013289756, tf_isp = -1013289784, tf_ebx = -1068408832, tf_edx = -1071675062, tf_ecx = 10, tf_eax = -1071288448, tf_trapno = 12, tf_err = 2, tf_eip = -1071288333, tf_cs = 8, tf_eflags = 68103, tf_esp = -1071576167, tf_ss = -559038242}) at ../../i386/i386/trap.c:436 #10 0xc0256ff3 in M_TEMP () #11 0xc02106ce in splx (ipl=3223270597) at ../../i386/isa/ipl_funcs.c:106 #12 0xc01f34c5 in apm_execute_hook (list=0xc0511c00) at ../../i386/apm/apm.c:351 #13 0xc01f3650 in apm_suspend (state=2) at ../../i386/apm/apm.c:466 #14 0xc01f3f98 in apmioctl (dev=9984, cmd=536891393, addr=0xc39a6edc "", flag=3, p=0xc3639520) at ../../i386/apm/apm.c:991 #15 0xc0165fae in spec_ioctl (ap=0xc39a6e18) at ../../miscfs/specfs/spec_vnops.c:440 #16 0xc0165839 in spec_vnoperate (ap=0xc39a6e18) at ../../miscfs/specfs/spec_vnops.c:129 #17 0xc01d8ebd in ufs_vnoperatespec (ap=0xc39a6e18) at ../../ufs/ufs/ufs_vnops.c:2327 #18 0xc015d0b5 in vn_ioctl (fp=0xc08ab680, com=536891393, data=0xc39a6edc "", p=0xc3639520) at vnode_if.h:395 #19 0xc013f1b7 in ioctl (p=0xc3639520, uap=0xc39a6f90) at ../../kern/sys_generic.c:564 #20 0xc0202a56 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 3, tf_esi = -1077944864, tf_ebp = -1077945212, tf_isp = -1013288988, tf_ebx = 0, tf_edx = -1077944868, tf_ecx = 0, tf_eax = 54, tf_trapno = 7, tf_err = 2, tf_eip = 671703256, tf_cs = 31, tf_eflags = 514, tf_esp = -1077945228, tf_ss = 47}) at ../../i386/i386/trap.c:1066 #21 0xc01f79b0 in Xint0x80_syscall () ---------------------------------------------------------------------- Index: sys/i386/isa/intr_machdep.c =================================================================== RCS file: /src/fbsd-repository/src/sys/i386/isa/intr_machdep.c,v retrieving revision 1.21 diff -u -w -u -w -r1.21 intr_machdep.c --- intr_machdep.c 1999/05/04 21:18:20 1.21 +++ intr_machdep.c 1999/05/17 02:15:18 @@ -823,12 +823,11 @@ oldspl = splq(1 << irq); - /* we want to remove the list head, which was known to intr_mux */ - icu_unset(irq, intr_mux); /* check whether the new list head is the only element on list */ head = intreclist_head[irq]; if (head != NULL) { + icu_unset(irq, intr_mux); if (head->next != NULL) { /* install the multiplex handler with new list head as argument */ errcode = icu_setup(irq, intr_mux, head, 0, 0); @@ -842,6 +841,8 @@ if (errcode == 0) update_intrname(irq, head->name); } + } else { + icu_unset(irq, idesc->handler); } splx(oldspl); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 20: 7:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id CFA581523C for ; Sun, 16 May 1999 20:07:43 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-79-127.atl.bellsouth.net [209.214.79.127]) by mail1.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id XAA01953; Sun, 16 May 1999 23:05:52 -0400 (EDT) Received: from wghicks (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id XAA16468; Sun, 16 May 1999 23:09:21 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199905170309.XAA16468@bellsouth.net> To: Mike Smith Cc: current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: FBSDBOOT.EXE In-reply-to: Your message of "Sun, 16 May 1999 19:13:26 PDT." <199905170213.TAA09636@dingo.cdrom.com> Date: Sun, 16 May 1999 23:09:21 -0400 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The loader won't help you because you are booting from under DOS, but > the loader will boot the kernel just fine off a DOS filesystem. I'd like to understand this aspect of the loader better. This mode might be useful for booting from (for example) a DOS flash filesystem? Um... off to the source code. Thanks for the tip. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 20:22:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.twcol.com (unknown [204.210.251.99]) by hub.freebsd.org (Postfix) with ESMTP id 61EB81549D for ; Sun, 16 May 1999 20:21:34 -0700 (PDT) (envelope-from dzerkel@columbus.rr.com) Received: from columbus.rr.com (dhcp219142.columbus.rr.com [208.169.219.142]) by storm.twcol.com (8.9.1/8.9.1) with ESMTP id XAA16797 for ; Sun, 16 May 1999 23:26:36 -0400 (EDT) Message-ID: <373F8B41.4B6D240B@columbus.rr.com> Date: Sun, 16 May 1999 23:21:38 -0400 From: "Danny J. Zerkel" Organization: Zerkular Software X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: Russian, ru, en MIME-Version: 1.0 To: FreeBSD Current Subject: Re: Different SCSI probe behavior References: <373EF0B7.60FE8868@camtech.com.au> <199905161859.MAA65851@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Interesting that this should come up. I'm getting timeouts also, but not on aha. (da1:bt0:0:1:0): CCB 0xc549d680 - timed out bt0: No longer in timeout (sa0:bt0:0:3:0): READ(06). CDB: 8 0 0 28 0 0 (sa0:bt0:0:3:0): UNIT ATTENTION asc:29,0 (sa0:bt0:0:3:0): Power on, reset, or bus device reset occurred (da1:bt0:0:1:0): CCB 0xc549ccc0 - timed out bt0: No longer in timeout (sa0:bt0:0:3:0): WRITE(06). CDB: a 0 0 28 0 0 (sa0:bt0:0:3:0): UNIT ATTENTION asc:29,0 (sa0:bt0:0:3:0): Power on, reset, or bus device reset occurred It seems that if I have tings happening on both a hard disk and the tape drive, I get these kinds of timeouts. I just tried to do a backup with "tar cvb 20 / /usr" and it died after 3 or so blocks with: Device not configured. I can read those blocks back off the tape, just fine. The tape drive was working before cam, but I was out of the country and offline March and April, so I don't entirely know when it stopped. I am running stable as of Sunday morning. Note: this is an ASUS-P2B-DS, the Adaptec controller is on the mother board, but won't handle more than a couple fast-scsi devices. I've got 4. So I'm still using my old Buslogic board, that all the scsi-2 devices were connected to and working fine before the new motherboard. Ideas? Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-STABLE #2: Sun May 16 00:13:44 EDT 1999 dzerkel@zoomer:/usr/src/sys/compile/zoomer Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 134217728 (131072K bytes) avail memory = 127467520 (124480K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02e9000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x02 on pci0.4.3 ahc0: rev 0x00 int a irq 19 on pci0.6.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs bt0: rev 0x00 int b irq 16 on pci0.9.0 bt0: BT-946C FW Rev. 4.24 Narrow SCSI Host Adapter, SCSI ID 7, 100 CCBs xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x64 int a irq 18 on pci0.10.0 xl0: Ethernet address: 00:50:04:60:70:70 xl0: autoneg complete, link status good (half-duplex, 10Mbps) fxp0: rev 0x05 int a irq 17 on pci0.11 .0 fxp0: Ethernet address 00:a0:c9:e5:00:19 Probing for devices on PCI bus 1: vga0: rev 0x01 int a irq 16 on pci1.0.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <4 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 flags 0x10 on isa sio1: type 16550A pca0 on motherboard pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Checking for GUS Plug-n-Play ... No Plug-n-Play devices were found gus0 at 0x220 irq 11 drq 1 flags 0x105 on isa snd0: snd0: apm0 on isa apm: found APM BIOS version 1.2 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 SMP: AP CPU #1 Launched! sa0 at bt0 bus 0 target 3 lun 0 sa0: Removable Sequential Access SCSI-2 device bt0: bt_cmd: Timeout waiting for command (d) to complete. bt0: status = 0x10, intstat = 0x81, rlen 33 bt0: btfetchtransinfo - Inquire Setup Info Failed 3c sa0: 3.300MB/s transfers da1 at bt0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2069MB (4238640 512 byte sectors: 255H 63S/T 263C) da2 at bt0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) changing root device to da0s2a cd0 at bt0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.545MB/s transfers (4.545MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present -- Danny J. Zerkel "Sursum ad Absurdum" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 20:39:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 247E214C1E for ; Sun, 16 May 1999 20:39:41 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id UAA20291 for ; Sun, 16 May 1999 20:38:50 -0700 (PDT) Date: Sun, 16 May 1999 20:38:49 -0700 (PDT) From: Annelise Anderson Reply-To: Annelise Anderson To: freebsd-current@freebsd.org Subject: pccard 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 I installed the April 13 -current snap on my laptop, but I can't build a kernel that will run pccards. pcic fails to allocate an IRQ, and the kernel module pcic won't load. I thought April 13 would avoid the newbus problems, but apparently there were problems back then too. A kernel build with -current sources from March 14 or so works, but has other problems (can't run top, ps, w). I tried using /usr/src/sys/pccard from March 14, but this makes no difference. Is there anything I might try to fix this, other than installing an earlier version? Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 16 20:59:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 1F252150D4 for ; Sun, 16 May 1999 20:59:50 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id XAA18931; Sun, 16 May 1999 23:59:49 -0400 (EDT) Message-ID: <19990516235949.A18232@netmonger.net> Date: Sun, 16 May 1999 23:59:49 -0400 From: Christopher Masto To: Assar Westerlund , current@FreeBSD.ORG Subject: Re: zzz crashing in current OR inthand_remove not removing handlers properly References: <5lr9ogzaqf.fsf@assaris.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <5lr9ogzaqf.fsf@assaris.sics.se>; from Assar Westerlund on Mon, May 17, 1999 at 04:33:12AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 17, 1999 at 04:33:12AM +0200, Assar Westerlund wrote: > Hi, on a -current from around a week ago `zzz' always managed to crash > my machine. The relevant parts from the panic and the backtrace are > included below. > > It seems that the cause of this was a stray interrupt was arriving > after having unloaded the driver. For some reason it wasn't handled > by isa_strayintr, and the reason for that was that inthand_remove > didn't manage to remove the interrupt (and get it replaced by the > stray function) correctly. After applying the patch at the end of > this mail I can once again sleep my laptop succesfully. Wow. I think that's actually done the trick. Not only can I suspend, but I can now remove my 3C589 without a panic. ... well, I just managed to lock up the machine.. but I think that was from a missed remove event. I must have lost that polling patch somewhere along the way. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- 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 Sun May 16 23:55:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from spawn.nectar.cc (gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id C3EFA14C38 for ; Sun, 16 May 1999 23:55:16 -0700 (PDT) (envelope-from nectar@nectar.cc) Received: from spawn.nectar.cc (localhost [127.0.0.1]) by spawn.nectar.cc (Postfix) with ESMTP id C80061F33; Mon, 17 May 1999 01:54:37 -0500 (CDT) X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.cc/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.cc/nectar-dh-dss.txt From: Jacques Vidrine To: Poul-Henning Kamp Cc: van.woerkom@netcologne.de, toasty@home.dragondata.com, current@FreeBSD.ORG In-reply-to: <544.926851664@critter.freebsd.dk> References: <544.926851664@critter.freebsd.dk> Subject: Re: -current page fault at 0xdeadc0de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 May 1999 01:54:37 -0500 Message-Id: <19990517065437.C80061F33@spawn.nectar.cc> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 May 1999 at 12:47, Poul-Henning Kamp wrote: > This is by intention: > > cd /sys/kern > grep -i deadc0de * > kern_malloc.c:#define WEIRD_ADDR 0xdeadc0de For those who like such factoids, AIX uses 0xdeadbeef similarly for uninitialized data. Prior to FreeBSD 2.1.0, we used 0xdeedbeef as well, but that was changed and accompanied by this cute log message: revision 1.11 date: 1995/04/16 11:25:15; author: davidg; state: Exp; lines: +3 -3 Make vegetarian and animal rights people happy and use 0xdeadc0de instead of 0xdeadbeef as the fill pattern. Decreased MAX_COPY to 64 (256 was a bit overzealous in most cases). Jacques Vidrine / n@nectar.cc / nectar@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 May 17 0:31:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 7BC5A150D7 for ; Mon, 17 May 1999 00:31:10 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id JAA29838; Mon, 17 May 1999 09:31:09 +0200 (CEST) (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 JAA02762; Mon, 17 May 1999 09:31:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: current@freebsd.org Subject: Re: sys/types.h rev. 1.33 breaks ps etc. on alpha In-reply-to: Your message of "Sun, 16 May 1999 13:39:47 PDT." Date: Mon, 17 May 1999 09:31:08 +0200 Message-ID: <2760.926926268@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , John Polstra writes: >Revision 1.33 of src/sys/types.h, which changed dev_t to a void * in >the kernel, breaks ps and a bunch of other things on the alpha. >Since dev_t now has a different size in the kernel than in userland, >ps and friends get a "proc size mismatch". Uhm... Ahh... change #define udev_t dev_t to typedef void *dev_t; and tell me how much that breaks... -- 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 Mon May 17 0:39:11 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 A0C1415409; Mon, 17 May 1999 00:38:52 -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 2.12 #1) id 10jHz7-0009yu-00; Mon, 17 May 1999 09:38:49 +0200 From: Sheldon Hearn To: adrian@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: PR 10570 - patch In-reply-to: Your message of "Sat, 15 May 1999 23:25:30 +0800." <19990515152530.3802.qmail@ewok.creative.net.au> Date: Mon, 17 May 1999 09:38:49 +0200 Message-ID: <38371.926926729@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 May 1999 23:25:30 +0800, adrian@freebsd.org wrote: > I sent in a patch to PR 10570 a couple days ago, after quite a bit of > testing (and catching up on email while changing countries..) Next time, you might want to add something like "The PR addresses panics when deleting many routes on a single interface" so that people have at least a hint as to what it's about. Otherwise, it's quite unlikely that the right people will look up your PR. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 0:55:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id D3DCB151E4 for ; Mon, 17 May 1999 00:55:08 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup3-62.iptelecom.net.ua [212.42.69.253]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA20928; Mon, 17 May 1999 10:57:00 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id KAA01779; Mon, 17 May 1999 10:54:48 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <373FCB47.7B47AB70@altavista.net> Date: Mon, 17 May 1999 10:54:47 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: "Gary D. Margiotta" Cc: current@FreeBSD.ORG Subject: Re: Building ports... References: Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Gary D. Margiotta" wrote: > any given port.  It then tells me the following: > > fetch: illegal option -- A It seems that you have outdated fetch - update your sources (via cvsup or any other way)  and then do following: # cd /usr/src/lib/libfetch/ # make all install clean # cd /usr/src/usr.bin/fetch/ # make all install clean   Regards, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 1:47:42 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 94513154EE for ; Mon, 17 May 1999 01:47:36 -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 JAA49134; Mon, 17 May 1999 09:47:26 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 May 1999 09:47:26 +0100 (BST) From: Doug Rabson To: Mike Smith Cc: Bob Bishop , "Carlos C. Tapang" , current@freebsd.org Subject: Re: FBSDBOOT.EXE In-Reply-To: <199905161955.MAA07783@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 Sun, 16 May 1999, Mike Smith wrote: > > Hi, > > > > At 15:22 11/05/99 -0700, you wrote: > > >Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF. > > >If anybody else needs it, please let me know and I'll see what I can do for > > >you. > > > > I'm going to have a use for it RSN > > It doesn't work. Don't use it. You need to reboot the system to > restore various vectors that DOS destroys. Please see the previous > threads on this topic, especially anything from Robert Nordier. Would it be possible to add a driver to config.sys which could record the various vectors or is that too late? -- 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 Mon May 17 1:52: 9 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 CB4FF154EE for ; Mon, 17 May 1999 01:52:04 -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 JAA50242; Mon, 17 May 1999 09:52:52 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 May 1999 09:52:52 +0100 (BST) From: Doug Rabson To: Annelise Anderson Cc: freebsd-current@freebsd.org Subject: Re: pccard status? 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, 16 May 1999, Annelise Anderson wrote: > I installed the April 13 -current snap on my laptop, but I > can't build a kernel that will run pccards. pcic fails to > allocate an IRQ, and the kernel module pcic won't load. > > I thought April 13 would avoid the newbus problems, but > apparently there were problems back then too. > > A kernel build with -current sources from March 14 or so > works, but has other problems (can't run top, ps, w). > > I tried using /usr/src/sys/pccard from March 14, but this > makes no difference. > > Is there anything I might try to fix this, other than > installing an earlier version? I think today's current works quite well on laptops (it works for me anyway). -- 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 Mon May 17 1:53:33 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 1F36D154EE for ; Mon, 17 May 1999 01:53:28 -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 JAA50140; Mon, 17 May 1999 09:50:42 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 May 1999 09:50:42 +0100 (BST) From: Doug Rabson To: Poul-Henning Kamp Cc: John Polstra , current@freebsd.org Subject: Re: sys/types.h rev. 1.33 breaks ps etc. on alpha In-Reply-To: <2760.926926268@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 Mon, 17 May 1999, Poul-Henning Kamp wrote: > > In message , John Polstra writes: > >Revision 1.33 of src/sys/types.h, which changed dev_t to a void * in > >the kernel, breaks ps and a bunch of other things on the alpha. > >Since dev_t now has a different size in the kernel than in userland, > >ps and friends get a "proc size mismatch". > > Uhm... Ahh... > > change > > #define udev_t dev_t > > to > > typedef void *dev_t; > > and tell me how much that breaks... If we define udev_t as a uintptr_t then they will both be the same size. -- 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 Mon May 17 2:13:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 5CEBF14C4B; Mon, 17 May 1999 02:13:08 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.2/8.8.8) id KAA43515; Mon, 17 May 1999 10:13:04 +0100 (BST) (envelope-from joe) Date: Mon, 17 May 1999 10:13:04 +0100 From: Josef Karthauser To: Studded Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: [Fwd: Re: Anybody actually using gigabit ethernet?] Message-ID: <19990517101304.A32313@pavilion.net> References: <373DAD38.7C739B3D@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <373DAD38.7C739B3D@gorean.org>; from Studded on Sat, May 15, 1999 at 10:22:00AM -0700 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 15, 1999 at 10:22:00AM -0700, Studded wrote: > > How about: > > tcp_extensions="NO" # Set to Yes to turn on RFC1323 extensions > > That would match existing style and be a lot more clear. I can submit a PR > if anyone thinks that's really necessary... I think that this is a good idea. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 2:25:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from fgw2.netvalue.fr (cegetel-gw.netvalue.fr [195.115.44.161]) by hub.freebsd.org (Postfix) with ESMTP id 776AA14C58 for ; Mon, 17 May 1999 02:25:20 -0700 (PDT) (envelope-from erwan@netvalue.fr) Received: (from bin@localhost) by fgw2.netvalue.fr (8.9.3/8.8.8) id LAA23060 for ; Mon, 17 May 1999 11:25:19 +0200 (CEST) (envelope-from erwan@netvalue.fr) X-Authentication-Warning: fgw2.netvalue.fr: bin set sender to using -f Received: from (etoile.netvalue.fr [192.168.1.11]) by fgw2.netvalue.fr via smap (V2.1) id xma023056; Mon, 17 May 99 11:25:09 +0200 Received: from netvalue.fr ([192.168.1.100]) by etoile.netvalue.fr (Netscape Messaging Server 3.6) with ESMTP id AAA20FE for ; Mon, 17 May 1999 11:25:08 +0200 Message-ID: <373FE057.FAE8FC5B@netvalue.fr> Date: Mon, 17 May 1999 11:24:39 +0200 From: Erwan Arzur Organization: NetValue S.A. X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en, fr-FR MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: xl0: couldn't map interrupt ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently cvsupped (as of today, and since around may 10) -current kernels fail to attach my 3C905-TX nic. I did not find any big difference between the current copy of if_xl.c ( $Id: if_xl.c,v 1.37 1999/05/09 17:07:06) and a copy dated 05/05 ( $Id: if_xl.c,v 1.100 1999/05/05 15:01:27) that was working flawlessly. I think the problem lies in pci_map_int, but this code is well beyond my hacking capacities :-) Well, here is the result of booting -v with a -current kernel : dev=0xac15, revid=0x01 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=11 found-> vendor=0x104c, dev=0xac15, revid=0x01 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=11 found-> vendor=0x8086, dev=0x7110, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000ffa0, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=11 map[0]: type 4, range 32, base 0000ece0, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x124b, revid=0x01 class=06-04-80, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 pci0: on pcib0 chip0: at device 0.0 on pci0 vga-pci0: irq 11 at device 2.0 on pci0 chip1: irq 11 at device 3.0 on pci0 chip2: irq 11 at device 3.1 on pci0 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 pc i0 uhci0: USB version 1.0, chip rev. 1 usb0: on uhci0 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: at device 7.3 on pci0 intpm0: I/O mapped 840 intpm0: intr IRQ 9 enabled revision 0 intsmb0: smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 800 pcib1: at device 17.0 on pci0 found-> vendor=0x1095, dev=0x0646, revid=0x03 class=01-01-8f, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000fcf8, size 3 map[1]: type 4, range 32, base 0000fcf0, size 2 map[2]: type 4, range 32, base 0000fce0, size 3 map[3]: type 4, range 32, base 0000fcd8, size 2 map[4]: type 4, range 32, base 0000fcc0, size 4 found-> vendor=0x9004, dev=0x6078, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000f800, size 8 map[1]: type 1, range 32, base fdfff000, size 12 found-> vendor=0x10b7, dev=0x9050, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000fc80, size 6 pci1: on pcib1 ata-pci1: irq 10 at device 5.0 on pci1 ata-pci1: Busmastering DMA supported ahc0: irq 10 at device 7.0 on pci1 ahc0: Reading SEEPROM...checksum error ahc0: No SEEPROM available. ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs ahc0: Host Adapter Bios disabled. Using default SCSI device parameters ahc0: Downloading Sequencer Program... 409 instructions downloaded xl0: <3Com 3c905-TX Fast Etherlink XL> irq 10 at device 8.0 on pci1 pci_map_int: can't allocate interrupt xl0: couldn't map interrupt 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 <...> Thanks for any help ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 2:28: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id BABC414BF4 for ; Mon, 17 May 1999 02:27:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id LAA00690; Mon, 17 May 1999 11:27:56 +0200 (CEST) (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 LAA03170; Mon, 17 May 1999 11:27:55 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Doug Rabson Cc: John Polstra , current@freebsd.org Subject: Re: sys/types.h rev. 1.33 breaks ps etc. on alpha In-reply-to: Your message of "Mon, 17 May 1999 09:50:42 BST." Date: Mon, 17 May 1999 11:27:55 +0200 Message-ID: <3168.926933275@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try it and tell me if it works... In message , Doug Rabson writes: >On Mon, 17 May 1999, Poul-Henning Kamp wrote: > >> >> In message , John Polstra writes: >> >Revision 1.33 of src/sys/types.h, which changed dev_t to a void * in >> >the kernel, breaks ps and a bunch of other things on the alpha. >> >Since dev_t now has a different size in the kernel than in userland, >> >ps and friends get a "proc size mismatch". >> >> Uhm... Ahh... >> >> change >> >> #define udev_t dev_t >> >> to >> >> typedef void *dev_t; >> >> and tell me how much that breaks... > >If we define udev_t as a uintptr_t then they will both be the same size. > >-- >Doug Rabson Mail: dfr@nlsystems.com >Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > -- 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 Mon May 17 2:48:56 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 A926C14BC9 for ; Mon, 17 May 1999 02:48:53 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA24787; Mon, 17 May 1999 11:48:45 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905170948.LAA24787@freebsd.dk> Subject: Re: IDE strangeness In-Reply-To: from Brian Feldman at "May 6, 1999 10: 4:19 pm" To: green@unixhelp.org (Brian Feldman) Date: Mon, 17 May 1999 11:48:45 +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 Brian Feldman wrote: > I'm having two problems with IDE nowadays. > > 1. ATA doesn't work with LS-120. That's not new. But ATA does seem to crash on > me, and there's no dump() so I can't figure out why. Good news is that I've gotten ahold of a LS120 drive, so I can test this now. Bad news is that it has stopped working on my ZIP drive too :( Something must have been screwed up since the newbus import, either in my driver (I feel at risk saying that it is not likely), or something else. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 3:17:50 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 7FE0414A2F for ; Mon, 17 May 1999 03:17:47 -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 LAA56258; Mon, 17 May 1999 11:14:49 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 May 1999 11:14:49 +0100 (BST) From: Doug Rabson To: Poul-Henning Kamp Cc: John Polstra , current@freebsd.org Subject: Re: sys/types.h rev. 1.33 breaks ps etc. on alpha In-Reply-To: <3168.926933275@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 Mon, 17 May 1999, Poul-Henning Kamp wrote: > > Try it and tell me if it works... Not good so far. In my test kernel which defines udev_t as uintptr_t, sh faults when init tries to go multiuser. -- 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 Mon May 17 3:34:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 457A0150F1 for ; Mon, 17 May 1999 03:33:28 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id MAA01102; Mon, 17 May 1999 12:33:27 +0200 (CEST) (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 MAA11517; Mon, 17 May 1999 12:33:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Doug Rabson Cc: John Polstra , current@freebsd.org Subject: Re: sys/types.h rev. 1.33 breaks ps etc. on alpha In-reply-to: Your message of "Mon, 17 May 1999 11:14:49 BST." Date: Mon, 17 May 1999 12:33:26 +0200 Message-ID: <11515.926937206@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Doug Rabson writes: >On Mon, 17 May 1999, Poul-Henning Kamp wrote: > >> >> Try it and tell me if it works... > >Not good so far. In my test kernel which defines udev_t as uintptr_t, sh >faults when init tries to go multiuser. I'm worried about the sign extension from 32 to 64 bits... -- 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 Mon May 17 3:45:41 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 7D79414CA5 for ; Mon, 17 May 1999 03:45:37 -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 LAA56344; Mon, 17 May 1999 11:42:52 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 May 1999 11:42:52 +0100 (BST) From: Doug Rabson To: Poul-Henning Kamp Cc: John Polstra , current@freebsd.org Subject: Re: sys/types.h rev. 1.33 breaks ps etc. on alpha In-Reply-To: <11515.926937206@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 Mon, 17 May 1999, Poul-Henning Kamp wrote: > In message , Doug > Rabson writes: > >On Mon, 17 May 1999, Poul-Henning Kamp wrote: > > > >> > >> Try it and tell me if it works... > > > >Not good so far. In my test kernel which defines udev_t as uintptr_t, sh > >faults when init tries to go multiuser. > > I'm worried about the sign extension from 32 to 64 bits... I haven't been able to diagnose the problem yet but I don't think its sign extension since uintptr_t is an unsigned type. -- 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 Mon May 17 3:47:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 23B2D14CA5 for ; Mon, 17 May 1999 03:47:31 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id MAA01195; Mon, 17 May 1999 12:47:31 +0200 (CEST) (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 MAA22169; Mon, 17 May 1999 12:47:23 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Doug Rabson Cc: John Polstra , current@freebsd.org Subject: Re: sys/types.h rev. 1.33 breaks ps etc. on alpha In-reply-to: Your message of "Mon, 17 May 1999 11:42:52 BST." Date: Mon, 17 May 1999 12:47:23 +0200 Message-ID: <22167.926938043@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Doug Rabson writes: >On Mon, 17 May 1999, Poul-Henning Kamp wrote: > >> In message , Doug >> Rabson writes: >> >On Mon, 17 May 1999, Poul-Henning Kamp wrote: >> > >> >> >> >> Try it and tell me if it works... >> > >> >Not good so far. In my test kernel which defines udev_t as uintptr_t, sh >> >faults when init tries to go multiuser. >> >> I'm worried about the sign extension from 32 to 64 bits... > >I haven't been able to diagnose the problem yet but I don't think its sign >extension since uintptr_t is an unsigned type. Lots of places fiddle minor/major in ints... -- 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 Mon May 17 4:10:39 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 017F314E93 for ; Mon, 17 May 1999 04:10:35 -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 MAA56424; Mon, 17 May 1999 12:07:51 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 May 1999 12:07:51 +0100 (BST) From: Doug Rabson To: Poul-Henning Kamp Cc: John Polstra , current@freebsd.org Subject: Re: sys/types.h rev. 1.33 breaks ps etc. on alpha In-Reply-To: <22167.926938043@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 Mon, 17 May 1999, Poul-Henning Kamp wrote: > In message , Doug > Rabson writes: > >On Mon, 17 May 1999, Poul-Henning Kamp wrote: > > > >> In message , Doug > >> Rabson writes: > >> >On Mon, 17 May 1999, Poul-Henning Kamp wrote: > >> > > >> >> > >> >> Try it and tell me if it works... > >> > > >> >Not good so far. In my test kernel which defines udev_t as uintptr_t, sh > >> >faults when init tries to go multiuser. > >> > >> I'm worried about the sign extension from 32 to 64 bits... > > > >I haven't been able to diagnose the problem yet but I don't think its sign > >extension since uintptr_t is an unsigned type. > > Lots of places fiddle minor/major in ints... This alternative patch seems to fix things (and its probably more correct). Index: sys/user.h =================================================================== RCS file: /home/ncvs/src/sys/sys/user.h,v retrieving revision 1.20 diff -u -r1.20 user.h --- user.h 1999/01/26 02:38:11 1.20 +++ user.h 1999/05/17 10:55:26 @@ -74,7 +74,7 @@ pid_t e_ppid; /* parent process id */ pid_t e_pgid; /* process group id */ short e_jobc; /* job control counter */ - dev_t e_tdev; /* controlling tty dev */ + udev_t e_tdev; /* controlling tty dev */ pid_t e_tpgid; /* tty process group id */ struct session *e_tsess; /* tty session pointer */ #define WMESGLEN 7 Index: kern/kern_proc.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_proc.c,v retrieving revision 1.50 diff -u -r1.50 kern_proc.c --- kern_proc.c 1999/05/11 19:54:29 1.50 +++ kern_proc.c 1999/05/17 10:55:17 @@ -443,7 +443,7 @@ if ((p->p_flag & P_CONTROLT) && (ep->e_sess != NULL) && ((tp = ep->e_sess->s_ttyp) != NULL)) { - ep->e_tdev = tp->t_dev; + ep->e_tdev = dev2udev(tp->t_dev); ep->e_tpgid = tp->t_pgrp ? tp->t_pgrp->pg_id : NO_PID; ep->e_tsess = tp->t_session; } else -- 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 Mon May 17 4:19:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 26D6615061 for ; Mon, 17 May 1999 04:19:33 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id NAA01393; Mon, 17 May 1999 13:19:33 +0200 (CEST) (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 NAA22325; Mon, 17 May 1999 13:19:32 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Doug Rabson Cc: John Polstra , current@freebsd.org Subject: Re: sys/types.h rev. 1.33 breaks ps etc. on alpha In-reply-to: Your message of "Mon, 17 May 1999 12:07:51 BST." Date: Mon, 17 May 1999 13:19:32 +0200 Message-ID: <22323.926939972@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So this is in addition to the uintptr_t definition of udev_t or without it ? Either way, I'll be in Rome for the rest of the week (in all likelyhood that is, the usual last-second gottchas have not been resolved yet :-) so I will not be able to test it myself. So if it works commit it. (If anybody in Rome wants to arrange a FreeBSD pow-wow one of the evenings this week let me know, I'll read email until tomorrow morning) Poul-Henning In message , Doug Rabson writes: >This alternative patch seems to fix things (and its probably more >correct). > >Index: sys/user.h >=================================================================== >RCS file: /home/ncvs/src/sys/sys/user.h,v >retrieving revision 1.20 >diff -u -r1.20 user.h >--- user.h 1999/01/26 02:38:11 1.20 >+++ user.h 1999/05/17 10:55:26 >@@ -74,7 +74,7 @@ > pid_t e_ppid; /* parent process id */ > pid_t e_pgid; /* process group id */ > short e_jobc; /* job control counter */ >- dev_t e_tdev; /* controlling tty dev */ >+ udev_t e_tdev; /* controlling tty dev */ > pid_t e_tpgid; /* tty process group id */ > struct session *e_tsess; /* tty session pointer */ > #define WMESGLEN 7 >Index: kern/kern_proc.c >=================================================================== >RCS file: /home/ncvs/src/sys/kern/kern_proc.c,v >retrieving revision 1.50 >diff -u -r1.50 kern_proc.c >--- kern_proc.c 1999/05/11 19:54:29 1.50 >+++ kern_proc.c 1999/05/17 10:55:17 >@@ -443,7 +443,7 @@ > if ((p->p_flag & P_CONTROLT) && > (ep->e_sess != NULL) && > ((tp = ep->e_sess->s_ttyp) != NULL)) { >- ep->e_tdev = tp->t_dev; >+ ep->e_tdev = dev2udev(tp->t_dev); > ep->e_tpgid = tp->t_pgrp ? tp->t_pgrp->pg_id : NO_PID; > ep->e_tsess = tp->t_session; > } else -- 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 Mon May 17 6:20:38 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 4B9F615140 for ; Mon, 17 May 1999 06:20:07 -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 OAA56596; Mon, 17 May 1999 14:16:51 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 May 1999 14:16:51 +0100 (BST) From: Doug Rabson To: Poul-Henning Kamp Cc: John Polstra , current@freebsd.org Subject: Re: sys/types.h rev. 1.33 breaks ps etc. on alpha In-Reply-To: <22323.926939972@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 Mon, 17 May 1999, Poul-Henning Kamp wrote: > > So this is in addition to the uintptr_t definition of udev_t or > without it ? Its instead of it. The e_tdev field seems to be the only dev_t in the structure and since this code is exporting values to userland, it ought to be converting to udev_t I think. -- 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 Mon May 17 6:21:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 9435414CA5 for ; Mon, 17 May 1999 06:21:28 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA02221; Mon, 17 May 1999 15:21:28 +0200 (CEST) (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 PAA22940; Mon, 17 May 1999 15:21:24 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Doug Rabson Cc: John Polstra , current@freebsd.org Subject: Re: sys/types.h rev. 1.33 breaks ps etc. on alpha In-reply-to: Your message of "Mon, 17 May 1999 14:16:51 BST." Date: Mon, 17 May 1999 15:21:24 +0200 Message-ID: <22938.926947284@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Doug Rabson writes: >On Mon, 17 May 1999, Poul-Henning Kamp wrote: > >> >> So this is in addition to the uintptr_t definition of udev_t or >> without it ? > >Its instead of it. Ok, just wanted to be clear. >The e_tdev field seems to be the only dev_t in the >structure and since this code is exporting values to userland, it ought to >be converting to udev_t I think. Yes, indead it should be udev_t. -- 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 Mon May 17 6:29:44 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 0395F14EE8 for ; Mon, 17 May 1999 06:29:39 -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 OAA56628; Mon, 17 May 1999 14:27:25 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 May 1999 14:27:25 +0100 (BST) From: Doug Rabson To: Poul-Henning Kamp Cc: John Polstra , current@freebsd.org Subject: Re: sys/types.h rev. 1.33 breaks ps etc. on alpha In-Reply-To: <22938.926947284@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 Mon, 17 May 1999, Poul-Henning Kamp wrote: > In message , Doug > Rabson writes: > >On Mon, 17 May 1999, Poul-Henning Kamp wrote: > > > >> > >> So this is in addition to the uintptr_t definition of udev_t or > >> without it ? > > > >Its instead of it. > > Ok, just wanted to be clear. > > >The e_tdev field seems to be the only dev_t in the > >structure and since this code is exporting values to userland, it ought to > >be converting to udev_t I think. > > Yes, indead it should be udev_t. I'll commit the patch then. -- 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 Mon May 17 6:34:39 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 0140814F8E for ; Mon, 17 May 1999 06:34: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 JAA28405; Mon, 17 May 1999 09:34:34 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA38688; Mon, 17 May 1999 09:34:20 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 17 May 1999 09:34:20 -0400 (EDT) To: Erwan Arzur Cc: freebsd-current@freebsd.org Subject: Re: xl0: couldn't map interrupt ? In-Reply-To: <373FE057.FAE8FC5B@netvalue.fr> References: <373FE057.FAE8FC5B@netvalue.fr> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14144.6406.402515.478941@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Erwan Arzur writes: > Recently cvsupped (as of today, and since around may 10) -current > kernels fail to attach my 3C905-TX nic. <...> > ata-pci1: irq 10 at device 5.0 on pci1 > ata-pci1: Busmastering DMA supported <..> > xl0: <3Com 3c905-TX Fast Etherlink XL> irq 10 at device 8.0 on pci1 > pci_map_int: can't allocate interrupt > xl0: couldn't map interrupt The problem has nothing to do with the xl driver, actually the ata driver is to blame. The ata driver doesn't want to place nice & share IRQs, and by the time the xl driver gets a chance to alloc irq10 the ata driver has reserved it totally. The following should fix it (beware, its against a slightly less-than-current version of ata-all.c; should it fail to apply, just replace the RF_SHAREABLE arguments to bus_alloc_resource with RF_SHAREABLE | RF_ACTIVE in ata_pciattach(). S=F8ren's told me that he'll be fixing this in his next commit. Drew -----------------------------------------------------------------------= ------- Andrew Gallatin, Sr Systems Programmer=09http://www.cs.duke.edu/~gallat= in Duke University=09=09=09=09Email: gallatin@cs.duke.edu Department of Computer Science=09=09Phone: (919) 660-6590 Index: /sys/dev/ata/ata-all.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.11 diff -u -b -B -r1.11 ata-all.c --- ata-all.c 1999/04/22 08:07:44 1.11 +++ ata-all.c 1999/05/16 00:40:13 @@ -312,7 +312,8 @@ int rid =3D 0; void *ih; =20 - irq =3D bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0, ~0,1,= RF_ACTIVE); + irq =3D bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0, ~0,1,= + RF_SHAREABLE | RF_ACTIVE); if (sysctrl) bus_setup_intr(dev, irq, promise_intr, scp, &ih); else @@ -337,7 +338,8 @@ int rid =3D 0; void *ih; =20 - irq =3D bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0, ~0,1,= RF_ACTIVE); + irq =3D bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0, ~0,1,= + RF_SHAREABLE | RF_ACTIVE); if (!sysctrl) bus_setup_intr(dev, irq, ataintr, scp, &ih); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 6:40: 9 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 D58731500E for ; Mon, 17 May 1999 06:40:06 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id PAA25213; Mon, 17 May 1999 15:40:00 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905171340.PAA25213@freebsd.dk> Subject: Re: xl0: couldn't map interrupt ? In-Reply-To: <14144.6406.402515.478941@grasshopper.cs.duke.edu> from Andrew Gallatin at "May 17, 1999 9:34:20 am" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Mon, 17 May 1999 15:40:00 +0200 (CEST) Cc: erwan@netvalue.fr, 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 Andrew Gallatin wrote: > > Erwan Arzur writes: > > Recently cvsupped (as of today, and since around may 10) -current > > kernels fail to attach my 3C905-TX nic. > <...> > > ata-pci1: irq 10 at device 5.0 on pci1 > > ata-pci1: Busmastering DMA supported > > <..> > > xl0: <3Com 3c905-TX Fast Etherlink XL> irq 10 at device 8.0 on pci1 > > pci_map_int: can't allocate interrupt > > xl0: couldn't map interrupt > > The problem has nothing to do with the xl driver, actually the ata > driver is to blame. The ata driver doesn't want to place nice & share > IRQs, and by the time the xl driver gets a chance to alloc irq10 the > ata driver has reserved it totally. The following should fix it > (beware, its against a slightly less-than-current version of > ata-all.c; should it fail to apply, just replace the RF_SHAREABLE > arguments to bus_alloc_resource with RF_SHAREABLE | RF_ACTIVE in > ata_pciattach(). > > Søren's told me that he'll be fixing this in his next commit. Yep, I just have to find the bug that causes LS120 drives to fail, then I have the next update ready, hopefully I get a few hours tonight... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 6:49:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns3.ge.com (ns3.ge.com [192.35.39.22]) by hub.freebsd.org (Postfix) with ESMTP id 083911504E for ; Mon, 17 May 1999 06:49:15 -0700 (PDT) (envelope-from burg@burg.is.ge.com) Received: from thomas.ge.com (thomas-o.ge.com [10.47.28.21]) by ns3.ge.com (8.9.3/8.9.3) with ESMTP id JAA27212; Mon, 17 May 1999 09:49:14 -0400 (EDT) Received: from burg.is.ge.com (burg.is.ge.com [3.19.120.24]) by thomas.ge.com (8.9.3/8.9.3) with ESMTP id JAA29376; Mon, 17 May 1999 09:49:13 -0400 (EDT) Received: (from burg@localhost) by burg.is.ge.com (8.9.1a/8.9.1) id PAA11659; Mon, 17 May 1999 15:37:54 +0200 (MET DST) From: Dick van den Burg MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 17 May 1999 15:37:53 +0200 (MET DST) To: Doug Rabson Cc: Annelise Anderson , freebsd-current@FreeBSD.ORG Subject: Re: pccard status? In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14144.6931.181693.932546@burg.is.ge.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I have not been able to get any modem recognized, although network cards (ed) work ok. The pccard stuff in sio.c seems to be ifdef'd out, but I am not sure I understand whether this code is still necessary ... Dick van den Burg Doug Rabson wrote: > On Sun, 16 May 1999, Annelise Anderson wrote: > > > I installed the April 13 -current snap on my laptop, but I > > can't build a kernel that will run pccards. pcic fails to > > allocate an IRQ, and the kernel module pcic won't load. > > > > I thought April 13 would avoid the newbus problems, but > > apparently there were problems back then too. > > > > A kernel build with -current sources from March 14 or so > > works, but has other problems (can't run top, ps, w). > > > > I tried using /usr/src/sys/pccard from March 14, but this > > makes no difference. > > > > Is there anything I might try to fix this, other than > > installing an earlier version? > > I think today's current works quite well on laptops (it works for me > anyway). > > -- > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 6:58: 2 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 7CADE15562 for ; Mon, 17 May 1999 06:57:56 -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 OAA56726; Mon, 17 May 1999 14:58:20 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 May 1999 14:58:20 +0100 (BST) From: Doug Rabson To: Dick van den Burg Cc: Annelise Anderson , freebsd-current@FreeBSD.ORG Subject: Re: pccard status? In-Reply-To: <14144.6931.181693.932546@burg.is.ge.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, 17 May 1999, Dick van den Burg wrote: > Well, I have not been able to get any modem recognized, although > network cards (ed) work ok. The pccard stuff in sio.c seems to be > ifdef'd out, but I am not sure I understand whether this code is still > necessary ... The sio support will need to wait until Warner Losh commits his changes to clean up the pccard driver. -- 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 Mon May 17 8: 1: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 65F3F14E96 for ; Mon, 17 May 1999 08:00:57 -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 JAA28161; Mon, 17 May 1999 09:00:51 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA22502; Mon, 17 May 1999 09:00:50 -0600 Date: Mon, 17 May 1999 09:00:50 -0600 Message-Id: <199905171500.JAA22502@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Christopher Masto Cc: Assar Westerlund , current@FreeBSD.ORG Subject: Re: zzz crashing in current OR inthand_remove not removing handlers properly In-Reply-To: <19990516235949.A18232@netmonger.net> References: <5lr9ogzaqf.fsf@assaris.sics.se> <19990516235949.A18232@netmonger.net> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi, on a -current from around a week ago `zzz' always managed to crash > > my machine. The relevant parts from the panic and the backtrace are > > included below. > > > > It seems that the cause of this was a stray interrupt was arriving > > after having unloaded the driver. For some reason it wasn't handled > > by isa_strayintr, and the reason for that was that inthand_remove > > didn't manage to remove the interrupt (and get it replaced by the > > stray function) correctly. After applying the patch at the end of > > this mail I can once again sleep my laptop succesfully. > > Wow. I think that's actually done the trick. Not only can I suspend, > but I can now remove my 3C589 without a panic. > > ... well, I just managed to lock up the machine.. but I think that was > from a missed remove event. I must have lost that polling patch > somewhere along the way. If you're polling, it's *REAL* easy to lockup the machine inside the card's interrupt handler, with no chance of it every escaping since the 'poll' can't interrupt the IRQ. The solution is to not poll and to make sure insertion/removal events generate an interrupt which can inform the card's interrupt handlers that there is no more card. (That's one of the main reasons polling is a very bad idea.) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 8:26:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 1BBA9155B1 for ; Mon, 17 May 1999 08:26:46 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id LAA13281; Mon, 17 May 1999 11:26:35 -0400 (EDT) Message-ID: <19990517112634.A12004@netmonger.net> Date: Mon, 17 May 1999 11:26:35 -0400 From: Christopher Masto To: Nate Williams Cc: Assar Westerlund , current@FreeBSD.ORG Subject: Re: zzz crashing in current OR inthand_remove not removing handlers properly References: <5lr9ogzaqf.fsf@assaris.sics.se> <19990516235949.A18232@netmonger.net> <199905171500.JAA22502@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199905171500.JAA22502@mt.sri.com>; from Nate Williams on Mon, May 17, 1999 at 09:00:50AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 17, 1999 at 09:00:50AM -0600, Nate Williams wrote: > > > Hi, on a -current from around a week ago `zzz' always managed to crash > > > my machine. The relevant parts from the panic and the backtrace are > > > included below. > > > > > > It seems that the cause of this was a stray interrupt was arriving > > > after having unloaded the driver. For some reason it wasn't handled > > > by isa_strayintr, and the reason for that was that inthand_remove > > > didn't manage to remove the interrupt (and get it replaced by the > > > stray function) correctly. After applying the patch at the end of > > > this mail I can once again sleep my laptop succesfully. > > > > Wow. I think that's actually done the trick. Not only can I suspend, > > but I can now remove my 3C589 without a panic. > > > > ... well, I just managed to lock up the machine.. but I think that was > > from a missed remove event. I must have lost that polling patch > > somewhere along the way. > > If you're polling, it's *REAL* easy to lockup the machine inside the > card's interrupt handler, with no chance of it every escaping since the > 'poll' can't interrupt the IRQ. Actually, I was not polling, which I thought might have been why pccard didn't notice when I removed my network card. Polling didn't fix that, so I looked elsewhere. It turns out that after a hibernate (but not after a suspend), insert/remove events stop working unless the kernel is compiled with PCIC_RESUME_RESET. With that and Assar's patch, my vaio is reasonably usable. (I hook it up to the ethernet at work, so having to shut down to remove the card or even just suspend is rather tedious.) > The solution is to not poll and to make sure insertion/removal events > generate an interrupt which can inform the card's interrupt handlers > that there is no more card. Fortunately the interrupts do seem to work on this machine. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- 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 Mon May 17 8:51: 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 D27971513B; Mon, 17 May 1999 08:50:56 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:TchqBdy6yTdELF/cnkmeL4P154nPNK8A@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id AAA15643; Tue, 18 May 1999 00:51:00 +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 AAA00483; Tue, 18 May 1999 00:54:51 +0900 (JST) Message-Id: <199905171554.AAA00483@zodiac.mech.utsunomiya-u.ac.jp> To: sos@freebsd.org, dfr@freebsd.org, kato@freebsd.org Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: syscons update - stage 2 snopshot 17 May Date: Tue, 18 May 1999 00:54:50 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is the second snapshot of the stage 2 of syscons update. I placed a set of patches in http://www.freebsd.org/~yokota/syscons-update.17May.tar.gz It is a snopshot of "work-in-progress", and is not complete yet. I would appriciate if you take a look and send me some comments. I am attaching the README file from the patch. Kazu ---------------------------------------------------------------------- Latest syscons update 17 May 1999 Kazutaka YOKOTA, yokota@FreeBSD.ORG 1. Introduction This is a snapshot of work-in-progress. I decided to release this because I am very much behind intended schedule and think it won't benefit us much if I will defer submitting this for public testing until everything is done. This update is still in the middle of active development and is incomplete yet. The main goal of this update is to split syscons source code into manageable chunks and in the process, reorganize some of complicated functions. It also includes some ideas and patches which were submitted to the FreeBSD PR database in the past and have not been integrated into syscons. A bunch of new ioctl commands are also added to syscons and the video driver in order to provide support for accessing frame buffer memory. At the moment the patch is prepared for the i386 and alpha architectures. The patch for the pc98 architecture will follow shortly. There is one other note; some screen savers need minor udpate. It will be provided later. The snapshot also includes a copy of (unfinished) text and some sample code to demonstrate video memory access by the userland program. 2. Applying patch files. There are 9 separate patch files and tar files: alpha.diff alpha-specific patch. devfb.diff Video driver patch. devfb.tar New video driver files. i386.diff i386-specific patch. sys.diff Patch for common kernel files. sys.tar New files in /sys/sys syscons.tar Updated and new syscons source files. kbdcontrol.diff Patch for kbdcontrol. vidcontrol.diff Patch for vidcontrol. They are relative to 4.0-CURRENT around 16 May 1999. They update and overwrite quite a few files. Please make backup first! Affected files are: alpha.diff /sys/alpha/alpha/cons.c /sys/alpha/conf/files.alpha /sys/alpha/conf/options.alpha /sys/alpha/include/cons.h /sys/alpha/include/console.h devfb.diff /sys/dev/fb/fb.c /sys/dev/fb/fbreg.c /sys/dev/fb/splash.c /sys/dev/fb/splashreg.c /sys/dev/fb/vgareg.c devfb.tar /sys/dev/fb/vga.c NEW FILE syscons.tar /sys/dev/syscons/syscons.c /sys/dev/syscons/syscons.h /sys/dev/syscons/scvidctl.c /sys/dev/syscons/scvesactl.c /sys/dev/syscons/schistory.c NEW FILE /sys/dev/syscons/scmouse.c NEW FILE /sys/dev/syscons/scvgarndr.c NEW FILE /sys/dev/syscons/scvtb.c NEW FILE i386.diff /sys/i386/conf/LINT /sys/i386/conf/files.i386 /sys/i386/conf/options.i386 /sys/i386/i386/cons.c /sys/i386/i386/cons.h /sys/i386/isa/pcvt/pcvt_drv.c /sys/i386/isa/vesa.c /sys/i386/include/console.h sys.diff /sys/isa/sio.c /sys/isa/syscons_isa.c /sys/isa/vga_isa.c /sys/sys/fbio.h sys.tar /sys/sys/kbio.h NEW FILE /sys/sys/consio.h NEW FILE vidcontrol.diff /usr/src/usr.sbin/vidcontrol/vidcontrol.c kbdcontrol.diff /usr/src/usr.sbin/kbdcontrol/lex.h /usr/src/usr.sbin/kbdcontrol/lex.l /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c Apply them as follows (assuming they are in /tmp): cd /sys patch < /tmp/sys.diff tar xvf /tmp/sys.tar cd i386 patch < /tmp/i386.diff cd ../alpha patch < /tmp/alpha.diff cd ../dev/fb patch < /tmp/devfb.diff tar xvf /tmp/devfb.tar cd ../syscons tar xvf /tmp/syscons.tar cd /usr/src/usr.sbin/vidcontrol patch < /tmp/vidcontrol.diff cd ../kbdcontrol patch < /tmp/kbdcontrol.diff Then, before you rebuild vidcontrol and kbdcontrol, cp /sys/`uname -m`/include/console.h /usr/include/machine 3. Rough descriptions on modifications 1) Syscons update: - Many static variables are moved to the softc structure. - History buffer (back-scroll buffer) management functions are moved to a new file, schistory.c. - Sysmouse management functions are moved to a new file, scmouse.c. - Created a set of functions to access the virtual terminal buffer (scvtb.c). - Added a new key function, PREV. When this key is pressed, the vty immediately before the current vty will become foreground. Analogue to PREV, which is usually assigned to the PrntScrn key. PR: kern/10113 Submitted by: Christian Weisgerber - Added a new ioctl: VT_GETINDEX. - Modified the console input function sccngetc() so that it handles function keys properly. - Reorganized the screen update routine. - Rendering functions (scvgarndr.c). - VT switching code is reorganized. It now should be slightly more robust than before. - Added the DEVICE_RESUME function so that syscons no longer hooks the APM resume event directly. - New kernel configuration options: options SC_NO_CUTPASTE options SC_NO_FONT_LOADING options SC_NO_HISTORY options SC_NO_SYSMOUSE Various parts of syscons can be omitted so that the kernel size is reduced. Use the above kernel configuration options to selectively disable parts of syscons. options SC_PIXEL_MODE Made the VESA 800x600 mode an option, rather than a standard part of syscons. This mode is useful on some laptop computers, but less so on most other systems, and it adds substantial amount of code to syscons. If the above kernel configuration option is NOT defined, you can reduce the kernel size a lot. options SC_DISABLE_DDBKEY Disables the `debug' key combination. It will prevent the user from entering DDB by pressing the key combination. DDB will still be invoked when the kernel panics or hits a break point if it is included in the kernel. options SC_ALT_MOUSE_IMAGE Inverse the character cell at the mouse cursor position in the text console, rather than drawing an arrow on the screen. This will reduce the system load a lot. Submitted by: Nick Hibma (n_hibma@FreeBSD.ORG) options SC_DFLT_FONT makeoptions "SC_DFLT_FONT=_font_name_" Include the named font as the default font of syscons. Available fonts are: iso, iso2, koi8-r, cp437, cp850, cp865 and cp866. 16- line, 14-line and 8-line font data will be compiled in. This option will replace the existing STD8X16FONT option, which loads 16- line font data only. 2) Video driver update: - The VGA driver is split into /sys/dev/fb/vga.c and /sys/isa/vga_isa.c. - The video driver provides a set of ioctl commands to manipulate the frame buffer. - New kernel configuration options: options "VGA_WIDTH90" Enables 90 column modes: 90x25, 90x30, 90x43, 90x50, 90x60. These modes are mot always supported by the video card. PR: i386/7510 Submitted by: kbyanc@freedomnet.com and alexv@sui.gda.itesm.mx. 3) Other changes - The header file machine/console.h is reorganized; it has been placed in the architecture-dependent part of the source tree while much of the stuff is architecture-neutral. Its contents is now split into sys/fbio.h, sys/kbio.h (a new file) and sys/consio.h (another new file). machine/console.h is still maintained for compatibility reasons; it simply includes the above three files (strange arrangement indeed that a machine dependent header file is including architecture-neutral headers! but...). - Kernel console selection/installation routines are fixed and slightly rebumped so that it should now be possible to switch between the interanl kernel console (sc or vt) and a remote kernel console (sio) again, as it was in 2.x, 3.0 and 3.1. ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 9: 1:16 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 81D291513B for ; Mon, 17 May 1999 09:01:09 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id SAA25465 for current@freebsd.org; Mon, 17 May 1999 18:01:09 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905171601.SAA25465@freebsd.dk> Subject: UPDATE7: ATA/ATAPI driver new version available. To: current@freebsd.org Date: Mon, 17 May 1999 18:01:08 +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 Seventh update to the new ATA/ATAPI driver: Fixed problems: LS120 drives currupted data. The workaround for drives not supporting upto 64K transfers has been reworked. It works now both on LS120 & ZIP drives. ISA only configs wont compile. Fixed. The ATA driver wont share interrupts. Fixed. The "unwanted interrupt" warning gave wrong controller. Another lun<>unit messup from the newbus integration. 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 Mon May 17 9:16:24 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 16F3D14E92 for ; Mon, 17 May 1999 09:16:22 -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 MAA02501; Mon, 17 May 1999 12:16:11 -0400 (EDT) (envelope-from wollman) Date: Mon, 17 May 1999 12:16:11 -0400 (EDT) From: Garrett Wollman Message-Id: <199905171616.MAA02501@khavrinen.lcs.mit.edu> To: John Polstra Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: Heads up! config(8) changes.. In-Reply-To: References: <199905150241.MAA11478@godzilla.zeta.org.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cleaning up some old mail.... < said: > It seems to me that all this spl hackery would be better avoided, > through a userland approach that used the tun device or something > similar. Some people need or prefer to have dependable bounds on the latency of their packets. -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 Mon May 17 9:18:47 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 7542A14F3E for ; Mon, 17 May 1999 09:18:44 -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 TAA26355; Mon, 17 May 1999 19:18:42 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 5879E1F8A; Mon, 17 May 1999 19:18:42 +0300 (EEST) Date: Mon, 17 May 1999 19:18:42 +0300 From: Vallo Kallaste To: Kazutaka YOKOTA Cc: freebsd-current@FreeBSD.ORG Subject: Re: syscons update - stage 2 snopshot 17 May Message-ID: <19990517191842.A89207@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <199905171554.AAA00483@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199905171554.AAA00483@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Tue, May 18, 1999 at 12:54:50AM +0900 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 18, 1999 at 12:54:50AM +0900, Kazutaka YOKOTA wrote: > 1) Syscons update: > > - Many static variables are moved to the softc structure. > > - History buffer (back-scroll buffer) management functions are moved > to a new file, schistory.c. My question is slightly off-topic, but.. is it now possible (or in the future) to choose which key combination to use for back-scroll buffer handling? I personally prefer the Linux way, +, no flames please. I can live with current combination but it's the one feature I miss. -- 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 Mon May 17 9:20:47 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 9A06F14FDF for ; Mon, 17 May 1999 09:20:45 -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 JAA02920; Mon, 17 May 1999 09:20:41 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA13892; Mon, 17 May 1999 09:20:41 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199905171616.MAA02501@khavrinen.lcs.mit.edu> Date: Mon, 17 May 1999 09:20:41 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Garrett Wollman Subject: Re: Heads up! config(8) changes.. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > < said: > >> It seems to me that all this spl hackery would be better avoided, >> through a userland approach that used the tun device or something >> similar. > > Some people need or prefer to have dependable bounds on the latency of > their packets. On the lp interface?? You've got to be joking! 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 Mon May 17 10: 2:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 7BFF414E96 for ; Mon, 17 May 1999 10:02:32 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id NAA20057; Mon, 17 May 1999 13:02:29 -0400 (EDT) (envelope-from luoqi) Date: Mon, 17 May 1999 13:02:29 -0400 (EDT) From: Luoqi Chen Message-Id: <199905171702.NAA20057@lor.watermarkgroup.com> To: Jos.Backus@nl.origin-it.com, current@FreeBSD.ORG Subject: Re: MFS still hosed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > With todays -current, mounting /tmp using > swap /tmp mfs rw,nosuid,nodev,-s=32768 0 0 > yields a > Are you sure you have the latest -current? I committed a fix Friday night. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 10:40:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 76A3314D92 for ; Mon, 17 May 1999 10:40:37 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id TAA29353 for ; Mon, 17 May 1999 19:40:36 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma029348; Mon, 17 May 99 19:40:37 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id TAA12782 for ; Mon, 17 May 1999 19:40:36 +0200 (MET DST) Received: (qmail 83594 invoked by uid 666); 17 May 1999 17:40:55 -0000 Date: Mon, 17 May 1999 19:40:55 +0200 From: Jos Backus To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: MFS still hosed Message-ID: <19990517194055.A83540@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <199905171702.NAA20057@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199905171702.NAA20057@lor.watermarkgroup.com>; from Luoqi Chen on Mon, May 17, 1999 at 01:02:29PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 17, 1999 at 01:02:29PM -0400, Luoqi Chen wrote: > Are you sure you have the latest -current? I committed a fix Friday night. I'm quite positive, because I experimented with a fresh -current/kernel yesterday. Changing NUMCDEV from 256 to 255 in kern_conf.c fixes the problem though. I'm not sure which fix you're alluding to... -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 10:45:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 10ADC14D92 for ; Mon, 17 May 1999 10:45:40 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.1) id KAA47992; Mon, 17 May 1999 10:45:15 -0700 (PDT) (envelope-from obrien) Message-ID: <19990517104515.A47978@nuxi.com> Date: Mon, 17 May 1999 10:45:15 -0700 From: "David O'Brien" To: Christopher Masto , Nate Williams Cc: Assar Westerlund , current@FreeBSD.ORG Subject: Re: zzz crashing in current OR inthand_remove not removing handlers properly Reply-To: obrien@NUXI.com References: <5lr9ogzaqf.fsf@assaris.sics.se> <19990516235949.A18232@netmonger.net> <199905171500.JAA22502@mt.sri.com> <19990517112634.A12004@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990517112634.A12004@netmonger.net>; from Christopher Masto on Mon, May 17, 1999 at 11:26:35AM -0400 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > With that and Assar's patch, my vaio is reasonably usable. (I hook it > up to the ethernet at work, so having to shut down to remove the card > or even just suspend is rather tedious.) Does/did your laptop freeze when you ejected the PC Card? My Vaio-505 locks solid. None of the Sony functions accessable via Fn- work either. -- -- David (obrien@NUXI.com -or- obrien@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 May 17 10:57: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 25D4814D92 for ; Mon, 17 May 1999 10:57:07 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.1) id KAA48074; Mon, 17 May 1999 10:55:43 -0700 (PDT) (envelope-from obrien) Message-ID: <19990517105543.B47978@nuxi.com> Date: Mon, 17 May 1999 10:55:43 -0700 From: "David O'Brien" To: Leif Neland , Marc van Woerkom Cc: freebsd-current@FreeBSD.ORG Subject: Re: No sound (Ensoniq Audio PCI 1370) Reply-To: obrien@NUXI.com References: <199905151958.VAA14199@oranje.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Leif Neland on Sun, May 16, 1999 at 06:19:41PM +0200 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Below follow dmesg output and kernel configuration. > > > device pcm0 at isa? port ? irq 10 drq 1 flags 0x0 > > I have this: > > device pcm0 at nexus? port ? irq 10 drq 1 flags 0x0 > ^^^^^^ I would like to update ``sys/i386/isa/snd/README'' since it currently does not have enough information to get a person going. Is the use of "nexus" vs "isa" the offical way to go now days? Also, what devices did people have to create to get sound and /dev/audio working? (ie. cd /dev ; ./MAKEDEV foo) -- -- David (obrien@NUXI.com -or- obrien@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 May 17 11: 6:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id AE2F114F3E for ; Mon, 17 May 1999 11:06:43 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id OAA22070; Mon, 17 May 1999 14:06:35 -0400 (EDT) Message-ID: <19990517140635.A21079@netmonger.net> Date: Mon, 17 May 1999 14:06:35 -0400 From: Christopher Masto To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: zzz crashing in current OR inthand_remove not removing handlers properly References: <5lr9ogzaqf.fsf@assaris.sics.se> <19990516235949.A18232@netmonger.net> <199905171500.JAA22502@mt.sri.com> <19990517112634.A12004@netmonger.net> <19990517104515.A47978@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19990517104515.A47978@nuxi.com>; from David O'Brien on Mon, May 17, 1999 at 10:45:15AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 17, 1999 at 10:45:15AM -0700, David O'Brien wrote: > > With that and Assar's patch, my vaio is reasonably usable. (I hook it > > up to the ethernet at work, so having to shut down to remove the card > > or even just suspend is rather tedious.) > > Does/did your laptop freeze when you ejected the PC Card? My Vaio-505 > locks solid. None of the Sony functions accessable via Fn- work > either. It used to, but now it works with the abovementioned patch. I'm not sure what I can get away with.. I usually "ifconfig ep0 down" and disconnect the cable before ejecting or suspending it (hoping to minimize the chance of getting an interrupt at the wrong time). Just tried ejecting the card while doing a ping -f, and it worked without a hitch. Here's my kernel config, if it helps... # # $Id: GENERIC,v 1.169 1999/05/09 16:45:52 phk Exp $ # machine i386 cpu I586_CPU ident HABANERO maxusers 64 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor controller isa0 controller pnp0 # PnP support for ISA controller pci0 #controller pccard0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 #controller ata0 #device atadisk0 # ATA disk drives #device atapicd0 # ATAPI CDROM drives #device atapist0 # ATAPI tape drives controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 # Options for psm: #options PSM_HOOKAPM #options PSM_RESETAFTERSUSPEND device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? # Advanced Power Management device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device ep0 at isa? port 0x300 irq 10 # SMB Bus controller smbus0 controller intpm0 controller alpm0 device smb0 at smbus? # PCCARD controller card0 device pcic0 at card? #device pcic0 options PCIC_RESUME_RESET # Sound device pcm0 at isa? port ? irq 5 drq 1 flags 0x0 #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 #device sbxvi0 at isa? drq 5 #device sbmidi0 at isa? port 0x330 #device awe0 at isa? port 0x620 # USB controller uhci0 controller ohci0 controller usb0 #controller umass0 device ums0 device ukbd0 device ulpt0 device uhid0 device ugen0 options UHCI_DEBUG options OHCI_DEBUG options USB_DEBUG options UHUB_DEBUG options UMS_DEBUG options UKBD_DEBUG options UMASS_DEBUG options UHID_DEBUG options UGEN_DEBUG options ULPT_DEBUG pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 32 pseudo-device gzip # Exec gzipped a.out's pseudo-device snp 3 # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG options SYSVSEM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 4 #Berkeley packet filter #options NETATALK options DDB options BREAK_TO_DEBUGGER options DDB_UNATTENDED options SOFTUPDATES options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_FORWARD options IPFIREWALL_VERBOSE_LIMIT=100 options ICMP_BANDLIM options DUMMYNET options USER_LDT options VM86 options VESA options INVARIANTS options INVARIANT_SUPPORT options DIAGNOSTIC options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- 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 Mon May 17 11:34:15 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 094DE14CC9 for ; Mon, 17 May 1999 11:34:13 -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 LAA00362; Mon, 17 May 1999 11:32:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905171832.LAA00362@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: current@freebsd.org Subject: Re: FBSDBOOT.EXE In-reply-to: Your message of "Mon, 17 May 1999 09:47:26 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 May 1999 11:32:31 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It doesn't work. Don't use it. You need to reboot the system to > > restore various vectors that DOS destroys. Please see the previous > > threads on this topic, especially anything from Robert Nordier. > > Would it be possible to add a driver to config.sys which could record the > various vectors or is that too late? We've been here and asked this; it's too late. Feel free to ask Robert for the details, or just trust me. 8) The only way to get a clean slate with the system is to reboot. If you can arrange a "controlled" reboot of some sort, we might get somewhere. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 12: 7:35 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 8547214D07 for ; Mon, 17 May 1999 12:07:27 -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 PAA25828 for ; Mon, 17 May 1999 15:07:26 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA22662; Mon, 17 May 1999 15:06:50 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id PAA76293 for freebsd-current@freebsd.org; Mon, 17 May 1999 15:06:42 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905171906.PAA76293@bb01f39.unx.sas.com> Subject: mfs related -current panic in MFS (stacktrace) To: freebsd-current@freebsd.org Date: Mon, 17 May 1999 15:06:42 -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've done alittle research into this with a debug kernel and the following is what I've found so far: db> trace checkalias(c71e2f80,ff00,0) at checkalias+0x13c mfs_mount(c0e0b800,bfbfde99,bfbfd79c,c7bb5eb4,c71ea4c0) at mfs_mount+0x28c mount(c71ea4c0,c7bb5490,0,80691e0,2000) at mount+0x4e7 syscall(... ... ...) Xint0x80_syscall() Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 12:10:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id C61B815457 for ; Mon, 17 May 1999 12:10:51 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial5-94.netcologne.de [194.8.195.94]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id VAA17001; Mon, 17 May 1999 21:10:39 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id VAA01774; Mon, 17 May 1999 21:10:56 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Mon, 17 May 1999 21:10:56 +0200 (CEST) Message-Id: <199905171910.VAA01774@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: leifn@neland.dk Cc: van.woerkom@netcologne.de, freebsd-current@FreeBSD.ORG In-reply-to: (message from Leif Neland on Sun, 16 May 1999 18:19:41 +0200 (CEST)) Subject: Re: No sound (Ensoniq Audio PCI 1370) Reply-To: van.woerkom@netcologne.de References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > device pcm0 at nexus? port ? irq 10 drq 1 flags 0x0 > ^^^^^^ I tried this out but discarded this approach because I got a trap 12 after boot (around the time X fires up). But In the meantime I found out that this must be caused by some other problem, so I will try again later - of course I would be happier if I knew what this choice of nexus implies. With the Friday kernels I get the afore mentioned trap everytime, except if I manually intervene early during booting and tell the system to use 'kernel' - yes kernel, the same kernel that otherwise traps if I don't caress the keyboard.. Could it be that the second stage bootloader (the one with Forth) is damaged somehow? Or did I screw up? I used 'disklabel -B da0' to make sure there is a recent bootblock on my system. Hereby I assumed that the necessary mechanism is built during a make buildworld/install world run. And, after having seen some logs fromt traps here, how do I save such output? Right now I hit a key and the system reboots - no idea how to capture this output. Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 12:37:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 89B5114CD0 for ; Mon, 17 May 1999 12:37:42 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id PAA21618; Mon, 17 May 1999 15:37:36 -0400 (EDT) (envelope-from luoqi) Date: Mon, 17 May 1999 15:37:36 -0400 (EDT) From: Luoqi Chen Message-Id: <199905171937.PAA21618@lor.watermarkgroup.com> To: Jos.Backus@nl.origin-it.com Subject: Re: MFS still hosed Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, May 17, 1999 at 01:02:29PM -0400, Luoqi Chen wrote: > > Are you sure you have the latest -current? I committed a fix Friday night. > > I'm quite positive, because I experimented with a fresh -current/kernel > yesterday. Changing NUMCDEV from 256 to 255 in kern_conf.c fixes the problem > though. I'm not sure which fix you're alluding to... > If you don't have `options MFS' in your config file, you will need to recompile the mfs kld module. > -- > Jos Backus _/ _/_/_/ "Reliability means never > _/ _/ _/ having to say you're sorry." > _/ _/_/_/ -- D. J. Bernstein > _/ _/ _/ _/ > Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 13: 1:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id 19E1A1500D for ; Mon, 17 May 1999 13:01:12 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id PAA58108 for freebsd-current@freebsd.org; Mon, 17 May 1999 15:01:12 -0500 (CDT) (envelope-from bob) Date: Mon, 17 May 1999 15:01:11 -0500 From: Bob Willcox To: current list Subject: panic: page fault (apparently caused by mount_mfs) Message-ID: <19990517150111.A30936@luke.pmr.com> Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have been getting a panic lately with every -current kernel that I have built for the past week or so (-current cvsupped daily). Even the GENERIC kernel panics. It is occuring when the mount for a /tmp mfs filesystem is attempted. If I boot an old kernel from 5/11 or remove the fstab entry for the mfs file system the system boots up okay. My fstab entry for this is: /dev/da0s1b /tmp mfs rw,nosuid,-s=102400 0 0 and the panic messages are: Fatal trap 12: pagefault while in kernel mode fault virtual address = 0x9d334e68 fault code = Supervisor read, page not present instruction pointer = 0x8:0xc0185cb0 stack pointer = 0x10:0xc98ad84 frame pointer = 0x10:0xc98adb0 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 = 40 (mount_mfs) interrupt mask = trap number = 12 panic: page fault Any ideas on what may be wrong? Thanks, Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 13: 4:49 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 7C78D1500D for ; Mon, 17 May 1999 13:04:47 -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 NAA00797; Mon, 17 May 1999 13:04:12 -0700 Date: Mon, 17 May 1999 13:03:50 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Bob Willcox Cc: current list Subject: Re: panic: page fault (apparently caused by mount_mfs) In-Reply-To: <19990517150111.A30936@luke.pmr.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 I use mfs a lot and have had no trouble whatsoever. I'm using: swap /tmp mfs rw,-s=200000 0 0 Do you suppose that the usage of /dev/da0s1b directly is what's causing some trouble? On Mon, 17 May 1999, Bob Willcox wrote: > Hi, > > I have been getting a panic lately with every -current kernel that I > have built for the past week or so (-current cvsupped daily). Even the > GENERIC kernel panics. It is occuring when the mount for a /tmp mfs > filesystem is attempted. If I boot an old kernel from 5/11 or remove > the fstab entry for the mfs file system the system boots up okay. My > fstab entry for this is: > > /dev/da0s1b /tmp mfs rw,nosuid,-s=102400 0 0 > > and the panic messages are: > > Fatal trap 12: pagefault while in kernel mode > fault virtual address = 0x9d334e68 > fault code = Supervisor read, page not present > instruction pointer = 0x8:0xc0185cb0 > stack pointer = 0x10:0xc98ad84 > frame pointer = 0x10:0xc98adb0 > 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 = 40 (mount_mfs) > interrupt mask = > trap number = 12 > panic: page fault > > > Any ideas on what may be wrong? > > Thanks, > Bob > > -- > Bob Willcox The man who follows the crowd will usually get no > bob@luke.pmr.com further than the crowd. The man who walks alone is > Austin, TX likely to find himself in places no one has ever > been. -- Alan Ashley-Pitt > > > 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 Mon May 17 13:11:27 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 ECBC61520D for ; Mon, 17 May 1999 13:11:22 -0700 (PDT) (envelope-from Thrumbar@Worldnet.att.net) Received: from 188.neworleans-15-20rs16rt.la.dial-access.att.net ([12.73.251.188]) by mtiwmhc06.worldnet.att.net (InterMail v03.02.07 118 124) with SMTP id <19990517201119.GMYC10864@188.neworleans-15-20rs16rt.la.dial-access.att.net> for ; Mon, 17 May 1999 20:11:19 +0000 From: Thrumbar@Worldnet.att.net (Thrumbar Pathfinder) To: freebsd-current@freebsd.org Subject: Re: Berkeley DB 1.85 --> 2.0 Date: Mon, 17 May 1999 20:09:06 GMT Organization: OmniCorp Interstellar Message-ID: <3746628e.2366261@mailhost.worldnet.att.net> References: <19990513164720.A26399@trinsec.com> <199905132050.QAA10438@khavrinen.lcs.mit.edu> In-Reply-To: <199905132050.QAA10438@khavrinen.lcs.mit.edu> X-Mailer: Forte Agent 1.5/32.452 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could you be more specific on what part of the license is so unfriendly????? Thrumbar@Worldnet.att.net On Thu, 13 May 1999 16:50:17 -0400 (EDT), you wrote: >< = said: > >> Out of curiosity, is there a reason we are still using Berkeley DB = v1.85 as >> apposed to v2? =20 > >Yes. v2 has an unfriendly license. > >-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=20 >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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 13:19:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id EF34514D28 for ; Mon, 17 May 1999 13:19:24 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id PAA81997; Mon, 17 May 1999 15:19:21 -0500 (CDT) (envelope-from bob) Date: Mon, 17 May 1999 15:19:20 -0500 From: Bob Willcox To: Matthew Jacob Cc: Bob Willcox , current list Subject: Re: panic: page fault (apparently caused by mount_mfs) Message-ID: <19990517151920.C30936@luke.pmr.com> Reply-To: Bob Willcox References: <19990517150111.A30936@luke.pmr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Matthew Jacob on Mon, May 17, 1999 at 01:03:50PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 17, 1999 at 01:03:50PM -0700, Matthew Jacob wrote: > > I use mfs a lot and have had no trouble whatsoever. I'm using: > > swap /tmp mfs rw,-s=200000 0 0 > > Do you suppose that the usage of /dev/da0s1b directly is what's causing > some trouble? Don't know, but I will change it and see what happens. Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 13:35:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id B408314D16 for ; Mon, 17 May 1999 13:35:31 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id QAA22167; Mon, 17 May 1999 16:34:50 -0400 (EDT) (envelope-from luoqi) Date: Mon, 17 May 1999 16:34:50 -0400 (EDT) From: Luoqi Chen Message-Id: <199905172034.QAA22167@lor.watermarkgroup.com> To: bob@pmr.com, freebsd-current@FreeBSD.ORG Subject: Re: panic: page fault (apparently caused by mount_mfs) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I have been getting a panic lately with every -current kernel that I > have built for the past week or so (-current cvsupped daily). Even the > GENERIC kernel panics. It is occuring when the mount for a /tmp mfs > filesystem is attempted. If I boot an old kernel from 5/11 or remove > the fstab entry for the mfs file system the system boots up okay. My > fstab entry for this is: > > /dev/da0s1b /tmp mfs rw,nosuid,-s=102400 0 0 > > and the panic messages are: > > Fatal trap 12: pagefault while in kernel mode > fault virtual address = 0x9d334e68 > fault code = Supervisor read, page not present > instruction pointer = 0x8:0xc0185cb0 > stack pointer = 0x10:0xc98ad84 > frame pointer = 0x10:0xc98adb0 > 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 = 40 (mount_mfs) > interrupt mask = > trap number = 12 > panic: page fault > > > Any ideas on what may be wrong? > > Thanks, > Bob > > -- > Bob Willcox The man who follows the crowd will usually get no > bob@luke.pmr.com further than the crowd. The man who walks alone is > Austin, TX likely to find himself in places no one has ever > been. -- Alan Ashley-Pitt > How about recompile mfs kld module and try again? -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 13:46:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id C7DC515500 for ; Mon, 17 May 1999 13:46:08 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id PAA82287; Mon, 17 May 1999 15:45:44 -0500 (CDT) (envelope-from bob) Date: Mon, 17 May 1999 15:45:44 -0500 From: Bob Willcox To: Matthew Jacob Cc: Bob Willcox , current list Subject: Re: panic: page fault (apparently caused by mount_mfs) Message-ID: <19990517154544.D30936@luke.pmr.com> Reply-To: Bob Willcox References: <19990517150111.A30936@luke.pmr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Matthew Jacob on Mon, May 17, 1999 at 01:03:50PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 17, 1999 at 01:03:50PM -0700, Matthew Jacob wrote: > > I use mfs a lot and have had no trouble whatsoever. I'm using: > > swap /tmp mfs rw,-s=200000 0 0 > > Do you suppose that the usage of /dev/da0s1b directly is what's causing > some trouble? Unfortunately, changing from /dev/da0s1b to swap didn't help. I also tried it without the nosuid option but it still panics. Bob > > > On Mon, 17 May 1999, Bob Willcox wrote: > > > Hi, > > > > I have been getting a panic lately with every -current kernel that I > > have built for the past week or so (-current cvsupped daily). Even the > > GENERIC kernel panics. It is occuring when the mount for a /tmp mfs > > filesystem is attempted. If I boot an old kernel from 5/11 or remove > > the fstab entry for the mfs file system the system boots up okay. My > > fstab entry for this is: > > > > /dev/da0s1b /tmp mfs rw,nosuid,-s=102400 0 0 > > > > and the panic messages are: > > > > Fatal trap 12: pagefault while in kernel mode > > fault virtual address = 0x9d334e68 > > fault code = Supervisor read, page not present > > instruction pointer = 0x8:0xc0185cb0 > > stack pointer = 0x10:0xc98ad84 > > frame pointer = 0x10:0xc98adb0 > > 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 = 40 (mount_mfs) > > interrupt mask = > > trap number = 12 > > panic: page fault > > > > > > Any ideas on what may be wrong? > > > > Thanks, > > Bob > > > > -- > > Bob Willcox The man who follows the crowd will usually get no > > bob@luke.pmr.com further than the crowd. The man who walks alone is > > Austin, TX likely to find himself in places no one has ever > > been. -- Alan Ashley-Pitt > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 13:48:48 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 9606B153E7 for ; Mon, 17 May 1999 13:48:44 -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 NAA00892; Mon, 17 May 1999 13:48:21 -0700 Date: Mon, 17 May 1999 13:47:59 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Bob Willcox Cc: current list Subject: Re: panic: page fault (apparently caused by mount_mfs) In-Reply-To: <19990517154544.D30936@luke.pmr.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 > > > > I use mfs a lot and have had no trouble whatsoever. I'm using: > > > > swap /tmp mfs rw,-s=200000 0 0 > > > > Do you suppose that the usage of /dev/da0s1b directly is what's causing > > some trouble? > > Unfortunately, changing from /dev/da0s1b to swap didn't help. I also > tried it without the nosuid option but it still panics. > Hmm. Is MFS a module as Luoqi keeps mentioning? How much real memory do you have? See- it's been working fine for me! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 13:52:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id 00D2714BDB for ; Mon, 17 May 1999 13:52:36 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id PAA82410; Mon, 17 May 1999 15:52:30 -0500 (CDT) (envelope-from bob) Date: Mon, 17 May 1999 15:52:30 -0500 From: Bob Willcox To: Matthew Jacob Cc: Bob Willcox , current list Subject: Re: panic: page fault (apparently caused by mount_mfs) Message-ID: <19990517155230.A82352@luke.pmr.com> Reply-To: Bob Willcox References: <19990517154544.D30936@luke.pmr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Matthew Jacob on Mon, May 17, 1999 at 01:47:59PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 17, 1999 at 01:47:59PM -0700, Matthew Jacob wrote: > > > > > > I use mfs a lot and have had no trouble whatsoever. I'm using: > > > > > > swap /tmp mfs rw,-s=200000 0 0 > > > > > > Do you suppose that the usage of /dev/da0s1b directly is what's causing > > > some trouble? > > > > Unfortunately, changing from /dev/da0s1b to swap didn't help. I also > > tried it without the nosuid option but it still panics. > > > > Hmm. Is MFS a module as Luoqi keeps mentioning? How much real memory do > you have? I believe it is in the kernel (the GENERIC kernel includes it as well as my customized kernel config file). This system has 256MB. > > > See- it's been working fine for me! Yep. I am going to try re-checking out all of the current sources and see if that helps. Perhaps something is hosed with my source tree. Thanks, Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 14: 5:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id DEF4A15355 for ; Mon, 17 May 1999 14:05:07 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id QAA82573; Mon, 17 May 1999 16:05:00 -0500 (CDT) (envelope-from bob) Date: Mon, 17 May 1999 16:05:00 -0500 From: Bob Willcox To: Luoqi Chen Cc: current list Subject: Re: panic: page fault (apparently caused by mount_mfs) Message-ID: <19990517160500.E30936@luke.pmr.com> Reply-To: Bob Willcox References: <199905172034.QAA22167@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199905172034.QAA22167@lor.watermarkgroup.com>; from Luoqi Chen on Mon, May 17, 1999 at 04:34:50PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 17, 1999 at 04:34:50PM -0400, Luoqi Chen wrote: > > Hi, > > > > I have been getting a panic lately with every -current kernel that I > > have built for the past week or so (-current cvsupped daily). Even the > > GENERIC kernel panics. It is occuring when the mount for a /tmp mfs > > filesystem is attempted. If I boot an old kernel from 5/11 or remove > > the fstab entry for the mfs file system the system boots up okay. My > > fstab entry for this is: > > > > /dev/da0s1b /tmp mfs rw,nosuid,-s=102400 0 0 > > > > and the panic messages are: > > > > Fatal trap 12: pagefault while in kernel mode > > fault virtual address = 0x9d334e68 > > fault code = Supervisor read, page not present > > instruction pointer = 0x8:0xc0185cb0 > > stack pointer = 0x10:0xc98ad84 > > frame pointer = 0x10:0xc98adb0 > > 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 = 40 (mount_mfs) > > interrupt mask = > > trap number = 12 > > panic: page fault > > > > > > Any ideas on what may be wrong? > > > > Thanks, > > Bob > > > > -- > > Bob Willcox The man who follows the crowd will usually get no > > bob@luke.pmr.com further than the crowd. The man who walks alone is > > Austin, TX likely to find himself in places no one has ever > > been. -- Alan Ashley-Pitt > > > How about recompile mfs kld module and try again? I have been making world each time after cvsupping so I would expect the mfs kld module to be getting rebuilt and it appears to be up-to-date: -r-xr-xr-x 1 root wheel 12778 May 17 13:34 /modules/mfs.ko Also, both my custom kernel config file and the GENERIC config file include "options MFS" so mfs should not be getting loaded, right? Thanks, Bob > > -lq -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 14:24:24 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 A6BD514DC3 for ; Mon, 17 May 1999 14:24:16 -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 WAA57438; Mon, 17 May 1999 22:25:00 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 May 1999 22:25:00 +0100 (BST) From: Doug Rabson To: Mike Smith Cc: current@freebsd.org Subject: Re: FBSDBOOT.EXE In-Reply-To: <199905171832.LAA00362@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 Mon, 17 May 1999, Mike Smith wrote: > > > It doesn't work. Don't use it. You need to reboot the system to > > > restore various vectors that DOS destroys. Please see the previous > > > threads on this topic, especially anything from Robert Nordier. > > > > Would it be possible to add a driver to config.sys which could record the > > various vectors or is that too late? > > We've been here and asked this; it's too late. Feel free to ask Robert > for the details, or just trust me. 8) Sure. I'm just thinking aloud :-) > > The only way to get a clean slate with the system is to reboot. If you > can arrange a "controlled" reboot of some sort, we might get somewhere. If you are going to reboot anyway, its not too much to ask for a bootable floppy/cd to be inserted. I don't think fbsdboot.exe has much practical value at this time. -- 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 Mon May 17 14:29: 5 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 ABFE014E10 for ; Mon, 17 May 1999 14:28:50 -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 WAA57450; Mon, 17 May 1999 22:28:03 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 May 1999 22:28:03 +0100 (BST) From: Doug Rabson To: obrien@NUXI.com Cc: Leif Neland , Marc van Woerkom , freebsd-current@freebsd.org Subject: Re: No sound (Ensoniq Audio PCI 1370) In-Reply-To: <19990517105543.B47978@nuxi.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, 17 May 1999, David O'Brien wrote: > > > Below follow dmesg output and kernel configuration. > > > > > device pcm0 at isa? port ? irq 10 drq 1 flags 0x0 > > > > I have this: > > > > device pcm0 at nexus? port ? irq 10 drq 1 flags 0x0 > > ^^^^^^ > > I would like to update ``sys/i386/isa/snd/README'' since it currently > does not have enough information to get a person going. Is the use of > "nexus" vs "isa" the offical way to go now days? > > Also, what devices did people have to create to get sound and /dev/audio > working? (ie. cd /dev ; ./MAKEDEV foo) I don't think nexus is the right place at all. I can't see how the probe would get called (except via pnp which isn't properly integrated yet). -- 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 Mon May 17 14:43:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (Postfix) with ESMTP id 85C3315093 for ; Mon, 17 May 1999 14:43:35 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with SMTP id OAA29046; Mon, 17 May 1999 14:42:46 -0700 Message-ID: <006201bea0ae$7e656340$0d787880@apex.tapang> From: "Carlos C. Tapang" To: "Mike Smith" Cc: Subject: Re: FBSDBOOT.EXE Date: Mon, 17 May 1999 14:44:51 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike, Thanks for trying fbsdboot.exe. I need more information to fix it. I would like to fix it, so please describe exactly what the problem is. What do you mean by the "need to reboot the system to restore various vectors that DOS destroys"? Do you mean that prior to executing the FreeBSD kernel init routines, DOS does something to the loaded area? I'm sorry I can't find any info on this either in the mail threads or in freebsd.org. Probably I'm not looking hard enough, but I believe it would be more efficient to just ask you. Carlos C. Tapang http://www.genericwindows.com -----Original Message----- From: Mike Smith To: Carlos C. Tapang Cc: Bob Bishop ; Mike Smith ; current@freebsd.org Date: Sunday, May 16, 1999 7:28 PM Subject: Re: FBSDBOOT.EXE >> >It doesn't work. Don't use it. You need to reboot the system to >> >restore various vectors that DOS destroys. Please see the previous >> >threads on this topic, especially anything from Robert Nordier. >> > >> The most relevant piece I can find from R. Nordier is the following: >> "The fbsdboot.exe program should probably be considered obsolete. It >> should (in theory) be possible to use it to load /boot/loader, which >> can then load the kernel, but there are various reasons this doesn't >> work too well." > >These reasons were also expounded, and I did summarise them in another >message on this thread. > >> I have not tested the updated program with /boot/loader. /boot/loader does >> not help me because my root directory is in a memory file system, and I can >> not assume that my users will want to reformat their DOS drives or even >> repartition it. So all FreeBSD files are in the DOS file system. > >The loader won't help you because you are booting from under DOS, but >the loader will boot the kernel just fine off a DOS filesystem. > >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 14:53:56 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 7AB6915424 for ; Mon, 17 May 1999 14:53:50 -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 RAA03341 for ; Mon, 17 May 1999 17:18:27 -0500 (EST) Date: Mon, 17 May 1999 17:18:25 -0500 (EST) From: Alfred Perlstein To: current@freebsd.org Subject: non-graceful NFS on server reboot. 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 default NFS mounts: mount server:/home/ncvs /home/ncvs I recently rebooted "server". When it came back all attempts to access mount point on the client returned the error "stale NFS handle". Is there a way to force NFS client to reaquire cookies for mountpoints? It doesn't seem that i should have to reboot my client to get NFS consistant again. Why should I even have to do this? (curiosity) anyone else have this problem with a pretty recent -current? thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 15:22:47 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 AAE061541D for ; Mon, 17 May 1999 15:22:42 -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 SAA24550; Mon, 17 May 1999 18:21:14 -0400 (EDT) Date: Mon, 17 May 1999 18:21:13 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: IDE strangeness In-Reply-To: <199905170948.LAA24787@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 May 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: > > I'm having two problems with IDE nowadays. > >=20 > > 1. ATA doesn't work with LS-120. That's not new. But ATA does seem to c= rash on > > me, and there's no dump() so I can't figure out why. Reply to my own problem: ATA crashed more often than wd, but they both cras= hed with my old, faulty CPU. My K6-2 350 now works perfectly. >=20 > Good news is that I've gotten ahold of a LS120 drive, so I can test this = now. >=20 > Bad news is that it has stopped working on my ZIP drive too :( That's bad, if it used to. LS-120 never worked under ATA, with or without new-bus. But you say Zip always has. >=20 > Something must have been screwed up since the newbus import, either in > my driver (I feel at risk saying that it is not likely), or something els= e. I'm pretty sure your driver isn't screwed up, as I've tracked most of the changes. >=20 > -S=F8ren >=20 Brian Feldman _ __ ___ ____ ___ ___ ___ =20 green@unixhelp.org _ __ ___ | _ ) __| \=20 FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 15:24:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from kushnir.kiev.ua (n183.cdialup.kar.net [195.178.130.183]) by hub.freebsd.org (Postfix) with ESMTP id 128D81541D for ; Mon, 17 May 1999 15:23:55 -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 BAA04461; Tue, 18 May 1999 01:22:07 +0300 (EEST) (envelope-from kushn@mail.kar.net) X-Authentication-Warning: kushnir.kiev.ua: volodya owned process doing -bs Date: Tue, 18 May 1999 01:22:06 +0300 (EEST) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: rplayd: mixer not installed In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-656368510-926979726=:2396" 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-656368510-926979726=:2396 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, This message has absolutely nothing to do with FreeBSD sound driver. It looks like it's a (bug/typo) in rplay. Try to change SOUND_MIXER_PCM in audio_FreeBSD.c to SOUND_MASK_PCM (patch attached, but it's for rplay-3.3.1, which has some another typos as well :-() On Mon, 17 May 1999, Leif Neland wrote: > At boot I get this message: > /usr/local/sbin/rplayd: rplay_audio_get_volume: pcm mixer device not > installed. > > However, /dev/mixer is installed, and works. > > I'm using current, Luiqi's pcm and a ESS soundcard. > > Leif > > Hope this helps, Vladimir ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | --0-656368510-926979726=:2396 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="audio_FreeBSD.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="audio_FreeBSD.diff" KioqIGF1ZGlvX0ZyZWVCU0QuYy5vbGQJVGh1IFNlcCAgMyAwOTowODo0NCAx OTk4DQotLS0gYXVkaW9fRnJlZUJTRC5jCVR1ZSBNYXkgMTggMDE6MDA6MjYg MTk5OQ0KKioqKioqKioqKioqKioqDQoqKiogMzUzLDM1OSAqKioqDQogIAly ZXR1cm4gKC0xKTsNCiAgICAgIH0NCiAgDQohICAgICBpZiAoIShteGRldm1h c2sgJiBTT1VORF9NSVhFUl9QQ00pKQ0KICAgICAgew0KICAJcmVwb3J0IChS RVBPUlRfRVJST1IsICJycGxheV9hdWRpb19nZXRfdm9sdW1lOiBwY20gbWl4 ZXIgZGV2aWNlIG5vdCBpbnN0YWxsZWRcbiIpOw0KICAJY2xvc2UgKG14KTsN Ci0tLSAzNTMsMzU5IC0tLS0NCiAgCXJldHVybiAoLTEpOw0KICAgICAgfQ0K ICANCiEgICAgIGlmICghKG14ZGV2bWFzayAmIFNPVU5EX01BU0tfUENNKSkN CiAgICAgIHsNCiAgCXJlcG9ydCAoUkVQT1JUX0VSUk9SLCAicnBsYXlfYXVk aW9fZ2V0X3ZvbHVtZTogcGNtIG1peGVyIGRldmljZSBub3QgaW5zdGFsbGVk XG4iKTsNCiAgCWNsb3NlIChteCk7DQoqKioqKioqKioqKioqKioNCioqKiA0 MTcsNDIzICoqKioNCiAgCXJldHVybiAoLTEpOw0KICAgICAgfQ0KICANCiEg ICAgIGlmICghKG14ZGV2bWFzayAmIFNPVU5EX01JWEVSX1BDTSkpDQogICAg ICB7DQogIAlyZXBvcnQgKFJFUE9SVF9FUlJPUiwgInJwbGF5X2F1ZGlvX3Nl dF92b2x1bWU6IHBjbSBtaXhlciBkZXZpY2Ugbm90IGluc3RhbGxlZFxuIik7 DQogIAljbG9zZSAobXgpOw0KLS0tIDQxNyw0MjMgLS0tLQ0KICAJcmV0dXJu ICgtMSk7DQogICAgICB9DQogIA0KISAgICAgaWYgKCEobXhkZXZtYXNrICYg U09VTkRfTUFTS19QQ00pKQ0KICAgICAgew0KICAJcmVwb3J0IChSRVBPUlRf RVJST1IsICJycGxheV9hdWRpb19zZXRfdm9sdW1lOiBwY20gbWl4ZXIgZGV2 aWNlIG5vdCBpbnN0YWxsZWRcbiIpOw0KICAJY2xvc2UgKG14KTsNCg== --0-656368510-926979726=:2396-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 15:36:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 8BB2C14FD4 for ; Mon, 17 May 1999 15:36:45 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id AAA17319; Tue, 18 May 1999 00:36:40 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 24BE0D21A; Tue, 18 May 1999 00:36:40 +0200 (CEST) Message-ID: <19990518003640.A2978@enst.fr> Date: Tue, 18 May 1999 00:36:40 +0200 From: Pierre Beyssac To: Matthew Dillon , Garrett Wollman Cc: freebsd-current@FreeBSD.ORG Subject: Re: mbuf starvation References: <19990512172544.A440@enst.fr> <199905121656.MAA00970@khavrinen.lcs.mit.edu> <199905122034.NAA88116@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905122034.NAA88116@apollo.backplane.com>; from Matthew Dillon on Wed, May 12, 1999 at 01:34:05PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 12, 1999 at 01:34:05PM -0700, Matthew Dillon wrote: > asleep() allows a subroutine deep in the call stack to specify an > asynchronous blocking condition and then return a temporary failure > up through the ranks. At the top level, the scheduler sees and acts > upon the asynchronous blocking condition. Higher level routines do not So if I get it right, this would give something like the code below. Is that the idea? What's missing in the asleep/await code to use them in such a way? soxxx() { for (;;) { await(&mbuf_slp); /* code */ error = xxx(&mbuf_slp); if (error != ENOBUFS) break; } } m_retry() { /* find an mbuf... */ if (/* got an mbuf to return */) return mbuf; else { asleep(&mbuf_slp); return NULL; } } m_free() { /* Free mbuf... */ wakeup(&mbuf_slp); } And, unless I'm missing something, we still need to properly check for NULL return values from m_get and friends. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 15:38:51 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 172F514FD4 for ; Mon, 17 May 1999 15:38:49 -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 SAA24808; Mon, 17 May 1999 18:37:22 -0400 (EDT) Date: Mon, 17 May 1999 18:37:22 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: UPDATE7: ATA/ATAPI driver new version available. In-Reply-To: <199905171601.SAA25465@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 May 1999, Soren Schmidt wrote: > Seventh update to the new ATA/ATAPI driver: >=20 > Fixed problems: >=20 > LS120 drives currupted data. > =09The workaround for drives not supporting upto 64K transfers > =09has been reworked. It works now both on LS120 & ZIP drives. Thank you!! >=20 > ISA only configs wont compile. > =09Fixed. >=20 > The ATA driver wont share interrupts. > =09Fixed. >=20 > The "unwanted interrupt" warning gave wrong controller. > =09Another lun<>unit messup from the newbus integration. >=20 > Some minor cleanups and rearrangements as well. >=20 > 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... >=20 > But please tell me how it works for you! >=20 > Enjoy! >=20 > -S=F8ren >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 Brian Feldman _ __ ___ ____ ___ ___ ___ =20 green@unixhelp.org _ __ ___ | _ ) __| \=20 FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 15:40:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 93C9E15666 for ; Mon, 17 May 1999 15:40:12 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id AAA23137 for ; Tue, 18 May 1999 00:40:10 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma023133; Tue, 18 May 99 00:40:10 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id AAA01892 for ; Tue, 18 May 1999 00:40:08 +0200 (MET DST) Received: (qmail 86125 invoked by uid 666); 17 May 1999 22:40:28 -0000 Date: Tue, 18 May 1999 00:40:28 +0200 From: Jos Backus To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: MFS still hosed Message-ID: <19990518004028.B86023@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <199905171937.PAA21618@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199905171937.PAA21618@lor.watermarkgroup.com>; from Luoqi Chen on Mon, May 17, 1999 at 03:37:36PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 17, 1999 at 03:37:36PM -0400, Luoqi Chen wrote: > If you don't have `options MFS' in your config file, you will need to > recompile the mfs kld module. I know, I did that this evening (did a make world/kernel rebuild around 8pm CEST): -r-xr-xr-x 1 root wheel 12874 May 17 21:20 mfs.ko* Still crashes without the NUMCDEV adjustment though... -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 15:42:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 46936150F3 for ; Mon, 17 May 1999 15:42:04 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id AAA22143; Tue, 18 May 1999 00:42:00 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id 49F08D21A; Tue, 18 May 1999 00:42:00 +0200 (CEST) Message-ID: <19990518004200.B2978@enst.fr> Date: Tue, 18 May 1999 00:42:00 +0200 From: Pierre Beyssac To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG Subject: Re: mbuf starvation References: <19990512172544.A440@enst.fr> <199905121750.KAA61736@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905121750.KAA61736@bubba.whistle.com>; from Archie Cobbs on Wed, May 12, 1999 at 10:50:42AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 12, 1999 at 10:50:42AM -0700, Archie Cobbs wrote: > > MCLGET(m, M_WAIT); > > + if (m == 0) { > > I think this part of the patch is useless. MCLGET() does not set > m to NULL when it fails, it simply doesn't set the M_EXT flag. > ...unless things have changed recently. No, they apparently haven't. You're absolutely right. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 16:19:35 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 DFD50151CE for ; Mon, 17 May 1999 16:19:33 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id BAA08847; Tue, 18 May 1999 01:22:47 +0200 (CEST) To: obrien@NUXI.com Cc: Christopher Masto , Nate Williams , current@FreeBSD.ORG Subject: Re: zzz crashing in current OR inthand_remove not removing handlers properly References: <5lr9ogzaqf.fsf@assaris.sics.se> <19990516235949.A18232@netmonger.net> <199905171500.JAA22502@mt.sri.com> <19990517112634.A12004@netmonger.net> <19990517104515.A47978@nuxi.com> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 18 May 1999 01:22:45 +0200 In-Reply-To: "David O'Brien"'s message of "Mon, 17 May 1999 10:45:15 -0700" Message-ID: <5lyainl1ru.fsf@assaris.sics.se> Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" writes: > > With that and Assar's patch, my vaio is reasonably usable. (I hook it > > up to the ethernet at work, so having to shut down to remove the card > > or even just suspend is rather tedious.) > > Does/did your laptop freeze when you ejected the PC Card? My laptop (Thinkpad 560) doesn't crash when ejecting the card (a 3c589c) with the patch. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 20:46:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id 16FB714E9C for ; Mon, 17 May 1999 20:46:43 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (Postfix) with ESMTP id 3AE5E1F72; Tue, 18 May 1999 11:46:32 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Thrumbar@Worldnet.att.net (Thrumbar Pathfinder) Cc: freebsd-current@freebsd.org Subject: Re: Berkeley DB 1.85 --> 2.0 In-reply-to: Your message of "Mon, 17 May 1999 20:09:06 GMT." <3746628e.2366261@mailhost.worldnet.att.net> Date: Tue, 18 May 1999 11:46:32 +0800 From: Peter Wemm Message-Id: <19990518034639.3AE5E1F72@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thrumbar Pathfinder wrote: > Could you be more specific on what part of the license is so > unfriendly????? > > Thrumbar@Worldnet.att.net For one, it's worse even than the GPL. Remember, this is in libc, it would effectively require publication of sources to all binaries linked against libc.. (This is probably and over generalization, and it's a while since I read it, so read it for yourself and don't take my word for it) It's in libc because the core of the password database routines are written around DB1.x. We can't use dlopen() since getpwxxx() has to work in static binaries. Also, old binaries can't read the new /etc/pwd.db etc and vice versa as the format has changed. I am no longer sure why there was a problem with shipping both versions, but I seem to recall there was some sort of conflict or risk of conflict with having a version in libc and a seperate -ldb library. Don't get me wrong, Keith Bostic has put a lot of effort into it and I wish him well in trying to get a return on his investment, but the way he's chosen to do that has pretty much ruled it out for us using or supplying it in the base OS. > On Thu, 13 May 1999 16:50:17 -0400 (EDT), you wrote: > > >< = > said: > > > >> Out of curiosity, is there a reason we are still using Berkeley DB = > v1.85 as > >> apposed to v2? =20 > > > >Yes. v2 has an unfriendly license. > > > >-GAWollman Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 21:14:21 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 21B4514D89 for ; Mon, 17 May 1999 21:14:17 -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 AAA32572; Tue, 18 May 1999 00:12:51 -0400 (EDT) Date: Tue, 18 May 1999 00:12:48 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: sos@freebsd.dk Cc: current@freebsd.org Subject: ATA and afd (LS-120): got it WORKING! 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 Yes, I finally got it working! The explanation is in the patch, which I should not need to explain again :) Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ --- src/sys/dev/ata/atapi-fd.c.orig Mon May 17 20:28:16 1999 +++ src/sys/dev/ata/atapi-fd.c Mon May 17 20:42:37 1999 @@ -83,7 +83,7 @@ int32_t afdattach(struct atapi_softc *); static int32_t afd_sense(struct afd_softc *); -static void afd_describe(struct afd_softc *); +static void afd_describe(struct afd_softc *, int8_t *, int8_t *); static void afd_strategy(struct buf *); static void afd_start(struct afd_softc *); static void afd_done(struct atapi_request *); @@ -96,6 +96,8 @@ afdattach(struct atapi_softc *atp) { struct afd_softc *fdp; + int8_t model_buf[40+1]; + int8_t revision_buf[8+1]; if (afdnlun >= NUNIT) { printf("afd: too many units\n"); @@ -106,18 +108,22 @@ printf("afd: out of memory\n"); return -1; } + bzero(fdp, sizeof(struct afd_softc)); bufq_init(&fdp->buf_queue); fdp->atp = atp; fdp->lun = afdnlun; fdp->flags = F_MEDIA_CHANGED; + bpack(atp->atapi_parm->model, model_buf, sizeof(model_buf)); + bpack(atp->atapi_parm->revision, revision_buf, sizeof(revision_buf)); + fdp->maxblks = strcmp(model_buf, "IOMEGA ZIP 100 ATAPI") ? 0 : 64; if (afd_sense(fdp)) { free(fdp, M_TEMP); return -1; } - afd_describe(fdp); + afd_describe(fdp, model_buf, revision_buf); afdtab[afdnlun++] = fdp; devstat_add_entry(&fdp->stats, "afd", fdp->lun, DEV_BSIZE, DEVSTAT_NO_ORDERED_TAGS, @@ -166,15 +172,10 @@ } static void -afd_describe(struct afd_softc *fdp) +afd_describe(struct afd_softc *fdp, int8_t *model, int8_t *revision) { - int8_t model_buf[40+1]; - int8_t revision_buf[8+1]; - - bpack(fdp->atp->atapi_parm->model, model_buf, sizeof(model_buf)); - bpack(fdp->atp->atapi_parm->revision, revision_buf, sizeof(revision_buf)); printf("afd%d: <%s/%s> rewriteable drive at ata%d as %s\n", - fdp->lun, model_buf, revision_buf, + fdp->lun, model, revision, fdp->atp->controller->lun, (fdp->atp->unit == ATA_MASTER) ? "master" : "slave "); printf("afd%d: %luMB (%u sectors), %u cyls, %u heads, %u S/T, %u B/S\n", @@ -320,9 +321,14 @@ lba = bp->b_blkno / (fdp->cap.sector_size / DEV_BSIZE); count = (bp->b_bcount + (fdp->cap.sector_size - 1)) / fdp->cap.sector_size; - /* Should only be needed for ZIP drives, but better safe than sorry */ - if (count > 64) - count = 64; + /* + * This should only be needed for ZIP drives, since they lock up if a + * transfer of > 64 sectors is attempted. XXX TODO (for SOS): when + * this problem is to be worked around, multiple transfers will need + * to be queued! + */ + if (fdp->maxblks && count > fdp->maxblks) + count = fdp->maxblks; bzero(ccb, sizeof(ccb)); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 21:24:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 1788C14C0A for ; Mon, 17 May 1999 21:24:39 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id XAA29737; Mon, 17 May 1999 23:24:38 -0500 (CDT) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.6.13/8.6.4) with ESMTP id XAA04887; Mon, 17 May 1999 23:24:37 -0500 Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id XAA02905; Mon, 17 May 1999 23:24:37 -0500 (CDT) Date: Mon, 17 May 1999 23:24:37 -0500 (CDT) From: Jonathan Lemon Message-Id: <199905180424.XAA02905@free.pcs> To: ctapang@easystreet.com, current@freebsd.org Subject: Re: FBSDBOOT.EXE X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Mike, Thanks for trying fbsdboot.exe. I need more information to fix it. I >would like to fix it, so please describe exactly what the problem is. What >do you mean by the "need to reboot the system to restore various vectors >that DOS destroys"? Do you mean that prior to executing the FreeBSD kernel >init routines, DOS does something to the loaded area? I'm sorry I can't find >any info on this either in the mail threads or in freebsd.org. Probably I'm >not looking hard enough, but I believe it would be more efficient to just >ask you. In a nutshell, there is a table of interrupt vectors which is set by the BIOS at boot time, which are used by the loader (and by the FreeBSD kernel, if VM86 is turned on). DOS, when it boots, loads itself into memory somewhere, and then changes the interrupt vectors to point to itself. The problem is, when the kernel/loader is loaded by fbsdboot.exe, DOS is overwritten. This results in the interrupt vectors pointing to garbage, which causes "bad things" (tm) when the they are used. Even if we don't stomp on DOS, I don't quite think that a BIOS call that ends up calling a DOS routine will do the right thing. There isn't any way (AFAIK) to restore the vectors to the original BIOS boot state. You may want to search the archives for "vm86" and "terry lambert", (IIRC), for some hypothetical solutions that have been proposed for this problem. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 21:55:40 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 4021914D9A for ; Mon, 17 May 1999 21:55:37 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id XAA17885; Mon, 17 May 1999 23:55:25 -0500 (CDT) Date: Mon, 17 May 1999 23:55:25 -0500 From: Tim Tsai To: Jonathan Lemon Cc: ctapang@easystreet.com, current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE Message-ID: <19990517235525.A17781@futuresouth.com> References: <199905180424.XAA02905@free.pcs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199905180424.XAA02905@free.pcs>; from Jonathan Lemon on Mon, May 17, 1999 at 11:24:37PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > DOS, when it boots, loads itself into memory somewhere, and then > changes the interrupt vectors to point to itself. How does Linux do it with loadlin? Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 23:37: 9 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 740AF15375 for ; Mon, 17 May 1999 23:37:07 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA27230; Tue, 18 May 1999 08:37:04 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905180637.IAA27230@freebsd.dk> Subject: Re: ATA and afd (LS-120): got it WORKING! In-Reply-To: from Brian Feldman at "May 18, 1999 0:12:48 am" To: green@unixhelp.org (Brian Feldman) Date: Tue, 18 May 1999 08:37:04 +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 Brian Feldman wrote: > Yes, I finally got it working! The explanation is in the patch, which I should > not need to explain again :) Hmm, Does it not work as is ?? It works on my LS120 drive, and a couble of others. Besides your hack doesn't find my ZIP drive, and makes it fail miserably. If its just that you are unsatisfied with only max 32K transfers, thats another matter, and stuff for later changes. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 23:48: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 1E27215150 for ; Mon, 17 May 1999 23:48:17 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA27270; Tue, 18 May 1999 08:48:14 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905180648.IAA27270@freebsd.dk> Subject: Re: IDE strangeness In-Reply-To: from Brian Feldman at "May 17, 1999 6:21:13 pm" To: green@unixhelp.org (Brian Feldman) Date: Tue, 18 May 1999 08:48:14 +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 Brian Feldman wrote: >> It seems Brian Feldman wrote: >> > I'm having two problems with IDE nowadays. >> > >> > 1. ATA doesn't work with LS-120. That's not new. But ATA does seem to crash on >> > me, and there's no dump() so I can't figure out why. > >Reply to my own problem: ATA crashed more often than wd, but they both crashed >with my old, faulty CPU. My K6-2 350 now works perfectly. Aha! >> Good news is that I've gotten ahold of a LS120 drive, so I can test this now. >> >> Bad news is that it has stopped working on my ZIP drive too :( > >That's bad, if it used to. LS-120 never worked under ATA, with or without >new-bus. But you say Zip always has. Well, it suddenly failed, and going over the driver again, I've no idea how it could have worked :) Too little sleep I guess... >> Something must have been screwed up since the newbus import, either in >> my driver (I feel at risk saying that it is not likely), or something else. > >I'm pretty sure your driver isn't screwed up, as I've tracked most of the >changes. Well, with update7 it should work, at least it does with both my ZIP and my LS120... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 17 23:54: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 EEEDD14DE9 for ; Mon, 17 May 1999 23:54:13 -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 2.12 #1) id 10jdl7-00016x-00; Tue, 18 May 1999 08:53:49 +0200 From: Sheldon Hearn To: Luoqi Chen Cc: Jos.Backus@nl.origin-it.com, current@FreeBSD.ORG Subject: Re: MFS still hosed In-reply-to: Your message of "Mon, 17 May 1999 13:02:29 -0400." <199905171702.NAA20057@lor.watermarkgroup.com> Date: Tue, 18 May 1999 08:53:49 +0200 Message-ID: <4274.927010429@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 May 1999 13:02:29 -0400, Luoqi Chen wrote: > Are you sure you have the latest -current? I committed a fix Friday > night. Hi Luoqi, I remade world and kernel (config -g -r) with yesterday's HEAD and still get a panic mounting MFS. My kernel config includes MFS but not MFS_ROOT. Shout if you want a trace. I haven't provided one here, since I'll need to copy it down by hand because I'm using the ATA* driver that's still under development and doesn't support crashdumps. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 1: 5:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 118D315421; Tue, 18 May 1999 01:05:43 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id RAA01690; Tue, 18 May 1999 17:35:41 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA24930; Tue, 18 May 1999 17:36:32 +0930 Date: Tue, 18 May 1999 17:36:30 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Tomer Weller Cc: FreeBSD Current , FreeBSD Ports Subject: Re: your mail In-Reply-To: <99050617135200.58638@Tomer.DrugsAreGood.org> 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, 6 May 1999, Tomer Weller wrote: > whenever i try to compile KDE software (ports also) i get this error, though > packages install fine. > i installed KDE from packages, i suspect that's the problem. I didn't see a response to this as I was going through my inbox, so apologies if this has already been answered: What version of FreeBSD are you running, and which compiler? If you're using egcs as your compiler (either running 4.0, or [23].x + egcs port, then you have to compile the KDE dependencies manually using the same compiler or it will not work. In other words, egcs produces C++ code which is not binary-compatible with that produced by gcc (e.g., the package). You can tell whether this is the case by looking at the error log produced by the port configure script. Kris > > this is from the kmp3 port, but happens with every piece of kde software : > > > checking for KDE... libraries /usr/local/lib, headers /usr/local/include > checking for extra includes... no > checking for extra libs... no > checking for kde headers installed... yes > checking for kde libraries installed... configure: error: your system fails at linking a small KDE application! > Check, if your compiler is installed correctly and if you have used the > same compiler to compile qt and kdelibs as you did use now > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > > > ====================================== > 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-ports" in the body of the message > ----- "That suit's sharper than a page of Oscar Wilde witticisms that's been rolled up into a point, sprinkled with lemon juice and jabbed into someone's eye" "Wow, that's sharp!" - Ace Rimmer and the Cat, _Red Dwarf_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 1:28:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (Postfix) with ESMTP id 77380150F7 for ; Tue, 18 May 1999 01:28:26 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id BAA01335; Tue, 18 May 1999 01:23:59 -0700 (PDT) Message-ID: <3741237F.F528C8FA@seattleu.edu> Date: Tue, 18 May 1999 01:23:27 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: obrien@NUXI.com Cc: Leif Neland , Marc van Woerkom , freebsd-current@FreeBSD.ORG Subject: Re: No sound (Ensoniq Audio PCI 1370) References: <199905151958.VAA14199@oranje.my.domain> <19990517105543.B47978@nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > > > Below follow dmesg output and kernel configuration. > > > > > device pcm0 at isa? port ? irq 10 drq 1 flags 0x0 > > > > I have this: > > > > device pcm0 at nexus? port ? irq 10 drq 1 flags 0x0 > > ^^^^^^ > > I would like to update ``sys/i386/isa/snd/README'' since it currently > does not have enough information to get a person going. Is the use of > "nexus" vs "isa" the offical way to go now days? I just use: device pcm0 and no more, since I only have a PCI card. Haven't cvsupped in about a week though. (I have no idea if this is correct or not. I removed the at... part in order to keep it from probing the isa stuff, for no other reason than I didn't want to see it.) > Also, what devices did people have to create to get sound and /dev/audio > working? (ie. cd /dev ; ./MAKEDEV foo) I think dmesg |grep pcm followed by cd /dev/; MAKEDEV foo will work, when foo is whatever pcm dsp you want working. SB128 has a patch to get two dsps working... -- Eric Hodel hodeleri@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 3:45:17 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 D4F9C1545F for ; Tue, 18 May 1999 03:45:13 -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 GAA38916; Tue, 18 May 1999 06:43:11 -0400 (EDT) Date: Tue, 18 May 1999 06:43:10 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: ATA and afd (LS-120): got it WORKING! In-Reply-To: <199905180637.IAA27230@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 May 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: > > Yes, I finally got it working! The explanation is in the patch, which I= should > > not need to explain again :) >=20 > Hmm, Does it not work as is ?? It works on my LS120 drive, and a couble > of others. Besides your hack doesn't find my ZIP drive, and makes it > fail miserably. In that case, I'll fix it to do a strstr or something like that. What's your ZIP drive say? >=20 > If its just that you are unsatisfied with only max 32K transfers, thats > another matter, and stuff for later changes. No, it does not work at all with that maximum set. I'm using the disk to ho= ld an FFS filesystem, and mounting it, BTW. See, in the old driver, it limited the transfer, but it ALSO queued the rest of the transfer. AFD doesn't, and I can tell this because I get random parts of kernel memory interspersed wi= th my files (that's the corruption), so I know all of the buffer is not being filled. You need to queue the rest of the transfer too. >=20 > -S=F8ren >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 Brian Feldman _ __ ___ ____ ___ ___ ___ =20 green@unixhelp.org _ __ ___ | _ ) __| \=20 FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 4: 5:42 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 787211546F for ; Tue, 18 May 1999 04:05:38 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA27765; Tue, 18 May 1999 13:05:35 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905181105.NAA27765@freebsd.dk> Subject: Re: ATA and afd (LS-120): got it WORKING! In-Reply-To: from Brian Feldman at "May 18, 1999 6:43:10 am" To: green@unixhelp.org (Brian Feldman) Date: Tue, 18 May 1999 13:05:35 +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 Brian Feldman wrote: >> It seems Brian Feldman wrote: >> > Yes, I finally got it working! The explanation is in the patch, which I should >> > not need to explain again :) >> >> Hmm, Does it not work as is ?? It works on my LS120 drive, and a couble >> of others. Besides your hack doesn't find my ZIP drive, and makes it >> fail miserably. > >In that case, I'll fix it to do a strstr or something like that. What's >your ZIP drive say? Have to get home to power up the sucker first, but if below doesn't work on all systems, it will still break on the ZIP then.. >> If its just that you are unsatisfied with only max 32K transfers, thats >> another matter, and stuff for later changes. > >No, it does not work at all with that maximum set. I'm using the disk to hold >an FFS filesystem, and mounting it, BTW. See, in the old driver, it limited >the transfer, but it ALSO queued the rest of the transfer. AFD doesn't, and >I can tell this because I get random parts of kernel memory interspersed with >my files (that's the corruption), so I know all of the buffer is not being >filled. You need to queue the rest of the transfer too. I use mine to hold a FFS filesystem too, infact I'm booting from it :) I know I cut off the transfer length, but I also return the missing size in b_resid, so the kernel _should_ come back with the rest of the transfer in a new request or at least fail on the unsatisfied request, and on my system it does seem to work... If this doesn't work in all cases, some other part of the kernel is broken IMHO. I thought of minphys once, but that seems not to work anymore either... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 5: 7: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 0227115655 for ; Tue, 18 May 1999 05:06:15 -0700 (PDT) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id QAA39738 for ; Tue, 18 May 1999 16:06:14 +0400 (MSD) (envelope-from camel@avias.com) From: Ilya Naumov Reply-To: camel@avias.com To: current@freebsd.org Subject: sane-1.00 port Date: Tue, 18 May 1999 16:02:11 +0400 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99051816061300.00444@camel.avias.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i cannot build sane -1.00 ports (ports/graphics/sane-1.00) for a long time under FreeBSD. i've tried to contact with maintainer of this port (gary@hotlava.com), but he doesn't respont. could anyone fix it? -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 5: 9:17 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 0E8AD15676 for ; Tue, 18 May 1999 05:08:44 -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 WAA12446; Tue, 18 May 1999 22:08:41 +1000 Date: Tue, 18 May 1999 22:08:41 +1000 From: Bruce Evans Message-Id: <199905181208.WAA12446@godzilla.zeta.org.au> To: green@unixhelp.org, sos@freebsd.dk Subject: Re: ATA and afd (LS-120): got it WORKING! Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I know I cut off the transfer length, but I also return the missing >size in b_resid, so the kernel _should_ come back with the rest of >the transfer in a new request or at least fail on the unsatisfied >request, and on my system it does seem to work... >If this doesn't work in all cases, some other part of the kernel is >broken IMHO. I thought of minphys once, but that seems not to work >anymore either... Using a driver-specific minphys is the correct method for unbuffered i/o, especially for tapes. This was recently made harder to use by replacing the specialised driver read/write routines by general ones (physread/physwrite). minphys and b_resid don't work for buffered i/o. vfs_bio.c doesn't even look at b_resid, so short i/o's are considered to have been complete. This is not much of a problem, because buffered i/o's are limited to MAXBSIZE (64K), and filesystems shouldn't have partial fs-blocks at the end of a disk. Buffered i/o's larger than MAXBSIZE can only occur for clustered i/o's if the driver supports them. E.g., the wd driver can easily transfer 255 sectors and it sets d_maxio to 248 so that clusters up to size 124K get created. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 5: 9:56 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 B7872155A6 for ; Tue, 18 May 1999 05:06:50 -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 IAA09218 for ; Tue, 18 May 1999 08:06:49 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA16070; Mon, 17 May 1999 14:26:25 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id OAA76104 for freebsd-current@freebsd.org; Mon, 17 May 1999 14:26:18 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905171826.OAA76104@bb01f39.unx.sas.com> Subject: Fatal Trap 12 (-current kernel w/MFS) To: freebsd-current@freebsd.org Date: Mon, 17 May 1999 14:26:18 -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, For those of you who know more than I.... When a -current kernel boots up, it dies when trying to mount /tmp as an mfs. Fatal Trap 12: page fault while in kernel mode fault virtual address = 0x9d2c0b38 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0170b44 stack pointer = 0x10:0xc7bbbd84 frame pointer = 0x10:0xc7bbbdb0 code segment = base 0x0, limit 0xfff, type=0x1b DPL 0, pres 1, def32 1, gran 1 processor eflags = interupt enabled, resume, IOPL=0 current process = 39 (mount_mfs) interrupt mask = trap number = 12 If I remove MFS & MFS_ROOT from the kernel and comment out the /tmp mfs mount from /etc/fstab, the kernel boots correctly. #------- Kernel config ----------- machine "i386" cpu "I686_CPU" ident FreeBSD maxusers 128 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols # # Enable Posix priority scheduling # #options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" #options "_KPOSIX_VERSION=199309L" controller isa0 #controller eisa0 controller pci0 controller dpt0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port IO_WD2 irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 device acd0 #IDE CD-ROM device wfd0 #IDE Floppy (e.g. LS-120) # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. controller ahc0 controller scbus0 device da0 device sa0 device pass0 device cd0 #Only need one of these, the code dynamically grows # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 # # sio: serial ports (see sio(4)) # device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # # Parallel-Port Bus # #controller ppbus0 #device lpt0 at ppbus? # Parallel Printer # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device fxp0 device xl0 device ti0 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 64 pseudo-device gzip # Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device ccd 4 #Concatenated disk driver pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM options SYSVSEM options SYSVMSG options USER_LDT #allow user-level control of i386 ldt # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. #pseudo-device bpfilter 4 #Berkeley packet filter # USB support #controller uhci0 #controller ohci0 #controller usb0 # # for the moment we have to specify the priorities of the device # drivers explicitly by the ordering in the list below. This will # be changed in the future. # #device ums0 #device ukbd0 #device ulpt0 #device uhub0 #device ucom0 #device umodem0 #device hid0 #device ugen0 # #options USB_DEBUG #options USBVERBOSE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 5:14:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 27F7B155A6 for ; Tue, 18 May 1999 05:13:34 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup1-35.iptelecom.net.ua [212.42.68.162]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id PAA16147; Tue, 18 May 1999 15:13:21 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.2) with ESMTP id PAA31610; Tue, 18 May 1999 15:11:49 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <37415904.967C7736@altavista.net> Date: Tue, 18 May 1999 15:11:48 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: UPDATE7: ATA/ATAPI driver new version available. References: <199905171601.SAA25465@freebsd.dk> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >     ISA only configs wont compile. >         Fixed. Unfortunately it still doesn't work on my Toshiba 445CDX notebook (it seems that driver isn't probed at all - no ata messages visible on boot time). I can't attach dmesg output because system can't mount root f/s and my floppy forgotten at home :( Following is my config entries (I've tried with and without ata0 line): controller      ata0 controller      ata1    at isa? port IO_WD1 irq 14 controller      ata2    at isa? port IO_WD2 irq 15   Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 5:21: 6 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 7BD6B14DB5 for ; Tue, 18 May 1999 05:20:31 -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 WAA13826; Tue, 18 May 1999 22:20:30 +1000 Date: Tue, 18 May 1999 22:20:30 +1000 From: Bruce Evans Message-Id: <199905181220.WAA13826@godzilla.zeta.org.au> To: green@unixhelp.org, sos@freebsd.dk Subject: Re: ATA and afd (LS-120): got it WORKING! Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> If its just that you are unsatisfied with only max 32K transfers, thats >> another matter, and stuff for later changes. > >No, it does not work at all with that maximum set. I'm using the disk to hold >an FFS filesystem, and mounting it, BTW. See, in the old driver, it limited >the transfer, but it ALSO queued the rest of the transfer. AFD doesn't, and >I can tell this because I get random parts of kernel memory interspersed with >my files (that's the corruption), so I know all of the buffer is not being >filled. You need to queue the rest of the transfer too. This can probably be "fixed" by turning off clustering. Clustering is only a large optimisation for slow disks like ZIPs :-]. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 5:50:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id DE68814BEC for ; Tue, 18 May 1999 05:49:45 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id HAA90419; Tue, 18 May 1999 07:49:43 -0500 (CDT) (envelope-from bob) Date: Tue, 18 May 1999 07:49:43 -0500 From: Bob Willcox To: Luoqi Chen Cc: current list Subject: Re: panic: page fault (apparently caused by mount_mfs) Message-ID: <19990518074943.A90395@luke.pmr.com> Reply-To: Bob Willcox References: <199905180342.XAA25777@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199905180342.XAA25777@lor.watermarkgroup.com>; from Luoqi Chen on Mon, May 17, 1999 at 11:42:21PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yep! The patch seems to have fixed the problem! :-) Thanks Luoqi!! Bob On Mon, May 17, 1999 at 11:42:21PM -0400, Luoqi Chen wrote: > > I have been making world each time after cvsupping so I would expect the > > mfs kld module to be getting rebuilt and it appears to be up-to-date: > > > > -r-xr-xr-x 1 root wheel 12778 May 17 13:34 /modules/mfs.ko > > > > Also, both my custom kernel config file and the GENERIC config file > > include "options MFS" so mfs should not be getting loaded, right? > > > > Thanks, > > Bob > > > > > > > > -lq > > > > -- > > Bob Willcox The man who follows the crowd will usually get no > > bob@luke.pmr.com further than the crowd. The man who walks alone is > > Austin, TX likely to find himself in places no one has ever > > been. -- Alan Ashley-Pitt > > > Would you try this patch? > > Index: kern_conf.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/kern_conf.c,v > retrieving revision 1.39 > diff -u -r1.39 kern_conf.c > --- kern_conf.c 1999/05/12 13:06:34 1.39 > +++ kern_conf.c 1999/05/18 03:27:36 > @@ -182,7 +182,7 @@ > uintptr_t i = (uintptr_t)x; > > #ifdef DEVT_FASCIST > - return(253 - ((i >> 8) & 0xff)); > + return(255 - ((i >> 8) & 0xff)); > #else > return((i >> 8) & 0xff); > #endif > @@ -200,7 +200,7 @@ > makedev(int x, int y) > { > #ifdef DEVT_FASCIST > - return ((dev_t) (((253 - x) << 8) | y)); > + return ((dev_t) (((255 - x) << 8) | y)); > #else > return ((dev_t) ((x << 8) | y)); > #endif -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 6:23:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id 3E078156D6 for ; Tue, 18 May 1999 06:22:43 -0700 (PDT) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id IAA08555 for ; Tue, 18 May 1999 08:22:47 -0500 (CDT) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id IAA08551 for ; Tue, 18 May 1999 08:22:46 -0500 (CDT) Message-ID: <004101bea131$8291df60$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: Sound Strangeness Date: Tue, 18 May 1999 08:22:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a Yamaha-SA3 card built into my motherboard. I uses the pcm drivers for sound. My system is current as of two days ago. I just installed KDE-1.1.1 (curious about performance) and I was testing out the one and only sound that seems to come with it. It seems that the sound device is buffering sound for a long period of time. The first time sound is set to the audio device it plays right away. The second and subsequent time that sound is sent to the device there is a considerable delay before the sound is played. I believe the files are just .wav (pcm) files. Has anybody else experienced this and can it be blamed upon KDE or is it a driver problem. I don't recall having this problem under Linux, but I can't remember if it was KDE 1.1.1 or KDE 1.1 that I had installed at that time, so I am not sure if that rules out KDE or not. Tom Veldhouse veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 8:16:37 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 DD82414DAC for ; Tue, 18 May 1999 08:15:50 -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.00 #1) id 10jlaU-0000B1-00; Tue, 18 May 1999 17:15:22 +0200 From: Sheldon Hearn To: Luoqi Chen Cc: Jos.Backus@nl.origin-it.com, current@FreeBSD.ORG Subject: Re: MFS still hosed In-reply-to: Your message of "Tue, 18 May 1999 08:53:49 +0200." <4274.927010429@axl.noc.iafrica.com> Date: Tue, 18 May 1999 17:15:21 +0200 Message-ID: <682.927040521@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 May 1999 08:53:49 +0200, Sheldon Hearn wrote: > I remade world and kernel (config -g -r) with yesterday's HEAD and still > get a panic mounting MFS. My kernel config includes MFS but not > MFS_ROOT. > > Shout if you want a trace. I haven't provided one here, since I'll need > to copy it down by hand because I'm using the ATA* driver that's still > under development and doesn't support crashdumps. I think I know why a lot of people _aren't_ seeing this panic: it doesn't show up if you #undef DEVT_FASCIST in kern/kern_conf.c . I found this by accident because I can't get a crash dump using the wd driver. I get dumping to dev (0, 131089), offset 524288 dump device bad Suspecting this whole major/minor/dev_t business, I #undef'd DEVT_FASCIST and all of a sudden I can't reproduce the panic to test dumps. ;-) I'm not whining, I just want to make sure that it's a known issue, not something that's completely resolved. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 8:32: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (steve.cioe.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id E7BF61510A for ; Tue, 18 May 1999 08:31:24 -0700 (PDT) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id KAA00546 for freebsd-current@freebsd.org; Tue, 18 May 1999 10:31:22 -0500 (EST) (envelope-from steve) Date: Tue, 18 May 1999 10:31:22 -0500 (EST) From: Steven Ames Message-Id: <199905181531.KAA00546@virtual-voodoo.com> To: freebsd-current@freebsd.org Subject: ed0/probe problem in 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last night switched from 3.1 to 4.0. Smooth transition. The only error I've seen is one of my ethernet cards is no longer detected. In the previous kernel (3.1-STABLE) I had the following config line: device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 When the system booted it would detect 'ed1' on the PCI bus and 'ed0' on the isa bus. All was good. Under 4.0 things changed. Now when the system boots the PCI card is assigned to 'ed0' and then a message is printed saying 'ed0' is already used, using next number. But my ISA card isn't probed. I switched the ISA card to 'ed1'. The 'already used' message stopped but my ISA card is still not detected. The PCI card is: ed0: irq 11 at device 15.0 on pci0 ed0: address 52:54:00:dc:08:ca, type NE2000 (16 bit) the ISA card is MIA. I don't even get a 'ed1 not found at' message. Can anyone point me in the right direction? Or tell me how to make the device probing more verbose? -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 8:49:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 98E46152D0 for ; Tue, 18 May 1999 08:48:35 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-15-84.camtech.net.au [203.55.243.84]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id BAA12083; Wed, 19 May 1999 01:23:45 +0930 (CST) Message-ID: <37418C29.DEECA1AC@camtech.com.au> Date: Wed, 19 May 1999 01:20:01 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: current@FreeBSD.ORG, dawes@rf900.physics.usyd.edu.au, green@unixhelp.org, jkh@zippy.cdrom.com Subject: XFree86 xsetpointer causes silo overflows (Was: Re: Fixed my MAMEd sio problem.) References: <199905170127.LAA04147@godzilla.zeta.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have confirmed that the problem occurs if I just do: xsetpointer Joystick sleep 1 xsetpointer pointer So M.A.M.E. is unrelated to the problem as Bruce Evans would suggest. So the problem appears to be with XFree86 not closing the joystick device after I've used it as a pointer with 'xsetpointer'. I am sure I am using xsetpointer correctly as I can use my PC joystick as a pointing device (once I calibrate it). I was just using xsetpointer with an incorrectly calibrated joystick so it moved the pointer to the top left corner of the screen in my xmame.sh shell script (I'd like to know how to do this another way). Bruce Evans wrote: > > >Just so you all know (the list included) how I have fixed my silo > >overflow problem which occurred while running xmame (and after I quit > >until I restarted the X server).... > > > >I have found the problem doesn't occur if I remove the following lines > >from the shell script I use to start xmame: > > > >xsetpointer Joystick > >sleep 1 > >xsetpointer pointer > > FreeBSD's joystick driver certainly causes silo overflows. It disables > CPU interrupts and polls for 2 msec. For 16550 serial hardware, this may > cause loss of 21 characters at 115200 bps (23 characters arriving in > 2 msec less 2 characters of buffering provided by the 16550 fifo above > the trigger level). If sio used a more conservative trigger level of 8, > then then the loss would be limited to only 15 characters. > > >With those lines in the script I had to restart the X-server after > >using xmame or I'd get continuous silo overflows. > > Closing the joystick device should also work. > > The joystick driver shouldn't disable CPU interrupts or mask clock > interrupts. > > Bruce -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 8:57:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx.nsu.ru (mx.nsu.ru [193.124.215.71]) by hub.freebsd.org (Postfix) with ESMTP id 6B6F6156FB for ; Tue, 18 May 1999 08:56:59 -0700 (PDT) (envelope-from semen@iclub.nsu.ru) Received: from iclub.nsu.ru (semen@iclub.nsu.ru [193.124.222.66]) by mx.nsu.ru (8.9.1/8.9.0) with ESMTP id WAA29319; Tue, 18 May 1999 22:52:23 +0700 (NOVST) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.9.3/8.8.5) with ESMTP id WAA03993; Tue, 18 May 1999 22:50:55 +0700 (NSS) Date: Tue, 18 May 1999 22:50:55 +0700 (NSS) From: Ustimenko Semen To: Narvi Cc: Alfred Perlstein , Garance A Drosehn , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: Nt source licenses... 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, 16 May 1999, Narvi wrote: > > On Sat, 15 May 1999, Alfred Perlstein wrote: > > > On Sat, 15 May 1999, Narvi wrote: > > > > > > > > On Fri, 14 May 1999, Garance A Drosehn wrote: > > > > > > > At 3:51 PM +0700 5/12/99, Ustimenko Semen wrote: > > > > > Are we going to get this license? I am interested in NTFS > > > > > source code a lot... > > > > > > > > I would be very careful about getting an NT source license if > > > > your intention is to write NTFS support for some other operating > > > > system. Microsoft is not doing this licensing for the benefit of > > > > mankind, they are doing it to attract college-type users to > > > > sticking with WinNT over open-source unixes. > > > > > > > > The last thing we need is some code from WinNT which causes us > > > > to be sued by Microsoft... > > > > > > > > > > It would probably be very unwise for the project to get get the licence. > > > > > > However, considering that we support loadable filesystem modules, somebody > > > adventurous enough can get the licence and write a (separate distributed, > > > possibly even only as binary) module. > > > > > > Downloading a kld module from the net definately does not "taint" your > > > mind. > > > > I'm unsure what the fuss is over, don't we have a kld to read NTFS already? > > > > How about writing? > Yes, there is no writing. The problem is that NTFS is ``Logging'' file system. Current documentation is totaly reverse developed, and it's very difficult to hack $LogFile... Anyway we have to read the license before discussing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 9:21:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles506.castles.com [208.214.165.70]) by hub.freebsd.org (Postfix) with ESMTP id 3276915421 for ; Tue, 18 May 1999 09:21:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA03981; Tue, 18 May 1999 09:16:59 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905181616.JAA03981@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: ATA and afd (LS-120): got it WORKING! In-reply-to: Your message of "Tue, 18 May 1999 06:43:10 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Tue, 18 May 1999 09:16:59 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > = > No, it does not work at all with that maximum set. I'm using the disk t= o hold > an FFS filesystem, and mounting it, BTW. See, in the old driver, it lim= ited > the transfer, but it ALSO queued the rest of the transfer. AFD doesn't,= and > I can tell this because I get random parts of kernel memory intersperse= d with > my files (that's the corruption), so I know all of the buffer is not be= ing > filled. You need to queue the rest of the transfer too. I wrote the original code for this in wfd, and it requeues the transfer for just this reason; the layer above doesn't retry the block operation for the remaining residual. I'm not sure this is an error; it's too long since I looked at the code, but I think there are some bad things that can happen (or were suggested might happen) if you persist in retrying the physical I/O. -- = \\ 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 Tue May 18 10: 4:54 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 5005114EDB for ; Tue, 18 May 1999 10:04:50 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id TAA28475; Tue, 18 May 1999 19:04:39 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905181704.TAA28475@freebsd.dk> Subject: Re: ATA and afd (LS-120): got it WORKING! In-Reply-To: <199905181616.JAA03981@dingo.cdrom.com> from Mike Smith at "May 18, 1999 9:16:59 am" To: mike@smith.net.au (Mike Smith) Date: Tue, 18 May 1999 19:04:38 +0200 (CEST) Cc: green@unixhelp.org, 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 Mike Smith wrote: > > > > No, it does not work at all with that maximum set. I'm using the disk to hold > > an FFS filesystem, and mounting it, BTW. See, in the old driver, it limited > > the transfer, but it ALSO queued the rest of the transfer. AFD doesn't, and > > I can tell this because I get random parts of kernel memory interspersed with > > my files (that's the corruption), so I know all of the buffer is not being > > filled. You need to queue the rest of the transfer too. > > I wrote the original code for this in wfd, and it requeues the transfer > for just this reason; the layer above doesn't retry the block operation > for the remaining residual. I'm not sure this is an error; it's too > long since I looked at the code, but I think there are some bad things > that can happen (or were suggested might happen) if you persist in > retrying the physical I/O. Well, the code uses d_maxio in many places, just not all regrettably :( That would be the way to solve this... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 11: 4: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E940814CBF; Tue, 18 May 1999 11:03:57 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id LAA53848; Tue, 18 May 1999 11:03:48 -0700 (PDT) (envelope-from obrien) Message-ID: <19990518110348.A53829@nuxi.com> Date: Tue, 18 May 1999 11:03:48 -0700 From: "David O'Brien" To: camel@avias.com, current@FreeBSD.ORG Cc: ports@FreeBSD.ORG Subject: Re: sane-1.00 port Reply-To: obrien@NUXI.com References: <99051816061300.00444@camel.avias.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <99051816061300.00444@camel.avias.com>; from Ilya Naumov on Tue, May 18, 1999 at 04:02:11PM +0400 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > i cannot build sane -1.00 ports (ports/graphics/sane-1.00) for a long time > under FreeBSD. i've tried to contact with maintainer of this > port (gary@hotlava.com), but he doesn't respont. could anyone fix it? Amancio Hasty has sent me a fix for this, but I have not had time to test and commit it. You can find it at ftp://relay.nuxi.com/pub/FreeBSD/sane-1.0.1-portball.tar.gz. (any committer that wishes to be me to checking and committing this, please be my guest) -- -- David (obrien@NUXI.com -or- obrien@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 May 18 12: 7:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from netcom14.netcom.com (netcom14.netcom.com [192.100.81.126]) by hub.freebsd.org (Postfix) with ESMTP id D760014F88; Tue, 18 May 1999 12:07:19 -0700 (PDT) (envelope-from hasty@netcom.com) Received: (from hasty@localhost) by netcom14.netcom.com (8.8.5-r-beta/8.8.5/(NETCOM v1.02)) id MAA20742; Tue, 18 May 1999 12:06:54 -0700 (PDT) Date: Tue, 18 May 1999 12:06:54 -0700 (PDT) From: Amancio Hasty Jr Message-Id: <199905181906.MAA20742@netcom14.netcom.com> To: camel@avias.com, current@FreeBSD.ORG, obrien@NUXI.com Subject: Re: sane-1.00 port Cc: ports@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In case that there are any further problems with SANE I am kind-off line due to my ISP (www.dspeed.net) disappearing from the Net :( Time to look for a different ISP provider Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 12:42: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (steve.cioe.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 8B19D14EDA for ; Tue, 18 May 1999 12:41:59 -0700 (PDT) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id OAA00952 for freebsd-current@freebsd.org; Tue, 18 May 1999 14:42:03 -0500 (EST) (envelope-from steve) Date: Tue, 18 May 1999 14:42:03 -0500 (EST) From: Steven Ames Message-Id: <199905181942.OAA00952@virtual-voodoo.com> To: freebsd-current@freebsd.org Subject: Re: ed0/probe problem in 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 > > You should probably show the list what device lines you are using for > current, since config barfs on the above line under current: > > config: line 52: `net' interrupt label obsolete Fair enough: device ed1 at isa? port 0x280 irq 10 iomem 0xd8000 *grin* -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 14:21:52 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 5380714FB3 for ; Tue, 18 May 1999 14:21:44 -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 QAA18450 for ; Tue, 18 May 1999 16:46:41 -0500 (EST) Date: Tue, 18 May 1999 16:46:39 -0500 (EST) From: Alfred Perlstein To: current@freebsd.org Subject: nodump is not a dump routine. 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 wondering why when the system dumpdev is set to a device that doesn't have a read dump routine (nodump()) why it lies about the dump being successful. Index: kern_shutdown.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_shutdown.c,v retrieving revision 1.52 diff -u -r1.52 kern_shutdown.c --- kern_shutdown.c 1999/05/12 22:30:46 1.52 +++ kern_shutdown.c 1999/05/19 00:38:43 @@ -387,6 +387,10 @@ printf("dump "); switch ((*bdevsw(dumpdev)->d_dump)(dumpdev)) { + case ENODEV: + printf("device has no dump routine\n"); + break; + case ENXIO: printf("device bad\n"); break; shouldn't src/sys/i386/i386/autoconf.c, and src/sys/alpha/alpha/autoconf.c decline to set the dump device to a device that has nodump() as its dump routine? With the recent udev_t <-> dev_t changes and alpha not being in sync with it (or so it seems) I don't feel comfortable suggesting a patch for it, even though it appears to be quite simple. one other question, considering the newbus stuff, shouldn't there be a way to get the text string of the dump device somehow so "dumpon" with no arguments can print out the current value without scanning /dev for a device that matches it? or does that still have to wait for devfs? thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 16:58:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (Postfix) with ESMTP id 6A32E15322 for ; Tue, 18 May 1999 16:58:14 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with SMTP id QAA04560; Tue, 18 May 1999 16:57:55 -0700 Message-ID: <00b201bea18a$93afbfc0$0d787880@apex.tapang> From: "Carlos C. Tapang" To: "Jonathan Lemon" , Subject: Re: FBSDBOOT.EXE Date: Tue, 18 May 1999 17:00:16 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >In a nutshell, there is a table of interrupt vectors which is set >by the BIOS at boot time, which are used by the loader (and by the >FreeBSD kernel, if VM86 is turned on). > Thanks, Jonathan. Are any of the following TRUE? 1. FreeBSD is affected by these vectors only if VM86 is turned ON. 2. If somebody is using VM86, s/he must be using DOSEMU or some other DOS emulator also (I can't think of anything else one would use VM86 for). 3. DOSEMU or any other DOS emulator re-initializes the DOS vectors for virtualization. Basically, what I am guessing is that probably we can fix the problem during vm86 or DOSEMU initialization. I am going to enable vm86 on my system and see what happens. Right now I am not experiencing any problems, and that's probably because I do not have vm86 enabled. --Carlos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 17: 5: 7 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 64DDD1530F for ; Tue, 18 May 1999 17:05:02 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id RAA18549; Tue, 18 May 1999 17:04:57 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 18 May 1999 17:04:56 -0700 (PDT) From: Doug White To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Fatal Trap 12 (-current kernel w/MFS) In-Reply-To: <199905171826.OAA76104@bb01f39.unx.sas.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, 17 May 1999, John W. DeBoskey wrote: > For those of you who know more than I.... When a -current > kernel boots up, it dies when trying to mount /tmp as an mfs. > > Fatal Trap 12: page fault while in kernel mode Fixed it earlier this week or last week in v1.63 (14 May) of /sys/ufs/mfs/mfs_vfsops.c. Resup. It dies in checkalias() due to improprieties by mfs. 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 Tue May 18 17:10:17 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 E033F14D52 for ; Tue, 18 May 1999 17:10:14 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id RAA20337; Tue, 18 May 1999 17:10:11 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 18 May 1999 17:10:10 -0700 (PDT) From: Doug White To: "Thomas T. Veldhouse" Cc: FreeBSD-Current Subject: Re: Sound Strangeness In-Reply-To: <004101bea131$8291df60$236319ac@w142844.carlson.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 Tue, 18 May 1999, Thomas T. Veldhouse wrote: > I have a Yamaha-SA3 card built into my motherboard. I uses the pcm drivers > for sound. My system is current as of two days ago. > > I just installed KDE-1.1.1 (curious about performance) and I was testing out > the one and only sound that seems to come with it. It seems that the sound > device is buffering sound for a long period of time. The first time sound > is set to the audio device it plays right away. The second and subsequent > time that sound is sent to the device there is a considerable delay before > the sound is played. I believe the files are just .wav (pcm) files. Has > anybody else experienced this and can it be blamed upon KDE or is it a > driver problem. I don't recall having this problem under Linux, but I can't > remember if it was KDE 1.1.1 or KDE 1.1 that I had installed at that time, > so I am not sure if that rules out KDE or not. This is usually indicitive of a resource problem with your soundcard (bad IRQ). Check your settings. 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 Tue May 18 18: 2:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (steve.cioe.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 0E86414CB0 for ; Tue, 18 May 1999 18:02:35 -0700 (PDT) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id UAA00351; Tue, 18 May 1999 20:02:31 -0500 (EST) (envelope-from steve) Date: Tue, 18 May 1999 20:02:31 -0500 (EST) From: Steven Ames Message-Id: <199905190102.UAA00351@virtual-voodoo.com> To: mtaylor@cybernet.com Subject: Re: ed0/probe problem in 4.0-CURRENT Cc: freebsd-current@freebsd.org In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Did all of that and a 'set boot_verbose'. Lots more data but I'm still not even seeing a probe for ethernet cards on the isa bus. I have 'ed1' and 'ep1' enabled in the kernel: device ed1 at isa? port 0x340 irq 10 iomem 0xd8000 device ep1 at isa? port 0x340 irq 10 And it is certainly not being detected. This behavior is new to 4.0-CURRENT. -Steve > At the second stage boot prompt, did you try "-v"? > > If you're at the 3rd stage boot prompt, use "boot -v". > > You'll get lots and lots of messages... > > > -Mark Taylor > NetMAX Developer > mtaylor@cybernet.com > > > On 18-May-99 Steven Ames wrote: > > > > Wow. I don't think that should ever happen but at this point I'll > > try a lot of things :) > > > > Tried it. didn't work. > > > > really, isn't there a way to enable more verbose probing so that > > it says 'ed0 not found at 0x280' or some such? > > > > > >> When I upgraded, my ed0 became ep0.... you might want to try that..... > >> > >> > >> Brandon Hicks - Gate Keeper Technologies > >> "Trixster" > >> bhicks@gatekeep.net > >> > >> > >> -----Original Message----- > >> From: Steven Ames > >> To: freebsd-hackers@FreeBSD.ORG > >> Date: Tuesday, May 18, 1999 10:10 AM > >> Subject: ed0/probe problem in 4.0-CURRENT > >> > >> > >> > > >> >Last night switched from 3.1 to 4.0. Smooth transition. The only > >> >error I've seen is one of my ethernet cards is no longer detected. > >> > > >> >In the previous kernel (3.1-STABLE) I had the following config > >> >line: > >> > > >> >device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 > >> > > >> >When the system booted it would detect 'ed1' on the PCI bus > >> >and 'ed0' on the isa bus. All was good. Under 4.0 things > >> >changed. > >> > > >> >Now when the system boots the PCI card is assigned to 'ed0' > >> >and then a message is printed saying 'ed0' is already used, > >> >using next number. But my ISA card isn't probed. I switched > >> >the ISA card to 'ed1'. The 'already used' message stopped > >> >but my ISA card is still not detected. > >> > > >> >The PCI card is: > >> > > >> >ed0: irq 11 at device 15.0 on pci0 > >> >ed0: address 52:54:00:dc:08:ca, type NE2000 (16 bit) > >> > > >> >the ISA card is MIA. I don't even get a 'ed1 not found at' message. > >> >Can anyone point me in the right direction? Or tell me how to > >> >make the device probing more verbose? > >> > > >> > -Steve > >> > > >> > > >> >To Unsubscribe: send mail to majordomo@FreeBSD.org > >> >with "unsubscribe freebsd-hackers" in the body of the message > >> > > >> > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 18:44:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (steve.cioe.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 9D5B614E38; Tue, 18 May 1999 18:44:30 -0700 (PDT) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id UAA00340; Tue, 18 May 1999 20:44:29 -0500 (EST) (envelope-from steve) Date: Tue, 18 May 1999 20:44:29 -0500 (EST) From: Steven Ames Message-Id: <199905190144.UAA00340@virtual-voodoo.com> To: freebsd-current@freebsd.org Subject: ed0/probe solved (Was: re: ed0/probe problem in 4.0-CURRENT) Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG *sigh* No suprise here. As 90% of these things are this was yet another Dumb User Error. I had a base address conflict that kept the card from being probed. Thanks for everyone's help. As always FreeBSD is working just great! -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 18:44:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 8679F14E38 for ; Tue, 18 May 1999 18:44:34 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id UAA03932; Tue, 18 May 1999 20:44:33 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id UAA03011; Tue, 18 May 1999 20:44:31 -0500 Message-ID: <19990518204431.15136@right.PCS> Date: Tue, 18 May 1999 20:44:31 -0500 From: Jonathan Lemon To: "Carlos C. Tapang" Cc: current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE References: <00b201bea18a$93afbfc0$0d787880@apex.tapang> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <00b201bea18a$93afbfc0$0d787880@apex.tapang>; from Carlos C. Tapang on May 05, 1999 at 05:00:16PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On May 05, 1999 at 05:00:16PM -0700, Carlos C. Tapang wrote: > > > >In a nutshell, there is a table of interrupt vectors which is set > >by the BIOS at boot time, which are used by the loader (and by the > >FreeBSD kernel, if VM86 is turned on). > > > Thanks, Jonathan. Are any of the following TRUE? > 1. FreeBSD is affected by these vectors only if VM86 is turned ON. Um, I would say that is true. Robert Nordier or Mike Smith may want to step in here and correct me as to what the loader is doing, but I think the kernel only uses the interrupt vectors if VM86 is on. > 2. If somebody is using VM86, s/he must be using DOSEMU or some other DOS > emulator also (I can't think of anything else one would use VM86 for). Not true. VM86 is also required to support VESA. Also, it is used for reliable memory detection (which is why I want to make it mandatory). No more "My Stinkpad only detected 64M, what do I do now??!" questions. > 3. DOSEMU or any other DOS emulator re-initializes the DOS vectors for > virtualization. True - ``doscmd'' has a virtual copy of the vectors that it initializes itself, and doesn't use the actual DOS vectors at all. > Basically, what I am guessing is that probably we can fix the problem during > vm86 or DOSEMU initialization. I am going to enable vm86 on my system and > see what happens. Right now I am not experiencing any problems, and that's > probably because I do not have vm86 enabled. The problem only comes into play during case 2; where the kernel actually calls the BIOS. The difficulty is that while FBSDBOOT.EXE may work in some cases, it is not guaranteed to work in _all_ cases (which causes a support nightmare). -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 19: 4:59 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 BC12314CE0 for ; Tue, 18 May 1999 19:04:57 -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 MAA25133; Wed, 19 May 1999 12:04:54 +1000 Date: Wed, 19 May 1999 12:04:54 +1000 From: Bruce Evans Message-Id: <199905190204.MAA25133@godzilla.zeta.org.au> To: luoqi@watermarkgroup.com, sheldonh@uunet.co.za Subject: Re: MFS still hosed Cc: current@FreeBSD.ORG, Jos.Backus@nl.origin-it.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I think I know why a lot of people _aren't_ seeing this panic: it >doesn't show up if you #undef DEVT_FASCIST in kern/kern_conf.c . #undef DEVT_FASICIST weakens tthe error detection. >I found this by accident because I can't get a crash dump using the wd >driver. I get > >dumping to dev (0, 131089), offset 524288 >dump device bad 131089 is the ordinary minor number 0x20011 (slice 2, unit 2, partition 1) (for wd2s1b). The dev_t changes obfuscated it by printing it in %d format instead of as part of the dev number in [0x]%x format. They should have used %#x format. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 20: 0:36 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 E91AE150C9 for ; Tue, 18 May 1999 20:00:31 -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 NAA31984; Wed, 19 May 1999 13:00:24 +1000 Date: Wed, 19 May 1999 13:00:24 +1000 From: Bruce Evans Message-Id: <199905190300.NAA31984@godzilla.zeta.org.au> To: bright@rush.net, current@FreeBSD.ORG Subject: Re: nodump is not a dump routine. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >i'm wondering why when the system dumpdev is set to a device that >doesn't have a read dump routine (nodump()) why it lies about the >dump being successful. Just another bug. >Index: kern_shutdown.c >=================================================================== >RCS file: /home/ncvs/src/sys/kern/kern_shutdown.c,v >retrieving revision 1.52 >diff -u -r1.52 kern_shutdown.c >--- kern_shutdown.c 1999/05/12 22:30:46 1.52 >+++ kern_shutdown.c 1999/05/19 00:38:43 >@@ -387,6 +387,10 @@ > printf("dump "); > switch ((*bdevsw(dumpdev)->d_dump)(dumpdev)) { > >+ case ENODEV: >+ printf("device has no dump routine\n"); >+ break; >+ Also, the default case should print "failed", and only the 0 case should print "succeeded". >shouldn't >src/sys/i386/i386/autoconf.c, and >src/sys/alpha/alpha/autoconf.c decline to set the dump device >to a device that has nodump() as its dump routine? setdumpdev() probably shouldn't know so much about the dump routine. The driver can easily have a routine that fails when it is actually called for reasons that setdumpdev() can't know. Perhaps nodump should be simply ((d_dump_t)NULL). dumpsys() already checks for a null d_dump pointer before calling it, although setdumpdev() doesn't. >one other question, considering the newbus stuff, shouldn't >there be a way to get the text string of the dump device somehow >so "dumpon" with no arguments can print out the current value >without scanning /dev for a device that matches it? This was broken by "newsysctl", not by newbus. In Lite1, the CONSDEV sysctl is specially handled and the device number is converted to a name using devname(3). Newsysctl neglects to convert to a name, and can't in general, since it has no way of knowing if the device is a cdev or a bdev. devname() is also broken. ISTR it has some fundamental problems, and it now returns NULL instead of the documented "??" when it can't determine the device name. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 18 23:49:48 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 4B37F14C93 for ; Tue, 18 May 1999 23:49:46 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id XAA57556; Tue, 18 May 1999 23:48:40 -0700 (PDT) From: Archie Cobbs Message-Id: <199905190648.XAA57556@bubba.whistle.com> Subject: Re: syscons update - stage 2 snopshot 17 May In-Reply-To: <19990517191842.A89207@myhakas.matti.ee> from Vallo Kallaste at "May 17, 99 07:18:42 pm" To: vallo@matti.ee Date: Tue, 18 May 1999 23:48:40 -0700 (PDT) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, freebsd-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 Vallo Kallaste writes: > > - History buffer (back-scroll buffer) management functions are moved > > to a new file, schistory.c. > > My question is slightly off-topic, but.. is it now possible (or in the > future) to choose which key combination to use for back-scroll buffer > handling? I personally prefer the Linux way, +, no > flames please. I can live with current combination but it's the one > feature I miss. Yeah, I'd like that too. It would make it consistent with xterm. -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 Wed May 19 0:23:29 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 E459B1580B for ; Wed, 19 May 1999 00:23:16 -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.00 #1) id 10k0ff-00005g-00; Wed, 19 May 1999 09:21:43 +0200 From: Sheldon Hearn To: Doug White Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: Fatal Trap 12 (-current kernel w/MFS) In-reply-to: Your message of "Tue, 18 May 1999 17:04:56 MST." Date: Wed, 19 May 1999 09:21:43 +0200 Message-ID: <351.927098503@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 May 1999 17:04:56 MST, Doug White wrote: > Fixed it earlier this week or last week in v1.63 (14 May) of > /sys/ufs/mfs/mfs_vfsops.c. Resup. I don't think so. Your changes didn't stop the panic for me. What _did_ fix it was Luoqi's change yesterday to kern_conf.c . John, make sure you have kern_conf.c v1.40 and try again. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 0:33: 4 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 AEE2014D91 for ; Wed, 19 May 1999 00:32:47 -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.00 #1) id 10k0pu-00006z-00; Wed, 19 May 1999 09:32:18 +0200 From: Sheldon Hearn To: Bruce Evans Cc: luoqi@watermarkgroup.com, current@FreeBSD.ORG, Jos.Backus@nl.origin-it.com Subject: Re: MFS still hosed In-reply-to: Your message of "Wed, 19 May 1999 12:04:54 +1000." <199905190204.MAA25133@godzilla.zeta.org.au> Date: Wed, 19 May 1999 09:32:18 +0200 Message-ID: <432.927099138@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 May 1999 12:04:54 +1000, Bruce Evans wrote: > >dumping to dev (0, 131089), offset 524288 > >dump device bad > > The dev_t changes obfuscated it by printing it in %d format instead of > as part of the dev number in [0x]%x format. So you reckon that whatever problem is making it imp[ossible for me to take dumps, it was present before the dev_t changes and I should be looking elsewhere? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 0:38:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from tardis.perspectives.net (ppp-as19-15.nss.udel.edu [128.175.143.17]) by hub.freebsd.org (Postfix) with ESMTP id 2FFB314D6A for ; Wed, 19 May 1999 00:38:17 -0700 (PDT) (envelope-from jerry.alexandratos@perspectives.net) Received: from localhost ([127.0.0.1] helo=tardis.perspectives.net) by tardis.perspectives.net with esmtp (Exim 2.12 #1) id 10k0vW-0000Du-00; Wed, 19 May 1999 03:38:06 -0400 To: Jonathan Lemon Cc: "Carlos C. Tapang" , current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE In-Reply-To: Message from Jonathan Lemon of "Tue, 18 May 1999 20:44:31 CDT." <19990518204431.15136@right.PCS> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <854.927099485.1@tardis.perspectives.net> Date: Wed, 19 May 1999 03:38:05 -0400 From: Jerry Alexandratos Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan Lemon says: : : Not true. VM86 is also required to support VESA. Also, it is used : for reliable memory detection (which is why I want to make it mandatory). : No more "My Stinkpad only detected 64M, what do I do now??!" questions. Actually, even with VM86, the kernel still doesn't correctly detect the StinkPad's memory. --Jerry name: Jerry Alexandratos || Open-Source software isn't a phone: 302.521.1018 || matter of life or death... email: jalexand@perspectives.net || ...It's much more important || than that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 0:41: 5 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 80A9F14D6A for ; Wed, 19 May 1999 00:40:54 -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 RAA31851; Wed, 19 May 1999 17:40:50 +1000 Date: Wed, 19 May 1999 17:40:50 +1000 From: Bruce Evans Message-Id: <199905190740.RAA31851@godzilla.zeta.org.au> To: bde@zeta.org.au, sheldonh@uunet.co.za Subject: Re: MFS still hosed Cc: current@FreeBSD.ORG, Jos.Backus@nl.origin-it.com, luoqi@watermarkgroup.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >dumping to dev (0, 131089), offset 524288 >> >dump device bad >> >> The dev_t changes obfuscated it by printing it in %d format instead of >> as part of the dev number in [0x]%x format. > >So you reckon that whatever problem is making it imp[ossible for me to >take dumps, it was present before the dev_t changes and I should be >looking elsewhere? "dump device bad" is printed for d_dump() returning ENXIO, which is fairly unambiguous. The new wd driver's d_dump would return ENODEV, so you must be using the old wd driver. The old wd_driver's d_dump only returns ENXIO when the drive doesn't exist or has never been opened or is not labeled. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 1: 0:20 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 F347E152E5 for ; Wed, 19 May 1999 01:00:01 -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.00 #1) id 10k1GS-0000Da-00; Wed, 19 May 1999 09:59:44 +0200 From: Sheldon Hearn To: Bruce Evans Cc: current@FreeBSD.ORG, Jos.Backus@nl.origin-it.com, luoqi@watermarkgroup.com Subject: Re: MFS still hosed In-reply-to: Your message of "Wed, 19 May 1999 17:40:50 +1000." <199905190740.RAA31851@godzilla.zeta.org.au> Date: Wed, 19 May 1999 09:59:44 +0200 Message-ID: <841.927100784@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 May 1999 17:40:50 +1000, Bruce Evans wrote: > so you must be using the old wd driver. The old wd_driver's d_dump > only returns ENXIO when the drive doesn't exist or has never been > opened or is not labeled. I'm using the "old" wd driver (controller wdc in CURRENT). The disk is labeled and I assume it's "opened" by swapon when it's configured as a swap device. So I'm at a loss as to why I get ENXIO (I did look at that part of the source, but thought it best to avoid talking in source terms, since I don't fully understand the meanings of the errors). Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 1: 7:14 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 0E8CB14D26 for ; Wed, 19 May 1999 01:07:03 -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 QAA24754 for ; Wed, 19 May 1999 16:06:13 +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 QAA01325 for ; Wed, 19 May 1999 16:06:57 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id QAA22293; Wed, 19 May 1999 16:06:57 +0800 Message-Id: <199905190806.QAA22293@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: MTRR support for AMD K6-2? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 May 1999 16:06:56 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do we have MTRR support for the AMD K6-2, and how's it done (e.g., if I want to allow mtrr support for my Voodoo Banshee) 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 Wed May 19 1:12:58 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 89C3D14BDE for ; Wed, 19 May 1999 01:12:36 -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 RAA18466; Wed, 19 May 1999 17:42:10 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199905190806.QAA22293@ariadne.tensor.pgs.com> Date: Wed, 19 May 1999 17:42:10 +0930 (CST) From: "Daniel O'Connor" To: Stephen Hocking-Senior Programmer PGS Tensor Perth Subject: RE: MTRR support for AMD K6-2? Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-May-99 Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > Do we have MTRR support for the AMD K6-2, and how's it done (e.g., if I want > to allow mtrr support for my Voodoo Banshee) I don't think its supported for the K6 (it only happens if you have i686). You can use it by playing with memcontrol which does ioctl's on /dev/mem Hmm.. memcontrol is a 'use the source' type of program at the mo, but its pretty simple :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 1:22:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id E075C14E55 for ; Wed, 19 May 1999 01:22:46 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id SAA00711; Wed, 19 May 1999 18:22:37 +1000 (EST) Message-ID: <19990519182237.H29455@rf900.physics.usyd.edu.au> Date: Wed, 19 May 1999 18:22:37 +1000 From: David Dawes To: Matthew Thyer Cc: current@FreeBSD.ORG Subject: Re: XFree86 xsetpointer causes silo overflows (Was: Re: Fixed my MAMEd sio problem.) References: <199905170127.LAA04147@godzilla.zeta.org.au> <37418C29.DEECA1AC@camtech.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <37418C29.DEECA1AC@camtech.com.au>; from Matthew Thyer on Wed, May 19, 1999 at 01:20:01AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 19, 1999 at 01:20:01AM +0930, Matthew Thyer wrote: >I have confirmed that the problem occurs if I just do: > > xsetpointer Joystick > sleep 1 > xsetpointer pointer > >So M.A.M.E. is unrelated to the problem as Bruce Evans would suggest. > >So the problem appears to be with XFree86 not closing the joystick >device after I've used it as a pointer with 'xsetpointer'. The problem is in the joystick driver (or are silo overflows acceptable while you actually want to use the joystick?). >I am sure I am using xsetpointer correctly as I can use my PC joystick >as a pointing device (once I calibrate it). > >I was just using xsetpointer with an incorrectly calibrated joystick >so it moved the pointer to the top left corner of the screen in my >xmame.sh shell script (I'd like to know how to do this another way). A better way would be a small X client that uses XWarpPointer(3). David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 3:37:34 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 4557B1515D for ; Wed, 19 May 1999 03:37:32 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id DAA24829 for ; Wed, 19 May 1999 03:38:06 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: "hanging root device to da0s1a" Date: Wed, 19 May 1999 03:38:06 -0700 Message-ID: <24825.927110286@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No offense, but can we use something like "assigning" in place of the rather loaded word "hanging?" I can just see the user bug reports now; "My root device is hanging! It says so every time I boot! HELP!" :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 3:48:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id A4C4B15414 for ; Wed, 19 May 1999 03:48:30 -0700 (PDT) (envelope-from ip@albatross.mcc.ac.uk) Received: from albatross.mcc.ac.uk ([130.88.202.16]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 10k3tk-000DRA-00; Wed, 19 May 1999 11:48:28 +0100 Received: (from ip@localhost) by albatross.mcc.ac.uk (8.9.3/8.9.1) id LAA10036; Wed, 19 May 1999 11:48:27 +0100 (BST) (envelope-from ip) From: Ian Pallfreeman Message-Id: <199905191048.LAA10036@albatross.mcc.ac.uk> Subject: Re: "hanging root device to da0s1a" In-Reply-To: <24825.927110286@zippy.cdrom.com> from "Jordan K. Hubbard" at "May 19, 1999 3:38: 6 am" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Wed, 19 May 1999 11:48:27 +0100 (BST) Cc: current@freebsd.org Reply-To: ip@mcc.ac.uk 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 > No offense, but can we use something like "assigning" in place of the > rather loaded word "hanging?" I can just see the user bug reports now; > "My root device is hanging! It says so every time I boot! HELP!" :) Or better still, revert to printing the SCSI probe results on a line break, rather than half-way through the "changing root device" message... Ian. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 3:53:26 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 B135215414 for ; Wed, 19 May 1999 03:53:22 -0700 (PDT) (envelope-from spud@i.am) Received: from Tomer.DrugsAreGood.org (RAS1-p51.hfa.netvision.net.il [62.0.145.51]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id NAA24595 for ; Wed, 19 May 1999 13:53:19 +0300 (IDT) From: Tomer Weller To: FreeBSD Current Subject: some1 messed with the voxware drivers ? Date: Wed, 19 May 1999 13:33:23 +0300 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99051913373500.00306@Tomer.DrugsAreGood.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG im -current, lat build world was two days ago, it seems like in the past week some1 has messed with the Voxware sound drivers, until last week i used a SB-Pro emulation with Voxware, and it worked fine, now it still works, but there are some annoying poping sound in the background (works FINE in windows), while im at it, another thing with Voware, the config doesn't allow the line : options SBC_IRQ=5 in the kernel configuration, though it works and is needed (won't compile without it). waiting for responds :) ==================================== 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 Wed May 19 5:13:35 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 BE5161541B for ; Wed, 19 May 1999 05:13:32 -0700 (PDT) (envelope-from spud@i.am) Received: from Tomer.DrugsAreGood.org (RAS6-p52.hfa.netvision.net.il [62.0.147.180]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id PAA28983 for ; Wed, 19 May 1999 15:13:29 +0300 (IDT) From: Tomer Weller To: FreeBSD Current Subject: ATA driver problem ? Date: Wed, 19 May 1999 14:54:26 +0300 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99051914574300.00313@Tomer.DrugsAreGood.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i've been using the ATA driver for a while now, but since my last word & kernel i get "WARNING: / was not properly dismounted" at the end of the dmesg and i have to fsck /. my last world was about 2 dayz ago. dmesg output for that ATA driver : ad1: ATA-4 disk at ata0 as slave ad1: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 0 depth queue, DMA mode ====================================== 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 Wed May 19 5:28: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 10A5F14EA6 for ; Wed, 19 May 1999 05:28:01 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id IAA11701; Wed, 19 May 1999 08:27:23 -0400 (EDT) (envelope-from luoqi) Date: Wed, 19 May 1999 08:27:23 -0400 (EDT) From: Luoqi Chen Message-Id: <199905191227.IAA11701@lor.watermarkgroup.com> To: jerry.alexandratos@perspectives.net, jlemon@americantv.com Subject: Re: FBSDBOOT.EXE Cc: ctapang@easystreet.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jonathan Lemon says: > : > : Not true. VM86 is also required to support VESA. Also, it is used > : for reliable memory detection (which is why I want to make it mandatory). > : No more "My Stinkpad only detected 64M, what do I do now??!" questions. > > Actually, even with VM86, the kernel still doesn't correctly detect the > StinkPad's memory. > > --Jerry > > name: Jerry Alexandratos || Open-Source software isn't a > phone: 302.521.1018 || matter of life or death... > email: jalexand@perspectives.net || ...It's much more important > || than that! It just occurred to me that we might be able to use initial MTRR settings by BIOS for memory detection (P6 and above, of course). Don't know how reliable that is. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 6:18:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (Postfix) with ESMTP id 0237915365 for ; Wed, 19 May 1999 06:18:17 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.2/8.9.1) with ESMTP id GAA78034; Wed, 19 May 1999 06:18:12 -0700 (PDT) Date: Wed, 19 May 1999 06:18:12 -0700 (PDT) From: Chris Timmons To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: "hanging root device to da0s1a" In-Reply-To: <24825.927110286@zippy.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 Heh. Well, then you would have people asking you what "ssigning" root devices means :) The message seems to get garbled when the CAM probes (being done in the background) emit their messages. The "c" in my "changing" creates a new device called cda4 in my log file: Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! cda4 at ahc1 bus 0 target 8 lun 0 da4: Fixed Direct Access SCSI-2 device -Chris On Wed, 19 May 1999, Jordan K. Hubbard wrote: > No offense, but can we use something like "assigning" in place of the > rather loaded word "hanging?" I can just see the user bug reports now; > "My root device is hanging! It says so every time I boot! HELP!" :) > > - Jordan > > > 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 Wed May 19 6:25: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id E95511549B for ; Wed, 19 May 1999 06:25:03 -0700 (PDT) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id IAA13225; Wed, 19 May 1999 08:25:06 -0500 (CDT) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id IAA13220; Wed, 19 May 1999 08:25:02 -0500 (CDT) Message-ID: <034701bea1fb$06245460$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Doug White" Cc: "FreeBSD-Current" Subject: Re: Sound Strangeness Date: Wed, 19 May 1999 08:25:07 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Same settings under Windows and same I have used under Linux [with the 2.2 kernels]. Tom Veldhouse veldy@visi.com -----Original Message----- From: Doug White To: Thomas T. Veldhouse Cc: FreeBSD-Current Date: Tuesday, May 18, 1999 7:10 PM Subject: Re: Sound Strangeness >This is usually indicitive of a resource problem with your soundcard (bad >IRQ). Check your settings. > >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 Wed May 19 6:58:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 05E4815604 for ; Wed, 19 May 1999 06:58:32 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-10-31.camtech.net.au [203.28.1.159]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id XAA12509; Wed, 19 May 1999 23:33:25 +0930 (CST) Message-ID: <3742C3CF.B8ADD15F@camtech.com.au> Date: Wed, 19 May 1999 23:29:43 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Carlos C. Tapang" Cc: Mike Smith , current@FreeBSD.ORG Subject: SUMMARY: why you cant use FBSDBOOT.EXE anymore (Was: Re: FBSDBOOT.EXE) References: <006201bea0ae$7e656340$0d787880@apex.tapang> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem is that recent versions of MS-DOS (version 7 and above ? ...definitely the DOS that comes with Windows 98 and I think the DOS with Windows 95 under some circumstances) change various vectors which destroy FBSDBOOTs ability to work (this is because there is no way to determine where these vectors used to point and the original addresses are required for correct operation of either FBSDBOOT or the kernel/ loader). What I do know is that at least some older versions of MS-DOS do not do this. Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22 boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel and hence the whole system. Hopefully now that Carlos Tapang has updated FBSDBOOT.EXE for ELF, such a boot floppy could boot a 3.1, 3.2 or -CURRENT system. Unfortunately the project cannot guarantee anything when you are booting from another vendor's operating system (such as MS-DOS) so its a lot easier to say that FBSDBOOT.EXE has been retired. Given the number of different DOSes that exist, that's an entirely understandable policy. I hope this clears things up (and adds a good summary to the archives). "Carlos C. Tapang" wrote: > > Mike, Thanks for trying fbsdboot.exe. I need more information to fix it. I > would like to fix it, so please describe exactly what the problem is. What > do you mean by the "need to reboot the system to restore various vectors > that DOS destroys"? Do you mean that prior to executing the FreeBSD kernel > init routines, DOS does something to the loaded area? I'm sorry I can't find > any info on this either in the mail threads or in freebsd.org. Probably I'm > not looking hard enough, but I believe it would be more efficient to just > ask you. > > Carlos C. Tapang > http://www.genericwindows.com > > -----Original Message----- > From: Mike Smith > To: Carlos C. Tapang > Cc: Bob Bishop ; Mike Smith ; > current@freebsd.org > Date: Sunday, May 16, 1999 7:28 PM > Subject: Re: FBSDBOOT.EXE > > >> >It doesn't work. Don't use it. You need to reboot the system to > >> >restore various vectors that DOS destroys. Please see the previous > >> >threads on this topic, especially anything from Robert Nordier. > >> > > >> The most relevant piece I can find from R. Nordier is the following: > >> "The fbsdboot.exe program should probably be considered obsolete. It > >> should (in theory) be possible to use it to load /boot/loader, which > >> can then load the kernel, but there are various reasons this doesn't > >> work too well." > > > >These reasons were also expounded, and I did summarise them in another > >message on this thread. > > > >> I have not tested the updated program with /boot/loader. /boot/loader does > >> not help me because my root directory is in a memory file system, and I can > >> not assume that my users will want to reformat their DOS drives or even > >> repartition it. So all FreeBSD files are in the DOS file system. > > > >The loader won't help you because you are booting from under DOS, but > >the loader will boot the kernel just fine off a DOS filesystem. > > > >-- > >\\ Sometimes you're ahead, \\ Mike Smith > >\\ sometimes you're behind. \\ mike@smith.net.au > >\\ The race is long, and in the \\ msmith@freebsd.org > >\\ end it's only with yourself. \\ msmith@cdrom.com > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 7: 6:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with ESMTP id 617301554F for ; Wed, 19 May 1999 07:06:21 -0700 (PDT) (envelope-from thyerm@camtech.com.au) Received: from camtech.com.au (dialup-ad-10-31.camtech.net.au [203.28.1.159]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id XAA13623; Wed, 19 May 1999 23:41:33 +0930 (CST) Message-ID: <3742C5B7.5E85F408@camtech.com.au> Date: Wed, 19 May 1999 23:37:51 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: David Dawes Cc: current@FreeBSD.ORG Subject: Re: XFree86 xsetpointer causes silo overflows (Was: Re: Fixed my MAMEd sio problem.) References: <199905170127.LAA04147@godzilla.zeta.org.au> <37418C29.DEECA1AC@camtech.com.au> <19990519182237.H29455@rf900.physics.usyd.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The big problem is that the silo overflows continue after I have returned the pointer to the mouse (with "xsetpointer pointer"). This should close the joystick device shouldn't it ? If it doesn't then there is a problem with either the X server or FreeBSD. Bruce has already indicated that there is a problem with the FreeBSD joystick driver but he thought it should stop when the joystick device is closed but I see that the problem continues until I restart the X server so that would seem to indicate a problem with the X server. David Dawes wrote: > > On Wed, May 19, 1999 at 01:20:01AM +0930, Matthew Thyer wrote: > >I have confirmed that the problem occurs if I just do: > > > > xsetpointer Joystick > > sleep 1 > > xsetpointer pointer > > > >So M.A.M.E. is unrelated to the problem as Bruce Evans would suggest. > > > >So the problem appears to be with XFree86 not closing the joystick > >device after I've used it as a pointer with 'xsetpointer'. > > The problem is in the joystick driver (or are silo overflows acceptable > while you actually want to use the joystick?). > > >I am sure I am using xsetpointer correctly as I can use my PC joystick > >as a pointing device (once I calibrate it). > > > >I was just using xsetpointer with an incorrectly calibrated joystick > >so it moved the pointer to the top left corner of the screen in my > >xmame.sh shell script (I'd like to know how to do this another way). > > A better way would be a small X client that uses XWarpPointer(3). > > David > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 8:15:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 74BFE15730 for ; Wed, 19 May 1999 08:15:20 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup1-13.iptelecom.net.ua [212.42.68.140]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id SAA18384; Wed, 19 May 1999 18:14:47 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.2) with ESMTP id SAA02839; Wed, 19 May 1999 18:14:42 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3742D561.2BEDEFD1@altavista.net> Date: Wed, 19 May 1999 18:14:41 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Matthew Thyer Cc: "Carlos C. Tapang" , Mike Smith , current@FreeBSD.ORG Subject: Re: SUMMARY: why you cant use FBSDBOOT.EXE anymore (Was: Re: FBSDBOOT.EXE) References: <006201bea0ae$7e656340$0d787880@apex.tapang> <3742C3CF.B8ADD15F@camtech.com.au> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Thyer wrote: > Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22 > boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel > and hence the whole system. Obviously it makes no sense at all to make special DOS boot floppy with older DOS just to run FBSDBOOT - it simply enough to make "native" FreeBSD boot floppy with /boot/loader and hacked /boot/loader.conf to boot kernel from your hard drive, so it seems that FBSDBOOT now totally useless :( Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 9:39: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles504.castles.com [208.214.165.68]) by hub.freebsd.org (Postfix) with ESMTP id EABAC14DA5 for ; Wed, 19 May 1999 09:39:00 -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 JAA03111; Wed, 19 May 1999 09:37:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905191637.JAA03111@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: "hanging root device to da0s1a" In-reply-to: Your message of "Wed, 19 May 1999 03:38:06 PDT." <24825.927110286@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 May 1999 09:37:13 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No offense, but can we use something like "assigning" in place of the > rather loaded word "hanging?" I can just see the user bug reports now; > "My root device is hanging! It says so every time I boot! HELP!" :) Actually, it says "changing", but the 'c' gets printed and then all of the interrupt context stuff happens for the outstanding SCSI probes, so all that's left to print at the end is 'hanging...' I'm not sure why it happens like this; try putting a DELAY() just before we actually set the root device and see if you can put it off. -- \\ 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 Wed May 19 9:44:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles504.castles.com [208.214.165.68]) by hub.freebsd.org (Postfix) with ESMTP id 8A43715043 for ; Wed, 19 May 1999 09:44:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA03143; Wed, 19 May 1999 09:41:47 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905191641.JAA03143@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luoqi Chen Cc: jerry.alexandratos@perspectives.net, jlemon@americantv.com, ctapang@easystreet.com, current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE In-reply-to: Your message of "Wed, 19 May 1999 08:27:23 EDT." <199905191227.IAA11701@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 May 1999 09:41:47 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Jonathan Lemon says: > > : > > : Not true. VM86 is also required to support VESA. Also, it is used > > : for reliable memory detection (which is why I want to make it mandatory). > > : No more "My Stinkpad only detected 64M, what do I do now??!" questions. > > > > Actually, even with VM86, the kernel still doesn't correctly detect the > > StinkPad's memory. This is because the BIOS probe results are still ignored. 8( > It just occurred to me that we might be able to use initial MTRR settings > by BIOS for memory detection (P6 and above, of course). Don't know how > reliable that is. Not at all. If there's 640k chopped off the end of eg. 128M of physical memory, you'd have to use a 64M segment, a 32M segment, a 16M segment, an 8M segment, a 4M segment, a 2M segment, a 1M segment, a 256k segment and a 128k segment to map it accurately. That's 9 variable MTRRs, and the P6 only has 8. -- \\ 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 Wed May 19 9:45:40 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 DAF4B14CE4 for ; Wed, 19 May 1999 09:45:26 -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 KAA62955; Wed, 19 May 1999 10:44:18 -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 KAA86243; Wed, 19 May 1999 10:46:16 -0600 (MDT) Message-Id: <199905191646.KAA86243@harmony.village.org> To: Nate Williams Subject: Re: zzz crashing in current OR inthand_remove not removing handlers properly Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 May 1999 09:00:50 MDT." <199905171500.JAA22502@mt.sri.com> References: <199905171500.JAA22502@mt.sri.com> <5lr9ogzaqf.fsf@assaris.sics.se> <19990516235949.A18232@netmonger.net> Date: Wed, 19 May 1999 10:46:16 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905171500.JAA22502@mt.sri.com> Nate Williams writes: : The solution is to not poll and to make sure insertion/removal events : generate an interrupt which can inform the card's interrupt handlers : that there is no more card. : : (That's one of the main reasons polling is a very bad idea.) Agreed. It is far better to figure out which interrupt lines are connected and how. I know the curretn code does a horrible job of figuring these things out... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 10: 6:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id F2C1F154DC; Wed, 19 May 1999 10:06:11 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA02484; Thu, 20 May 1999 02:05:58 +0900 (JST) Message-ID: <3742DF58.583E9C29@newsguy.com> Date: Thu, 20 May 1999 00:57:12 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Steven Ames Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: ed0/probe solved (Was: re: ed0/probe problem in 4.0-CURRENT) References: <199905190144.UAA00340@virtual-voodoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steven Ames wrote: > > *sigh* No suprise here. As 90% of these things are this was yet > another Dumb User Error. I had a base address conflict that kept > the card from being probed. So, can we say it was due? ;-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If at first you don't succeed, skydiving is not for you." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 10:30:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 6B9B4152E5 for ; Wed, 19 May 1999 10:30:30 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id NAA14869; Wed, 19 May 1999 13:29:56 -0400 (EDT) (envelope-from luoqi) Date: Wed, 19 May 1999 13:29:56 -0400 (EDT) From: Luoqi Chen Message-Id: <199905191729.NAA14869@lor.watermarkgroup.com> To: luoqi@watermarkgroup.com, mike@smith.net.au Subject: Re: FBSDBOOT.EXE Cc: ctapang@easystreet.com, current@FreeBSD.ORG, jerry.alexandratos@perspectives.net, jlemon@americantv.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Not at all. If there's 640k chopped off the end of eg. 128M of > physical memory, you'd have to use a 64M segment, a 32M segment, a 16M > segment, an 8M segment, a 4M segment, a 2M segment, a 1M segment, a > 256k segment and a 128k segment to map it accurately. That's 9 > variable MTRRs, and the P6 only has 8. > No you don't need that many, fixed MTRRs take precedence over variable MTRRs, so you can just use one variable segment covering 0-128M and override with fixed MTRRs in the low memory area. > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ msmith@freebsd.org > \\ -- Joseph Merrick \\ msmith@cdrom.com > > > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 10:41:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id C3E86154A8 for ; Wed, 19 May 1999 10:41:43 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id NAA14945; Wed, 19 May 1999 13:34:59 -0400 (EDT) (envelope-from luoqi) Date: Wed, 19 May 1999 13:34:59 -0400 (EDT) From: Luoqi Chen Message-Id: <199905191734.NAA14945@lor.watermarkgroup.com> To: sobomax@altavista.net, thyerm@camtech.com.au Subject: Re: SUMMARY: why you cant use FBSDBOOT.EXE anymore (Was: Re: FBSDBOOT.EXE) Cc: ctapang@easystreet.com, current@FreeBSD.ORG, mike@smith.net.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22 > > boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel > > and hence the whole system. > > Obviously it makes no sense at all to make special DOS boot floppy with older DOS > just to run FBSDBOOT - it simply enough to make "native" FreeBSD boot floppy with > /boot/loader and hacked /boot/loader.conf to boot kernel from your hard drive, so it > seems that FBSDBOOT now totally useless :( > > Sincerely, > > Maxim > Why can't we make a copy of the vector table and save to file and have fbsdboot use the table from the file? -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 11: 1:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from ras.interaccess.com (207-229-151-151.d.enteract.com [207.229.151.151]) by hub.freebsd.org (Postfix) with ESMTP id DB0A114D2B for ; Wed, 19 May 1999 11:01:17 -0700 (PDT) (envelope-from ras@interaccess.com) Received: from localhost (ras@localhost) by ras.interaccess.com (8.9.3/8.9.2) with ESMTP id NAA10405 for ; Wed, 19 May 1999 13:01:16 -0500 (CDT) (envelope-from ras@interaccess.com) X-Authentication-Warning: ras.interaccess.com: ras owned process doing -bs Date: Wed, 19 May 1999 13:00:59 -0500 (CDT) From: Chris Silva To: freebsd-current@FreeBSD.org Subject: WDM maddness 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have installed 4.0-CURRENT however, It seems that wdm is still broken. Here is the tail end of a make install for wdm: ras# make install > tmp ras# more tmp ===> Extracting for wdm-1.0 >> Checksum OK for wdm/wdm-1.0.tar.gz. >> Checksum OK for wdm/daemon1-HQ-1280x960.jpg. ===> wdm-1.0 depends on shared library: Xpm.4 - found ===> wdm-1.0 depends on shared library: gif.3 - found ===> wdm-1.0 depends on shared library: jpeg.9 - found ===> wdm-1.0 depends on shared library: png.3 - found ===> wdm-1.0 depends on shared library: tiff.4 - found ===> wdm-1.0 depends on shared library: wraster.2 - not found ===> Verifying install for wraster.2 in /usr/ports/x11-wm/windowmaker ===> Returning to build of wdm-1.0 Error: shared library "wraster.2" does not exist *** Error code 1 Stop. Are there plans to fix this? TIA Chris _____________________________________________________________________ RSA Key Fingerprint = 6D0B 5536 7825 3D09 9093 384A 9694 FDB6 RSA Key Fingerprint = 4390 44E5 E316 F2AA A11E 5755 F3F9 D69B DH/DSS Fingerprint = 089B 0B5C 75C7 A7B4 B050 DD14 2D65 5DD6 E87D 239A PGP Mail encouraged / preferred - keys available on common keyservers _____________________________________________________________________ -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQA/AwUBN0LuWi1lXdbofSOaEQLZPACfTrtxieMsDmr2eTkApTYFuU+1o/QAoISS 9FxYpIDgRWKqtqLKBb7KBMDu =nz9q -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 11:46:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 9F34F14F13 for ; Wed, 19 May 1999 11:46:15 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id NAA00353; Wed, 19 May 1999 13:46:09 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id NAA25347; Wed, 19 May 1999 13:46:07 -0500 Message-ID: <19990519134607.23968@right.PCS> Date: Wed, 19 May 1999 13:46:07 -0500 From: Jonathan Lemon To: Jerry Alexandratos Cc: "Carlos C. Tapang" , current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Jerry Alexandratos on May 05, 1999 at 03:38:05AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On May 05, 1999 at 03:38:05AM -0400, Jerry Alexandratos wrote: > Jonathan Lemon says: > : > : Not true. VM86 is also required to support VESA. Also, it is used > : for reliable memory detection (which is why I want to make it mandatory). > : No more "My Stinkpad only detected 64M, what do I do now??!" questions. > > Actually, even with VM86, the kernel still doesn't correctly detect the > StinkPad's memory. Hm, if that's so, then it's an implementation bug. Can you try the following patch, boot the system with the -v flag, and mail me back the result of the dmesg output? -- Jonathan Index: i386/i386/vm86.c =================================================================== RCS file: /tuna/ncvs/src/sys/i386/i386/vm86.c,v retrieving revision 1.25 diff -u -r1.25 vm86.c --- vm86.c 1999/05/12 21:38:45 1.25 +++ vm86.c 1999/05/19 15:47:10 @@ -41,6 +41,7 @@ #include #include +#include #include #include @@ -524,6 +525,13 @@ *pte = (1 << PAGE_SHIFT) | PG_RW | PG_V; /* + * use whatever is leftover of the vm86 page layout as a + * message buffer so we can capture early output. + */ + msgbufinit((vm_offset_t)vm86paddr + sizeof(struct vm86_layout), + ctob(3) - sizeof(struct vm86_layout)); + + /* * get memory map with INT 15:E820 */ #define SMAPSIZ sizeof(*smap) @@ -541,6 +549,13 @@ i = vm86_datacall(0x15, &vmf, &vmc); if (i || vmf.vmf_eax != SMAP_SIG) break; + if (boothowto & RB_VERBOSE) + printf("SMAP type=%02x base=%08x %08x len=%08x %08x\n", + smap->type, + *(u_int32_t *)((char *)&smap->base + 4), + (u_int32_t)smap->base, + *(u_int32_t *)((char *)&smap->length + 4), + (u_int32_t)smap->length); if (smap->type == 0x01 && smap->base >= highwat) { *extmem += (smap->length / 1024); highwat = smap->base + smap->length; Index: kern/subr_prf.c =================================================================== RCS file: /tuna/ncvs/src/sys/kern/subr_prf.c,v retrieving revision 1.51 diff -u -r1.51 subr_prf.c --- subr_prf.c 1998/12/03 04:45:56 1.51 +++ subr_prf.c 1999/03/19 19:10:47 @@ -674,10 +674,24 @@ } } +static void +msgbufcopy(struct msgbuf *oldp) +{ + int pos; + + pos = oldp->msg_bufr; + while (pos != oldp->msg_bufx) { + msglogchar(oldp->msg_ptr[pos], NULL); + if (++pos >= oldp->msg_size) + pos = 0; + } +} + void msgbufinit(void *ptr, size_t size) { char *cp; + static struct msgbuf *oldp = NULL; cp = (char *)ptr; msgbufp = (struct msgbuf *) (cp + size - sizeof(*msgbufp)); @@ -687,7 +701,10 @@ msgbufp->msg_size = (char *)msgbufp - cp; msgbufp->msg_ptr = cp; } + if (msgbufmapped && oldp != msgbufp) + msgbufcopy(oldp); msgbufmapped = 1; + oldp = msgbufp; } #include "opt_ddb.h" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 12:31: 7 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 7B4C714BDE for ; Wed, 19 May 1999 12:31:03 -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 MAA00410; Wed, 19 May 1999 12:27:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905191927.MAA00410@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luoqi Chen Cc: mike@smith.net.au, ctapang@easystreet.com, current@FreeBSD.ORG, jerry.alexandratos@perspectives.net, jlemon@americantv.com Subject: Re: FBSDBOOT.EXE In-reply-to: Your message of "Wed, 19 May 1999 13:29:56 EDT." <199905191729.NAA14869@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 May 1999 12:27:31 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Not at all. If there's 640k chopped off the end of eg. 128M of > > physical memory, you'd have to use a 64M segment, a 32M segment, a 16M > > segment, an 8M segment, a 4M segment, a 2M segment, a 1M segment, a > > 256k segment and a 128k segment to map it accurately. That's 9 > > variable MTRRs, and the P6 only has 8. > > > No you don't need that many, fixed MTRRs take precedence over variable MTRRs, > so you can just use one variable segment covering 0-128M and override with > fixed MTRRs in the low memory area. I specifically said "640k chopped off the end", referring to the possibly non-aligned _end_ of physical memory. The issue here is that the BIOS will tell us how much memory we are _allowed_to_use_, which is not always the same as the amount of physical memory present in the system. Some memory may be (is sometimes) reserved for use by eg. APM/ACPI. We fare badly at the moment on these systems because we ignore this and use all the memory we can find. -- \\ 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 Wed May 19 12:33:48 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 2DBDF14C4A for ; Wed, 19 May 1999 12:33:31 -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 MAA00425; Wed, 19 May 1999 12:29:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905191929.MAA00425@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luoqi Chen Cc: sobomax@altavista.net, thyerm@camtech.com.au, ctapang@easystreet.com, current@FreeBSD.ORG, mike@smith.net.au Subject: Re: SUMMARY: why you cant use FBSDBOOT.EXE anymore (Was: Re: FBSDBOOT.EXE) In-reply-to: Your message of "Wed, 19 May 1999 13:34:59 EDT." <199905191734.NAA14945@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 May 1999 12:29:08 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22 > > > boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel > > > and hence the whole system. > > > > Obviously it makes no sense at all to make special DOS boot floppy with older DOS > > just to run FBSDBOOT - it simply enough to make "native" FreeBSD boot floppy with > > /boot/loader and hacked /boot/loader.conf to boot kernel from your hard drive, so it > > seems that FBSDBOOT now totally useless :( > > > > Sincerely, > > > > Maxim > > > Why can't we make a copy of the vector table and save to file and have > fbsdboot use the table from the file? How do we get this vector table in the first place? How do we keep it updated? -- \\ 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 Wed May 19 12:41:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id D6BEB14DEE for ; Wed, 19 May 1999 12:41:26 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id OAA00959; Wed, 19 May 1999 14:41:14 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id OAA03700; Wed, 19 May 1999 14:41:12 -0500 Message-ID: <19990519144111.52604@right.PCS> Date: Wed, 19 May 1999 14:41:11 -0500 From: Jonathan Lemon To: Mike Smith Cc: Luoqi Chen , ctapang@easystreet.com, current@FreeBSD.ORG, jerry.alexandratos@perspectives.net Subject: Re: FBSDBOOT.EXE References: <199905191729.NAA14869@lor.watermarkgroup.com> <199905191927.MAA00410@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199905191927.MAA00410@dingo.cdrom.com>; from Mike Smith on May 05, 1999 at 12:27:31PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On May 05, 1999 at 12:27:31PM -0700, Mike Smith wrote: > The issue here is that the BIOS will tell us how much memory we are > _allowed_to_use_, which is not always the same as the amount of > physical memory present in the system. Some memory may be (is > sometimes) reserved for use by eg. APM/ACPI. We fare badly at the > moment on these systems because we ignore this and use all the memory > we can find. Yup. That's probably the problem with the Thinkpads; the code patch I just sent out will dump the ACPI System Address map, so I can figure out what is happening. I bet that it declares one memory range for all the ram, and then overlays a second "reserved" address on top of it. Right now, I don't handle that correctly. It "should" be simple to write some code to aggregate this map and fill in the phys_avail[] structure; then the entire memory probe in machdep.c can go away. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 12:48:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from 001101.zer0.org (001101.zer0.org [206.24.105.163]) by hub.freebsd.org (Postfix) with ESMTP id 70BB514D38 for ; Wed, 19 May 1999 12:48:55 -0700 (PDT) (envelope-from gsutter@001101.zer0.org) Received: (from gsutter@localhost) by 001101.zer0.org (8.9.2/8.9.2) id MAA35275; Wed, 19 May 1999 12:48:05 -0700 (PDT) (envelope-from gsutter) Date: Wed, 19 May 1999 12:48:04 -0700 From: Gregory Sutter To: Archie Cobbs Cc: vallo@matti.ee, yokota@zodiac.mech.utsunomiya-u.ac.jp, freebsd-current@FreeBSD.ORG Subject: Re: syscons update - stage 2 snopshot 17 May Message-ID: <19990519124804.V80987@001101.zer0.org> References: <19990517191842.A89207@myhakas.matti.ee> <199905190648.XAA57556@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199905190648.XAA57556@bubba.whistle.com>; from Archie Cobbs on Tue, May 18, 1999 at 11:48:40PM -0700 Organization: Zer0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 18, 1999 at 11:48:40PM -0700, Archie Cobbs wrote: > Vallo Kallaste writes: > > > - History buffer (back-scroll buffer) management functions are moved > > > to a new file, schistory.c. > > > > My question is slightly off-topic, but.. is it now possible (or in the > > future) to choose which key combination to use for back-scroll buffer > > handling? I personally prefer the Linux way, +, no > > flames please. I can live with current combination but it's the one > > feature I miss. > > Yeah, I'd like that too. It would make it consistent with xterm. I think I've tried to find a way to make the older syscons do that on three separate occasions, each time getting interrupted by something of higher priority. Sure would be nice to have an easily configurable buffer-scroll sequence... defaulting to shift-pg{up,down} of course. :) Greg -- Gregory S. Sutter Madness takes its toll. mailto:gsutter@pobox.com Please have exact change. http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 13:51:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m1-55-dbn.dial-up.net [196.34.155.55]) by hub.freebsd.org (Postfix) with ESMTP id B070214F42 for ; Wed, 19 May 1999 13:51:13 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA00961; Wed, 19 May 1999 22:48:57 +0200 (SAST) From: Robert Nordier Message-Id: <199905192048.WAA00961@ceia.nordier.com> Subject: Re: SUMMARY: why you cant use FBSDBOOT.EXE anymore (Was: Re: FBSDBOOT.EXE) In-Reply-To: <199905191929.MAA00425@dingo.cdrom.com> from Mike Smith at "May 19, 1999 12:29:08 pm" To: mike@smith.net.au (Mike Smith) Date: Wed, 19 May 1999 22:48:50 +0200 (SAST) Cc: luoqi@watermarkgroup.com (Luoqi Chen), sobomax@altavista.net, thyerm@camtech.com.au, ctapang@easystreet.com, 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 > > > > Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22 > > > > boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel > > > > and hence the whole system. > > > > > > Obviously it makes no sense at all to make special DOS boot floppy with old > er DOS > > > just to run FBSDBOOT - it simply enough to make "native" FreeBSD boot flopp > y with > > > /boot/loader and hacked /boot/loader.conf to boot kernel from your hard dri > ve, so it > > > seems that FBSDBOOT now totally useless :( > > > > > > Sincerely, > > > > > > Maxim > > > > > Why can't we make a copy of the vector table and save to file and have > > fbsdboot use the table from the file? > > How do we get this vector table in the first place? > > How do we keep it updated? The flags and values in the BIOS data area would not necessarily be at their default values, so restoring the vectors might itself crash the BIOS (because it's reconfigured itself for the present vectors/drivers, not the default ones). Some hardware (eg. popular SCSI controllers) also configures itself differently when it finds it's running on DOS/Windows. This kind of thing in any scenario in which we start DOS then kill it would have the potential to seriously confuse matters. Incidentally (to correct a point made in an earlier post) *all* versions of DOS since 1.x have changed interrupt vectors. This is not a DOS 7+ phenomenon. The reason FBSDBOOT.EXE is deprecated at this stage is that, in the future, VM86 will be increasingly relied on by FreeBSD. And FBSDBOOT.EXE has *never* worked reliably in a VM86 context. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 13:56:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id AACA014F42 for ; Wed, 19 May 1999 13:52:47 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial8-229.netcologne.de [195.14.235.229]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id WAA17342; Wed, 19 May 1999 22:52:41 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id WAA15511; Wed, 19 May 1999 22:52:58 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Wed, 19 May 1999 22:52:58 +0200 (CEST) Message-Id: <199905192052.WAA15511@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: freebsd-current@freebsd.org Subject: X11 aout compat pack Reply-To: van.woerkom@netcologne.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG May I suggest to add the XFree86 aout libraries to src/compat, or to add them as port - for easy update via make. Background: Netscape 4.6 installation complained that I need X11 aout libs, so I had to download xlib.tgz (3.3M) just for the aout libs (0.7M). Or am I missing some opportunity elsewhere, to get these libs reinstalled on my system? Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 14: 7:47 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 AC90114CA7 for ; Wed, 19 May 1999 14:07:46 -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 OAA00935; Wed, 19 May 1999 14:05:21 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905192105.OAA00935@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@freebsd.org Subject: Re: MTRR support for AMD K6-2? In-reply-to: Your message of "Wed, 19 May 1999 16:06:56 +0800." <199905190806.QAA22293@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 May 1999 14:05:21 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Do we have MTRR support for the AMD K6-2, and how's it done (e.g., if I want > to allow mtrr support for my Voodoo Banshee) It's being worked on. The K6 is a problematic device, as it only supports two memory ranges, as opposed to the eight the P6 does. -- \\ 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 Wed May 19 14:43:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (Postfix) with ESMTP id B85FC14FA5 for ; Wed, 19 May 1999 14:43:46 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by mail4.aracnet.com (8.9.1/8.9.0) with SMTP id OAA00368; Wed, 19 May 1999 14:43:20 -0700 Message-ID: <024501bea240$ebb029b0$0d787880@apex.tapang> From: "Carlos C. Tapang" To: "Robert Nordier" , "Mike Smith" Cc: "Luoqi Chen" , , , Subject: Re: SUMMARY: why you cant use FBSDBOOT.EXE anymore (Was: Re: FBSDBOOT.EXE) Date: Wed, 19 May 1999 14:45:26 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to all who pitched in their input to this issue. Most users of my system are running Windows and don't want to have to reformat or repartition their hard disk. So I am stuck with the DOS file system. I think the best solution is to have my users use a FreeBSD boot floppy. The floppy will have /boot/loader which I will point to the DOS-formatted hard disk in which the kernel resides. >The flags and values in the BIOS data area would not necessarily >be at their default values, so restoring the vectors might itself >crash the BIOS (because it's reconfigured itself for the present >vectors/drivers, not the default ones). > >Some hardware (eg. popular SCSI controllers) also configures itself >differently when it finds it's running on DOS/Windows. This kind >of thing in any scenario in which we start DOS then kill it would >have the potential to seriously confuse matters. > >Incidentally (to correct a point made in an earlier post) *all* >versions of DOS since 1.x have changed interrupt vectors. This is >not a DOS 7+ phenomenon. The reason FBSDBOOT.EXE is deprecated at >this stage is that, in the future, VM86 will be increasingly relied >on by FreeBSD. And FBSDBOOT.EXE has *never* worked reliably in a >VM86 context. > >-- >Robert Nordier > > >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 Wed May 19 15: 1:54 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 CE0881519D for ; Wed, 19 May 1999 15:01:52 -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 QAA63789; Wed, 19 May 1999 16:00:44 -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 QAA01861; Wed, 19 May 1999 16:00:37 -0600 (MDT) Message-Id: <199905192200.QAA01861@harmony.village.org> To: Annelise Anderson Subject: Re: pccard status? Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 16 May 1999 20:38:49 PDT." References: Date: Wed, 19 May 1999 16:00:36 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The pccard code kinda sorta works on some systems, but not on others. The support for sio and fdc no longer works on any system. I'm working on a rewrite in the new bus framework. I have pcic interrupting now, and hope to have I/O and memory mapping working again to allow pccards to work again shortly. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 15: 2:55 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 17F4D1540D for ; Wed, 19 May 1999 15:02:52 -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 QAA63796; Wed, 19 May 1999 16:01:44 -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 QAA01881; Wed, 19 May 1999 16:01:37 -0600 (MDT) Message-Id: <199905192201.QAA01881@harmony.village.org> To: Doug Rabson Subject: Re: pccard status? Cc: Dick van den Burg , Annelise Anderson , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 May 1999 14:58:20 BST." References: Date: Wed, 19 May 1999 16:01:37 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Rabson writes: : The sio support will need to wait until Warner Losh commits his changes to : clean up the pccard driver. I'm hoping to have this done before I take off for Memorial Day weekend. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 15:41:34 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 BFC7C14E24 for ; Wed, 19 May 1999 15:41:32 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id QAA09421; Wed, 19 May 1999 16:31:25 -0600 (MDT) Date: Wed, 19 May 1999 16:31:25 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905192231.QAA09421@narnia.plutotech.com> To: Mike Smith Cc: current@FreeBSD.org Subject: Re: "hanging root device to da0s1a" X-Newsgroups: pluto.freebsd.current In-Reply-To: <199905191637.JAA03111@dingo.cdrom.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 <199905191637.JAA03111@dingo.cdrom.com> you wrote: > I'm not sure why it happens like this; try putting a DELAY() just > before we actually set the root device and see if you can put it off. Why not just spl() protect that printf call so that its output is dumped contiguously into the console buffer? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 15:58:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 0CF4914E24 for ; Wed, 19 May 1999 15:58:32 -0700 (PDT) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id CAA12362 for freebsd-current@freebsd.org; Thu, 20 May 1999 02:49:25 +0400 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.3/8.9.1) with ESMTP id CAA00525 for ; Thu, 20 May 1999 02:53:29 +0400 (MSD) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199905192253.CAA00525@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-current@freebsd.org Subject: calcru and upages Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 May 1999 02:53:28 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG calcru() access p_stats, which is in upages. Therefore, as I understand, it should not be called on a swapped out process. Neither calcru() nor its callers seem to ensure this. At least the call in procfs_dostatus() may happen on a swapped out process. (It test for P_INMEM for another access to p_stats several lines before :-/) Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 16:18:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp.uky.edu (smtp.uky.edu [128.163.2.17]) by hub.freebsd.org (Postfix) with ESMTP id 0F0EF15164 for ; Wed, 19 May 1999 16:18:18 -0700 (PDT) (envelope-from gchil0@pop.uky.edu) Received: from pop.uky.edu (pop.uky.edu [128.163.2.16]) by smtp.uky.edu (8.9.3/8.9.3) with ESMTP id TAA01870 for ; Wed, 19 May 1999 19:18:15 -0400 (EDT) Received: from p200 (kilauea.volcano.flex.qx.net [208.235.88.64]) by pop.uky.edu (8.8.8/8.8.8) with SMTP id TAA29214 for ; Wed, 19 May 1999 19:18:14 -0400 (EDT) Message-Id: <4.1.19990519191409.0092ad90@pop.uky.edu> X-Sender: gchil0@pop.uky.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 19 May 1999 19:17:16 -0400 To: current@FreeBSD.ORG From: Greg Childers Subject: Re: SUMMARY: why you cant use FBSDBOOT.EXE anymore (Was: Re: FBSDBOOT.EXE) In-Reply-To: <024501bea240$ebb029b0$0d787880@apex.tapang> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sounds like you want something like a FreeBSD version of DOS Linux. See http://www.tux.org/pub/people/kent-robotti/index.html. How do they overcome this problem? Greg At 02:45 PM 5/19/99 -0700, Carlos C. Tapang wrote: >Thanks to all who pitched in their input to this issue. Most users of my >system are running Windows and don't want to have to reformat or repartition >their hard disk. So I am stuck with the DOS file system. I think the best >solution is to have my users use a FreeBSD boot floppy. The floppy will have >/boot/loader which I will point to the DOS-formatted hard disk in which the >kernel resides. > >>The flags and values in the BIOS data area would not necessarily >>be at their default values, so restoring the vectors might itself >>crash the BIOS (because it's reconfigured itself for the present >>vectors/drivers, not the default ones). >> >>Some hardware (eg. popular SCSI controllers) also configures itself >>differently when it finds it's running on DOS/Windows. This kind >>of thing in any scenario in which we start DOS then kill it would >>have the potential to seriously confuse matters. >> >>Incidentally (to correct a point made in an earlier post) *all* >>versions of DOS since 1.x have changed interrupt vectors. This is >>not a DOS 7+ phenomenon. The reason FBSDBOOT.EXE is deprecated at >>this stage is that, in the future, VM86 will be increasingly relied >>on by FreeBSD. And FBSDBOOT.EXE has *never* worked reliably in a >>VM86 context. >> >>-- >>Robert Nordier >> >> >>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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 18: 2:34 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 19FFF15678 for ; Wed, 19 May 1999 18:01:39 -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 VAA76976; Wed, 19 May 1999 21:00:51 -0400 (EDT) Date: Wed, 19 May 1999 21:00:50 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Luoqi Chen Cc: jerry.alexandratos@perspectives.net, jlemon@americantv.com, ctapang@easystreet.com, current@FreeBSD.ORG Subject: Re: FBSDBOOT.EXE In-Reply-To: <199905191227.IAA11701@lor.watermarkgroup.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 Wed, 19 May 1999, Luoqi Chen wrote: > > Jonathan Lemon says: > > : > > : Not true. VM86 is also required to support VESA. Also, it is used > > : for reliable memory detection (which is why I want to make it mandatory). > > : No more "My Stinkpad only detected 64M, what do I do now??!" questions. > > > > Actually, even with VM86, the kernel still doesn't correctly detect the > > StinkPad's memory. > > > > --Jerry > > > > name: Jerry Alexandratos || Open-Source software isn't a > > phone: 302.521.1018 || matter of life or death... > > email: jalexand@perspectives.net || ...It's much more important > > || than that! > > It just occurred to me that we might be able to use initial MTRR settings > by BIOS for memory detection (P6 and above, of course). Don't know how > reliable that is. And K6-family processors with newer BIOSes are usually write allocate-enabled and that can be used too. > > -lq > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 May 19 20:17:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-36.camalott.com [208.229.74.36]) by hub.freebsd.org (Postfix) with ESMTP id 331C8153D0 for ; Wed, 19 May 1999 20:17:03 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id WAA73457; Wed, 19 May 1999 22:16:53 -0500 (CDT) (envelope-from joelh) To: Jos Backus Cc: Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: mount_mfs panics (Was: ``65536-byte tape record bigger than suplied buffer'') References: <19990515221001.A59122@hal.mpn.cp.philips.com> <19990515222647.A59246@hal.mpn.cp.philips.com> From: Joel Ray Holveck Date: 19 May 1999 22:16:52 -0500 In-Reply-To: Jos Backus's message of "Sat, 15 May 1999 22:26:47 +0200" Message-ID: <86r9ocxwez.fsf_-_@detlev.UUCP> Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Well, I'll recheck mine... > It'd be interesting to see if you (and others) can reproduce this too. Using a May 17 15:00 CDT -current, I also have gotten a panic mounting MFS. The line from fstab is: /dev/da0s2b /tmp mfs rw 0 0 I commented it out, and things work fine. Since no dumpdev was configured yet, I don't have a dump, but can try to produce one now if somebody would find a backtrace useful. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 19 20:42:33 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 565D114D84; Wed, 19 May 1999 20:42:18 -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 LAA26517; Thu, 20 May 1999 11:41:29 +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 LAA15383; Thu, 20 May 1999 11:42:13 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id LAA25592; Thu, 20 May 1999 11:42:13 +0800 Message-Id: <199905200342.LAA25592@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org, hackers@freebsd.org Subject: SGI to release XFS under Open Source license Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 May 1999 11:42:13 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some of you may already know this - I'm wondering about the pain involved in fitting it to our architecture. Journaling. Hmmm. http://www.news.com/News/Item/0,4,36807,00.html?owv -- 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 Thu May 20 0:51:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 49CD414EBD for ; Thu, 20 May 1999 00:51:15 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id JAA29492 for ; Thu, 20 May 1999 09:51:14 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma029488; Thu, 20 May 99 09:51:14 +0200 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.6.10-1.2.2m-970826) with SMTP id JAA27887 for ; Thu, 20 May 1999 09:51:00 +0200 (MET DST) Received: (qmail 11930 invoked by uid 666); 20 May 1999 07:51:21 -0000 Date: Thu, 20 May 1999 09:51:21 +0200 From: Jos Backus To: Joel Ray Holveck Cc: Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: Re: mount_mfs panics (Was: ``65536-byte tape record bigger than suplied buffer'') Message-ID: <19990520095121.A8913@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19990515221001.A59122@hal.mpn.cp.philips.com> <19990515222647.A59246@hal.mpn.cp.philips.com> <86r9ocxwez.fsf_-_@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <86r9ocxwez.fsf_-_@detlev.UUCP>; from Joel Ray Holveck on Wed, May 19, 1999 at 10:16:52PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 19, 1999 at 10:16:52PM -0500, Joel Ray Holveck wrote: > >> Well, I'll recheck mine... > > It'd be interesting to see if you (and others) can reproduce this too. Fwiw, my home system (and that of a few others' as well) has been fixed by Luoqi's commit to kern_conf.c on the 18th. Cheers, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 1: 6:16 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 1807D14FE3 for ; Thu, 20 May 1999 01:06:12 -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 KAA29628; Thu, 20 May 1999 10:06:07 +0200 (MET DST) Date: Thu, 20 May 1999 10:06:04 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: USB BSD list Cc: FreeBSD current mailing list Subject: USB home page update 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 added two new sections to the USB home pages. http://www.etla.net/~n_hibma/usb/usb.pl One is the section on the project status. The most significant change is that it is an included document I can edit at home and upload once in a while. Much easier. The second thing is more down the page: a list of patches I have not been able to commit or are half way through (like the suspend one we saw lately). As I am not everyday working on the USB stuff, I would not like to deprive you of any improvements anyone else has made but I have not yet committed. Let me know if you have idea's on how to restyle the pages a bit so they become more readable. The pages is a bit of a mess. Please be sure to read the USB-BSD@egroups.com mailing list if you are interested. (to subscribe, go to www.egroups.com) Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 2:13:50 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 A6C941584E for ; Thu, 20 May 1999 02:13:47 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA32546 for current@freebsd.org; Thu, 20 May 1999 11:13:46 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905200913.LAA32546@freebsd.dk> Subject: UPDATE8: : ATA/ATAPI driver new version available. To: current@freebsd.org Date: Thu, 20 May 1999 11:13:46 +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 Eigth update to the new ATA/ATAPI driver: Fixed problems: LS120/ZIP drives still currupted data. Reworked once again, buffered I/O is just ignoring any sizehints it is given :( Now the atapifd driver splits up requests for devices that has limitted transfer size. ISA only configs fails on boot with interrupt timeouts. The new-bus integration introduced a bug where the softc ptr was lost during the probe. 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 Thu May 20 2:32:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from blue.bad.bris.ac.uk (blue.bad.bris.ac.uk [137.222.132.60]) by hub.freebsd.org (Postfix) with SMTP id 21BF714C9D for ; Thu, 20 May 1999 02:32:13 -0700 (PDT) (envelope-from matt@blue.bad.bris.ac.uk) Received: (qmail 10243 invoked by uid 58871); 20 May 1999 09:32:11 -0000 Date: Thu, 20 May 1999 10:32:11 +0100 (BST) From: Matt Hamilton Reply-To: Matt Hamilton To: freebsd-current@freebsd.org Subject: mmap() on raw devices 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 Dear All, I am trying to mmap a raw device (/dev/rda0) yet mmap() keeps returning EINVAL. From what I have read on the list archives, mmap() should be able to map a character device (just not a block device), am I missing something here? I have tried this on 3.1-STABLE and 4.0-CURRENT, but no luck. TIA, Matt -------------------------------------------------------------------------------- Matt Hamilton matt.hamilton@acm.org Hamilton Computing +44 (0)797 909 2482 -------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 3: 2:45 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 F3CEE14D96 for ; Thu, 20 May 1999 03:02:40 -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.00 #1) id 10kPeC-0001vq-00; Thu, 20 May 1999 12:01:52 +0200 From: Sheldon Hearn To: Joel Ray Holveck Cc: Jos Backus , Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: Re: mount_mfs panics In-reply-to: Your message of "19 May 1999 22:16:52 EST." <86r9ocxwez.fsf_-_@detlev.UUCP> Date: Thu, 20 May 1999 12:01:52 +0200 Message-ID: <7429.927194512@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19 May 1999 22:16:52 EST, Joel Ray Holveck wrote: > Using a May 17 15:00 CDT -current, I also have gotten a panic mounting > MFS. The line from fstab is: > > /dev/da0s2b /tmp mfs rw 0 0 Fixed on Tuesday, a little after 1 o'clock in the afternoon (GMT). 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 May 20 5:51: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id BE96715019 for ; Thu, 20 May 1999 05:50:56 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id WAA04691; Thu, 20 May 1999 22:49:19 +1000 (EST) Message-ID: <19990520224919.B4105@rf900.physics.usyd.edu.au> Date: Thu, 20 May 1999 22:49:19 +1000 From: David Dawes To: Matthew Thyer Cc: current@FreeBSD.ORG Subject: Re: XFree86 xsetpointer causes silo overflows (Was: Re: Fixed my MAMEd sio problem.) References: <199905170127.LAA04147@godzilla.zeta.org.au> <37418C29.DEECA1AC@camtech.com.au> <19990519182237.H29455@rf900.physics.usyd.edu.au> <3742C5B7.5E85F408@camtech.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3742C5B7.5E85F408@camtech.com.au>; from Matthew Thyer on Wed, May 19, 1999 at 11:37:51PM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 19, 1999 at 11:37:51PM +0930, Matthew Thyer wrote: >The big problem is that the silo overflows continue after I have >returned the pointer to the mouse (with "xsetpointer pointer"). > >This should close the joystick device shouldn't it ? No. I've had a look through some of the XInput code, and it seems that it isn't unusual for an Xserver to open all devices at server startup, and not close them until server exit. There are provisions for delaying the open until the device is referenced, and for closing it before the server exits. The XFree86-specific XInput code does the former, but not the latter. Here are some comments from the Xserver/Xi code (which is not XFree86-specific): * Caller: ProcXOpenDevice * * This is the implementation-dependent routine to open an input device. * Some implementations open all input devices when the server is first * initialized, and never close them. Other implementations open only * the X pointer and keyboard devices during server initialization, * and only open other input devices when some client makes an * XOpenDevice request. This entry point is for the latter type of * implementation. * * If the physical device is not already open, do it here. In this case, * you need to keep track of the fact that one or more clients has the * device open, and physically close it when the last client that has * it open does an XCloseDevice. * * The default implementation is to do nothing (assume all input devices * are opened during X server initialization and kept open). * Caller: ProcXCloseDevice * * Take care of implementation-dependent details of closing a device. * Some implementations may actually close the device, others may just * remove this clients interest in that device. * * The default implementation is to do nothing (assume all input devices * are initialized during X server initialization and kept open). There is one aspect of XFree86's XInput support that I do consider a bug, and that is that it doesn't close the extended input devices when VT switching away from the server. We'll probably fix that in 4.0. >If it doesn't then there is a problem with either the X server >or FreeBSD. > >Bruce has already indicated that there is a problem with the >FreeBSD joystick driver but he thought it should stop when the >joystick device is closed but I see that the problem continues >until I restart the X server so that would seem to indicate a >problem with the X server. IMHO the problem is in the joystick driver and in your assumptions. By configuring the joystick in your Xserver config file, you're giving the server exclusive use of the device for the lifetime of the X server process. Implementing more agressive closing might solve your particular problem, but it doesn't deal with the real problem of the joystick driver causing the silo overflows. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 6:54: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 275D514F10 for ; Thu, 20 May 1999 06:53:56 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup1-34.iptelecom.net.ua [212.42.68.161]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id QAA27298; Thu, 20 May 1999 16:54:01 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.2) with ESMTP id QAA05614; Thu, 20 May 1999 16:53:51 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <374413EE.5D762DB4@altavista.net> Date: Thu, 20 May 1999 16:53:50 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: UPDATE8: : ATA/ATAPI driver new version available. References: <199905200913.LAA32546@freebsd.dk> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: >     ISA only configs fails on boot with interrupt timeouts. >         The new-bus integration introduced a bug where the softc ptr >         was lost during the probe. Thank you, now it finaly works on my laptop (ISA only config)! Sincerely, Maxim     To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 6:54:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id BDD9414F10 for ; Thu, 20 May 1999 06:54:41 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup1-34.iptelecom.net.ua [212.42.68.161]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id QAA27328 for ; Thu, 20 May 1999 16:54:48 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.2) with ESMTP id QAA05619 for ; Thu, 20 May 1999 16:54:38 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3744141D.1CC1EE6B@altavista.net> Date: Thu, 20 May 1999 16:54:37 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Plip almost unusable :( Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anybody have experience with plip usage on -current? For me it seems broken - generally it works, but when I trying to make more or less massive transfer (1-2 MB is sufficient for most cases) any of two system dying in panic. Also "ping -f -s 8000 "š kills remote or local host in several seconds :( Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 6:55:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 0728714CFE for ; Thu, 20 May 1999 06:55:30 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup1-34.iptelecom.net.ua [212.42.68.161]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id QAA27406; Thu, 20 May 1999 16:55:35 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.2) with ESMTP id QAA05627; Thu, 20 May 1999 16:55:25 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <3744144C.F06FF0C2@altavista.net> Date: Thu, 20 May 1999 16:55:24 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: "Carlos C. Tapang" Cc: Robert Nordier , Mike Smith , Luoqi Chen , thyerm@camtech.com.au, current@FreeBSD.ORG Subject: Re: SUMMARY: why you cant use FBSDBOOT.EXE anymore (Was: Re: FBSDBOOT.EXE) References: <024501bea240$ebb029b0$0d787880@apex.tapang> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Carlos C. Tapang" wrote: > Thanks to all who pitched in their input to this issue. Most users of my > system are running Windows and don't want to have to reformat or repartition > their hard disk. So I am stuck with the DOS file system. I think the best > solution is to have my users use a FreeBSD boot floppy. The floppy will have > /boot/loader which I will point to the DOS-formatted hard disk in which the > kernel resides. Correct me if I'm wrong, but loader is unable to directly load kernel from non-FreeBSD partition (DOS in your case), so problem is slightly more complicated but I though your can take PicoBSD (FreeBSD on floppy) and tweak it to match your needs. Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 8:16:30 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 F268E152A2 for ; Thu, 20 May 1999 08:16:28 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id JAA56044; Thu, 20 May 1999 09:16:24 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905201516.JAA56044@panzer.plutotech.com> Subject: Re: mmap() on raw devices In-Reply-To: from Matt Hamilton at "May 20, 1999 10:32:11 am" To: matt.hamilton@acm.org Date: Thu, 20 May 1999 09:16:24 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Hamilton wrote... > Dear All, > > I am trying to mmap a raw device (/dev/rda0) yet mmap() keeps returning > EINVAL. From what I have read on the list archives, mmap() should be able > to map a character device (just not a block device), am I missing > something here? > > I have tried this on 3.1-STABLE and 4.0-CURRENT, but no luck. You'll only be able to mmap a device node if it supports mmaping. The da(4) driver, like the sd(4) driver before it, doesn't support mmapping. 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 Thu May 20 9: 7:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from send205.yahoomail.com (web131.yahoomail.com [205.180.60.174]) by hub.freebsd.org (Postfix) with SMTP id EC88E15011 for ; Thu, 20 May 1999 09:07:31 -0700 (PDT) (envelope-from valsho@yahoo.com) Message-ID: <19990520161016.29667.rocketmail@send205.yahoomail.com> Received: from [147.226.112.101] by web131.yahoomail.com; Thu, 20 May 1999 09:10:16 PDT Date: Thu, 20 May 1999 09:10:16 -0700 (PDT) From: Valentin Shopov Subject: Problem with ATA/ATAPI driver new version (update8) To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just tried the new ATA driver on my old ISA only notebook. After correct recognition of the hard disk: .... ad0: invalid primary partition table: no magic error 22: panic:..... what does that mean? Thanx, Val _____________________________________________________________ Do You Yahoo!? Free instant messaging and more at http://messenger.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 9:18:54 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 C433C15011 for ; Thu, 20 May 1999 09:18:45 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id SAA33267; Thu, 20 May 1999 18:18:05 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905201618.SAA33267@freebsd.dk> Subject: Re: Problem with ATA/ATAPI driver new version (update8) In-Reply-To: <19990520161016.29667.rocketmail@send205.yahoomail.com> from Valentin Shopov at "May 20, 1999 9:10:16 am" To: valsho@yahoo.com (Valentin Shopov) Date: Thu, 20 May 1999 18:18:05 +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 Valentin Shopov wrote: > I just tried the new ATA driver on my old ISA only > notebook. > After correct recognition of the hard disk: > > .... > ad0: invalid primary partition table: no magic > error 22: panic:..... Hmm, sounds like it has trouble talking to the disk, try changeing the two #if 0's in ata-disk.c so that it uses 16 bit transfers.. If that fails, try to make it only use singlesector transfers, quite a lot older disks messes up there... -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 May 20 10:22:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from qix.jmz.org (ppp008.infranet.fr [195.68.70.135]) by hub.freebsd.org (Postfix) with ESMTP id 3C23715195 for ; Thu, 20 May 1999 10:22:52 -0700 (PDT) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.3) id TAA04440; Thu, 20 May 1999 19:23:49 +0200 (MET DST) (envelope-from jmz@FreeBSD.ORG) Date: Thu, 20 May 1999 19:23:49 +0200 (MET DST) Message-Id: <199905201723.TAA04440@qix.jmz.org> From: Jean-Marc Zucconi To: dawes@rf900.physics.usyd.edu.au Cc: thyerm@camtech.com.au, current@FreeBSD.ORG In-reply-to: <19990520224919.B4105@rf900.physics.usyd.edu.au> (message from David Dawes on Thu, 20 May 1999 22:49:19 +1000) Subject: Re: XFree86 xsetpointer causes silo overflows (Was: Re: Fixed my MAMEd sio problem.) X-Mailer: Emacs References: <199905170127.LAA04147@godzilla.zeta.org.au> <37418C29.DEECA1AC@camtech.com.au> <19990519182237.H29455@rf900.physics.usyd.edu.au> <3742C5B7.5E85F408@camtech.com.au> <19990520224919.B4105@rf900.physics.usyd.edu.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> David Dawes writes: > IMHO the problem is in the joystick driver and in your assumptions. By > configuring the joystick in your Xserver config file, you're giving the > server exclusive use of the device for the lifetime of the X server > process. Implementing more agressive closing might solve your particular > problem, but it doesn't deal with the real problem of the joystick driver > causing the silo overflows. All interrupts are blocked when you read the joystick position, and this is the reason of the silo overflows. It is almost impossible to avoid (it could be possible to use a very high frequency timer and to check the joystick status during the interrupts, but this has an impact on the precision of the position). However keeping the device opened can't cause silo overflows. It seems rather than the X server continues to read the joystick position after the client stops using it. This can be considered as a bug in the X server. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@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 May 20 12:46:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from web113.yahoomail.com (web113.yahoomail.com [205.180.60.84]) by hub.freebsd.org (Postfix) with SMTP id B1890157CF for ; Thu, 20 May 1999 12:46:45 -0700 (PDT) (envelope-from valsho@yahoo.com) Message-ID: <19990520194716.10079.rocketmail@web113.yahoomail.com> Received: from [147.226.112.101] by web113.yahoomail.com; Thu, 20 May 1999 12:47:16 PDT Date: Thu, 20 May 1999 12:47:16 -0700 (PDT) From: Valentin Shopov Subject: Re: Problem with ATA/ATAPI driver new version (update8) To: Soren Schmidt Cc: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Soren Schmidt wrote: > It seems Valentin Shopov wrote: > > I just tried the new ATA driver on my old ISA only > > notebook. > > After correct recognition of the hard disk: > > > > .... > > ad0: invalid primary partition table: no magic > > error 22: panic:..... > > Hmm, sounds like it has trouble talking to the disk, > try changeing the > two #if 0's in ata-disk.c so that it uses 16 bit > transfers.. > If that fails, try to make it only use singlesector > transfers, quite > a lot older disks messes up there... > > -Søren > you're right, it's 16 bit transfer. After changing #if 0's it's working. Thanks. BTW, is it possible to define this in the "flags" of ata[12]? Val _____________________________________________________________ Do You Yahoo!? Free instant messaging and more at http://messenger.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 13: 6: 6 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 AE1C114E73 for ; Thu, 20 May 1999 13:06:01 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id WAA33724; Thu, 20 May 1999 22:05:56 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905202005.WAA33724@freebsd.dk> Subject: Re: Problem with ATA/ATAPI driver new version (update8) In-Reply-To: <19990520194716.10079.rocketmail@web113.yahoomail.com> from Valentin Shopov at "May 20, 1999 12:47:16 pm" To: valsho@yahoo.com (Valentin Shopov) Date: Thu, 20 May 1999 22:05:56 +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 Valentin Shopov wrote: > > > > Hmm, sounds like it has trouble talking to the disk, > > try changeing the > > two #if 0's in ata-disk.c so that it uses 16 bit > > transfers.. > > If that fails, try to make it only use singlesector > > transfers, quite > > a lot older disks messes up there... > > > > -Søren > > > > you're right, it's 16 bit transfer. After changing #if > 0's it's working. Thanks. > BTW, is it possible to define this in the "flags" of > ata[12]? When I get the time, I'll put in code that figures it out automagically, but a flag value to override could be handy... -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 May 20 13: 7:51 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 18FC414C09; Thu, 20 May 1999 13:07:45 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-182.skylink.it [194.185.55.182]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA10030; Thu, 20 May 1999 22:08:40 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id VAA03445; Thu, 20 May 1999 21:59:57 +0200 (CEST) Date: Thu, 20 May 1999 21:59:56 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Peter Wemm , Doug Rabson Cc: FreeBSD current Mailing list Subject: priorities 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 set a 'low' priority for the ide match as -100. I suggest we use a much lower value for that: -10000. With USB we have 15 levels already, spaced ten apart (welcome back BASIC :) makes 150. Has anyone come up with a decent set of levels yet, or is the best bet still Mike's example (can; #define PRIORITY_STUB -10000 #define PRIORITY_GENERIC -100 #define PRIORITY_BEST 1 #define PRIORITY_DEVICE 0 #define PRIORITY_FAIL -1 It sounds like we can loads of haggling about the names there... The last one is to take out the dependency on errno being greater than zero. Nick -- 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 Thu May 20 13:25:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.8]) by hub.freebsd.org (Postfix) with ESMTP id 2E00415090 for ; Thu, 20 May 1999 13:25:03 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id PAA24205; Thu, 20 May 1999 15:25:01 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 20 May 1999 15:25:01 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: current@freebsd.org Subject: Re: FBSDBOOT.EXE X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14148.28275.166902.9777@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem which remains unsolved is how to boot FreeBSD from DOS/Windows without the ability to use a boot floppy or boot CD. Perhaps a DOS/Windows utility which installs boot blocks? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 14:18:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from neuman.interaccess.com (neuman.interaccess.com [207.70.126.130]) by hub.freebsd.org (Postfix) with ESMTP id 6EEDC14E9F for ; Thu, 20 May 1999 14:18:28 -0700 (PDT) (envelope-from ourpressrelease@yahoo.com) Received: from bsbpub (d136.focal6.interaccess.com [207.208.186.136]) by neuman.interaccess.com (8.9.0/8.9.0) with SMTP id QAA13000; Thu, 20 May 1999 16:17:32 -0500 (CDT) Date: Thu, 20 May 1999 16:17:32 -0500 (CDT) Message-Id: <199905202117.QAA13000@neuman.interaccess.com> From: "Important Info." To: Subject: 40% Off Sale on Black Books 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 Quantities Are Limited . . . Place Your Order Today. 800-305-1458 - MUST MENTION SALE WHEN ORDERING TO GET DISCOUNT Disounted Books --------------- "Pulpit Confessions: Exposing The Black Church" by N. Moore (0965829928) Was $16.00 - NOW $9.60 ______________________________ "Brothers Beware: Games Black Women Play" by A. Marshall (0965829936) Was $12.00 - NOW $7.20 ______________________________ "Louis Farrakhan: Made In America" by A. Marshall (0965572900) Was $19.95 - NOW $11.97 ______________________________ "How To Juggle Women Without Getting Killed or Going Broke" (0965829944) Was $12.00 - NOW $7.20 ______________________________ Also Available $50 for 50,000 African American Email Addresses (Free Black Entreprneur list included for a limited time) CALL TODAY - (800) 305-1458 MUST MENTION THIS SALE WHEN ORDERING FREE COD CHARGES - $3 SHIPPING To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 16:15:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (Postfix) with ESMTP id D1EA6154A1 for ; Thu, 20 May 1999 16:15:41 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with SMTP id QAA30088; Thu, 20 May 1999 16:15:39 -0700 Message-ID: <000a01bea316$faf598c0$0d787880@apex.tapang> From: "Carlos C. Tapang" To: Cc: Subject: Re: SUMMARY: why you cant use FBSDBOOT.EXE anymore (Was: Re: FBSDBOOT.EXE) Date: Thu, 20 May 1999 16:17:50 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="x-user-defined" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim writes, >Correct me if I'm wrong, but loader is unable to directly load kernel from >non-FreeBSD partition (DOS in your case), so problem is slightly more >complicated but I though your can take PicoBSD (FreeBSD on floppy) and tweak it >to match your needs. > I have tried booting /boot/loader from a floppy, and then have loader boot a kernel that resides in a DOS file system. As far as I can tell, it works flawlessly. Carlos C. Tapang http://www.genericwindows.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 16:25:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14]) by hub.freebsd.org (Postfix) with ESMTP id 08DC415824 for ; Thu, 20 May 1999 16:25:23 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (216-99-199-225.cust.aracnet.com [216.99.199.225]) by jumping-spider.aracnet.com (8.9.1/8.9.0) with SMTP id QAA31181; Thu, 20 May 1999 16:25:22 -0700 Message-ID: <001101bea318$569f5de0$0d787880@apex.tapang> From: "Carlos C. Tapang" To: , Subject: Re: FBSDBOOT.EXE Date: Thu, 20 May 1999 16:27:33 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anthony writes, > >The problem which remains unsolved is how to boot FreeBSD from >DOS/Windows without the ability to use a boot floppy or boot CD. > >Perhaps a DOS/Windows utility which installs boot blocks? > Such a utility may be useful in most cases, but I do not want to have to mess around with my users' boot blocks at this point. When Generic Windows is stable enough and is ready for prime-time, then I will have a use for such a utility. The idea is to minimize the changes done to a user's system so that uninstalling Generic Windows (name to change later) will be easy. It's just too risky to modify the boot blocks and then have to put it in its original state during uninstall. Carlos C. Tapang http://www.genericwindows.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 16:30:18 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 1C46B15898 for ; Thu, 20 May 1999 16:30:16 -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 TAA21483; Thu, 20 May 1999 19:29:52 -0400 (EDT) Message-Id: <199905202329.TAA21483@cs.rpi.edu> To: "Carlos C. Tapang" Cc: alk@pobox.com, current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: FBSDBOOT.EXE In-Reply-To: Message from "Carlos C. Tapang" of "Thu, 20 May 1999 16:27:33 PDT." <001101bea318$569f5de0$0d787880@apex.tapang> Date: Thu, 20 May 1999 19:29:51 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lets also consider the case of a root partition exists on a device which the BIOS does not support, but DOS and FreeBSD do. A good example of this may be a SCSI controller without a BIOS, or maybe a network style load. A person could have just the kernel on the DOS parition, or have the driver for the device loaded and boot off of it that way. -- 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 Thu May 20 16:40:56 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 0F77F158C7 for ; Thu, 20 May 1999 16:40:51 -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 JAA15191; Fri, 21 May 1999 09:10:49 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA13729; Fri, 21 May 1999 09:10:48 +0930 (CST) Date: Fri, 21 May 1999 09:10:47 +0930 From: Greg Lehey To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: Plip almost unusable :( Message-ID: <19990521091047.P89091@freebie.lemis.com> References: <3744141D.1CC1EE6B@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i In-Reply-To: <3744141D.1CC1EE6B@altavista.net>; from Maxim Sobolev on Thu, May 20, 1999 at 04:54:37PM +0300 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 Thursday, 20 May 1999 at 16:54:37 +0300, Maxim Sobolev wrote: > Is anybody have experience with plip usage on -current? For me it seems > broken - generally it works, but when I trying to make more or less > massive transfer (1-2 MB is sufficient for most cases) any of two system > > dying in panic. Also "ping -f -s 8000 "  kills remote or > local host in several seconds :( What was the panic? 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 Thu May 20 18:44:11 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 DDF2614D25 for ; Thu, 20 May 1999 18:44:05 -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 JAA28731; Fri, 21 May 1999 09:43:03 +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 JAA04504; Fri, 21 May 1999 09:43:46 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA00122; Fri, 21 May 1999 09:43:46 +0800 Message-Id: <199905210143.JAA00122@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: shocking@bandicoot.prth.tensor.pgs.com, current@freebsd.org Subject: Re: MTRR support for AMD K6-2? In-reply-to: Your message of "Wed, 19 May 1999 14:05:21 MST." <199905192105.OAA00935@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 May 1999 09:43:46 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Do we have MTRR support for the AMD K6-2, and how's it done (e.g., if I want > > to allow mtrr support for my Voodoo Banshee) > > It's being worked on. The K6 is a problematic device, as it only > supports two memory ranges, as opposed to the eight the P6 does. > OK - give me a yell once it's ready for testing. 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 Thu May 20 18:53:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id 8977E14E8A; Thu, 20 May 1999 18:53:05 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id LAA06862; Fri, 21 May 1999 11:53:02 +1000 (EST) Message-ID: <19990521115302.D6580@rf900.physics.usyd.edu.au> Date: Fri, 21 May 1999 11:53:02 +1000 From: David Dawes To: Jean-Marc Zucconi Cc: thyerm@camtech.com.au, current@FreeBSD.ORG Subject: Re: XFree86 xsetpointer causes silo overflows (Was: Re: Fixed my MAMEd sio problem.) References: <199905170127.LAA04147@godzilla.zeta.org.au> <37418C29.DEECA1AC@camtech.com.au> <19990519182237.H29455@rf900.physics.usyd.edu.au> <3742C5B7.5E85F408@camtech.com.au> <19990520224919.B4105@rf900.physics.usyd.edu.au> <199905201723.TAA04440@qix.jmz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905201723.TAA04440@qix.jmz.org>; from Jean-Marc Zucconi on Thu, May 20, 1999 at 07:23:49PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 20, 1999 at 07:23:49PM +0200, Jean-Marc Zucconi wrote: >>>>>> David Dawes writes: > > > IMHO the problem is in the joystick driver and in your assumptions. By > > configuring the joystick in your Xserver config file, you're giving the > > server exclusive use of the device for the lifetime of the X server > > process. Implementing more agressive closing might solve your particular > > problem, but it doesn't deal with the real problem of the joystick driver > > causing the silo overflows. > >All interrupts are blocked when you read the joystick position, and >this is the reason of the silo overflows. It is almost impossible to >avoid (it could be possible to use a very high frequency timer and to >check the joystick status during the interrupts, but this has an >impact on the precision of the position). > >However keeping the device opened can't cause silo overflows. It >seems rather than the X server continues to read the joystick >position after the client stops using it. This can be considered as a >bug in the X server. That's implicit in the device remaining open. In the context of the X server's input device handling, "Open" means make active, and "Close" means make inactive. For most devices, the fd is added to the list of fds to select() on. For the joystick device, a timer callback is installed to check the device at regular intervals. This is never disabled once it has been started. If someone has a fix for this, please submit it to patch@xfree86.org and it can be included in our next 3.3.x release. I'll keep this issue in mind while working on the input device code for XFree86 4.0. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 21:25:14 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 E332F14ECA for ; Thu, 20 May 1999 21:25:10 -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 OAA10853; Fri, 21 May 1999 14:25:07 +1000 Date: Fri, 21 May 1999 14:25:07 +1000 From: Bruce Evans Message-Id: <199905210425.OAA10853@godzilla.zeta.org.au> To: current@FreeBSD.ORG, sobomax@altavista.net Subject: Re: Plip almost unusable :( Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is anybody have experience with plip usage on -current? For me it seems >broken - generally it works, but when I trying to make more or less >massive transfer (1-2 MB is sufficient for most cases) any of two system > >dying in panic. Also "ping -f -s 8000 "š kills remote or >local host in several seconds :( This is normal if you don't use the current workaround of configuring ppp. New-bus broke the previous workarounds of configuring slip or putting ppbus in device class "net". I haven't checked that configuring ppp actually helps for plip. The workaround provided by configuring slip was slightly stronger. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 20 21:35:40 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 F16FC15316 for ; Thu, 20 May 1999 21:35:37 -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 OAA11995; Fri, 21 May 1999 14:35:31 +1000 Date: Fri, 21 May 1999 14:35:31 +1000 From: Bruce Evans Message-Id: <199905210435.OAA11995@godzilla.zeta.org.au> To: gibbs@narnia.plutotech.com, mike@smith.net.au Subject: Re: "hanging root device to da0s1a" Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I'm not sure why it happens like this; try putting a DELAY() just >> before we actually set the root device and see if you can put it off. > >Why not just spl() protect that printf call so that its output is >dumped contiguously into the console buffer? This would just move the race. It is probably already elsewhere for serial consoles. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 21 1:21:20 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 5FDBA14D61; Fri, 21 May 1999 01:21:16 -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 JAA67799; Fri, 21 May 1999 09:21:13 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 21 May 1999 09:21:12 +0100 (BST) From: Doug Rabson To: Nick Hibma Cc: Peter Wemm , Doug Rabson , FreeBSD current Mailing list Subject: Re: priorities 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 Thu, 20 May 1999, Nick Hibma wrote: > > You set a 'low' priority for the ide match as -100. I suggest we use a > much lower value for that: -10000. With USB we have 15 levels already, > spaced ten apart (welcome back BASIC :) makes 150. > > Has anyone come up with a decent set of levels yet, or is the best bet > still Mike's example (can; > > > #define PRIORITY_STUB -10000 > #define PRIORITY_GENERIC -100 > #define PRIORITY_BEST 1 > #define PRIORITY_DEVICE 0 > #define PRIORITY_FAIL -1 > > It sounds like we can loads of haggling about the names there... The > last one is to take out the dependency on errno being greater than > zero. I would actually quite like to keep the possibility of returning an errno. It gives the possibility of returning an appropriate error if something strange happened (other than the hardware not being present). -- 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 Fri May 21 1:30:23 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 E8936151F1; Fri, 21 May 1999 01:30:19 -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 KAA03040; Fri, 21 May 1999 10:22:39 +0200 (MET DST) Date: Fri, 21 May 1999 10:22:37 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Doug Rabson Cc: Nick Hibma , Peter Wemm , Doug Rabson , FreeBSD current Mailing list Subject: Re: priorities 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 > > #define PRIORITY_FAIL -1 > > > > It sounds like we can loads of haggling about the names there... The > > last one is to take out the dependency on errno being greater than > > zero. > > I would actually quite like to keep the possibility of returning an errno. > It gives the possibility of returning an appropriate error if something > strange happened (other than the hardware not being present). How do you guarantuee that the errno is positive? Add an assert somewhere, like checking whether ENXIO >= PRIORITY_FAIL? Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 21 1:35:27 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 CE6CE15959; Fri, 21 May 1999 01:35:23 -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 JAA70961; Fri, 21 May 1999 09:35:02 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 21 May 1999 09:35:02 +0100 (BST) From: Doug Rabson To: Nick Hibma Cc: Nick Hibma , Peter Wemm , Doug Rabson , FreeBSD current Mailing list Subject: Re: priorities 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, 21 May 1999, Nick Hibma wrote: > > > #define PRIORITY_FAIL -1 > > > > > > It sounds like we can loads of haggling about the names there... The > > > last one is to take out the dependency on errno being greater than > > > zero. > > > > I would actually quite like to keep the possibility of returning an errno. > > It gives the possibility of returning an appropriate error if something > > strange happened (other than the hardware not being present). > > > How do you guarantuee that the errno is positive? Add an assert > somewhere, like checking whether ENXIO >= PRIORITY_FAIL? They just are positive and have always been positive :-) Changing that (making errnos negative) would break so much code I don't even want to think about it. -- 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 Fri May 21 1:43: 3 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 86D9C14D61; Fri, 21 May 1999 01:42: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 SAA06293; Fri, 21 May 1999 18:42:57 +1000 Date: Fri, 21 May 1999 18:42:57 +1000 From: Bruce Evans Message-Id: <199905210842.SAA06293@godzilla.zeta.org.au> To: dfr@nlsystems.com, nick.hibma@jrc.it Subject: Re: priorities Cc: current@FreeBSD.ORG, dfr@FreeBSD.ORG, hibma@skylink.it, peter@netplex.com.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> How do you guarantuee that the errno is positive? Add an assert >> somewhere, like checking whether ENXIO >= PRIORITY_FAIL? > >They just are positive and have always been positive :-) > >Changing that (making errnos negative) would break so much code I don't >even want to think about it. From errno.h: #ifdef KERNEL /* pseudo-errors returned inside kernel to modify return to process */ #define ERESTART (-1) /* restart syscall */ #define EJUSTRETURN (-2) /* don't modify regs, just return */ #define ENOIOCTL (-3) /* ioctl not handled by this layer */ #endif Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 21 1:58:10 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 2039514D61; Fri, 21 May 1999 01:58:02 -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 JAA76519; Fri, 21 May 1999 09:58:47 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 21 May 1999 09:58:47 +0100 (BST) From: Doug Rabson To: Bruce Evans Cc: nick.hibma@jrc.it, current@FreeBSD.ORG, dfr@FreeBSD.ORG, hibma@skylink.it, peter@netplex.com.au Subject: Re: priorities In-Reply-To: <199905210842.SAA06293@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, 21 May 1999, Bruce Evans wrote: > >> How do you guarantuee that the errno is positive? Add an assert > >> somewhere, like checking whether ENXIO >= PRIORITY_FAIL? > > > >They just are positive and have always been positive :-) > > > >Changing that (making errnos negative) would break so much code I don't > >even want to think about it. > > >From errno.h: > > #ifdef KERNEL > /* pseudo-errors returned inside kernel to modify return to process */ > #define ERESTART (-1) /* restart syscall */ > #define EJUSTRETURN (-2) /* don't modify regs, just return */ > #define ENOIOCTL (-3) /* ioctl not handled by this layer */ > #endif They aren't real errnos, just signals to the kernel. -- 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 Fri May 21 2:17:24 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 B1C861596D; Fri, 21 May 1999 02:17:18 -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 TAA09318; Fri, 21 May 1999 19:17:15 +1000 Date: Fri, 21 May 1999 19:17:15 +1000 From: Bruce Evans Message-Id: <199905210917.TAA09318@godzilla.zeta.org.au> To: bde@zeta.org.au, dfr@nlsystems.com Subject: Re: priorities Cc: current@FreeBSD.ORG, dfr@FreeBSD.ORG, hibma@skylink.it, nick.hibma@jrc.it, peter@netplex.com.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >They just are positive and have always been positive :-) >> > >> >Changing that (making errnos negative) would break so much code I don't >> >even want to think about it. >> >> >From errno.h: >> >> #ifdef KERNEL >> /* pseudo-errors returned inside kernel to modify return to process */ >> #define ERESTART (-1) /* restart syscall */ >> #define EJUSTRETURN (-2) /* don't modify regs, just return */ >> #define ENOIOCTL (-3) /* ioctl not handled by this layer */ >> #endif > >They aren't real errnos, just signals to the kernel. Same as all other error codes in the kernel. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 21 2:34:16 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 96EC514BCD; Fri, 21 May 1999 02:34:11 -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 KAA76722; Fri, 21 May 1999 10:35:39 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 21 May 1999 10:35:39 +0100 (BST) From: Doug Rabson To: Bruce Evans Cc: current@FreeBSD.ORG, dfr@FreeBSD.ORG, hibma@skylink.it, nick.hibma@jrc.it, peter@netplex.com.au Subject: Re: priorities In-Reply-To: <199905210917.TAA09318@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, 21 May 1999, Bruce Evans wrote: > >> >They just are positive and have always been positive :-) > >> > > >> >Changing that (making errnos negative) would break so much code I don't > >> >even want to think about it. > >> > >> >From errno.h: > >> > >> #ifdef KERNEL > >> /* pseudo-errors returned inside kernel to modify return to process */ > >> #define ERESTART (-1) /* restart syscall */ > >> #define EJUSTRETURN (-2) /* don't modify regs, just return */ > >> #define ENOIOCTL (-3) /* ioctl not handled by this layer */ > >> #endif > > > >They aren't real errnos, just signals to the kernel. > > Same as all other error codes in the kernel. What I meant was that they are not real error conditions and as such will not be returned from the device probe methods so there isn't a problem. -- 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 Fri May 21 5:51: 6 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 F13081531A for ; Fri, 21 May 1999 05:51:01 -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 IAA09793; Fri, 21 May 1999 08:50:27 -0400 (EDT) Date: Fri, 21 May 1999 08:50:26 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: Mike Smith , shocking@bandicoot.prth.tensor.pgs.com, current@FreeBSD.ORG Subject: Re: MTRR support for AMD K6-2? In-Reply-To: <199905210143.JAA00122@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 On Fri, 21 May 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > > > > > Do we have MTRR support for the AMD K6-2, and how's it done (e.g., if I want > > > to allow mtrr support for my Voodoo Banshee) > > > > It's being worked on. The K6 is a problematic device, as it only > > supports two memory ranges, as opposed to the eight the P6 does. > > > > OK - give me a yell once it's ready for testing. I've got the docs and I _DO_ plan on writing the support relatively soon; I have been having busy weekends though. > > > 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 > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 Fri May 21 8:44: 0 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 C65D2159BD for ; Fri, 21 May 1999 08:43:57 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id JAA12876; Fri, 21 May 1999 09:33:50 -0600 (MDT) Date: Fri, 21 May 1999 09:33:50 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905211533.JAA12876@narnia.plutotech.com> To: Bruce Evans Cc: current@FreeBSD.org Subject: Re: "hanging root device to da0s1a" X-Newsgroups: pluto.freebsd.current In-Reply-To: <199905210435.OAA11995@godzilla.zeta.org.au> 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 <199905210435.OAA11995@godzilla.zeta.org.au> you wrote: >>> I'm not sure why it happens like this; try putting a DELAY() just >>> before we actually set the root device and see if you can put it off. >> >>Why not just spl() protect that printf call so that its output is >>dumped contiguously into the console buffer? > > This would just move the race. It is probably already elsewhere for > serial consoles. Perhaps I should use the log facility instead of printf in the announce code? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 21 8:53:48 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 65A6E159A9 for ; Fri, 21 May 1999 08:53:28 -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 LAA23099; Fri, 21 May 1999 11:53:25 -0400 (EDT) (envelope-from wollman) Date: Fri, 21 May 1999 11:53:25 -0400 (EDT) From: Garrett Wollman Message-Id: <199905211553.LAA23099@khavrinen.lcs.mit.edu> To: Nick Hibma Cc: FreeBSD current Mailing list Subject: Re: priorities In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > How do you guarantuee that the errno is positive? Add an assert > somewhere, like checking whether ENXIO >= PRIORITY_FAIL? No, we simply define it to be so. -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 Fri May 21 9: 7:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles521.castles.com [208.214.165.85]) by hub.freebsd.org (Postfix) with ESMTP id 9AA6F14F5F for ; Fri, 21 May 1999 09:07:45 -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 UAA00358; Thu, 20 May 1999 20:27:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905210327.UAA00358@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: W Gerald Hicks Cc: Mike Smith , current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: FBSDBOOT.EXE In-reply-to: Your message of "Sun, 16 May 1999 23:09:21 EDT." <199905170309.XAA16468@bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 May 1999 20:27:09 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The loader won't help you because you are booting from under DOS, but > > the loader will boot the kernel just fine off a DOS filesystem. > > I'd like to understand this aspect of the loader better. This mode > might be useful for booting from (for example) a DOS flash filesystem? Typically a bootable volume on the PC has a helper BIOS that makes it look like a floppy disk. > Um... off to the source code. Thanks for the tip. The loader's multiple filesystem support is pretty simple and consequently a bit stupid; it will simply apply every filesystem module to the current device until one works (yay!) or they all fail. It's so stupid that you can even call it recursively (this is how transparent gunzipping works, and why the files have to have different names). -- \\ 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 May 21 11:52:30 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 9C80714F9F for ; Fri, 21 May 1999 11:52:20 -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 OAA09011 for ; Fri, 21 May 1999 14:52:15 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA03256; Fri, 21 May 1999 14:51:45 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id OAA77331 for freebsd-current@freebsd.org; Fri, 21 May 1999 14:51:45 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905211851.OAA77331@bb01f39.unx.sas.com> Subject: 4.0-current install problem(s) To: freebsd-current@freebsd.org Date: Fri, 21 May 1999 14:51:45 -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 build a 4.0-current SNAP each evenning, and thought I'd give a new install a try since the dev_t issue appears to have been resolved.. Unfortunately, booting from either a CD or boot floppies, after probing the ppi0(or maybe plip0) device, the system spontaniously reboots (and I can't easily read the last few message lines). I then went into the /snap/release area and starting re-running the release.8 target while removing devices from the GENERIC config file used for the boot floppies. I finally got it down to the point where I get the following: error 6: panic: cannot mount root (2) syncing disks... done Automatic reboot in 15 seconds... etc, etc, etc So, I'll continue to see if I can narrow down the problem, but it looks like we have a problem mounting an MFSROOT root partition which the boot/install system requires. Comments & critiques are welcome! Thanks! -John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 21 18: 9: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from imc01.ex.nus.edu.sg (imc01.ex.nus.edu.sg [137.132.14.60]) by hub.freebsd.org (Postfix) with ESMTP id 8BC7614CA6; Fri, 21 May 1999 18:08:58 -0700 (PDT) (envelope-from ccegongw@nus.edu.sg) Received: by imc01.ex.nus.edu.sg with Internet Mail Service (5.5.2448.0) id ; Sat, 22 May 1999 09:09:37 +0800 Message-ID: <762388C091FAD01180FF00A024621378E8EDD1@exs01.ex.nus.edu.sg> From: Gong Wei To: "'stable@freebsd.org'" , "'current@freebsd.org'" Subject: commercial products for computer telephony development (*BSD and/ or Linux) Date: Sat, 22 May 1999 09:09:35 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BEA3EF.C20D6DA6" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01BEA3EF.C20D6DA6 Content-Type: text/plain; charset="ISO-8859-1" Hi all, Is there any commercial products for computer telephony development on *BSD and/or Linux exists today? Basically we are looking for quite standard features like interactive voice response, voice messaging, text to speech, fax, notification systems, etc. I am in fact trying one product from Dialogic ( http://www.dialogic.com) but unfortunately it doesn't support *BSD/Linux :-( Any hints/pointer of info would be much appreciated! ------_=_NextPart_000_01BEA3EF.C20D6DA6 Content-Type: application/octet-stream; name="Gong Wei.vcf" Content-Disposition: attachment; filename="Gong Wei.vcf" BEGIN:VCARD VERSION:2.1 N:Wei;Gong;;; FN:Gong Wei ORG:National University of Singapore; TITLE:Analyst Programmer TEL;WORK;VOICE:+65 8746421 TEL;PAGER;VOICE:+65 94963742 TEL;WORK;FAX:+65 7780198 ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;Computer Centre=0D=0ANational University of Singapore=0D=0A2 Engineering D= rive 4;Singapore;;117584;Singapore LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Computer Centre=0D=0ANational University of Singapore=0D=0A2 Engineering Dri= ve 4=0D=0ASingapore, 117584=0D=0ASingapore EMAIL;PREF;INTERNET:ccegongw@nus.edu.sg REV:19990518T103531Z END:VCARD ------_=_NextPart_000_01BEA3EF.C20D6DA6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 21 18:44: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C08AD15133 for ; Fri, 21 May 1999 18:44:01 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA69156; Fri, 21 May 1999 18:43:53 -0700 (PDT) (envelope-from dillon) Date: Fri, 21 May 1999 18:43:53 -0700 (PDT) From: Matthew Dillon Message-Id: <199905220143.SAA69156@apollo.backplane.com> To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: -current deadlocks within 5 mins, over NFS References: <199905070817.DAA15632@home.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Matt, I told you about this before, but completely forgot about it. After :doing considerable testing on my test servers, i thought -current was safe :enough to try on our production shell servers. I installed -current on one :of my servers, and to my dismay, it hung. :) : :Within 5 minutes of running, nearly every process is blocked on 'inode', :with the exception of a single 'cp' stuck in vmopar. : :I have a very silly, *very* poorly written script i run out of cron, every :10 mins or so, to update my passwd and group files. : :#/bin/sh : :cp /home/private/passwd /etc :cp /home/private/master.passwd /etc :cp /home/private/group /etc :rm /etc/spwd.db.tmp >/dev/null 2>&1 :pwd_mkdb /etc/master.passwd : :Kevin : ( Also in a later conversation Kevin indicated that a cron job on the server was updating /home/private/, creating a race between the server operating on /home/private and the client trying to copy files from /home/private. It is this race which is revealing the bug ). I've managed to repeat the problem with two scripts. On the server: while (1) cp file1 file2 echo -n "l" end And on the client: while (1) cp file2 /tmp/test3 echo -n "C" end On the client: ccccccccccccccccp: /tmp/test3: Bad address cccccccccccccccp: /tmp/test3: Bad address cccp: /tmp/test3: Bad address cccccccccp: /tmp/test3: Bad address ccccccccccccccccccp: /tmp/test3: Bad address cccccccccp: /tmp/test3: Bad address cccccccccccccp: /tmp/test3: Bad address cccccccccccccccccccccccccccp: /tmp/test3: Bad address cccccccccccccccccccccccccccccccccp: /tmp/test3: Bad address ccccccccccccccccccccccccccccccccccccccccccccccccccccccccp: /tmp/test3: Bad address cc ( The Bad address errors are correct for NFS considering what the server is doing to the poor file. The hang of course is not ) The cp process on the client gets stuck in vmopar, as previously reported. Fortunately I can have a gdb already running on the client on the live kernel so it's easy to see what is going on. The problem is a same-process deadlock. A VM fault occurs accessing a NFS-backed page. The fault locks (PG_BUSY's) the page in question then calls vnode_pager_getpages() to bring the page in. This filters down into an nfs_getpages() call which then calls nfs_readrpc(). nfs_readrpc() normally ( and properly ) tries to keep the vnode synchronized to the NFS state returned by the RPC. The problem is that if the state indicates that the server has truncated the file, vnode_pager_setsize() will be called and will attempt to remove all the pages beyond the truncation point from the VM object. Unfortunately, at least one of those pages has been locked by the same process. Bewm. Deadlock. So, how to fix? The only thing I can think of is to pass a flag to nfs_readrpc() so it knows the RPC is related to a VM fault, and to then allow nfs_readrpc() to leave np->n_size and vap->va_size *unsynchronized* if a file truncation occurs. i.e. to avoid calling vnode_pager_setsize() and thus avoid the deadlock. This is kinda icky. We have no opportunity anywhere to call vnode_pager_setsize() because the faulted page must remain BUSY'd throughout the entire getpages operation. Comments? ( If I haven't confused the bajeezus out of everyone, that is :-) ) -Matt Matthew Dillon 17754 c41d4940 c45e9000 0 15192 15192 804006 S cp vmopar c049b930 vm_page_t 0xc049b930: object = 0xc46297b4, pindex = 0x0, phys_addr = 0x2732000, queue = 0x0, flags = 0x83, (PG_BUSY|PG_WANTED|PG_REFERENCED) pc = 0x32, wire_count = 0x0, hold_count = 0x0, act_count = 0x0, busy = 0x0, valid = 0x0, dirty = 0x0 #0 mi_switch () at ../../kern/kern_synch.c:827 #1 0xc0137f21 in tsleep (ident=0xc049b930, priority=0x4, wmesg=0xc023bac7 "vmopar", timo=0x0) at ../../kern/kern_synch.c:443 #2 0xc01e8f12 in vm_object_page_remove (object=0xc46297b4, start=0x0, end=0x1, clean_only=0x0) at ../../vm/vm_page.h:555 #3 0xc01ed93f in vnode_pager_setsize (vp=0xc46208c0, nsize=0x0000000000000000) at ../../vm/vnode_pager.c:285 #4 0xc01a3017 in nfs_loadattrcache (vpp=0xc45eab94, mdp=0xc45eaba0, dposp=0xc45eaba4, vaper=0x0) at ../../nfs/nfs_subs.c:1383 #5 0xc01abc7c in nfs_readrpc (vp=0xc46208c0, uiop=0xc45eac08, cred=0xc09ba400) at ../../nfs/nfs_vnops.c:1060 #6 0xc0184f05 in nfs_getpages (ap=0xc45eac44) at ../../nfs/nfs_bio.c:154 #7 0xc01edefa in vnode_pager_getpages (object=0xc46297b4, m=0xc45eacec, count=0x1, reqpage=0x0) at vnode_if.h:1067 #8 0xc01e2069 in vm_fault (map=0xc41d8d40, vaddr=0x28057000, fault_type=0x1, fault_flags=0x0) at ../../vm/vm_pager.h:130 #9 0xc0207508 in trap_pfault (frame=0xc45ead94, usermode=0x0, eva=0x28057000) at ../../i386/i386/trap.c:791 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 21 21:43: 9 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 CB1CC15110 for ; Fri, 21 May 1999 21:43:05 -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 OAA28230; Sat, 22 May 1999 14:43:04 +1000 Date: Sat, 22 May 1999 14:43:04 +1000 From: Bruce Evans Message-Id: <199905220443.OAA28230@godzilla.zeta.org.au> To: bde@zeta.org.au, gibbs@narnia.plutotech.com Subject: Re: "hanging root device to da0s1a" Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Perhaps I should use the log facility instead of printf in the announce >code? This would just duplicate boot-time output, since log() echoes everything using printf() if the log device is not open. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 21 22: 5:27 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 B1420151D2 for ; Fri, 21 May 1999 22:05:24 -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 BAA27982 for ; Sat, 22 May 1999 01:05:23 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA27037; Sat, 22 May 1999 01:04:53 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id BAA85997 for freebsd-current@freebsd.org; Sat, 22 May 1999 01:04:53 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905220504.BAA85997@bb01f39.unx.sas.com> Subject: Re: 4.0-current install problem(s)(cannot mount root) To: freebsd-current@freebsd.org Date: Sat, 22 May 1999 01:04:53 -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, Following up on my own mail... I applied the patch below from John Birrell, and the boot process got farther, but still fails. Chasing the problem alittle farther I found the following in ufs/mfs/mfs_vfsops.c: rootdev = makedev(255, mfs_minor++); printf("rootfs is %ld Kbyte compiled in MFS: dev_t 0x%08x\n", mfs_rootsize/1024,rootdev); if ((err = bdevvp(rootdev, &rootvp))) { printf("mfs_mountroot: can't find rootvp\n"); return (err); } After the assignment, rootdev is 0. The function bdevvp() then contains the following test: int bdevvp(dev, vpp) dev_t dev; struct vnode **vpp; { register struct vnode *vp; struct vnode *nvp; int error; if (dev == NODEV || major(dev) >= nblkdev || bdevsw(dev) == NULL) { *vpp = NULLVP; return (ENXIO); } Well, bdevsw(dev) is returning 0, thus the 3rd expression in the 'if' statement is true and causes ENXIO to be returned. I'm not sure where to go from here... Would someone more familiar with the mfs code and the boot sequence please comment on the above? Thanks! John Index: vfs_conf.c =================================================================== RCS file: /mirror/ncvs/src/sys/kern/vfs_conf.c,v retrieving revision 1.26 diff -u -r1.26 vfs_conf.c --- vfs_conf.c 1998/09/14 19:56:40 1.26 +++ vfs_conf.c 1999/05/22 03:15:41 @@ -52,6 +52,7 @@ * on SMP reentrancy */ #include "opt_bootp.h" +#include "opt_mfs.h" #include /* dev_t (types.h)*/ #include @@ -136,6 +137,9 @@ /* * Attempt the mount */ +#ifdef MFS_ROOT + err = VFS_MOUNT(mp, NULL, NULL, NULL, p); +#else err = ENXIO; orootdev = rootdev; if (rootdevs[0] == NODEV) @@ -154,6 +158,7 @@ if (err != ENXIO) break; } +#endif if (err) { /* * XXX should ask the user for the name in some cases. > Hi, > > I build a 4.0-current SNAP each evenning, and thought I'd give a new > install a try since the dev_t issue appears to have been resolved.. > > Unfortunately, booting from either a CD or boot floppies, after > probing the ppi0(or maybe plip0) device, the system spontaniously > reboots (and I can't easily read the last few message lines). > > I then went into the /snap/release area and starting re-running > the release.8 target while removing devices from the GENERIC > config file used for the boot floppies. > > I finally got it down to the point where I get the following: > > error 6: panic: cannot mount root (2) > syncing disks... done > Automatic reboot in 15 seconds... > > etc, etc, etc > > > > So, I'll continue to see if I can narrow down the problem, but > it looks like we have a problem mounting an MFSROOT root partition > which the boot/install system requires. > > Comments & critiques are welcome! > > > Thanks! > - -John > > > 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 May 21 22:55:56 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 B56751523C for ; Fri, 21 May 1999 22:55:51 -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 BAA29305 for ; Sat, 22 May 1999 01:55:50 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA27972; Sat, 22 May 1999 01:55:20 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id BAA86299 for freebsd-current@freebsd.org; Sat, 22 May 1999 01:55:20 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905220555.BAA86299@bb01f39.unx.sas.com> Subject: Re: 4.0-current install problem(s)(error mounting root) In-Reply-To: From "John W. DeBoskey" at "May 21, 1999 2:51:45 pm" To: freebsd-current@freebsd.org Date: Sat, 22 May 1999 01:55:20 -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, The following patch and John Birrell's patch posted earlier appear to fix the problem when booting a 4.0-current install floppy(kern.flp). The DEVT_FASCIST macro is incorrect and does the wrong thing when the device id 'x' passed into makedev is 255. Thanks, John Index: kern_conf.c =================================================================== RCS file: /mirror/ncvs/src/sys/kern/kern_conf.c,v retrieving revision 1.40 diff -u -r1.40 kern_conf.c --- kern_conf.c 1999/05/18 13:14:43 1.40 +++ kern_conf.c 1999/05/22 05:32:59 @@ -200,6 +200,8 @@ makedev(int x, int y) { #ifdef DEVT_FASCIST + if (x == 255) + return ((dev_t) ((x << 8) | y)); return ((dev_t) (((255 - x) << 8) | y)); #else return ((dev_t) ((x << 8) | y)); John Birrell's patch: Index: vfs_conf.c =================================================================== RCS file: /mirror/ncvs/src/sys/kern/vfs_conf.c,v retrieving revision 1.26 diff -u -r1.26 vfs_conf.c --- vfs_conf.c 1998/09/14 19:56:40 1.26 +++ vfs_conf.c 1999/05/22 03:15:41 @@ -52,6 +52,7 @@ * on SMP reentrancy */ #include "opt_bootp.h" +#include "opt_mfs.h" #include /* dev_t (types.h)*/ #include @@ -136,6 +137,9 @@ /* * Attempt the mount */ +#ifdef MFS_ROOT + err = VFS_MOUNT(mp, NULL, NULL, NULL, p); +#else err = ENXIO; orootdev = rootdev; if (rootdevs[0] == NODEV) @@ -154,6 +158,7 @@ if (err != ENXIO) break; } +#endif if (err) { /* * XXX should ask the user for the name in some cases. > Hi, > > I build a 4.0-current SNAP each evenning, and thought I'd give a new > install a try since the dev_t issue appears to have been resolved.. > > Unfortunately, booting from either a CD or boot floppies, after > probing the ppi0(or maybe plip0) device, the system spontaniously > reboots (and I can't easily read the last few message lines). > > I then went into the /snap/release area and starting re-running > the release.8 target while removing devices from the GENERIC > config file used for the boot floppies. > > I finally got it down to the point where I get the following: > > error 6: panic: cannot mount root (2) > syncing disks... done > Automatic reboot in 15 seconds... > > etc, etc, etc > > > > So, I'll continue to see if I can narrow down the problem, but > it looks like we have a problem mounting an MFSROOT root partition > which the boot/install system requires. > > Comments & critiques are welcome! > > > Thanks! > - -John > > > 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 May 22 4: 1:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id CF9AA14E7F for ; Sat, 22 May 1999 04:01:49 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial4-96.netcologne.de [195.14.233.96]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id NAA04974; Sat, 22 May 1999 13:01:38 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id NAA01071; Sat, 22 May 1999 13:01:48 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Sat, 22 May 1999 13:01:48 +0200 (CEST) Message-Id: <199905221101.NAA01071@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: hodeleri@seattleu.edu Cc: obrien@NUXI.com, freebsd-current@FreeBSD.ORG In-reply-to: <3741237F.F528C8FA@seattleu.edu> (message from Eric Hodel on Tue, 18 May 1999 01:23:27 -0700) Subject: Re: No sound (Ensoniq Audio PCI 1370) Reply-To: van.woerkom@netcologne.de References: <199905151958.VAA14199@oranje.my.domain> <19990517105543.B47978@nuxi.com> <3741237F.F528C8FA@seattleu.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just use: > > device pcm0 > > and no more, since I only have a PCI card. So you reasoned something like This card has nothing to do with ISA, let the PCI routines figure out the parameters by themselves Joachim's Ensoniq driver was the first extension of Luigi's underlying pcm driver for ISA cards towards PCI. Looks like bus issues are not arranged 100%: On my FreeBSD 4.0-CURRENT #10: Fri May 21 19:50:23 CEST 1999 system I changed CONFIG to #device pcm0 at isa? port ? irq 10 drq 1 flags 0x0 device pcm0 at nexus? and got this messages after reboot es0: irq 11 at device 15.0 on pci0 pcm0: using I/O space register mapping at 0x6400 pcm1: unit not configured, perhaps you want pcm0 ? and indeed marc@oranje$ cat /dev/sndstat FreeBSD Audio Driver (981002) May 21 1999 19:50:06 Installed devices: pcm0: at 0x6400 irq 0 dma 0:0 the card is recognized by Luigi's driver. Compare this to what pcm(4) says: device pcm0 ... your first PnP audio card will be unit #1, i.e. it will be accessible as /dev/audio1, /dev/dsp1, etc. Many application default to using /dev/au- dio, so you can create symlinks from /dev/audio etc to the correct device entries as follows: cd /dev rm audio dsp dspW mixer ./MAKEDEV snd1 ln -s audio1 audio ln -s dsp1 dsp ln -s dspW1 dspW ln -s mixer1 mixer (note: the links are laid by MAKEDEV already) instead I had to use unit #0 via ./MAKEDEV snd0 and this way it works OK right now although I think it was not meant to. Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 22 6: 5:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (Postfix) with ESMTP id 79A6814C05 for ; Sat, 22 May 1999 06:05:44 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id GAA21933; Sat, 22 May 1999 06:05:10 -0700 (PDT) Message-ID: <3746AB6C.620A0D60@seattleu.edu> Date: Sat, 22 May 1999 06:04:44 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: van.woerkom@netcologne.de Cc: obrien@NUXI.com, freebsd-current@FreeBSD.ORG Subject: Re: No sound (Ensoniq Audio PCI 1370) References: <199905151958.VAA14199@oranje.my.domain> <19990517105543.B47978@nuxi.com> <3741237F.F528C8FA@seattleu.edu> <199905221101.NAA01071@oranje.my.domain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc van Woerkom wrote: > > > I just use: > > > > device pcm0 > > > > and no more, since I only have a PCI card. > > So you reasoned something like > > This card has nothing to do with ISA, let the PCI routines figure out > the parameters by themselves Exactly -- Eric Hodel hodeleri@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 22 6:21:12 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 068C314C05 for ; Sat, 22 May 1999 06:21:09 -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 OAA35781; Sat, 22 May 1999 14:22:27 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 22 May 1999 14:22:27 +0100 (BST) From: Doug Rabson To: Marc van Woerkom Cc: hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@freebsd.org Subject: Re: No sound (Ensoniq Audio PCI 1370) In-Reply-To: <199905221101.NAA01071@oranje.my.domain> 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, 22 May 1999, Marc van Woerkom wrote: > > I just use: > > > > device pcm0 > > > > and no more, since I only have a PCI card. > > So you reasoned something like > > This card has nothing to do with ISA, let the PCI routines figure out > the parameters by themselves > > Joachim's Ensoniq driver was the first extension of Luigi's underlying > pcm driver for ISA cards towards PCI. > > Looks like bus issues are not arranged 100%: I'm working on it. -- 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 May 22 8: 3:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 44B811500E for ; Sat, 22 May 1999 08:03:37 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id RAA20614; Sat, 22 May 1999 17:03:30 +0200 (CEST) (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 RAA04686; Sat, 22 May 1999 17:03:20 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Justin T. Gibbs" Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: "hanging root device to da0s1a" In-reply-to: Your message of "Wed, 19 May 1999 16:31:25 MDT." <199905192231.QAA09421@narnia.plutotech.com> Date: Sat, 22 May 1999 17:03:19 +0200 Message-ID: <4684.927385399@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905192231.QAA09421@narnia.plutotech.com>, "Justin T. Gibbs" writ es: >In article <199905191637.JAA03111@dingo.cdrom.com> you wrote: >> I'm not sure why it happens like this; try putting a DELAY() just >> before we actually set the root device and see if you can put it off. > >Why not just spl() protect that printf call so that its output is >dumped contiguously into the console buffer? Am I missing something here ? We shouldn't set the root device until CAM is done probing, right ? -- 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 May 22 10:39:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id D268614F3B for ; Sat, 22 May 1999 10:39:16 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id LAA08495; Sat, 22 May 1999 11:36:37 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <199905221736.LAA08495@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: "Justin T. Gibbs" , Mike Smith , current@FreeBSD.ORG Subject: Re: "hanging root device to da0s1a" In-reply-to: Your message of "Sat, 22 May 1999 17:03:19 +0200." <4684.927385399@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 May 1999 11:26:38 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In message <199905192231.QAA09421@narnia.plutotech.com>, "Justin T. Gibbs" wri >t >es: >>In article <199905191637.JAA03111@dingo.cdrom.com> you wrote: >>> I'm not sure why it happens like this; try putting a DELAY() just >>> before we actually set the root device and see if you can put it off. >> >>Why not just spl() protect that printf call so that its output is >>dumped contiguously into the console buffer? > >Am I missing something here ? We shouldn't set the root device until >CAM is done probing, right ? CAM has finished probing at this point, but it holds off on announcing devices until it has all necessary info. The drives may need to be spun up, etc. I believe the printf happens before the device has been opened and CAM blocks in the open until the device is really ready for service. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 22 10:48:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 261A814D93 for ; Sat, 22 May 1999 10:48:39 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id TAA21185; Sat, 22 May 1999 19:48:38 +0200 (CEST) (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 TAA05829; Sat, 22 May 1999 19:48:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Justin T. Gibbs" Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: "hanging root device to da0s1a" In-reply-to: Your message of "Sat, 22 May 1999 11:26:38 MDT." <199905221736.LAA08495@pluto.plutotech.com> Date: Sat, 22 May 1999 19:48:37 +0200 Message-ID: <5827.927395317@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905221736.LAA08495@pluto.plutotech.com>, "Justin T. Gibbs" write s: >>Am I missing something here ? We shouldn't set the root device until >>CAM is done probing, right ? > >CAM has finished probing at this point, but it holds off on announcing >devices until it has all necessary info. The drives may need to >be spun up, etc. I believe the printf happens before the device has >been opened and CAM blocks in the open until the device is really >ready for service. I think we should hold off the rootdev determination until after the printfs, unless you tell me that this will delay the boot by many seconds in too many cases. -- 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 May 22 11: 0: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 10C0A14D93 for ; Sat, 22 May 1999 11:00:05 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial8-214.netcologne.de [195.14.235.214]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id TAA27273; Sat, 22 May 1999 19:59:28 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id TAA00654; Sat, 22 May 1999 19:59:42 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Sat, 22 May 1999 19:59:42 +0200 (CEST) Message-Id: <199905221759.TAA00654@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: dfr@nlsystems.com Cc: van.woerkom@netcologne.de, hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@freebsd.org In-reply-to: (message from Doug Rabson on Sat, 22 May 1999 14:22:27 +0100 (BST)) Subject: ES 1370 audio driver and ncr SCSI driver interfere! Reply-To: van.woerkom@netcologne.de References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Joachim's Ensoniq driver was the first extension of Luigi's underlying > > pcm driver for ISA cards towards PCI. > > > > Looks like bus issues are not arranged 100%: > > I'm working on it. Great to hear. If there is any technical document about FreeBSD drivers and how they should manage their resources (and that is so recent, that it takes PCI into account) please tell me. I would like to understand what is going on to help myself - e.g. the ES1370's MIDI interface is unsupported yet .. Another remark - I filed a PR some weeks ago where I reported that my ncr SCSI controller dies during listening to real audio streams. Friday's -CURRENT still has this problem - but today I observed that it has nothing special to do with the real player or the Linux emulation layer. The same ncr confusion happens if I listen to MP3's and have disk activity (cvsup) at the same time .. so now I believe that it is an interference of the audio drivers { es0, pcm0 } with ncr0. Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 22 11:15:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id BF91A14E26 for ; Sat, 22 May 1999 11:15:15 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id MAA09033; Sat, 22 May 1999 12:11:52 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <199905221811.MAA09033@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: "Justin T. Gibbs" , Mike Smith , current@FreeBSD.ORG Subject: Re: "hanging root device to da0s1a" In-reply-to: Your message of "Sat, 22 May 1999 19:48:37 +0200." <5827.927395317@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 22 May 1999 12:01:53 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>CAM has finished probing at this point, but it holds off on announcing >>devices until it has all necessary info. The drives may need to >>be spun up, etc. I believe the printf happens before the device has >>been opened and CAM blocks in the open until the device is really >>ready for service. > >I think we should hold off the rootdev determination until after the >printfs, unless you tell me that this will delay the boot by many >seconds in too many cases. It will probably add 5->15 seconds for anyone with a cdrom drive with even greater delays for people with more than 2 or 3 devices. There are also devices like scanners and older WORM devices that can take up to a minute to become ready. It seems quite silly to me to hold up booting for devices that are not even referenced during boot. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 22 11:44:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 37D8D14E1E for ; Sat, 22 May 1999 11:44:53 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA21384; Sat, 22 May 1999 20:44:53 +0200 (CEST) (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 UAA05951; Sat, 22 May 1999 20:44:52 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Justin T. Gibbs" Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: "hanging root device to da0s1a" In-reply-to: Your message of "Sat, 22 May 1999 12:01:53 MDT." <199905221811.MAA09033@pluto.plutotech.com> Date: Sat, 22 May 1999 20:44:52 +0200 Message-ID: <5949.927398692@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905221811.MAA09033@pluto.plutotech.com>, "Justin T. Gibbs" write s: >>>CAM has finished probing at this point, but it holds off on announcing >>>devices until it has all necessary info. The drives may need to >>>be spun up, etc. I believe the printf happens before the device has >>>been opened and CAM blocks in the open until the device is really >>>ready for service. >> >>I think we should hold off the rootdev determination until after the >>printfs, unless you tell me that this will delay the boot by many >>seconds in too many cases. > >It will probably add 5->15 seconds for anyone with a cdrom drive with >even greater delays for people with more than 2 or 3 devices. There >are also devices like scanners and older WORM devices that can take >up to a minute to become ready. It seems quite silly to me to hold >up booting for devices that are not even referenced during boot. Hmm, OK then... -- 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 May 22 12:11:36 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 15114150F8 for ; Sat, 22 May 1999 12:11:32 -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 UAA00695; Sat, 22 May 1999 20:10:53 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 22 May 1999 20:10:53 +0100 (BST) From: Doug Rabson To: Marc van Woerkom Cc: hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@freebsd.org Subject: Re: ES 1370 audio driver and ncr SCSI driver interfere! In-Reply-To: <199905221759.TAA00654@oranje.my.domain> 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, 22 May 1999, Marc van Woerkom wrote: > > > Joachim's Ensoniq driver was the first extension of Luigi's underlying > > > pcm driver for ISA cards towards PCI. > > > > > > Looks like bus issues are not arranged 100%: > > > > I'm working on it. > > Great to hear. > > If there is any technical document about FreeBSD drivers and how they should > manage their resources (and that is so recent, that it takes PCI into account) > please tell me. I would like to understand what is going on to help myself - > e.g. the ES1370's MIDI interface is unsupported yet .. There isn't any such document as yet and some of the interfaces are still in a state of flux. I'm sure that some kind of documentation will be available before 4.0 ships. -- 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 May 22 12:40:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id C852514CC9; Sat, 22 May 1999 12:40:41 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA22395; Sat, 22 May 1999 21:16:31 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA17416; Sat, 22 May 1999 21:03:43 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905221903.VAA17416@yedi.iaf.nl> Subject: Re: de driver problem In-Reply-To: from Doug Rabson at "May 15, 1999 3:55:22 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Sat, 22 May 1999 21:03:43 +0200 (CEST) Cc: khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Doug Rabson wrote ... > On Sat, 15 May 1999, Wilko Bulte wrote: > > > As Doug Rabson wrote ... > > > On Mon, 10 May 1999, Wilko Bulte wrote: > > > > > > > > > > > > > Yeah. That must be why my 164lx won't netboot. > > > > > > > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit > > > > only) worked just dandy. > > > > > > That reminds me. Does your Alpine still work after the new-bus stuff? I > > > wasn't sure I hadn't broken it when I changed the apecs driver. > > > > After a buildworld of yesterday's -current and a new kernel things > > work just fine. As an added bonus the serial console seems to work better. > > It used to be very slow, looks like that is gone. > > > > If you want more info you'll have to wait a bit, I'll be offline for > > a week. > > Thats good. The slow serial sounds like it used to be polling (i.e. sio > interrupts weren't getting through). I've been away to Oslo this week, but I plan to bang a bit more on the console to see if it keeps working ok. | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 22 15:13:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id B088414D7B for ; Sat, 22 May 1999 15:13:22 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id RAA22494 for ; Sat, 22 May 1999 17:13:21 -0500 (CDT) Date: Sat, 22 May 1999 17:13:20 -0500 (CDT) From: Steve Price To: freebsd-current@freebsd.org Subject: libg2c.a in -current 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 Anyone know why libf2c* was renamed to libg2c* in egcs? Does egcs have a replacement for f2c? Would anyone object if I installed the header file, g2c.h, along with the library? -steve Index: Makefile =================================================================== RCS file: /home/ncvs/src/gnu/lib/libg2c/Makefile,v retrieving revision 1.3 diff -u -r1.3 Makefile --- Makefile 1999/05/01 22:30:14 1.3 +++ Makefile 1999/05/22 18:35:59 @@ -120,4 +120,8 @@ @mv ${.TARGET}.tmp ${.TARGET} .endif +beforeinstall: + ${INSTALL} -C -o ${BINOWN} -g ${BINGRP} -m 444 ${.CURDIR}/g2c.h \ + ${DESTDIR}/usr/include + .include To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 22 15:23:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from unknown (sar-fl2-27.ix.netcom.com [205.184.138.91]) by hub.freebsd.org (Postfix) with SMTP id E29DD14D13; Sat, 22 May 1999 15:23:37 -0700 (PDT) (envelope-from netstar44@popmail.com) From: Subject: FREE Y2K FIX !!! <..,:adv.,,< Date: Sat, 22 May 1999 18:24:49 Message-Id: <33.743743.233739@unknown> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ***************************************************************** ***************************************************************** THE GOOD NEWS IS: You can now test your computer for full Y2K compliance,(both BIOS and REAL TIME CLOCKS), and even correct it with a simple inexpensive download. THE GREAT NEWS IS: We offer a FREE TEST & EVALUATION period while you decide whether you want to purchase this solution. No one else offers the comprehensive guarantee that we have for you. For additional information on our free evaluation period, visit our site at: www.freey2kdownload.com ***************************************************************** To be removed from this mailing list please reply to: y2kfreetest.com and type REMOVE on the subject line. ***************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 22 17:47: 3 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 1320815101 for ; Sat, 22 May 1999 17:47:01 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id RAA22218; Sat, 22 May 1999 17:46:29 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Sat, 22 May 1999 17:46:28 -0700 (PDT) From: Doug White To: Doug Rabson Cc: FreeBSD current Mailing list Subject: Re: priorities 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, 21 May 1999, Doug Rabson wrote: > > It sounds like we can loads of haggling about the names there... The > > last one is to take out the dependency on errno being greater than > > zero. > > I would actually quite like to keep the possibility of returning an errno. > It gives the possibility of returning an appropriate error if something > strange happened (other than the hardware not being present). Echo that here. There are few things more annoying than device drivers that fail for unknown reasons. Even if the error doesn't make sense at first, we can trace the code back to the true point of failure. If you've worked on Windows or Macs, you know what I'm talking about ("Device failure" or "Could not switch your connection due to an error"). 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 Sat May 22 19:46:35 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 3BA1B14E3C for ; Sat, 22 May 1999 19:46:30 -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 MAA13333; Sun, 23 May 1999 12:45:47 +1000 Date: Sun, 23 May 1999 12:45:47 +1000 From: Bruce Evans Message-Id: <199905230245.MAA13333@godzilla.zeta.org.au> To: dima@tejblum.dnttm.rssi.ru, freebsd-current@FreeBSD.ORG Subject: Re: calcru and upages Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >calcru() access p_stats, which is in upages. Therefore, as I understand, >it should not be called on a swapped out process. Neither calcru() nor Does anyone object to moving everything except the stack from the upages to the proc table? Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 22 20:37:51 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 3D00514D93 for ; Sat, 22 May 1999 20:37:44 -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 841F922; Sun, 23 May 1999 11:37:40 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: dima@tejblum.dnttm.rssi.ru, freebsd-current@FreeBSD.ORG Subject: Re: calcru and upages In-reply-to: Your message of "Sun, 23 May 1999 12:45:47 +1000." <199905230245.MAA13333@godzilla.zeta.org.au> Date: Sun, 23 May 1999 11:37:40 +0800 From: Peter Wemm Message-Id: <19990523033740.841F922@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > >calcru() access p_stats, which is in upages. Therefore, as I understand, > >it should not be called on a swapped out process. Neither calcru() nor > > Does anyone object to moving everything except the stack from the upages > to the proc table? > > Bruce Well, we have three things that are about the same size: struct pcb u_pcb; 240 bytes struct sigacts u_sigacts; 292 bytes struct pstats u_stats; 248 bytes On the other hand: sizeof (struct proc) = 328 bytes. the pcb contains a heap of space for the FP state. It accounts for 176 of the 240 bytes, leaving 64-odd bytes left for the pcb proper. The ldt pointers need to move to proc scope for rfork()/clone(), and gc'ing a few things that can get it as low as 40 - 48 bytes. pcb_savefpu has padding in case a FPU emulator is used and is actually smaller than 176 bytes, and could be changed depending on whether it's a real or emulated fpu. IMHO, I'd move them to reference counted malloc'ed structs since sigacts needs to be shared for clone/rforked processes. I think there is also benefit to having the sigacts at least malloced, one day we should be able to extend the signals beyond the existing 32 set, at least for the 32 extra RT signals. I personally would love to see this come out of the upages, it makes tracking through a stack overflow even harder. We could put an unmapped red-line page below the bottom stack page to ensure we get a double fault on an overflow instead of mystery corruptions etc. I also think it's a step closer towards seperating thread context vs. process context. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 22 23:57:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id E75A814C1D for ; Sat, 22 May 1999 23:57:20 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id IAA23973; Sun, 23 May 1999 08:57:17 +0200 (CEST) (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 IAA07759; Sun, 23 May 1999 08:57:01 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: dima@tejblum.dnttm.rssi.ru, freebsd-current@FreeBSD.ORG Subject: Re: calcru and upages In-reply-to: Your message of "Sun, 23 May 1999 12:45:47 +1000." <199905230245.MAA13333@godzilla.zeta.org.au> Date: Sun, 23 May 1999 08:57:01 +0200 Message-ID: <7757.927442621@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905230245.MAA13333@godzilla.zeta.org.au>, Bruce Evans writes: >>calcru() access p_stats, which is in upages. Therefore, as I understand, >>it should not be called on a swapped out process. Neither calcru() nor > >Does anyone object to moving everything except the stack from the upages >to the proc table? not me. -- 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 Sun May 23 2:33: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 571AF14F8F for ; Sun, 23 May 1999 02:32:59 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id LAA24755; Sun, 23 May 1999 11:32:34 +0200 (CEST) (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 LAA08134; Sun, 23 May 1999 11:32:27 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Sheldon Hearn Cc: Bruce Evans , luoqi@watermarkgroup.com, current@FreeBSD.ORG, Jos.Backus@nl.origin-it.com Subject: Re: MFS still hosed In-reply-to: Your message of "Wed, 19 May 1999 09:32:18 +0200." <432.927099138@axl.noc.iafrica.com> Date: Sun, 23 May 1999 11:32:27 +0200 Message-ID: <8132.927451947@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can somebody please try if this fixes MFS ? Poul-Henning Index: ufs/mfs/mfs_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/mfs/mfs_vfsops.c,v retrieving revision 1.63 diff -u -r1.63 mfs_vfsops.c --- mfs_vfsops.c 1999/05/14 20:40:23 1.63 +++ mfs_vfsops.c 1999/05/23 09:22:20 @@ -62,6 +62,10 @@ MALLOC_DEFINE(M_MFSNODE, "MFS node", "MFS vnode private part"); +/* XXX: this is bogus, should be (NUMCDEV-1) or use dynamic allocation */ +#define CDEV_MAJOR 255 +#define BDEV_MAJOR 255 + #ifdef MFS_ROOT static caddr_t mfs_rootbase; /* address of mini-root in kernel virtual memory */ static u_long mfs_rootsize; /* size of mini-root in bytes */ @@ -462,8 +466,6 @@ mfs_init(vfsp) struct vfsconf *vfsp; { - dev_t dev = NODEV; - cdevsw_add(&dev, &mfs_cdevsw, NULL); - cdevsw_add_generic(255, major(dev), &mfs_cdevsw); + cdevsw_add_generic(BDEV_MAJOR, CDEV_MAJOR, &mfs_cdevsw); return (0); } -- 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 Sun May 23 2:58:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 08AAA14C42 for ; Sun, 23 May 1999 02:58:09 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id CAA89522; Sun, 23 May 1999 02:58:08 -0700 (PDT) (envelope-from obrien) Message-ID: <19990523025808.A89493@nuxi.com> Date: Sun, 23 May 1999 02:58:08 -0700 From: "David O'Brien" To: Steve Price , freebsd-current@FreeBSD.ORG Subject: Re: libg2c.a in -current Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Steve Price on Sat, May 22, 1999 at 05:13:20PM -0500 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anyone know why libf2c* was renamed to libg2c* in egcs? Cygnus has hacked (possibly considerably) Bell-Labs' libf2c. To the point a program written to the EGCS's FORTRAN lib wouldn't be linkable with libf2c. Thus they felt the need for a unique name. > Does egcs have a replacement for f2c? Yep, g77. :-) f2c was written to compile FORTRAN programs. It was quicker for the f2c authors to write f2c to output C code than ASM, *AND* it meant they didn't have to deal with code generation, nor optimization. However, there are many optimizations the code generator can do if it knows the input language was FORTRAN. Thus a native FORTRAN compiler (ie, g77) is preferred. f2c was never meant to be a FORTRAN to C translator in which you then maintained the resulting C. > Would anyone object if I installed the header file, g2c.h, along with > the library? Since you seem to believe it is useful, I'll install it. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 3: 0:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C400A150F7 for ; Sun, 23 May 1999 03:00:49 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id DAA89546; Sun, 23 May 1999 03:00:48 -0700 (PDT) (envelope-from obrien) Message-ID: <19990523030048.B89493@nuxi.com> Date: Sun, 23 May 1999 03:00:48 -0700 From: "David O'Brien" To: Steve Price , freebsd-current@FreeBSD.ORG Subject: Re: libg2c.a in -current Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Steve Price on Sat, May 22, 1999 at 05:13:20PM -0500 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Index: Makefile > =================================================================== > RCS file: /home/ncvs/src/gnu/lib/libg2c/Makefile,v .... > +beforeinstall: > + ${INSTALL} -C -o ${BINOWN} -g ${BINGRP} -m 444 ${.CURDIR}/g2c.h \ > + ${DESTDIR}/usr/include > + $ brucify Makefile Line 123: Continuation of rule should be indented 4 spaces, not 1 tab character. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 3:45:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 77F5815270; Sun, 23 May 1999 03:45:24 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id MAA25236; Sun, 23 May 1999 12:45:22 +0200 (CEST) (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 MAA08295; Sun, 23 May 1999 12:45:19 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Date: Sun, 23 May 1999 12:45:19 +0200 Message-ID: <8293.927456319.1@critter.freebsd.dk> From: Poul-Henning Kamp Subject: UFS parameter survey: HELP WANTED! MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message Subject: UFS parameter survey: HELP WANTED! From: Poul-Henning Kamp Date: Sun, 23 May 1999 12:45:19 +0200 Message-ID: <8293.927456319@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Bcc: Blind Distribution List: ; MIME-Version: 1.0 I recently made a 15GB filesystem and ended up with almost 500 cylinder groups. That is unlikely to be optimal. I talked to Kirk about the right parameters for UFS on modern disks some years back, and he said that no more than maybe a hundred cylinder groups made any sense. I think the fact that disks have gotten 25 times larger since the newfs paramters were last tweaked means that it is time to do so again. Unfortunately determining the parameters are not simple, so I would like to solicit help from as many as possible in determining if we should retune the newfs defaults. What I'm looking for is hard and soft data on the difference it makes for various sets of parameters, for various workloads and programs. So if you have time and facilities, lend me a hand. Basically, we can only sensibly compare data from the same hardware with the same workload, otherwise there are too many things to compare. Not all things can be measured precisely, but try to provide as much data as you can, and as good data as you can, ie: don't change controllers move partitions change BIOS settings without noting that you did so. The newfs parameters I would like to map out are: -a -b -c -e -f -i -m -t -u I'm generally interested in all impacts of this, but in particular if you can measure one or more of these specific parameters: read performance write performance create performance fsck time space wastage "other" I have no particular wishes for what program/application is used to excercise the system, but I would always prefer real-world over synthetic benchmarks. If somebody could measure news-server and web-server performance for instance it would be great. If anybody feels like making a structured benchmark script which just takes a device name as arg and runs some standardized tests that would be great too! Please report all results to using this form. Put the information instead of the "___", but leave the line number intact please. You don't need to return the lines starting with # I will post news and updates about this project on: http://phk.freebsd.dk/ufs If there is sufficient interest we will make a mailing list too. Thank you for your participation! Poul-Henning *BEGIN UFSTUNE FORM* # Your email address. This will be used only to catalogue and # request further details from you. It will not be published # or distributed. # Example: # 1 phk@freebsd.org 1 ___ # Identity of the system you used. This is just to keep all measurements # straight. It is used with your email as a unique index. This # should identify one particular combination of hardware, excluding # the disk you had the filesystems on. If you have the disk on # different controllers in the same system, that will count as two # systems. Use names/numbers/whatever helps you keep track of things. # Please use the same thing for all measurements made on the same # system. # Example: # 2 rover using NCR controller 2 ___ # Identity of the disk/device you had the filesystem on, please # cut&paste the <...> piece from /var/run/dmesg.boot: # Example: # 3 3 ___ # Describe the nature of the test in one-line form. # Example: # 4 Time to fsck filesystem with all four 3.2 CD's loaded 4 ___ # Describe the nature and conditions of the test in # sufficient detail that somebody else can repeat it. # Example: # 5 Filesystem is newfs'ed and mounted. The four CDs from the FreeBSD # 5 3.2 release were copied in using "find . -print | cpio -dump XXX" # 5 where XXX is mountpoint/cd[1234]. Filesystem unmounted and run # 5 /usr/bin/time -l fsck /dev/rsd0c 5 ___ # You must repeat the rest of the form for each experiment. # document the newfs commandline used. Include a -s option here. # Example: # 6 newfs -f 2048 -s 30720000 6 ___ # document any mount options, kernel features or softupdates. # Example: # 7 softupdates 7 ___ # note any other detailes pertaining to this experiment (multiline) # Example: # 8 BIOS set to 5 MHz/narrow 8 ___ # document the result of the experiment, for instance the output from # time(1) or similar (multiline) # Example: # 9 2.91 real 0.03 user 0.05 sys 9 ___ *END UFSTUNE FORM* -- 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! ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 5:43:44 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 5A6BD151F4 for ; Sun, 23 May 1999 05:43:32 -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.00 #1) id 10lXX6-0001AG-00; Sun, 23 May 1999 14:39:12 +0200 From: Sheldon Hearn To: Poul-Henning Kamp Cc: Bruce Evans , luoqi@watermarkgroup.com, current@FreeBSD.ORG, Jos.Backus@nl.origin-it.com Subject: Re: MFS still hosed In-reply-to: Your message of "Sun, 23 May 1999 11:32:27 +0200." <8132.927451947@critter.freebsd.dk> Date: Sun, 23 May 1999 14:39:11 +0200 Message-ID: <4478.927463151@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 May 1999 11:32:27 +0200, Poul-Henning Kamp wrote: > Can somebody please try if this fixes MFS ? Do you want your patch applied alongside Luoqi Chen's patch to kern_conf.c from last week? I've been able to mount_mfs without problems since then. Ciao, Sheldon/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 6:10:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (Postfix) with ESMTP id DC7D015304 for ; Sun, 23 May 1999 06:10:07 -0700 (PDT) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id RAA08381; Sun, 23 May 1999 17:00:59 +0400 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.3/8.9.1) with ESMTP id RAA01695; Sun, 23 May 1999 17:04:04 +0400 (MSD) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199905231304.RAA01695@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Peter Wemm Cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: calcru and upages In-reply-to: Your message of "Sun, 23 May 1999 11:37:40 +0800." <19990523033740.841F922@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 May 1999 17:04:04 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > Bruce Evans wrote: > > >calcru() access p_stats, which is in upages. Therefore, as I understand, > > >it should not be called on a swapped out process. Neither calcru() nor > > > > Does anyone object to moving everything except the stack from the upages > > to the proc table? This would certainly make my sleep better. However, IMO the real problem here is the hackish way the VM maintain upages. It is not so hard to make such incorrect accesses to u-area detected better. I used this: --- vm_glue.c Thu May 20 00:24:18 1999 +++ vm_glue.c Thu May 20 00:27:33 1999 @@ -317,6 +317,9 @@ faultin(p) setrunqueue(p); p->p_flag |= P_INMEM; + p->p_stats = &p->p_addr->u_stats; + if (p->p_sigacts == NULL) + p->p_sigacts = &p->p_addr->u_sigacts; /* undo the effect of setting SLOCK above */ --p->p_lock; @@ -516,6 +519,9 @@ swapout(p) (void) splhigh(); p->p_flag &= ~P_INMEM; p->p_flag |= P_SWAPPING; + p->p_stats = NULL; + if (p->p_sigacts == &p->p_addr->u_sigacts) + p->p_sigacts = NULL; if (p->p_stat == SRUN) remrq(p); (void) spl0(); Probably better idea would be pass MAP_NOFAULT in a non-currently-existent argument to kmem_alloc_pageable() in pmap_new_proc(). > Well, we have three things that are about the same size: > struct pcb u_pcb; 240 bytes > struct sigacts u_sigacts; 292 bytes > struct pstats u_stats; 248 bytes > > On the other hand: sizeof (struct proc) = 328 bytes. > > the pcb contains a heap of space for the FP state. It accounts for 176 of > the 240 bytes, leaving 64-odd bytes left for the pcb proper. The ldt > pointers need to move to proc scope for rfork()/clone(), and gc'ing a few > things that can get it as low as 40 - 48 bytes. pcb_savefpu has padding in > case a FPU emulator is used and is actually smaller than 176 bytes, and > could be changed depending on whether it's a real or emulated fpu. I guess, this is bit different on alpha ;-). > > IMHO, I'd move them to reference counted malloc'ed structs since sigacts > needs to be shared for clone/rforked processes. I think sigacts is already sometimes shared, and not stored in u-area in these cases. > I think there is also > benefit to having the sigacts at least malloced, one day we should be able > to extend the signals beyond the existing 32 set, at least for the 32 > extra RT signals. Isn't this an argument for keep them in upages? When the struct is larger, you want to swap it out stronger? > I personally would love to see this come out of the upages, it makes > tracking through a stack overflow even harder. We could put an unmapped > red-line page below the bottom stack page to ensure we get a double fault > on an overflow instead of mystery corruptions etc. Why not move 'struct user' on top of the upages, above the kernel stack? Sayed all that, I don't actually suggest to keep struct user. I almost hate it. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 6:13:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 201A515304 for ; Sun, 23 May 1999 06:13:41 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA26199; Sun, 23 May 1999 15:13:37 +0200 (CEST) (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 PAA08844; Sun, 23 May 1999 15:13:33 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Sheldon Hearn Cc: Bruce Evans , luoqi@watermarkgroup.com, current@FreeBSD.ORG, Jos.Backus@nl.origin-it.com Subject: Re: MFS still hosed In-reply-to: Your message of "Sun, 23 May 1999 14:39:11 +0200." <4478.927463151@axl.noc.iafrica.com> Date: Sun, 23 May 1999 15:13:33 +0200 Message-ID: <8842.927465213@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4478.927463151@axl.noc.iafrica.com>, Sheldon Hearn writes: > > >On Sun, 23 May 1999 11:32:27 +0200, Poul-Henning Kamp wrote: > >> Can somebody please try if this fixes MFS ? > >Do you want your patch applied alongside Luoqi Chen's patch to >kern_conf.c from last week? I've been able to mount_mfs without problems >since then. Yes. The problem here is to get MFS-rootfs to work. -- 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 Sun May 23 6:20: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from bsd1.gccs.com.au (router.gccs.com.au [203.17.152.1]) by hub.freebsd.org (Postfix) with ESMTP id 86CF8150E2 for ; Sun, 23 May 1999 06:19:53 -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 XAA90327 for ; Sun, 23 May 1999 23:19:51 +1000 (EST) Message-ID: <005e01bea51e$dc3dc470$0a9811cb@gccs.com.au> From: "Harry Starr" To: "current" Subject: MAKEDEV problems Date: Sun, 23 May 1999 23:19:16 +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 The -current MAKEDEV has a problem. The recent addition of the i4btel?? stuff has broken "sh MAKEDEV all" The section of the sh case for "i4teld*)" should be BEFORE the case for "i4tel*)". (match the longest prefix first!) This problem is causing the generation of i4teld? to FAIL! and thus the 'all' Harry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 6:28:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from bsd1.gccs.com.au (router.gccs.com.au [203.17.152.1]) by hub.freebsd.org (Postfix) with ESMTP id 3B9BB14D18 for ; Sun, 23 May 1999 06:28:47 -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 XAA90343 for ; Sun, 23 May 1999 23:28:46 +1000 (EST) Message-ID: <006901bea520$1b41dbb0$0a9811cb@gccs.com.au> From: "Harry Starr" To: "current" Subject: disk slices and MAKEDEV confusion Date: Sun, 23 May 1999 23:28:12 +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 I am confused! The /boot/loader is "announcing" that it wants the root device to be "da0s1a". It appears that the "normal" fstab entries want "sliced" versions as well, eg. # Device Mountpoint FStype Options Dump Pass# /dev/da0s1b none swap sw 0 0 /dev/da0s1a / ufs rw 1 1 SO! Why does "sh MAKEDEV all" NOT make the partition entries for the slice(s) ??? ie, "sh MAKEDEV all" only makes the "compatability" slice entries -- da0s1, da0s2 etc. It requires a "sh MAKEDEV da0s1a" to get the slice/partition entries. I checked on the "standard" entries in "disc2" of the "release" cds (/R/cdrom/disc2/dev) and the partition entries are not there either for the "da" and "wd" entries. Have I totally lost the plot on device naming.....??? Harry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 6:47:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 237DC15253 for ; Sun, 23 May 1999 06:47:37 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id IAA04259; Sun, 23 May 1999 08:47:36 -0500 (CDT) Date: Sun, 23 May 1999 08:47:36 -0500 (CDT) From: Steve Price To: obrien@NUXI.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: libg2c.a in -current In-Reply-To: <19990523030048.B89493@nuxi.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, 23 May 1999, David O'Brien wrote: # > Index: Makefile # > =================================================================== # > RCS file: /home/ncvs/src/gnu/lib/libg2c/Makefile,v # .... # > +beforeinstall: # > + ${INSTALL} -C -o ${BINOWN} -g ${BINGRP} -m 444 ${.CURDIR}/g2c.h \ # > + ${DESTDIR}/usr/include # > + # # # $ brucify Makefile # Line 123: Continuation of rule should be indented 4 spaces, not 1 tab # character. I pilfered the format from src/lib/libalias/Makefile, so it fails brucify(1) there as well. :) -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 7: 3:26 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 6281F152EF for ; Sun, 23 May 1999 07:03:23 -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 AAA28416; Mon, 24 May 1999 00:03:21 +1000 Date: Mon, 24 May 1999 00:03:21 +1000 From: Bruce Evans Message-Id: <199905231403.AAA28416@godzilla.zeta.org.au> To: obrien@NUXI.com, sprice@hiwaay.net Subject: Re: libg2c.a in -current Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ># $ brucify Makefile ># Line 123: Continuation of rule should be indented 4 spaces, not 1 tab ># character. > >I pilfered the format from src/lib/libalias/Makefile, so it fails >brucify(1) there as well. :) I don't know where all the bad examples in src/lib/*/Makefile came from. In Lite2 there are only 3 examples of beforeinstall targets, all of which have rules with continuation lines, all of which are indented 4 spaces. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 7:16:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 3637A1530D for ; Sun, 23 May 1999 07:16:44 -0700 (PDT) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id PAA27860; Sun, 23 May 1999 15:16:43 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id PAA04398; Sun, 23 May 1999 15:16:11 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199905231416.PAA04398@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: obrien@NUXI.com, sprice@hiwaay.net, freebsd-current@FreeBSD.ORG Subject: Re: libg2c.a in -current In-reply-to: Your message of "Mon, 24 May 1999 00:03:21 +1000." <199905231403.AAA28416@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 May 1999 15:16:11 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ># $ brucify Makefile > ># Line 123: Continuation of rule should be indented 4 spaces, not 1 tab > ># character. > > > >I pilfered the format from src/lib/libalias/Makefile, so it fails > >brucify(1) there as well. :) > > I don't know where all the bad examples in src/lib/*/Makefile came from. > In Lite2 there are only 3 examples of beforeinstall targets, all of which > have rules with continuation lines, all of which are indented 4 spaces. I can't pass the blame for libalias/Makefile.... :-} > Bruce -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 10:56: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from sundance.KKS.net (sundance.KKS.net [212.62.128.10]) by hub.freebsd.org (Postfix) with ESMTP id E281A14F18 for ; Sun, 23 May 1999 10:55:58 -0700 (PDT) (envelope-from andy@kksonline.com) Received: from notebook (cm-33.rot.KKS.net [212.62.129.33]) by sundance.KKS.net (8.8.8/8.8.8/HPatch) with SMTP id TAA29929 for ; Sun, 23 May 1999 19:55:44 +0200 Message-Id: <199905231755.TAA29929@sundance.KKS.net> X-Sender: arozman@pop3.kks.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sun, 23 May 1999 19:50:32 +0200 To: freebsd-current@FreeBSD.ORG From: Aleksander Rozman - Andy Subject: ethernet card problems In-Reply-To: <19990523174734.3219C14F45@hub.freebsd.org> 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 am new to to list and to BSD-current. I cvsup'ed whole thing and installed it over weekend, but I encountered problem. I have one machine at home with two ethernet cards of same type (NE2000 compatible). One is used for connection to cable modem and other to my private network. Problem is that in kernel they aren't both added. I added them in config file (ed0 and ed1), but on startup the second card isn't started. On previous kernel (v3.1) everything worked ok, but now it doesn't. Is this change in kernel or did I make mistake in my config file. Please help me, cause running 3.1 kernel on 4.0 all other files, doesn't work very good. Andy ************************************************************************** * Aleksander Rozman - Andy * Member of: E2:EA, E2F, SAABer, Trekkie, * * andy@mail.kks.net * X-Phile, Heller's angel, True's screamer, * * andy@atechnet.ml.org * True's Trooper, Questie, Legacy, PO5, * * Maribor, Slovenia (Europe) * Profiler, Buffy (Slayerete), Pretender * * ICQ-UIC: 4911125 ********************************************* * PGP key available * http://www.atechnet.ml.org/~andy/ * ************************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 17:14: 4 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 BD63014E44 for ; Sun, 23 May 1999 17:13:58 -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 5311763; Mon, 24 May 1999 08:13:57 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: Bruce Evans , dima@tejblum.dnttm.rssi.ru, freebsd-current@FreeBSD.ORG Subject: Re: calcru and upages In-reply-to: Your message of "Sun, 23 May 1999 08:57:01 +0200." <7757.927442621@critter.freebsd.dk> Date: Mon, 24 May 1999 08:13:57 +0800 From: Peter Wemm Message-Id: <19990524001357.5311763@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message <199905230245.MAA13333@godzilla.zeta.org.au>, Bruce Evans writes: > >>calcru() access p_stats, which is in upages. Therefore, as I understand, > >>it should not be called on a swapped out process. Neither calcru() nor > > > >Does anyone object to moving everything except the stack from the upages > >to the proc table? > > not me. I'd also like to implement a proper clone(2) ala Linux. We have most of the infrastructure in place already, using that and comparing with NetBSD's take on the subject should be fairly useful in the end. The main difference between clone(2) and rfork(2) is that clone() takes a stack argument and is more specific about certain sharing semantics. At present these are emulated via flags added into rfork's visibility, I think it would be cleaner to just use a proper syscall interface onto fork1() rather than bend rfork(2) even more. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 18:35:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from i4got.pechter.dyndns.org (bg-tc-ppp508.monmouth.com [209.191.63.68]) by hub.freebsd.org (Postfix) with ESMTP id 8AFF014E21 for ; Sun, 23 May 1999 18:35:11 -0700 (PDT) (envelope-from pechter@i4got.pechter.dyndns.org) Received: (from pechter@localhost) by i4got.pechter.dyndns.org (8.9.3/8.9.3) id VAA01878 for freebsd-current@freebsd.org; Sun, 23 May 1999 21:33:14 -0400 (EDT) (envelope-from pechter) From: Bill Pechter Message-Id: <199905240133.VAA01878@i4got.pechter.dyndns.org> Subject: ed0 not recognized (even tried it as ed1) To: freebsd-current@freebsd.org Date: Sun, 23 May 1999 21:33:13 -0400 (EDT) Reply-To: bpechter@shell.monmouth.com X-Phone-Number: 908-389-3592 X-OS-Type: FreeBSD 3.0-Stable 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 Following my latest rebuild (make world on Friday, make of kernel on Friday) -- I can no longer find my ed0 (WD 8216) network card. dmesg.yesterday:ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 dmesg.yesterday:ed0: address 00:00:c0:bb:a8:b2, type SMC8216/SMC8216C (16 bit) dmesg.yesterday:ed0: interrupting at irq 10 I see no probe at all for the device. Any suggestions? The ed0 line is the same as it was before: device ed0 at isa? port 0x260 irq 9 iomem 0xd8000 I did fix the atkbdc0 lines... after the keyboard didn't respond. controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 Have I missed something in the last few days? Bill --- bpechter@shell.monmouth.com|pechter@pechter.dyndns.org Three things never anger: First, the one who runs your DEC, The one who does Field Service and the one who signs your check. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 19:22:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 07CD914D5A for ; Sun, 23 May 1999 19:22:44 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id WAA00560 for ; Sun, 23 May 1999 22:22:43 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <199905240222.WAA00560@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@freebsd.org From: "Louis A. Mamakos" Subject: panic() in devfs_makelink() with recent -current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 May 1999 22:22:43 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently tried building a new kernel after quite a bit, and I get a panic while the system's booting in devfs_makelink, apparently being called from fd_attach(). Is DEVFS and the new-bus code hopelessly incompatable, and should I just unconfigure DEVFS? Or is this something that I can dig into a bit more and find a relatively simple fix? I copied down some of what the trace command spewed in ddb, and it appears that the first argument to devfs_makelink is 0, which is sorta weird.. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 20: 7:56 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 AAFB215256 for ; Sun, 23 May 1999 20:07:45 -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 VAA78438; Sun, 23 May 1999 21:06:26 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA15929; Sun, 23 May 1999 21:06:46 -0600 (MDT) Message-Id: <199905240306.VAA15929@harmony.village.org> To: bpechter@shell.monmouth.com Subject: Re: ed0 not recognized (even tried it as ed1) Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 23 May 1999 21:33:13 EDT." <199905240133.VAA01878@i4got.pechter.dyndns.org> References: <199905240133.VAA01878@i4got.pechter.dyndns.org> Date: Sun, 23 May 1999 21:06:46 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905240133.VAA01878@i4got.pechter.dyndns.org> Bill Pechter writes: : dmesg.yesterday:ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 : The ed0 line is the same as it was before: : device ed0 at isa? port 0x260 irq 9 iomem 0xd8000 I find that extremely hard to believe... Different IRQ and different port is what it appears to me... Maybe that's why things didn't work. : I did fix the atkbdc0 lines... after the keyboard didn't respond. : controller atkbdc0 at isa? port IO_KBD : device atkbd0 at atkbdc? irq 1 # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts is what I have in my config file. Maybe you didn't run config(8)? You can tell if you didn't because there is a copy of the config file in compile/BLAH/config.c. That was my problem with the keyboard (I had changed it in my config file, but had neglected to run config on the correct config file, hence I got all confused for a short period of time). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 22: 4: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id 66D611509A for ; Sun, 23 May 1999 22:03:57 -0700 (PDT) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id BAA00452; Mon, 24 May 1999 01:27:07 -0400 (EDT) (envelope-from dervish) Date: Mon, 24 May 1999 01:27:07 -0400 From: Natty Rebel To: "Louis A. Mamakos" Cc: freebsd-current@freebsd.org Subject: Re: panic() in devfs_makelink() with recent -current Message-ID: <19990524012627.A405@ikhala.tcimet.net> References: <199905240222.WAA00560@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199905240222.WAA00560@whizzo.transsys.com>; from Louis A. Mamakos on Sun, May 23, 1999 at 10:22:43PM -0400 X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 2C CE A5 D7 FA 4D D5 FD 9A CC 2B 23 04 46 48 F8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Louis A. Mamakos (louie@TransSys.COM): > > I recently tried building a new kernel after quite a bit, and I get a > panic while the system's booting in devfs_makelink, apparently being > called from fd_attach(). > > Is DEVFS and the new-bus code hopelessly incompatable, and should I just > unconfigure DEVFS? Or is this something that I can dig into a bit more > and find a relatively simple fix? > > I copied down some of what the trace command spewed in ddb, and it appears > that the first argument to devfs_makelink is 0, which is sorta weird.. Can I say me too here. My panics were happening in the swapper process. After reading your message I commented out the DEVFS option and voila! the new kernel booted without a hitch. I'm up for doing some kernel digging ... > > louie > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message #;^) -- natty rebel harder than the rest ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 22:50:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from deep-thought.demos.su (deep-thought.demos.su [194.87.1.76]) by hub.freebsd.org (Postfix) with ESMTP id 1CE3815206 for ; Sun, 23 May 1999 22:50:06 -0700 (PDT) (envelope-from ache@deep-thought.demos.su) Received: (from ache@localhost) by deep-thought.demos.su (8.9.3/8.9.3) id JAA00336 for current@freebsd.org; Mon, 24 May 1999 09:49:57 +0400 (MSD) (envelope-from ache) Date: Mon, 24 May 1999 09:49:56 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: isa_compat error diagnostic Message-ID: <19990524094956.A325@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got this with recent -current. Something need to be fixed since ed0 line is the same as in LINT (iomem 0xd8000) excepting irq is different. ... ed0 at port 0x300-0x31f iomem 0 irq 10 on isa0 isa_compat: didn't get memory for ed ed0: address 00:c0:6c:62:47:20, type NE2000 (16 bit) ... -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 23 23:24:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 96AE514D89 for ; Sun, 23 May 1999 23:24:35 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id IAA02708; Mon, 24 May 1999 08:24:34 +0200 (CEST) (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 IAA11044; Mon, 24 May 1999 08:24:30 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Louis A. Mamakos" Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic() in devfs_makelink() with recent -current In-reply-to: Your message of "Sun, 23 May 1999 22:22:43 EDT." <199905240222.WAA00560@whizzo.transsys.com> Date: Mon, 24 May 1999 08:24:30 +0200 Message-ID: <11042.927527070@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905240222.WAA00560@whizzo.transsys.com>, "Louis A. Mamakos" writ es: > >I recently tried building a new kernel after quite a bit, and I get a >panic while the system's booting in devfs_makelink, apparently being >called from fd_attach(). > >Is DEVFS and the new-bus code hopelessly incompatable, and should I just >unconfigure DEVFS? Or is this something that I can dig into a bit more >and find a relatively simple fix? DEVFS is probably not compatible with the dev_t changes I introduced. -- 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 Mon May 24 1:28:15 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 C700B14C97 for ; Mon, 24 May 1999 01:28:09 -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 JAA89465; Mon, 24 May 1999 09:28:16 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 24 May 1999 09:28:15 +0100 (BST) From: Doug Rabson To: bpechter@shell.monmouth.com Cc: freebsd-current@freebsd.org Subject: Re: ed0 not recognized (even tried it as ed1) In-Reply-To: <199905240133.VAA01878@i4got.pechter.dyndns.org> 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, 23 May 1999, Bill Pechter wrote: > Following my latest rebuild (make world on Friday, make of kernel > on Friday) -- I can no longer find my ed0 (WD 8216) network card. > > dmesg.yesterday:ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 > dmesg.yesterday:ed0: address 00:00:c0:bb:a8:b2, type SMC8216/SMC8216C (16 bit) > dmesg.yesterday:ed0: interrupting at irq 10 > > I see no probe at all for the device. I think I must have broken it. I'm trying to figure out what happened right now. -- 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 Mon May 24 2:42:39 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 9FC141517F for ; Mon, 24 May 1999 02:42:35 -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 KAA96879; Mon, 24 May 1999 10:42:44 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 24 May 1999 10:42:44 +0100 (BST) From: Doug Rabson To: bpechter@shell.monmouth.com Cc: freebsd-current@freebsd.org Subject: Re: ed0 not recognized (even tried it as ed1) 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, 24 May 1999, Doug Rabson wrote: > On Sun, 23 May 1999, Bill Pechter wrote: > > > Following my latest rebuild (make world on Friday, make of kernel > > on Friday) -- I can no longer find my ed0 (WD 8216) network card. > > > > dmesg.yesterday:ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 > > dmesg.yesterday:ed0: address 00:00:c0:bb:a8:b2, type SMC8216/SMC8216C (16 bit) > > dmesg.yesterday:ed0: interrupting at irq 10 > > > > I see no probe at all for the device. > > I think I must have broken it. I'm trying to figure out what happened > right now. Please try this patch: Index: isa_compat.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.c,v retrieving revision 1.10 diff -u -r1.10 isa_compat.c --- isa_compat.c 1999/05/22 15:18:12 1.10 +++ isa_compat.c 1999/05/24 09:40:04 @@ -81,7 +81,8 @@ res->ports = 0; if (ISA_GET_RESOURCE(parent, dev, SYS_RES_MEMORY, 0, - &start, &count) == 0) { + &start, &count) == 0 + && start != 0) { rid = 0; res->memory = bus_alloc_resource(dev, SYS_RES_MEMORY, &rid, 0ul, ~0ul, 1, -- 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 Mon May 24 3:53: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id A517014C02 for ; Mon, 24 May 1999 03:52:52 -0700 (PDT) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id MAA19648; Mon, 24 May 1999 12:52:19 +0200 (MET DST) Received: (from nsouch@localhost) by teaser.fr (8.9.3/8.9.1) id MAA02056; Mon, 24 May 1999 12:46:29 +0200 (CEST) (envelope-from nsouch) Message-ID: <19990524124629.55958@breizh.teaser.fr> Date: Mon, 24 May 1999 12:46:29 +0200 From: Nicolas Souchu To: Mike Smith Cc: John Polstra , peter@netplex.com.au, current@FreeBSD.ORG Subject: Re: Heads up! config(8) changes.. References: <199904300521.WAA03402@vashon.polstra.com> <199904300526.WAA01120@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199904300526.WAA01120@dingo.cdrom.com>; from Mike Smith on Thu, Apr 29, 1999 at 10:26:48PM -0700 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 29, 1999 at 10:26:48PM -0700, Mike Smith wrote: > >> In article <19990424190901.D3A791F58@spinner.netplex.com.au>, >> Peter Wemm wrote: >> > This shouldn't cause much in the way of trouble, but it will complain >> > about old lint in your config files. That includes 'net/tty/bio/cam' >> > mask indicators, and 'vector xxxintr' as well as some of the wierder >> > workarounds for the poor 'options' parsing. >> > >> > So: things like: >> > device sio1 at isa? tty port "IO_COM2" tty irq 3 >> > become: >> > device sio1 at isa? port IO_COM2 irq3 >> >> What do you do about the "ppc" device? Formerly, it needed to be "net >> irq ..." if the "plip" device was going to be used, but "tty irq ..." >> otherwise. Which one did you pick? > >It needs to flip between one or both, but I can't raise Nicolas lately, >so I'm starting to fear that we're going to need a new maintainer. >That bites, given how well things were going. Someone who would help me driving ppbus, yes. I didn't have enough time last months. So, what are the next issues: - porting ppbus to newbus (especially irq managment) - fix ppc probe bugs with recent mainboards - sync -current and -stable - test plip in depth I think there is more to do with making ppbus more and more stable than bringing new capabilities to it yet. > >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Mon May 24 5:57:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (unknown [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 5393D14DFB for ; Mon, 24 May 1999 05:57:26 -0700 (PDT) (envelope-from dispatch@blackhelicopters.org) Received: (from dispatch@localhost) by blackhelicopters.org (8.8.8/8.8.8) id IAA25174; Mon, 24 May 1999 08:57:14 -0400 (EDT) (envelope-from dispatch) From: Dispatcher Message-Id: <199905241257.IAA25174@blackhelicopters.org> Subject: Re: ethernet card problems In-Reply-To: <199905231755.TAA29929@sundance.KKS.net> from Aleksander Rozman - Andy at "May 23, 1999 7:50:32 pm" To: andy@kksonline.com (Aleksander Rozman - Andy) Date: Mon, 24 May 1999 08:57:14 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Honestly, FreeBSD-current is not what you want if you're having this sort of problem. -current is for people who want to read C code, debug device drivers, and who are perfectly willing to have their system, hardware, and or software destroyed by bugs. Since the machine in question connects your private network to the public one, it is a very bad choice for -current. You have to assume that -current will be unusable for days on end. I strongly suggest you downgrade to 3-stable. Failing that, ask this over on -questions. Regards, Michael > Hi ! > > I am new to to list and to BSD-current. I cvsup'ed whole thing and > installed it over weekend, but I encountered problem. I have one machine at > home with two ethernet cards of same type (NE2000 compatible). One is used > for connection to cable modem and other to my private network. Problem is > that in kernel they aren't both added. I added them in config file (ed0 and > ed1), but on startup the second card isn't started. On previous kernel > (v3.1) everything worked ok, but now it doesn't. Is this change in kernel > or did I make mistake in my config file. Please help me, cause running 3.1 > kernel on 4.0 all other files, doesn't work very good. > > Andy > > ************************************************************************** > * Aleksander Rozman - Andy * Member of: E2:EA, E2F, SAABer, Trekkie, * > * andy@mail.kks.net * X-Phile, Heller's angel, True's screamer, * > * andy@atechnet.ml.org * True's Trooper, Questie, Legacy, PO5, * > * Maribor, Slovenia (Europe) * Profiler, Buffy (Slayerete), Pretender * > * ICQ-UIC: 4911125 ********************************************* > * PGP key available * http://www.atechnet.ml.org/~andy/ * > ************************************************************************** > > > > 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 Mon May 24 6:56:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 627A51537E for ; Mon, 24 May 1999 06:56:53 -0700 (PDT) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id IAA03078; Mon, 24 May 1999 08:52:30 -0500 (CDT) (envelope-from dick) Date: Mon, 24 May 1999 08:52:30 -0500 From: "Richard Seaman, Jr." To: Peter Wemm Cc: Poul-Henning Kamp , Bruce Evans , dima@tejblum.dnttm.rssi.ru, freebsd-current@FreeBSD.ORG Subject: Re: calcru and upages Message-ID: <19990524085229.A384@tar.com> References: <7757.927442621@critter.freebsd.dk> <19990524001357.5311763@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990524001357.5311763@overcee.netplex.com.au>; from Peter Wemm on Mon, May 24, 1999 at 08:13:57AM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 24, 1999 at 08:13:57AM +0800, Peter Wemm wrote: > I'd also like to implement a proper clone(2) ala Linux. We have most of > the infrastructure in place already, using that and comparing with NetBSD's > take on the subject should be fairly useful in the end. The main > difference between clone(2) and rfork(2) is that clone() takes a stack > argument and is more specific about certain sharing semantics. At present > these are emulated via flags added into rfork's visibility, I think it > would be cleaner to just use a proper syscall interface onto fork1() rather > than bend rfork(2) even more. The function linux_clone() in linux_misc.c could be a starting place. Making that (or a modified version of it) a FreeBSD syscall would seem to do the trick. It calls rfork() instead of fork1(), but then rfork is implemented as a call to fork1, so the only difference is the interface. Probably the only real issue you have is whether the flags you pass in are FreeBSD rfork flags, or Linux flags that get translated into their equivalent FreeBSD flags internally before you call fork1(). The linux_clone() function obviously needs to take Linux flags. But, if your goal is to have a better interface than rfork(), you don't need to limit yourself to mimicing the linux clone() syscall. However, it seems to me that there are really only three reasons to have a "clone" call. One is for linux emulation, which we already have. Another is to facilitate porting linux apps. But, linux apps normally call the glibc version of clone, which wraps the linux clone(2) syscall. Its easy enough to create a userland (eg. libc) clone() call that wraps rfork (see the Linux threads port for an example implementation). The third is to create a better syscall interface for threading/ process creation than we have with rfork. I think that if FreeBSD is going to have really good "many to many" kernel/user threads there will probably need to be one or a few new syscalls for thread creation/thread management. IMO the best choice would be to think through what these calls should look like. I haven't had time to really work this through in my own mind, though. I suspect that the linux clone(2) syscall is not the best choice for this either. If you're going to work on this, and if you think it would help you, I'd try to find some time to jot down some of my (only partly formed) thoughts on what FreeBSD thread related syscalls might be helpful. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 24 9:21:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles504.castles.com [208.214.165.68]) by hub.freebsd.org (Postfix) with ESMTP id 963EB1515D for ; Mon, 24 May 1999 09:21:12 -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 JAA22046; Mon, 24 May 1999 09:18:59 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905241618.JAA22046@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Harry Starr" Cc: "current" Subject: Re: disk slices and MAKEDEV confusion In-reply-to: Your message of "Sun, 23 May 1999 23:28:12 +1000." <006901bea520$1b41dbb0$0a9811cb@gccs.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 May 1999 09:18:53 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am confused! > > The /boot/loader is "announcing" that it wants the root device to be > "da0s1a". > > It appears that the "normal" fstab entries want "sliced" versions as well, > eg. > # Device Mountpoint FStype Options Dump > Pass# > /dev/da0s1b none swap sw 0 0 > /dev/da0s1a / ufs rw 1 1 > > SO! Why does "sh MAKEDEV all" NOT make the partition entries for the > slice(s) ??? > > ie, "sh MAKEDEV all" only makes the "compatability" slice entries -- da0s1, > da0s2 etc. da0s1 is not a "compatibility slice" entry. That would be da0a, etc. The problem is that if you made all of the nodes for all of the supported slices, /dev would be incredibly bloated. There are 8 potential nodes per slice, and 20 potential slices per disk, plus the compatability slice, so that's 168 node pairs (raw and buffered) _per_disk_. -- \\ 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 Mon May 24 9:49:12 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 EF46A15401 for ; Mon, 24 May 1999 09:49:06 -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 MAA07444; Mon, 24 May 1999 12:49:05 -0400 (EDT) (envelope-from wollman) Date: Mon, 24 May 1999 12:49:05 -0400 (EDT) From: Garrett Wollman Message-Id: <199905241649.MAA07444@khavrinen.lcs.mit.edu> To: current@freebsd.org Subject: Effect of compiler options on performance Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have recently done a series of tests using the HINT benchmark () to see whether various compiler options have any useful effect under EGCS. Unsurprisingly, the only option which has any effect at all on this benchmark is `-ffast-math'. See a graph at . -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 24 11:35:50 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 A202414D7F for ; Mon, 24 May 1999 11:35:48 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA02016; Mon, 24 May 1999 11:35:32 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 24 May 1999 11:35:32 -0700 (PDT) From: Doug White To: Mike Smith Cc: Harry Starr , current Subject: Re: disk slices and MAKEDEV confusion In-Reply-To: <199905241618.JAA22046@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 Mon, 24 May 1999, Mike Smith wrote: > > I am confused! > > > > The /boot/loader is "announcing" that it wants the root device to be > > "da0s1a". > > > > It appears that the "normal" fstab entries want "sliced" versions as well, > > eg. > > # Device Mountpoint FStype Options Dump > > Pass# > > /dev/da0s1b none swap sw 0 0 > > /dev/da0s1a / ufs rw 1 1 > > > > SO! Why does "sh MAKEDEV all" NOT make the partition entries for the > > slice(s) ??? > > > > ie, "sh MAKEDEV all" only makes the "compatability" slice entries -- da0s1, > > da0s2 etc. > > da0s1 is not a "compatibility slice" entry. That would be da0a, etc. > > The problem is that if you made all of the nodes for all of the > supported slices, /dev would be incredibly bloated. There are 8 > potential nodes per slice, and 20 potential slices per disk, plus the > compatability slice, so that's 168 node pairs (raw and buffered) > _per_disk_. Yes, but you're going to make them manually anyway, so why not make 'MAKEDEV all' DTRT and not blindly hose people? I'll take bloat if it keeps people from asking -questions. 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 May 24 12: 0:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from cepheus.azstarnet.com (cepheus.azstarnet.com [169.197.56.195]) by hub.freebsd.org (Postfix) with ESMTP id 748CD153ED; Mon, 24 May 1999 12:00:46 -0700 (PDT) (envelope-from nje@azstarnet.com) Received: from black-hole (black-hole.azstarnet.com [169.197.53.211]) by cepheus.azstarnet.com (8.9.3/8.9.3) with SMTP id LAA18322; Mon, 24 May 1999 11:55:48 -0700 (MST) X-Sent-via: StarNet http://www.azstarnet.com/ Date: Mon, 24 May 1999 12:00:45 -0700 (MST) From: "Nicholas J. Esborn" X-Sender: nje@black-hole To: current@freebsd.org, stable@freebsd.org Subject: natd as a 'routing daemon' 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 a thought... Might it not be logical to put natd in the 'routing daemons' section of the boot process? That would start it before things like quota checking, which can take a lot of time and prevent a combination worgroup server/NAT box from providing network access, even when it could be with no consequence. Also, it does seem rather like a form of routing. Nicholas Esborn | www.azstarnet.com | StarNet (520) 618-RTFM | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 24 13:19:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.scl.ameslab.gov (mailhub.scl.ameslab.gov [147.155.137.127]) by hub.freebsd.org (Postfix) with ESMTP id 8FD461517C for ; Mon, 24 May 1999 13:19:25 -0700 (PDT) (envelope-from ghelmer@scl.ameslab.gov) Received: from demios.ether.scl.ameslab.gov ([147.155.137.54]) by mailhub.scl.ameslab.gov with esmtp (Exim 1.90 #1) for current@freebsd.org id 10m1Cq-0004a8-00; Mon, 24 May 1999 15:20:16 -0500 Date: Mon, 24 May 1999 15:19:24 -0500 From: Guy Helmer To: current@freebsd.org Subject: Mounting CD-ROM as root 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 been trying to mount a CD-ROM as root on FreeBSD so as to have a self-contained demo of a project that I could run anywhere. However, I found that the "-C" option was apparently being ignored by the new boot loader. The following patch fixed the problem: --- sys/boot/i386/libi386/bootinfo.c.ORIG Mon Mar 22 10:13:36 1999 +++ sys/boot/i386/libi386/bootinfo.c Mon May 24 14:32:01 1999 @@ -79,6 +79,9 @@ case 'c': howto |= RB_CONFIG; break; + case 'C': + howto |= RB_CDROM; + break; case 'd': howto |= RB_KDB; break; Is this worthy of a PR? Guy Guy Helmer, Ph.D. Candidate, Iowa State University Dept. of Computer Science Research Assistant, Ames Laboratory --- ghelmer@scl.ameslab.gov Research Assistant, Dept. of Computer Science --- ghelmer@cs.iastate.edu http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 24 13:21:55 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 3FADE1517C for ; Mon, 24 May 1999 13:21:41 -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 QAA15050 for ; Mon, 24 May 1999 16:21:40 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA89498; Mon, 24 May 1999 16:21:38 -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: Mon, 24 May 1999 16:21:38 -0400 (EDT) To: freebsd-current@freebsd.org Subject: process getting stuck in objtrm at exit X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14153.43614.342209.262970@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On recent -currents, one of our users has managed to wedge a job in objtrm when its exiting. Anybody know what's causing this? I've appended a stack trace of the offending process, as well as a printout of the offending object. The machine seems otherwise healthy. I don't really understand what the app in question is doing, so its hard for me to come up w/a concise test case. ------------------------------------------------------------------------------ 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 <3:40pm>waffle/gallatin:IDESERVER#ps axl | egrep objtrm\|UID UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 1660 22207 4370 122 -18 0 1220 0 objtrm DE+ p1 0:00.00 (step) <3:35pm>waffle/gallatin:IDESERVER#gdb -k kernel.debug /dev/mem <....> (kgdb) proc pidhashtbl[22207 & pidhash]->lh_first (kgdb) bt #0 mi_switch () at ../../kern/kern_synch.c:827 #1 0xc0152cd9 in tsleep (ident=0xca1e79f8, priority=4, wmesg=0xc024bbca "objtrm", timo=0) at ../../kern/kern_synch.c:443 #2 0xc01f6249 in vm_object_terminate (object=0xca1e79f8) at ../../vm/vm_object.h:235 #3 0xc01f61f9 in vm_object_deallocate (object=0xca1e79f8) at ../../vm/vm_object.c:384 #4 0xc01f3ae7 in vm_map_entry_delete (map=0xca1c0380, entry=0xca2b65f0) at ../../vm/vm_map.c:1887 #5 0xc01f3ca5 in vm_map_delete (map=0xca1c0380, start=0, end=3217022976) at ../../vm/vm_map.c:1990 #6 0xc01f3d29 in vm_map_remove (map=0xca1c0380, start=0, end=3217022976) at ../../vm/vm_map.c:2015 #7 0xc014a615 in exit1 (p=0xca2465a0, rv=0) at ../../kern/kern_exit.c:223 #8 0xc014a434 in exit1 (p=0xca2465a0, rv=-904133760) at ../../kern/kern_exit.c:106 #9 0xc0210dd6 in syscall (frame={tf_fs = 135004207, tf_es = 1209466927, tf_ds = -1078001617, tf_edi = 0, tf_esi = -1, tf_ebp = -1077947172, tf_isp = -903335964, tf_ebx = 1209464980, tf_edx = 0, tf_ecx = 0, tf_eax = 1, tf_trapno = 7, tf_err = 2, tf_eip = 1209204908, tf_cs = 31, tf_eflags = 582, tf_esp = -1077947196, tf_ss = 47}) at ../../i386/i386/trap.c:1069 #10 0xc0206aa0 in Xint0x80_syscall () rror reading /proc/22207/mem (kgdb) frame 2 #2 0xc01f6249 in vm_object_terminate (object=0xca1e79f8) at ../../vm/vm_object.h:235 235 tsleep(object, PVM, waitid, 0); (kgdb) p object $4 = 0xca1e79f8 (kgdb) p *object $5 = { object_list = { tqe_next = 0xca234244, tqe_prev = 0xca2ee488 }, shadow_head = { tqh_first = 0x0, tqh_last = 0xca1e7a00 }, shadow_list = { tqe_next = 0x0, tqe_prev = 0xca29c24c }, memq = { tqh_first = 0xc04ff370, tqh_last = 0xc04e65fc }, generation = 26962387, type = OBJT_SWAP, size = 165, ref_count = 0, shadow_count = 0, pg_color = 60, hash_rand = -71709939, flags = 8652, paging_in_progress = 1, behavior = 0, resident_page_count = 51, cache_count = 0, wire_count = 0, backing_object = 0x0, backing_object_offset = 0, last_read = 63, pager_object_list = { tqe_next = 0xca234244, tqe_prev = 0xca175970 }, handle = 0x0, un_pager = { vnp = { vnp_size = 5 }, devp = { devp_pglist = { tqh_first = 0x5, tqh_last = 0x0 } }, swp = { swp_bcount = 5 } } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 24 16: 8:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from po0.wam.umd.edu (po0.wam.umd.edu [128.8.10.162]) by hub.freebsd.org (Postfix) with ESMTP id D633B14E82; Mon, 24 May 1999 16:08:18 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po0.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA25894; Mon, 24 May 1999 19:08:16 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id TAA23533; Mon, 24 May 1999 19:08:15 -0400 (EDT) Received: from localhost by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id TAA23529; Mon, 24 May 1999 19:08:15 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Mon, 24 May 1999 19:08:15 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-questions@freebsd.org Cc: freebsd-current@freebsd.org Subject: Vortex sound support in FreeBSD 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 just wondering if anyone has gotten a soundcard based on the Vortex chip to work under FreeBSD. I know that OSS (www.opensound.com) supports it, but I don't want to use OSS because of the problems with it. If nobody has gotten that card to work, then can someone point me in the right direction to getting specs for the card and any how-to type advice on writing the driver myself for FreeBSD. I'd be willing to donate the driver to the project if I get it working well. Thanks. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 24 18:43:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id 7663514E47 for ; Mon, 24 May 1999 18:43:24 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id VAA23786; Mon, 24 May 1999 21:31:57 -0400 Date: Mon, 24 May 1999 21:31:57 -0400 (EDT) From: Zhihui Zhang To: Mike Smith Cc: Harry Starr , current Subject: Re: disk slices and MAKEDEV confusion In-Reply-To: <199905241618.JAA22046@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 > > The problem is that if you made all of the nodes for all of the > supported slices, /dev would be incredibly bloated. There are 8 > potential nodes per slice, and 20 potential slices per disk, plus the > compatability slice, so that's 168 node pairs (raw and buffered) > _per_disk_. > According to the information in sys/diskslice.h, there are 32 slices per disk, including the compatibility slice and the base slice. Am I right? -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 24 18:49:45 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 357FE14E47 for ; Mon, 24 May 1999 18:49:42 -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 SAA00951; Mon, 24 May 1999 18:45:58 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905250145.SAA00951@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Zhihui Zhang Cc: Mike Smith , Harry Starr , current Subject: Re: disk slices and MAKEDEV confusion In-reply-to: Your message of "Mon, 24 May 1999 21:31:57 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 May 1999 18:45:58 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > The problem is that if you made all of the nodes for all of the > > supported slices, /dev would be incredibly bloated. There are 8 > > potential nodes per slice, and 20 potential slices per disk, plus the > > compatability slice, so that's 168 node pairs (raw and buffered) > > _per_disk_. > > > > According to the information in sys/diskslice.h, there are 32 slices per > disk, including the compatibility slice and the base slice. Am I right? There is an allowable maximum of 32 slices. In reality, the DOS partitioning scheme allows four partitions, each of which may be an "extended" partition containing four more. -- \\ 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 Mon May 24 22:48:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles502.castles.com [208.214.165.66]) by hub.freebsd.org (Postfix) with ESMTP id 8F04F14E31 for ; Mon, 24 May 1999 22:48:42 -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 WAA00428; Mon, 24 May 1999 22:46:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905250546.WAA00428@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nicolas Souchu Cc: current@FreeBSD.ORG Subject: Re: Heads up! config(8) changes.. In-reply-to: Your message of "Mon, 24 May 1999 12:46:29 +0200." <19990524124629.55958@breizh.teaser.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 May 1999 22:46:41 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> What do you do about the "ppc" device? Formerly, it needed to be "net > >> irq ..." if the "plip" device was going to be used, but "tty irq ..." > >> otherwise. Which one did you pick? > > > >It needs to flip between one or both, but I can't raise Nicolas lately, > >so I'm starting to fear that we're going to need a new maintainer. > >That bites, given how well things were going. > > Someone who would help me driving ppbus, yes. I didn't have enough time > last months. Do you expect that the situation will improve, or do you feel you need to hand it over to a new maintainer? > So, what are the next issues: > > - porting ppbus to newbus (especially irq managment) Yes. > - fix ppc probe bugs with recent mainboards I think that this needs to wait on the PnP hooks into the resource manager. If the chipset probes are killing something, I'd wager that the something in question is mentioned in the PnP data. > - sync -current and -stable This would be handy, and could probably be achieved easily. > - test plip in depth That'd be useful. I would add - Improve ECP/EPP performance if possible. - Add/finish bidirectional ECP printer support. > I think there is more to do with making ppbus more and more stable than > bringing new capabilities to it yet. That's certainly a worthwhile perspective. What can we do to help you? -- \\ 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 Tue May 25 1:50: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id 6A7E614C93; Tue, 25 May 1999 01:49:58 -0700 (PDT) (envelope-from brian@keep.lan.Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id JAA03493; Tue, 25 May 1999 09:49:55 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00559; Tue, 25 May 1999 08:46:21 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199905250746.IAA00559@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Nicholas J. Esborn" Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: natd as a 'routing daemon' In-reply-to: Your message of "Mon, 24 May 1999 12:00:45 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 May 1999 08:46:21 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just a thought... > > Might it not be logical to put natd in the 'routing daemons' section of > the boot process? That would start it before things like quota checking, > which can take a lot of time and prevent a combination worgroup server/NAT > box from providing network access, even when it could be with no > consequence. > > Also, it does seem rather like a form of routing. Natd is now started right after the firewall is loaded - as a ``divert daemon''. > Nicholas Esborn | > www.azstarnet.com | StarNet > (520) 618-RTFM | -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 1:54:38 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 827D114C93 for ; Tue, 25 May 1999 01:54:35 -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 JAA46199; Tue, 25 May 1999 09:54:31 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 25 May 1999 09:54:31 +0100 (BST) From: Doug Rabson To: Mike Smith Cc: Nicolas Souchu , current@freebsd.org Subject: Re: Heads up! config(8) changes.. In-Reply-To: <199905250546.WAA00428@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 Mon, 24 May 1999, Mike Smith wrote: > I would add > > - Improve ECP/EPP performance if possible. > > - Add/finish bidirectional ECP printer support. Could you also move the source for ppc out of the i386 tree into somewhere architecture independant. If its ported to new-bus then this driver should work virtually unmodified on the alpha. -- 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 Tue May 25 2:52:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 4668D14BE1; Tue, 25 May 1999 02:52:09 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id KAA23813; Tue, 25 May 1999 10:01:11 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id JAA09060; Tue, 25 May 1999 09:59:38 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905250759.JAA09060@yedi.iaf.nl> Subject: Re: de driver problem In-Reply-To: <199905221903.VAA17416@yedi.iaf.nl> from Wilko Bulte at "May 22, 1999 9: 3:43 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Tue, 25 May 1999 09:59:38 +0200 (CEST) Cc: dfr@nlsystems.com, khaled@mailbox.telia.net, freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Wilko Bulte wrote ... > As Doug Rabson wrote ... > > On Sat, 15 May 1999, Wilko Bulte wrote: > > > > > As Doug Rabson wrote ... > > > > On Mon, 10 May 1999, Wilko Bulte wrote: > > > After a buildworld of yesterday's -current and a new kernel things > > > work just fine. As an added bonus the serial console seems to work better. > > > It used to be very slow, looks like that is gone. > > > > > > If you want more info you'll have to wait a bit, I'll be offline for > > > a week. > > > > Thats good. The slow serial sounds like it used to be polling (i.e. sio > > interrupts weren't getting through). > > I've been away to Oslo this week, but I plan to bang a bit more on the > console to see if it keeps working ok. Banged on it and it works great now on the Alpine. Wilko | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 3: 4: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 8316714BE1 for ; Tue, 25 May 1999 03:04:40 -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 UAA13651; Tue, 25 May 1999 20:02:54 +1000 Date: Tue, 25 May 1999 20:02:54 +1000 From: Bruce Evans Message-Id: <199905251002.UAA13651@godzilla.zeta.org.au> To: mike@smith.net.au, starr3@gccs.com.au Subject: Re: disk slices and MAKEDEV confusion Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> SO! Why does "sh MAKEDEV all" NOT make the partition entries for the >> slice(s) ??? >> >> ie, "sh MAKEDEV all" only makes the "compatability" slice entries -- da0s1, >> da0s2 etc. > >da0s1 is not a "compatibility slice" entry. That would be da0a, etc. > >The problem is that if you made all of the nodes for all of the >supported slices, /dev would be incredibly bloated. There are 8 >potential nodes per slice, and 20 potential slices per disk, plus the 30 >compatability slice, so that's 168 node pairs (raw and buffered) plus the whole disk slice times 2 for character devices (8 * 31 + 1) * 2 = 498 >_per_disk_. However, this should have been considered before changing the default configuration from using the compatibility slice to using a real slice. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 3: 5:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 1704D1566A for ; Tue, 25 May 1999 03:05:23 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Tue, 25 May 1999 12:08:11 +0200 Message-ID: <55586E7391ACD211B9730000C110027617961A@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Doug White' , Doug Rabson Cc: FreeBSD current Mailing list Subject: RE: priorities Date: Tue, 25 May 1999 12:03:12 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Doug White [SMTP:dwhite@resnet.uoregon.edu] > Sent: Sunday, May 23, 1999 2:46 AM > To: Doug Rabson > Cc: FreeBSD current Mailing list > Subject: Re: priorities > > On Fri, 21 May 1999, Doug Rabson wrote: > > If you've worked on Windows or Macs, you know what I'm talking about > ("Device failure" or "Could not switch your connection due to an > error"). > [ML] Or my all-time-favorite from Excel: "File was not saved." /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 3:38:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id 6D04D1565D for ; Tue, 25 May 1999 03:38:10 -0700 (PDT) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id MAA30412; Tue, 25 May 1999 12:38:01 +0200 (MET DST) Received: (from nsouch@localhost) by teaser.fr (8.9.3/8.9.1) id MAA27723; Tue, 25 May 1999 12:37:10 +0200 (CEST) (envelope-from nsouch) Message-ID: <19990525123709.08844@breizh.teaser.fr> Date: Tue, 25 May 1999 12:37:09 +0200 From: Nicolas Souchu To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: Heads up! config(8) changes.. References: <19990524124629.55958@breizh.teaser.fr> <199905250546.WAA00428@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199905250546.WAA00428@dingo.cdrom.com>; from Mike Smith on Mon, May 24, 1999 at 10:46:41PM -0700 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 24, 1999 at 10:46:41PM -0700, Mike Smith wrote: >> >> Someone who would help me driving ppbus, yes. I didn't have enough time >> last months. > >Do you expect that the situation will improve, or do you feel you need >to hand it over to a new maintainer? > The situation shall improve. But I'd like to keep time to manage iic/smbus a bit more closely. What takes time is not the development, but answering to questions, track bugs, fix them... the second live of the software. I don't have time for both, especially when the whole operating system is changing very fast like it did last few months, breaking all development tools (ether/netboot, elf/aout, gdb...). I stop here :) Most of the framework is ready to work. Just some fixes and more testing are needed for the topics mentionned later (excepted ECP support which needs more work). > >> - fix ppc probe bugs with recent mainboards > >I think that this needs to wait on the PnP hooks into the resource >manager. If the chipset probes are killing something, I'd wager that >the something in question is mentioned in the PnP data. > >> - sync -current and -stable > >This would be handy, and could probably be achieved easily. > >> - test plip in depth > >That'd be useful. > >I would add > > - Improve ECP/EPP performance if possible. What do you mean here? PLIP? Then yes. I was in contact with the Linux part for this. We'll have to look at there protocol choices. > > - Add/finish bidirectional ECP printer support. Shall not be too hard with an ECP printer. Most of the needed routines are already in the ppbus framework. But I'm afraid that it will lead to the rewrite of lpt driver, not a bad thing though. > >> I think there is more to do with making ppbus more and more stable than >> bringing new capabilities to it yet. > >That's certainly a worthwhile perspective. What can we do to help you? Thanks. I can't afford both developments and ppbus support. Peter proposed me some help for the newbus port (removing linker_sets). I still need manpower for the support (I know this may not be the finest part of the advanture) and the plip extensions if requested by the FreeBSD community (may not be mandatory with cheaper network cards and USB...). And finally find an ECP printer around. > >-- >\\ The mind's the standard \\ Mike Smith >\\ of the man. \\ msmith@freebsd.org >\\ -- Joseph Merrick \\ msmith@cdrom.com > > > Nicholas -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Tue May 25 7:26:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4866A14C24 for ; Tue, 25 May 1999 07:26:17 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from hamilton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 25 May 99 15:26:17 +0100 (BST) To: freebsd-current@freebsd.org Subject: Sandbox for rpc services? X-Request-Do: Date: Tue, 25 May 1999 15:26:17 +0100 From: David Malone Message-ID: <9905251526.aa27225@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since identd and talk have been sandboxed in -current I was wondering if rpc services could also be sandboxed, or is there something which says they have to run as root. I'm guessing, but it might be possible to run the following services with the following privilege. rstatd kmem rusersd nobody walld tty pcnfsd root rquotad root sprayd nobody lockd root statd ? nfsd root nfsiod root Has anyone thought about this? Is it a dead end, or should I try to find out if it works? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 9:35:19 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 98C5914A09 for ; Tue, 25 May 1999 09:35: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 MAA11353; Tue, 25 May 1999 12:35:12 -0400 (EDT) (envelope-from wollman) Date: Tue, 25 May 1999 12:35:12 -0400 (EDT) From: Garrett Wollman Message-Id: <199905251635.MAA11353@khavrinen.lcs.mit.edu> To: current@freebsd.org Subject: More compiler option comparisons Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just for completeness, I did one final run of HINT with just `-O' specified (our usual default). `-O' results in significantly better integer performance than `-O4'. (Floating-point performance is just the opposite.) This suggests that compiling the world with `-O' levels higher than one is probably a bad idea. (The generated assembly is identical from `-O2' to `-O4'.) The `-O2' code appears to be less efficient at register allocation; about twice as much stack temporary space is required. For the graph, see . -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 Tue May 25 9:44: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 822C214CD5 for ; Tue, 25 May 1999 09:42:55 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (unknown [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id C8EFF3EA; Tue, 25 May 1999 16:42:48 +0000 (GMT) Date: Tue, 25 May 1999 20:42:48 +0400 (MSD) From: oZZ!!! To: Marc van Woerkom Cc: hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@FreeBSD.ORG Subject: Re: No sound (Ensoniq Audio PCI 1370) In-Reply-To: <199905221101.NAA01071@oranje.my.domain> 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! I install new SB card to my computer & configure kernel with follwing string, describing SB 128 PCI: device pcm0 at nexus? and got this messages after reboot: es0: irq 5 at device 11.0 on pci0 pcm0: using I/O space register mapping at 0xe800 osa@ozz$ cat /dev/sndstat FreeBSD Audio Driver (981002) May 25 1999 19:13:45 Installed devices: pcm0: at 0xe800 irq 0 dma 0:0 # cd /dev # rm audio dsp dspW mixer # ./MAKEDEV snd0 But play (from ports) can't work... # play file.wav play: /dev/dsp: Invalid argument Something wrong? Rgdz, Sergey Osokin aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 9:50:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id 5F5D414DDD for ; Tue, 25 May 1999 09:50:29 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-69-140.atl.bellsouth.net [209.214.69.140]) by mail1.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id MAA11140; Tue, 25 May 1999 12:48:15 -0400 (EDT) Received: from wghicks (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id MAA81982; Tue, 25 May 1999 12:52:16 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199905251652.MAA81982@bellsouth.net> To: oZZ!!! Cc: Marc van Woerkom , hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: No sound (Ensoniq Audio PCI 1370) In-reply-to: Your message of "Tue, 25 May 1999 20:42:48 +0400." Date: Tue, 25 May 1999 12:52:16 -0400 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snips] > device pcm0 at nexus? . . . > # cd /dev > # rm audio dsp dspW mixer > # ./MAKEDEV snd0 > But play (from ports) can't work... That should be snd1 for the pcm driver Good Luck, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 9:58: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id 1CC4C15351 for ; Tue, 25 May 1999 09:58:03 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-69-140.atl.bellsouth.net [209.214.69.140]) by mail1.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id MAA16645; Tue, 25 May 1999 12:55:58 -0400 (EDT) Received: from wghicks (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id NAA82022; Tue, 25 May 1999 13:00:00 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199905251700.NAA82022@bellsouth.net> To: W Gerald Hicks Cc: current@freebsd.org Subject: Re: No sound (Ensoniq Audio PCI 1370) In-reply-to: Your message of "Tue, 25 May 1999 12:52:16 EDT." <199905251652.MAA81982@bellsouth.net> Date: Tue, 25 May 1999 13:00:00 -0400 From: W Gerald Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ARGH! Trim the reply list next time Jerry... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 10:13: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from hermes.koege-gym.dk (unknown [195.192.213.120]) by hub.freebsd.org (Postfix) with ESMTP id E3CDB14FBF for ; Tue, 25 May 1999 10:13:00 -0700 (PDT) (envelope-from sst@hermes.koege-gym.dk) Received: (from sst@localhost) by hermes.koege-gym.dk (8.9.2/8.9.2) id TAA01866 for current@freebsd.org; Tue, 25 May 1999 19:12:59 +0200 (CEST) (envelope-from sst) Date: Tue, 25 May 1999 19:12:59 +0200 From: Sune Stjerneby To: current@freebsd.org Subject: CCD and the new ATA/ATAPI subsystem? Message-ID: <19990525191258.B1642@hermes.koege-gym.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Am I correct in the assumption that CCD and the new ATA/ATAPI subsystem is a bad combination? It won't let me configure ccd0 when using the adx rather than wdx syntax.. // Sune Stjerneby {Herfoelge, Denmark, EU} -- "Go, Go, DECzilla!" -- "Berkeley UNIX: 22 Years on the VAX." -- http://www.{Net,Free,Open}BSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 11: 2:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id E56EB15227 for ; Tue, 25 May 1999 11:02:29 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (unknown [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 335F8173; Tue, 25 May 1999 18:02:23 +0000 (GMT) Date: Tue, 25 May 1999 22:02:23 +0400 (MSD) From: oZZ!!! To: W Gerald Hicks Cc: Marc van Woerkom , hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: No sound (Ensoniq Audio PCI 1370) In-Reply-To: <199905251652.MAA81982@bellsouth.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 Tue, 25 May 1999, W Gerald Hicks wrote: > [snips] > > device pcm0 at nexus? > . > . > . > > # cd /dev > > # rm audio dsp dspW mixer > > # ./MAKEDEV snd0 > > > But play (from ports) can't work... > > That should be snd1 for the pcm driver # cd /dev # rm audio dsp dspW mixer # ./MAKEDEV snd1 # play notify.wav play: /dev/dsp: Invalid argument Whats wrong? Rgdz, Sergey Osokin, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 11:11:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.t.dk (freesbee.t.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with SMTP id C079314DF5 for ; Tue, 25 May 1999 11:10:47 -0700 (PDT) (envelope-from jesper@freesbee.t.dk) Received: (qmail 18854 invoked by uid 1001); 25 May 1999 18:10:45 -0000 Date: Tue, 25 May 1999 20:10:45 +0200 From: Jesper Skriver To: Sune Stjerneby Cc: current@freebsd.org Subject: Re: CCD and the new ATA/ATAPI subsystem? Message-ID: <19990525201045.C18424@skriver.dk> References: <19990525191258.B1642@hermes.koege-gym.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.2i In-Reply-To: <19990525191258.B1642@hermes.koege-gym.dk>; from Sune Stjerneby on Tue, May 25, 1999 at 07:12:59PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Don't know, but have a look a vinum instead, a much better solution. /Jesper On Tue, May 25, 1999 at 07:12:59PM +0200, Sune Stjerneby wrote: > Hi, > > Am I correct in the assumption that CCD and the new ATA/ATAPI subsystem > is a bad combination? It won't let me configure ccd0 when using the adx > rather than wdx syntax.. > > // Sune Stjerneby > {Herfoelge, Denmark, EU} > -- "Go, Go, DECzilla!" > -- "Berkeley UNIX: 22 Years on the VAX." > -- http://www.{Net,Free,Open}BSD.ORG > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 11:35:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id EFCF0153FA for ; Tue, 25 May 1999 11:35:06 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id NAA18684; Tue, 25 May 1999 13:35:02 -0500 (CDT) (envelope-from dan) Date: Tue, 25 May 1999 13:35:00 -0500 From: Dan Nelson To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: More compiler option comparisons Message-ID: <19990525133459.B17956@dan.emsphone.com> References: <199905251635.MAA11353@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199905251635.MAA11353@khavrinen.lcs.mit.edu>; from "Garrett Wollman" on Tue May 25 12:35:12 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (May 25), Garrett Wollman said: > Just for completeness, I did one final run of HINT with just `-O' > specified (our usual default). `-O' results in significantly better > integer performance than `-O4'. (Floating-point performance is just > the opposite.) > > This suggests that compiling the world with `-O' levels higher than > one is probably a bad idea. (The generated assembly is identical from > `-O2' to `-O4'.) The `-O2' code appears to be less efficient at > register allocation; about twice as much stack temporary space is > required. -O4 doesn't exist in egcs (or it didn't a month or so ago). According to the source, -O2 enables all optimizations except -funroll-all-loops, and all -O3 does is enable -funroll-all-loops. I'd like to see separate runs, one with each -march= option (i386, i486, i586, i686), so see if those many any difference at all. -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 12: 5:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id BAEE0158E0 for ; Tue, 25 May 1999 12:05:45 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id VAA03897 for ; Tue, 25 May 1999 21:05:41 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id VAA29541 for ; Tue, 25 May 1999 21:05:40 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905251905.VAA29541@greenpeace.grondar.za> To: current@freebsd.org Subject: Boot process Date: Tue, 25 May 1999 21:05:39 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I am having some problems with a machine I recently rebuilt; I suspect either the drive geometry or something else in the boot process. The machine has to be booted "manually". Situation: I installed FreeBSD 3.1 on a 4G SCSI disk that had had Current on it before (CURRENT snaps wouldn't boot). At the F1 FreeBSD F5 Disk 1 prompt, the machine just beeps, and does not reboot. (The other disk is a 2G SCSI) Drive geometry is 64 heads, 32 sectors and N(>1024) tracks. The a partition is the first and it is only 32MB. Disklabel looks OK. If I play around (Hit F5 or space or enter), I get "Invalid partition" errors. Hitting enter at that stage gets me a Boot: prompt. The only thing that gets an actial boot is typing 0:da(1,a)/boot/loader. Then both disks are visible and fine. Both disks have had fdisk -b and disklabel -B done to them. Any clues? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 12:34: 0 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 4C9FA15B55 for ; Tue, 25 May 1999 12:33:56 -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 MAA00615; Tue, 25 May 1999 12:31:12 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905251931.MAA00615@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray Cc: current@freebsd.org Subject: Re: Boot process In-reply-to: Your message of "Tue, 25 May 1999 21:05:39 +0200." <199905251905.VAA29541@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 May 1999 12:31:12 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am having some problems with a machine I recently rebuilt; I suspect > either the drive geometry or something else in the boot process. The > machine has to be booted "manually". > > Situation: I installed FreeBSD 3.1 on a 4G SCSI disk that had had > Current on it before (CURRENT snaps wouldn't boot). At the > F1 FreeBSD > F5 Disk 1 > prompt, the machine just beeps, and does not reboot. (The other > disk is a 2G SCSI) Which disk are you trying to boot from? > Drive geometry is 64 heads, 32 sectors and N(>1024) tracks. The > a partition is the first and it is only 32MB. Disklabel looks > OK. > > If I play around (Hit F5 or space or enter), I get "Invalid partition" > errors. Hitting enter at that stage gets me a Boot: prompt. The only > thing that gets an actial boot is typing 0:da(1,a)/boot/loader. Then > both disks are visible and fine. Both disks have had fdisk -b and > disklabel -B done to them. > > Any clues? Sounds like the layout of the first disk is not compatible with your BIOS. What's the slice scheme look like? -- \\ 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 Tue May 25 12:50:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 3C36A15AE6 for ; Tue, 25 May 1999 12:49:50 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id VAA03988; Tue, 25 May 1999 21:49:44 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id VAA29779; Tue, 25 May 1999 21:49:42 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905251949.VAA29779@greenpeace.grondar.za> To: Mike Smith Cc: current@freebsd.org Subject: Re: Boot process Date: Tue, 25 May 1999 21:49:41 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am having some problems with a machine I recently rebuilt; I suspect > > either the drive geometry or something else in the boot process. The > > machine has to be booted "manually". > > > > Situation: I installed FreeBSD 3.1 on a 4G SCSI disk that had had > > Current on it before (CURRENT snaps wouldn't boot). At the > > F1 FreeBSD > > F5 Disk 1 > > prompt, the machine just beeps, and does not reboot. (The other > > disk is a 2G SCSI) > > Which disk are you trying to boot from? Default: da0(s1) > > Drive geometry is 64 heads, 32 sectors and N(>1024) tracks. The > > a partition is the first and it is only 32MB. Disklabel looks > > OK. > > > > If I play around (Hit F5 or space or enter), I get "Invalid partition" > > errors. Hitting enter at that stage gets me a Boot: prompt. The only > > thing that gets an actial boot is typing 0:da(1,a)/boot/loader. Then > > both disks are visible and fine. Both disks have had fdisk -b and > > disklabel -B done to them. > > > > Any clues? > > Sounds like the layout of the first disk is not compatible with your > BIOS. What's the slice scheme look like? Not sure _exactly_ what you want; fdisk says: (copying) : cylinders=4340 heads=64 sectors/track=32 (2048 blocks/cyl) : The data for partition 1 is: sysid 165,(FreeBSD/.... start 32, size 8888288, (4339 Meg), flag 80 (active) beg: cyl 0/head 1/sector 1; end: cyl 1023/head 32/head 63; The data for partition 2 is: : I've seen some funny things in fdisk, but they usually work. ("Funny" == cyl-is-strange-due-to-11-bit-limit). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 13:28:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 36EA71536B for ; Tue, 25 May 1999 13:28:39 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id FAA27996; Wed, 26 May 1999 05:28:14 +0900 (JST) Message-ID: <374B0709.DDD21E45@newsguy.com> Date: Wed, 26 May 1999 05:24:41 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: Boot process References: <199905251905.VAA29541@greenpeace.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > If I play around (Hit F5 or space or enter), I get "Invalid partition" > errors. Hitting enter at that stage gets me a Boot: prompt. The only > thing that gets an actial boot is typing 0:da(1,a)/boot/loader. Then > both disks are visible and fine. Both disks have had fdisk -b and > disklabel -B done to them. What happens if you press F1? And on the help message of the second stage prompt, what does it claims to be the default? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If at first you don't succeed, skydiving is not for you." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 13:40:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 0A2D215476 for ; Tue, 25 May 1999 13:40:05 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA04113; Tue, 25 May 1999 22:40:03 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id WAA30048; Tue, 25 May 1999 22:40:02 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905252040.WAA30048@greenpeace.grondar.za> To: "Daniel C. Sobral" Cc: current@FreeBSD.ORG Subject: Re: Boot process Date: Tue, 25 May 1999 22:40:01 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mark Murray wrote: > > > > If I play around (Hit F5 or space or enter), I get "Invalid partition" > > errors. Hitting enter at that stage gets me a Boot: prompt. The only > > thing that gets an actial boot is typing 0:da(1,a)/boot/loader. Then > > both disks are visible and fine. Both disks have had fdisk -b and > > disklabel -B done to them. > > What happens if you press F1? > And on the help message of the second stage prompt, what does it > claims to be the default? F5 gives F1 FreeBSD F5 Disk 0 (or whatever) F1 gives Gives Boot: With a default of 1:da(1,a)/boot/loader If I type 0:da(1,a)/boot/loader it boots. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 13:43:40 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 DF8B915465 for ; Tue, 25 May 1999 13:43:36 -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 QAA12105; Tue, 25 May 1999 16:43:35 -0400 (EDT) (envelope-from wollman) Date: Tue, 25 May 1999 16:43:35 -0400 (EDT) From: Garrett Wollman Message-Id: <199905252043.QAA12105@khavrinen.lcs.mit.edu> To: Dan Nelson Cc: current@FreeBSD.ORG Subject: Re: More compiler option comparisons In-Reply-To: <19990525133459.B17956@dan.emsphone.com> References: <199905251635.MAA11353@khavrinen.lcs.mit.edu> <19990525133459.B17956@dan.emsphone.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I'd like to see separate runs, one with each -march= option (i386, > i486, i586, i686), so see if those many any difference at all. As you will have seen from my post yesterday, there is no measurable difference between -march=pentiumpro and no -march= option. You're certainly welcome to try it yourself for whatever other combinations of options you like. -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 Tue May 25 13:46:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m2-33-dbn.dial-up.net [196.34.155.97]) by hub.freebsd.org (Postfix) with ESMTP id 8839B15476 for ; Tue, 25 May 1999 13:46:17 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA16260; Tue, 25 May 1999 22:45:31 +0200 (SAST) From: Robert Nordier Message-Id: <199905252045.WAA16260@ceia.nordier.com> Subject: Re: Boot process In-Reply-To: <199905251949.VAA29779@greenpeace.grondar.za> from Mark Murray at "May 25, 1999 09:49:41 pm" To: mark@grondar.za (Mark Murray) Date: Tue, 25 May 1999 22:45:29 +0200 (SAST) Cc: mike@smith.net.au (Mike Smith), 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 am having some problems with a machine I recently rebuilt; I suspect > > > either the drive geometry or something else in the boot process. The > > > machine has to be booted "manually". > > > > > > Situation: I installed FreeBSD 3.1 on a 4G SCSI disk that had had > > > Current on it before (CURRENT snaps wouldn't boot). At the > > > F1 FreeBSD > > > F5 Disk 1 > > > prompt, the machine just beeps, and does not reboot. (The other > > > disk is a 2G SCSI) > > > > Which disk are you trying to boot from? > > Default: da0(s1) > > > > Drive geometry is 64 heads, 32 sectors and N(>1024) tracks. The > > > a partition is the first and it is only 32MB. Disklabel looks > > > OK. > > > > > > If I play around (Hit F5 or space or enter), I get "Invalid partition" > > > errors. Hitting enter at that stage gets me a Boot: prompt. The only > > > thing that gets an actial boot is typing 0:da(1,a)/boot/loader. Then > > > both disks are visible and fine. Both disks have had fdisk -b and > > > disklabel -B done to them. > > > > > > Any clues? > > > > Sounds like the layout of the first disk is not compatible with your > > BIOS. What's the slice scheme look like? > > Not sure _exactly_ what you want; fdisk says: (copying) > > : > cylinders=4340 heads=64 sectors/track=32 (2048 blocks/cyl) > : > The data for partition 1 is: > sysid 165,(FreeBSD/.... > start 32, size 8888288, (4339 Meg), flag 80 (active) > beg: cyl 0/head 1/sector 1; > end: cyl 1023/head 32/head 63; > The data for partition 2 is: > > : > > I've seen some funny things in fdisk, but they usually work. ("Funny" > == cyl-is-strange-due-to-11-bit-limit). If you want to dd the first sector of /dev/rda0, and the first 17 sectors of /dev/rda0s1, and send them to me, I don't mind taking a look. It's usually just quicker to resolve these things with the raw disk sectors handy. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 14:35:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from virtualia.combios.es (virtualia.combios.es [195.53.190.48]) by hub.freebsd.org (Postfix) with SMTP id B1E7B158AE; Tue, 25 May 1999 14:34:43 -0700 (PDT) (envelope-from callback@workmail.com) Received: from pop01.globecomm.net (206.253.129.185) by virtualia.combios.es (EMWAC SMTPRS 0.81) with SMTP id ; Tue, 25 May 1999 23:32:59 +0200 Received: from workmail.com (36229.rad.bbv.es [195.235.36.229]) by pop01.globecomm.net (8.9.0/8.8.0) with SMTP id RAA18023; Tue, 25 May 1999 17:33:32 -0400 (EDT) Date: Tue, 25 May 1999 17:33:32 -0400 (EDT) From: callback@workmail.com Message-Id: <199905252133.RAA18023@pop01.globecomm.net> To: callback@workmail.com Subject: CAMBIO DE DIRECCION EMAIL Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Disculpe la intromisión. Tengo que comunicarles que mis tres direcciones principales de redireccionamiento hasta ahora: callback@correo.nu call-back@correo.nu call-back@correovirtual.com han sido eliminadas por cese de actividad de su dominio como pueden comprobar en las direcciones http://www.correo.nu y http://www.correovirtual.com. Por otro lado por nuestra cuenta vamos a abandonar las direcciones: callback@workmail.com call-back@lycosmail.com por los muchos fallos y desconexiones que tiene el proveedor mail.com. Asi con todo lo relacionado con el sistema CallBack y sistema 800 (Tarjetas Virtuales) de IAS, pueden ponerse en contacto con nuestra dirección principal ya conocida o con la siguiente direccion info@callback.zzn.com Saludos -------------------------------------------------------------------------------------------------------------------------------- CORREO GRATUITO EN NUEVE IDIOMAS EN http://callback.zzn.com --------------------------------------------------------------------------------------------------------------- Hallo: Exculpates the interference. I than to communicate them than this addresses main of forward until now: callback@correo.nu call-back@correo.nu call-back@correovirtual.com han been eliminated by end of activity of his domain as they can check at the addresses http://www.correo.nu and http://www.correovirtual.com. Let's go to abandon the addresses: callback@workmail.com call-back@lycosmail.com by the many failures and desconexiones than he have the providor mail.com. Related to with the system CallBack and system 800 (Virtual Cards) of IAS, they can to be laied at contact with our address main already knowed or with the following address info@callback.zzn.com Greetings -------------------------------------------------------------------------------------------------------------------------------- EMAIL FREE AT NINE LANGUAGES AT http://callback.zzn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 16:45:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx.nsu.ru (mx.nsu.ru [193.124.215.71]) by hub.freebsd.org (Postfix) with ESMTP id D0D4E15027; Tue, 25 May 1999 16:45:06 -0700 (PDT) (envelope-from semen@iclub.nsu.ru) Received: from iclub.nsu.ru (semen@iclub.nsu.ru [193.124.222.66]) by mx.nsu.ru (8.9.1/8.9.0) with ESMTP id GAA08815; Wed, 26 May 1999 06:45:01 +0700 (NOVST) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.9.3/8.8.5) with ESMTP id GAA07714; Wed, 26 May 1999 06:45:00 +0700 (NSS) Date: Wed, 26 May 1999 06:45:00 +0700 (NSS) From: Ustimenko Semen To: freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: HPFS driver for FreeBSD needs testers. 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! There is a driver to read from HPFS partition at: http://iclub.nsu.ru/~semen/hpfs/hpfs-0.2b.tgz Testers are welcome. Bye. P.S. We can put it in current, and i'll support it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 17:12:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 15D6914F55 for ; Tue, 25 May 1999 17:12:21 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id RAA03549; Tue, 25 May 1999 17:12:12 -0700 (PDT) (envelope-from obrien) Message-ID: <19990525171212.B3497@nuxi.com> Date: Tue, 25 May 1999 17:12:12 -0700 From: "David O'Brien" To: Nicolas Souchu Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Heads up! config(8) changes.. Reply-To: obrien@NUXI.com References: <199905250546.WAA00428@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Doug Rabson on Tue, May 25, 1999 at 09:54:31AM +0100 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 25, 1999 at 09:54:31AM +0100, Doug Rabson wrote: > > Could you also move the source for ppc out of the i386 tree into somewhere > architecture independant. PLEASE ask cvs@freebsd.org for a repository copy when you do this. When you renamed nlpt.c to lpt.c, you just committed a new file and thus all history was lost. -- -- David (obrien@NUXI.com -or- obrien@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 May 25 17:17:20 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 7F34714F55 for ; Tue, 25 May 1999 17:17:17 -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 UAA07633; Tue, 25 May 1999 20:16:33 -0400 (EDT) Date: Tue, 25 May 1999 20:16:32 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: oZZ!!! Cc: W Gerald Hicks , Marc van Woerkom , hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: No sound (Ensoniq Audio PCI 1370) 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 Tue, 25 May 1999, oZZ!!! wrote: > > On Tue, 25 May 1999, W Gerald Hicks wrote: > > > [snips] > > > device pcm0 at nexus? > > . > > . > > . > > > # cd /dev > > > # rm audio dsp dspW mixer > > > # ./MAKEDEV snd0 > > > > > But play (from ports) can't work... > > > > That should be snd1 for the pcm driver > # cd /dev > # rm audio dsp dspW mixer > # ./MAKEDEV snd1 > # play notify.wav > play: /dev/dsp: Invalid argument > > Whats wrong? What's wrong is that you have _only_ tried using a single program to test your audio system out. > > Rgdz, > Sergey Osokin, > osa@etrust.ru > > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 Tue May 25 20: 8:14 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 3DF2714E01 for ; Tue, 25 May 1999 20:08:00 -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 LAA08768 for ; Wed, 26 May 1999 11:07:07 +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 LAA10921 for ; Wed, 26 May 1999 11:07:57 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id LAA12331; Wed, 26 May 1999 11:07:56 +0800 Message-Id: <199905260307.LAA12331@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Hacking objcopy Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 May 1999 11:07:55 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would anyone have any objections to me hacking objcopy so that it could do the following - a) Change symbol names from one thing to another b) Add/remove dependencies on other shared objects. If I submit these changes, what chance do I have of getting them made "official"? 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 Tue May 25 21:20:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep8.mail.ozemail.net (fep8.mail.ozemail.net [203.2.192.102]) by hub.freebsd.org (Postfix) with ESMTP id E75C11509D for ; Tue, 25 May 1999 21:20:22 -0700 (PDT) (envelope-from c9710216@atlas.newcastle.edu.au) Received: from atlas.newcastle.edu.au (slnew51p29.ozemail.com.au [203.108.150.45]) by fep8.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id OAA08120 for ; Wed, 26 May 1999 14:20:19 +1000 (EST) Message-ID: <374B7669.E8463ABF@atlas.newcastle.edu.au> Date: Wed, 26 May 1999 14:19:53 +1000 From: obituary X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: More compiler option comparisons References: <199905251635.MAA11353@khavrinen.lcs.mit.edu> <19990525133459.B17956@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Nelson wrote: > -O4 doesn't exist in egcs (or it didn't a month or so ago). According > to the source, -O2 enables all optimizations except -funroll-all-loops, > and all -O3 does is enable -funroll-all-loops. I think I recall reading somewhere that EGCS uses -O numbers > 3 to test experimental optimizations. -jake (obituary) Powered by FreeBSD c9710216@atlas.newcastle.edu.au 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 Tue May 25 21:34:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id BE97D15051 for ; Tue, 25 May 1999 21:34:36 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Tue, 25 May 1999 21:34:35 -0700 From: "David Schwartz" To: "obituary" Cc: Subject: RE: More compiler option comparisons Date: Tue, 25 May 1999 21:34:34 -0700 Message-ID: <000001bea731$0e713990$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-reply-to: <374B7669.E8463ABF@atlas.newcastle.edu.au> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With egcs, the '-O' flag doesn't specify the optimization level like it does in GCC. It specifies the desired stability of the generated code. Lower numbers (0,1,2) request higher stability. ;) DS > Dan Nelson wrote: > > -O4 doesn't exist in egcs (or it didn't a month or so ago). According > > to the source, -O2 enables all optimizations except -funroll-all-loops, > > and all -O3 does is enable -funroll-all-loops. > > I think I recall reading somewhere that EGCS uses -O numbers > 3 to test > experimental optimizations. > > -jake (obituary) Powered by FreeBSD > c9710216@atlas.newcastle.edu.au 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 Tue May 25 22: 8:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from deep-thought.demos.su (deep-thought.demos.su [194.87.1.76]) by hub.freebsd.org (Postfix) with ESMTP id 7A37814D8B for ; Tue, 25 May 1999 22:08:14 -0700 (PDT) (envelope-from ache@deep-thought.demos.su) Received: (from ache@localhost) by deep-thought.demos.su (8.9.3/8.9.3) id JAA23760 for current@freebsd.org; Wed, 26 May 1999 09:08:13 +0400 (MSD) (envelope-from ache) Date: Wed, 26 May 1999 09:08:11 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: kvm_getswapinfo is broken Message-ID: <19990526090810.A23737@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just check 'swapinfo' in recent -current, it shows "/dev/(null)" as swap device, it means that devinfo() call in kvm_getswapinfo() returns NULL, i.e. called with wrong argument which is swinfo.sw_dev Fix it, please. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 22:25: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id B7D4E15018 for ; Tue, 25 May 1999 22:24:53 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (unknown [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 1BE1D1EA; Wed, 26 May 1999 05:24:50 +0000 (GMT) Date: Wed, 26 May 1999 09:24:50 +0400 (MSD) From: oZZ!!! To: Brian Feldman Cc: W Gerald Hicks , Marc van Woerkom , hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: No sound (Ensoniq Audio PCI 1370) 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 Tue, 25 May 1999, Brian Feldman wrote: > > > > device pcm0 at nexus? > > > . > > > > # cd /dev > > > > # rm audio dsp dspW mixer > > > > # ./MAKEDEV snd0 > > > > > > > But play (from ports) can't work... > > > > > > That should be snd1 for the pcm driver > > # cd /dev > > # rm audio dsp dspW mixer > > # ./MAKEDEV snd1 > > # play notify.wav > > play: /dev/dsp: Invalid argument > > > > Whats wrong? > > What's wrong is that you have _only_ tried using a single program to test your > audio system out. > > > Hmm... other programs (like wmsound from ports) also don't work... Rgdz, Sergey Osokin, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 22:29:32 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 5BF7914FF0 for ; Tue, 25 May 1999 22:29:16 -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.00 #1) id 10mWFb-000Lf8-00; Wed, 26 May 1999 07:29:11 +0200 From: Sheldon Hearn To: Sune Stjerneby Cc: current@FreeBSD.ORG Subject: Re: CCD and the new ATA/ATAPI subsystem? In-reply-to: Your message of "Tue, 25 May 1999 19:12:59 +0200." <19990525191258.B1642@hermes.koege-gym.dk> Date: Wed, 26 May 1999 07:29:11 +0200 Message-ID: <83273.927696551@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 May 1999 19:12:59 +0200, Sune Stjerneby wrote: > Am I correct in the assumption that CCD and the new ATA/ATAPI subsystem > is a bad combination? It won't let me configure ccd0 when using the adx > rather than wdx syntax.. Without getting into the ccd/vinum comparisons, is there a reason you want to use ad? and not wd? ? AFAIK, wd? works fine with Soren's new driver (well, it's working for me, at any rate). Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 22:34:20 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 7263C15068 for ; Tue, 25 May 1999 22:34:13 -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.00 #1) id 10mWKD-000Lgq-00; Wed, 26 May 1999 07:33:57 +0200 From: Sheldon Hearn To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: kvm_getswapinfo is broken In-reply-to: Your message of "Wed, 26 May 1999 09:08:11 +0400." <19990526090810.A23737@nagual.pp.ru> Date: Wed, 26 May 1999 07:33:57 +0200 Message-ID: <83379.927696837@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 May 1999 09:08:11 +0400, "Andrey A. Chernov" wrote: > Just check 'swapinfo' in recent -current, it shows "/dev/(null)" as swap > device, it means that devinfo() call in kvm_getswapinfo() returns NULL, > i.e. called with wrong argument which is swinfo.sw_dev Are you sure it isn't simply because kvm_getswapinfo is being asked for totals, and not per-device stats? i.e: Are you getting /dev/(null) for multiple swap devices? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 25 22:39: 0 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 B786D15224 for ; Tue, 25 May 1999 22:38:56 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id XAA08124; Tue, 25 May 1999 23:38:38 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905260538.XAA08124@panzer.plutotech.com> Subject: Re: kvm_getswapinfo is broken In-Reply-To: <83379.927696837@axl.noc.iafrica.com> from Sheldon Hearn at "May 26, 1999 07:33:57 am" To: sheldonh@uunet.co.za (Sheldon Hearn) Date: Tue, 25 May 1999 23:38:38 -0600 (MDT) Cc: ache@nagual.pp.ru (Andrey A. Chernov), 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 Sheldon Hearn wrote... > > > On Wed, 26 May 1999 09:08:11 +0400, "Andrey A. Chernov" wrote: > > > Just check 'swapinfo' in recent -current, it shows "/dev/(null)" as swap > > device, it means that devinfo() call in kvm_getswapinfo() returns NULL, > > i.e. called with wrong argument which is swinfo.sw_dev > > Are you sure it isn't simply because kvm_getswapinfo is being asked for > totals, and not per-device stats? i.e: Are you getting /dev/(null) for > multiple swap devices? {panzer:/usr/home/ken:2:0} pstat -s Device 1K-blocks Used Avail Capacity Type /dev/(null) 327552 0 327552 0% Interleaved /dev/(null) 393088 0 393088 0% Interleaved Total 720640 0 720640 0% That's with -current as of Friday. 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 May 25 22:42:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from deep-thought.demos.su (deep-thought.demos.su [194.87.1.76]) by hub.freebsd.org (Postfix) with ESMTP id E91651524D for ; Tue, 25 May 1999 22:42:26 -0700 (PDT) (envelope-from ache@deep-thought.demos.su) Received: (from ache@localhost) by deep-thought.demos.su (8.9.3/8.9.3) id JAA23915; Wed, 26 May 1999 09:42:16 +0400 (MSD) (envelope-from ache) Date: Wed, 26 May 1999 09:42:16 +0400 From: "Andrey A. Chernov" To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: kvm_getswapinfo is broken Message-ID: <19990526094215.A23880@nagual.pp.ru> References: <19990526090810.A23737@nagual.pp.ru> <83379.927696837@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <83379.927696837@axl.noc.iafrica.com>; from sheldonh@uunet.co.za on Wed, May 26, 1999 at 07:33:57AM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 26, 1999 at 07:33:57AM +0200, Sheldon Hearn wrote: > > > On Wed, 26 May 1999 09:08:11 +0400, "Andrey A. Chernov" wrote: > > > Just check 'swapinfo' in recent -current, it shows "/dev/(null)" as swap > > device, it means that devinfo() call in kvm_getswapinfo() returns NULL, > > i.e. called with wrong argument which is swinfo.sw_dev > > Are you sure it isn't simply because kvm_getswapinfo is being asked for > totals, and not per-device stats? i.e: Are you getting /dev/(null) for > multiple swap devices? I have only one swap device. I got line like this (tested on two -current machines): > swapinfo Device 1K-blocks Used Avail Capacity Type /dev/(null) 82800 6144 76656 7% Interleaved I.e. all other parameters here excepting device name are right. 'systat -swap' show the same picture, i.e. "(null" as device name. Yes I rebuild everything including /var/run/dev.db -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 0:23:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from chandra.eatell.msr.prug.or.jp (dhcp418.6bone.nec.co.jp [202.247.4.18]) by hub.freebsd.org (Postfix) with ESMTP id 0953715359 for ; Wed, 26 May 1999 00:23:23 -0700 (PDT) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id HAA27352; Wed, 26 May 1999 07:21:47 GMT Message-Id: <199905260721.HAA27352@chandra.eatell.msr.prug.or.jp> To: Sheldon Hearn Cc: Sune Stjerneby , current@FreeBSD.ORG Subject: Re: CCD and the new ATA/ATAPI subsystem? In-reply-to: Your message of "Wed, 26 May 1999 07:29:11 +0200." <83273.927696551@axl.noc.iafrica.com> Date: Wed, 26 May 1999 16:21:47 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Without getting into the ccd/vinum comparisons, is there a reason you > want to use ad? and not wd? ? AFAIK, wd? works fine with Soren's new > driver (well, it's working for me, at any rate). Soren's driver is alpha level, and danger with some chipset. For example, it cause file system crash with Opti Viper-M chipset. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 May 26 0:30:37 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 0D5371502A for ; Wed, 26 May 1999 00:30:33 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id CAA24452; Wed, 26 May 1999 02:30:10 -0500 (CDT) Date: Wed, 26 May 1999 02:30:10 -0500 From: "Matthew D. Fuller" To: "Kenneth D. Merry" Cc: Sheldon Hearn , "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: kvm_getswapinfo is broken Message-ID: <19990526023009.C6251@futuresouth.com> References: <83379.927696837@axl.noc.iafrica.com> <199905260538.XAA08124@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199905260538.XAA08124@panzer.plutotech.com>; from Kenneth D. Merry on Tue, May 25, 1999 at 11:38:38PM -0600 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 25, 1999 at 11:38:38PM -0600, a little birdie told me that Kenneth D. Merry remarked > > {panzer:/usr/home/ken:2:0} pstat -s > Device 1K-blocks Used Avail Capacity Type > /dev/(null) 327552 0 327552 0% Interleaved > /dev/(null) 393088 0 393088 0% Interleaved > Total 720640 0 720640 0% > > That's with -current as of Friday. In a -CURRENT as of early last week, I see the same: [2:28:11] mortis:~ (ttyp6):{106}% pstat -s Device 1024-blocks Used Avail Capacity Type /dev/(null) 655232 144 655088 0% Interleaved /dev/(null) 524160 196 523964 0% Interleaved /dev/(null) 130944 80 130864 0% Interleaved /dev/(null) 262016 56 261960 0% Interleaved /dev/(null) 524160 12 524148 0% Interleaved Total 2096512 488 2096024 0% It happened also through the buildworld before that one, which was a few days before, but not the one before that, which was about a week back (or something like that). A quick perusal of the code tells me absolutely nothing; at a guess, the kvm_read() is turning up nothing there, so I'll make a wild guess that something moved and forget to tell the post office to forward its references. -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller MF4839 http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 1:18:17 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 49A70154D2 for ; Wed, 26 May 1999 01:18:14 -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 JAA13510; Wed, 26 May 1999 09:18:03 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 26 May 1999 09:18:02 +0100 (BST) From: Doug Rabson To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@freebsd.org Subject: Re: Hacking objcopy In-Reply-To: <199905260307.LAA12331@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 On Wed, 26 May 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > Would anyone have any objections to me hacking objcopy so that it could do the > following - > > a) Change symbol names from one thing to another > > b) Add/remove dependencies on other shared objects. > > If I submit these changes, what chance do I have of getting them made > "official"? If the changes are modular enough so that it won't make life difficult merging new versions of binutils, then I don't mind committing such a thing. If you can get the binutils maintainers to take the change, that would be the best possible situation. -- 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 Wed May 26 1:39: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id DD77715351 for ; Wed, 26 May 1999 01:38:59 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup1-43.iptelecom.net.ua [212.42.68.170]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA12832; Wed, 26 May 1999 11:39:48 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id LAA52397; Wed, 26 May 1999 11:38:55 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <374BB31E.96E21EE5@altavista.net> Date: Wed, 26 May 1999 11:38:54 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: More compiler option comparisons References: <199905251635.MAA11353@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > Just for completeness, I did one final run of HINT with just `-O' > specified (our usual default).  `-O' results in significantly better > integer performance than `-O4'.  (Floating-point performance is just > the opposite.) > > This suggests that compiling the world with `-O' levels higher than > one is probably a bad idea.  (The generated assembly is identical from > `-O2' to `-O4'.)  The `-O2' code appears to be less efficient at > register allocation; about twice as much stack temporary space is > required. > > For the graph, see . As my own test shown hint reporded benchmarks depend highly on options used to compile libm, so to get more accurate results your must consider to make libm with the same options used to compile hint (probably better to make several static versions of hint executable linked with the corresponding libm). Also please report your processor model when reporting benchmarks result, because non-Intel processors (AMD for the example) can pepform better with 486 optimisation that with pentium optimisation) Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 1:39:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 8B54C15484 for ; Wed, 26 May 1999 01:38:58 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup1-43.iptelecom.net.ua [212.42.68.170]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA12827; Wed, 26 May 1999 11:39:45 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id LAA52393; Wed, 26 May 1999 11:38:53 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <374BA9CD.AC107917@altavista.net> Date: Wed, 26 May 1999 10:59:09 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: More compiler option comparisons References: <199905251635.MAA11353@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > Just for completeness, I did one final run of HINT with just `-O' > specified (our usual default).  `-O' results in significantly better > integer performance than `-O4'.  (Floating-point performance is just > the opposite.) > > This suggests that compiling the world with `-O' levels higher than > one is probably a bad idea.  (The generated assembly is identical from > `-O2' to `-O4'.)  The `-O2' code appears to be less efficient at > register allocation; about twice as much stack temporary space is > required. > > For the graph, see . As my own test shown hint reporded benchmarks depend highly on options used to compile libm, so to get more accurate results your must consider to make libm with the same options used to compile hint (probably better to make several static versions of hint executable linked with the corresponding libm). Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 3:49:12 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 0055715230 for ; Wed, 26 May 1999 03:49:10 -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 DAA16260 for ; Wed, 26 May 1999 03:50:22 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: FTP passive mode - a new default? Date: Wed, 26 May 1999 03:50:21 -0700 Message-ID: <16256.927715821@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unless I hear unanimous fierce outcry against it, I'm strongly considering making FTP_PASSIVE_MODE obsolete by virtue of being the default for all tools/libraries which currently examine it. FTP_ACTIVE_MODE will be the new flag for toggling the previous behavior. Given the state of the Internet today, I think this is purely a sensible change in defaults. Comments? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 4: 2:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 17FD81502A for ; Wed, 26 May 1999 04:02:16 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Wed, 26 May 1999 12:01:44 +0100 Received: from voodoo.pandhm.co.uk ([10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id L4VBJH8R; Wed, 26 May 1999 11:53:57 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10mbV3-000Mze-00; Wed, 26 May 1999 12:05:29 +0100 To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: FTP passive mode - a new default? X-Mailer: nmh-1.0 X-Colour: Green Organization: Palmer & Harvey McLane In-Reply-To: "Jordan K. Hubbard"'s message of "Wed, 26 May 1999 03:50:21 PDT" <16256.927715821@zippy.cdrom.com> Date: Wed, 26 May 1999 12:05:28 +0100 From: Dom Mitchell Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 May 1999, "Jordan K. Hubbard" proclaimed: > Unless I hear unanimous fierce outcry against it, I'm strongly > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > default for all tools/libraries which currently examine it. > FTP_ACTIVE_MODE will be the new flag for toggling the previous > behavior. > > Given the state of the Internet today, I think this is purely a > sensible change in defaults. Comments? Please do. However, a suitable notice must be plastered somewhere suitable (RELNOTES?). It might also be worth noting in ipfw(8). -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Value of 2 may go down as well as up" -- FORTRAN programmers manual -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 4:38:35 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 6B260151F1 for ; Wed, 26 May 1999 04:38:32 -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 NAA14580; Wed, 26 May 1999 13:38:24 +0200 (MET DST) Date: Wed, 26 May 1999 13:38:23 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? In-Reply-To: <16256.927715821@zippy.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 Is there a list of pro-/cons- available? - it is slower, but by how much and on which types of lines (low/high latency, low/high bandwidth)? - any (windows) tools not supporting it? Nick > Unless I hear unanimous fierce outcry against it, I'm strongly > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > default for all tools/libraries which currently examine it. > FTP_ACTIVE_MODE will be the new flag for toggling the previous > behavior. > > Given the state of the Internet today, I think this is purely a > sensible change in defaults. Comments? > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 4:42:52 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 641BD151F1 for ; Wed, 26 May 1999 04:42:47 -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 VAA38429; Wed, 26 May 1999 21:12:25 +0930 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 26 May 1999 21:12:24 +0930 (CST) From: "Daniel J. O'Connor" To: Nick Hibma Subject: Re: FTP passive mode - a new default? Cc: current@FreeBSD.ORG, "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26-May-99 Nick Hibma wrote: > Is there a list of pro-/cons- available? > > - it is slower, but by how much and on which types of lines (low/high > latency, low/high bandwidth)? > > - any (windows) tools not supporting it? Well funnily enough some servers won't allow passive mode, and I have seen a broken server/firewall combo which meant that passive ftp wouldn't work because the firewall denied the clients connection for passive mode (very duh). FTP passive mode works by getting the server to bind to a port and telling the client to connect to that to get/send the data, whereas normal ftp mode the client binds the port and the server connects to it. FreeBSD's ftpd allows you to specify a port range for passive ftp so you don't have to have your system wide open. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 4:49:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 1AECE14D76 for ; Wed, 26 May 1999 04:48:53 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Wed, 26 May 1999 13:51:34 +0200 Message-ID: <55586E7391ACD211B9730000C110027617961F@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Nick Hibma' , "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: RE: FTP passive mode - a new default? Date: Wed, 26 May 1999 13:46:33 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Nick Hibma [SMTP:nick.hibma@jrc.it] > Sent: Wednesday, May 26, 1999 1:38 PM > To: Jordan K. Hubbard > Cc: current@FreeBSD.ORG > Subject: Re: FTP passive mode - a new default? > > > Is there a list of pro-/cons- available? > > - it is slower, but by how much and on which types of lines (low/high > latency, low/high bandwidth)? [ML] same speed. passive means that the client (and not the server) opens the data connection. advantageous for people sitting behind packet or nat firewalls. > - any (windows) tools not supporting it? [ML] this is an ftp client request. some ancient ftp servers may not support passive data connections, but I haven't seen one of those in a long while. I don't know whether the windows ftpd is incapable of passive mode. actually, if the passive mode default is implemented correctly, the client should send PASV and if the server accepts it proceed, otherwise remain in active mode (and if you are behind a nat or a firewall you are no worse off than you already were). /Marino > Nick > > > Unless I hear unanimous fierce outcry against it, I'm strongly > > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > > default for all tools/libraries which currently examine it. > > FTP_ACTIVE_MODE will be the new flag for toggling the previous > > behavior. > > > > Given the state of the Internet today, I think this is purely a > > sensible change in defaults. Comments? > > > > - Jordan > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > -- > ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy > > > > 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 Wed May 26 5: 3:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from mnw.eas.slu.edu (mnw.eas.slu.edu [165.134.8.248]) by hub.freebsd.org (Postfix) with ESMTP id 7A5BA14D76 for ; Wed, 26 May 1999 05:03:17 -0700 (PDT) (envelope-from ejh@mnw.eas.slu.edu) Received: (from ejh@localhost) by mnw.eas.slu.edu (8.9.3/8.9.3) id HAA03513 for current@freebsd.org; Wed, 26 May 1999 07:03:15 -0500 (CDT) Date: Wed, 26 May 1999 07:03:15 -0500 (CDT) From: Eric Haug Message-Id: <199905261203.HAA03513@mnw.eas.slu.edu> To: current@freebsd.org Subject: process did not exit properly after kill signal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a pr440fx dual PPro system with 132Mb. I replaced memory and was testing memory with a short program (included below) and decided to try to kill it keyboard signals did change what the system was doing in that the swapping that was occurring stopped. kill -9 PID did not have the usual effect. But the process has not exited, the shell prompt has not returned. The system now is strangely sluggish. ps indicates that the pagedaemon is accumulating a lot of run time. the program is in DE+ state. top says it's STATE is objtrm. this is with FreeBSD 4.0-CURRENT of about Wed May 5 06:20 CDT I suppose this is some VM problem with cleaning up on program exit. Fixed since May 5 ??? eric haug Saint Louis Univ #define L 32 long j[L][1024][1024]; main() { int l,m,n,o; for(o=0; o<16;o++) for(l=0; l; Wed, 26 May 1999 07:26:21 -0700 (PDT) (envelope-from rjk@moran.grauel.com) Received: (from rjk@localhost) by moran.grauel.com (8.9.3/8.9.2) id JAA27843; Wed, 26 May 1999 09:26:44 -0500 (EST) (envelope-from rjk) From: Richard J Kuhns MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14156.1188.726396.700281@moran.grauel.com> Date: Wed, 26 May 1999 09:26:44 -0500 (EST) To: freebsd-current@freebsd.org Subject: PPP problem + mailing list archive problem X-Mailer: VM 6.71 under 21.1 "20 Minutes to Nikko" XEmacs Lucid (patch 2) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I'd hoped I'd be able to do a little more before bothering the list, but... I'd last built world around the end of April, with no problems. I then grew a fairly heavy workload, and so didn't get a chance to build world again until 2 days ago (May 24). During that time, something changed with ppp so it no longer works correctly for me (details shortly). ** I decided to check the -commit archives in case I missed an alert somewhere, and the database seems to be corrupted. Using netscape 4.5, I checked cvs-committers only, asked for articles on ppp sorted by date, and got a nice list. However, when I click on, say, 4.Brian Some cvs commit: src/usr.sbin/ppp arp.c defs.c iface.c ipcp.c tun.c Score: 711; Lines: 35; 26-Apr-1999; Archive: cvs-committers I get an article commenting on a commit to src/secure/usr.bin/bdes bdes.c. ** I normally start ppp with -auto XXX-pppd, with the following ppp.conf (I have a static IP address). # # Default setup. Executed always when PPP is invoked. # default: set log Phase Chat Connect LCP IPCP CCP TUN command set device /dev/cuaa0 set speed 57600 set ctsrts on set stopped 5 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATZ OK-AT-OK \\dATDT\\T TIMEOUT 40 CONNECT" # # XXX-pppd: allow user me set openmode passive set phone 123456 set login "TIMEOUT 5 login:-\\r-login: ppp word: xxxxxx set timeout 1200 set socket /var/tmp/internet "" deny lqr disable lqr delete all set ifaddr *myaddr* *hisaddr* add default HISADDR enable dns test-pppd: allow user me set openmode passive set phone 123456 set login "TIMEOUT 5 login:-\\r-login: ppp word: xxxxxx ################################################# I dial and login ok, but then nothing happens. the ppp.log says (normal successful login...) May 25 11:02:48 moran ppp[3577]: tun0: Phase: deflink: login -> lcp May 25 11:02:48 moran ppp[3577]: tun0: LCP: FSM: Using "deflink" as a transport May 25 11:02:48 moran ppp[3577]: tun0: LCP: deflink: State change Initial --> Closed May 25 11:02:48 moran ppp[3577]: tun0: LCP: deflink: State change Closed --> Stopped May 25 11:02:53 moran ppp[3577]: tun0: LCP: deflink: Stopped timer expired May 25 11:02:53 moran ppp[3577]: tun0: LCP: deflink: State change Stopped --> Closed May 25 11:02:53 moran ppp[3577]: tun0: LCP: deflink: State change Closed --> Initial May 25 11:03:01 moran ppp[3577]: tun0: Command: /dev/tty: down May 25 11:03:01 moran ppp[3577]: tun0: Phase: deflink: Disconnected! It sits at the "State change Closed --> Initial" until I tell it to disconnect or the idle time goes off. ps shows it waiting on "select". All the `p's in the pppctl/ppp prompt are lower case. Curiously enough, if I do everything manually, it works! Ie, I start ppp, set device, set speed, use "term" to talk directly to the modem, and ATDT123456 to dial and then login, I get the prompt almost immediately with all upper-case Ps, and I can then enter the commands to set address/routes and it works just fine. At this moment, I'm running a 3.1 binary from the CD; it works perfectly also. Did I miss something, or is this a genuine bug? I'll be happy to try other things/supply more info on request. Thanks... -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 7:54: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 3697B1550B; Wed, 26 May 1999 07:54:03 -0700 (PDT) From: "Jonathan M. Bresler" To: jkh@zippy.cdrom.com Cc: current@freebsd.org In-reply-to: <16256.927715821@zippy.cdrom.com> (jkh@zippy.cdrom.com) Subject: Re: FTP passive mode - a new default? Message-Id: <19990526145403.3697B1550B@hub.freebsd.org> Date: Wed, 26 May 1999 07:54:03 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Unless I hear unanimous fierce outcry against it, I'm strongly > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > default for all tools/libraries which currently examine it. > FTP_ACTIVE_MODE will be the new flag for toggling the previous > behavior. > > Given the state of the Internet today, I think this is purely a > sensible change in defaults. Comments? > so the difference between the current and proposed is: FTP_PASSIVE_MODE=YES vs FTP_ACTIVE_MODE=NO FTP_PASSIVE_MODE=NO vs FTP_ACTIVE_MODE=YES do any apps check for FTP_ACTIVE_MODE? are we going to apply patches to each app to check for this and maintains those patches over the course of time? seems to be a change without commensurate benefit.....it will confuse some, suprise others and doesnt seem to offer substantial benefit. recommend against the change. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 7:57:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id DE82E14D0C for ; Wed, 26 May 1999 07:57:02 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id KAA25282; Wed, 26 May 1999 10:56:56 -0400 (EDT) Date: Wed, 26 May 1999 10:51:08 -0400 (EDT) From: "Matthew N. Dodd" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? In-Reply-To: <16256.927715821@zippy.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 Wed, 26 May 1999, Jordan K. Hubbard wrote: > Unless I hear unanimous fierce outcry against it, I'm strongly > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > default for all tools/libraries which currently examine it. > FTP_ACTIVE_MODE will be the new flag for toggling the previous > behavior. > > Given the state of the Internet today, I think this is purely a > sensible change in defaults. Comments? Yay! -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 8:18:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id A7C03155E0 for ; Wed, 26 May 1999 08:18:41 -0700 (PDT) (envelope-from brian@keep.lan.Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id QAA79890; Wed, 26 May 1999 16:18:36 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id QAA02381; Wed, 26 May 1999 16:18:01 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199905261518.QAA02381@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Richard J Kuhns Cc: freebsd-current@freebsd.org Subject: Re: PPP problem + mailing list archive problem In-reply-to: Your message of "Wed, 26 May 1999 09:26:44 CDT." <14156.1188.726396.700281@moran.grauel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 May 1999 16:17:59 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I'd hoped I'd be able to do a little more before bothering the list, > but... > > I'd last built world around the end of April, with no problems. I then > grew a fairly heavy workload, and so didn't get a chance to build world > again until 2 days ago (May 24). During that time, something changed with > ppp so it no longer works correctly for me (details shortly). > [.....] > May 25 11:02:53 moran ppp[3577]: tun0: LCP: deflink: Stopped timer expired > May 25 11:02:53 moran ppp[3577]: tun0: LCP: deflink: State change Stopped --> Closed This happens because the peer hasn't said anything in the five seconds you've been connected (``set openmode passive'' says to wait for the peer to start talking and ``set stopped 5'' says to bring the layer down if we find ourselves in the STOPPED state for 5 seconds). Your login script looks suspect - it's always dangerous to have a login script that sends your password and waits for no confirmation of success (or failure). Isn't there something you can ``expect'' ? Try increasing your ``set stopped'' value to (say) 20 and see if that helps. [.....] > Thanks... > > -- > Richard Kuhns rjk@grauel.com > PO Box 6249 Tel: (765)477-6000 \ > 100 Sawmill Road x319 > Lafayette, IN 47903 (800)489-4891 / -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 9:25:18 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 82F3014F3A for ; Wed, 26 May 1999 09:25: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 JAA16132; Wed, 26 May 1999 09:47:59 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA21476; Wed, 26 May 1999 09:41:43 -0600 Date: Wed, 26 May 1999 09:41:43 -0600 Message-Id: <199905261541.JAA21476@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? In-Reply-To: <16256.927715821@zippy.cdrom.com> References: <16256.927715821@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 > Unless I hear unanimous fierce outcry against it, I'm strongly > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > default for all tools/libraries which currently examine it. > FTP_ACTIVE_MODE will be the new flag for toggling the previous > behavior. > > Given the state of the Internet today, I think this is purely a > sensible change in defaults. Comments? Gofer it! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 11:25:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta2-rme.xtra.co.nz (mta.xtra.co.nz [203.96.92.3]) by hub.freebsd.org (Postfix) with ESMTP id 1DF9015671 for ; Wed, 26 May 1999 11:25:41 -0700 (PDT) (envelope-from junkmale@pop3.xtra.co.nz) Received: from wocker ([210.55.152.128]) by mta2-rme.xtra.co.nz (InterMail v04.00.02.07 201-227-108) with SMTP id <19990526182800.EGOX7623210.mta2-rme@wocker> for ; Thu, 27 May 1999 06:28:00 +1200 From: "Dan Langille" Organization: The FreeBSD Diary To: current@freebsd.org Date: Thu, 27 May 1999 06:25:34 +1200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: FTP passive mode - a new default? Reply-To: junkmale@xtra.co.nz In-reply-to: <16256.927715821@zippy.cdrom.com> X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <19990526182800.EGOX7623210.mta2-rme@wocker> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 May 99, at 3:50, Jordan K. Hubbard wrote: > Unless I hear unanimous fierce outcry against it, I'm strongly > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > default for all tools/libraries which currently examine it. > FTP_ACTIVE_MODE will be the new flag for toggling the previous > behavior. > > Given the state of the Internet today, I think this is purely a > sensible change in defaults. Comments? It would surely simplify some things. If you are using a firewall, you'll need passive mode. If you're not using a firewall, passive mode won't bother you one bit. For the argument that some ftp servers don't accept passive mode, I say it's a question of numbers: which default setting will satisfy the greatest number of people? which setting will reduce the number of questions "how do I do X"? -- Dan Langille - DVL Software Limited The FreeBSD Diary - http://www.FreeBSDDiary.org/freebsd/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/racingsystem.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 14:10:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from caffeine.internal.enteract.com (caffeine.internal.enteract.com [207.229.129.24]) by hub.freebsd.org (Postfix) with SMTP id A167215786 for ; Wed, 26 May 1999 14:10:46 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 25843 invoked from network); 26 May 1999 21:10:46 -0000 Received: from shell-1.enteract.com (dscheidt@207.229.143.40) by caffeine.internal.enteract.com with SMTP; 26 May 1999 21:10:46 -0000 Received: from localhost (dscheidt@localhost) by shell-1.enteract.com (8.9.3/8.9.2) with SMTP id QAA25721 for ; Wed, 26 May 1999 16:10:46 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-1.enteract.com: dscheidt owned process doing -bs Date: Wed, 26 May 1999 16:10:46 -0500 (CDT) From: David Scheidt To: freebsd-current@freebsd.org Subject: moused broken? 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 My -CURRENT box is having problems with the mouse pointer freezing. Killing moused and restarting it seems to solve the problem, until it happens again, of course. It seems to happen after about 8 or nine hours of use. This hadn't been a problem with the previous -CURRENT, which was a month or so old. I am now running -CURRENT as of cvs-cur-5352, which is from sunday 23 May. I haven't seen anything in the commit logs that would indicate anything has changed that would break this. If it happens again, I shall see if I can get a better look at what happens. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 15:16:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (Postfix) with ESMTP id B806A14DF7 for ; Wed, 26 May 1999 15:16:06 -0700 (PDT) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id CAA22102; Thu, 27 May 1999 02:06:00 +0400 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.3/8.9.1) with ESMTP id CAA01936; Thu, 27 May 1999 02:09:14 +0400 (MSD) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199905262209.CAA01936@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: kvm_getswapinfo is broken In-reply-to: Your message of "Wed, 26 May 1999 09:08:11 +0400." <19990526090810.A23737@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 May 1999 02:09:14 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > Just check 'swapinfo' in recent -current, it shows "/dev/(null)" as swap > device, it means that devinfo() call in kvm_getswapinfo() returns NULL, > i.e. called with wrong argument which is swinfo.sw_dev This is a known problem. It is because dev_t in kernel and dev_t and userland are now different things. This is worse on the alpha, where they also have different sizes. So, on the alpha, the numbers are broken too, not just device names. Supposedly, it will be fixed by a junior kernel hacker. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 15:27:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mordred.cs.ucla.edu (Mordred.CS.UCLA.EDU [131.179.192.128]) by hub.freebsd.org (Postfix) with ESMTP id 62D9C14DF7 for ; Wed, 26 May 1999 15:27:56 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Received: from mordred.cs.ucla.edu (localhost [127.0.0.1]) by mordred.cs.ucla.edu (8.9.3/8.9.3) with ESMTP id PAA17737; Wed, 26 May 1999 15:27:52 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Message-Id: <199905262227.PAA17737@mordred.cs.ucla.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: "David Schwartz" Cc: current@freebsd.org Subject: Re: More compiler option comparisons In-Reply-To: Your message of "Tue, 25 May 1999 21:34:34 PDT." <000001bea731$0e713990$021d85d1@whenever.youwant.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 May 1999 15:27:52 -0700 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't recall that the FreeBSD version of egcs is built with Haifa turned on, which is supposed to improve optimizations as the level is increased (more aggressive instruction scheduling.) > With egcs, the '-O' flag doesn't specify the optimization level like it > does in GCC. It specifies the desired stability of the generated code. Lower > numbers (0,1,2) request higher stability. ;) > > DS > > > Dan Nelson wrote: > > > -O4 doesn't exist in egcs (or it didn't a month or so ago). According > > > to the source, -O2 enables all optimizations except -funroll-all-loops, > > > and all -O3 does is enable -funroll-all-loops. > > > > I think I recall reading somewhere that EGCS uses -O numbers > 3 to test > > experimental optimizations. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 16: 6:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from moran.grauel.com (moran.grauel.com [199.233.104.44]) by hub.freebsd.org (Postfix) with ESMTP id 578C614DE8 for ; Wed, 26 May 1999 16:06:33 -0700 (PDT) (envelope-from rjk@moran.grauel.com) Received: (from rjk@localhost) by moran.grauel.com (8.9.3/8.9.2) id SAA28685; Wed, 26 May 1999 18:04:42 -0500 (EST) (envelope-from rjk) From: Richard J Kuhns MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14156.32266.625134.89210@moran.grauel.com> Date: Wed, 26 May 1999 18:04:42 -0500 (EST) To: Brian Somers Cc: freebsd-current@freebsd.org Subject: Re: PPP problem + mailing list archive problem In-Reply-To: <199905261518.QAA02381@keep.lan.Awfulhak.org> References: <14156.1188.726396.700281@moran.grauel.com> <199905261518.QAA02381@keep.lan.Awfulhak.org> X-Mailer: VM 6.71 under 21.1 "20 Minutes to Nikko" XEmacs Lucid (patch 2) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers writes: > > Well, I'd hoped I'd be able to do a little more before bothering the list, > > but... > > > > I'd last built world around the end of April, with no problems. I then > > grew a fairly heavy workload, and so didn't get a chance to build world > > again until 2 days ago (May 24). During that time, something changed with > > ppp so it no longer works correctly for me (details shortly). > > > [.....] > > May 25 11:02:53 moran ppp[3577]: tun0: LCP: deflink: Stopped timer expired > > May 25 11:02:53 moran ppp[3577]: tun0: LCP: deflink: State change Stopped --> Closed > > This happens because the peer hasn't said anything in the five > seconds you've been connected (``set openmode passive'' says to wait > for the peer to start talking and ``set stopped 5'' says to bring the > layer down if we find ourselves in the STOPPED state for 5 seconds). > > Your login script looks suspect - it's always dangerous to have a > login script that sends your password and waits for no confirmation > of success (or failure). Isn't there something you can ``expect'' ? > > Try increasing your ``set stopped'' value to (say) 20 and see if that > helps. > > [.....] I raised my `set stopped' to 20; that just made it wait 20 seconds before it said `stopped timer expired' :-(. I removed the `set openmode passive' and got ############ May 26 17:49:59 moran ppp-4[28641]: tun0: LCP: FSM: Using "deflink" as a transpo rt May 26 17:49:59 moran ppp-4[28641]: tun0: LCP: deflink: State change Initial --> Closed May 26 17:49:59 moran ppp-4[28641]: tun0: LCP: deflink: State change Closed --> Stopped May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: deflink: LayerStart May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: deflink: SendConfigReq(1) state = Stopped May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: ACFCOMP[2] May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: PROTOCOMP[2] May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: ACCMAP[6] 0x00000000 May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: MRU[4] 1500 May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: MAGICNUM[6] 0x1f0d216b May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: deflink: State change Stopped --> Req-Sent May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: deflink: RecvConfigReq(1) state = Req-Sent May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: ACFCOMP[2] May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: PROTOCOMP[2] May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: ACCMAP[6] 0x00000000 May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: MRU[4] 1500 May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: MAGICNUM[6] 0x1f0d216b May 26 17:50:00 moran ppp-4[28641]: tun0: LCP: Magic is same (1f0d216b) - 1 time s May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: deflink: SendConfigNak(1) state = Req-Sent May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: MAGICNUM[6] 0x1f0d216b May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: deflink: RecvConfigNak(1) state = Req-Sent May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: MAGICNUM[6] 0x1f0d216b May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: Magic 0x1f0d216b is NAKed! May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: deflink: SendConfigReq(2) state = Req-Sent May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: ACFCOMP[2] May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: PROTOCOMP[2] May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: ACCMAP[6] 0x00000000 May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: MRU[4] 1500 May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: MAGICNUM[6] 0x38e4a5bd May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: deflink: RecvConfigReq(2) state = Req-Sent May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: ACFCOMP[2] May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: PROTOCOMP[2] May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: ACCMAP[6] 0x00000000 May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: MRU[4] 1500 May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: MAGICNUM[6] 0x38e4a5bd May 26 17:50:01 moran ppp-4[28641]: tun0: LCP: Magic is same (38e4a5bd) - 2 time s May 26 17:50:02 moran ppp-4[28641]: tun0: LCP: deflink: SendConfigNak(2) state = Req-Sent [...] May 26 17:50:50 moran ppp-4[28641]: tun0: LCP: ACFCOMP[2] May 26 17:50:50 moran ppp-4[28641]: tun0: LCP: PROTOCOMP[2] May 26 17:50:50 moran ppp-4[28641]: tun0: LCP: ACCMAP[6] 0x00000000 May 26 17:50:50 moran ppp-4[28641]: tun0: LCP: MRU[4] 1500 May 26 17:50:50 moran ppp-4[28641]: tun0: LCP: MAGICNUM[6] 0x534d1784 May 26 17:50:53 moran ppp-4[28641]: tun0: Phase: deflink: Too many LCP REQs sent - abandoning negotiation May 26 17:50:53 moran ppp-4[28641]: tun0: LCP: deflink: SendTerminateReq(13) sta te = Req-Sent May 26 17:50:53 moran ppp-4[28641]: tun0: LCP: deflink: State change Req-Sent -- > Closing May 26 17:50:56 moran ppp-4[28641]: tun0: LCP: deflink: SendTerminateReq(13) sta te = Closing ################ which didn't do much good. Finally, I told it to expect `Welcome' after logging in, and received the following -- note the extra `e' it says it's Expecting, which is definitely NOT in my ppp.conf file. I tried Expecting `Last' also, and it wanted to Expect `Lastt' and timed out again. ################ May 26 17:55:15 moran ppp-4[28664]: tun0: Chat: Received: Password: May 26 17:55:15 moran ppp-4[28664]: tun0: Chat: Send: xxxxxx^M May 26 17:55:15 moran ppp-4[28664]: tun0: Chat: Expect(5): Welcomee May 26 17:55:15 moran ppp-4[28664]: tun0: Chat: Received: ^M May 26 17:55:15 moran ppp-4[28664]: tun0: Chat: Received: Last login: Wed May 26 17:53:17 on ttyd0^M May 26 17:55:15 moran ppp-4[28664]: tun0: Chat: Received: FreeBSD 2.1-STABLE (WATSON) #0: Wed May 19 07:47:08 EST 1999^M May 26 17:55:15 moran ppp-4[28664]: tun0: Chat: Received: ^M May 26 17:55:15 moran ppp-4[28664]: tun0: Chat: Received: Welcome to FreeBSD!^M May 26 17:55:15 moran ppp-4[28664]: tun0: Chat: Received: ^M May 26 17:55:20 moran ppp-4[28664]: tun0: Chat: Expect timeout May 26 17:55:20 moran ppp-4[28664]: tun0: Warning: Chat script failed ################ Thanks again... -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 16:16:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 8BCBD14F0A for ; Wed, 26 May 1999 16:16:17 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.2) with ESMTP id SAA66601; Wed, 26 May 1999 18:16:07 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 26 May 1999 18:16:07 -0500 (CDT) From: Chris Dillon To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? In-Reply-To: <16256.927715821@zippy.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 Wed, 26 May 1999, Jordan K. Hubbard wrote: > Unless I hear unanimous fierce outcry against it, I'm strongly > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > default for all tools/libraries which currently examine it. > FTP_ACTIVE_MODE will be the new flag for toggling the previous > behavior. > > Given the state of the Internet today, I think this is purely a > sensible change in defaults. Comments? Wouldn't bother me a bit. I just set up a firewall and now need passive mode to do any FTPing to outside hosts. Passive shouldn't hurt people who don't have firewalls anyway, so go for it. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 19:17:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 18971157E3; Wed, 26 May 1999 19:17:25 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id EAA12492; Thu, 27 May 1999 04:17:21 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id EAA05431; Thu, 27 May 1999 04:17:20 +0200 (MET DST) Date: Thu, 27 May 1999 04:17:20 +0200 From: Eivind Eklund To: "Jonathan M. Bresler" Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? Message-ID: <19990527041720.I1444@bitbox.follo.net> References: <16256.927715821@zippy.cdrom.com> <19990526145403.3697B1550B@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990526145403.3697B1550B@hub.freebsd.org>; from Jonathan M. Bresler on Wed, May 26, 1999 at 07:54:03AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 26, 1999 at 07:54:03AM -0700, Jonathan M. Bresler wrote: > > > > Unless I hear unanimous fierce outcry against it, I'm strongly > > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > > default for all tools/libraries which currently examine it. > > FTP_ACTIVE_MODE will be the new flag for toggling the previous > > behavior. > > > > Given the state of the Internet today, I think this is purely a > > sensible change in defaults. Comments? > > > do any apps check for FTP_ACTIVE_MODE? > are we going to apply patches to each app to check for this > and maintains those patches over the course of time? > > seems to be a change without commensurate benefit.....it will > confuse some, suprise others and doesnt seem to offer > substantial benefit. It has the (large!) benefit of NATed[1] and firewalled users getting a working setup at once. I'm in favour. [1] Those using natd/ppp -alias will get this already, due to a protocol translator in libalias. Alas, this does not combine with firewalls on the NAT machine unless somebody choose to activate the code I added to libalias to punch 'holes' in ipfw. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 20: 5:28 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 6194014BDE; Wed, 26 May 1999 20:05:26 -0700 (PDT) From: "Jonathan M. Bresler" To: eivind@FreeBSD.ORG Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG In-reply-to: <19990527041720.I1444@bitbox.follo.net> (message from Eivind Eklund on Thu, 27 May 1999 04:17:20 +0200) Subject: Re: FTP passive mode - a new default? Message-Id: <19990527030526.6194014BDE@hub.freebsd.org> Date: Wed, 26 May 1999 20:05:26 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > do any apps check for FTP_ACTIVE_MODE? > > are we going to apply patches to each app to check for this > > and maintains those patches over the course of time? > > > > seems to be a change without commensurate benefit.....it will > > confuse some, suprise others and doesnt seem to offer > > substantial benefit. > > It has the (large!) benefit of NATed[1] and firewalled users getting a > working setup at once. I'm in favour. changing the default to FTP_PASSIVE_MODE=YES would accomplish the same thing, no? i agree that this is good. i disgree about changin the name of the knob to FTP_ACTIVE_MODE. jmb > > [1] Those using natd/ppp -alias will get this already, due to a > protocol translator in libalias. Alas, this does not combine with > firewalls on the NAT machine unless somebody choose to activate the > code I added to libalias to punch 'holes' in ipfw. > > Eivind. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 20:24: 2 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 E1DE014D85 for ; Wed, 26 May 1999 20:23:58 -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 XAA26718 for ; Wed, 26 May 1999 23:23:58 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA04379; Wed, 26 May 1999 23:23:28 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id XAA66917 for freebsd-current@freebsd.org; Wed, 26 May 1999 23:23:27 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199905270323.XAA66917@bb01f39.unx.sas.com> Subject: Re: cvs commit: src/sys/i386/isa ida.c To: freebsd-current@freebsd.org Date: Wed, 26 May 1999 23:23:27 -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 moving this to -current from -cvs which I beleive is more appropriate... >> Is this a driver for a RAID controller or something else? I'm just >> curious because on the Compaq servers I have there are some disk >> status lights (disk OK/online/failure, etc) on each individual >> hot-swap disk that operate under NT, but not under FreeBSD. Does this >> driver control that hardware monitoring feature on these servers >> (S.M.A.R.T. I would assume)? > >There is a standard for ``SCSI-Attached Fault-Tolerant Enclosures'' >(SAF-TE) which is implemented by some vendors. If an unknown >processor target shows up in your SCSI probe list, that's probably >what you have. I have several machines with two of them: > >pt0 at ahc0 bus 0 target 6 lun 0 >pt0: Fixed Processor SCSI-2 device >pt0: 3.300MB/s transfers >pt1 at ahc1 bus 0 target 6 lun 0 >pt1: Fixed Processor SCSI-2 device >pt1: 3.300MB/s transfers > >The way you recognize and talk to them is defined in a Microslop Word >document which you can find floating about under the name >`saftespec.zip'. I have/use Dell enclosures. These show-up at boot-time as: pass6 at ahc0 bus 0 target 6 lun 0 pass6: Fixed Processor SCSI-2 device pass6: 3.300MB/s transfers I was thinking about how I could talk to this unit so I could write a daemon to monitor all the drives for failures. If a drive fails, I'd like to automatically (somehow) swap to the spare drive and reconstruct. This sounds like a vinum subject (which I have not looked into at all yet). Has anyone actually worked on something like this? Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 20:50:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from ruby.bsdx.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 9F1E215152 for ; Wed, 26 May 1999 20:50:05 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by ruby.bsdx.net (8.9.3/8.9.1) with SMTP id XAA15591; Wed, 26 May 1999 23:50:03 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Wed, 26 May 1999 23:50:02 -0400 (EDT) From: Adam X-Sender: bsdx@ruby To: current@freebsd.org Cc: "Jordan K. Hubbard" Subject: Re: FTP passive mode - a new default? In-Reply-To: <199905261541.JAA21476@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 > > Unless I hear unanimous fierce outcry against it, I'm strongly > > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > > default for all tools/libraries which currently examine it. If they already examine FTP_PASSIVE_MODE, why not just set it to YES by default somewhere? > > FTP_ACTIVE_MODE will be the new flag for toggling the previous > > behavior. > > > > Given the state of the Internet today, I think this is purely a > > sensible change in defaults. Comments? > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 23: 0:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id D41F21533E for ; Wed, 26 May 1999 23:00:43 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA08379; Thu, 27 May 1999 08:00:42 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id IAA61109; Thu, 27 May 1999 08:00:40 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199905270600.IAA61109@greenpeace.grondar.za> To: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? Date: Thu, 27 May 1999 08:00:40 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 May 1999, Jordan K. Hubbard wrote: > Unless I hear unanimous fierce outcry against it, I'm strongly > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > default for all tools/libraries which currently examine it. > FTP_ACTIVE_MODE will be the new flag for toggling the previous > behavior. > > Given the state of the Internet today, I think this is purely a > sensible change in defaults. Comments? Very sensible. You have my vote. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 23:11:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta1-rme.xtra.co.nz (mta.xtra.co.nz [203.96.92.1]) by hub.freebsd.org (Postfix) with ESMTP id 7EED314F2C for ; Wed, 26 May 1999 23:11:09 -0700 (PDT) (envelope-from junkmale@pop3.xtra.co.nz) Received: from wocker ([210.55.152.128]) by mta1-rme.xtra.co.nz (InterMail v04.00.02.07 201-227-108) with SMTP id <19990527055617.VFKU7869945.mta1-rme@wocker> for ; Thu, 27 May 1999 17:56:17 +1200 From: "Dan Langille" Organization: The FreeBSD Diary To: current@freebsd.org Date: Thu, 27 May 1999 17:53:48 +1200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: FTP passive mode - a new default? Reply-To: junkmale@xtra.co.nz References: <199905261541.JAA21476@mt.sri.com> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <19990527055617.VFKU7869945.mta1-rme@wocker> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 May 99, at 23:50, Adam wrote: > > > Unless I hear unanimous fierce outcry against it, I'm strongly > > > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > > > default for all tools/libraries which currently examine it. > > If they already examine FTP_PASSIVE_MODE, why not just set it to YES by > default somewhere? That makes more sense to me than introducing a new flag. -- Dan Langille - DVL Software Limited The FreeBSD Diary - http://www.FreeBSDDiary.org/freebsd/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/racingsystem.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 26 23:26:20 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 8089D155C6 for ; Wed, 26 May 1999 23:26:19 -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 XAA57769; Wed, 26 May 1999 23:27:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: junkmale@xtra.co.nz Cc: current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? In-reply-to: Your message of "Thu, 27 May 1999 17:53:48 +1200." <19990527055617.VFKU7869945.mta1-rme@wocker> Date: Wed, 26 May 1999 23:27:24 -0700 Message-ID: <57765.927786444@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I could accept this as an alternative implementation, no problem. All I care about is the functionality, and I'd personally be happier not to have to document a new flag. :) I'll see what setting it in login.conf does - that *should* solve the problem swiftly and easily. - Jordan > On 26 May 99, at 23:50, Adam wrote: > > > > > Unless I hear unanimous fierce outcry against it, I'm strongly > > > > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > > > > default for all tools/libraries which currently examine it. > > > > If they already examine FTP_PASSIVE_MODE, why not just set it to YES by > > default somewhere? > > That makes more sense to me than introducing a new flag. > -- > Dan Langille - DVL Software Limited > The FreeBSD Diary - http://www.FreeBSDDiary.org/freebsd/ > NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ > The Racing System - http://www.racingsystem.com/racingsystem.htm > > > 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 Thu May 27 0:54: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from rossel.saarnet.de (rossel.saarnet.de [145.253.240.29]) by hub.freebsd.org (Postfix) with ESMTP id 52CDF1583A for ; Thu, 27 May 1999 00:53:57 -0700 (PDT) (envelope-from doehrm@aubi.de) Received: from igate.aubi.de (root@igate.aubi.de [145.253.242.249]) by rossel.saarnet.de (8.8.8/8.8.8) with ESMTP id KAA04714 for ; Thu, 27 May 1999 10:00:30 +0200 (MET DST) Received: from cisco.aubi.de (soraya.aubi.de [170.56.121.252]) by igate.aubi.de (8.9.1a/8.9.1) with ESMTP id JAA15457 for ; Thu, 27 May 1999 09:48:01 +0200 Received: from exchange.aubi.de (EXCHANGE.aubi.de [170.56.121.91]) by cisco.aubi.de (8.9.1/8.9.1) with ESMTP id KAA03995 for ; Thu, 27 May 1999 10:12:56 +0200 (CEST) Received: by EXCHANGE.aubi.de with Internet Mail Service (5.5.2232.9) id ; Thu, 27 May 1999 09:50:39 +0200 Message-ID: From: =?iso-8859-1?Q?Markus_D=F6hr?= To: "'freebsd-current@freebsd.org'" Subject: make world fails continously Date: Thu, 27 May 1999 09:50:37 +0200 Importance: high X-Priority: 1 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to recompile world, but since two weeks it fails continously = in vm/vnode_pager.h -> vm/vnode_pager.ph *** Error code 1 I read something about a "broken" perl in the list.=20 =3D=3D=3D> gnu/usr.bin/perl/utils/h2ph install -c -o root -g wheel -m 555 h2ph /usr/bin install -c -o root -g wheel -m 444 h2ph.1.gz /usr/share/man/man1 cd /usr/include; miniperl = /usr/obj/usr/src/gnu/usr.bin/perl/utils/h2ph/h2ph -d I re-cvsupped three times after deletion of the whole tree. Any ideas what's happening here? # uname -a FreeBSD beta.aubi.de 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Fri May 21 = 22:07:02 CES T 1999 root@beta.aubi.de:/usr/src/sys/compile/beta i386 -- Markus Doehr =20 IT Admin =20 AUBI Baubeschl=E4ge GmbH =20 Tel.: +49 6503 917 152 =20 Fax : +49 6503 917 190 =20 e-Mail: doehrm@aubi.de MD1139-RIPE =20 ************************* =20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 1:45:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id 4AC8D151CB for ; Thu, 27 May 1999 01:45:51 -0700 (PDT) (envelope-from brian@keep.lan.Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id JAA67459; Thu, 27 May 1999 09:45:50 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA00802; Thu, 27 May 1999 09:10:43 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199905270810.JAA00802@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Richard J Kuhns Cc: Brian Somers , freebsd-current@freebsd.org Subject: Re: PPP problem + mailing list archive problem In-reply-to: Your message of "Wed, 26 May 1999 18:04:42 CDT." <14156.32266.625134.89210@moran.grauel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 May 1999 09:10:43 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > I removed the `set openmode passive' and got [.....] How about ``set openmode active 5''. The problem you're seeing is that the other side is `reflecting' you data back because it hasn't yet turned ECHO off on the port. By the time the peer wakes up and does something, everything's hopelessly confused. > which didn't do much good. Finally, I told it to expect `Welcome' after > logging in, and received the following -- note the extra `e' it says it's > Expecting, which is definitely NOT in my ppp.conf file. I tried Expecting > `Last' also, and it wanted to Expect `Lastt' and timed out again. [.....] Can you send me an exact copy of your ``set login'' line ? Also, what does ``show version'' in ppp say ? Are you running the latest version ? Cheers. > -- > Richard Kuhns rjk@grauel.com > PO Box 6249 Tel: (765)477-6000 \ > 100 Sawmill Road x319 > Lafayette, IN 47903 (800)489-4891 / -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 4: 5:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id BB42214C58 for ; Thu, 27 May 1999 04:00:16 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup1-44.iptelecom.net.ua [212.42.68.171]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA18093 for ; Thu, 27 May 1999 13:57:53 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id NAA57516 for ; Thu, 27 May 1999 13:56:48 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <374D24F0.3C9748A5@altavista.net> Date: Thu, 27 May 1999 13:56:48 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: current@freebsd.org Subject: Today world breakage. Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make world broken (sources cvsup'ed several hours ago) ===> sys/modules/vn make: don't know how to make /usr/src/sys/modules/vn/vn.h. Stop Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 5:51:34 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 D247515705; Thu, 27 May 1999 05:51:28 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:syKPN4lfCMi7mKPwpqdQRhkFF6XSyb8W@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id VAA13850; Thu, 27 May 1999 21:51:35 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id VAA25360; Thu, 27 May 1999 21:55:26 +0900 (JST) Message-Id: <199905271255.VAA25360@zodiac.mech.utsunomiya-u.ac.jp> To: sos@freebsd.org, dfr@freebsd.org, kato@freebsd.org, des@freebsd.org Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: syscons update - stage 2 snopshot 27 May Date: Thu, 27 May 1999 21:55:26 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is the third, and hopefully the last, snapshot of the stage 2 of syscons update. I placed a set of patches in http://www.freebsd.org/~yokota/syscons-update.27May.tar.gz This tar file includes patches for all architectures (i386, alpha, PC98), and minor modifications for screen savers and splash screen decoders. I would appreciate if you take a look and send me some comments. I intend to commit these changes to the source tree in the next week or so. I am attaching the README file from the tar file. Kazu ---------------------------------------------------------------------- Latest syscons update 28 May 1999 Kazutaka YOKOTA, yokota@FreeBSD.ORG 1. Introduction This is a snapshot of work-in-progress. I decided to release this because I am very much behind intended schedule and think it won't benefit us much if I will defer submitting this for public testing until everything is done. This update is still in the middle of active development and is incomplete yet. The main goal of this update is to split syscons source code into manageable chunks and in the process, reorganize some of complicated functions. It also includes some ideas and patches which were submitted to the FreeBSD PR database in the past and have not been integrated into syscons. A bunch of new ioctl commands are also added to syscons and the video driver in order to provide support for accessing frame buffer memory. The snapshot also includes a copy of (unfinished) text and some sample code to demonstrate video memory access by the userland program. 2. Applying patch files. There are 13 separate patch files and tar files: alpha.diff alpha-specific patch. devfb.diff Video driver patch. devfb.tar New video driver files. i386.diff i386-specific patch. sys.diff Patch for common kernel files. sys.tar New files in /sys/sys syscons.tar Updated and new syscons source files. pc98.diff Patch for the PC98 architecture syscons-pc98.tar Updated and new syscons source files for PC98 kbdcontrol.diff Patch for kbdcontrol. vidcontrol.diff Patch for vidcontrol. saver.diff Patch for screen saver KLDs. splash.diff Patch for splash screen KLDs. They are relative to 4.0-CURRENT around 26 May 1999. They update and overwrite quite a few files. Please make backup first! Affected files are: alpha.diff /sys/alpha/alpha/cons.c /sys/alpha/conf/files.alpha /sys/alpha/conf/options.alpha /sys/alpha/include/cons.h /sys/alpha/include/console.h devfb.diff /sys/dev/fb/fb.c /sys/dev/fb/fbreg.c /sys/dev/fb/splash.c /sys/dev/fb/splashreg.c /sys/dev/fb/vgareg.c devfb.tar /sys/dev/fb/vga.c NEW FILE syscons.tar /sys/dev/syscons/syscons.c /sys/dev/syscons/syscons.h /sys/dev/syscons/scvidctl.c /sys/dev/syscons/scvesactl.c /sys/dev/syscons/schistory.c NEW FILE /sys/dev/syscons/scmouse.c NEW FILE /sys/dev/syscons/scvgarndr.c NEW FILE /sys/dev/syscons/scvtb.c NEW FILE i386.diff /sys/i386/conf/LINT /sys/i386/conf/files.i386 /sys/i386/conf/options.i386 /sys/i386/i386/cons.c /sys/i386/i386/cons.h /sys/i386/isa/pcvt/pcvt_drv.c /sys/i386/isa/vesa.c /sys/i386/include/console.h sys.diff /sys/isa/sio.c /sys/isa/syscons_isa.c /sys/isa/vga_isa.c /sys/sys/fbio.h sys.tar /sys/sys/kbio.h NEW FILE /sys/sys/consio.h NEW FILE vidcontrol.diff /usr/src/usr.sbin/vidcontrol/vidcontrol.c kbdcontrol.diff /usr/src/usr.sbin/kbdcontrol/lex.h /usr/src/usr.sbin/kbdcontrol/lex.l /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c pc98.diff /sys/pc98/pc98/pc98gdc.c /sys/pc98/pc98/sio.c /sys/pc98/conf/files.pc98 /sys/pc98/conf/options.pc98 syscons-pc98.tar /sys/pc98/pc98/syscons.c /sys/pc98/pc98/syscons_pc98.c NEW FILE /sys/pc98/pc98/sc_machdep.h NEW FILE /sys/pc98/pc98/scgdcrndr.c NEW FILE /sys/pc98/pc98/scvtbpc98.c NEW FILE saver.diff /sys/modules/syscons/* splash.diff /sys/modules/splash/* Apply them as follows (assuming they are in /tmp): cd /sys patch < /tmp/sys.diff tar xvf /tmp/sys.tar cd i386 patch < /tmp/i386.diff cd ../alpha patch < /tmp/alpha.diff cd ../pc98 patch < /tmp/pc98.diff cd pc98 tar xvf /tmp/syscons-pc98.tar cd ../../dev/fb patch < /tmp/devfb.diff tar xvf /tmp/devfb.tar cd ../syscons tar xvf /tmp/syscons.tar cd /usr/src/usr.sbin/vidcontrol patch < /tmp/vidcontrol.diff cd ../kbdcontrol patch < /tmp/kbdcontrol.diff cd /sys/modules/syscons patch < /tmp/saver.diff cd ../splash patch < /tmp/splash.diff Then, before you rebuild vidcontrol and kbdcontrol, cp /sys/`uname -m`/include/console.h /usr/include/machine 3. Rough descriptions on modifications 1) Syscons update: - Many static variables are moved to the softc structure. - History buffer (back-scroll buffer) management functions are moved to a new file, schistory.c. - Sysmouse management functions are moved to a new file, scmouse.c. - Created a set of functions to access the virtual terminal buffer (scvtb.c). - Added a new key function, PREV. When this key is pressed, the vty immediately before the current vty will become foreground. Analogue to PREV, which is usually assigned to the PrntScrn key. PR: kern/10113 Submitted by: Christian Weisgerber - Added a new ioctl: VT_GETINDEX. - Modified the console input function sccngetc() so that it handles function keys properly. - Reorganized the screen update routine. - Rendering functions (scvgarndr.c). - VT switching code is reorganized. It now should be slightly more robust than before. - Added the DEVICE_RESUME function so that syscons no longer hooks the APM resume event directly. - New kernel configuration options: options SC_NO_CUTPASTE options SC_NO_FONT_LOADING options SC_NO_HISTORY options SC_NO_SYSMOUSE Various parts of syscons can be omitted so that the kernel size is reduced. Use the above kernel configuration options to selectively disable parts of syscons. options SC_PIXEL_MODE Made the VESA 800x600 mode an option, rather than a standard part of syscons. This mode is useful on some laptop computers, but less so on most other systems, and it adds substantial amount of code to syscons. If the above kernel configuration option is NOT defined, you can reduce the kernel size a lot. options SC_DISABLE_DDBKEY Disables the `debug' key combination. It will prevent the user from entering DDB by pressing the key combination. DDB will still be invoked when the kernel panics or hits a break point if it is included in the kernel. options SC_ALT_MOUSE_IMAGE Inverse the character cell at the mouse cursor position in the text console, rather than drawing an arrow on the screen. This will reduce the system load a lot. Submitted by: Nick Hibma (n_hibma@FreeBSD.ORG) options SC_DFLT_FONT makeoptions "SC_DFLT_FONT=_font_name_" Include the named font as the default font of syscons. Available fonts are: iso, iso2, koi8-r, cp437, cp850, cp865 and cp866. 16- line, 14-line and 8-line font data will be compiled in. This option will replace the existing STD8X16FONT option, which loads 16- line font data only. 2) Video driver update: - The VGA driver is split into /sys/dev/fb/vga.c and /sys/isa/vga_isa.c. - The video driver provides a set of ioctl commands to manipulate the frame buffer. - New kernel configuration options: options "VGA_WIDTH90" Enables 90 column modes: 90x25, 90x30, 90x43, 90x50, 90x60. These modes are mot always supported by the video card. PR: i386/7510 Submitted by: kbyanc@freedomnet.com and alexv@sui.gda.itesm.mx. 3) Other changes - The header file machine/console.h is reorganized; it has been placed in the architecture-dependent part of the source tree while much of the stuff is architecture-neutral. Its contents is now split into sys/fbio.h, sys/kbio.h (a new file) and sys/consio.h (another new file). machine/console.h is still maintained for compatibility reasons; it simply includes the above three files (strange arrangement indeed that a machine dependent header file is including architecture-neutral headers! but...). - Kernel console selection/installation routines are fixed and slightly rebumped so that it should now be possible to switch between the interanl kernel console (sc or vt) and a remote kernel console (sio) again, as it was in 2.x, 3.0 and 3.1. - Screen savers and splash screen decoders Because of the header file reorganization described above, screen savers and splash screen decoders are slightly modified. After this update, /sys/modules/syscons/saver.h is no longer necessary and is deprecated. Text screen savers are modified to use virtual terminal buffer manipulation functions in scvtb.c; they no longer directly poke into the buffer. There is no functional changes in the screen savers and the splash screen decoders after these changes. ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 7:12:59 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 E6BDF14D04 for ; Thu, 27 May 1999 07:12:38 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:OsM0+HRksPSEb2n7aGrK17vyrEb/g2D+@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id XAA14128; Thu, 27 May 1999 23:12:43 +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 XAA26529; Thu, 27 May 1999 23:16:34 +0900 (JST) Message-Id: <199905271416.XAA26529@zodiac.mech.utsunomiya-u.ac.jp> To: David Scheidt Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: moused broken? In-reply-to: Your message of "Wed, 26 May 1999 16:10:46 EST." References: Date: Thu, 27 May 1999 23:16:34 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >My -CURRENT box is having problems with the mouse pointer freezing. Killing >moused and restarting it seems to solve the problem, until it happens again, >of course. It seems to happen after about 8 or nine hours of use. This >hadn't been a problem with the previous -CURRENT, which was a month or so >old. I am now running -CURRENT as of cvs-cur-5352, which is from sunday 23 >May. I haven't seen anything in the commit logs that would indicate >anything has changed that would break this. If it happens again, I shall >see if I can get a better look at what happens. It is a PS/2 mouse or a serial mouse? What model is it? 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 Thu May 27 7:47:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 500E51530C for ; Thu, 27 May 1999 07:47:33 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id JAA04258 for current@freebsd.org; Thu, 27 May 1999 09:47:28 -0500 (CDT) From: Kevin Day Message-Id: <199905271447.JAA04258@home.dragondata.com> Subject: -Current still leaking mbuf's To: current@freebsd.org Date: Thu, 27 May 1999 09:47:27 -0500 (CDT) 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 I've got two systems that panic about every 48 hours, saying they're out of mbuf's. I've tried raising maxusers. (It's at 128 now, but i've gone up to 256 and still seen the same thing). I believe it's a leak, since it's pretty consistant how long it will stay up before it runs out. I've tried raising NBMCLUSTERs, but this just seems to prolong it before it finally panic's. The only unusual thing about these two machines are that they're very heavy NFS client users. Is there anything any of you would like to see, if someone's willing to try to debug this? vmstat -m doesn't show anything too out of the ordinary, but I've got several coredumps waiting. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 7:56: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from caffeine.internal.enteract.com (caffeine.internal.enteract.com [207.229.129.24]) by hub.freebsd.org (Postfix) with SMTP id 7422B156D3 for ; Thu, 27 May 1999 07:55:58 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 11465 invoked from network); 27 May 1999 14:55:57 -0000 Received: from shell-1.enteract.com (dscheidt@207.229.143.40) by caffeine.internal.enteract.com with SMTP; 27 May 1999 14:55:57 -0000 Received: from localhost (dscheidt@localhost) by shell-1.enteract.com (8.9.3/8.9.2) with SMTP id JAA30576; Thu, 27 May 1999 09:55:57 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-1.enteract.com: dscheidt owned process doing -bs Date: Thu, 27 May 1999 09:55:56 -0500 (CDT) From: David Scheidt To: Kazutaka YOKOTA Cc: freebsd-current@freebsd.org Subject: Re: moused broken? In-Reply-To: <199905271416.XAA26529@zodiac.mech.utsunomiya-u.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 Thu, 27 May 1999, Kazutaka YOKOTA wrote: > It is a PS/2 mouse or a serial mouse? What model is it? > Sorry. It is a three button PS/2 mouse, an AT&T 320. I think it is really a Logitech mouse in Deathstar clothing. From dmesg: May 24 13:59:31 rally3 /kernel: psm0: irq 12 on atkbdc0 May 24 13:59:31 rally3 /kernel: psm0: model Generic PS/2 mouse, device ID 0 I never had a problem with the mouse under 2.2.8, 3.x, or NT. (I really like these mice: 3m cords). I also found the following lines in syslog: May 25 15:33:34 rally3 /kernel: psmintr: out of sync (0080 != 0000). David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 8:17:57 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 B6D34158D9 for ; Thu, 27 May 1999 08:17:48 -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 LAA19291; Thu, 27 May 1999 11:17:46 -0400 (EDT) (envelope-from wollman) Date: Thu, 27 May 1999 11:17:46 -0400 (EDT) From: Garrett Wollman Message-Id: <199905271517.LAA19291@khavrinen.lcs.mit.edu> To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/isa ida.c In-Reply-To: <199905270323.XAA66917@bb01f39.unx.sas.com> References: <199905270323.XAA66917@bb01f39.unx.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I have/use Dell enclosures. These show-up at boot-time as: > pass6 at ahc0 bus 0 target 6 lun 0 > pass6: Fixed Processor SCSI-2 device > pass6: 3.300MB/s transfers If they implement the SAF-TE standard, then they will return 50 bytes of inquire data; after the usual SCSI standard data comes the string `SAF-TE'. Here is an example, using the old `libscsi' interface and some appropriate structure definitions: static int is_safte(int fd, struct hsbp *hs) { int i; char *cp; struct scsireq req; struct inquire_response resp; struct encl_config encl; struct hsbp_info *info = &hs->info; scsireq_reset(&req); scsireq_build(&req, sizeof resp, (char *)&resp, SCCMD_READ, "12 v:b3 0:b5 0 0 v 0", (int)info->hi_sc_lun, (int)sizeof resp); scsireq_enter(fd, &req); /* * If we had an error this early, we can't possibly work with this * device. Also return false if we didn't get enough data back * to be a valid SAF-TE response. */ if (SCSIREQ_ERROR((&req)) || req.datalen_used < sizeof resp) return 0; if (strncmp(resp.safte_id, "SAF-TE", 6) != 0) return 0; if (strncmp(resp.safte_rev, "1.0", 3) != 0) return 0; info->hi_type = HSBP_TYPE_SAFTE_1; /* * Format the enclosure ID as something human-readable. */ for (i = 0, cp = info->hi_serial; i < sizeof(resp.encl_id); i++, cp += 2) { snprintf(cp, 2, "%02x", (u_int)resp.encl_id[i] & 0xff); } /* * Copy the other INQUIRE information into the standard * format. */ #define TRIM(field) \ do { cp = &field[(sizeof field) - 1]; \ while (cp > field && *cp == ' ') { \ *cp-- = '\0'; \ } \ } while(0) TRIM(resp.vendor); TRIM(resp.product); TRIM(resp.firmware); #undef TRIM info->hi_vendor[0] = info->hi_model[0] = info->hi_swrev[0] = '\0'; strncat(info->hi_vendor, resp.vendor, sizeof resp.vendor); strncat(info->hi_model, resp.product, sizeof resp.product); strncat(info->hi_swrev, resp.firmware, sizeof resp.firmware); if (safte_read_buffer(fd, info->hi_sc_lun, SAFTE_BUF_ENCL_CONFIG, sizeof encl, &encl) < sizeof encl) { warnx("/dev/pt%d did not accept Read Enclosure Configuration", info->hi_pt_unit); return 0; } info->hi_nslots = encl.nslots; info->hi_nfans = encl.nfans; info->hi_nps = encl.npower; info->hi_ntemps = encl.ntemps; info->hi_haslock = encl.haslock; info->hi_hasspkr = encl.hasspkr; hs->u.safte.statuslen = encl.nfans + encl.npower + encl.nslots + 2 + encl.ntemps + 2; hs->u.safte.status = malloc(hs->u.safte.statuslen); if (hs->u.safte.status == 0) err(EX_OSERR, "malloc(%lu)", (u_long)hs->u.safte.statuslen); hs->u.safte.slotstatus = malloc(4 * encl.nslots); if (hs->u.safte.slotstatus == 0) err(EX_OSERR, "malloc(%d)", 4 * encl.nslots); hs->u.safte.oslotstatus = malloc(4 * encl.nslots); if (hs->u.safte.oslotstatus == 0) err(EX_OSERR, "malloc(%d)", 4 * encl.nslots); hs->u.safte.psstatus = hs->u.safte.status + encl.nfans; hs->u.safte.slotids = hs->u.safte.psstatus + encl.npower; hs->u.safte.lockstatus = hs->u.safte.slotids + encl.nslots; hs->u.safte.spkrstatus = hs->u.safte.lockstatus + 1; hs->u.safte.temps = hs->u.safte.spkrstatus + 1; hs->u.safte.tempalarms = hs->u.safte.temps + encl.ntemps; if (safte_read_buffer(fd, info->hi_sc_lun, SAFTE_BUF_ENCL_STATUS, hs->u.safte.statuslen, hs->u.safte.status) < (int)hs->u.safte.statuslen) { warnx("/dev/pt%d did not accept Read Enclosure Status", info->hi_pt_unit); free(hs->u.safte.status); free(hs->u.safte.slotstatus); hs->u.safte.status = 0; hs->u.safte.statuslen = 0; return 0; } /* * Build the SCSI unit number map. * The specification has the bug that, when no device is installed, * the unit might be specified as 255 (meaning ``none''). */ for (i = 0; i < 16; i++) info->hi_slotunit[i] = -1; for (cp = hs->u.safte.slotids, i = 0; i < encl.nslots; i++) { if (cp[i] < 16) info->hi_slotunit[(u_char)cp[i]] = i; } if (safte_read_buffer(fd, info->hi_sc_lun, SAFTE_BUF_SLOT_STATUS, 4 * encl.nslots, hs->u.safte.slotstatus) < 4 * encl.nslots) { warnx("/dev/pt%d did not accept Read Device Slot Status", info->hi_pt_unit); free(hs->u.safte.status); free(hs->u.safte.slotstatus); return 0; } memcpy(hs->u.safte.oslotstatus, hs->u.safte.slotstatus, 4 * encl.nslots); memset(hs->u.safte.cmdbytes, 0, sizeof hs->u.safte.cmdbytes); hs->u.safte.cmdbytes[0] = SAFTE_WRT_GLOBAL_CMD; return 1; } -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 Thu May 27 10:55: 8 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 835D614F99 for ; Thu, 27 May 1999 10:55:05 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA02337; Thu, 27 May 1999 10:53:49 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 27 May 1999 10:53:48 -0700 (PDT) From: Doug White To: oZZ!!! Cc: Brian Feldman , W Gerald Hicks , Marc van Woerkom , hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: No sound (Ensoniq Audio PCI 1370) 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, 26 May 1999, oZZ!!! wrote: > > What's wrong is that you have _only_ tried using a single program to test your > > audio system out. > > > > > > Hmm... other programs (like wmsound from ports) also don't work... What about cat /bin/cat > /dev/audio ? 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 Thu May 27 10:56: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id C383315935 for ; Thu, 27 May 1999 10:56:00 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id MAA03552 for ; Thu, 27 May 1999 12:55:56 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id MAA04543; Thu, 27 May 1999 12:55:55 -0500 Message-ID: <19990527125555.63299@right.PCS> Date: Thu, 27 May 1999 12:55:55 -0500 From: Jonathan Lemon To: current@freebsd.org Subject: Request for testers; removing VM86 as an option. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a patch that reworks the memory calculation at bootup, and correctly obtains the physical memory map from the BIOS using the INT 15, AX=E820 call. This should allow correct operation on machines which reserve certain segments of memory for non-OS use (ThinkPads). It can also preserve the ACPI tables for later use. If 15/E820 is not supported, various other methods are tried, including falling back to the current scheme of speculative probing. I'd like some testers (preferrably a ThinkPad user with > 64M of memory) to try this out and see if it correctly detects all usable memory; and also if the system boots without needing to specify MAXMEM (or npx0 size). If it works, great. If not, boot with `-v', and send me back the SMAP lines from the dmesg output. Barring any serious objections(*), I'd like to merge this into -current, and then `unifdef -DVM86' to make it mandatory. There appears to be no other reliable way to detect > 64M of memory on modern PC hardware. PC98 developers - this should actually simplify things, as it moves the memory calculations into their own routine. The -current patch is ftp://sumatra.americantv.com/pub/memsize.patch There is a bootable -stable picobsd floppy too, for those who don't want to compile a kernel: ftp://sumatra.americantv.com/pub/picobsd.bin -- Jonathan (*) I don't consider FBSDBOOT.EXE a serious objection; it may or may not have worked before, and it may or may not work now. (As discussed to death on earlier threads on this list). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 11: 7:41 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 831B314F99 for ; Thu, 27 May 1999 11:07:35 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA07409; Thu, 27 May 1999 11:07:27 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 27 May 1999 11:07:24 -0700 (PDT) From: Doug White To: "Jordan K. Hubbard" Cc: junkmale@xtra.co.nz, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? In-Reply-To: <57765.927786444@zippy.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 Wed, 26 May 1999, Jordan K. Hubbard wrote: > I could accept this as an alternative implementation, no problem. All > I care about is the functionality, and I'd personally be happier not > to have to document a new flag. :) > > I'll see what setting it in login.conf does - that *should* solve the > problem swiftly and easily. I second the suggestion to 'autoprobe' PASV support, and revert to active mode (w/ an appropriate msg) if PASV is refused. Also, please preserve the -[pP] flag, even if it's noop'd. Just covering bases. :) 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 Thu May 27 11:12:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id ED5691592A for ; Thu, 27 May 1999 11:12:38 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (unknown [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 132E5C7; Thu, 27 May 1999 18:12:35 +0000 (GMT) Date: Thu, 27 May 1999 22:12:35 +0400 (MSD) From: oZZ!!! To: Doug White Cc: Brian Feldman , W Gerald Hicks , Marc van Woerkom , hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: No sound (Ensoniq Audio PCI 1370) 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 Thu, 27 May 1999, Doug White wrote: > On Wed, 26 May 1999, oZZ!!! wrote: > > > > What's wrong is that you have _only_ tried using a single program to test your > > > audio system out. > > > > > > > > > Hmm... other programs (like wmsound from ports) also don't work... > > What about > > cat /bin/cat > /dev/audio > pcm don't work correct in -current... wmsound with my card too can't work correct. SB 128 PCI its a PCI-device & (as i known) it must be detect as es0 + pcm1 (not pcm0), because pcm0 reserved for ISA-device (right?). Kernel at boot-time detect my SB 128 PCI as es0 + pcm0... Rgdz, Sergey Osokin aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 11:15:14 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 AA55615932 for ; Thu, 27 May 1999 11:15:11 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA09515; Thu, 27 May 1999 11:15:01 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 27 May 1999 11:14:59 -0700 (PDT) From: Doug White To: Eric Haug Cc: current@FreeBSD.ORG Subject: Re: process did not exit properly after kill signal In-Reply-To: <199905261203.HAA03513@mnw.eas.slu.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 On Wed, 26 May 1999, Eric Haug wrote: > Hi, > I have a pr440fx dual PPro system with 132Mb. > I replaced memory and was testing memory with a short program > (included below) and decided to try to kill it > keyboard signals did change what the system was doing > in that the swapping that was occurring stopped. > kill -9 PID did not have the usual effect. > #define L 32 > > long j[L][1024][1024]; Hm... a long is 4 bytes, right? So if I'm doing my math right, you issued a request for 128MB of RAM with this declaration, then touched each page. This means that the VM system has to allocate space for all that. This is hammering your swap more than your memory. :) The kernel will complete the alloc request (and subsequent VM ops) then kill the program, then swap everything back in. It should clear after it gets done swapping. For a more effective memory test, try 'make -j8 world' a few times in parallel. 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 Thu May 27 11:29:42 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 164DA14BCF for ; Thu, 27 May 1999 11:29:39 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA14859; Thu, 27 May 1999 11:29:28 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 27 May 1999 11:29:27 -0700 (PDT) From: Doug White To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: -Current still leaking mbuf's In-Reply-To: <199905271447.JAA04258@home.dragondata.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, 27 May 1999, Kevin Day wrote: > I've got two systems that panic about every 48 hours, saying they're out of > mbuf's. I've tried raising maxusers. (It's at 128 now, but i've gone up to > 256 and still seen the same thing). > > I believe it's a leak, since it's pretty consistant how long it will stay up > before it runs out. > > I've tried raising NBMCLUSTERs, but this just seems to prolong it before it > finally panic's. How high do you have it set? You might want to collect some netstat -m stats as time goes on. In addition to being easier to read, it may give you some hints as to how high you want to go with mbuf clusters. You can crank them pretty high if you're on 3.2 or later. > The only unusual thing about these two machines are that they're very heavy > NFS client users. That might do it by itself irrespective of any bugs. 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 Thu May 27 11:47:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 2912715991 for ; Thu, 27 May 1999 11:47:18 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id NAA18802; Thu, 27 May 1999 13:47:09 -0500 (CDT) From: Kevin Day Message-Id: <199905271847.NAA18802@home.dragondata.com> Subject: Re: -Current still leaking mbuf's In-Reply-To: from Doug White at "May 27, 1999 11:29:27 am" To: dwhite@resnet.uoregon.edu (Doug White) Date: Thu, 27 May 1999 13:47:08 -0500 (CDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 27 May 1999, Kevin Day wrote: > > > I've got two systems that panic about every 48 hours, saying they're out of > > mbuf's. I've tried raising maxusers. (It's at 128 now, but i've gone up to > > 256 and still seen the same thing). > > > > I believe it's a leak, since it's pretty consistant how long it will stay up > > before it runs out. > > > > I've tried raising NBMCLUSTERs, but this just seems to prolong it before it > > finally panic's. > > How high do you have it set? > I tried doubling whatever it was that putting maxusers at 256 set it at. (I can get the exact number later). I'm running with no NMBCLUSTERS setting, just with maxusers at 128 at the moment. > You might want to collect some netstat -m stats as time goes on. In > addition to being easier to read, it may give you some hints as to how > high you want to go with mbuf clusters. I added a cron job to to netstat -m every half hour... Right now, after 10 hours of being up: 494/2624 mbufs in use: 160 mbufs allocated to data 334 mbufs allocated to packet headers 130/1686/2560 mbuf clusters in use (current/peak/max) 3700 Kbytes allocated to network (8% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines > > The only unusual thing about these two machines are that they're very heavy > > NFS client users. > > That might do it by itself irrespective of any bugs. > This didn't happen in 2.2.8 or 3.1, so I'm trying to figure out what's causing it. :) Here's a typical panic: IdlePTD 3096576 initial pcb at 27ea40 panicstr: Out of mbuf clusters panic messages: --- panic: Out of mbuf clusters syncing disks... panic: Out of mbuf clusters dumping to dev 20001, offset 467137 dump 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:288 288 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:288 #1 0xc0145755 in panic () at ../../kern/kern_shutdown.c:450 #2 0xc015c2ca in m_retry (i=0, t=1) at ../../kern/uipc_mbuf.c:269 #3 0xc01b2c77 in nfsm_reqh (vp=0xcb6bddc0, procid=21, hsiz=68, bposp=0xcb2cecdc) at ../../nfs/nfs_subs.c:599 #4 0xc01c8e13 in nfs_commit (vp=0xcb6bddc0, offset=0, cnt=8192, cred=0xc13b0200, procp=0xc02955a0) at ../../nfs/nfs_vnops.c:2580 #5 0xc01c9620 in nfs_flush (vp=0xcb6bddc0, cred=0xc0a5f900, waitfor=2, p=0xc02955a0, commit=1) at ../../nfs/nfs_vnops.c:2846 #6 0xc01c9389 in nfs_fsync (ap=0xcb2cedfc) at ../../nfs/nfs_vnops.c:2710 #7 0xc01b9489 in nfs_sync (mp=0xc113bc00, waitfor=2, cred=0xc0a5f900, p=0xc02955a0) at vnode_if.h:499 #8 0xc016ceaf in sync (p=0xc02955a0, uap=0x0) at ../../kern/vfs_syscalls.c:543 #9 0xc014535a in boot (howto=256) at ../../kern/kern_shutdown.c:205 #10 0xc0145755 in panic () at ../../kern/kern_shutdown.c:450 #11 0xc015c382 in m_retryhdr (i=0, t=1) at ../../kern/uipc_mbuf.c:297 #12 0xc015de2b in sosend (so=0xc9a55000, addr=0x0, uio=0xcb2cef00, top=0x0, control=0x0, flags=0, p=0xcb2692e0) at ../../kern/uipc_socket.c:499 #13 0xc016093f in sendit (p=0xcb2692e0, s=5, mp=0xcb2cef40, flags=0) at ../../kern/uipc_syscalls.c:514 #14 0xc0160a2d in sendto (p=0xcb2692e0, uap=0xcb2cef90) at ../../kern/uipc_syscalls.c:564 #15 0xc020ec26 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077951456, tf_esi = 0, tf_ebp = -1077951564, tf_isp = -886247452, tf_ebx = 538075232, tf_edx = 682064, tf_ecx = 0, tf_eax = 133, tf_trapno = 7, tf_err = 7, tf_eip = 537941473, tf_cs = 31, tf_eflags = 534, tf_esp = -1077951596, tf_ss = 47}) at ../../i386/i386/trap.c:1066 #16 0x7 in ?? () (kgdb) #10 0xc0145755 in panic () at ../../kern/kern_shutdown.c:450 450 boot(bootopt); (kgdb) #11 0xc015c382 in m_retryhdr (i=0, t=1) at ../../kern/uipc_mbuf.c:297 297 panic("Out of mbuf clusters"); Looks like it panic'ed, tried to sync, which caused another panic. Looking at the core dump with vmstat -M doesn't show really anything that interesting, FFS Node is using the most memory, and that's only 1.3M. Any further digging anyone would like? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 13:19:47 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 541D81535D for ; Thu, 27 May 1999 13:19:40 -0700 (PDT) (envelope-from klui@cup.hp.com) Received: from cup44ux.cup.hp.com (klui@cup44ux.cup.hp.com [15.13.168.124]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id NAA02263 for ; Thu, 27 May 1999 13:19:29 -0700 (PDT) Received: (from klui@localhost) by cup44ux.cup.hp.com (8.8.6 (PHNE_14041)/8.7.3 TIS Messaging 5.0) id NAA05582 for current@freebsd.org; Thu, 27 May 1999 13:15:02 -0700 (PDT) From: Ken Lui Message-Id: <199905272015.NAA05582@cup44ux.cup.hp.com> Subject: Spontaneous reboot while CPU usage is high To: current@freebsd.org Date: Thu, 27 May 1999 13:15:00 -0700 (PDT) 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, I have FreeBSD3.2 from ftp7.de.freebsd.org dated May 1999 installed on an AMD K6-2 333MHz with Aladdin V chipset and have experienced spontaneous reboots while CPU usage is very high--compiling or bringing a new web link in another window within Netscape Communicator. There are no entries in /var/log/messages. The symptom is the machine wedges for around 5-10 seconds and then my machine reboots. I have searched for the GNATS database and in dejanews and the closest things that may be causing my problem is perhaps the K6-2 itself or need of finetuning of some kernel parameters. I am unsure of how to check for the bad K6-2 itself. This system is a "hand-me-down," but is fairly reliable under Linux. Attached, please browse through my dmesg log and my kernel configuration file. Regards, Ken ---dmesg--- Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-RELEASE #4: Wed May 26 12:55:59 PDT 1999 root@black.tmpest1.org:/usr/src/sys/compile/BLACK Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (333.37-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf real memory = 100663296 (98304K bytes) avail memory = 95182848 (92952K bytes) Probing for devices on PCI bus 0: chip0: rev 0x04 on pci0.0.0 chip1: rev 0x04 on pci0.1.0 chip2: rev 0xb4 on pci0.7.0 ed1: rev 0x00 int a irq 9 on pci0.8.0 ed1: address 00:80:c8:fd:90:ae, type NE2000 (16 bit) ed2: rev 0x00 int a irq 9 on pci0.9.0 ed2: address 00:80:c8:fd:88:0d, type NE2000 (16 bit) adv0: rev 0x02 int a irq 9 on pci0.11.0 adv0: AdvanSys Ultra SCSI Host Adapter, SCSI ID 7, queue depth 240 ide_pci0: rev 0x20 int a irq 0 on pci0.15.0 Probing for devices on PCI bus 1: vga0: rev 0xf3 int a irq 10 on pci1.6.0 Probing for PnP devices: CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 flags 0x10 on isa Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model MouseMan+, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pcm0 not probed due to drq conflict with pcm1 at 1 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1625MB (3329424 sectors), 3303 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 1 (wd3): wd3: 4121MB (8440992 sectors), 8374 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 0 (atapi): , removable, intr, dma, iordy acd0: drive speed 1031KB/sec, 120KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/1 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port lpt0: on ppbus 0 lpt0: Interrupt-driven port adv0 not found at 0x330 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.2 Waiting 5 seconds for SCSI devices to settle sa0 at adv0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) changing root device to wd3s1a da0 at adv0 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: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) ---kernelconfiguration--- # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.143.2.12 1999/05/14 15:12:26 jkh Exp $ machine "i386" #cpu "I386_CPU" #cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident BLACK maxusers 32 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "EXT2FS" options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_LINUX options SCSI_DELAY=5000 options IDE_DELAY=2000 options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd3 # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 controller pnp0 #controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 #options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. #controller ncr0 #controller ahb0 #controller ahc0 #controller isp0 # This controller offers a number of configuration options, too many to # document here - see the LINT file in this directory and look up the # dpt0 entry there for much fuller documentation on this. #controller dpt0 controller adv0 at isa? port ? cam irq ? #controller adw0 #controller bt0 at isa? port ? cam irq ? #controller aha0 at isa? port ? cam irq ? controller scbus0 device da0 device sa0 device pass0 device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 #device mcd0 at isa? port 0x300 bio irq 10 #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty #options PCVT_FREEBSD=211 #options PCVT_EMU_MOUSE #options PCVT_PRETTYSCRNS #options PCVT_SCREENSAVER options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at isa? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # #device apm0 at isa? disable flags 0x31 # Advanced Power Management device apm0 at isa? # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 #device sio2 at isa? disable port "IO_COM3" tty irq 5 #device sio3 at isa? disable port "IO_COM4" tty irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 net irq 7 controller ppbus0 device lpt0 at ppbus? #device plip0 at ppbus? #device ppi0 at ppbus? #controller vpo0 at ppbus? # # The following Ethernet NICs are all PCI devices. # #device ax0 # ASIX AX88140A #device de0 # DEC/Intel DC21x4x (``Tulip'') #device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) #device mx0 # Macronix 98713/98715/98725 (``PMAC'') #device pn0 # Lite-On 82c168/82c169 (``PNIC'') #device rl0 # RealTek 8129/8139 #device tl0 # Texas Instruments ThunderLAN #device tx0 # SMC 9432TX (83c170 ``EPIC'') #device vr0 # VIA Rhine, Rhine II #device vx0 # 3Com 3c590, 3c595 (``Vortex'') #device wb0 # Winbond W89C840F #device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 #device ep0 at isa? port 0x300 net irq 10 #device ex0 at isa? port? net irq? #device fe0 at isa? port 0x300 net irq ? #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 net irq 10 drq 0 #device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000 #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 #device cs0 at isa? port 0x300 net irq ? pseudo-device loop pseudo-device ether #pseudo-device sl 1 #pseudo-device ppp 1 #pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. #options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG options SYSVSEM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. #pseudo-device bpfilter 4 #Berkeley packet filter device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 -- Ken Lui 19111 Pruneridge Avenue klui@cup.hp.com Cupertino, CA 95014-0795 USA Information Solutions & Services 1.408.447.3230 FAX 1.408.447.0218 Views within this message may not be those of the Hewlett-Packard Company To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 15:47:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 9201514BFA for ; Thu, 27 May 1999 15:47:20 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id RAA72903; Thu, 27 May 1999 17:47:12 -0500 (CDT) (envelope-from dan) Date: Thu, 27 May 1999 17:47:11 -0500 From: Dan Nelson To: David Scheidt Cc: Kazutaka YOKOTA , freebsd-current@FreeBSD.ORG Subject: Re: moused broken? Message-ID: <19990527174711.A72808@dan.emsphone.com> References: <199905271416.XAA26529@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from "David Scheidt" on Thu May 27 09:55:56 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (May 27), David Scheidt said: > On Thu, 27 May 1999, Kazutaka YOKOTA wrote: > > It is a PS/2 mouse or a serial mouse? What model is it? > > Sorry. It is a three button PS/2 mouse, an AT&T 320. I think it is really > a Logitech mouse in Deathstar clothing. From dmesg: > May 24 13:59:31 rally3 /kernel: psm0: irq 12 on atkbdc0 > May 24 13:59:31 rally3 /kernel: psm0: model Generic PS/2 mouse, device ID 0 > > I never had a problem with the mouse under 2.2.8, 3.x, or NT. (I > really like these mice: 3m cords). > > I also found the following lines in syslog: > May 25 15:33:34 rally3 /kernel: psmintr: out of sync (0080 != 0000). Are you also using a Cybex switchbox? Try tapping , , "M", "W", (or if you've got one of the fancy ones, reset the mouse via the onscreen menu). I've had this happen to me on two separate machines. -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 16:11:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 4ADF714CE5 for ; Thu, 27 May 1999 16:11:53 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA11415 for freebsd-current@freebsd.org; Thu, 27 May 1999 23:51:41 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA03196 for freebsd-current@freebsd.org; Thu, 27 May 1999 22:43:21 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905272043.WAA03196@yedi.iaf.nl> Subject: error message, what does this mean? To: freebsd-current@freebsd.org Date: Thu, 27 May 1999 22:43:21 +0200 (CEST) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi My P100 testbox running a fairly recent current just said: May 27 23:39:23 p100 /kernel: vnode_pager: *** WARNING *** stale FS getpages May 27 23:39:23 p100 /kernel: No strategy for buffer at 0xc13637e0 May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) May 27 23:39:23 p100 /kernel: tag VT_PROCFS, type 5, pid 252, mode 180, flags 0 May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) May 27 23:39:23 p100 /kernel: tag VT_PROCFS, type 5, pid 252, mode 180, flags 0 May 27 23:39:23 p100 /kernel: vnode_pager_getpages: I/O read error May 27 23:39:23 p100 /kernel: vm_fault: pager read error, pid 252 (cp) May 27 23:39:23 p100 /kernel: vnode_pager: *** WARNING *** stale FS getpages May 27 23:39:23 p100 /kernel: No strategy for buffer at 0xc13637e0 May 27 23:39:23 p100 /kernel: : 0xc36002c0: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) etc This was during a cp -R /* /mnt where /mnt is a SCSI disk I'm testing. Both disks are on seperate SCSI buses. Is this because the cp -R tries to copy /proc ?? | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 18:47:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from po0.wam.umd.edu (po0.wam.umd.edu [128.8.10.162]) by hub.freebsd.org (Postfix) with ESMTP id 66D61159FB for ; Thu, 27 May 1999 18:47:19 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po0.wam.umd.edu (8.9.3/8.9.3) with ESMTP id VAA15587 for ; Thu, 27 May 1999 21:47:18 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id VAA01413 for ; Thu, 27 May 1999 21:47:17 -0400 (EDT) Received: from localhost by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id VAA01407 for ; Thu, 27 May 1999 21:47:17 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Thu, 27 May 1999 21:47:17 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: splash screen broken?? 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 Whenever I try to load the splash screen (300x200 256 colors) the modules seem to load right, however, when the kernel boots, it gives me an error about mod_register_init or something of that nature, I was just testing the config... I tried these commands at the boot loader. load kernel load -t splash_image_data /boot/splash.bmp load splash_bmp.ko boot and it gave me the error I tried switching the the second two loads around, but that didn't work, and I tried just letting /boot/defaults/loader.conf do the loading for me, no matter what, I got the same error. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 18:57:41 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 E726D151A9 for ; Thu, 27 May 1999 18:57:39 -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 SAA03649; Thu, 27 May 1999 18:54:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905280154.SAA03649@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org Subject: Re: splash screen broken?? In-reply-to: Your message of "Thu, 27 May 1999 21:47:17 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 May 1999 18:54:45 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Whenever I try to load the splash screen (300x200 256 colors) the modules > seem to load right, however, when the kernel boots, it gives me an error > about mod_register_init or something of that nature, I was just testing > the config... I tried these commands at the boot loader. It is never correct for a problem report to contain "something of that nature". -- \\ 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 Thu May 27 19: 1:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id ECEA814D64 for ; Thu, 27 May 1999 19:01:52 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA17364; Thu, 27 May 1999 19:01:44 -0700 (PDT) (envelope-from dillon) Date: Thu, 27 May 1999 19:01:44 -0700 (PDT) From: Matthew Dillon Message-Id: <199905280201.TAA17364@apollo.backplane.com> To: Wilko Bulte Cc: freebsd-current@FreeBSD.ORG Subject: Re: error message, what does this mean? References: <199905272043.WAA03196@yedi.iaf.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :etc : :This was during a cp -R /* /mnt where /mnt is a SCSI disk I'm testing. :Both disks are on seperate SCSI buses. Is this because the cp -R :tries to copy /proc ?? : :| / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - :|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org It seems to me that a cp command like is probably trying to cp -R /mnt to /mnt ... /* will include /mnt, right? I'm not sure what would be causing the errors, though, unless the cp is recursing endlessly due to the cp of /mnt on top of /mnt and running the filesystem out of space... -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 20: 5:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from po0.wam.umd.edu (po0.wam.umd.edu [128.8.10.162]) by hub.freebsd.org (Postfix) with ESMTP id 87D59151B4 for ; Thu, 27 May 1999 20:05:42 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po0.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA22443; Thu, 27 May 1999 23:05:01 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA05809; Thu, 27 May 1999 23:05:00 -0400 (EDT) Received: from localhost by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA05799; Thu, 27 May 1999 23:05:00 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Thu, 27 May 1999 23:05:00 -0400 (EDT) From: Kenneth Wayne Culver Reply-To: Kenneth Wayne Culver To: Mike Smith Cc: freebsd-current@freebsd.org Subject: Re: splash screen broken?? In-Reply-To: <199905280154.SAA03649@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 > > Whenever I try to load the splash screen (300x200 256 colors) the modules > > seem to load right, however, when the kernel boots, it gives me an error > > about mod_register_init or something of that nature, I was just testing > > the config... I tried these commands at the boot loader. > Here it is... I typed the exact same lines into the bootloader that I showed you in my last mail, and here is my dmesg output... I also have the line pseudo-device splash in my kernel so I know that's not the problem. 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 May 27 20:56:03 EDT 1999 culverk@culverk.x-press.net:/usr/src/sys/compile/MYKERNEL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff real memory = 67043328 (65472K bytes) avail memory = 61747200 (60300K bytes) Preloaded elf kernel "kernel" at 0xc0346000. Preloaded elf module "splash_bmp.ko" at 0xc034609c. Preloaded splash_image_data "/boot/splash.bmp" at 0xc0346140. Pentium Pro MTRR support enabled, default memory type is uncacheable module_register_init: MOD_LOAD (splash_bmp, c028162c, 0) error 19 That is all the dmesg output that has anything to do with splash. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 20: 9:26 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 7CA241522B for ; Thu, 27 May 1999 20:09:20 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:djdqC0mm5n8LVU2eniR8yoV26hjEtnTw@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id MAA15346; Fri, 28 May 1999 12:09:26 +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 MAA09521; Fri, 28 May 1999 12:13:18 +0900 (JST) Message-Id: <199905280313.MAA09521@zodiac.mech.utsunomiya-u.ac.jp> To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: splash screen broken?? In-reply-to: Your message of "Thu, 27 May 1999 21:47:17 -0400." References: Date: Fri, 28 May 1999 12:13:17 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Whenever I try to load the splash screen (300x200 256 colors) the modules >seem to load right, however, when the kernel boots, it gives me an error >about mod_register_init or something of that nature, I was just testing >the config... I tried these commands at the boot loader. > >load kernel >load -t splash_image_data /boot/splash.bmp >load splash_bmp.ko >boot > >and it gave me the error >I tried switching the the second two loads around, but that didn't work, >and I tried just letting /boot/defaults/loader.conf do the loading for me, >no matter what, I got the same error. Although it is hard to tell what is wrong in your case without the precise error message, the followings are possible cause of errors. 1. The bitmap format is something splash_bmp doesn't understand. Are you sure the file is a W*ndows BMP file? 2. The bitmap is larger than the maximum screen size the video card supports. Without the VESA module, the maximum allowed size is 320x200. (Your bitmap size is 300x200, thus, should be OK.) With the VESA module, the maximum size varies; it depends on the VESA BIOS on your video card. 3. The video card doesn't support required graphics modes. Run 'vidcontrol -i mode' and see if the 320x200 256 color mode is supported. The vga driver in FreeBSD may not be able to support all video modes, if the video card's BIOS is not as compatible as it should be. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 20:45:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from xtsw12c.ukc.ac.uk (user.jakinternet.co.uk [212.41.35.69]) by hub.freebsd.org (Postfix) with ESMTP id 0600C15271; Thu, 27 May 1999 20:45:03 -0700 (PDT) (envelope-from dlombardo@excite.com) Received: from excite.com (localhost [127.0.0.1]) by xtsw12c.ukc.ac.uk (8.9.3/8.9.1) with ESMTP id FAA01167; Fri, 28 May 1999 05:46:58 +0100 (BST) (envelope-from dlombardo@excite.com) Message-ID: <374E1FC1.C10DCBE@excite.com> Date: Fri, 28 May 1999 05:46:57 +0100 From: Dean Lombardo Organization: University of Kent at Canterbury (England) X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-multimedia@freebsd.org Subject: pcm still broken in -current (at least for me) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kernel sources cvsupped yesterday. The sound card is a Yamaha YMF 715 (non-PnP); worked fine until about the end of April. Now boot -v shows: /kernel: mss_detect - chip revision 0x0a /kernel: ... try to identify the yamaha /kernel: mss_detect() - Detected CS4231 /kernel: pcm0 at port 0x530 irq 5 drq 1 flags 0x15 on isa0 /kernel: mss_attach 0 at 0x530 irq 5 dma 1:5 flags 0xa215 /kernel: device combination doesn't support shared irq3 /kernel: intr_connect(irq3) failed, result=-1 /kernel: device combination doesn't support shared irq4 /kernel: intr_connect(irq4) failed, result=-1 /kernel: device combination doesn't support shared irq5 /kernel: intr_connect(irq5) failed, result=-1 /kernel: device combination doesn't support shared irq7 /kernel: intr_connect(irq7) failed, result=-1 /kernel: device combination doesn't support shared irq9 /kernel: intr_connect(irq9) failed, result=-1 /kernel: device combination doesn't support shared irq12 /kernel: intr_connect(irq12) failed, result=-1 /kernel: device combination doesn't support shared irq14 /kernel: intr_connect(irq14) failed, result=-1 /kernel: device combination doesn't support shared irq15 /kernel: intr_connect(irq15) failed, result=-1 The same happens with snd0 instead of pcm. It looks like it can't register the interrupt handler - is it now supposed to be registered in a different way (perhaps via nexus)? Normal boot (without -v) doesn't show any error messages. mpg123 starts normally and just sits there doing nothing: UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 1001 1159 256 52 -6 0 6464 716 dspwr S+ p1 0:03.28 mpg123 test.mp3 until I press Ctrl-C, after which the following appears in /var/log/messages /kernel: How strange... mss_intr with no reason! /kernel: tsleep returns 4 Just wondering whether anyone else had the same problem... Dean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 27 20:51: 2 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 3C95015094; Thu, 27 May 1999 20:50:55 -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 LAA20438; Fri, 28 May 1999 11:49:54 +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 LAA02623; Fri, 28 May 1999 11:50:47 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id LAA18208; Fri, 28 May 1999 11:50:47 +0800 Message-Id: <199905280350.LAA18208@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dean Lombardo Cc: current@freebsd.org, multimedia@freebsd.org Subject: Re: pcm still broken in -current (at least for me) In-reply-to: Your message of "Fri, 28 May 1999 05:46:57 +0100." <374E1FC1.C10DCBE@excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 May 1999 11:50:46 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The same happens with snd0 instead of pcm. It looks like it can't > register the interrupt handler - is it now supposed to be registered in > a different way (perhaps via nexus)? > I'm seeing the exact same problem, only with the Voxware driver and a PAS16. I've held off upgrading the soundcard because all the local vendors only seem to sell cards we don't have drivers for. Sigh. 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 Thu May 27 21:46:55 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 7324C14C80 for ; Thu, 27 May 1999 21:46:53 -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 VAA29623; Thu, 27 May 1999 21:46:52 -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 VAA06342; Thu, 27 May 1999 21:46:51 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 27 May 1999 21:46:51 -0700 (PDT) Message-Id: <199905280446.VAA06342@vashon.polstra.com> To: dwhite@resnet.uoregon.edu Subject: Re: FTP passive mode - a new default? In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Doug White wrote: > I second the suggestion to 'autoprobe' PASV support, and revert to active > mode (w/ an appropriate msg) if PASV is refused. That won't be a good solution in practice. When passive mode doesn't work, it's almost always because a firewall on the server side is blocking the incoming data connection. The client doesn't see a refusal; its connect() call just times out. The trouble is, the timeout takes a long time (on the order of a minute or more). 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 Thu May 27 23:18:46 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 381D814D77 for ; Thu, 27 May 1999 23:18:42 -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 QAA32640; Fri, 28 May 1999 16:18:40 +1000 Date: Fri, 28 May 1999 16:18:40 +1000 From: Bruce Evans Message-Id: <199905280618.QAA32640@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, wilko@yedi.iaf.nl Subject: Re: error message, what does this mean? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >May 27 23:39:23 p100 /kernel: vnode_pager: *** WARNING *** stale FS getpages >May 27 23:39:23 p100 /kernel: No strategy for buffer at 0xc13637e0 >May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, >writecount 0, > refcount 0, flags (VOBJBUF) >May 27 23:39:23 p100 /kernel: tag VT_PROCFS, type 5, pid 252, mode 180, >flags 0 >May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, >... >This was during a cp -R /* /mnt where /mnt is a SCSI disk I'm testing. >Both disks are on seperate SCSI buses. Is this because the cp -R >tries to copy /proc ?? Probably. Procfs has bugs that cause bad things to happen when some files in it are copied. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 2: 6:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (Postfix) with ESMTP id 2123C14D93 for ; Fri, 28 May 1999 02:06:14 -0700 (PDT) (envelope-from jkb@shell6.ba.best.com) Received: (from jkb@localhost) by shell6.ba.best.com (8.9.3/8.9.2/best.sh) id CAA13565; Fri, 28 May 1999 02:05:42 -0700 (PDT) Message-ID: <19990528020541.D8308@best.com> Date: Fri, 28 May 1999 02:05:41 -0700 From: "Jan B. Koum " To: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <16256.927715821@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <16256.927715821@zippy.cdrom.com>; from Jordan K. Hubbard on Wed, May 26, 1999 at 03:50:21AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 26, 1999 at 03:50:21AM -0700, "Jordan K. Hubbard" wrote: > Unless I hear unanimous fierce outcry against it, I'm strongly > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > default for all tools/libraries which currently examine it. > FTP_ACTIVE_MODE will be the new flag for toggling the previous > behavior. > > Given the state of the Internet today, I think this is purely a > sensible change in defaults. Comments? > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Yay! This is awesome. I guess in addition to ftp, the tools and libraries you talk about would also include fetch, and other firewall not so friendly things? (Would be nice if CVSup can fake FTP_PASSIVE_MODE by doing '-P -' too). -- Yan P.S. - Everyone knows allowing connections from other side's port 20 is silly since root can control src port. Hell, nmap even does port scan with source port of 20 if you ask it to. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 3:56:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 84C5714C87 for ; Fri, 28 May 1999 03:56:32 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id MAA10588; Fri, 28 May 1999 12:01:57 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id JAA10071; Fri, 28 May 1999 09:19:11 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905280719.JAA10071@yedi.iaf.nl> Subject: Re: error message, what does this mean? In-Reply-To: <199905280618.QAA32640@godzilla.zeta.org.au> from Bruce Evans at "May 28, 1999 4:18:40 pm" To: bde@zeta.org.au (Bruce Evans) Date: Fri, 28 May 1999 09:19:11 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Bruce Evans wrote ... > >May 27 23:39:23 p100 /kernel: vnode_pager: *** WARNING *** stale FS getpages > >May 27 23:39:23 p100 /kernel: No strategy for buffer at 0xc13637e0 > >May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, > >writecount 0, > > refcount 0, flags (VOBJBUF) > >May 27 23:39:23 p100 /kernel: tag VT_PROCFS, type 5, pid 252, mode 180, > >flags 0 > >May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, > >... > > >This was during a cp -R /* /mnt where /mnt is a SCSI disk I'm testing. > >Both disks are on seperate SCSI buses. Is this because the cp -R > >tries to copy /proc ?? > > Probably. Procfs has bugs that cause bad things to happen when some > files in it are copied. Hmm. Never seen it before. But doing a "cd / ; find . -fstype ufs -print | cpio -pudm /mnt" works like a charm without the vnode_pager messages. So looks like procfs alright. | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 3:56:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id B0BA615A89 for ; Fri, 28 May 1999 03:56:32 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id MAA10589; Fri, 28 May 1999 12:01:59 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id JAA09963; Fri, 28 May 1999 09:09:17 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905280709.JAA09963@yedi.iaf.nl> Subject: Re: error message, what does this mean? In-Reply-To: <199905280201.TAA17364@apollo.backplane.com> from Matthew Dillon at "May 27, 1999 7: 1:44 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 28 May 1999 09:09:17 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Matthew Dillon wrote ... > :etc > : > :This was during a cp -R /* /mnt where /mnt is a SCSI disk I'm testing. > :Both disks are on seperate SCSI buses. Is this because the cp -R > :tries to copy /proc ?? > : > :| / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - > :|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org > > It seems to me that a cp command like is probably trying to > cp -R /mnt to /mnt ... /* will include /mnt, right? I'm not > sure what would be causing the errors, though, unless the cp > is recursing endlessly due to the cp of /mnt on top of /mnt > and running the filesystem out of space... In the end that happens, but not after a couple of seconds already. I'm quite sure it is the copying of /proc that triggers the messages. The VT_PROCFS like in May 28 10:04:15 p100 /kernel: tag VT_PROCFS, type 6, pid 193, mode 180, flags 0 also seems to indicate this. If I do: cd / ; find . -fstype ufs -print | cpio -pdum /mnt it works just fine without messages (of course until /mnt becomes full like you mention above). I've never seen this procfs behaviour before BTW. | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 5: 4:18 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 A4E4314C81 for ; Fri, 28 May 1999 05:04:16 -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 OAA05713; Fri, 28 May 1999 14:04:11 +0200 (CEST) (envelope-from des) To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <16256.927715821@zippy.cdrom.com> From: Dag-Erling Smorgrav Date: 28 May 1999 14:04:10 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of "Wed, 26 May 1999 03:50:21 -0700" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > Unless I hear unanimous fierce outcry against it, I'm strongly > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > default for all tools/libraries which currently examine it. > FTP_ACTIVE_MODE will be the new flag for toggling the previous > behavior. I agree that passive mode should be the default. I do not agree that the tools should be changed to reflect this. I suggest that we instead set FTP_PASSIVE_MODE to YES in some suitable place (e.g. /etc/profile, /etc/cshrc). 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 Fri May 28 5: 5:24 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 87E5C151AC for ; Fri, 28 May 1999 05:05:22 -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 OAA05726; Fri, 28 May 1999 14:05:17 +0200 (CEST) (envelope-from des) To: Doug White Cc: "Jordan K. Hubbard" , junkmale@xtra.co.nz, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: From: Dag-Erling Smorgrav Date: 28 May 1999 14:05:16 +0200 In-Reply-To: Doug White's message of "Thu, 27 May 1999 11:07:24 -0700 (PDT)" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White writes: > I second the suggestion to 'autoprobe' PASV support, and revert to active > mode (w/ an appropriate msg) if PASV is refused. No. Ncftp tries to do this, and provides adequate proof that it is not practical. 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 Fri May 28 5: 5:58 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 2F61314CCB for ; Fri, 28 May 1999 05:05:54 -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 OAA05731; Fri, 28 May 1999 14:05:48 +0200 (CEST) (envelope-from des) To: junkmale@xtra.co.nz Cc: current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <19990526182800.EGOX7623210.mta2-rme@wocker> From: Dag-Erling Smorgrav Date: 28 May 1999 14:05:48 +0200 In-Reply-To: "Dan Langille"'s message of "Thu, 27 May 1999 06:25:34 +1200" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Dan Langille" writes: > For the argument that some ftp servers don't accept passive mode, I say > it's a question of numbers: which default setting will satisfy the > greatest number of people? which setting will reduce the number of > questions "how do I do X"? FTP servers which do not accept passive mode are, IMHO, broken. Their loss. 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 Fri May 28 5: 9:53 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 3C2DA14F5B for ; Fri, 28 May 1999 05:09:23 -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 OAA05747; Fri, 28 May 1999 14:09:20 +0200 (CEST) (envelope-from des) To: "Jan B. Koum " Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <16256.927715821@zippy.cdrom.com> <19990528020541.D8308@best.com> From: Dag-Erling Smorgrav Date: 28 May 1999 14:09:19 +0200 In-Reply-To: "Jan B. Koum "'s message of "Fri, 28 May 1999 02:05:41 -0700" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jan B. Koum " writes: > Yay! This is awesome. I guess in addition to ftp, the tools and > libraries you talk about would also include fetch, and other firewall > not so friendly things? (Would be nice if CVSup can fake FTP_PASSIVE_MODE > by doing '-P -' too). CVSup uses multiplexed mode by default, which means it multiplexes its various data channels over a single TCP connection. The server does not (should not) attempt to connect back to the client. 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 Fri May 28 5:19:17 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 5D61A14CCB for ; Fri, 28 May 1999 05:19:14 -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 OAA23457; Fri, 28 May 1999 14:19:09 +0200 (MET DST) Date: Fri, 28 May 1999 14:19:09 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? 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 28 May 1999, Dag-Erling Smorgrav wrote: > "Jan B. Koum " writes: > > Yay! This is awesome. I guess in addition to ftp, the tools and > > libraries you talk about would also include fetch, and other firewall > > not so friendly things? (Would be nice if CVSup can fake FTP_PASSIVE_MODE > > by doing '-P -' too). > > CVSup uses multiplexed mode by default, which means it multiplexes its > various data channels over a single TCP connection. The server does > not (should not) attempt to connect back to the client. No. $ /usr/local/bin/cvsup /usr/src-supfile -g -L 2 ... Establishing active-mode data connection Timed out waiting for connection from server. Check your firewall setup or try the "-P m" option And it never gets there (firewall is 3 hops down the road). '-P m' does change the behaviour. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 5:31: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 5C71C14D28 for ; Fri, 28 May 1999 05:31:41 -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 OAA05834; Fri, 28 May 1999 14:31:38 +0200 (CEST) (envelope-from des) To: Nick Hibma Cc: Dag-Erling Smorgrav , current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: From: Dag-Erling Smorgrav Date: 28 May 1999 14:31:38 +0200 In-Reply-To: Nick Hibma's message of "Fri, 28 May 1999 14:19:09 +0200 (MET DST)" Message-ID: Lines: 24 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma writes: > On 28 May 1999, Dag-Erling Smorgrav wrote: > > CVSup uses multiplexed mode by default, which means it multiplexes its > > various data channels over a single TCP connection. The server does > > not (should not) attempt to connect back to the client. > No. Yes, it does. If your version doesn't, you're way overdue for an upgrade :) The documentation for CVSup 16.0 says "The modes provided for this are multiplexed mode, passive mode, SOCKS mode, and active mode. All but multiplexed mode are deprecated. Multiplexed mode can handle any situation that the other modes can handle. By default the channels are established in multiplexed mode, if the server is new enough to support it." I can't remember how long multiplexed mode has been the default, but I'm sure it was already the default in 15.4 or whatever was the last version before 16.0. 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 Fri May 28 6:31:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (unknown [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id A995B14BFA for ; Fri, 28 May 1999 06:31:16 -0700 (PDT) (envelope-from dispatch@blackhelicopters.org) Received: (from dispatch@localhost) by blackhelicopters.org (8.8.8/8.8.8) id JAA26508; Fri, 28 May 1999 09:31:02 -0400 (EDT) (envelope-from dispatch) From: Dispatcher Message-Id: <199905281331.JAA26508@blackhelicopters.org> Subject: Re: FTP passive mode - a new default? In-Reply-To: from Nick Hibma at "May 28, 1999 2:19: 9 pm" To: nick.hibma@jrc.it Date: Fri, 28 May 1999 09:31:02 -0400 (EDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > CVSup uses multiplexed mode by default, which means it multiplexes its > > various data channels over a single TCP connection. The server does > > not (should not) attempt to connect back to the client. > > No. > > $ /usr/local/bin/cvsup /usr/src-supfile -g -L 2 > ... > Establishing active-mode data connection > Timed out waiting for connection from server. Check your firewall setup > or try the "-P m" option > > And it never gets there (firewall is 3 hops down the road). > '-P m' does change the behaviour. You're probably still running cvsup 15.4 or earlier. As of version 16, multiplexed mode is the default. Upgrade, if it's that important. I'm still running 15.4 at a lot of places... works well enough for cvsup && make world, even with the (petty) annoyance of '-P m'. ==Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 9:26:50 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 4852E15434 for ; Fri, 28 May 1999 09:26:48 -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 JAA00805; Fri, 28 May 1999 09:23:28 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905281623.JAA00805@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kenneth Wayne Culver Cc: Mike Smith , freebsd-current@freebsd.org Subject: Re: splash screen broken?? In-reply-to: Your message of "Thu, 27 May 1999 23:05:00 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 May 1999 09:23:27 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Whenever I try to load the splash screen (300x200 256 colors) the modules > > > seem to load right, however, when the kernel boots, it gives me an error > > > about mod_register_init or something of that nature, I was just testing > > > the config... I tried these commands at the boot loader. > > > Here it is... I typed the exact same lines into the bootloader that I > showed you in my last mail, and here is my dmesg output... I also have the > line > > pseudo-device splash > > in my kernel so I know that's not the problem. ... > module_register_init: MOD_LOAD (splash_bmp, c028162c, 0) error 19 That's what we needed to see. Error 19 is ENODEV; this means you either don't have VESA support compiled in, haven't loaded the VESA module, or your VESA BIOS doesn't support a mode that allows a 300x200x8 image to be displayed. -- \\ 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 May 28 12: 1:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from spawn.nectar.cc (gw.nectar.com [204.0.249.101]) by hub.freebsd.org (Postfix) with ESMTP id E338214F98 for ; Fri, 28 May 1999 12:01:26 -0700 (PDT) (envelope-from nectar@nectar.cc) Received: from spawn.nectar.cc (localhost [127.0.0.1]) by spawn.nectar.cc (Postfix) with ESMTP id 3C3CBB740; Fri, 28 May 1999 14:00:55 -0500 (CDT) X-Mailer: exmh version 2.0.2 2/24/98 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: mlist/freebsd/current X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.cc/nectar-rsa.txt X-PGP-DSSfprint: AB2F 8D71 A4F4 467D 352E 8A41 5D79 22E4 71A2 8C73 X-PGP-DHfprint: 2D50 12E5 AB38 60BA AF4B 0778 7242 4460 1C32 F6B1 X-PGP-DH-DSSkey: http://www.nectar.cc/nectar-dh-dss.txt From: Jacques Vidrine To: Dag-Erling Smorgrav Cc: junkmale@xtra.co.nz, current@FreeBSD.ORG In-reply-to: References: <19990526182800.EGOX7623210.mta2-rme@wocker> Subject: Re: FTP passive mode - a new default? Mime-Version: 1.0 Content-Type: text/plain Date: Fri, 28 May 1999 14:00:55 -0500 Message-Id: <19990528190055.3C3CBB740@spawn.nectar.cc> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 May 1999 at 14:05, Dag-Erling Smorgrav wrote: > FTP servers which do not accept passive mode are, IMHO, broken. Their > loss. I'll second that opinion. Netscape and Microsoft browsers, at least, have been using passive FTP for years (1994 or earlier). One could argue that these are the most used FTP clients in the world, and has made passive mode a de facto requirement for public FTP servers. Jacques Vidrine / n@nectar.cc / nectar@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 May 28 12:38:51 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 03F5714E92 for ; Fri, 28 May 1999 12:38:47 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id MAA21452; Fri, 28 May 1999 12:38:05 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 28 May 1999 12:38:04 -0700 (PDT) From: Doug White To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: -Current still leaking mbuf's In-Reply-To: <199905271847.NAA18802@home.dragondata.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, 27 May 1999, Kevin Day wrote: > I tried doubling whatever it was that putting maxusers at 256 set it at. (I > can get the exact number later). I'm running with no NMBCLUSTERS setting, > just with maxusers at 128 at the moment. Okay, you may want to bump NMBCLUSTERS. > > You might want to collect some netstat -m stats as time goes on. In > > addition to being easier to read, it may give you some hints as to how > > high you want to go with mbuf clusters. > > I added a cron job to to netstat -m every half hour... Right now, after 10 > hours of being up: > > 130/1686/2560 mbuf clusters in use (current/peak/max) ^^^^ This is what you care about. If the peak pops above 1670 (2/3 of 2560), you should try bumping NMBCLUSTERS to 4096 or maybe 8192. > This didn't happen in 2.2.8 or 3.1, so I'm trying to figure out what's > causing it. :) NFS could be a little less efficient than in previous versions. [...] > #11 0xc015c382 in m_retryhdr (i=0, t=1) at ../../kern/uipc_mbuf.c:297 > 297 panic("Out of mbuf clusters"); 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 May 28 13:20: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id AF58514F30 for ; Fri, 28 May 1999 13:19:59 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id WAA27777 for current@FreeBSD.ORG; Fri, 28 May 1999 22:19:55 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 3021E87AE; Fri, 28 May 1999 19:59:47 +0200 (CEST) (envelope-from roberto) Date: Fri, 28 May 1999 19:59:47 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? Message-ID: <19990528195947.A93018@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <19990526182800.EGOX7623210.mta2-rme@wocker> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: ; from Dag-Erling Smorgrav on Fri, May 28, 1999 at 02:05:48PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5322 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Dag-Erling Smorgrav: > FTP servers which do not accept passive mode are, IMHO, broken. Their They're broken with respect to RFC-959, not only to your opinion :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #71: Sun May 9 20:16:32 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 14:44: 4 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 630F615291; Fri, 28 May 1999 14:44:03 -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 OAA16611; Fri, 28 May 1999 14:44:58 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Cc: jdp@freebsd.org Subject: Announcing a new cvsup server - cvsup6.freebsd.org Date: Fri, 28 May 1999 14:44:58 -0700 Message-ID: <16607.927927898@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A florida ISP recently donated a T3 connection and a beefy SMP box to us, so I took advantage of this to create another cvsup mirror which allows up to 32 connections. Folks are encouraged to use this site in preference to some of our more loaded cvsup servers (like cvsup1 and cvsup2) and it updates from freefall once an hour, so the bits are nice and fresh. :) This site is also set to become an FTP and www mirror, but we need a bit more disk space first. Those of you who are experienced DNS sleuths as well as hardened baseball fans might also find this site interesting for other reasons (and that's the only clue you guys get). That is all! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 14:53:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 2571D151DF; Fri, 28 May 1999 14:53:46 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id OAA12447; Fri, 28 May 1999 14:47:37 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Fri, 28 May 1999 14:47:37 -0700 Date: Fri, 28 May 1999 14:47:37 -0700 (PDT) From: X-Sender: kip@luna To: "Jordan K. Hubbard" Cc: current@freebsd.org, jdp@freebsd.org Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org In-Reply-To: <16607.927927898@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: jkh@zippy.cdrom.com,current@freebsd.org,jdp@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a warning -- it does not appear to have reverse DNS set up on it. This could be a problem if you try to ever send mail from it. > host cvsup6.freebsd.org cvsup6.freebsd.org is a nickname for hitter.freebsd.org hitter.freebsd.org has address 207.192.64.20 > nslookup 207.192.64.20 Server: ns2-snfc21.pbi.net Address: 206.13.28.12 *** ns2-snfc21.pbi.net can't find 207.192.64.20: Non-existent host/domain On Fri, 28 May 1999, Jordan K. Hubbard wrote: > A florida ISP recently donated a T3 connection and a beefy SMP box to > us, so I took advantage of this to create another cvsup mirror which > allows up to 32 connections. Folks are encouraged to use this site > in preference to some of our more loaded cvsup servers (like cvsup1 > and cvsup2) and it updates from freefall once an hour, so the > bits are nice and fresh. :) > > This site is also set to become an FTP and www mirror, but we need a > bit more disk space first. Those of you who are experienced DNS > sleuths as well as hardened baseball fans might also find this site > interesting for other reasons (and that's the only clue you guys get). > > That is all! > > - Jordan > > > 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 May 28 15:14:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (Postfix) with ESMTP id A7CC714E7C for ; Fri, 28 May 1999 15:14:44 -0700 (PDT) (envelope-from jkb@shell6.ba.best.com) Received: (from jkb@localhost) by shell6.ba.best.com (8.9.3/8.9.2/best.sh) id PAA21334; Fri, 28 May 1999 15:13:55 -0700 (PDT) Message-ID: <19990528151355.A20812@best.com> Date: Fri, 28 May 1999 15:13:55 -0700 From: "Jan B. Koum " To: Dag-Erling Smorgrav Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <16256.927715821@zippy.cdrom.com> <19990528020541.D8308@best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Dag-Erling Smorgrav on Fri, May 28, 1999 at 02:09:19PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 28, 1999 at 02:09:19PM +0200, Dag-Erling Smorgrav wrote: > "Jan B. Koum " writes: > > Yay! This is awesome. I guess in addition to ftp, the tools and > > libraries you talk about would also include fetch, and other firewall > > not so friendly things? (Would be nice if CVSup can fake FTP_PASSIVE_MODE > > by doing '-P -' too). > > CVSup uses multiplexed mode by default, which means it multiplexes its > various data channels over a single TCP connection. The server does > not (should not) attempt to connect back to the client. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no I know how CVSup works. If you are behind firewall, you need to use "-P -" command line switch. What I am saying, is that it would be nice if CVSup would use passive mode by default now also (like ftp/fetch will). -- Yan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 15:17:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (Postfix) with ESMTP id 742C615353 for ; Fri, 28 May 1999 15:17:35 -0700 (PDT) (envelope-from jkb@shell6.ba.best.com) Received: (from jkb@localhost) by shell6.ba.best.com (8.9.3/8.9.2/best.sh) id PAA21894; Fri, 28 May 1999 15:17:16 -0700 (PDT) Message-ID: <19990528151716.B20812@best.com> Date: Fri, 28 May 1999 15:17:16 -0700 From: "Jan B. Koum " To: Dag-Erling Smorgrav Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <16256.927715821@zippy.cdrom.com> <19990528020541.D8308@best.com> <19990528151355.A20812@best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990528151355.A20812@best.com>; from Jan B. Koum on Fri, May 28, 1999 at 03:13:55PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 28, 1999 at 03:13:55PM -0700, "Jan B. Koum " wrote: > On Fri, May 28, 1999 at 02:09:19PM +0200, Dag-Erling Smorgrav wrote: > > "Jan B. Koum " writes: > > > Yay! This is awesome. I guess in addition to ftp, the tools and > > > libraries you talk about would also include fetch, and other firewall > > > not so friendly things? (Would be nice if CVSup can fake FTP_PASSIVE_MODE > > > by doing '-P -' too). > > > > CVSup uses multiplexed mode by default, which means it multiplexes its > > various data channels over a single TCP connection. The server does > > not (should not) attempt to connect back to the client. > > > > DES > > -- > > Dag-Erling Smorgrav - des@flood.ping.uio.no > > I know how CVSup works. If you are behind firewall, you need to use > "-P -" command line switch. What I am saying, is that it would be nice if > CVSup would use passive mode by default now also (like ftp/fetch will). > > -- Yan Never mind me. I go upgrade now ;) -- Yan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 17:33:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 76F631530A for ; Fri, 28 May 1999 17:33:40 -0700 (PDT) (envelope-from asami@sunrise.cs.berkeley.edu) Received: from bubble.didi.com (sji-ca41-214.ix.netcom.com [209.111.208.214]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id RAA10984; Fri, 28 May 1999 17:34:58 -0700 (PDT) Received: (from asami@localhost) by bubble.didi.com (8.9.2/8.8.8) id RAA02950; Fri, 28 May 1999 17:33:25 -0700 (PDT) (envelope-from asami) Date: Fri, 28 May 1999 17:33:25 -0700 (PDT) Message-Id: <199905290033.RAA02950@bubble.didi.com> To: des@flood.ping.uio.no Cc: junkmale@xtra.co.nz, current@FreeBSD.ORG In-reply-to: (message from Dag-Erling Smorgrav on 28 May 1999 14:05:48 +0200) Subject: Re: FTP passive mode - a new default? From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Dag-Erling Smorgrav * FTP servers which do not accept passive mode are, IMHO, broken. Their * loss. No. The losers will be our users who can't talk to them. I don't have a problem with changing the default as long as there are ways to turn them off easily (read: on a per-port basis). Can we cancel an environment variable set in /etc/login.conf from a Makefile? -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 17:40:58 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 E309814C19 for ; Fri, 28 May 1999 17:40:51 -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 CAA07786; Sat, 29 May 1999 02:40:34 +0200 (CEST) (envelope-from des) To: "Jan B. Koum " Cc: Dag-Erling Smorgrav , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <16256.927715821@zippy.cdrom.com> <19990528020541.D8308@best.com> <19990528151355.A20812@best.com> From: Dag-Erling Smorgrav Date: 29 May 1999 02:40:33 +0200 In-Reply-To: "Jan B. Koum "'s message of "Fri, 28 May 1999 15:13:55 -0700" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jan B. Koum " writes: > I know how CVSup works. If you are behind firewall, you need to use > "-P -" command line switch. [...] No. I use CVSup from behind a firewall daily (actually, 23 times a day on one box and 24 times a day on another) without any fancy switches. 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 Fri May 28 17:44: 4 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 C7F5D14C19; Fri, 28 May 1999 17:43:59 -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 CAA07813; Sat, 29 May 1999 02:43:57 +0200 (CEST) (envelope-from des) To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Cc: junkmale@xtra.co.nz, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <199905290033.RAA02950@bubble.didi.com> From: Dag-Erling Smorgrav Date: 29 May 1999 02:43:57 +0200 In-Reply-To: asami@FreeBSD.ORG's message of "Fri, 28 May 1999 17:33:25 -0700 (PDT)" Message-ID: Lines: 19 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) writes: > * From: Dag-Erling Smorgrav > > * FTP servers which do not accept passive mode are, IMHO, broken. Their > * loss. > > No. The losers will be our users who can't talk to them. > > I don't have a problem with changing the default as long as there are > ways to turn them off easily (read: on a per-port basis). Can we > cancel an environment variable set in /etc/login.conf from a Makefile? If we just set FTP_PASSIVE_MODE=YES in /etc/login.conf or /etc/profile, all the user needs to do is set FTP_PASSIVE_MODE=NO before trying to fetch the port. 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 Fri May 28 17:49:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id DDFB31546F for ; Fri, 28 May 1999 17:49:41 -0700 (PDT) (envelope-from asami@sunrise.cs.berkeley.edu) Received: from bubble.didi.com (sji-ca41-214.ix.netcom.com [209.111.208.214]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id RAA11004; Fri, 28 May 1999 17:51:01 -0700 (PDT) Received: (from asami@localhost) by bubble.didi.com (8.9.2/8.8.8) id RAA02997; Fri, 28 May 1999 17:49:35 -0700 (PDT) (envelope-from asami) Date: Fri, 28 May 1999 17:49:35 -0700 (PDT) Message-Id: <199905290049.RAA02997@bubble.didi.com> To: des@flood.ping.uio.no Cc: junkmale@xtra.co.nz, current@FreeBSD.ORG In-reply-to: (message from Dag-Erling Smorgrav on 29 May 1999 02:43:57 +0200) Subject: Re: FTP passive mode - a new default? From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Dag-Erling Smorgrav * > I don't have a problem with changing the default as long as there are * > ways to turn them off easily (read: on a per-port basis). Can we * > cancel an environment variable set in /etc/login.conf from a Makefile? * * If we just set FTP_PASSIVE_MODE=YES in /etc/login.conf or * /etc/profile, all the user needs to do is set FTP_PASSIVE_MODE=NO * before trying to fetch the port. No. This is from libftpio/ftpio.c: === static void check_passive(FILE *fp) { if (getenv("FTP_PASSIVE_MODE")) ftpPassive(fp, TRUE); } === Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 17:57:46 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 D669614D77; Fri, 28 May 1999 17:57:36 -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 CAA07860; Sat, 29 May 1999 02:57:34 +0200 (CEST) (envelope-from des) To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Cc: junkmale@xtra.co.nz, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <199905290049.RAA02997@bubble.didi.com> From: Dag-Erling Smorgrav Date: 29 May 1999 02:57:33 +0200 In-Reply-To: asami@FreeBSD.ORG's message of "Fri, 28 May 1999 17:49:35 -0700 (PDT)" Message-ID: Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) writes: > No. This is from libftpio/ftpio.c: Libftpio will shortly be deprecated. 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 Fri May 28 18:10:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (Postfix) with ESMTP id A676114EBE for ; Fri, 28 May 1999 18:10:19 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (hidden-user@216-99-199-225.cust.aracnet.com [216.99.199.225]) by mail4.aracnet.com (8.9.1/8.9.1) with SMTP id SAA00738 for ; Fri, 28 May 1999 18:10:25 -0700 Message-ID: <018b01bea970$5566bbe0$0d787880@tapang> From: "Carlos C. Tapang" To: Subject: Anybody working on dset utility for ELF? Date: Fri, 28 May 1999 18:12:33 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0188_01BEA935.A88E4710" 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 is a multi-part message in MIME format. ------=_NextPart_000_0188_01BEA935.A88E4710 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Is there anybody out there working on making /sbin/dset recognize ELF = kernel files? I need it, so if there is nobody, I'm going to work on it = myself. If you are familiar with this, please give me pointers or hints as to = how best to do this. Carlos C. Tapang http://www.genericwindows.com ------=_NextPart_000_0188_01BEA935.A88E4710 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Is there anybody out there working on = making=20 /sbin/dset recognize ELF kernel files? I need it, so if there is nobody, = I'm=20 going to work on it myself.
 
If you are familiar with this, please = give me=20 pointers or hints as to how best to do this.
 
Carlos C. Tapang
http://www.genericwindows.com<= /FONT>
------=_NextPart_000_0188_01BEA935.A88E4710-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 18:13:19 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 E8D6215B4A; Fri, 28 May 1999 18:13:01 -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 SAA17595; Fri, 28 May 1999 18:13:57 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Dag-Erling Smorgrav Cc: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami), junkmale@xtra.co.nz, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? In-reply-to: Your message of "29 May 1999 02:43:57 +0200." Date: Fri, 28 May 1999 18:13:56 -0700 Message-ID: <17591.927940436@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If we just set FTP_PASSIVE_MODE=YES in /etc/login.conf or > /etc/profile, all the user needs to do is set FTP_PASSIVE_MODE=NO > before trying to fetch the port. Heh, no. UTSL. All the code which checks this, checks to see if it's set to anything at all, not if it's set explicitly to YES. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 18:20:23 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 DE64A14CE3; Fri, 28 May 1999 18:20:20 -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 DAA07970; Sat, 29 May 1999 03:20:09 +0200 (CEST) (envelope-from des) To: "Jordan K. Hubbard" Cc: Dag-Erling Smorgrav , asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami), junkmale@xtra.co.nz, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <17591.927940436@zippy.cdrom.com> From: Dag-Erling Smorgrav Date: 29 May 1999 03:20:08 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of "Fri, 28 May 1999 18:13:56 -0700" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > > If we just set FTP_PASSIVE_MODE=YES in /etc/login.conf or > > /etc/profile, all the user needs to do is set FTP_PASSIVE_MODE=NO > > before trying to fetch the port. > Heh, no. UTSL. All the code which checks this, checks to see if it's > set to anything at all, not if it's set explicitly to YES. :) In that case, the source is wrong. 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 Fri May 28 18:20:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 84C7614DD5 for ; Fri, 28 May 1999 18:20:27 -0700 (PDT) (envelope-from asami@sunrise.cs.berkeley.edu) Received: from bubble.didi.com (sji-ca41-214.ix.netcom.com [209.111.208.214]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id SAA11055; Fri, 28 May 1999 18:21:30 -0700 (PDT) Received: (from asami@localhost) by bubble.didi.com (8.9.2/8.8.8) id SAA03114; Fri, 28 May 1999 18:19:16 -0700 (PDT) (envelope-from asami) Date: Fri, 28 May 1999 18:19:16 -0700 (PDT) Message-Id: <199905290119.SAA03114@bubble.didi.com> To: des@flood.ping.uio.no Cc: junkmale@xtra.co.nz, current@FreeBSD.ORG In-reply-to: (message from Dag-Erling Smorgrav on 29 May 1999 02:57:33 +0200) Subject: Re: FTP passive mode - a new default? From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Dag-Erling Smorgrav * Libftpio will shortly be deprecated. Fine. Just make sure /etc/login.conf is not updated too early then. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 18:20:38 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 DA56D15B40; Fri, 28 May 1999 18:20:31 -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 SAA17674; Fri, 28 May 1999 18:21:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Dag-Erling Smorgrav Cc: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami), junkmale@xtra.co.nz, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? In-reply-to: Your message of "29 May 1999 02:57:33 +0200." Date: Fri, 28 May 1999 18:21:23 -0700 Message-ID: <17670.927940883@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, if we're replacing it with libfetch then either fetch(1) or libfetch(3) need to check it too. At the moment, neither does - I just checked. :-) - Jordan > asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) writes: > > No. This is from libftpio/ftpio.c: > > Libftpio will shortly be deprecated. > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 18:23:43 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 2325F14E3A; Fri, 28 May 1999 18:23:41 -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 SAA17707; Fri, 28 May 1999 18:23:54 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Dag-Erling Smorgrav Cc: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami), junkmale@xtra.co.nz, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? In-reply-to: Your message of "29 May 1999 03:20:08 +0200." Date: Fri, 28 May 1999 18:23:54 -0700 Message-ID: <17703.927941034@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No, you're the one who's wrong, the source is simply the source. :-) My only point was that you should make sure something is a certain way before you offer advice for dealing with its *current* behavior since, otherwise, that's just confusing to everyone. Either way, I don't think that *any* of the current sources, from libfetch to libftpio, are currently doing anything "right" with FTP_PASSIVE_MODE and hence this debate is also 100% academic for the time being. :-) - Jordan > "Jordan K. Hubbard" writes: > > > If we just set FTP_PASSIVE_MODE=YES in /etc/login.conf or > > > /etc/profile, all the user needs to do is set FTP_PASSIVE_MODE=NO > > > before trying to fetch the port. > > Heh, no. UTSL. All the code which checks this, checks to see if it's > > set to anything at all, not if it's set explicitly to YES. :) > > In that case, the source is wrong. > > 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 Fri May 28 18:24:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (Postfix) with ESMTP id 2133814E3A for ; Fri, 28 May 1999 18:24:24 -0700 (PDT) (envelope-from jkb@shell6.ba.best.com) Received: (from jkb@localhost) by shell6.ba.best.com (8.9.3/8.9.2/best.sh) id SAA19716; Fri, 28 May 1999 18:23:54 -0700 (PDT) Message-ID: <19990528182354.A18352@best.com> Date: Fri, 28 May 1999 18:23:54 -0700 From: "Jan B. Koum " To: "Carlos C. Tapang" , freebsd-current@FreeBSD.ORG Subject: Re: Anybody working on dset utility for ELF? References: <018b01bea970$5566bbe0$0d787880@tapang> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <018b01bea970$5566bbe0$0d787880@tapang>; from Carlos C. Tapang on Fri, May 28, 1999 at 06:12:33PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 28, 1999 at 06:12:33PM -0700, "Carlos C. Tapang" wrote: > Is there anybody out there working on making /sbin/dset recognize ELF kernel files? > I need it, so if there is nobody, I'm going to work on it myself. > > If you are familiar with this, please give me pointers or hints as to how best to do this. > > Carlos C. Tapang > http://www.genericwindows.com Uhm.. I thought that is what /sbin/kget does, no?! -- Yan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 18:26:10 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 6FD8714EBE; Fri, 28 May 1999 18:26:03 -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 DAA08020; Sat, 29 May 1999 03:25:55 +0200 (CEST) (envelope-from des) To: "Jordan K. Hubbard" Cc: Dag-Erling Smorgrav , asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami), junkmale@xtra.co.nz, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <17670.927940883@zippy.cdrom.com> From: Dag-Erling Smorgrav Date: 29 May 1999 03:25:55 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of "Fri, 28 May 1999 18:21:23 -0700" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > Well, if we're replacing it with libfetch then either fetch(1) or > libfetch(3) need to check it too. At the moment, neither does - I > just checked. :-) Umm, I'm kinda embarassed. The 19990529 patchkit fixes that :) 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 Fri May 28 18:27:23 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 25C3314EBE for ; Fri, 28 May 1999 18:27:21 -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 SAA17755 for ; Fri, 28 May 1999 18:28:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: Interesting bogons from last night's 4.0 snapshot. Date: Fri, 28 May 1999 18:28:19 -0700 Message-ID: <17751.927941299@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bogon #1: Userconfig doesn't appear to work - change anything at all and you're looking at a kernel panic when you exit. Hmmm! Bogon #2: "Correcting Natoma for non-SMP configuration" message on SMP boxes is now printed twice (once for each CPU? :). Bogon #3: bt_isa_probe: Probe failed for card at 0xNNN Where NNN is 6 different addresses. The driver should never be this chatty unless bootverbose is set. JFYI - don't want us getting *too* complacent with -current now, do we? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 19:19: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (Postfix) with ESMTP id 073C215370 for ; Fri, 28 May 1999 19:19:00 -0700 (PDT) (envelope-from ctapang@easystreet.com) Received: from apex (hidden-user@216-99-199-225.cust.aracnet.com [216.99.199.225]) by mail4.aracnet.com (8.9.1/8.9.1) with SMTP id TAA05058 for ; Fri, 28 May 1999 19:19:03 -0700 Message-ID: <01d601bea979$ede9ebe0$0d787880@tapang> From: "Carlos C. Tapang" To: Subject: Anybody working on dset for ELF? (resend) Date: Fri, 28 May 1999 19:21:11 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" 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 Sorry I had to do this again. I sent the first one in html format, which most mail readers don't support. Is there anybody upgrading dset to work with ELF kernels? If not, I'd like to work on it myself. If you are familiar with this, please give me pointers or hints. Thanks. Carlos C. Tapang http://www.genericwindows.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 19:19:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kt.rim.or.jp (mail.kt.rim.or.jp [202.247.130.53]) by hub.freebsd.org (Postfix) with ESMTP id C6DBD1538F for ; Fri, 28 May 1999 19:19:50 -0700 (PDT) (envelope-from kuriyama@sky.rim.or.jp) Received: from moon.sky.rim.or.jp (ppp534.kt.rim.or.jp [202.247.140.184]) by mail.kt.rim.or.jp (8.8.8/3.6W-RIMNET-98-06-09) with ESMTP id LAA12871 for ; Sat, 29 May 1999 11:19:49 +0900 (JST) Received: from sky.rim.or.jp (earth.sky.rim.or.jp [192.168.1.2]) by moon.sky.rim.or.jp (8.8.8/3.5Wpl4/moon-1.0) with ESMTP id LAA01233 for ; Sat, 29 May 1999 11:19:48 +0900 (JST) Message-ID: <374F4E89.68CEAEBA@sky.rim.or.jp> Date: Sat, 29 May 1999 11:18:49 +0900 From: Jun Kuriyama X-Mailer: Mozilla 4.51 [ja] (Win95; I) X-Accept-Language: ja MIME-Version: 1.0 To: FreeBSD-current Subject: Invocating as at "gcc -pipe filename.s" Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my 3.1-REL and 3.1-STABLE-19990331 systems, invocation of gas at "gcc -pipe" is not treated correctly. For example, on my 2.2.8-STABLE system says, ----- moon: {101} touch test.s moon: {102} gcc -v -pipe test.s gcc version 2.7.2.1 /usr/bin/as -o /var/tmp/ccsU37121.o test.s /usr/bin/ld -e start -dc -dp /usr/lib/crt0.o -L/usr/libdata/gcc /var/tmp/ccsU37 121.o /usr/lib/libgcc.a -lc /usr/lib/libgcc.a /usr/lib/crt0.o: Undefined symbol `_main' referenced from text segment moon: {103} ----- gcc doesn't use -pipe option when passes test.s to /usr/bin/as. But on my 3.1-RELEASE system, ----- leda: {100} touch test.s leda: {101} gcc -v -pipe test.s gcc version 2.7.2.1 /usr/libexec/elf/as -v -o /var/tmp/ccjoC3551.o test.s - GNU assembler version 2.9.1 (i386-unknown-freebsdelf), using BFD version 2.9.1 ^C leda: {102} ----- gcc passes test.s and "-" to /usr/libexec/elf/as. With these arguments, /usr/libexec/elf/as waits source from stdin (but "-" should be "--"). Does anyone know that this problem may occur on recent -current system? # Sorry, I have no -current system for testing now. -- Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@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 May 28 19:24:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from homer.talcom.net (unknown [209.5.1.4]) by hub.freebsd.org (Postfix) with ESMTP id AF06D1538F for ; Fri, 28 May 1999 19:24:51 -0700 (PDT) (envelope-from leo@homer.talcom.net) Received: (from leo@localhost) by homer.talcom.net (8.8.8/8.8.5) id WAA07697 for current@freebsd.org; Fri, 28 May 1999 22:27:54 -0400 (EDT) Date: Fri, 28 May 1999 22:27:54 -0400 From: Leo Papandreou To: current@freebsd.org Subject: Re: FTP passive mode - a new default? Message-ID: <19990528222754.A6792@homer.talcom.net> References: <16256.927715821@zippy.cdrom.com> <19990528020541.D8308@best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990528020541.D8308@best.com>; from Jan B. Koum on Fri, May 28, 1999 at 02:05:41AM -0700 X-No-Archive: Yes X-Organization: Not very, no. X-Wife: Forgotten but not gone. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, May 26, 1999 at 03:50:21AM -0700, "Jordan K. Hubbard" wrote: > > Unless I hear unanimous fierce outcry against it, I'm strongly > > considering making FTP_PASSIVE_MODE obsolete by virtue of being the > > default for all tools/libraries which currently examine it. > > FTP_ACTIVE_MODE will be the new flag for toggling the previous > > behavior. > > > > Given the state of the Internet today, I think this is purely a > > sensible change in defaults. Comments? It would be nice if the various ports that support ftp URLs have their configuration files updated to use passive ftp before current becomes a release. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 20: 2: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 A4CCE15047; Fri, 28 May 1999 20:02:01 -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 XAA24867; Fri, 28 May 1999 23:01:50 -0400 (EDT) (envelope-from wollman) Date: Fri, 28 May 1999 23:01:50 -0400 (EDT) From: Garrett Wollman Message-Id: <199905290301.XAA24867@khavrinen.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, jdp@FreeBSD.ORG Subject: Announcing a new cvsup server - cvsup6.freebsd.org In-Reply-To: <16607.927927898@zippy.cdrom.com> References: <16607.927927898@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > [...] create another cvsup mirror which allows up to 32 connections. > Folks are encouraged to use this site in preference to some of our > more loaded cvsup servers (like cvsup1 and cvsup2) and it updates > from freefall once an hour, so the bits are nice and fresh. :) cvsup3 allows 24 connections (max 3 per /24, unlimited within MIT). If you're connected to the vBNS, it's probably your best choice as we're only four 100-Mbit/s hops away from MIT's vBNS connection. Likewise ESnet (hi, Guy!). -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 Fri May 28 21: 7:13 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 AEDF8151B5 for ; Fri, 28 May 1999 21:07:11 -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 VAA18231; Fri, 28 May 1999 21:08:08 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Carlos C. Tapang" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Anybody working on dset for ELF? (resend) In-reply-to: Your message of "Fri, 28 May 1999 19:21:11 PDT." <01d601bea979$ede9ebe0$0d787880@tapang> Date: Fri, 28 May 1999 21:08:08 -0700 Message-ID: <18227.927950888@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dset is no longer required for ELF kernels - see kget instead. - Jordan > Sorry I had to do this again. I sent the first one in html format, which > most mail readers don't support. > > Is there anybody upgrading dset to work with ELF kernels? If not, I'd like > to work on it myself. > > If you are familiar with this, please give me pointers or hints. Thanks. > > Carlos C. Tapang > http://www.genericwindows.com > > > > 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 May 28 21:40:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from deep-thought.demos.su (deep-thought.demos.su [194.87.1.76]) by hub.freebsd.org (Postfix) with ESMTP id CDD4114CB6 for ; Fri, 28 May 1999 21:40:52 -0700 (PDT) (envelope-from ache@deep-thought.demos.su) Received: (from ache@localhost) by deep-thought.demos.su (8.9.3/8.9.3) id IAA64767; Sat, 29 May 1999 08:40:45 +0400 (MSD) (envelope-from ache) Date: Sat, 29 May 1999 08:40:44 +0400 From: "Andrey A. Chernov" To: Dmitrij Tejblum Cc: current@FreeBSD.ORG Subject: savecore too (Re: kvm_getswapinfo is broken) Message-ID: <19990529084042.A64683@nagual.pp.ru> References: <19990526090810.A23737@nagual.pp.ru> <199905262209.CAA01936@tejblum.dnttm.rssi.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199905262209.CAA01936@tejblum.dnttm.rssi.ru>; from dima@tejblum.dnttm.rssi.ru on Thu, May 27, 1999 at 02:09:14AM +0400 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 27, 1999 at 02:09:14AM +0400, Dmitrij Tejblum wrote: > This is a known problem. It is because dev_t in kernel and dev_t and > userland are now different things. This is worse on the alpha, where > they also have different sizes. So, on the alpha, the numbers are broken > too, not just device names. Just found that savecore is broken in the same way. What is proper procedure to fix it? I.e. is it must be fixed in the kernel, leaving userland programs as is or in userland, leaving kernel as is? -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 21:55:39 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 987AE14EDA for ; Fri, 28 May 1999 21:55:34 -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 OAA48182; Sat, 29 May 1999 14:25:22 +0930 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990528182354.A18352@best.com> Date: Sat, 29 May 1999 14:25:22 +0930 (CST) From: "Daniel J. O'Connor" To: "Jan B. Koum" Subject: Re: Anybody working on dset utility for ELF? Cc: freebsd-current@FreeBSD.ORG, "Carlos C. Tapang" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-May-99 Jan B. Koum wrote: > Uhm.. I thought that is what /sbin/kget does, no?! It would appear so (I didn't even know kget existed :) But it isn't in any .rc files, so presumably it isn't automagic. Presumably it would be trivial to add though, ie have 'kget /boot/kernel.conf' somewhere in /etc/rc.* ie in /etc/rc.local have -> echo -n 'saving boot -c changes..' /sbin/kget /boot/kernel.conf echo 'done' --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 28 22:19:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 595B315345 for ; Fri, 28 May 1999 22:19:45 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id OAA07075 for current@freebsd.org; Sat, 29 May 1999 14:49:44 +0930 (CST) (envelope-from newton) Date: Sat, 29 May 1999 14:49:44 +0930 (CST) From: Mark Newton Message-Id: <199905290519.OAA07075@gizmo.internode.com.au> To: current@freebsd.org Subject: NFS diskless on -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried to upgrade my diskless router this afternoon to -current as cvsupped last night. I can't make it boot, though. The configuration it has been using since it was last rebuilt from Feb 24's -current (and which has been working for longer than I care to remember) is: - /etc/bootptab features: yeahwhatever:\ :ha=000021409773:\ :ip=YYY.YYY.YYY.YYY:\ :sm=255.255.255.240:\ :ht=ether:\ :sa=XXX.XXX.XXX.XXX: - /tftpboot/freebsd.YYY.YYY.YYY.YYY specifies: hostname yeahwhatever netmask 255.255.255.240 rootfs XXX.XXX.XXX.XXX:/export/root/dotat swapfs XXX.XXX.XXX.XXX:/export/swap/dotat swapsize 20480 - kernel config mentions NFS_ROOT and NFS. - kernel built with KERNFORMAT=aout ('cos loader is too stupid to do NFS just now). It now panics with "Can't mount root" when I boot it. And yes, I have updated the kernel config for new-bus. I noticed the BOOTP stuff in LINT, but that's been there for a while and I've never needed to use it before. I turned it on anyway just to see what happens, but tcpdump doesn't show it sending any bootp requests. I'm obviously missing something really stupid. Would anyone care to educate me about changes to diskless booting with NFS root filesystems since February 24? - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 2: 0:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id 9E7751539B for ; Sat, 29 May 1999 02:00:48 -0700 (PDT) (envelope-from npp@swamp.dk) Received: from petri (fw.micon.dk [195.249.147.131]) by distortion.dk (8.9.1/8.9.1) with SMTP id MAA03489 for ; Sat, 29 May 1999 12:34:59 +0200 (CEST) (envelope-from npp@swamp.dk) Message-ID: <002201bea9b1$f0772c00$6535a8c0@petri> From: "Nicolai Petri" To: Subject: kldload (module parameters ??) Date: Sat, 29 May 1999 10:50:55 +0200 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 Would it be possible and wise to implement a way to pass parameters to modules when they are loaded ?? Like "kldload if_olp -recv_debug" ? ----- Nicolai Petri npp@swamp.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 3: 5:14 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 0044615073 for ; Sat, 29 May 1999 03:05:10 -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 MAA11787; Sat, 29 May 1999 12:04:07 +0200 (CEST) (envelope-from des) To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: kvm_getswapinfo is broken References: <19990526090810.A23737@nagual.pp.ru> From: Dag-Erling Smorgrav Date: 29 May 1999 12:04:06 +0200 In-Reply-To: "Andrey A. Chernov"'s message of "Wed, 26 May 1999 09:08:11 +0400" Message-ID: Lines: 22 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" writes: > Just check 'swapinfo' in recent -current, it shows "/dev/(null)" as swap > device, it means that devinfo() call in kvm_getswapinfo() returns NULL, > i.e. called with wrong argument which is swinfo.sw_dev Other interesting swapinfo(8) behaviour: root(yeshs-3)--# uname -a FreeBSD yeshs-3.yes.no 3.1-19990505-STABLE FreeBSD 3.1-19990505-STABLE #1: Wed May 19 01:13:59 CEST 1999 root@yeshs-3.yes.no:/usr/src/sys/compile/YESHS i386 root(yeshs-3)--# swapinfo Device 1K-blocks Used Avail Capacity Type /dev/od0b 524288 0 524160 0% Interleaved /dev/da1b 524288 0 524160 0% Interleaved /dev/da2b 524288 0 524160 0% Interleaved Total 1572480 0 1572480 0% (before you ask - no, this machine does *not* swap to a magneto- optiocal disk, and magneto-optical devices aren't named od any more) 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 Sat May 29 3:13:41 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 4BD8C15206 for ; Sat, 29 May 1999 03:13: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 MAA11801; Sat, 29 May 1999 12:13:30 +0200 (CEST) (envelope-from des) To: Mike Smith Cc: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: splash screen broken?? References: <199905281623.JAA00805@dingo.cdrom.com> From: Dag-Erling Smorgrav Date: 29 May 1999 12:13:30 +0200 In-Reply-To: Mike Smith's message of "Fri, 28 May 1999 09:23:27 -0700" Message-ID: Lines: 17 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > module_register_init: MOD_LOAD (splash_bmp, c028162c, 0) error 19 > That's what we needed to see. Error 19 is ENODEV; this means you > either don't have VESA support compiled in, haven't loaded the VESA > module, or your VESA BIOS doesn't support a mode that allows > a 300x200x8 image to be displayed. 320x200x8 has nothing to do with VESA. If no VESA modes are available, splash_bmp falls back to M_VGA_CG320, which should be available on all VGA compatible frame buffers. ENODEV from splash_bmp can also mean that no image is loaded, or that the image is invalid. 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 Sat May 29 3:18:28 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 0FC2814FEE for ; Sat, 29 May 1999 03:18:25 -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 MAA11849; Sat, 29 May 1999 12:18:20 +0200 (CEST) (envelope-from des) To: Ollivier Robert Cc: current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <19990526182800.EGOX7623210.mta2-rme@wocker> <19990528195947.A93018@keltia.freenix.fr> From: Dag-Erling Smorgrav Date: 29 May 1999 12:18:19 +0200 In-Reply-To: Ollivier Robert's message of "Fri, 28 May 1999 19:59:47 +0200" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert writes: > According to Dag-Erling Smorgrav: > > FTP servers which do not accept passive mode are, IMHO, broken. Their > They're broken with respect to RFC-959, not only to your opinion :-) No. Allowable responses to the PASV command include 227 (Entering passive mode), 500 (Unrecognized command), 501 (Invalid parameters), 502 (Command not implemented), 421 (Service not available), and 530 (Not logged in). A server which does not wish to allow passive mode can thus choose to acknowledge the command but refuse to obey it (502), or to reject the command altogether (500). 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 Sat May 29 3:21:44 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 AB6EE1545D; Sat, 29 May 1999 03:21:40 -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 MAA11860; Sat, 29 May 1999 12:21:34 +0200 (CEST) (envelope-from des) To: "Jordan K. Hubbard" Cc: Dag-Erling Smorgrav , asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami), junkmale@xtra.co.nz, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <17703.927941034@zippy.cdrom.com> From: Dag-Erling Smorgrav Date: 29 May 1999 12:21:33 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of "Fri, 28 May 1999 18:23:54 -0700" Message-ID: Lines: 30 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > My only point was that you should make sure something is a certain way > before you offer advice for dealing with its *current* behavior since, > otherwise, that's just confusing to everyone. Either way, I don't > think that *any* of the current sources, from libfetch to libftpio, > are currently doing anything "right" with FTP_PASSIVE_MODE and hence > this debate is also 100% academic for the time being. :-) So let's *make* them Do The Right Thing. That's what commit privs are for, after all. des@des ~$ stable FTP_PASSIVE_MODE src/lib/libfetch/ftp.c: #define FTP_PASSIVE_MODE 227 src/lib/libfetch/ftp.c: if ((e = _ftp_cmd(cf, "PASV" ENDL)) != FTP_PASSIVE_MODE) src/lib/libftpio/ftpio.3: .Bl -tag -width FTP_PASSIVE_MODE -offset 123 src/lib/libftpio/ftpio.3: .It Ev FTP_PASSIVE_MODE src/lib/libftpio/ftpio.c: if (getenv("FTP_PASSIVE_MODE")) src/usr.bin/fetch/fetch.1: .Bl -tag -width FTP_PASSIVE_MODE -offset indent src/usr.bin/fetch/fetch.1: .It Ev FTP_PASSIVE_MODE src/usr.bin/ftp/ftp.1: .Bl -tag -width "FTP_PASSIVE_MODE" src/usr.bin/ftp/ftp.1: .It Ev FTP_PASSIVE_MODE src/usr.bin/ftp/main.c: if (getenv("FTP_PASSIVE_MODE") || strcmp(cp, "pftp") == 0) src/usr.sbin/pkg_install/add/pkg_add.1: FTP_PASSIVE_MODE Looks like ftpio(3) and ftp(1) both Do The Wrong Thing. Should be trivial to fix, but I have a train to catch right now :) 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 Sat May 29 4: 6: 8 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 CD30F14C44 for ; Sat, 29 May 1999 04:06:04 -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 VAA24214; Sat, 29 May 1999 21:06:03 +1000 Date: Sat, 29 May 1999 21:06:03 +1000 From: Bruce Evans Message-Id: <199905291106.VAA24214@godzilla.zeta.org.au> To: current@FreeBSD.ORG, newton@internode.com.au Subject: Re: NFS diskless on -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I'm obviously missing something really stupid. Would anyone care to >educate me about changes to diskless booting with NFS root filesystems >since February 24? rootdev is now correctly initialised to NODEV, but vfs_mountrootfs() still uses NODEV to terminate the list of root devices to try. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 5:13:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from cons.org (knight.cons.org [194.233.237.195]) by hub.freebsd.org (Postfix) with ESMTP id 5926214E09 for ; Sat, 29 May 1999 05:13:24 -0700 (PDT) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id OAA04795; Sat, 29 May 1999 14:13:18 +0200 (CEST) Date: Sat, 29 May 1999 14:13:18 +0200 From: Martin Cracauer To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: FP exceptions broken (Re: Interesting bogons from last night's 4.0 snapshot.) Message-ID: <19990529141318.A4777@cons.org> References: <17751.927941299@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <17751.927941299@zippy.cdrom.com>; from Jordan K. Hubbard on Fri, May 28, 1999 at 06:28:19PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <17751.927941299@zippy.cdrom.com>, Jordan K. Hubbard wrote: [...] > JFYI - don't want us getting *too* complacent with -current now, do we? :-) Floating point exceptions are also broken, they always behave like masked, even if you unmask some explicitly with fpsetmask(). Even worse, a wrong result is returned if an exception had to be thrown, while the result is right for masked exceptions. #include #include #include int main(void) { fpsetmask(0); fprintf(stderr, "I want no exception, but an exception value\n"); fprintf(stderr, "res: %g\n", atof("1.0") / atof("0.0")); fpsetmask(FP_X_INV|FP_X_DNML|FP_X_DZ|FP_X_OFL|FP_X_UFL); fprintf(stderr, "I want an exception. Or at least an exceptional value\n"); fprintf(stderr, "res: %g\n", atof("1.0") / atof("0.0")); fprintf(stderr, "I didn't get one!\n"); return 0; } output on -current: I want no exception, but an exception value res: Inf I want an exception. Or at least an exception value res: 1 I didn't get one! output on anything else: I want no exception, but an exception value res: Inf I want an exception. Or at least an exception value Floating point exception (core dumped) Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 5:21:30 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 6D5D21522E for ; Sat, 29 May 1999 05:21:25 -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 WAA28838; Sat, 29 May 1999 22:21:11 +1000 Date: Sat, 29 May 1999 22:21:11 +1000 From: Bruce Evans Message-Id: <199905291221.WAA28838@godzilla.zeta.org.au> To: ache@nagual.pp.ru, dima@tejblum.dnttm.rssi.ru Subject: Re: savecore too (Re: kvm_getswapinfo is broken) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Just found that savecore is broken in the same way. What is proper >procedure to fix it? I.e. is it must be fixed in the kernel, leaving >userland programs as is or in userland, leaving kernel as is? The kernel needs to maintain (or create as necessary for return by sysctl()) udev_t versions of most (all?) device numbers that are accessed in userland. I think the proper way to do this will be to maintain a udev_t for each dev_t in the kernel too. udev_t should be named dev_t, the current dev_t should be named something like kdev_t and should be a pointer to a struct containing the (user) dev_t. The kernel needs something like this for fast conversions in old interfaces like stat(2). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 5:43:36 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 6B10B1522E for ; Sat, 29 May 1999 05:43:32 -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 WAA30183; Sat, 29 May 1999 22:43:22 +1000 Date: Sat, 29 May 1999 22:43:22 +1000 From: Bruce Evans Message-Id: <199905291243.WAA30183@godzilla.zeta.org.au> To: cracauer@cons.org, jkh@zippy.cdrom.com Subject: Re: FP exceptions broken (Re: Interesting bogons from last night's 4.0 snapshot.) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> JFYI - don't want us getting *too* complacent with -current now, do we? :-) > >Floating point exceptions are also broken, they always behave like >masked, even if you unmask some explicitly with fpsetmask(). > >Even worse, a wrong result is returned if an exception had to be >thrown, while the result is right for masked exceptions. This seems to have fixed itself: May 23 kernel: fails May 24 kernel: works May 28 kernel: works For the failing case, the FPU seems to be working properly but no CPU exception 16 is received for the unmasked FPU exception, and CR0_TS is in an unusualy state (not set) at the end of another test program. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 6:42:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 390BE152EB for ; Sat, 29 May 1999 06:42:54 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id JAA08628; Sat, 29 May 1999 09:42:52 -0400 (EDT) Date: Sat, 29 May 1999 09:42:51 -0400 (EDT) From: "Matthew N. Dodd" To: Nicolai Petri Cc: current@FreeBSD.ORG Subject: Re: kldload (module parameters ??) In-Reply-To: <002201bea9b1$f0772c00$6535a8c0@petri> 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, 29 May 1999, Nicolai Petri wrote: > Would it be possible and wise to implement a way to pass parameters to > modules when they are loaded ?? Like "kldload if_olp -recv_debug" ? Use sysctl for this. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 7: 7: 8 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 4FEC515006 for ; Sat, 29 May 1999 07:07:05 -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 QAA10093; Sat, 29 May 1999 16:05:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: ache@nagual.pp.ru, dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG Subject: Re: savecore too (Re: kvm_getswapinfo is broken) In-reply-to: Your message of "Sat, 29 May 1999 22:21:11 +1000." <199905291221.WAA28838@godzilla.zeta.org.au> Date: Sat, 29 May 1999 16:05:08 +0200 Message-ID: <10091.927986708@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199905291221.WAA28838@godzilla.zeta.org.au>, Bruce Evans writes: >>Just found that savecore is broken in the same way. What is proper >>procedure to fix it? I.e. is it must be fixed in the kernel, leaving >>userland programs as is or in userland, leaving kernel as is? > >The kernel needs to maintain (or create as necessary for return by >sysctl()) udev_t versions of most (all?) device numbers that are accessed >in userland. I think the proper way to do this will be to maintain a >udev_t for each dev_t in the kernel too. udev_t should be named dev_t, >the current dev_t should be named something like kdev_t and should be >a pointer to a struct containing the (user) dev_t. The kernel needs >something like this for fast conversions in old interfaces like stat(2). ... But since renaming dev_t in the kernel will totally hose all device driver writers, we don't rename it, but suffer the trouble of the overloaded name. The structure thing will happen RSN. -- 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 May 29 7:16:33 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 5113F15210 for ; Sat, 29 May 1999 07:16:30 -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 QAA12319; Sat, 29 May 1999 16:16:08 +0200 (CEST) (envelope-from des) To: Dag-Erling Smorgrav Cc: Mike Smith , Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: splash screen broken?? References: <199905281623.JAA00805@dingo.cdrom.com> From: Dag-Erling Smorgrav Date: 29 May 1999 16:16:08 +0200 In-Reply-To: Dag-Erling Smorgrav's message of "29 May 1999 12:13:30 +0200" Message-ID: Lines: 17 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > ENODEV from splash_bmp can also mean that no image is loaded, or that > the image is invalid. Specifically, splash_bmp will return ENODEV if one of the following holds: - no image is loaded - the image data has a negative length (!) - the first two bytes are not 0x4d42 - the compression format is not RGB, RLE4 or RLE8 - the image size and / or color depth does not match any supported mode (320x200, 640x480, 800x600 or 1024x768 in 8-bit color) 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 Sat May 29 7:38: 1 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 B884A15231 for ; Sat, 29 May 1999 07:37:57 -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 AAA04536; Sun, 30 May 1999 00:37:46 +1000 Date: Sun, 30 May 1999 00:37:46 +1000 From: Bruce Evans Message-Id: <199905291437.AAA04536@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org, jkh@zippy.cdrom.com Subject: Re: FP exceptions broken (Re: Interesting bogons from last night's 4.0 snapshot.) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> JFYI - don't want us getting *too* complacent with -current now, do we? :-) >> >>Floating point exceptions are also broken, they always behave like >>masked, even if you unmask some explicitly with fpsetmask(). >> >>Even worse, a wrong result is returned if an exception had to be >>thrown, while the result is right for masked exceptions. > >This seems to have fixed itself: > >May 23 kernel: fails >May 24 kernel: works >May 28 kernel: works Actually, it works on a Celeron but fails on a P5. This is caused by the following bug suite (in approximately historical order): 1) IRQ13 interface was broken as designed. 2) Intel F00F bug. 3) Probe for (1) is not very well implemented. It hacks on the idt[] global to context switch some IDT entries. 4) Fix for (2) is not very well implemented. It moves the IDT without hiding idt[] from (3). 5) Rev.1.55 of disturbed the probe order so that (4) is done before (3). This breaks the IDT context switching if the F00F fix gets installed. npx traps and interrupts end up being serviced by the dummy probe routines. The easiest fix is to change the probe order. The F00F fix should never have been attached to proc0 initialisation. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 8: 1:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id B038514CFD for ; Sat, 29 May 1999 08:01:46 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (unknown [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id EEC58246 for ; Sat, 29 May 1999 15:01:26 +0000 (GMT) Date: Sat, 29 May 1999 19:01:26 +0400 (MSD) From: Osokin Sergey To: freebsd-current@FreeBSD.org Subject: pcm for SB 128 PCI in -current is broken... 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! pcm driver for SB 128 PCI in -current is broken... # dmesg | more ..... es0: irq 5 at device 11.0 on pci0 pcm0: using I/O space register mapping at 0xe800 .... play, waveplay, wmsound dont' work correct. Does someone have any idea? And when it fixed? Rgdz, Osokin Sergey aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 9:56:26 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 B146F14CFF for ; Sat, 29 May 1999 09:56:22 -0700 (PDT) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA06340; Sat, 29 May 1999 09:56:17 -0700 (PDT) Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id JAA11770; Sat, 29 May 1999 09:55:55 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199905291655.JAA11770@whistle.com> Subject: Re: NFS diskless on -current In-Reply-To: <199905290519.OAA07075@gizmo.internode.com.au> from Mark Newton at "May 29, 99 02:49:44 pm" To: newton@internode.com.au (Mark Newton) Date: Sat, 29 May 1999 09:55:54 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (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 Mark Newton writes: | I tried to upgrade my diskless router this afternoon to -current as | cvsupped last night. | | I can't make it boot, though. | | It now panics with "Can't mount root" when I boot it. And yes, I have | updated the kernel config for new-bus. | | I noticed the BOOTP stuff in LINT, but that's been there for a while and | I've never needed to use it before. I turned it on anyway just to see | what happens, but tcpdump doesn't show it sending any bootp requests. I have a fix for you based on the MFS mount root problem! Note it is a best guess and works for me. It seems rootdev needs to be defined or it ignores trying to mount it. I ran into this a couple of days ago. Doug A. Index: bootp_subr.c =================================================================== RCS file: /cvs/freebsd/src/sys/nfs/bootp_subr.c,v retrieving revision 1.19 diff -c -r1.19 bootp_subr.c *** bootp_subr.c 1999/01/27 23:45:39 1.19 --- bootp_subr.c 1999/05/29 16:52:14 *************** *** 1043,1048 **** --- 1043,1049 ---- panic("nfs_boot: lookup swap, error=%d", error); } nfs_diskless_valid = 3; + rootdev = makedev(255,0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 11:47:48 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 E397214EA7 for ; Sat, 29 May 1999 11:47:44 -0700 (PDT) (envelope-from cpiazza@home.net) Received: from norn.ca.eu.org (localhost.norn.ca.eu.org [127.0.0.1]) by norn.ca.eu.org (Postfix) with ESMTP id DA037140B; Sat, 29 May 1999 11:47:41 -0700 (PDT) Content-Length: 738 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 29 May 1999 11:47:41 -0700 (PDT) Reply-To: Chris Piazza From: Chris Piazza To: Osokin Sergey Subject: RE: pcm for SB 128 PCI in -current is broken... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-May-99 Osokin Sergey wrote: > > Hello! > pcm driver for SB 128 PCI in -current is broken... ># dmesg | more > ..... > es0: irq 5 at device 11.0 on pci0 > pcm0: using I/O space register mapping at 0xe800 > .... > > play, waveplay, wmsound dont' work correct. > Does someone have any idea? > And when it fixed? That's odd, working here! I just built world and the kernel about an hour ago. A few random thoughts.. did you set the mixer volumes? do you have the right entries in /dev (snd0 in current)? when was this last working? are there any error messages? *Happily playing a wav with waveplay* --- Chris Piazza Abbotsford, BC, Canada cpiazza@home.net finger norn@norn.ca.eu.org for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 13:12: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (Postfix) with ESMTP id EA7DF14C33; Sat, 29 May 1999 13:12:02 -0700 (PDT) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id QAA10534; Sat, 29 May 1999 16:11:59 -0400 (EDT) Date: Sat, 29 May 1999 16:11:59 -0400 From: Christian Kuhtz To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, jdp@FreeBSD.ORG Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org Message-ID: <19990529161158.A9898@ns1.adsu.bellsouth.com> References: <16607.927927898@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <16607.927927898@zippy.cdrom.com>; from Jordan K. Hubbard on Fri, May 28, 1999 at 02:44:58PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 28, 1999 at 02:44:58PM -0700, Jordan K. Hubbard wrote: > A florida ISP recently donated a T3 connection and a beefy SMP box to > us, so I took advantage of this to create another cvsup mirror which > allows up to 32 connections. Folks are encouraged to use this site > in preference to some of our more loaded cvsup servers (like cvsup1 > and cvsup2) and it updates from freefall once an hour, so the > bits are nice and fresh. :) FYI.. cvsup5.freebsd.org (2xXeon, also wearing the hat of cvsup4) is also still not at capacity and welcomes anyone in need of CVSup services, updates are also hourly from freefall. Cheers, Chris -- Christian Kuhtz, Sr. Network Architect BellSouth Corporation -wk, -hm Advanced Data Services "Affiliation given for identification, not representation." Atlanta, GA, U.S. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 15:13: 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 A459314DA3 for ; Sat, 29 May 1999 15:12:59 -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 SAA60467 for ; Sat, 29 May 1999 18:13:00 -0400 (EDT) Date: Sat, 29 May 1999 18:13:00 -0400 (EDT) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: libgcc 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 got an egcs related question here. If it wasn't for the linking, this would be a ports question, but bear with me, you'll see. Anyhow, I was trying to get sp to work, as I continue checking into xml and xsl, so I used the /usr/ports/textproc/sp port. It dies in several places, because it's unable to find the symbol "set_new_handler". This guy is defined in new.h (which points towards "new", which has the very simple code for it). The problem is, the code for it is stuffed into libgcc.a. I thought libgcc was being deprecated, isn't that so? That only libstdc++ was going to be needed? This is a pretty well needed function, so I'm somewhat confused, and hope that some other C++ expert can explain what's happening under egcs these days, with respect to libgcc. ----------------------------+----------------------------------------------- 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 (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 19:40:22 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 55F0F14D5E for ; Sat, 29 May 1999 19:40:15 -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 TAA10609; Sat, 29 May 1999 19:40:14 -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 TAA00740; Sat, 29 May 1999 19:40:13 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sat, 29 May 1999 19:40:13 -0700 (PDT) Message-Id: <199905300240.TAA00740@vashon.polstra.com> To: chuckr@picnic.mat.net Subject: Re: libgcc In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Chuck Robey wrote: > I thought libgcc was being deprecated, isn't that so? That only > libstdc++ was going to be needed? No, I think you're confusing libgcc with libg++. 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 May 29 19:47: 8 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 C072B14FA5 for ; Sat, 29 May 1999 19:47:05 -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 WAA61198; Sat, 29 May 1999 22:46:50 -0400 (EDT) Date: Sat, 29 May 1999 22:46:50 -0400 (EDT) From: Chuck Robey To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: libgcc In-Reply-To: <199905300240.TAA00740@vashon.polstra.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 Sat, 29 May 1999, John Polstra wrote: > In article , > Chuck Robey wrote: > > > I thought libgcc was being deprecated, isn't that so? That only > > libstdc++ was going to be needed? > > No, I think you're confusing libgcc with libg++. Yeah, guess you're right, I was. OK, thanks. > > 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 > ----------------------------+----------------------------------------------- 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 (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 19:57:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from spook.navinet.net (spook.navinet.net [216.67.14.69]) by hub.freebsd.org (Postfix) with ESMTP id 0ECF714FA5 for ; Sat, 29 May 1999 19:57:18 -0700 (PDT) (envelope-from forrie@forrie.com) Received: from boom (forrie.ne.mediaone.net [24.128.72.15]) by spook.navinet.net (8.9.3/8.9.3) with SMTP id WAA32804 for ; Sat, 29 May 1999 22:58:50 -0400 (EDT) Message-Id: <4.1.19990529225641.0091d100@216.67.14.69> X-Sender: forrie@216.67.14.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 29 May 1999 22:58:07 -0400 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Pcmcia support 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 still at 3.2; however, I wonder what plans there are (if any) to have pcmcia support in 4.x (like the 3com 3c574, etc). Might be a good idea to include a pcmcia floppy in the installation media (like Linux already has). Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 23:39:11 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 A99FE14D4E for ; Sat, 29 May 1999 23:39:09 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id XAA18627; Sat, 29 May 1999 23:39:06 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Sat, 29 May 1999 23:39:06 -0700 (PDT) From: Doug White To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: Pcmcia support In-Reply-To: <4.1.19990529225641.0091d100@216.67.14.69> 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, 29 May 1999, Forrest Aldrich wrote: > I'm still at 3.2; however, I wonder what plans there are (if any) to have > pcmcia > support in 4.x (like the 3com 3c574, etc). Might be a good idea to include > a pcmcia floppy in the installation media (like Linux already has). Someone has never discovered PAO, apparently. 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 Sat May 29 23:48:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 9D48E14CB0 for ; Sat, 29 May 1999 23:48:08 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id XAA22753; Sat, 29 May 1999 23:41:49 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sat, 29 May 1999 23:41:49 -0700 Date: Sat, 29 May 1999 23:41:49 -0700 (PDT) From: X-Sender: kip@luna To: Doug White Cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Pcmcia support In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: dwhite@resnet.uoregon.edu,forrie@forrie.com,freebsd-current@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why can't the PAO changes be committed to the main source tree? It would be nice if I could just install the latest version of FreeBSD from the Walnut Creek CD-ROM as is and have PCMCIA and APM support on my laptop without always having to wait for Hosokawa. I asked about this previously and received a disappointingly emotional and uninformative response. On Sat, 29 May 1999, Doug White wrote: > On Sat, 29 May 1999, Forrest Aldrich wrote: > > > I'm still at 3.2; however, I wonder what plans there are (if any) to have > > pcmcia > > support in 4.x (like the 3com 3c574, etc). Might be a good idea to include > > a pcmcia floppy in the installation media (like Linux already has). > > Someone has never discovered PAO, apparently. > > 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 29 23:51:41 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 6DDBE14CB0 for ; Sat, 29 May 1999 23:51:40 -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 XAA35778; Sat, 29 May 1999 23:52:26 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: kip@lyris.com Cc: Doug White , Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Pcmcia support In-reply-to: Your message of "Sat, 29 May 1999 23:41:49 PDT." Date: Sat, 29 May 1999 23:52:26 -0700 Message-ID: <35774.928047146@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why can't the PAO changes be committed to the main source tree? It would > be nice if I could just install the latest version of FreeBSD from > the Walnut Creek CD-ROM as is and have PCMCIA and APM support on my Yes, it would be nice. To make a long story short (and emotionless) there are integration problems which prevent this and I think that's about as much summary information as I need to state here. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 0: 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 3079314CB0 for ; Sun, 30 May 1999 00: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 JAA12549; Sun, 30 May 1999 09:02:13 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: kip@lyris.com Cc: Doug White , Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Pcmcia support In-reply-to: Your message of "Sat, 29 May 1999 23:41:49 PDT." Date: Sun, 30 May 1999 09:02:12 +0200 Message-ID: <12547.928047732@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , kip@lyris.com write s: >Why can't the PAO changes be committed to the main source tree? Because they are, technically speaking, a messy hack. -- 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 Sun May 30 0: 6:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 936A014F76 for ; Sun, 30 May 1999 00:06:20 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id XAA23937; Sat, 29 May 1999 23:59:35 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sat, 29 May 1999 23:59:35 -0700 Date: Sat, 29 May 1999 23:59:35 -0700 (PDT) From: X-Sender: kip@luna To: "Jordan K. Hubbard" Cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Pcmcia support In-Reply-To: <35774.928047146@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: jkh@zippy.cdrom.com,forrie@forrie.com,freebsd-current@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That is the kind of response I like. I don't appreciate being flamed for a reasonable question about something that is not documented in an obvious place. Is it something that I can help with? Or is it more a political issue? Can you send me a pointer to something that goes into more detail? I will be upgrading to -current shortly to keep track of improvements in thread support, my interest, for better or worse, is not purely academic (read business). Even in 3.2-S unpatched libc_r had infinite recursion problems in malloc, fortunately for me, it was easy enough to hack around. On Sat, 29 May 1999, Jordan K. Hubbard wrote: > > Why can't the PAO changes be committed to the main source tree? It would > > be nice if I could just install the latest version of FreeBSD from > > the Walnut Creek CD-ROM as is and have PCMCIA and APM support on my > > Yes, it would be nice. To make a long story short (and emotionless) > there are integration problems which prevent this and I think that's > about as much summary information as I need to state here. > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 0:28: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 2387314C87 for ; Sun, 30 May 1999 00:27:56 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.13) with ESMTP id TAA15194; Sun, 30 May 1999 19:27:53 +1200 (NZST) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.3/8.9.2) id TAA51387; Sun, 30 May 1999 19:27:51 +1200 (NZST) (envelope-from jabley) Date: Sun, 30 May 1999 19:27:51 +1200 From: Joe Abley To: kip@lyris.com Cc: "Jordan K. Hubbard" , Forrest Aldrich , freebsd-current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: Pcmcia support Message-ID: <19990530192751.B51029@clear.co.nz> References: <35774.928047146@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from kip@lyris.com on Sat, May 29, 1999 at 11:59:35PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 29, 1999 at 11:59:35PM -0700, kip@lyris.com wrote: > That is the kind of response I like. I don't appreciate being flamed for a > reasonable question about something that is not documented in an obvious > place. Check the archives for freebsd-current, freebsd-hackers and freebsd-mobile. They're easy to find from www.freebsd.org, and contain numerous extensive threads with all the details. If you _do_ look for these, you will easily see how (a) the apparently hostile responses you got were, in fact, quite mild and (b) why nobody is eager to start another discussion on the subject. I think the correct way of asking "why doesn't someone roll PAO into current" is "I have taken aspect X of APM/PCMCIA/whatever support from PAO, and tidied it up for CURRENT -- the patch is attached, please test". Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 0:38:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 0858014C0E for ; Sun, 30 May 1999 00:38:43 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id AAA24253; Sun, 30 May 1999 00:32:26 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sun, 30 May 1999 00:32:25 -0700 Date: Sun, 30 May 1999 00:32:25 -0700 (PDT) From: X-Sender: kip@luna To: Joe Abley Cc: "Jordan K. Hubbard" , Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Pcmcia support In-Reply-To: <19990530192751.B51029@clear.co.nz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: jabley@clear.co.nz,jkh@zippy.cdrom.com,forrie@forrie.com,freebsd-current@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks. End of discussion. If I am able to tidy up parts of PAO I will do just that. -Kip On Sun, 30 May 1999, Joe Abley wrote: > On Sat, May 29, 1999 at 11:59:35PM -0700, kip@lyris.com wrote: > > That is the kind of response I like. I don't appreciate being flamed for a > > reasonable question about something that is not documented in an obvious > > place. > > Check the archives for freebsd-current, freebsd-hackers and freebsd-mobile. > They're easy to find from www.freebsd.org, and contain numerous extensive > threads with all the details. > > If you _do_ look for these, you will easily see how (a) the apparently > hostile responses you got were, in fact, quite mild and (b) why nobody > is eager to start another discussion on the subject. > > I think the correct way of asking "why doesn't someone roll PAO into > current" is "I have taken aspect X of APM/PCMCIA/whatever support from > PAO, and tidied it up for CURRENT -- the patch is attached, please test". > > > Joe > > > > 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 Sun May 30 1:22: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id AE6AE14D38 for ; Sun, 30 May 1999 01:21:55 -0700 (PDT) (envelope-from npp@swamp.dk) Received: from petri (fw.micon.dk [195.249.147.131]) by distortion.dk (8.9.1/8.9.1) with SMTP id LAA06252 for ; Sun, 30 May 1999 11:56:07 +0200 (CEST) (envelope-from npp@swamp.dk) Message-ID: <007701beaa75$ab2e8200$6535a8c0@petri> From: "Nicolai Petri" To: Subject: Was is status on cardbus ? Date: Sun, 30 May 1999 10:23:13 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 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 Is cardbus work in progress ?? And will newbus designed drivers work without ´larger modifications ? ------------- Nicolai Petri npp@swamp.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 1:32:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id D0ADC14C13; Sun, 30 May 1999 01:32:36 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id SAA16388; Sun, 30 May 1999 18:02:34 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA17226; Sun, 30 May 1999 18:03:34 +0930 Date: Sun, 30 May 1999 18:03:34 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Christian Kuhtz Cc: "Jordan K. Hubbard" , current@freebsd.org, jdp@freebsd.org Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org In-Reply-To: <19990529161158.A9898@ns1.adsu.bellsouth.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 Sat, 29 May 1999, Christian Kuhtz wrote: > FYI.. cvsup5.freebsd.org (2xXeon, also wearing the hat of cvsup4) is also > still not at capacity and welcomes anyone in need of CVSup services, updates > are also hourly from freefall. I was wondering the other day about the feasibility of setting up some kind of load meter for the various cvsup servers, so people could determine the best one to use and share the load a bit more. Perhaps this could even be taken a step further and cvsup could choose the optimal server for you based on an end-to-end network bandwidth metric and the server load. I'm sure there are many people who aren't using the optimal server for their network location. Kris ---- "Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes." -- Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 2:29:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta1-rme.xtra.co.nz (mta.xtra.co.nz [203.96.92.1]) by hub.freebsd.org (Postfix) with ESMTP id 625D514CAA for ; Sun, 30 May 1999 02:29:23 -0700 (PDT) (envelope-from junkmale@pop3.xtra.co.nz) Received: from wocker ([210.55.152.128]) by mta1-rme.xtra.co.nz (InterMail v04.00.02.07 201-227-108) with SMTP id <19990530093155.ZAYW7869945.mta1-rme@wocker>; Sun, 30 May 1999 21:31:55 +1200 From: "Dan Langille" Organization: The FreeBSD Diary To: Kris Kennaway Date: Sun, 30 May 1999 21:29:21 +1200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org Reply-To: junkmale@xtra.co.nz Cc: current@freebsd.org References: <19990529161158.A9898@ns1.adsu.bellsouth.com> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <19990530093155.ZAYW7869945.mta1-rme@wocker> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30 May 99, at 18:03, Kris Kennaway wrote: > I'm sure there are many people who aren't using the optimal server for > their network location. FWIW: I had someone in the Netherlands using cvsup.nz.freebsd.org for a bit. They claimed better times than stuff like Dallas or someething. cvsup, when it was up, was an old 486. It's down now, but it should return within the next few weeks. Umm, well, actually, we're waiting for ncr to work under 3.* and then we'll upgrade and deploy the box. -- Dan Langille - DVL Software Limited The FreeBSD Diary - http://www.FreeBSDDiary.org/freebsd/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/racingsystem.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 2:48:47 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 99F0814CAA for ; Sun, 30 May 1999 02:48:44 -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 KAA93022; Sun, 30 May 1999 10:49:21 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 30 May 1999 10:49:21 +0100 (BST) From: Doug Rabson To: Nicolai Petri Cc: current@freebsd.org Subject: Re: Was is status on cardbus ? In-Reply-To: <007701beaa75$ab2e8200$6535a8c0@petri> 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, 30 May 1999, Nicolai Petri wrote: > Is cardbus work in progress ?? > And will newbus designed drivers work without larger modifications ? Cardbus will happen after pccard is cleaned up a bit. Warner Losh is working hard on pccard at the moment. I think that a newbus pci driver (or even an old pci driver using the backwards compatible apis) will work with cardbus with only small modifications. -- 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 Sun May 30 3:40: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from mickey00.mickey.ai.kyutech.ac.jp (mickey00.mickey.ai.kyutech.ac.jp [131.206.21.1]) by hub.freebsd.org (Postfix) with ESMTP id 782D914D75 for ; Sun, 30 May 1999 03:39:56 -0700 (PDT) (envelope-from ohashi@mickey.ai.kyutech.ac.jp) Received: from atohasi.mickey.ai.kyutech.ac.jp (atohasi.mickey.ai.kyutech.ac.jp [131.206.21.80]) by mickey00.mickey.ai.kyutech.ac.jp (8.8.8/3.6W-mickey) with ESMTP id TAA20557 for ; Sun, 30 May 1999 19:39:50 +0900 (JST) Received: (from ohashi@localhost) by atohasi.mickey.ai.kyutech.ac.jp (8.9.3/3.5Wpl5) id TAA03114; Sun, 30 May 1999 19:39:50 +0900 (JST) Date: Sun, 30 May 1999 19:39:50 +0900 (JST) Message-Id: <199905301039.TAA03114@atohasi.mickey.ai.kyutech.ac.jp> To: current@freebsd.org Subject: Re: Was is status on cardbus ? In-Reply-To: Your message of "Sun, 30 May 1999 18:49:21 JST". From: ohashi@mickey.ai.kyutech.ac.jp (Takeshi OHASHI) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dfr>>> Is cardbus work in progress ?? dfr>>> And will newbus designed drivers work without larger modifications ? dfr>> dfr>>Cardbus will happen after pccard is cleaned up a bit. Warner Losh is dfr>>working hard on pccard at the moment. I think that a newbus pci driver dfr>>(or even an old pci driver using the backwards compatible apis) will work dfr>>with cardbus with only small modifications. First, I do not want flame. [FYI] Our newconfig project is supporting some PCI-CardBus bridges and some CardBus cards. # CardBus-Card network interfaces ep* at cardbus? dev ? func ? # 3Com 3c575TX Ethernet xl* at cardbus? dev ? func ? # 3Com 3c575TX and 3c575BTX Ethernet newconfig into FreeBSD: http://www.jp.freebsd.org/newconfig/index.html Current suported devices: http://www.jp.freebsd.org/newconfig/device-list.txt Thanks. -- Takeshi OHASHI ohashi@mickey.ai.kyutech.ac.jp ohashi@jp.FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 9:42:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-gw6.pacbell.net (mail-gw6.pacbell.net [206.13.28.41]) by hub.freebsd.org (Postfix) with ESMTP id 2034615105 for ; Sun, 30 May 1999 09:42:28 -0700 (PDT) (envelope-from viagra_online@usa.net) Received: from adsl-207-105-40-236.dsl.lsan03.pacbell.net (adsl-207-105-40-236.dsl.lsan03.pacbell.net [207.105.40.236]) by mail-gw6.pacbell.net (8.9.3/8.9.3) with SMTP id JAA11010 for ; Sun, 30 May 1999 09:42:24 -0700 (PDT) Message-Id: <199905301642.JAA11010@mail-gw6.pacbell.net> X-Authentication-Warning: mail-gw6.pacbell.net: adsl-207-105-40-236.dsl.lsan03.pacbell.net [207.105.40.236] didn't use HELO protocol To: freebsd-current@FreeBSD.ORG From: "Medical Center Online" Date: Sun, 30 May 99 09:43:19 -0700 Subject: Pfizer VIAGRA(tm) - FOR AS LITTLE AS $6 PER DOSE X-Mailer: http://www.smartsurf.net/clients/medicalcenter Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.smartsurf.net/clients/medicalcenter Some people may find this subject a bit offensive, but the truth of the matter is Viagra from Pfizer has truly helped many people and even saved marriages. The only problem in the past was that in order to get a prescription for this marriage-saving pill was to go through an EMBARASSING appointment with your doctor. I know, I had to tell a strange nurse why I wanted to see the doctor - it wasn't one of the most comfortable phone calls :-) So if you are one of the many millions of Americans suffering from ED (erectile dysfunction) or you would just like to try Viagra to see if it will increase intimacy with your mate (it will) - here is an opportunity to order it discretely, privately and inexpensively right over the internet. ------------------------------ Need Viagra? No Prescription? No Problem... No appointments, no waiting rooms, no embarrassment. Imagine -- your next order of Viagra is just a click away. MedCenter Online in association with KwikMed, Inc. is able to offer individuals afflicted with sexual dysfunction the ability to order Viagra online --------------------------------------------------------------------------------- Genuine Pfizer Viagra(tm) Can Be Legally Ordered Online For As Little As $6 Per Dose (normally $10 per dose - You save $4 per dose) --------------------------------------------------------------------------------- click on the link below for information on how you can order Viagra(tm) for as little as $6 per dose: http://www.smartsurf.net/clients/medicalcenter --------------------------------------------------------------------------------- It has been estimated that up to 30 million American men suffer from sexual dysfunction (impotence). Until recently, sexual dysfunction has been effectively treated with injections, surgery, and other procedures, many of which are painful and embarrassing. In March 1998, the FDA announced that Viagra® a new drug from Pfizer, Inc., has been approved as treatment for male sexual dysfunction. MedCenter Online & KwikMed, Inc. is able to offer individuals afflicted with sexual dysfunction an evaluation for suitability to Viagra therapy. The evaluation is performed by qualified American physicians in a manner which is simple, secure, and without embarrassment. http://www.smartsurf.net/clients/medicalcenter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 12:52:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx.nsu.ru (mx.nsu.ru [193.124.215.71]) by hub.freebsd.org (Postfix) with ESMTP id 8788814C26 for ; Sun, 30 May 1999 12:51:55 -0700 (PDT) (envelope-from semen@iclub.nsu.ru) Received: from iclub.nsu.ru (semen@iclub.nsu.ru [193.124.222.66]) by mx.nsu.ru (8.9.1/8.9.0) with ESMTP id CAA27576 for ; Mon, 31 May 1999 02:51:31 +0700 (NOVST) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.9.3/8.8.5) with ESMTP id CAA25741 for ; Mon, 31 May 1999 02:51:31 +0700 (NSS) Date: Mon, 31 May 1999 02:51:31 +0700 (NSS) From: Ustimenko Semen To: freebsd-current@FreeBSD.org Subject: How can i fail buf? 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! The problem is following: FS driver recieves VOP_FSYNC request, then it scan the queue and pick up dirty buffers to bwrite(bp) them. bwrite calls VOP_STRATEGY, FS's strategy routine is trying to VOP_BMAP buf, and fails (suppose it fails), then xxfs_strategy do: bp->b_error = error; bp->b_flags |= B_ERROR; biodone(bp); return(bp); (Looks right, at least IMO) But: biodone will not rel*se(bp), as it is not B_ASYNC, then it returns to bwrite, where it will brelse(bp) after biowait(bp). Then bp will come to brelse with B_ERROR set. in the begining, brelse: ... if ((bp->b_flags & (B_READ | B_ERROR)) == B_ERROR) { bp->b_flags &= ~B_ERROR; bdirty(bp); } ... then buffer returns to dirty queue, and is dirty, all repeates infinite. How this is solved? Sorry if i miss something obvious... Sorry for bad english... Bye To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 13: 4:37 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 EFC6C14DBE for ; Sun, 30 May 1999 13:04:35 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id NAA00369; Sun, 30 May 1999 13:54:14 -0600 (MDT) Date: Sun, 30 May 1999 13:54:14 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905301954.NAA00369@narnia.plutotech.com> To: Bruce Evans Cc: current@FreeBSD.org Subject: Re: FP exceptions broken (Re: Interesting bogons from last night's 4.0 snapshot.) X-Newsgroups: pluto.freebsd.current In-Reply-To: <199905291437.AAA04536@godzilla.zeta.org.au> 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 > Actually, it works on a Celeron but fails on a P5. This is caused by the > following bug suite (in approximately historical order): > 1) IRQ13 interface was broken as designed. > 2) Intel F00F bug. > 3) Probe for (1) is not very well implemented. It hacks on the idt[] > global to context switch some IDT entries. > 4) Fix for (2) is not very well implemented. It moves the IDT without > hiding idt[] from (3). > 5) Rev.1.55 of disturbed the probe order so that (4) is > done before (3). This breaks the IDT context switching if the F00F > fix gets installed. npx traps and interrupts end up being serviced > by the dummy probe routines. Do you record this stuff anywhere? I think we should have a Bruce's nits page so this stuff isn't forgotten. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 18:56: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 0D92514C49; Sun, 30 May 1999 18:55:58 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id UAA41825; Sun, 30 May 1999 20:55:40 -0500 (CDT) (envelope-from dan) Date: Sun, 30 May 1999 20:55:39 -0500 From: Dan Nelson To: Kris Kennaway Cc: Christian Kuhtz , "Jordan K. Hubbard" , current@FreeBSD.ORG, jdp@FreeBSD.ORG Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org Message-ID: <19990530205539.B41328@dan.emsphone.com> References: <19990529161158.A9898@ns1.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from "Kris Kennaway" on Sun May 30 18:03:34 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (May 30), Kris Kennaway said: > On Sat, 29 May 1999, Christian Kuhtz wrote: > > FYI.. cvsup5.freebsd.org (2xXeon, also wearing the hat of cvsup4) > > is also still not at capacity and welcomes anyone in need of CVSup > > services, updates are also hourly from freefall. > > I was wondering the other day about the feasibility of setting up > some kind of load meter for the various cvsup servers, so people > could determine the best one to use and share the load a bit more. > Perhaps this could even be taken a step further and cvsup could > choose the optimal server for you based on an end-to-end network > bandwidth metric and the server load. A simple round-robin DNS for all the active cvsup servers should suffice; make it cvsup.freebsd.org, stick it back in the sample cvsup config files, and put a comment mentioning that if you only cvsup once a day or less it will work fine. I think the only complaint about RR servers (the last time this was brought up) was that if you cvsup'ed twice in a short period of time, you might catch two servers with different update times (differing by up to an hour). > I'm sure there are many people who aren't using the optimal server > for their network location. I don't think bandwidth is a problem; I used to cvsup daily from a 14.4K modem and it only took 5 minutes. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 19:18:17 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 0374A14C49 for ; Sun, 30 May 1999 19:18:15 -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 TAA15080; Sun, 30 May 1999 19:18:15 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA02562; Sun, 30 May 1999 19:18:14 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990530205539.B41328@dan.emsphone.com> Date: Sun, 30 May 1999 19:18:14 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Dan Nelson Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Nelson wrote: > A simple round-robin DNS for all the active cvsup servers should > suffice; make it cvsup.freebsd.org, stick it back in the sample cvsup > config files, and put a comment mentioning that if you only cvsup once > a day or less it will work fine. > > I think the only complaint about RR servers (the last time this was > brought up) was that if you cvsup'ed twice in a short period of time, > you might catch two servers with different update times (differing by > up to an hour). There were other objections which were serious to make me (hang on a second -- where is that CVSupMeister cap ... ah, there we go, it's in place now) decide not to do it. One objection was that a mirror might have been network-isolated from the master server for an extended period of time. In that case, you'd randomly get a _big_ step backwards in time. 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 Sun May 30 19:31: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 6ACDF14C0D for ; Sun, 30 May 1999 19:31:02 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 55800 invoked from network); 31 May 1999 03:32:05 -0000 Received: from shell-1.enteract.com (dscheidt@207.229.143.40) by pop3-3.enteract.com with SMTP; 31 May 1999 03:32:05 -0000 Received: from localhost (dscheidt@localhost) by shell-1.enteract.com (8.9.3/8.9.2) with SMTP id VAA53352; Sun, 30 May 1999 21:31:02 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-1.enteract.com: dscheidt owned process doing -bs Date: Sun, 30 May 1999 21:31:02 -0500 (CDT) From: David Scheidt To: John Polstra Cc: Dan Nelson , current@FreeBSD.ORG Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org 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, 30 May 1999, John Polstra wrote: > There were other objections which were serious to make me (hang on > a second -- where is that CVSupMeister cap ... ah, there we go, > it's in place now) decide not to do it. One objection was that a > mirror might have been network-isolated from the master server for an > extended period of time. In that case, you'd randomly get a _big_ > step backwards in time. > > John Can't the supfile be made to ignore updates into the past? David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 19:32:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id B65AE14C0D for ; Sun, 30 May 1999 19:32:18 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id VAA42462; Sun, 30 May 1999 21:32:14 -0500 (CDT) (envelope-from dan) Date: Sun, 30 May 1999 21:32:13 -0500 From: Dan Nelson To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org Message-ID: <19990530213213.A42309@dan.emsphone.com> References: <19990530205539.B41328@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from "John Polstra" on Sun May 30 19:18:14 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (May 30), John Polstra said: > Dan Nelson wrote: > > A simple round-robin DNS for all the active cvsup servers should > > suffice; make it cvsup.freebsd.org, stick it back in the sample > > cvsup config files, and put a comment mentioning that if you only > > cvsup once a day or less it will work fine. > > > > I think the only complaint about RR servers (the last time this was > > brought up) was that if you cvsup'ed twice in a short period of > > time, you might catch two servers with different update times > > (differing by up to an hour). > > There were other objections which were serious to make me (hang on a > second -- where is that CVSupMeister cap ... ah, there we go, it's in > place now) decide not to do it. One objection was that a mirror > might have been network-isolated from the master server for an > extended period of time. In that case, you'd randomly get a _big_ > step backwards in time. Any way to timestamp a CVS tree so that cvsup knows if its current tree is "newer" than the one the server is trying to send it? It looks like the "checkouts.cvs" file is updated every time cvsup is run; could this be used as a timestamp? (this won't work for people cvsupping off freefall directly, but since the public cvsupd servers use cvsup to update themselves, cvsupd should be able to determine its own "last update" time) Alternatively, a script could be run every 8 hours or so that checks all the members of the cvsup RR group and verifies that all servers are uptodate. If one isn't, it is removed from the RR group until it catches up. This is a bit more work but is certainly feasible. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 21:21:43 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 4B6E714D08 for ; Sun, 30 May 1999 21:21: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 OAA27787; Mon, 31 May 1999 14:21:37 +1000 Date: Mon, 31 May 1999 14:21:37 +1000 From: Bruce Evans Message-Id: <199905310421.OAA27787@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, semen@iclub.nsu.ru Subject: Re: How can i fail buf? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The problem is following: > >FS driver recieves VOP_FSYNC request, >then it scan the queue and pick up dirty buffers to >bwrite(bp) them. bwrite calls VOP_STRATEGY, >FS's strategy routine is trying to VOP_BMAP buf, and >fails (suppose it fails), then xxfs_strategy do: > > bp->b_error = error; > bp->b_flags |= B_ERROR; > biodone(bp); > return(bp); > >(Looks right, at least IMO) >But: >biodone will not rel*se(bp), as it is not B_ASYNC, >then it returns to bwrite, where it will brelse(bp) after >biowait(bp). Then bp will come to brelse with B_ERROR set. >in the begining, brelse: > > ... > > if ((bp->b_flags & (B_READ | B_ERROR)) == B_ERROR) { > bp->b_flags &= ~B_ERROR; > bdirty(bp); > } ... > >then buffer returns to dirty queue, and is dirty, all >repeates infinite. Also, for async writes, the file may be closed before the write completes (the write never completes...). Then vinvalbuf() calls VOP_FSYNC() to write all dirty buffers and panics when VOP_FSYNC() fails to do this. >How this is solved? This isn't solved. It was less serious before rev.1.196 of vfs_bio.c when B_ERROR buffers were discarded insead of re-dirtied in the above code fragment. See also PR 11697, and about 20 PRs reporting problems with i/o errors and EOF "errors" (ENOSPC/EINVAL) for (mis)using buffered devices (especially fd0). I use the following variant of the patch in PR 11697: diff -c2 vfs_bio.c~ vfs_bio.c *** vfs_bio.c~ Thu May 13 14:42:10 1999 --- vfs_bio.c Thu May 13 16:36:09 1999 *************** *** 744,752 **** bp->b_flags &= ~B_ERROR; ! if ((bp->b_flags & (B_READ | B_ERROR)) == B_ERROR) { /* * Failed write, redirty. Must clear B_ERROR to prevent ! * pages from being scrapped. Note: B_INVAL is ignored ! * here but will presumably be dealt with later. */ bp->b_flags &= ~B_ERROR; --- 800,808 ---- bp->b_flags &= ~B_ERROR; ! if ((bp->b_flags & (B_READ | B_ERROR | B_INVAL)) == B_ERROR && ! (bp->b_error == EIO || bp->b_error == 0)) { /* * Failed write, redirty. Must clear B_ERROR to prevent ! * pages from being scrapped. */ bp->b_flags &= ~B_ERROR; This fixes the primary problem in all cases except the most interesting one: for real i/o errors. It doesn't touch the secondary problem that most VOP_FSYNC() routines don't try hard enough to write all dirty buffers in the MNT_WAIT case, so vinvalbuf() may panic. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 21:26:12 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 33B4B14D08 for ; Sun, 30 May 1999 21:26:08 -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 OAA28293; Mon, 31 May 1999 14:26:06 +1000 Date: Mon, 31 May 1999 14:26:06 +1000 From: Bruce Evans Message-Id: <199905310426.OAA28293@godzilla.zeta.org.au> To: bde@zeta.org.au, gibbs@narnia.plutotech.com Subject: Re: FP exceptions broken (Re: Interesting bogons from last night's 4.0 snapshot.) Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Actually, it works on a Celeron but fails on a P5. This is caused by the >> following bug suite (in approximately historical order): >> 1) IRQ13 interface was broken as designed. >> 2) Intel F00F bug. >> 3) Probe for (1) is not very well implemented. It hacks on the idt[] >> global to context switch some IDT entries. >>... >Do you record this stuff anywhere? I think we should have a Bruce's >nits page so this stuff isn't forgotten. Usually not. I can regenerate it on demand :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 30 22:15:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 5AFAD14C49 for ; Sun, 30 May 1999 22:15:31 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id OAA23547; Mon, 31 May 1999 14:45:29 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA29523; Mon, 31 May 1999 14:46:30 +0930 Date: Mon, 31 May 1999 14:46:29 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: John Polstra Cc: Dan Nelson , current@freebsd.org Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org 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, 30 May 1999, John Polstra wrote: > There were other objections which were serious to make me (hang on > a second -- where is that CVSupMeister cap ... ah, there we go, > it's in place now) decide not to do it. One objection was that a > mirror might have been network-isolated from the master server for an > extended period of time. In that case, you'd randomly get a _big_ > step backwards in time. The solution I see here is for the cvsup mirrors to maintain a timestamp of the last time they updated from freefall (for multi-tiered mirrors, this value should be passed down the chain so each of them knows the age of their files relative to the master server) User clients will maintain their own timestamp when updating from a server (one per collection), which is the time at which their server's files were last updated from freefall, expressed relative to the local system clock (i.e. the server says "I last updated x seconds ago", and the client records time()-x to deal with clock synchronisation problems with the server). When a client connects to a server, it receives the time delta from the server corresponding to the time since the collection was mirrored (since this value is passed down from parent mirrors it corresponds to the "freefall age" of the current collection state), and if the local time delta is shorter, will refuse to update. In other words, the client says "The files I got on my last update were mirrored as of 45 minutes ago on freefall, but this server has a mirror which is 2 hours old, so I'm not touching it". Can anyone see a simpler way? Something like this could have another use if the servers could be polled for their timestamp - you could poll a set of servers and pick the one with the most recent mirror: on average, out of 20 servers chances are one of them has files which are less than 3 minutes old. This would have the effect of hitting servers (maybe hard) just after they update - maybe that would be too destabilizing. Kris ----- "Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes." -- Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 31 5:32:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx.nsu.ru (mx.nsu.ru [193.124.215.71]) by hub.freebsd.org (Postfix) with ESMTP id BFA3A14E50 for ; Mon, 31 May 1999 05:32:19 -0700 (PDT) (envelope-from semen@iclub.nsu.ru) Received: from iclub.nsu.ru (semen@iclub.nsu.ru [193.124.222.66]) by mx.nsu.ru (8.9.1/8.9.0) with ESMTP id TAA24384; Mon, 31 May 1999 19:30:08 +0700 (NOVST) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.9.3/8.8.5) with ESMTP id TAA57865; Mon, 31 May 1999 19:30:08 +0700 (NSS) Date: Mon, 31 May 1999 19:30:08 +0700 (NSS) From: Ustimenko Semen To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: How can i fail buf? In-Reply-To: <199905310421.OAA27787@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 Mon, 31 May 1999, Bruce Evans wrote: > This isn't solved. It was less serious before rev.1.196 of vfs_bio.c > when B_ERROR buffers were discarded insead of re-dirtied in the above > code fragment. See also PR 11697, and about 20 PRs reporting problems > with i/o errors and EOF "errors" (ENOSPC/EINVAL) for (mis)using buffered > devices (especially fd0). > Why they have done so? B_ERROR have to mean unrecoverable error, doesn't it? Or we need something like Writing to ... at ... failed. (A)bort, (R)etry, (I)gnore? :-) > I use the following variant of the patch in PR 11697: > > [patch skipped] > Will it ever included in current? > This fixes the primary problem in all cases except the most interesting one: > for real i/o errors. It doesn't touch the secondary problem that most > VOP_FSYNC() routines don't try hard enough to write all dirty buffers in > the MNT_WAIT case, so vinvalbuf() may panic. > As i see, we need some B_FATAL flag, that will signal brelse to do not redirty buf, for example to set when media in fd was changed. About F_SYNC: usually they do, they try very hard to free dirty queue, look at msdosfs_vnops.c, and 'man VOP_FSYNC' pseudocode. Pseudocode even loops infinitly if there is a not writable buf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 31 6:13:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from pauling.research.devcon.net (pauling.research.devcon.net [212.15.193.194]) by hub.freebsd.org (Postfix) with ESMTP id 06EF1154A1 for ; Mon, 31 May 1999 06:13:31 -0700 (PDT) (envelope-from cc@devcon.net) Received: from localhost (cc@localhost) by pauling.research.devcon.net (8.9.3/8.9.2) with ESMTP id PAA34144 for ; Mon, 31 May 1999 15:13:30 +0200 (CEST) (envelope-from cc@devcon.net) X-Authentication-Warning: pauling.research.devcon.net: cc owned process doing -bs Date: Mon, 31 May 1999 15:13:30 +0200 (CEST) From: Christian Carstensen X-Sender: cc@pauling.research.devcon.net To: current@FreeBSD.ORG Subject: i4b broken by cdevsw changes... 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 there, it seems as isdn drivers have been broken with current cdevsw registration changes. The current kernel does not link with i4b anymore. -- christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 31 6:23:23 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 B761714D80 for ; Mon, 31 May 1999 06:23:20 -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 PAA16820; Mon, 31 May 1999 15:22:40 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Christian Carstensen Cc: current@FreeBSD.ORG Subject: Re: i4b broken by cdevsw changes... In-reply-to: Your message of "Mon, 31 May 1999 15:13:30 +0200." Date: Mon, 31 May 1999 15:22:40 +0200 Message-ID: <16818.928156960@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG True, I'm waiting for Hellmut to review and/or commit the patches I've sent to him. If you want to fix it locally you need to: initialize d_maj in cdevsw s/nullreset/noreset/ remove first and last args in cdevsw_add() calls. In message , Christian Carstensen writes: > >hi there, > >it seems as isdn drivers have been broken with current cdevsw registration >changes. The current kernel does not link with i4b anymore. > > >-- > christian > > > >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 Mon May 31 10:33:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1F39D14F62 for ; Mon, 31 May 1999 10:33:12 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA76108; Mon, 31 May 1999 10:32:10 -0700 (PDT) (envelope-from dillon) Date: Mon, 31 May 1999 10:32:10 -0700 (PDT) From: Matthew Dillon Message-Id: <199905311732.KAA76108@apollo.backplane.com> To: Ustimenko Semen Cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: How can i fail buf? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Mon, 31 May 1999, Bruce Evans wrote: : :> This isn't solved. It was less serious before rev.1.196 of vfs_bio.c :> when B_ERROR buffers were discarded insead of re-dirtied in the above :> code fragment. See also PR 11697, and about 20 PRs reporting problems :> with i/o errors and EOF "errors" (ENOSPC/EINVAL) for (mis)using buffered :> devices (especially fd0). :> : :Why they have done so? B_ERROR have to mean unrecoverable :error, doesn't it? Or we need something like : :Writing to ... at ... failed. Generally the problem is that when a write fails, the buffer is not invalid - it still contains perfectly valid data. We need a more sophisticated mechanism to deal with I/O errors. Throwing away the buffer (at least initially) is *not* the correct solution. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 31 10:56:11 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 45CFA14CAA for ; Mon, 31 May 1999 10:56:08 -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 KAA18884; Mon, 31 May 1999 10:56:08 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA03578; Mon, 31 May 1999 10:56:07 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 31 May 1999 10:56:07 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Kris Kennaway Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > The solution I see here is for the cvsup mirrors to maintain > a timestamp of the last time they updated from freefall (for > multi-tiered mirrors, this value should be passed down the chain so > each of them knows the age of their files relative to the master > server) I've been down that road and was not able to come up with a workable solution. But if anybody can come up with a detailed algorithm for me, I'll welcome it with open arms. The basic problem is in the phrase "a timestamp of the last time they updated from freefall." There is no single timestamp that is representative of an update. Suppose I start an update at 15:00:00 UTC, and it finishes at 15:10:00. Every file updated came from a snapshot at some point of time in that range. In other words, CVSup can't take an instantaneous, coherent snapshot of the entire repository and give it to you. How could it, given that a tree walk alone over the repository takes a couple minutes? And that's just the easy case. Suppose that a mirror started an update, and then the network bogged down, and it didn't finish until hours later. Or suppose that it got partway through its update and then the connection was lost. In that case, some of its files would be current from within the range of the update, and some of them would still be the old versions from the previous run. Plus, a user might do an update of, say, cvs-all one day, and then just src-bin (a subset of cvs-all) a week later. Or he might use the "-i pattern" construct to update just a few files. Experience has shown that it's a bad idea to use the timestamps of the individual files, except for equality/inequality tests. You can't assume that the timestamps advance monotonically forward, because system administrators are human beings and they do dumb things like set their clocks wrong. Also, when a file has been removed on one side or the other, there's no timestamp to check. I think there might be an algorithm that would work, similar to what you proposed but a little bit more sophisticated. Each site (including clients) would need two timestamps T0 and T1, such that: * The site's most out-of-date file is at least as new as T0, and * The site's most up-to-date file is no newer than T1. Or something like that. ;-) 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 Mon May 31 11:36:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (Postfix) with ESMTP id E343915039 for ; Mon, 31 May 1999 11:36:13 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id ; Mon, 31 May 1999 14:36:00 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 31 May 1999 11:34:56 -0700 (PDT) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 31 May 1999 18:34:55 GMT X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org In-Reply-To: John Polstra's (jdp@polstra.com) message dated Mon, 31 May 1999 10:56:07. X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 May 1999 14:34:55 -0400 Message-ID: <17780.928175695@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Several questions. First, what's wrong with stamping the files in a mirror with the timestamp it has on the master? Second, how much work would it be to add, say, md5 checksums to CVS. Third, isn't the version number useful for something? Just some ramblings... H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 31 11:49:40 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 2F9F914BE3 for ; Mon, 31 May 1999 11:49:37 -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 LAA11628; Mon, 31 May 1999 11:51:47 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <199905311851.LAA11628@troutmask.apl.washington.edu> Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org In-Reply-To: from John Polstra at "May 31, 1999 10:56:07 am" To: jdp@polstra.com (John Polstra) Date: Mon, 31 May 1999 11:51:47 -0700 (PDT) Cc: kkennawa@physics.adelaide.edu.au (Kris Kennaway), 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 John Polstra wrote: > Kris Kennaway wrote: > > > The solution I see here is for the cvsup mirrors to maintain > > a timestamp of the last time they updated from freefall (for > > multi-tiered mirrors, this value should be passed down the chain so > > each of them knows the age of their files relative to the master > > server) > > I've been down that road and was not able to come up with a workable > solution. But if anybody can come up with a detailed algorithm for > me, I'll welcome it with open arms. > If you want a robust (but probably really slow) algorithm, you could use the revision number of a file. Isn't this a monotonically increasing number? Would it be possible to compute md5 signatures on a per-file per-collection basis? The cvsup server would have, for example, src-bin.md5 which contains a list of all files in the src-bin collection and their md5 signatures. When a connection is made to the server, the server sends src-bin.md5 to the client. The client compares the local src-bin.md5 with the server's src-bin.md5. Any difference would indicate a file has changed, and the client then requests the server to send the changed file(s). The client would then update the local src-bin.md5. The only problem would be a ping-pong effect if a server is out-of-date for some reason. This is were you use version numbers. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 31 14:50: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx.nsu.ru (mx.nsu.ru [193.124.215.71]) by hub.freebsd.org (Postfix) with ESMTP id 4FD8D14F85 for ; Mon, 31 May 1999 14:49:58 -0700 (PDT) (envelope-from semen@iclub.nsu.ru) Received: from iclub.nsu.ru (semen@iclub.nsu.ru [193.124.222.66]) by mx.nsu.ru (8.9.1/8.9.0) with ESMTP id EAA08109 for ; Tue, 1 Jun 1999 04:48:39 +0700 (NOVST) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.9.3/8.8.5) with ESMTP id EAA70795 for ; Tue, 1 Jun 1999 04:48:39 +0700 (NSS) Date: Tue, 1 Jun 1999 04:48:39 +0700 (NSS) From: Ustimenko Semen To: freebsd-current@FreeBSD.org Subject: FS Driver writing tactic 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 FS Guru! Is this a good tactic to write working VOP_BMAP and VOP_STRATEGY handlers, and implement VOP_READ and VOP_WRITE via bread and bwrite of own vnodes? Bye. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 31 17:15:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-41.ppp.wenet.net [206.15.85.41]) by hub.freebsd.org (Postfix) with ESMTP id C05B814E4C for ; Mon, 31 May 1999 17:15:23 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id RAA00783; Mon, 31 May 1999 17:15:13 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Mon, 31 May 1999 17:15:13 -0700 (PDT) From: Alex Zepeda To: John Polstra Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org 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 > The basic problem is in the phrase "a timestamp of the last time > they updated from freefall." There is no single timestamp that is > representative of an update. Suppose I start an update at 15:00:00 > UTC, and it finishes at 15:10:00. Every file updated came from > a snapshot at some point of time in that range. In other words, > CVSup can't take an instantaneous, coherent snapshot of the entire > repository and give it to you. How could it, given that a tree walk > alone over the repository takes a couple minutes? Since cvsup can take a revision of a file from a given time, why not use the time that the cvsup was started, this way it will ignore anything that was modified while cvsup was running, and the mirror can say, all the files are from xx.yy.zz point in time. And then have xntpd or somesuch running, so that all the cvsup mirrors have the same idea of when xx.yy.zz was.. - 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 Mon May 31 17:35:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id D313414DDE for ; Mon, 31 May 1999 17:35:25 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id UAA24794 for current@freebsd.org; Mon, 31 May 1999 20:35:24 -0400 (EDT) Message-ID: <19990531203317.A24491@netmonger.net> Date: Mon, 31 May 1999 20:33:17 -0400 From: Christopher Masto To: fb-current@freebsd.org, bsd-usb@egroups.com Subject: USB fixes for cdevsw change Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG USB stopped working as of the recent cdevsw cleanup. This fixes it. Index: usb.c =================================================================== RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usb.c,v retrieving revision 1.12 diff -u -r1.12 usb.c --- usb.c 1999/05/30 16:51:51 1.12 +++ usb.c 1999/06/01 00:30:23 @@ -129,7 +129,7 @@ /* strategy */ nostrategy, /* name */ "usb", /* parms */ noparms, - /* maj */ -1, + /* maj */ USB_CDEV_MAJOR, /* dump */ nodump, /* psize */ nopsize, /* flags */ 0, Index: usbdi.c =================================================================== RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usbdi.c,v retrieving revision 1.17 diff -u -r1.17 usbdi.c --- usbdi.c 1999/05/31 11:25:21 1.17 +++ usbdi.c 1999/06/01 00:30:23 @@ -80,12 +80,6 @@ static SIMPLEQ_HEAD(, usbd_request) usbd_free_requests; -#if defined(__FreeBSD__) -#define USB_CDEV_MAJOR 108 - -extern struct cdevsw usb_cdevsw; -#endif - #ifdef USB_DEBUG char *usbd_error_strs[USBD_ERROR_MAX] = { "NORMAL_COMPLETION", Index: usbdi.h =================================================================== RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usbdi.h,v retrieving revision 1.11 diff -u -r1.11 usbdi.h --- usbdi.h 1999/05/20 20:02:37 1.11 +++ usbdi.h 1999/06/01 00:30:23 @@ -115,6 +115,12 @@ #define USBD_NO_TIMEOUT 0 #define USBD_DEFAULT_TIMEOUT 5000 /* ms = 5 s */ +#if defined(__FreeBSD__) +#define USB_CDEV_MAJOR 108 + +extern struct cdevsw usb_cdevsw; +#endif + usbd_status usbd_open_pipe __P((usbd_interface_handle iface, u_int8_t address, u_int8_t flags, usbd_pipe_handle *pipe)); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 31 21:17:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from po2.wam.umd.edu (po2.wam.umd.edu [128.8.10.164]) by hub.freebsd.org (Postfix) with ESMTP id 014061558E for ; Mon, 31 May 1999 21:17:25 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA21236; Tue, 1 Jun 1999 00:16:55 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id AAA06801; Tue, 1 Jun 1999 00:16:54 -0400 (EDT) Received: from localhost by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id AAA06797; Tue, 1 Jun 1999 00:16:54 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Tue, 1 Jun 1999 00:16:54 -0400 (EDT) From: Kenneth Wayne Culver To: questions@soim.com Cc: freebsd-current@freebsd.org Subject: Aureal Vortex soundcard In-Reply-To: <199906010154.VAA25819@po0.wam.umd.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 > I was just wondering if anyone has gotten a soundcard based on the Vortex > chip to work under FreeBSD. I know that OSS (www.opensound.com) supports > it, but I don't want to use OSS because of the problems with it. If nobody > has gotten that card to work, then can someone point me in the right > direction to getting specs for the card and any how-to type advice on > writing the driver myself for FreeBSD. I'd be willing to donate the driver > to the project if I get it working well. Thanks. > > Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 31 23: 6:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from maildns.FSBDial.co.uk (maildns.fsbdial.co.uk [195.89.137.2]) by hub.freebsd.org (Postfix) with ESMTP id F0FDA15636 for ; Mon, 31 May 1999 23:06:31 -0700 (PDT) (envelope-from dlombardo@excite.com) Received: from [212.1.135.41] by maildns.freenet.co.uk (NTMail 4.30.0008/NT0619.00.8ceac940) with ESMTP id ishqgaaa for ; Tue, 1 Jun 1999 07:01:54 +0100 Message-ID: <375378FD.D876174C@excite.com> Date: Tue, 01 Jun 1999 07:09:01 +0100 From: Dean Lombardo Organization: University of Kent at Canterbury X-Mailer: Mozilla 4.5 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kenneth Wayne Culver Cc: questions@soim.com, freebsd-current@freebsd.org Subject: Re: Aureal Vortex soundcard References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > > > I was just wondering if anyone has gotten a soundcard based on the Vortex > > chip to work under FreeBSD. I know that OSS (www.opensound.com) supports > > it, but I don't want to use OSS because of the problems with it. If nobody > > has gotten that card to work, then can someone point me in the right > > direction to getting specs for the card and any how-to type advice on > > writing the driver myself for FreeBSD. I'd be willing to donate the driver > > to the project if I get it working well. Thanks. It's not supported, mostly because Aureal refused to release the specs (as far as I know). However, several people (Cameron Grant and Doug Rabson) are currently working on the new sound code, and according to their postings to freebsd-multimedia, they already have an "almost functional" Aureal Vortex 1 driver. Dean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 31 23:17: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (Postfix) with SMTP id DFC56155F3 for ; Mon, 31 May 1999 23:16:59 -0700 (PDT) (envelope-from will@ns.oeno.com) Received: (qmail 21150 invoked by uid 1001); 1 Jun 1999 06:16:53 -0000 To: Ustimenko Semen Cc: current@freebsd.org Subject: Re: FS Driver writing tactic References: From: Ville-Pertti Keinonen Date: 01 Jun 1999 09:14:49 +0300 In-Reply-To: Ustimenko Semen's message of "1 Jun 1999 00:50:28 +0300" Message-ID: <864skse9ba.fsf@not.demophon.com> Lines: 18 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ustimenko Semen writes: > Is this a good tactic to write working VOP_BMAP and > VOP_STRATEGY handlers, and implement VOP_READ and VOP_WRITE > via bread and bwrite of own vnodes? Considering that that's how the primary filesystem layers (ufs/ffs) do it, it should be fair to assume that it's at least a reasonable way of doing things. If you *don't* do it that way...the alternative (unless you want to bypass the cache) is to bread/bwrite the underlying device from VOP_READ/VOP_WRITE, which avoids a layer of indirection when the cache doesn't get hit (not very useful). The problem is, you're not going to be able to associate cached data with vm_objects usefully because you're buffers are associated with the underlying (device) vnode rather than the file vnode. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 0:26:48 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 8DF661560B for ; Tue, 1 Jun 1999 00:26:45 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-185.skylink.it [194.185.55.185]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id JAA12958; Tue, 1 Jun 1999 09:26:18 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id JAA02747; Tue, 1 Jun 1999 09:22:17 +0200 (CEST) Date: Tue, 1 Jun 1999 09:22:17 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Christopher Masto Cc: FreeBSD current Mailing list , USB BSD list Subject: Re: USB fixes for cdevsw change In-Reply-To: <19990531203317.A24491@netmonger.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 Thanks. Committed. Nick On Mon, 31 May 1999, Christopher Masto wrote: > USB stopped working as of the recent cdevsw cleanup. This fixes it. > > Index: usb.c > =================================================================== > RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usb.c,v > retrieving revision 1.12 > diff -u -r1.12 usb.c > --- usb.c 1999/05/30 16:51:51 1.12 > +++ usb.c 1999/06/01 00:30:23 > @@ -129,7 +129,7 @@ > /* strategy */ nostrategy, > /* name */ "usb", > /* parms */ noparms, > - /* maj */ -1, > + /* maj */ USB_CDEV_MAJOR, > /* dump */ nodump, > /* psize */ nopsize, > /* flags */ 0, > Index: usbdi.c > =================================================================== > RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usbdi.c,v > retrieving revision 1.17 > diff -u -r1.17 usbdi.c > --- usbdi.c 1999/05/31 11:25:21 1.17 > +++ usbdi.c 1999/06/01 00:30:23 > @@ -80,12 +80,6 @@ > > static SIMPLEQ_HEAD(, usbd_request) usbd_free_requests; > > -#if defined(__FreeBSD__) > -#define USB_CDEV_MAJOR 108 > - > -extern struct cdevsw usb_cdevsw; > -#endif > - > #ifdef USB_DEBUG > char *usbd_error_strs[USBD_ERROR_MAX] = { > "NORMAL_COMPLETION", > Index: usbdi.h > =================================================================== > RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usbdi.h,v > retrieving revision 1.11 > diff -u -r1.11 usbdi.h > --- usbdi.h 1999/05/20 20:02:37 1.11 > +++ usbdi.h 1999/06/01 00:30:23 > @@ -115,6 +115,12 @@ > #define USBD_NO_TIMEOUT 0 > #define USBD_DEFAULT_TIMEOUT 5000 /* ms = 5 s */ > > +#if defined(__FreeBSD__) > +#define USB_CDEV_MAJOR 108 > + > +extern struct cdevsw usb_cdevsw; > +#endif > + > usbd_status usbd_open_pipe > __P((usbd_interface_handle iface, u_int8_t address, > u_int8_t flags, usbd_pipe_handle *pipe)); > > > 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 Tue Jun 1 1:50:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail (unknown [203.69.75.251]) by hub.freebsd.org (Postfix) with ESMTP id 5481C1548A for ; Tue, 1 Jun 1999 01:49:16 -0700 (PDT) (envelope-from samon@mail) Received: (from samon@localhost) by mail (8.8.7/8.8.7) id QAA18745 for current@FreeBSD.ORG; Tue, 1 Jun 1999 16:24:59 +0800 Date: Tue, 1 Jun 1999 16:24:59 +0800 From: samon@mail.FreeBSD.ORG Message-Id: <199906010824.QAA18745@mail> To: current@FreeBSD.ORG Subject: ½Ð±z°È¥²¤Wºô¨ú®ø¹q¤l¶l¥ó´£¿ô¶Ç©Iªº³]©w Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ¿Ë·Rªº¥Î¤á±z¦n: ¥Ñ©ó±z´¿¤µ¨Ï¥Î alpha-call ªº¹q¤l¶l¥ó´£¿ô¶Ç©I(email to pager) ²{¦bÁöµM§A¤w¨ú®ø§Aªºe-mail to pager, §Ú­Ì¤´µM¦¬¨ì§Aªº email to pager ½Ð±z°È¥²¤Wºô¨ú®ø,¥H¸`¬Ùºô¸ô¸ê·½. ¨ú®øªººô§}¬O: http://www.pager.com.tw/web/service/cancele2p.asp ­Y¦³°ÝÃD: ½Ð»P§Ú­ÌÁpµ¸ e2psos@mail.pager.com.tw ÁpµØ¹q«Hºô¸ôªA°È²Õ,¯¬§A«Ø±d§Ö¼Ö. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 2:29:53 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 369F714C89 for ; Tue, 1 Jun 1999 02:29:49 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from kim.ispra.webweaving.org (va-133.skylink.it [194.185.55.133]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id LAA19311; Tue, 1 Jun 1999 11:29:25 +0200 Received: from brunte.ispra.webweaving.org (brunte.ispra.webweaving.org [10.0.0.12]) by kim.ispra.webweaving.org (8.8.8/8.8.5) with ESMTP id IAA04096; Tue, 1 Jun 1999 08:33:55 GMT X-Passed: MX on Ispra.WebWeaving.org Tue, 1 Jun 1999 08:33:55 GMT and masked X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Tue, 1 Jun 1999 08:33:55 GMT Date: Tue, 1 Jun 1999 10:40:02 +0200 (CEST) From: Dirk-Willem van Gulik X-Sender: dirkx@brunte.ispra.webweaving.org To: USB BSD list Cc: Christopher Masto , FreeBSD current Mailing list Subject: Re: [usb-bsd] Re: USB fixes for cdevsw change 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 Thanks Christopher ! Dw. On Tue, 1 Jun 1999, Nick Hibma wrote: > > Thanks. Committed. > > Nick > > On Mon, 31 May 1999, Christopher Masto wrote: > > > USB stopped working as of the recent cdevsw cleanup. This fixes it. > > > > Index: usb.c > > =================================================================== > > RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usb.c,v > > retrieving revision 1.12 > > diff -u -r1.12 usb.c > > --- usb.c 1999/05/30 16:51:51 1.12 > > +++ usb.c 1999/06/01 00:30:23 > > @@ -129,7 +129,7 @@ > > /* strategy */ nostrategy, > > /* name */ "usb", > > /* parms */ noparms, > > - /* maj */ -1, > > + /* maj */ USB_CDEV_MAJOR, > > /* dump */ nodump, > > /* psize */ nopsize, > > /* flags */ 0, > > Index: usbdi.c > > =================================================================== > > RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usbdi.c,v > > retrieving revision 1.17 > > diff -u -r1.17 usbdi.c > > --- usbdi.c 1999/05/31 11:25:21 1.17 > > +++ usbdi.c 1999/06/01 00:30:23 > > @@ -80,12 +80,6 @@ > > > > static SIMPLEQ_HEAD(, usbd_request) usbd_free_requests; > > > > -#if defined(__FreeBSD__) > > -#define USB_CDEV_MAJOR 108 > > - > > -extern struct cdevsw usb_cdevsw; > > -#endif > > - > > #ifdef USB_DEBUG > > char *usbd_error_strs[USBD_ERROR_MAX] = { > > "NORMAL_COMPLETION", > > Index: usbdi.h > > =================================================================== > > RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usbdi.h,v > > retrieving revision 1.11 > > diff -u -r1.11 usbdi.h > > --- usbdi.h 1999/05/20 20:02:37 1.11 > > +++ usbdi.h 1999/06/01 00:30:23 > > @@ -115,6 +115,12 @@ > > #define USBD_NO_TIMEOUT 0 > > #define USBD_DEFAULT_TIMEOUT 5000 /* ms = 5 s */ > > > > +#if defined(__FreeBSD__) > > +#define USB_CDEV_MAJOR 108 > > + > > +extern struct cdevsw usb_cdevsw; > > +#endif > > + > > usbd_status usbd_open_pipe > > __P((usbd_interface_handle iface, u_int8_t address, > > u_int8_t flags, usbd_pipe_handle *pipe)); > > > > > > 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 1 2:36: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 2C8E914C89 for ; Tue, 1 Jun 1999 02:36:13 -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 LAA19409; Tue, 1 Jun 1999 11:35:19 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Dirk-Willem van Gulik Cc: USB BSD list , Christopher Masto , FreeBSD current Mailing list Subject: Re: [usb-bsd] Re: USB fixes for cdevsw change In-reply-to: Your message of "Tue, 01 Jun 1999 10:40:02 +0200." Date: Tue, 01 Jun 1999 11:35:19 +0200 Message-ID: <19407.928229719@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for overlooking that one. In message , Dirk-Willem van Gulik writes: > > >Thanks Christopher ! > >Dw. >On Tue, 1 Jun 1999, Nick Hibma wrote: > >> >> Thanks. Committed. >> >> Nick >> >> On Mon, 31 May 1999, Christopher Masto wrote: >> >> > USB stopped working as of the recent cdevsw cleanup. This fixes it. >> > >> > Index: usb.c >> > =================================================================== >> > RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usb.c,v >> > retrieving revision 1.12 >> > diff -u -r1.12 usb.c >> > --- usb.c 1999/05/30 16:51:51 1.12 >> > +++ usb.c 1999/06/01 00:30:23 >> > @@ -129,7 +129,7 @@ >> > /* strategy */ nostrategy, >> > /* name */ "usb", >> > /* parms */ noparms, >> > - /* maj */ -1, >> > + /* maj */ USB_CDEV_MAJOR, >> > /* dump */ nodump, >> > /* psize */ nopsize, >> > /* flags */ 0, >> > Index: usbdi.c >> > =================================================================== >> > RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usbdi.c,v >> > retrieving revision 1.17 >> > diff -u -r1.17 usbdi.c >> > --- usbdi.c 1999/05/31 11:25:21 1.17 >> > +++ usbdi.c 1999/06/01 00:30:23 >> > @@ -80,12 +80,6 @@ >> > >> > static SIMPLEQ_HEAD(, usbd_request) usbd_free_requests; >> > >> > -#if defined(__FreeBSD__) >> > -#define USB_CDEV_MAJOR 108 >> > - >> > -extern struct cdevsw usb_cdevsw; >> > -#endif >> > - >> > #ifdef USB_DEBUG >> > char *usbd_error_strs[USBD_ERROR_MAX] = { >> > "NORMAL_COMPLETION", >> > Index: usbdi.h >> > =================================================================== >> > RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usbdi.h,v >> > retrieving revision 1.11 >> > diff -u -r1.11 usbdi.h >> > --- usbdi.h 1999/05/20 20:02:37 1.11 >> > +++ usbdi.h 1999/06/01 00:30:23 >> > @@ -115,6 +115,12 @@ >> > #define USBD_NO_TIMEOUT 0 >> > #define USBD_DEFAULT_TIMEOUT 5000 /* ms = 5 s */ >> > >> > +#if defined(__FreeBSD__) >> > +#define USB_CDEV_MAJOR 108 >> > + >> > +extern struct cdevsw usb_cdevsw; >> > +#endif >> > + >> > usbd_status usbd_open_pipe >> > __P((usbd_interface_handle iface, u_int8_t address, >> > u_int8_t flags, usbd_pipe_handle *pipe)); >> > >> > >> > 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 > -- 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 Tue Jun 1 3:17:19 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 E50961529E; Tue, 1 Jun 1999 03:17:04 -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.00 #1) id 10olbT-000Bcj-00; Tue, 01 Jun 1999 12:17:03 +0200 From: Sheldon Hearn To: grog@freebsd.org Cc: current@freebsd.org Subject: cdevsw changes broke world in vinum Date: Tue, 01 Jun 1999 12:17:03 +0200 Message-ID: <44684.928232223@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Greg, It appears as though the recent changes to the cdevsw structure broke world in vinum: " cc -O -pipe -DVINUMDEBUG -g -O -DKERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/vinum -I/usr/obj/usr/src/sys/modules/vinum/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/vinum/../../dev/vinum/vinum.c /usr/src/sys/modules/vinum/../../dev/vinum/vinum.c:55: `nullreset' undeclared here (not in a function) /usr/src/sys/modules/vinum/../../dev/vinum/vinum.c:55: initializer element for `vinum_cdevsw.d_bogoreset' is not constant /usr/src/sys/modules/vinum/../../dev/vinum/vinum.c: In function `vinumattach': /usr/src/sys/modules/vinum/../../dev/vinum/vinum.c:88: warning: implicit declaration of function `cdevsw_add_generic' /usr/src/sys/modules/vinum/../../dev/vinum/vinum.c: In function `vinum_modevent': /usr/src/sys/modules/vinum/../../dev/vinum/vinum.c:239: `cdevsw' undeclared (first use in this function) /usr/src/sys/modules/vinum/../../dev/vinum/vinum.c:239: (Each undeclared identifier is reported only once /usr/src/sys/modules/vinum/../../dev/vinum/vinum.c:239: for each function it appears in.) *** Error code 1 Stop. [...] " The offending line is: cdevsw[CDEV_MAJOR] = NULL; /* no cdevsw any more */ Should that be vinum_cdevsw? Or did I get unlucky and pull sources between commits? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 4:59:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from atdot.dotat.org (atdot.dotat.org [150.101.89.3]) by hub.freebsd.org (Postfix) with ESMTP id A85DC1527C for ; Tue, 1 Jun 1999 04:59:26 -0700 (PDT) (envelope-from newton@atdot.dotat.org) Received: (from newton@localhost) by atdot.dotat.org (8.9.3/8.7) id VAA00496 for current@freebsd.org; Tue, 1 Jun 1999 21:27:09 +0930 (CST) Date: Tue, 1 Jun 1999 21:27:09 +0930 (CST) From: Mark Newton Message-Id: <199906011157.VAA00496@atdot.dotat.org> To: current@freebsd.org Subject: IRQ sharing with newbus Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've blown the dust off an old ISA multiport serial card. In the old days, I used to make it work with BSD by including "options COM_MULTIPORT" and using the following config file directives: device sio2 at isa? port 0x280 tty flags 0x0201 irq 5 vector siointr device sio3 at isa? port 0x288 tty flags 0x0201 device sio4 at isa? port 0x290 tty flags 0x0201 device sio5 at isa? port 0x298 tty flags 0x0201 device sio6 at isa? port 0x2a0 tty flags 0x0201 device sio7 at isa? port 0x2a8 tty flags 0x0201 device sio8 at isa? port 0x2b0 tty flags 0x0201 device sio9 at isa? port 0x2b8 tty flags 0x0201 Under newbus, of course, things look slightly different, so I tried this: device sio2 at isa? port 0x280 flags 0x0201 irq 5 device sio3 at isa? port 0x288 flags 0x0201 device sio4 at isa? port 0x290 flags 0x0201 [ ... ] device sio9 at isa? port 0x2b8 flags 0x0201 Natch: "panic: NULL irq resource!" from nexus_setup_intr() in sys/i386/i386/nexus.c while probing sio3 (and I know that sio2 is probing successfully - see below). Assuming (from the panic message) that it wants an IRQ, I've tried this: device sio2 at isa? port 0x280 flags 0x0201 irq 5 conflicts device sio3 at isa? port 0x288 flags 0x0201 irq 5 conflicts [ ... ] device sio9 at isa? port 0x2b8 flags 0x0201 irq 5 conflicts Same bat-panic, same bat-probe. If I boot -c and disable sio3-thru-sio9, the kernel successfully probes and boots, but the "slave" ports on the serial card will, of course, never be seen. (This is how I know it's the sio3 probe that's causing the panic). I'm guessing the reason for this is that an IRQ that has been "eaten" by a device under the newbus architecture is made unavailable for subsequent devices, so the "irq 5" hint on sio3-thru-sio9 is ignored, and there are no alternatives the device can try instead. So, guys -- What is the officially blessed way of sharing IRQs under newbus? - mark -------------------------------------------------------------------- I tried an internal modem, newton@atdot.dotat.org but it hurt when I walked. Mark Newton ----- Voice: +61-4-1620-2223 ------------- Fax: +61-8-82231777 ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 8:53:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id A9D1214E32 for ; Tue, 1 Jun 1999 08:53:30 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id LAA16549; Tue, 1 Jun 1999 11:53:17 -0400 (EDT) Date: Tue, 1 Jun 1999 11:53:15 -0400 (EDT) From: "Matthew N. Dodd" To: Mark Newton Cc: current@FreeBSD.ORG Subject: Re: IRQ sharing with newbus In-Reply-To: <199906011157.VAA00496@atdot.dotat.org> 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 Tue, 1 Jun 1999, Mark Newton wrote: > So, guys -- What is the officially blessed way of sharing IRQs under > newbus? If you find out, let me know since the EISA code suffers the same problem (though the drivers do a bit better job detecting the condition, and just fail to attach instead of panicing.) -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 11:41:14 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 50B8114F82 for ; Tue, 1 Jun 1999 11:41:10 -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 UAA20885 for ; Tue, 1 Jun 1999 20:41:00 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: net.inet.tcp.always_keepalive on as default ? From: Poul-Henning Kamp Date: Tue, 01 Jun 1999 20:41:00 +0200 Message-ID: <20883.928262460@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Considering the number of hosts on the net today, which come and go with no warning and with dynamic IP assignments, I would propose that we disregard what the "old farts" felt about TCP keepalives, and enable the sysctl net.inet.tcp.always_keepalive as default. Setting this will make all TCP connections send a probing ACK every couple of hours if no other activity were present on the connection, this enables the TCP stack to figure out if the other end has gone or is still there. The typical symptom that you need this is that netstat shows many connections which have been standing there for any amount of time up to your uptime, simply because your machine is waiting to receive something from the other end, and for all practical purposes, "the other end" doesn't exist anymore. The argument against is that this will increas trafic and keep dynamic lines up when they should otherwise have been allowed to fall down. The former argument doesn't hold water, since we're talking about a TCP segment per hour (or less) per connection. The second argument falls on the same reasoning in my book, I don't know of any on-demand lines with a timeout longer than 10 minutes anyway. -- 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 Tue Jun 1 11:48:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 7BD831500F; Tue, 1 Jun 1999 11:47:59 -0700 (PDT) (envelope-from rgrimes@gndrsh.aac.dev.com) Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.9.3/8.9.3) id LAA13583; Tue, 1 Jun 1999 11:47:57 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199906011847.LAA13583@gndrsh.aac.dev.com> Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <20883.928262460@critter.freebsd.dk> from Poul-Henning Kamp at "Jun 1, 1999 08:41:00 pm" To: phk@FreeBSD.ORG (Poul-Henning Kamp) Date: Tue, 1 Jun 1999 18:47:57 +0000 (GMT) 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 > > Considering the number of hosts on the net today, which come and > go with no warning and with dynamic IP assignments, I would propose > that we disregard what the "old farts" felt about TCP keepalives, > and enable the sysctl net.inet.tcp.always_keepalive as default. > > Setting this will make all TCP connections send a probing ACK every > couple of hours if no other activity were present on the connection, > this enables the TCP stack to figure out if the other end has gone > or is still there. > > The typical symptom that you need this is that netstat shows many > connections which have been standing there for any amount of time > up to your uptime, simply because your machine is waiting to receive > something from the other end, and for all practical purposes, "the > other end" doesn't exist anymore. I have no problem with this, though the traffic load created by the aggregate base of installed FreeBSD boxes over the global internet might even be measurable :-). > > The argument against is that this will increas trafic and keep > dynamic lines up when they should otherwise have been allowed to > fall down. > > The former argument doesn't hold water, since we're talking about > a TCP segment per hour (or less) per connection. > > The second argument falls on the same reasoning in my book, I don't > know of any on-demand lines with a timeout longer than 10 minutes > anyway. Well, we run many at 1 to 3 hours, but then they have ``activity filters'' that could be tweaked to not consider these packets as real traffic so they would still timeout. I would rather save the connection table for things that are useful than save a few port/hours of connect time :-). This may have more drastic effects for others though. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.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 1 11:51:34 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 DE9981565E; Tue, 1 Jun 1999 11:51:21 -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 MAA19417; Tue, 1 Jun 1999 12:51:17 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA14756; Tue, 1 Jun 1999 12:51:16 -0600 Date: Tue, 1 Jun 1999 12:51:16 -0600 Message-Id: <199906011851.MAA14756@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <20883.928262460@critter.freebsd.dk> References: <20883.928262460@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Considering the number of hosts on the net today, which come and > go with no warning and with dynamic IP assignments, I would propose > that we disregard what the "old farts" felt about TCP keepalives, > and enable the sysctl net.inet.tcp.always_keepalive as default. Seeing as the amount of traffic and congestion in the Internet, I propose we diregard what the 'old fart' PHK says and not increase the congestion with the use of keepalives. :) The 'old farts' did a good job of designing a system that happens to work better than all of the systems the 'young farts' were able to design. PHK's arguments are specious, since *any* traffic when the link is congested is more congestion. > The argument against is that this will increas trafic and keep > dynamic lines up when they should otherwise have been allowed to > fall down. > > The former argument doesn't hold water, since we're talking about > a TCP segment per hour (or less) per connection. That's still traffic, and congestion is congestion. On one systems that isn't a lot, but with alot of connections it can add up to a significant amount of bandwidth. > The second argument falls on the same reasoning in my book, I don't > know of any on-demand lines with a timeout longer than 10 minutes > anyway. You don't know of any, but that doesn't mean they don't exist. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 12:29:13 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 68CC115787; Tue, 1 Jun 1999 12:29:12 -0700 (PDT) From: "Jonathan M. Bresler" To: phk@freebsd.org Cc: current@freebsd.org In-reply-to: <20883.928262460@critter.freebsd.dk> (message from Poul-Henning Kamp on Tue, 01 Jun 1999 20:41:00 +0200) Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-Id: <19990601192912.68CC115787@hub.freebsd.org> Date: Tue, 1 Jun 1999 12:29:12 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Poul-Henning Kamp > Date: Tue, 01 Jun 1999 20:41:00 +0200 > > Considering the number of hosts on the net today, which come and > go with no warning and with dynamic IP assignments, I would propose > that we disregard what the "old farts" felt about TCP keepalives, > and enable the sysctl net.inet.tcp.always_keepalive as default. we should consult with hte tcp-impl mailing list and get their take on the matter before we decide what to do here. the address is tcp-impl@grc.nasa.gov. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 12:36:58 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 6EF8215787 for ; Tue, 1 Jun 1999 12:36:54 -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 FAA11098; Wed, 2 Jun 1999 05:36:52 +1000 Date: Wed, 2 Jun 1999 05:36:52 +1000 From: Bruce Evans Message-Id: <199906011936.FAA11098@godzilla.zeta.org.au> To: current@FreeBSD.ORG, newton@atdot.dotat.org Subject: Re: IRQ sharing with newbus Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Under newbus, of course, things look slightly different, so I tried >this: > >device sio2 at isa? port 0x280 flags 0x0201 irq 5 >device sio3 at isa? port 0x288 flags 0x0201 >device sio4 at isa? port 0x290 flags 0x0201 > [ ... ] >device sio9 at isa? port 0x2b8 flags 0x0201 > >Natch: "panic: NULL irq resource!" from nexus_setup_intr() in >sys/i386/i386/nexus.c while probing sio3 (and I know that sio2 >is probing successfully - see below). This was apparently broken when sio was converted to new-bus. The driver (actually mainly isa.c) used to simply skip irq allocation for devices with no irq (COM_MULTIPORT non-master ones and polled ones). >Assuming (from the panic message) that it wants an IRQ, I've tried this: > >device sio2 at isa? port 0x280 flags 0x0201 irq 5 conflicts >device sio3 at isa? port 0x288 flags 0x0201 irq 5 conflicts > [ ... ] >device sio9 at isa? port 0x2b8 flags 0x0201 irq 5 conflicts > >Same bat-panic, same bat-probe. I don't understand why this doesn't get further, since the RF_SHAREABLE flag is (incorrectly) specified. sio fast interrupts are particularly unshareable. sio now forces fast interrupts, although this is wrong for sio pccard devices. >So, guys -- What is the officially blessed way of sharing IRQs under >newbus? It should be almost the same as it used to be: specify RF_SHAREABLE for allocating shared irq resources; this corresponds to not specifying INTR_EXCL in the pre-new-bus interface (intr_create()?). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 12:47: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id CA18B14D1E; Tue, 1 Jun 1999 12:46:48 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id MAA06468; Tue, 1 Jun 1999 12:40:34 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 01 Jun 1999 12:40:34 -0700 Date: Tue, 1 Jun 1999 12:40:34 -0700 (PDT) From: X-Sender: kip@luna To: Nate Williams Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <199906011851.MAA14756@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: nate@mt.sri.com,phk@FreeBSD.ORG,current@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think it is fair to say that the nature of the internet has changed somewhat since the standards were made. Keepalives by default are not sent until after two hours, if they are acknowledged no more packets are sent. If not 10 more probes are sent 75 seconds apart before the connection is declared dead. I think it somewhat silly to say that this is consuming a lot of bandwidth. The average mail message (4k) is 4 packets, the average telnet session is at least several hundred and an ftp session is going to be many, many more. Back in the day when people were arguing about the congestion it would create a 300baud modem was considered completely normal. Nowadays, when the average gaudy web page is > 20k (read ~20 1k packets) it is safe to say that things have changed. -Kip On Tue, 1 Jun 1999, Nate Williams wrote: > > Considering the number of hosts on the net today, which come and > > go with no warning and with dynamic IP assignments, I would propose > > that we disregard what the "old farts" felt about TCP keepalives, > > and enable the sysctl net.inet.tcp.always_keepalive as default. > > Seeing as the amount of traffic and congestion in the Internet, I > propose we diregard what the 'old fart' PHK says and not increase the > congestion with the use of keepalives. :) > > The 'old farts' did a good job of designing a system that happens to > work better than all of the systems the 'young farts' were able to > design. > > PHK's arguments are specious, since *any* traffic when the link is > congested is more congestion. > > > The argument against is that this will increas trafic and keep > > dynamic lines up when they should otherwise have been allowed to > > fall down. > > > > The former argument doesn't hold water, since we're talking about > > a TCP segment per hour (or less) per connection. > > That's still traffic, and congestion is congestion. On one systems that > isn't a lot, but with alot of connections it can add up to a significant > amount of bandwidth. > > > The second argument falls on the same reasoning in my book, I don't > > know of any on-demand lines with a timeout longer than 10 minutes > > anyway. > > You don't know of any, but that doesn't mean they don't exist. > > > Nate > > > 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 1 13: 3:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id C46351503E; Tue, 1 Jun 1999 13:03:38 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id NAA21559; Tue, 1 Jun 1999 13:03:31 -0700 (PDT) (envelope-from mph) Date: Tue, 1 Jun 1999 13:03:31 -0700 From: Matthew Hunt To: kip@lyris.com Cc: Nate Williams , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990601130331.A21176@wopr.caltech.edu> References: <199906011851.MAA14756@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from kip@lyris.com on Tue, Jun 01, 1999 at 12:40:34PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 01, 1999 at 12:40:34PM -0700, kip@lyris.com wrote: > declared dead. I think it somewhat silly to say that this is consuming a > lot of bandwidth. The average mail message (4k) is 4 packets, the average The other issue is that you don't necessarily want the TCP connection to close just because you lose connectivity for a few hours. If we send keepalives by default, might that not surprise users who don't expect it? I'm thinking of long-lived connections like telnet and ssh; if you're doing work over such a connection, it would be nice if the connection endured an outage while you're away sleeping, like it does without keepalives. -- Matthew Hunt * UNIX is a lever for the http://www.pobox.com/~mph/ * intellect. -J.R. Mashey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 13:11:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1]) by hub.freebsd.org (Postfix) with ESMTP id 1F09E14E9D; Tue, 1 Jun 1999 13:11:53 -0700 (PDT) (envelope-from crawdad@gungnir.fnal.gov) Received: from gungnir.fnal.gov (localhost [127.0.0.1]) by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id PAA16774; Tue, 1 Jun 1999 15:11:49 -0500 (CDT) Message-Id: <199906012011.PAA16774@gungnir.fnal.gov> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG From: "Matt Crawford" Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of Tue, 01 Jun 1999 20:41:00 +0200. <20883.928262460@critter.freebsd.dk> Date: Tue, 01 Jun 1999 15:11:49 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ... and keep dynamic lines up when they should otherwise have been > allowed to fall down. > [...] > The second argument falls on the same reasoning in my book, I don't > know of any on-demand lines with a timeout longer than 10 minutes > anyway. But it will bring the line back *up*, to no useful purpose. Always think very hard before messing with TCP. And then don't. Matt Crawford To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 13:13:44 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 108A614E9D for ; Tue, 1 Jun 1999 13:13:37 -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 WAA22396; Tue, 1 Jun 1999 22:12:02 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Hunt Cc: kip@lyris.com, Nate Williams , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Tue, 01 Jun 1999 13:03:31 PDT." <19990601130331.A21176@wopr.caltech.edu> Date: Tue, 01 Jun 1999 22:12:02 +0200 Message-ID: <22394.928267922@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mind you, this is only a problem because FreeBSD is to bloddy stable: I logged into a customers server a few days a go, it had been up for over a year, and had accumulated tons of ftpds from WIN* machines which had gotten a vulcan nerve pinch or a different IP#. (I'm sure windows NT servers doesn't have this problem at all) It doesn't have to be 2h timeout. I would be happy with a default of 24h, even one week would be OK with me. But infinity is too long for my taste. Can people live with a one week TCP keepalive as default ? -- 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 Tue Jun 1 13:14:24 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 26A1915802; Tue, 1 Jun 1999 13:14:19 -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 NAA20523; Tue, 1 Jun 1999 13:14:07 -0700 (PDT) Date: Tue, 1 Jun 1999 13:14:05 -0700 (PDT) From: Julian Elischer To: Matthew Hunt Cc: kip@lyris.com, Nate Williams , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <19990601130331.A21176@wopr.caltech.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 this is less and less of a problem because if you lose your link on PPP you are liable to get a differetn IP address on your redial. for network outages in the middle it works though.. but I'd rather have a keepalive of 10 x 4 hour pings before failure.. (or something as long..) It's really a per-connection decision on what makes sense julian On Tue, 1 Jun 1999, Matthew Hunt wrote: > On Tue, Jun 01, 1999 at 12:40:34PM -0700, kip@lyris.com wrote: > > > declared dead. I think it somewhat silly to say that this is consuming a > > lot of bandwidth. The average mail message (4k) is 4 packets, the average > > The other issue is that you don't necessarily want the TCP connection > to close just because you lose connectivity for a few hours. If we > send keepalives by default, might that not surprise users who don't > expect it? > > I'm thinking of long-lived connections like telnet and ssh; if you're > doing work over such a connection, it would be nice if the connection > endured an outage while you're away sleeping, like it does without > keepalives. > > -- > Matthew Hunt * UNIX is a lever for the > http://www.pobox.com/~mph/ * intellect. -J.R. Mashey > > > 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 1 13:15:28 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 C85B014FD7 for ; Tue, 1 Jun 1999 13:15:14 -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 OAA20242; Tue, 1 Jun 1999 14:15:06 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA15519; Tue, 1 Jun 1999 14:15:05 -0600 Date: Tue, 1 Jun 1999 14:15:05 -0600 Message-Id: <199906012015.OAA15519@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: Matthew Hunt , kip@lyris.com, Nate Williams , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <22394.928267922@critter.freebsd.dk> References: <19990601130331.A21176@wopr.caltech.edu> <22394.928267922@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mind you, this is only a problem because FreeBSD is to bloddy > stable: I logged into a customers server a few days a go, it had > been up for over a year, and had accumulated tons of ftpds from > WIN* machines which had gotten a vulcan nerve pinch or a different > IP#. (I'm sure windows NT servers doesn't have this problem at > all) > > It doesn't have to be 2h timeout. I would be happy with a default > of 24h, even one week would be OK with me. > > But infinity is too long for my taste. > > Can people live with a one week TCP keepalive as default ? Compromise. I like it. One week is certainly adequate for me. If I leave a link 'active' for longer than that w/out activity, I deserve to lose the link Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 13:16:13 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 7FB8F157BA; Tue, 1 Jun 1999 13:16: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 WAA22446; Tue, 1 Jun 1999 22:15:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jonathan M. Bresler" Cc: current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Tue, 01 Jun 1999 12:29:12 PDT." <19990601192912.68CC115787@hub.freebsd.org> Date: Tue, 01 Jun 1999 22:15:57 +0200 Message-ID: <22444.928268157@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990601192912.68CC115787@hub.freebsd.org>, "Jonathan M. Bresler" w rites: > we should consult with hte tcp-impl mailing list and get their >take on the matter before we decide what to do here. the address is >tcp-impl@grc.nasa.gov. I already did, but it is such a hot issue that they don't get into it. A good summary of the "traditionalist" view can be found in: http://tcp-impl.grc.nasa.gov/tcp-impl/list/archive/1246.html I agree in principle, but not in practice. Having no keep-alives just doesn't work when WIN* boxes drop carrier and get another IP# when they come back, or when they just randomly crashes... Saying that it should be an application function is bogus in my book, since the problem is valid for all TCP users, and there are clearly not any reason to duplicate the code in telnetd, ftpd, talkd, &c &c. Of course if the application has particular hysteric requirements (ircd anyone) it can implement its own methods as well. -- 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 Tue Jun 1 13:17:10 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 4184015055; Tue, 1 Jun 1999 13:17:01 -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 OAA20273; Tue, 1 Jun 1999 14:16:56 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA15554; Tue, 1 Jun 1999 14:16:55 -0600 Date: Tue, 1 Jun 1999 14:16:55 -0600 Message-Id: <199906012016.OAA15554@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Julian Elischer Cc: Matthew Hunt , kip@lyris.com, Nate Williams , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: References: <19990601130331.A21176@wopr.caltech.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > this is less and less of a problem because > if you lose your link on PPP > you are liable to get a differetn IP address on your redial. Not true. Only if you're using a dynamic IP address setup. Most business connections have a static connection, so they'll end up with the same IP address everytime. > for network outages in the middle it works though.. > but I'd rather have a keepalive of 10 x 4 hour pings before failure.. > (or something as long..) I think PHK's one-week KEEPALIVE is acceptable to me. It lets me logon to freefall and have the link go bad overnight, yet still keep me on in the morning when I check it. Nate > > It's really a per-connection decision on what makes sense > > julian > > > > On Tue, 1 Jun 1999, Matthew Hunt wrote: > > > On Tue, Jun 01, 1999 at 12:40:34PM -0700, kip@lyris.com wrote: > > > > > declared dead. I think it somewhat silly to say that this is consuming a > > > lot of bandwidth. The average mail message (4k) is 4 packets, the average > > > > The other issue is that you don't necessarily want the TCP connection > > to close just because you lose connectivity for a few hours. If we > > send keepalives by default, might that not surprise users who don't > > expect it? > > > > I'm thinking of long-lived connections like telnet and ssh; if you're > > doing work over such a connection, it would be nice if the connection > > endured an outage while you're away sleeping, like it does without > > keepalives. > > > > -- > > Matthew Hunt * UNIX is a lever for the > > http://www.pobox.com/~mph/ * intellect. -J.R. Mashey > > > > > > 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 1 13:17:38 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 CAAAE15803 for ; Tue, 1 Jun 1999 13:17:34 -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 WAA22469; Tue, 1 Jun 1999 22:16:49 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Matt Crawford" Cc: current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Tue, 01 Jun 1999 15:11:49 CDT." <199906012011.PAA16774@gungnir.fnal.gov> Date: Tue, 01 Jun 1999 22:16:49 +0200 Message-ID: <22467.928268209@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906012011.PAA16774@gungnir.fnal.gov>, "Matt Crawford" writes: >> ... and keep dynamic lines up when they should otherwise have been >> allowed to fall down. >> [...] >> The second argument falls on the same reasoning in my book, I don't >> know of any on-demand lines with a timeout longer than 10 minutes >> anyway. > >But it will bring the line back *up*, to no useful purpose. set your filters right. -- 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 Tue Jun 1 13:18:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 8C51515413 for ; Tue, 1 Jun 1999 13:18:09 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Tue, 1 Jun 1999 13:18:07 -0700 From: "David Schwartz" To: "Poul-Henning Kamp" , "Matthew Hunt" Cc: , "Nate Williams" , Subject: RE: net.inet.tcp.always_keepalive on as default ? Date: Tue, 1 Jun 1999 13:18:07 -0700 Message-ID: <000001beac6b$dc847920$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <22394.928267922@critter.freebsd.dk> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why not just fix the application programs that really want timeouts but don't implement them? DS > Mind you, this is only a problem because FreeBSD is to bloddy > stable: I logged into a customers server a few days a go, it had > been up for over a year, and had accumulated tons of ftpds from > WIN* machines which had gotten a vulcan nerve pinch or a different > IP#. (I'm sure windows NT servers doesn't have this problem at > all) > > It doesn't have to be 2h timeout. I would be happy with a default > of 24h, even one week would be OK with me. > > But infinity is too long for my taste. > > Can people live with a one week TCP keepalive as default ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 13:20:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id A2C7A1589E for ; Tue, 1 Jun 1999 13:20:18 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Tue, 1 Jun 1999 13:20:16 -0700 From: "David Schwartz" To: "Poul-Henning Kamp" , "Jonathan M. Bresler" Cc: Subject: RE: net.inet.tcp.always_keepalive on as default ? Date: Tue, 1 Jun 1999 13:20:16 -0700 Message-ID: <000101beac6c$29979d00$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <22444.928268157@critter.freebsd.dk> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Saying that it should be an application function is bogus in my > book, since the problem is valid for all TCP users, and there are > clearly not any reason to duplicate the code in telnetd, ftpd, > talkd, &c &c. But the problem is that every application uses TCP a little bit differently, and so the type of timeout logic that is appropriate for one application is not the same as the timeout that's appropriate for another. What type of timeout you want in a TCP connection really depends upon what you are going to do with it, and that the kernel cannot know. If an application does not timeout a TCP connection in a sane way, it is broken. It should be fixed. 'Fixing' it in the kernel simply allows the application to remain broken. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 13:22:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 3E68B155BD; Tue, 1 Jun 1999 13:22:46 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id NAA06709; Tue, 1 Jun 1999 13:16:26 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 01 Jun 1999 13:16:26 -0700 Date: Tue, 1 Jun 1999 13:16:26 -0700 (PDT) From: X-Sender: kip@luna To: Matthew Hunt Cc: Nate Williams , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <19990601130331.A21176@wopr.caltech.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: mph@astro.caltech.edu,nate@mt.sri.com,phk@FreeBSD.ORG,current@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That is a much more genuine concern than bandwidth. Applications should decide for themselves whether or not to use keepalives. -Kip On Tue, 1 Jun 1999, Matthew Hunt wrote: > On Tue, Jun 01, 1999 at 12:40:34PM -0700, kip@lyris.com wrote: > > > declared dead. I think it somewhat silly to say that this is consuming a > > lot of bandwidth. The average mail message (4k) is 4 packets, the average > > The other issue is that you don't necessarily want the TCP connection > to close just because you lose connectivity for a few hours. If we > send keepalives by default, might that not surprise users who don't > expect it? > > I'm thinking of long-lived connections like telnet and ssh; if you're > doing work over such a connection, it would be nice if the connection > endured an outage while you're away sleeping, like it does without > keepalives. > > -- > Matthew Hunt * UNIX is a lever for the > http://www.pobox.com/~mph/ * intellect. -J.R. Mashey > > > 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 1 13:25:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id D1BFC14E9D for ; Tue, 1 Jun 1999 13:25:22 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from bell.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 1 Jun 99 21:20:46 +0100 (BST) Date: Tue, 1 Jun 1999 21:20:45 +0100 From: David Malone To: Nate Williams Cc: Poul-Henning Kamp , Matthew Hunt , kip@lyris.com, current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990601212045.A13137@bell.maths.tcd.ie> References: <19990601130331.A21176@wopr.caltech.edu> <22394.928267922@critter.freebsd.dk> <199906012015.OAA15519@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199906012015.OAA15519@mt.sri.com>; from Nate Williams on Tue, Jun 01, 1999 at 02:15:05PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 01, 1999 at 02:15:05PM -0600, Nate Williams wrote: > > Can people live with a one week TCP keepalive as default ? > > Compromise. I like it. One week is certainly adequate for me. If I > leave a link 'active' for longer than that w/out activity, I deserve to > lose the link Surely that violates POLA? That upsets people who have keepalive turned on already and find 1 week is way too long. For instance, we use keepalive to get rid of stuck netscapes, and we'd probably run out of swap or mbufs if it went up to a week. We just managed by putting this in rc.local: sysctl -w net.inet.tcp.always_keepalive=1 Make it a rc.conf knob if anything. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 13:29:35 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 7B472152EA; Tue, 1 Jun 1999 13:29:33 -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 NAA21796; Tue, 1 Jun 1999 13:29:28 -0700 (PDT) Date: Tue, 1 Jun 1999 13:29:27 -0700 (PDT) From: Julian Elischer To: Nate Williams Cc: Matthew Hunt , kip@lyris.com, Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <199906012016.OAA15554@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 how about a keepalive of 48 days.. the maximum a W95 machine can stay alive... :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 13:31:26 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 1B6081539F for ; Tue, 1 Jun 1999 13:31:22 -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 OAA20398; Tue, 1 Jun 1999 14:27:57 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA15700; Tue, 1 Jun 1999 14:27:56 -0600 Date: Tue, 1 Jun 1999 14:27:56 -0600 Message-Id: <199906012027.OAA15700@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: David Malone Cc: Nate Williams , Poul-Henning Kamp , Matthew Hunt , kip@lyris.com, current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <19990601212045.A13137@bell.maths.tcd.ie> References: <19990601130331.A21176@wopr.caltech.edu> <22394.928267922@critter.freebsd.dk> <199906012015.OAA15519@mt.sri.com> <19990601212045.A13137@bell.maths.tcd.ie> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Can people live with a one week TCP keepalive as default ? > > > > Compromise. I like it. One week is certainly adequate for me. If I > > leave a link 'active' for longer than that w/out activity, I deserve to > > lose the link > > Surely that violates POLA? That upsets people who have keepalive > turned on already and find 1 week is way too long. For instance, > we use keepalive to get rid of stuck netscapes, and we'd probably > run out of swap or mbufs if it went up to a week. We just managed > by putting this in rc.local: > > sysctl -w net.inet.tcp.always_keepalive=1 As I understand it, it would always on, and 'one-week' would be the default. Old (traditional) programs that turned it on would be given the 'traditional' timeout of 1 hour. Or something like that. Off == 1 week KEEPALIVE ON == traditiona 1 hour KEEPALIVe. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 13:34:18 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 A722F150AD for ; Tue, 1 Jun 1999 13:34:10 -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 WAA22638; Tue, 1 Jun 1999 22:32:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: David Malone Cc: Nate Williams , Matthew Hunt , kip@lyris.com, current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Tue, 01 Jun 1999 21:20:45 BST." <19990601212045.A13137@bell.maths.tcd.ie> Date: Tue, 01 Jun 1999 22:32:12 +0200 Message-ID: <22636.928269132@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990601212045.A13137@bell.maths.tcd.ie>, David Malone writes: >On Tue, Jun 01, 1999 at 02:15:05PM -0600, Nate Williams wrote: >> > Can people live with a one week TCP keepalive as default ? >> >> Compromise. I like it. One week is certainly adequate for me. If I >> leave a link 'active' for longer than that w/out activity, I deserve to >> lose the link > >Surely that violates POLA? That upsets people who have keepalive >turned on already and find 1 week is way too long. For instance, >we use keepalive to get rid of stuck netscapes, and we'd probably >run out of swap or mbufs if it went up to a week. We just managed >by putting this in rc.local: > >sysctl -w net.inet.tcp.always_keepalive=1 My intent was an "implementation" which would set: net.inet.tcp.keepidle: 86400 net.inet.tcp.keepintvl: 64800 net.inet.tcp.always_keepalive: 1 Leaving people to set whatever they want for a local policy. All I'm talking about is what our default should be... -- 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 Tue Jun 1 13:37: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 3ACAE15826; Tue, 1 Jun 1999 13:36:57 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id NAA06799; Tue, 1 Jun 1999 13:30:38 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 01 Jun 1999 13:30:38 -0700 Date: Tue, 1 Jun 1999 13:30:37 -0700 (PDT) From: X-Sender: kip@luna To: Julian Elischer Cc: Nate Williams , Matthew Hunt , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: julian@whistle.com,nate@mt.sri.com,mph@astro.caltech.edu,phk@FreeBSD.ORG,current@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it that long? I honestly don't think I have ever seen one stay up for a week. Are you sure you did not mean 48 hours? I don't speak in jest. -Kip On Tue, 1 Jun 1999, Julian Elischer wrote: > how about a keepalive of 48 days.. the maximum a W95 machine can stay > alive... :-) > > > > > > 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 1 13:37:34 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 3E3B1150AD for ; Tue, 1 Jun 1999 13:37:27 -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 NAA22054; Tue, 1 Jun 1999 13:30:32 -0700 (PDT) Date: Tue, 1 Jun 1999 13:30:31 -0700 (PDT) From: Julian Elischer To: David Schwartz Cc: Poul-Henning Kamp , Matthew Hunt , kip@lyris.com, Nate Williams , current@FreeBSD.ORG Subject: RE: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <000001beac6b$dc847920$021d85d1@whenever.youwant.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 maybe we should fix our SERVER apps.. e.g. telnetd, sshd, etc. to have 1 week timeouts On Tue, 1 Jun 1999, David Schwartz wrote: > > Why not just fix the application programs that really want timeouts but > don't implement them? > > DS > > > Mind you, this is only a problem because FreeBSD is to bloddy > > stable: I logged into a customers server a few days a go, it had > > been up for over a year, and had accumulated tons of ftpds from > > WIN* machines which had gotten a vulcan nerve pinch or a different > > IP#. (I'm sure windows NT servers doesn't have this problem at > > all) > > > > It doesn't have to be 2h timeout. I would be happy with a default > > of 24h, even one week would be OK with me. > > > > But infinity is too long for my taste. > > > > Can people live with a one week TCP keepalive as default ? > > > > 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 1 13:45: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id 216FB150AD for ; Tue, 1 Jun 1999 13:44:47 -0700 (PDT) (envelope-from npp@distortion.dk) Received: from localhost (npp@localhost) by distortion.dk (8.9.1/8.9.1) with ESMTP id AAA01343 for ; Wed, 2 Jun 1999 00:19:29 +0200 (CEST) (envelope-from npp@distortion.dk) Date: Wed, 2 Jun 1999 00:19:29 +0200 (CEST) From: Nicolai Petri To: current@freebsd.org Subject: How do I change IRQ priority for pcm ? 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 think newbus is come a long way now. But I still have a problem wich I believe is related to newbus. When I try to play and MP3 file. It's sounds like the soundcard plays the DMA buffer 3-4 times before reloading new data into it ! (missing ints??) Would it be possible to increase int. priority on the card.. And could it make a difference ?? -------- Nicolai Petri npp@swamp.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 13:46:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id 60DD615824 for ; Tue, 1 Jun 1999 13:46:26 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id NAA22765; Tue, 1 Jun 1999 13:42:32 -0700 (PDT) (envelope-from mph) Date: Tue, 1 Jun 1999 13:42:32 -0700 From: Matthew Hunt To: Julian Elischer Cc: David Schwartz , Poul-Henning Kamp , kip@lyris.com, Nate Williams , current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990601134232.A22685@wopr.caltech.edu> References: <000001beac6b$dc847920$021d85d1@whenever.youwant.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Julian Elischer on Tue, Jun 01, 1999 at 01:30:31PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 01, 1999 at 01:30:31PM -0700, Julian Elischer wrote: > maybe we should fix our SERVER apps.. > e.g. telnetd, sshd, etc. to have 1 week timeouts IIRC, it is not possible to specify how long the keepalive interval should be, using the socket interface. Do you suggest we add a new interface not present in other Unix implementations, or that we make SO_KEEPALIVE always have a one-week timeout, surprising the other applications that expect it to be faster? Both of these seem remarkably unappealing to me. Matt -- Matthew Hunt * Inertia is a property http://www.pobox.com/~mph/ * of matter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 14: 0: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 29677150AD for ; Tue, 1 Jun 1999 13:59:57 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Tue, 1 Jun 1999 13:59:48 -0700 From: "David Schwartz" To: "Matthew Hunt" , "Julian Elischer" Cc: "Poul-Henning Kamp" , , "Nate Williams" , Subject: RE: net.inet.tcp.always_keepalive on as default ? Date: Tue, 1 Jun 1999 13:59:48 -0700 Message-ID: <000001beac71$af125a10$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <19990601134232.A22685@wopr.caltech.edu> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think he was suggesting that the apps close the connection if they receive no data from some amount of time. (Isn't this common sense?) DS > On Tue, Jun 01, 1999 at 01:30:31PM -0700, Julian Elischer wrote: > > > maybe we should fix our SERVER apps.. > > e.g. telnetd, sshd, etc. to have 1 week timeouts > > IIRC, it is not possible to specify how long the keepalive interval > should be, using the socket interface. Do you suggest we add a new > interface not present in other Unix implementations, or that we make > SO_KEEPALIVE always have a one-week timeout, surprising the other > applications that expect it to be faster? > > Both of these seem remarkably unappealing to me. > > Matt > > -- > Matthew Hunt * Inertia is a property > http://www.pobox.com/~mph/ * of matter. > > > 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 1 14: 6:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id 660F314F6C for ; Tue, 1 Jun 1999 14:06:19 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id OAA23103; Tue, 1 Jun 1999 14:01:46 -0700 (PDT) (envelope-from mph) Date: Tue, 1 Jun 1999 14:01:46 -0700 From: Matthew Hunt To: David Schwartz Cc: Julian Elischer , Poul-Henning Kamp , kip@lyris.com, Nate Williams , current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990601140146.A23081@wopr.caltech.edu> References: <19990601134232.A22685@wopr.caltech.edu> <000001beac71$af125a10$021d85d1@whenever.youwant.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <000001beac71$af125a10$021d85d1@whenever.youwant.to>; from David Schwartz on Tue, Jun 01, 1999 at 01:59:48PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 01, 1999 at 01:59:48PM -0700, David Schwartz wrote: > I think he was suggesting that the apps close the connection if they > receive no data from some amount of time. (Isn't this common sense?) No, I frequently keep telnet/ssh connections idle for long periods, and have no particular desire for them to close on me. -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 14:10:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 3DA7814D08 for ; Tue, 1 Jun 1999 14:09:39 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Tue, 1 Jun 1999 14:09:29 -0700 From: "David Schwartz" To: "Matthew Hunt" Cc: "Julian Elischer" , "Poul-Henning Kamp" , , "Nate Williams" , Subject: RE: net.inet.tcp.always_keepalive on as default ? Date: Tue, 1 Jun 1999 14:09:29 -0700 Message-ID: <000001beac73$097b3ac0$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <19990601140146.A23081@wopr.caltech.edu> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, exactly, everybody wants something different. That's why you don't want to enforce a new policy in the kernel. Let each app choose the policy that makes the most sense for it, either with or without command line options or whatnot. But an application that is not happy with the default TCP timeout semantics and doesn't enforce something else is broken. DS > On Tue, Jun 01, 1999 at 01:59:48PM -0700, David Schwartz wrote: > > > I think he was suggesting that the apps close the connection if they > > receive no data from some amount of time. (Isn't this common sense?) > > No, I frequently keep telnet/ssh connections idle for long periods, > and have no particular desire for them to close on me. > > -- > Matthew Hunt * Stay close to the Vorlon. > http://www.pobox.com/~mph/ * > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 14:24:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by hub.freebsd.org (Postfix) with ESMTP id 761A014F34; Tue, 1 Jun 1999 14:24:07 -0700 (PDT) (envelope-from se@dialup124.zpr.Uni-Koeln.DE) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.9.3/8.9.3) id VAA00694; Mon, 31 May 1999 21:50:07 +0200 (CEST) (envelope-from se) Date: Mon, 31 May 1999 21:50:07 +0200 From: Stefan Esser To: oZZ!!! Cc: Doug White , Brian Feldman , W Gerald Hicks , Marc van Woerkom , hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net, Stefan Esser Subject: Re: No sound (Ensoniq Audio PCI 1370) Message-ID: <19990531215007.A650@dialup124.mi.uni-koeln.de> Reply-To: se@FreeBSD.ORG Mail-Followup-To: oZZ!!! , Doug White , Brian Feldman , W Gerald Hicks , Marc van Woerkom , hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from oZZ!!! on Thu, May 27, 1999 at 10:12:35PM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-05-27 22:12 +0400, oZZ!!! wrote: > > wmsound with my card too can't work correct. > SB 128 PCI its a PCI-device & (as i known) it must be detect as es0 + pcm1 > (not pcm0), because pcm0 reserved for ISA-device (right?). Kernel at > boot-time detect my SB 128 PCI as es0 + pcm0... You are using -current, and that will in fact attach the PCI card as pcm0. Please try the following line your kernel config file: device pcm0 at pci? And be sure to remove any line that configures pcm0 on ISA ... What's going on ? I guess that after the PCI attach of es0/pcm0, the ISA probe tries to attach an ISA card as pcm0, too, and stomps over the values filled into the device structure for the PCI card ... But I did not have time to look into this more closer, currently it is just an assumption based on the behaviour you describe (and I found a few days ago ;-) Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 14:24:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id DDC0B15837 for ; Tue, 1 Jun 1999 14:24:44 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id OAA07101; Tue, 1 Jun 1999 14:04:46 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 01 Jun 1999 14:04:45 -0700 Date: Tue, 1 Jun 1999 14:04:45 -0700 (PDT) From: X-Sender: kip@luna To: David Schwartz Cc: Matthew Hunt , Julian Elischer , Poul-Henning Kamp , Nate Williams , current@freebsd.org Subject: RE: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <000001beac71$af125a10$021d85d1@whenever.youwant.to> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: davids@webmaster.com,mph@astro.caltech.edu,julian@whistle.com,phk@critter.freebsd.dk,nate@mt.sri.com,current@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This does make sense. I do some work on a mail server and I don't use keepalives because 2 hours is _too_much_ time to be wasting a descriptor. I periodically check how long a connection has been open and if it exceeds a certain amount I close the connection. -Kip On Tue, 1 Jun 1999, David Schwartz wrote: > > I think he was suggesting that the apps close the connection if they > receive no data from some amount of time. (Isn't this common sense?) > > DS > > > On Tue, Jun 01, 1999 at 01:30:31PM -0700, Julian Elischer wrote: > > > > > maybe we should fix our SERVER apps.. > > > e.g. telnetd, sshd, etc. to have 1 week timeouts > > > > IIRC, it is not possible to specify how long the keepalive interval > > should be, using the socket interface. Do you suggest we add a new > > interface not present in other Unix implementations, or that we make > > SO_KEEPALIVE always have a one-week timeout, surprising the other > > applications that expect it to be faster? > > > > Both of these seem remarkably unappealing to me. > > > > Matt > > > > -- > > Matthew Hunt * Inertia is a property > > http://www.pobox.com/~mph/ * of matter. > > > > > > 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 14:30:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from ra.eng.mindspring.net (ra.eng.mindspring.net [207.69.192.184]) by hub.freebsd.org (Postfix) with SMTP id A16B514FDA for ; Tue, 1 Jun 1999 14:30:25 -0700 (PDT) (envelope-from sj@ra.eng.mindspring.net) Received: (qmail 21107 invoked by uid 52477); 1 Jun 1999 21:30:13 -0000 To: current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <19990601130331.A21176@wopr.caltech.edu> <22394.928267922@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii From: Sudish Joseph Date: 01 Jun 1999 17:30:13 -0400 In-Reply-To: Poul-Henning Kamp's message of "Tue, 01 Jun 1999 22:12:02 +0200" Message-ID: Lines: 22 User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) XEmacs/21.2(beta12) (Clio) MIME-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > Mind you, this is only a problem because FreeBSD is to bloddy > stable: I logged into a customers server a few days a go, it had > been up for over a year, and had accumulated tons of ftpds from If this customer is using wu-ftpd, it's very possible that you saw daemons blocked inside of accept() for PASV data connections. We used to see the same behavior here wrt. ftpds hanging around and it was almost always the case that the socket was in the LISTEN state. The code (ftpd.c:dataconn()) was changed to time out the data connection establishment using select() before calling accept(). If the client doesn't connect within 15 minutes, we log the event and the daemon exits. A diff against our code wouldn't be helpful, since we've added our own ugly warts to it (but I'll do so if you want it). If this is indeed the same problem you're seeing, tcp keepalives won't help. I haven't looked at the FreeBSD ftpd code to see if the accept is timed out somehow to prevent this (possibly inadvertent) DOS attack. -- Sudish Joseph MindSpring Enterprises To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 14:47:30 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 0F4A7150AD for ; Tue, 1 Jun 1999 14:47:12 -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 WAA25080; Tue, 1 Jun 1999 22:46:40 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 1 Jun 1999 22:46:40 +0100 (BST) From: Doug Rabson To: Bruce Evans Cc: current@freebsd.org, newton@atdot.dotat.org Subject: Re: IRQ sharing with newbus In-Reply-To: <199906011936.FAA11098@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 Wed, 2 Jun 1999, Bruce Evans wrote: > >Under newbus, of course, things look slightly different, so I tried > >this: > > > >device sio2 at isa? port 0x280 flags 0x0201 irq 5 > >device sio3 at isa? port 0x288 flags 0x0201 > >device sio4 at isa? port 0x290 flags 0x0201 > > [ ... ] > >device sio9 at isa? port 0x2b8 flags 0x0201 > > > >Natch: "panic: NULL irq resource!" from nexus_setup_intr() in > >sys/i386/i386/nexus.c while probing sio3 (and I know that sio2 > >is probing successfully - see below). > > This was apparently broken when sio was converted to new-bus. The driver > (actually mainly isa.c) used to simply skip irq allocation for devices > with no irq (COM_MULTIPORT non-master ones and polled ones). This is almost certainly just simple breakage. I'll take a look at the code and see if I can spot something. The slave devices shouldn't be trying to allocate interrupts at all. > > >Assuming (from the panic message) that it wants an IRQ, I've tried this: > > > >device sio2 at isa? port 0x280 flags 0x0201 irq 5 conflicts > >device sio3 at isa? port 0x288 flags 0x0201 irq 5 conflicts > > [ ... ] > >device sio9 at isa? port 0x2b8 flags 0x0201 irq 5 conflicts > > > >Same bat-panic, same bat-probe. > > I don't understand why this doesn't get further, since the RF_SHAREABLE > flag is (incorrectly) specified. sio fast interrupts are particularly > unshareable. sio now forces fast interrupts, although this is wrong for > sio pccard devices. > > >So, guys -- What is the officially blessed way of sharing IRQs under > >newbus? > > It should be almost the same as it used to be: specify RF_SHAREABLE for > allocating shared irq resources; this corresponds to not specifying > INTR_EXCL in the pre-new-bus interface (intr_create()?). I don't think the sio multiport stuff needs to use RF_SHAREABLE - the master device knows how to field interrupts for the slaves (at least thats how I understood it). -- 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 Tue Jun 1 14:47:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 4C0E31584A for ; Tue, 1 Jun 1999 14:47:48 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 29081 invoked by uid 1001); 1 Jun 1999 21:47:42 +0000 (GMT) To: mph@astro.caltech.edu Cc: julian@whistle.com, davids@webmaster.com, phk@critter.freebsd.dk, kip@lyris.com, nate@mt.sri.com, current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? From: sthaug@nethelp.no In-Reply-To: Your message of "Tue, 1 Jun 1999 13:42:32 -0700" References: <19990601134232.A22685@wopr.caltech.edu> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 01 Jun 1999 23:47:42 +0200 Message-ID: <29074.928273662@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > maybe we should fix our SERVER apps.. > > e.g. telnetd, sshd, etc. to have 1 week timeouts > > IIRC, it is not possible to specify how long the keepalive interval > should be, using the socket interface. Do you suggest we add a new > interface not present in other Unix implementations, or that we make > SO_KEEPALIVE always have a one-week timeout, surprising the other > applications that expect it to be faster? There *is* a well defined interface for this, namely the TCP_KEEPALIVE socket option. This is a *per connection* keepalive timer, and is implemented by for instance Solaris 2.6. See http://www.unix-systems.org/single_unix_specification_v2/xns/xti.h.html Also mentioned in Stevens vol. 2 as far as I can remember. If the FreeBSD kernel implemented TCP_KEEPALIVE, it would be rather simple to set this on an application basis. (No, unfortunately, I'm not offering to implement it.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 14:48:19 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 C713515881 for ; Tue, 1 Jun 1999 14:48:14 -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 WAA25087; Tue, 1 Jun 1999 22:48:14 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 1 Jun 1999 22:48:14 +0100 (BST) From: Doug Rabson To: "Matthew N. Dodd" Cc: Mark Newton , current@freebsd.org Subject: Re: IRQ sharing with newbus 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 Tue, 1 Jun 1999, Matthew N. Dodd wrote: > On Tue, 1 Jun 1999, Mark Newton wrote: > > So, guys -- What is the officially blessed way of sharing IRQs under > > newbus? > > If you find out, let me know since the EISA code suffers the same problem > (though the drivers do a bit better job detecting the condition, and just > fail to attach instead of panicing.) For EISA, it should be possible to add RF_SHAREABLE to the bus_alloc_resource call (assuming that EISA interrupts are shareable like pci interrupts). -- 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 Tue Jun 1 14:52:29 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 351AA1515A for ; Tue, 1 Jun 1999 14:51:55 -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 WAA25100; Tue, 1 Jun 1999 22:52:08 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 1 Jun 1999 22:52:08 +0100 (BST) From: Doug Rabson To: Nicolai Petri Cc: current@freebsd.org Subject: Re: How do I change IRQ priority for pcm ? 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, 2 Jun 1999, Nicolai Petri wrote: > I think newbus is come a long way now. But I still have a problem wich I > believe is related to newbus. > > When I try to play and MP3 file. It's sounds like the soundcard plays the > DMA buffer 3-4 times before reloading new data into it ! (missing ints??) > > Would it be possible to increase int. priority on the card.. And could it > make a difference ?? I don't think interrupt priority is the problem. Its probably something dumb which I have missed so far but I haven't spotted the problem yet. -- 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 Tue Jun 1 14:53:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from turing.mathematik.uni-ulm.de (turing.mathematik.uni-ulm.de [134.60.166.1]) by hub.freebsd.org (Postfix) with SMTP id EFFD515868; Tue, 1 Jun 1999 14:53:06 -0700 (PDT) (envelope-from kuebart@mathematik.uni-ulm.de) Received: by turing.mathematik.uni-ulm.de (5.x/UniUlm-2.0m) id AA10689; Tue, 1 Jun 1999 23:52:56 +0200 From: kuebart@mathematik.uni-ulm.de (Joachim Kuebart) Message-Id: <9906012152.AA10689@turing.mathematik.uni-ulm.de> Subject: Re: No sound (Ensoniq Audio PCI 1370) To: se@FreeBSD.ORG Date: Tue, 1 Jun 1999 23:52:56 +0200 (MET DST) Cc: osa@etrust.ru, dwhite@resnet.uoregon.edu, green@unixhelp.org, wghicks@bellsouth.net, van.woerkom@netcologne.de, hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net, se@FreeBSD.ORG In-Reply-To: <19990531215007.A650@dialup124.mi.uni-koeln.de> from Stefan Esser at "May 31, 99 09:50:07 pm" X-Mailer: ELM [version 2.4ME+ PL22 (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 Stefan Esser wrote: > On 1999-05-27 22:12 +0400, oZZ!!! wrote: > > > > wmsound with my card too can't work correct. > > SB 128 PCI its a PCI-device & (as i known) it must be detect as es0 + pcm1 > > (not pcm0), because pcm0 reserved for ISA-device (right?). Kernel at > > boot-time detect my SB 128 PCI as es0 + pcm0... > > What's going on ? > > I guess that after the PCI attach of es0/pcm0, the ISA probe tries to > attach an ISA card as pcm0, too, and stomps over the values filled into > the device structure for the PCI card ... That's right, and it's because the implementation is broken: the PCI driver part in /sys/pci/es1370.c uses the name "es" instead of "pcm". I.e. if it used "pcm", different unit numbers would get assigned to ISA and PCI devices and no clashes would result. Sorry I didn't make this a PR before, but I'm working on the driver and it's in no condition to be released. This was my fault, so here's the fix: Index: es1370.c =================================================================== RCS file: /usr/CVS-Repository/src/sys/pci/es1370.c,v retrieving revision 1.4 diff -u -r1.4 es1370.c --- es1370.c 1999/05/09 17:06:45 1.4 +++ es1370.c 1999/06/01 21:51:37 @@ -147,7 +147,7 @@ */ static struct pci_device es_pci_driver = { - "es", + "pcm", es_pci_probe, es_pci_attach, &nsnd, cu Jo --------------------------------------------------------------------- PGP Key is at What am I doing here? God, these people drinking milk! But the clothes they wear look rather cool to me. Joachim Kuebart I wear the same -- what am I doing here? Ulm, Germany --- Banana Fishbones To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 14:55:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 5342C15597; Tue, 1 Jun 1999 14:54:53 -0700 (PDT) (envelope-from osa@etrust.ru) Received: from localhost (unknown [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 8545AD0; Tue, 1 Jun 1999 21:54:47 +0000 (GMT) Date: Wed, 2 Jun 1999 01:54:47 +0400 (MSD) From: Osokin Sergey To: Stefan Esser Cc: Doug White , Brian Feldman , W Gerald Hicks , Marc van Woerkom , hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: No sound (Ensoniq Audio PCI 1370) In-Reply-To: <19990531215007.A650@dialup124.mi.uni-koeln.de> 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, 31 May 1999, Stefan Esser wrote: > On 1999-05-27 22:12 +0400, oZZ!!! wrote: > > > > wmsound with my card too can't work correct. > > SB 128 PCI its a PCI-device & (as i known) it must be detect as es0 + pcm1 > > (not pcm0), because pcm0 reserved for ISA-device (right?). Kernel at > > boot-time detect my SB 128 PCI as es0 + pcm0... > > You are using -current, and that will in fact attach the PCI card as pcm0. > Please try the following line your kernel config file: > > device pcm0 at pci? i have following string at my kernel: device pcm0 > > And be sure to remove any line that configures pcm0 on ISA ... > > What's going on ? > > I guess that after the PCI attach of es0/pcm0, the ISA probe tries to > attach an ISA card as pcm0, too, and stomps over the values filled into > the device structure for the PCI card ... > > But I did not have time to look into this more closer, currently it is just > an assumption based on the behaviour you describe (and I found a few days > ago ;-) I talk about my problem with Joachim Kuebart & he send me a patch. > > Regards, STefan > Rgdz, Osokin Sergey aka oZZ, osa@etrust.ru http://www.freebsd.org.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 15: 3: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id ABD3D15820; Tue, 1 Jun 1999 15:02:49 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA84865; Tue, 1 Jun 1999 15:02:47 -0700 (PDT) (envelope-from dillon) Date: Tue, 1 Jun 1999 15:02:47 -0700 (PDT) From: Matthew Dillon Message-Id: <199906012202.PAA84865@apollo.backplane.com> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <20883.928262460@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :... Sheesh, talk about a topic to generate noise! I think keepalive's could easily be turned on by default. At BEST, one of the first things I did 5 years ago was to turn them on permanently on all of our machines. The reason is simple: Without keepalives you can end up with stale connections that hang forever due to users hanging up their modems without disconnecting telnet, pop, and other assorted sessions. Turning on keepalives will produce NO DISCERNABLE INCREASE IN NETWORK TRAFFIC. Period. Anybody who says they do doesn't understand how keepalives work. You could have a thousand active connections and it still wouldn't show a discernable increase. Daemons do not usually bother to turn on per-connection keepalives. I do not consider this a bug in the daemon, but instead simply a "the default nature of this daemon is to use the default keepalive state assigned to the system as a whole". Simple. Not a bug. We should NOT go around trying to 'fix' all of our daemons. The only argument against turning on keepalives by default is that occassionally someone will expect their telnet to hang around after the network inbetween them and the remote site has been down for hours. This used to be a HUGE argument in the days where networks were less reliable and dialup lines were scarse. It is not an argument now, however. Whatever we do, we should not start messing around with the internals of the kernel trying to 'fix' a non-problem. Keepalives work just dandy as they are currently implemented, we do not have to mess with it beyond possibly changing the default in rc.conf. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 15:13:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 67B7615822 for ; Tue, 1 Jun 1999 15:13:05 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40399>; Wed, 2 Jun 1999 07:57:05 +1000 Date: Wed, 2 Jun 1999 08:12:52 +1000 From: Peter Jeremy Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: <20883.928262460@critter.freebsd.dk> To: current@FreeBSD.ORG Message-Id: <99Jun2.075705est.40399@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: >Considering the number of hosts on the net today, which come and >go with no warning and with dynamic IP assignments, I would propose >that we disregard what the "old farts" felt about TCP keepalives, >and enable the sysctl net.inet.tcp.always_keepalive as default. I think this sounds reasonable, but in this case, all the relevant knobs need to be documented. There's currently no documententation strings for any of net.inet.tcp.keepidle, net.inet.tcp.keepintvl or net.inet.tcp.keepinit. It's also not immediately obvious that these counters are all in 500msec intervals I believe we should also add sysctl knobs for tcp_keepcnt and tcp_maxpersistidle (the latter because it shares the same default value - TCPTV_KEEP_IDLE - with tcp_keepidle). And, whilst studying the code, I notice that the comments in netinet/tcp_timer.h state: * an ack segment in response from the peer. If, despite the TCPT_KEEP * initiated segments we cannot elicit a response from a peer in TCPT_MAXIDLE * amount of time probing, then we drop the connection. But there's no variable or macro `TCPT_MAXIDLE'. The connection is dropped after tcp_maxidle = tcp_keepcnt [fixed at TCPTV_KEEPCNT=8] * tcp_keepintvl [initially TCPTV_KEEPINTVL=75s, adjust via net.inet.tcp.keepintvl]. Does one of the committers feel like fixing this, or should I just send-pr it? Matthew Hunt wrote: >I'm thinking of long-lived connections like telnet and ssh; if you're >doing work over such a connection, it would be nice if the connection >endured an outage while you're away sleeping, like it does without >keepalives. I'm not sure this point is valid. An increasing percentage of such connections will be using dynamic IP addresses - so you can't be sure that you'll get the same address back. And this presupposes that neither system tries to send anything across the link whilst it's dead. Nate Williams wrote: >Off == 1 week KEEPALIVE >ON == traditiona 1 hour KEEPALIVe. ^^^^^^ 2 hours actually. I think that definitely violates POLA. If I have keepalives off (for whatever reason), I expect there to be _no_ keepalives - not just less frequent keepalives. We'd need to make net.inet.tcp.always_keepalive a 3-way switch: on, off and 'i_dont_want_any_!@%$!#@_keepalives' :-) Poul-Henning Kamp wrote: >My intent was an "implementation" which would set: > > net.inet.tcp.keepidle: 86400 12-hour keepalives. That's different to previous suggestions :-). > net.inet.tcp.keepintvl: 64800 I don't see any real need to extend the default keepintvl. I suspect a slow burst (currently every 75 secs) is probably better than this chinese water-torture approach. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 15:32:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id D677F15849 for ; Tue, 1 Jun 1999 15:31:43 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA07335 for current@FreeBSD.ORG; Wed, 2 Jun 1999 00:31:42 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id D051A87AE; Wed, 2 Jun 1999 00:13:50 +0200 (CEST) (envelope-from roberto) Date: Wed, 2 Jun 1999 00:13:50 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990602001350.A35065@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <199906011851.MAA14756@mt.sri.com> <19990601130331.A21176@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: <19990601130331.A21176@wopr.caltech.edu>; from Matthew Hunt on Tue, Jun 01, 1999 at 01:03:31PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5322 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Matthew Hunt: > I'm thinking of long-lived connections like telnet and ssh; if you're FWIW ssh has been using keelalives for a long time by default... KeepAlive Specifies whether the system should send keepalive messages to the other side. If they are sent, death of the connection or crash of one of the machines will be properly noticed. However, this means that connections will die if the route is down temporarily, and some people find it annoying. The default is "yes" (to send keepalives), and the client will notice if the network goes down or the remote host dies. This is important in scripts, and many users want it too. To disable keepalives, the value should be set to "no" in both the server and the client configura- tion files. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #71: Sun May 9 20:16:32 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 15:50:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from eterna.binary.net (eterna.binary.net [12.13.84.6]) by hub.freebsd.org (Postfix) with ESMTP id 1DF0B14C82 for ; Tue, 1 Jun 1999 15:50:37 -0700 (PDT) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id RAA09954; Tue, 1 Jun 1999 17:50:36 -0500 (CDT) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id RAA13890; Tue, 1 Jun 1999 17:50:36 -0500 (CDT) Date: Tue, 1 Jun 1999 18:50:35 -0400 From: Nathan Dorfman To: John Polstra Cc: dwhite@resnet.uoregon.edu, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? Message-ID: <19990601185035.A11288@rtfm.net> References: <199905280446.VAA06342@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199905280446.VAA06342@vashon.polstra.com>; from John Polstra on Thu, May 27, 1999 at 09:46:51PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 27, 1999 at 09:46:51PM -0700, John Polstra wrote: > In article , > Doug White wrote: > > > I second the suggestion to 'autoprobe' PASV support, and revert to active > > mode (w/ an appropriate msg) if PASV is refused. > > That won't be a good solution in practice. When passive mode doesn't > work, it's almost always because a firewall on the server side is > blocking the incoming data connection. The client doesn't see a > refusal; its connect() call just times out. The trouble is, the > timeout takes a long time (on the order of a minute or more). Certain shareware lose95 FTP servers don't know how to do passive mode. The NetBSD ftp client uses passive mode by default, but will send a PORT if the PASV is unsuccessful. > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-interest is the aphrodisiac of belief." -- James V. DeLong -- Nathan Dorfman The statements and opinions in my Unix Admin @ Frontline Communications public posts are mine, not FCC's. "The light at the end of the tunnel is the headlight of an approaching train." --/usr/games/fortune To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 16:41:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 9A6B414DC3 for ; Tue, 1 Jun 1999 16:41:09 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id TAA23829; Tue, 1 Jun 1999 19:40:14 -0400 (EDT) Date: Tue, 1 Jun 1999 19:40:14 -0400 (EDT) From: "Matthew N. Dodd" To: Doug Rabson Cc: Mark Newton , current@freebsd.org Subject: Re: IRQ sharing with newbus 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 Tue, 1 Jun 1999, Doug Rabson wrote: > For EISA, it should be possible to add RF_SHAREABLE to the > bus_alloc_resource call (assuming that EISA interrupts are shareable > like pci interrupts). The observed behavior suggests that RF_SHAREABLE is not being honored. dpt99: DPT PM2022A/9X FW Rev. 07CK, 1 channel, 64 CCBs dpt0: at slot 4 on eisa0 dpt0: DPT PM2022A/9X FW Rev. 07CK, 1 channel, 64 CCBs dpt99: DPT PM2022A/9X FW Rev. 005A, 1 channel, 64 CCBs dpt1: at slot 5 on eisa0 dpt1: No irq?! device_probe_and_attach: dpt1 attach returned -1 (The 'dpt99' lines are an artifact of the mechanism I'm using to complete the probe.) Now, since the resource ranges aren't printed anymore, you can't see that both cards are using (set to use) the same IRQ. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 16:56:27 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 0654714D13 for ; Tue, 1 Jun 1999 16:56:23 -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 TAA18849; Tue, 1 Jun 1999 19:56:14 -0400 (EDT) (envelope-from wollman) Date: Tue, 1 Jun 1999 19:56:14 -0400 (EDT) From: Garrett Wollman Message-Id: <199906012356.TAA18849@khavrinen.lcs.mit.edu> To: Doug Rabson Cc: Bruce Evans , current@FreeBSD.ORG, newton@atdot.dotat.org Subject: Re: IRQ sharing with newbus In-Reply-To: References: <199906011936.FAA11098@godzilla.zeta.org.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I don't think the sio multiport stuff needs to use RF_SHAREABLE - the > master device knows how to field interrupts for the slaves (at least thats > how I understood it). But the sio non-multiport stuff should be able to use RF_TIMESHARE. -- If I'm not using my serial port, I should be able to use my infrared.... -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 Tue Jun 1 20:29:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from midgard.dhs.org (dhcp9560151.columbus.rr.com [24.95.60.151]) by hub.freebsd.org (Postfix) with ESMTP id B00FF15140 for ; Tue, 1 Jun 1999 20:29:11 -0700 (PDT) (envelope-from caa@midgard.dhs.org) Received: (from caa@localhost) by midgard.dhs.org (8.9.3/8.9.3) id XAA17988; Tue, 1 Jun 1999 23:29:02 -0400 (EDT) (envelope-from caa) Date: Tue, 1 Jun 1999 23:29:02 -0400 From: Charles Anderson To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: cdevsw changes broke world in vinum Message-ID: <19990601232902.A17503@midgard.dhs.org> References: <44684.928232223@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <44684.928232223@axl.noc.iafrica.com>; from Sheldon Hearn on Tue, Jun 01, 1999 at 12:17:03PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 01, 1999 at 12:17:03PM +0200, Sheldon Hearn wrote: > > The offending line is: > > cdevsw[CDEV_MAJOR] = NULL; /* no cdevsw any more */ > > Should that be vinum_cdevsw? Or did I get unlucky and pull sources > between commits? > > Ciao, > Sheldon. I got the same error, I supped around 10, did a buildworld, look at the results later in the afternoon, saw the error, did a make dirclean, re- supped, and rebuilt, same error. So I say unless the commits were REAL far apart, it wasn't between commits. -Charlie -- Charles Anderson caa@midgard.dhs.org No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 20:48: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id E8EB115116 for ; Tue, 1 Jun 1999 20:47:24 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id OAA05481; Wed, 2 Jun 1999 14:05:31 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199906020405.OAA05481@cimlogic.com.au> Subject: Re: cdevsw changes broke world in vinum In-Reply-To: <19990601232902.A17503@midgard.dhs.org> from Charles Anderson at "Jun 1, 1999 11:29: 2 pm" To: caa@midgard.dhs.org (Charles Anderson) Date: Wed, 2 Jun 1999 14:05:30 +1000 (EST) Cc: sheldonh@uunet.co.za, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charles Anderson wrote: > On Tue, Jun 01, 1999 at 12:17:03PM +0200, Sheldon Hearn wrote: > > > > The offending line is: > > > > cdevsw[CDEV_MAJOR] = NULL; /* no cdevsw any more */ > > > > Should that be vinum_cdevsw? Or did I get unlucky and pull sources > > between commits? > > > > Ciao, > > Sheldon. > > I got the same error, I supped around 10, did a buildworld, look at the > results later in the afternoon, saw the error, did a make dirclean, re- > supped, and rebuilt, same error. So I say unless the commits were REAL > far apart, it wasn't between commits. If you were reading the commit messages, you would have noticed that phk said he mailed patches for vinum and i4b to the respective authors. i4b has since been fixed (AFAIK) and vinum is waiting for Greg to stop galavanting around China on his way to Usenix.... I doubt that he'll be able to do anything for a few weeks. Just be patient. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 22:19: 4 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 5361814D50 for ; Tue, 1 Jun 1999 22:19:02 -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 WAA26523; Tue, 1 Jun 1999 22:19:01 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA42622; Tue, 1 Jun 1999 22:19:00 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <17780.928175695@brown.pfcs.com> Date: Tue, 01 Jun 1999 22:19:00 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Harlan Stenn Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Harlan Stenn wrote: > First, what's wrong with stamping the files in a mirror with the timestamp > it has on the master? That's what it does already. > Second, how much work would it be to add, say, md5 checksums to CVS. CVSup can already do md5 checksums, but I don't see how it would help here. Remember the problem we're trying to solve: find out quickly whether a given server would regress any of the client's files. > Third, isn't the version number useful for something? Yes, there's promise there. But there are things such as tags that don't have any history associated with them. Also, not all files are RCS files. 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 Tue Jun 1 22:22:32 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 4DD2D14D50 for ; Tue, 1 Jun 1999 22:22:30 -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 WAA26555; Tue, 1 Jun 1999 22:22:29 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA42632; Tue, 1 Jun 1999 22: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 In-Reply-To: <199905311851.LAA11628@troutmask.apl.washington.edu> Date: Tue, 01 Jun 1999 22:22:28 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Steve Kargl Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl wrote: > > If you want a robust (but probably really slow) algorithm, you > could use the revision number of a file. I'd really prefer to have something for the whole collection. If it has to check every file, then it will take about as long as doing an update. I want it to be able to decide very quickly on a per-collection basis before updating anything. > Isn't this a monotonically increasing number? The version numbers should monotonically increase. But they don't always do so, in practice. CVS repository managers occasionally have to do damage control that entails deleting deltas. > Would it be possible to compute md5 signatures on a per-file per-collection > basis? The cvsup server would have, for example, src-bin.md5 which > contains a list of all files in the src-bin collection and their > md5 signatures. When a connection is made to the server, the server > sends src-bin.md5 to the client. The client compares the local > src-bin.md5 with the server's src-bin.md5. Any difference would > indicate a file has changed, and the client then requests the > server to send the changed file(s). But comparing checksums only tells you whether the files are (probably) the same or not. It doesn't tell you which one is more up-to-date. 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 Tue Jun 1 22:27:41 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 5B86E14D50 for ; Tue, 1 Jun 1999 22:27:39 -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 WAA26598; Tue, 1 Jun 1999 22:27:38 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA42661; Tue, 1 Jun 1999 22:27:37 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 01 Jun 1999 22:27:37 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Alex Zepeda Subject: Re: Announcing a new cvsup server - cvsup6.freebsd.org Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > Since cvsup can take a revision of a file from a given time, why not > use the time that the cvsup was started, this way it will ignore > anything that was modified while cvsup was running, and the mirror > can say, all the files are from xx.yy.zz point in time. Something like that might help. It's true that CVSup could ignore deltas newer than when it started. Tags don't have dates associated with them, so they're harder. But they do point to deltas, so still there's hope. > And then have xntpd or somesuch running, so that all the cvsup mirrors > have the same idea of when xx.yy.zz was.. Cheater! ;-) Seriously, there are all kinds of mirrors out there, and you really can't be sure they'll all have accurate timekeeping. 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 Tue Jun 1 22:27:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id E583C15281 for ; Tue, 1 Jun 1999 22:27:46 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id HAA02882 for ; Wed, 2 Jun 1999 07:27:45 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Wed, 2 Jun 1999 07:27:39 +0200 (CEST) From: Leif Neland Cc: current@FreeBSD.ORG Subject: Re: cdevsw changes broke world in vinum In-Reply-To: <199906020405.OAA05481@cimlogic.com.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 Wed, 2 Jun 1999, John Birrell wrote: > > > cdevsw[CDEV_MAJOR] = NULL; /* no cdevsw any more */ > > > > > > Should that be vinum_cdevsw? Or did I get unlucky and pull sources > > > between commits? > > > > If you were reading the commit messages, you would have noticed that > phk said he mailed patches for vinum and i4b to the respective authors. > i4b has since been fixed (AFAIK) and vinum is waiting for Greg to stop > galavanting around China on his way to Usenix.... I doubt that he'll > be able to do anything for a few weeks. Just be patient. > I don't use vinum, but how do I turn it off in my config-file? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 22:41:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id F18F814E49 for ; Tue, 1 Jun 1999 22:41:39 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id PAA05818; Wed, 2 Jun 1999 15:59:03 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199906020559.PAA05818@cimlogic.com.au> Subject: Re: cdevsw changes broke world in vinum In-Reply-To: from Leif Neland at "Jun 2, 1999 7:27:39 am" To: leifn@neland.dk (Leif Neland) Date: Wed, 2 Jun 1999 15:59:03 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > On Wed, 2 Jun 1999, John Birrell wrote: > > If you were reading the commit messages, you would have noticed that > > phk said he mailed patches for vinum and i4b to the respective authors. > > i4b has since been fixed (AFAIK) and vinum is waiting for Greg to stop > > galavanting around China on his way to Usenix.... I doubt that he'll > > be able to do anything for a few weeks. Just be patient. > > > I don't use vinum, but how do I turn it off in my config-file? You should just edit the parent Makefile (sys/modules/Makefile) and remove vinum if that's where the build barfs. [ IMHO this is one situation where phk should just go ahead and make the edit. ] -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 22:42:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 805C114C82 for ; Tue, 1 Jun 1999 22:42:33 -0700 (PDT) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 10p3nI-00068A-00; Wed, 2 Jun 1999 01:42:28 -0400 To: John Birrell Cc: caa@midgard.dhs.org (Charles Anderson), sheldonh@uunet.co.za, current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: cdevsw changes broke world in vinum In-reply-to: Your message of "Wed, 02 Jun 1999 14:05:30 +1000." <199906020405.OAA05481@cimlogic.com.au> Date: Wed, 02 Jun 1999 01:42:24 -0400 Message-ID: <23569.928302144@noop.colo.erols.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell wrote in message ID <199906020405.OAA05481@cimlogic.com.au>: > If you were reading the commit messages, you would have noticed that > phk said he mailed patches for vinum and i4b to the respective authors. > i4b has since been fixed (AFAIK) and vinum is waiting for Greg to stop > galavanting around China on his way to Usenix.... I doubt that he'll > be able to do anything for a few weeks. Just be patient. If its on the order of weeks for this to get fixed, I think removing the vinum module from the build process is in order ... its breaking the snapshots by stopping make world/make release... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 22:44:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id D949414C82; Tue, 1 Jun 1999 22:44:36 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id QAA05850; Wed, 2 Jun 1999 16:03:24 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199906020603.QAA05850@cimlogic.com.au> Subject: Re: cdevsw changes broke world in vinum In-Reply-To: <23569.928302144@noop.colo.erols.net> from Gary Palmer at "Jun 2, 1999 1:42:24 am" To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Wed, 2 Jun 1999 16:03:24 +1000 (EST) Cc: jb@cimlogic.com.au, caa@midgard.dhs.org, sheldonh@uunet.co.za, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Palmer wrote: > John Birrell wrote in message ID > <199906020405.OAA05481@cimlogic.com.au>: > > If you were reading the commit messages, you would have noticed that > > phk said he mailed patches for vinum and i4b to the respective authors. > > i4b has since been fixed (AFAIK) and vinum is waiting for Greg to stop > > galavanting around China on his way to Usenix.... I doubt that he'll > > be able to do anything for a few weeks. Just be patient. > > If its on the order of weeks for this to get fixed, I think removing > the vinum module from the build process is in order ... its breaking > the snapshots by stopping make world/make release... I think it would be better to make phk's commits. That way vinum should keep working and be up-to-date for those people who would be hurt by using an incompatible module. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 23:17:42 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 B8FCD15179 for ; Tue, 1 Jun 1999 23:17:38 -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 QAA17171; Wed, 2 Jun 1999 16:17:36 +1000 Date: Wed, 2 Jun 1999 16:17:36 +1000 From: Bruce Evans Message-Id: <199906020617.QAA17171@godzilla.zeta.org.au> To: dfr@nlsystems.com, wollman@khavrinen.lcs.mit.edu Subject: Re: IRQ sharing with newbus Cc: bde@zeta.org.au, current@FreeBSD.ORG, newton@atdot.dotat.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I don't think the sio multiport stuff needs to use RF_SHAREABLE - the >> master device knows how to field interrupts for the slaves (at least thats >> how I understood it). > >But the sio non-multiport stuff should be able to use RF_TIMESHARE. -- >If I'm not using my serial port, I should be able to use my >infrared.... Preemptive timesharing would be hard to implement reasonably for irqs. A uniform timeslice would have to be 86 usec to work properly for unbuffered sio devices at 115200 bps. This is not reasonable, so the interrupt system would have to guess which device you are using and only switch irqs away from it every few [hundred] msec. This would work better for slower and output-mostly devices, mainly for printers. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 1 23:54: 2 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 4A45014D61 for ; Tue, 1 Jun 1999 23:53:58 -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 IAA24169; Wed, 2 Jun 1999 08:52:33 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Charles Anderson Cc: Sheldon Hearn , current@FreeBSD.ORG Subject: Re: cdevsw changes broke world in vinum In-reply-to: Your message of "Tue, 01 Jun 1999 23:29:02 EDT." <19990601232902.A17503@midgard.dhs.org> Date: Wed, 02 Jun 1999 08:52:32 +0200 Message-ID: <24167.928306352@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm waiting for Greg to review the patch I sent to him: Index: vinum.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinum.c,v retrieving revision 1.23 diff -u -r1.23 vinum.c --- vinum.c 1999/05/15 05:49:19 1.23 +++ vinum.c 1999/05/31 12:29:11 @@ -49,13 +49,26 @@ #endif #include -STATIC struct cdevsw vinum_cdevsw = -{ - vinumopen, vinumclose, physread, physwrite, - vinumioctl, nostop, nullreset, nodevtotty, - seltrue, nommap, vinumstrategy, "vinum", - NULL, -1, vinumdump, vinumsize, - D_DISK, 0, -1 +static struct cdevsw vinum_cdevsw = { + /* open */ vinumopen, + /* close */ vinumclose, + /* read */ physread, + /* write */ physwrite, + /* ioctl */ vinumioctl, + /* stop */ nostop, + /* reset */ noreset, + /* devtotty */ nodevtotty, + /* poll */ nopoll, + /* mmap */ nommap, + /* strategy */ vinumstrategy, + /* name */ "vinum", + /* parms */ noparms, + /* maj */ CDEV_MAJOR, + /* dump */ vinumdump, + /* psize */ vinumsize, + /* flags */ D_DISK, + /* maxio */ 0, + /* bmaj */ BDEV_MAJOR }; /* Called by main() during pseudo-device attachment. */ @@ -85,7 +98,7 @@ daemonq = NULL; /* initialize daemon's work queue */ dqend = NULL; - cdevsw_add_generic(BDEV_MAJOR, CDEV_MAJOR, &vinum_cdevsw); + cdevsw_add(&vinum_cdevsw); #ifdef DEVFS #error DEVFS not finished yet #endif @@ -236,7 +249,9 @@ } } #endif +#if 0 cdevsw[CDEV_MAJOR] = NULL; /* no cdevsw any more */ +#endif log(LOG_INFO, "vinum: unloaded\n"); /* tell the world */ return 0; default: -- 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 Wed Jun 2 0: 8:30 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 B36621529C for ; Wed, 2 Jun 1999 00:08:27 -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 IAA43830; Wed, 2 Jun 1999 08:08:44 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 2 Jun 1999 08:08:43 +0100 (BST) From: Doug Rabson To: "Matthew N. Dodd" Cc: Mark Newton , current@freebsd.org Subject: Re: IRQ sharing with newbus 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 Tue, 1 Jun 1999, Matthew N. Dodd wrote: > On Tue, 1 Jun 1999, Doug Rabson wrote: > > For EISA, it should be possible to add RF_SHAREABLE to the > > bus_alloc_resource call (assuming that EISA interrupts are shareable > > like pci interrupts). > > The observed behavior suggests that RF_SHAREABLE is not being honored. > > dpt99: DPT PM2022A/9X FW Rev. 07CK, 1 channel, 64 CCBs > dpt0: at slot 4 on eisa0 > dpt0: DPT PM2022A/9X FW Rev. 07CK, 1 channel, 64 CCBs > dpt99: DPT PM2022A/9X FW Rev. 005A, 1 channel, 64 CCBs > dpt1: at slot 5 on eisa0 > dpt1: No irq?! > device_probe_and_attach: dpt1 attach returned -1 > > (The 'dpt99' lines are an artifact of the mechanism I'm using to complete > the probe.) > > Now, since the resource ranges aren't printed anymore, you can't see that > both cards are using (set to use) the same IRQ. The EISA bus code needs a new maintainer (who could put back such things as resource reporting). Are you interested? You seem to be one of the few people who actively uses this bus. -- 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 Wed Jun 2 0:10:15 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 9B09814EC0; Wed, 2 Jun 1999 00:10:10 -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 IAA43837; Wed, 2 Jun 1999 08:10:28 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 2 Jun 1999 08:10:28 +0100 (BST) From: Doug Rabson To: Joachim Kuebart Cc: se@freebsd.org, osa@etrust.ru, dwhite@resnet.uoregon.edu, green@unixhelp.org, wghicks@bellsouth.net, van.woerkom@netcologne.de, hodeleri@seattleu.edu, obrien@NUXI.com, freebsd-current@freebsd.org, wghicks@wghicks.bellsouth.net.demon.co.uk Subject: Re: No sound (Ensoniq Audio PCI 1370) In-Reply-To: <9906012152.AA10689@turing.mathematik.uni-ulm.de> 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 Tue, 1 Jun 1999, Joachim Kuebart wrote: > Stefan Esser wrote: > > On 1999-05-27 22:12 +0400, oZZ!!! wrote: > > > > > > wmsound with my card too can't work correct. > > > SB 128 PCI its a PCI-device & (as i known) it must be detect as es0 + pcm1 > > > (not pcm0), because pcm0 reserved for ISA-device (right?). Kernel at > > > boot-time detect my SB 128 PCI as es0 + pcm0... > > > > What's going on ? > > > > I guess that after the PCI attach of es0/pcm0, the ISA probe tries to > > attach an ISA card as pcm0, too, and stomps over the values filled into > > the device structure for the PCI card ... > > That's right, and it's because the implementation is broken: the PCI driver > part in /sys/pci/es1370.c uses the name "es" instead of "pcm". I.e. if it > used "pcm", different unit numbers would get assigned to ISA and PCI > devices and no clashes would result. > > Sorry I didn't make this a PR before, but I'm working on the driver and > it's in no condition to be released. This was my fault, so here's the fix: There is no need for a PR. Cameron's driver already has the correct name for this driver. -- 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 Wed Jun 2 0:19:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (Postfix) with ESMTP id F32F5152D8; Wed, 2 Jun 1999 00:19:23 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.13) with ESMTP id TAA28861; Wed, 2 Jun 1999 19:19:21 +1200 (NZST) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.3/8.9.2) id TAA15634; Wed, 2 Jun 1999 19:19:11 +1200 (NZST) (envelope-from jabley) Date: Wed, 2 Jun 1999 19:19:11 +1200 From: Joe Abley To: Nate Williams Cc: Julian Elischer , Matthew Hunt , kip@lyris.com, Poul-Henning Kamp , current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990602191911.A15558@clear.co.nz> References: <19990601130331.A21176@wopr.caltech.edu> <199906012016.OAA15554@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906012016.OAA15554@mt.sri.com>; from Nate Williams on Tue, Jun 01, 1999 at 02:16:55PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 01, 1999 at 02:16:55PM -0600, Nate Williams wrote: > > this is less and less of a problem because > > if you lose your link on PPP > > you are liable to get a differetn IP address on your redial. > > Not true. Only if you're using a dynamic IP address setup. Most > business connections have a static connection, so they'll end up with > the same IP address everytime. I would take issue with that. All of the regional registries require extremely good justification for allocating static IP addresses to transient network connections. This might be something that older, established providers are able to do (since they were delegated way too many addresses in the good ol' days) but it isn't an option for (m)any ISPs younger than three or four years. When it comes down to it, there is very little justification for a static address. The one I most commonly hear is "so we can do SMTP mail delivery to the customer", but even that doesn't mandate use of static addressing -- we support SMTP mail delivery (we call it "mailbagging" for some reason) to dynamically-addressed dial-up clients, and it works just fine. Other times the reason is "so the customer can carry on downloading after the line dropped" to which the answer is "maintain your access servers properly and this won't happen". Anyway, this is off-topic. Back to your scheduled programming. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 0:54: 2 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 B327D1586E; Wed, 2 Jun 1999 00:54:00 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:a576egpuDezju3XPKXijmSqtDurE90HL@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id QAA30826; Wed, 2 Jun 1999 16:54:11 +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 QAA27753; Wed, 2 Jun 1999 16:58:03 +0900 (JST) Message-Id: <199906020758.QAA27753@zodiac.mech.utsunomiya-u.ac.jp> To: jlemon@freebsd.org Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: svr4 module broken after VM86 change Date: Wed, 02 Jun 1999 16:58:02 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The svr4 module is broken after the following change to svr4_machdep.c rev 1.5. ---------------------------------------------------------------------- revision 1.5 date: 1999/06/01 18:20:23; author: jlemon; state: Exp; lines: +0 -4 Unifdef VM86. Reviewed by: silence on on -current ---------------------------------------------------------------------- The problem is svr4_getcontext() and svr4_setcontext() now refers to tf_vm86_xx fields which are defined in struct trapframe_vm68 but not in p->p_md.md_regs (struct trapframe). int svr4_setcontext(p, uc) struct proc *p; struct svr4_ucontext *uc; { struct sigacts *psp = p->p_sigacts; register struct trapframe *tf; svr4_greg_t *r = uc->uc_mcontext.greg; struct svr4_sigaltstack *s = &uc->uc_stack; struct sigaltstack *sf = &psp->ps_sigstk; int mask; [...] if ((uc->uc_flags & SVR4_UC_CPU) == 0) return 0; tf = p->p_md.md_regs; /* * Restore register context. */ if (r[SVR4_X86_EFL] & PSL_VM) { tf->tf_vm86_gs = r[SVR4_X86_GS]; tf->tf_vm86_ffs = r[SVR4_X86_FS]; tf->tf_vm86_es = r[SVR4_X86_ES]; tf->tf_vm86_ds = r[SVR4_X86_DS]; set_vflags(p, r[SVR4_X86_EFL]); } else { [...] Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 3:45:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id A485B14C32 for ; Wed, 2 Jun 1999 03:45:49 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id GAA02357; Wed, 2 Jun 1999 06:45:35 -0400 (EDT) Date: Wed, 2 Jun 1999 06:45:35 -0400 (EDT) From: "Matthew N. Dodd" To: Doug Rabson Cc: current@freebsd.org Subject: Re: IRQ sharing with newbus 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, 2 Jun 1999, Doug Rabson wrote: > The EISA bus code needs a new maintainer (who could put back such > things as resource reporting). Are you interested? You seem to be one > of the few people who actively uses this bus. I'm still fairly far behind on the learning curve with respect to the new_bus code so I can't really promise anything. :/ -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 7:17:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id A263114D04; Wed, 2 Jun 1999 07:17:11 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id XAA17704; Wed, 2 Jun 1999 23:46:09 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199906021416.XAA17704@gizmo.internode.com.au> Subject: Re: svr4 module broken after VM86 change To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Wed, 2 Jun 1999 23:46:09 +0930 (CST) Cc: jlemon@FreeBSD.ORG, current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp In-Reply-To: <199906020758.QAA27753@zodiac.mech.utsunomiya-u.ac.jp> from "Kazutaka YOKOTA" at Jun 2, 99 04:58:02 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 Kazutaka YOKOTA wrote: > The svr4 module is broken after the following change to svr4_machdep.c > rev 1.5. > ---------------------------------------------------------------------- > revision 1.5 > date: 1999/06/01 18:20:23; author: jlemon; state: Exp; lines: +0 -4 > Unifdef VM86. > Reviewed by: silence on on -current > ---------------------------------------------------------------------- Ah, that would be a mistake: I haven't completed the VM86 stuff yet (it has been among the lower of my priorities). Sorry, I didn't see your mesage on -current asking about it. I'l back the change out, anyway. - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 7:25:34 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 2461E14D04; Wed, 2 Jun 1999 07:25:27 -0700 (PDT) (envelope-from shocking@bandicoot.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 WAA29990; Wed, 2 Jun 1999 22:24:28 +0800 (WST) Received: (from shocking@localhost) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) id WAA02267; Wed, 2 Jun 1999 22:25:22 +0800 (WST) Date: Wed, 2 Jun 1999 22:25:22 +0800 (WST) From: Stephen Hocking-Senior Programmer PGS Tensor Perth Message-Id: <199906021425.WAA02267@bandicoot.prth.tensor.pgs.com> To: current@freebsd.org, hackers@freebsd.org Subject: Finding out what function an interrupt is tied to.. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having some problems since when the newbus code went in, in that my sound card doesn't seem to be interrupting anymore (PAS16, Voxware drivers). So what I'd like to do is look at the kernel and see if an interrupt actually has a function associated with it, and if it's being masked out. Any ideas? Of course, this would have to happen just as I learnt to rip my music CD's into mp3s. Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 9: 3:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id EDC8914D92 for ; Wed, 2 Jun 1999 09:03:32 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id SAA30664 for ; Wed, 2 Jun 1999 18:03:29 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Wed, 2 Jun 1999 18:03:28 +0200 (CEST) From: Leif Neland To: freebsd-current@FreeBSD.ORG Subject: The official splash screen 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 Where can I find a nice splash-screen? I'd like to try getting a splash screen, but I'm not sure the image is bad, or I just have misconfigured it wrong. So I wonder if an 'official FreeBSD splash screen' exists. Or does somebody have any splash screen for download somewhere? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 9:13:22 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 47622152E6 for ; Wed, 2 Jun 1999 09:13:18 -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 CAA06534; Thu, 3 Jun 1999 02:13:16 +1000 Date: Thu, 3 Jun 1999 02:13:16 +1000 From: Bruce Evans Message-Id: <199906021613.CAA06534@godzilla.zeta.org.au> To: bde@zeta.org.au, semen@iclub.nsu.ru Subject: Re: How can i fail buf? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> This isn't solved. It was less serious before rev.1.196 of vfs_bio.c >> when B_ERROR buffers were discarded insead of re-dirtied in the above >> code fragment. See also PR 11697, and about 20 PRs reporting problems >> with i/o errors and EOF "errors" (ENOSPC/EINVAL) for (mis)using buffered >> devices (especially fd0). >> > >Why they have done so? B_ERROR have to mean unrecoverable >error, doesn't it? Or we need something like > >Writing to ... at ... failed. >(A)bort, (R)etry, (I)gnore? > >:-) Even that has some advantages over our current and previous handling :-(. >> I use the following variant of the patch in PR 11697: >> >> [patch skipped] >> > >Will it ever included in current? I'm waiting for the committer of vfs_bio.c rev.1.196 to fix it. >> This fixes the primary problem in all cases except the most interesting one: >> for real i/o errors. It doesn't touch the secondary problem that most >> VOP_FSYNC() routines don't try hard enough to write all dirty buffers in >> the MNT_WAIT case, so vinvalbuf() may panic. > >As i see, we need some B_FATAL flag, that will signal brelse to >do not redirty buf, for example to set when media in fd >was changed. Still not quite right. I debugged this with write protected floppies. The driver currently retries a lot and spews a message for each failure. The best handling is close to what is provided by Abort/Retry/Fail (don't do anything until the disk is changed...). >About F_SYNC: usually they do, they try very hard to free >dirty queue, look at msdosfs_vnops.c, and 'man VOP_FSYNC' >pseudocode. Pseudocode even loops infinitly if there is a >not writable buf. I overestimated the extent of this problem. It seems to be limited to ffs_fsync(), which gives up after a couple of passes. I think the fatal case is only reached for unmount(). 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 2 10:34:53 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 C054114C30; Wed, 2 Jun 1999 10:34:50 -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 TAA25583; Wed, 2 Jun 1999 19:34:42 +0200 (CEST) (envelope-from des) To: Cc: Julian Elischer , Nate Williams , Matthew Hunt , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: From: Dag-Erling Smorgrav Date: 02 Jun 1999 19:34:41 +0200 In-Reply-To: 's message of "Tue, 1 Jun 1999 13:30:37 -0700 (PDT)" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG writes: > Is it that long? I honestly don't think I have ever seen one stay up for a > week. Are you sure you did not mean 48 hours? I don't speak in jest. 49.7 days until an internal millisecond counter rolls around and crashes the machine. Microsoft have a patch out, but according to their web site, it's untested. I don't know what's worse; that Microsoft themselves can't keep Windows running for 50 days, or that they're incapable of manually bumping the counter to a value close to UINT_MAX and wait a few minutes for it to roll over. 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 Wed Jun 2 10:46:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from beach.silcom.com (beach.silcom.com [199.201.128.19]) by hub.freebsd.org (Postfix) with ESMTP id 3E29214FC2 for ; Wed, 2 Jun 1999 10:46:35 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Received: from smarter.than.nu (pm0-19.vpop1.avtel.net [207.71.237.19]) by beach.silcom.com (Postfix) with ESMTP id 2DFC54E0; Wed, 2 Jun 1999 10:46:30 -0700 (PDT) Date: Wed, 2 Jun 1999 10:46:30 -0700 (PDT) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: The official splash screen 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, 2 Jun 1999, Leif Neland wrote: > Where can I find a nice splash-screen? > > I'd like to try getting a splash screen, but I'm not sure the image is > bad, or I just have misconfigured it wrong. > > So I wonder if an 'official FreeBSD splash screen' exists. > > Or does somebody have any splash screen for download somewhere? In the future, questions like this should be directed to freebsd-questions, as it doesn't directly pertain to -current. The FreeBSD Advocacy site at http://advocacy.freebsd.org/ has a collection of splash screens. See http://advocacy.freebsd.org/ammunition/splash.html -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org daemon(n): 1. an attendant power or spirit : GENIUS 2. the cute little mascot of the FreeBSD operating system To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 10:47:52 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 3E83415108 for ; Wed, 2 Jun 1999 10:47:48 -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 TAA25618; Wed, 2 Jun 1999 19:47:36 +0200 (CEST) (envelope-from des) To: Nathan Dorfman Cc: John Polstra , dwhite@resnet.uoregon.edu, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? References: <199905280446.VAA06342@vashon.polstra.com> <19990601185035.A11288@rtfm.net> From: Dag-Erling Smorgrav Date: 02 Jun 1999 19:47:36 +0200 In-Reply-To: Nathan Dorfman's message of "Tue, 1 Jun 1999 18:50:35 -0400" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nathan Dorfman writes: > Certain shareware lose95 FTP servers don't know how to do passive mode. No need to go looking through Windows software; the unjustly popular ncftp is equally braindead. The ncftp man page makes for very interesting (and depressing) reading; it is quite obvious that the author has never read RFC959. 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 Wed Jun 2 11:40:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 3615614DDB for ; Wed, 2 Jun 1999 11:40:46 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA15836; Wed, 2 Jun 1999 19:44:16 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA04951; Wed, 2 Jun 1999 00:10:31 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199906012210.AAA04951@yedi.iaf.nl> Subject: Re: IRQ sharing with newbus In-Reply-To: from Doug Rabson at "Jun 1, 1999 10:48:14 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 2 Jun 1999 00:10:31 +0200 (CEST) Cc: winter@jurai.net, newton@atdot.dotat.org, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Doug Rabson wrote ... > On Tue, 1 Jun 1999, Matthew N. Dodd wrote: > > > On Tue, 1 Jun 1999, Mark Newton wrote: > > > So, guys -- What is the officially blessed way of sharing IRQs under > > > newbus? > > > > If you find out, let me know since the EISA code suffers the same problem > > (though the drivers do a bit better job detecting the condition, and just > > fail to attach instead of panicing.) > > For EISA, it should be possible to add RF_SHAREABLE to the > bus_alloc_resource call (assuming that EISA interrupts are shareable like > pci interrupts). IRRC (it's been years) EISA cards can, but don't have to, support shared interrupts. I think the SCU/ECU can set this based on what the .CFG file of the card tells it the hardware can do. I once designed a EISA 2 channel SCSI adapter but that was > 9 years ago. Bitrot.. | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 11:45:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 24EB414DDB for ; Wed, 2 Jun 1999 11:45:53 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id OAA09131; Wed, 2 Jun 1999 14:45:37 -0400 (EDT) Date: Wed, 2 Jun 1999 14:45:37 -0400 (EDT) From: "Matthew N. Dodd" To: Wilko Bulte Cc: Doug Rabson , newton@atdot.dotat.org, current@FreeBSD.ORG Subject: Re: IRQ sharing with newbus In-Reply-To: <199906012210.AAA04951@yedi.iaf.nl> 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, 2 Jun 1999, Wilko Bulte wrote: > > For EISA, it should be possible to add RF_SHAREABLE to the > > bus_alloc_resource call (assuming that EISA interrupts are shareable like > > pci interrupts). > > IRRC (it's been years) EISA cards can, but don't have to, support shared > interrupts. I think the SCU/ECU can set this based on what the .CFG > file of the card tells it the hardware can do. > > I once designed a EISA 2 channel SCSI adapter but that was > 9 years ago. > Bitrot.. The point that I continue to try to make is that the new_bus code isn't honoring the RF_SHAREABLE flag. I believe this issue to be outside of the EISA specific bits but have nothing more than idle speculation to back that up as it appears the ISA issue was caused by a different feature of the new_bus code. Most EISA devices can be set to used 'EDGE' or 'LEVEL' triggered IRQs. Most that allow this, only allow sharing with other cards of the same type. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 12:13:58 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 A284D1551D for ; Wed, 2 Jun 1999 12:13:44 -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 PAA24696; Wed, 2 Jun 1999 15:13:27 -0400 (EDT) (envelope-from wollman) Date: Wed, 2 Jun 1999 15:13:27 -0400 (EDT) From: Garrett Wollman Message-Id: <199906021913.PAA24696@khavrinen.lcs.mit.edu> To: Bruce Evans Cc: dfr@nlsystems.com, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG, newton@atdot.dotat.org Subject: Re: IRQ sharing with newbus In-Reply-To: <199906020617.QAA17171@godzilla.zeta.org.au> References: <199906020617.QAA17171@godzilla.zeta.org.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> But the sio non-multiport stuff should be able to use RF_TIMESHARE. -- >> If I'm not using my serial port, I should be able to use my >> infrared.... > Preemptive timesharing would be hard to implement reasonably for irqs. > A uniform timeslice would have to be 86 usec to work properly for > unbuffered sio devices at 115200 bps. You're talking intervals about six orders of magnitude smaller than I am. -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 Wed Jun 2 12:57:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from beach.silcom.com (beach.silcom.com [199.201.128.19]) by hub.freebsd.org (Postfix) with ESMTP id B81D514BE1 for ; Wed, 2 Jun 1999 12:57:50 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Received: from smarter.than.nu (pm0-19.vpop1.avtel.net [207.71.237.19]) by beach.silcom.com (Postfix) with ESMTP id CFA3273E for ; Wed, 2 Jun 1999 12:57:43 -0700 (PDT) Date: Wed, 2 Jun 1999 12:57:42 -0700 (PDT) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: freebsd-current@freebsd.org Subject: FDC_YE and newbus 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 FDC_YE is still marked as broken with newbus. What's the timetable on getting this fixed, and is there anything I can do to help out? (I've been looking for an excuse to learn kernel internals, anyway... ;) I'd like to upgrade my Libretto to -current, but having a nonfunctional floppy drive is kind of a pain. -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org daemon(n): 1. an attendant power or spirit : GENIUS 2. the cute little mascot of the FreeBSD operating system To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 13:58:32 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 792CE14F60; Wed, 2 Jun 1999 13:58:09 -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 VAA08673; Wed, 2 Jun 1999 21:58:11 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 2 Jun 1999 21:58:11 +0100 (BST) From: Doug Rabson To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@freebsd.org, hackers@freebsd.org Subject: Re: Finding out what function an interrupt is tied to.. In-Reply-To: <199906021425.WAA02267@bandicoot.prth.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 On Wed, 2 Jun 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > I'm having some problems since when the newbus code went in, in that > my sound card doesn't seem to be interrupting anymore (PAS16, Voxware > drivers). So what I'd like to do is look at the kernel and see > if an interrupt actually has a function associated with it, and if > it's being masked out. Any ideas? Of course, this would have to happen > just as I learnt to rip my music CD's into mp3s. I suggest that you start by putting print statements (or using the kernel debugger) to find out what is going on in nexus_setup_intr() (i386/i386/nexus.c). -- 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 Wed Jun 2 13:58:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from opi.flirtbox.ch (unknown [62.48.0.50]) by hub.freebsd.org (Postfix) with SMTP id 695B215967 for ; Wed, 2 Jun 1999 13:58:50 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 88485 invoked from network); 2 Jun 1999 20:58:48 -0000 Received: from unknown (HELO pipeline.ch) (195.134.128.41) by opi.flirtbox.ch with SMTP; 2 Jun 1999 20:58:48 -0000 Message-ID: <37559B01.23719902@pipeline.ch> Date: Wed, 02 Jun 1999 22:58:41 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Matthew Hunt Cc: David Schwartz , Julian Elischer , Poul-Henning Kamp , kip@lyris.com, Nate Williams , current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <19990601134232.A22685@wopr.caltech.edu> <000001beac71$af125a10$021d85d1@whenever.youwant.to> <19990601140146.A23081@wopr.caltech.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Hunt wrote: > > On Tue, Jun 01, 1999 at 01:59:48PM -0700, David Schwartz wrote: > > > I think he was suggesting that the apps close the connection if they > > receive no data from some amount of time. (Isn't this common sense?) > > No, I frequently keep telnet/ssh connections idle for long periods, > and have no particular desire for them to close on me. They don't close on you because keepalive would succeed. It would only drop your connection after the keepalive times out when you become unreachable by IP. -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 14: 3:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id A221B14F60 for ; Wed, 2 Jun 1999 14:03:12 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id XAA91040; Wed, 2 Jun 1999 23:03:05 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Wed, 2 Jun 1999 23:03:05 +0200 (CEST) From: Leif Neland To: Joe Abley Cc: current@FreeBSD.ORG Subject: SMTP to dynamic ip's In-Reply-To: <19990602191911.A15558@clear.co.nz> 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 > When it comes down to it, there is very little justification for a static > address. The one I most commonly hear is "so we can do SMTP mail delivery > to the customer", but even that doesn't mandate use of static addressing -- > we support SMTP mail delivery (we call it "mailbagging" for some reason) > to dynamically-addressed dial-up clients, and it works just fine. > Would you care to explain how? Very interested. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 14: 5:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id B51EE15434 for ; Wed, 2 Jun 1999 14:05:23 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id OAA47058; Wed, 2 Jun 1999 14:01:08 -0700 (PDT) (envelope-from mph) Date: Wed, 2 Jun 1999 14:01:08 -0700 From: Matthew Hunt To: Andre Oppermann Cc: David Schwartz , Julian Elischer , Poul-Henning Kamp , kip@lyris.com, Nate Williams , current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990602140108.A47013@wopr.caltech.edu> References: <19990601134232.A22685@wopr.caltech.edu> <000001beac71$af125a10$021d85d1@whenever.youwant.to> <19990601140146.A23081@wopr.caltech.edu> <37559B01.23719902@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <37559B01.23719902@pipeline.ch>; from Andre Oppermann on Wed, Jun 02, 1999 at 10:58:41PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 02, 1999 at 10:58:41PM +0200, Andre Oppermann wrote: > Matthew Hunt wrote: > > On Tue, Jun 01, 1999 at 01:59:48PM -0700, David Schwartz wrote: > > > > > I think he was suggesting that the apps close the connection if they > > > receive no data from some amount of time. (Isn't this common sense?) > > > > No, I frequently keep telnet/ssh connections idle for long periods, > > and have no particular desire for them to close on me. > > They don't close on you because keepalive would succeed. It would > only drop your connection after the keepalive times out when you become > unreachable by IP. That's how keepalives work. My understanding is that David Schwartz's comment referred to application idle timeouts, not keepalives. -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 14:17: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (Postfix) with ESMTP id EFC6714BEC for ; Wed, 2 Jun 1999 14:16:49 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.11) with ESMTP id JAA09710; Thu, 3 Jun 1999 09:16:47 +1200 (NZST) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.3/8.9.2) id JAA26244; Thu, 3 Jun 1999 09:16:42 +1200 (NZST) (envelope-from jabley) Date: Thu, 3 Jun 1999 09:16:42 +1200 From: Joe Abley To: Leif Neland Cc: current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: SMTP to dynamic ip's Message-ID: <19990603091642.E25988@clear.co.nz> References: <19990602191911.A15558@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Leif Neland on Wed, Jun 02, 1999 at 11:03:05PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 02, 1999 at 11:03:05PM +0200, Leif Neland wrote: > > When it comes down to it, there is very little justification for a static > > address. The one I most commonly hear is "so we can do SMTP mail delivery > > to the customer", but even that doesn't mandate use of static addressing -- > > we support SMTP mail delivery (we call it "mailbagging" for some reason) > > to dynamically-addressed dial-up clients, and it works just fine. > > Would you care to explain how? > > Very interested. Inbound mail to "mailbagging" customers is not queued normally by sendmail, but is delivered through a local-like mailer to a separate per-user queue directory. When users authenticate, radius uses a back-end RPC service to register users as connected from a particular IP address. This IP address is dynamically assigned. When we receive a stop record from radius (indicating that the user has disconnected) a similar RPC removes the record. Inserting this record triggers an SMTP delivery attempt after a few seconds' delay. The per-user queue directory (the "mailbag") is emptied as messages are sent to the connected user. A periodic job (every ten minutes, I think, to give people a chance to idle out their automatically-dialled connection) checks for connected mailbagging customers for whom a queue run is not in progress. For each of these users, the mailbag is delivered by SMTP to the registered, connected address. The main thing to be careful on all this is to do paranoid checking at every stage to try to ensure that the user hasn't disconnected and been replaced by someone else (who should not get their mail). Incidentally, ETRN is still accepted (some people like to do it) but it doesn't do anything. We rely on mail being delivered regularly enough for ETRN not to be necessary. Calling the RPCs is very cheap, and we have experienced no load issues with scaling this to "large" numbers of customers. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 2 20:40:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 6F27014ED8 for ; Wed, 2 Jun 1999 20:40:16 -0700 (PDT) (envelope-from mike@sentex.net) Received: from ospf-wat.sentex.net (ospf-wat.sentex.net [209.167.248.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id XAA13820 for ; Wed, 2 Jun 1999 23:40:14 -0400 (EDT) From: mike@sentex.net (Mike Tancsa) To: current@FreeBSD.ORG Subject: Re: SMTP to dynamic ip's Date: Thu, 03 Jun 1999 03:51:07 GMT Message-ID: <3755fb29.1035417701@mail.sentex.net> References: <19990602191911.A15558@clear.co.nz> In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2 Jun 1999 17:20:38 -0400, in sentex.lists.freebsd.current you wrote: >Inbound mail to "mailbagging" customers is not queued normally by sendmail, >but is delivered through a local-like mailer to a separate per-user >queue directory. > >When users authenticate, radius uses a back-end RPC service to register >users as connected from a particular IP address. This IP address is >dynamically assigned. When we receive a stop record from radius >(indicating that the user has disconnected) a similar RPC removes >the record. Do you make checks to see that the person does not login twice with the same account name ? Also, what happens if one user who has a big queue, gets killed mid transit, than another user comes on with the same IP. Do you have a facility for stopping the queue ? ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 3 0:56:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (Postfix) with ESMTP id 5A00F14E23 for ; Thu, 3 Jun 1999 00:56:40 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.12) with ESMTP id TAA00231; Thu, 3 Jun 1999 19:56:37 +1200 (NZST) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.3/8.9.2) id TAA34530; Thu, 3 Jun 1999 19:56:28 +1200 (NZST) (envelope-from jabley) Date: Thu, 3 Jun 1999 19:56:28 +1200 From: Joe Abley To: Mike Tancsa Cc: current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: SMTP to dynamic ip's Message-ID: <19990603195628.B34283@clear.co.nz> References: <19990602191911.A15558@clear.co.nz> <3755fb29.1035417701@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <3755fb29.1035417701@mail.sentex.net>; from Mike Tancsa on Thu, Jun 03, 1999 at 03:51:07AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jun 03, 1999 at 03:51:07AM +0000, Mike Tancsa wrote: > On 2 Jun 1999 17:20:38 -0400, in sentex.lists.freebsd.current you wrote: > > > [mailbagging] > > Do you make checks to see that the person does not login twice with the > same account name ? Yes. Simultaneous logins are prohibited -- instead, users get to create multiple userids on a single account, and those individual userids can each connect at the same time. > Also, what happens if one user who has a big queue, > gets killed mid transit, than another user comes on with the same IP. Do > you have a facility for stopping the queue ? We rely partially on TCP to sort this out for us (i.e. on the "guess the sequence number" game being hard to play), but also make checks during the queue run using the same RPC service to find out whether the user has gone away. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 3 3:51: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 4C6F81500A for ; Thu, 3 Jun 1999 03:50:43 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id LAA32666 for freebsd.org!current; Thu, 3 Jun 1999 11:50:35 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Thu, 3 Jun 1999 11:49:07 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 3 Jun 1999 11:49:06 +0000 To: current@freebsd.org From: Bob Bishop Subject: Panic on reboot Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, For a few weeks, I've been seeing a double fault panic on rebooting after building world followed by kernel. The panic hits right after "syncing disks... done". It doesn't seem to happen if the machine hasn't done a fair bit of work since last reboot, and it's happening on two separate machines (one is SMP). Any ideas? -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 3 6:38: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (as1-p29.tfs.net [139.146.210.29]) by hub.freebsd.org (Postfix) with ESMTP id 9EFB315272 for ; Thu, 3 Jun 1999 06:37:59 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id IAA00523 for freebsd-current@freebsd.org; Thu, 3 Jun 1999 08:37:57 -0500 (CDT) From: Jim Bryant Message-Id: <199906031337.IAA00523@argus.tfs.net> Subject: SMP on Tyan Thunder2 and Thunder100 motherboards To: freebsd-current@freebsd.org Date: Thu, 3 Jun 1999 08:37:56 -0500 (CDT) Reply-To: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (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 are there any known problems with the Tyan Thunder2 [1696DLUA] and Thunder100 [1836DLUA] motherboards? I am finishing up putting together the thunder-2 system with dual 333's, and am starting to obtain the parts for the Thunder100. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 3 6:52:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from wiretap.read.tasc.com (wiretap.read.tasc.com [147.81.246.176]) by hub.freebsd.org (Postfix) with ESMTP id 038A314EBA for ; Thu, 3 Jun 1999 06:52:55 -0700 (PDT) (envelope-from ira@wiretap.read.tasc.com) Received: (from ira@localhost) by wiretap.read.tasc.com (8.8.8/8.8.8) id JAA16288; Thu, 3 Jun 1999 09:56:14 -0400 (EDT) (envelope-from ira) To: jbryant@unix.tfs.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP on Tyan Thunder2 and Thunder100 motherboards References: <199906031337.IAA00523@argus.tfs.net> From: ilcooper@tasc.com (Ira L. Cooper) Date: 03 Jun 1999 09:56:14 -0400 In-Reply-To: Jim Bryant's message of "Thu, 3 Jun 1999 08:37:56 -0500 (CDT)" Message-ID: <86zp2h2xs1.fsf@wiretap.read.tasc.com> Lines: 6 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I run a -STABLE system on a S1836DLUAN, it seems to do just fine. If you need more info contact me. -Ira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 3 6:53:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from rem.club.gagarinclub.ru (unknown [212.16.0.202]) by hub.freebsd.org (Postfix) with ESMTP id 5FD4314DD5 for ; Thu, 3 Jun 1999 06:53:11 -0700 (PDT) (envelope-from firma@rem.club.gagarinclub.ru) Received: from localhost (firma@localhost) by rem.club.gagarinclub.ru (8.9.3/8.9.3) with ESMTP id RAA00816 for ; Thu, 3 Jun 1999 17:57:58 +0400 (MSD) Date: Thu, 3 Jun 1999 17:57:58 +0400 (MSD) From: REM Reply-To: REM To: current@freebsd.org Subject: Can't detect AWE32 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 Kernel settings: # Sound Blaster ------------- controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device awe0 at isa? port 0x620 device opl0 at isa? port 0x388 #For normal case use this line Messages log: Jun 2 18:16:05 rem /kernel: Copyright (c) 1992-1999 The FreeBSD Project. Jun 2 18:16:05 rem /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jun 2 18:16:05 rem /kernel: The Regents of the University of California. All rights reserved. Jun 2 18:16:05 rem /kernel: FreeBSD 4.0-CURRENT #0: Thu May 27 19:47:44 MSD 1999 [skip] Jun 2 18:16:06 rem /kernel: sb0 at port 0x220 irq 5 drq 1 on isa0 Jun 2 18:16:06 rem /kernel: snd0: Jun 2 18:16:06 rem /kernel: sbxvi0 at port 0xffffffff drq 5 on isa0 Jun 2 18:16:06 rem /kernel: isa_compat: didn't get ports for sbxvi Jun 2 18:16:06 rem /kernel: snd0: Jun 2 18:16:06 rem /kernel: sbmidi0 at port 0x330 on isa0 Jun 2 18:16:06 rem /kernel: snd0: Jun 2 18:16:06 rem /kernel: awe0 at port 0x620 on isa0 Jun 2 18:16:06 rem /kernel: SoundBlaster EMU8000 (RAM512k)> Where is bug? REM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 3 7:13:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id 6E783151C9 for ; Thu, 3 Jun 1999 07:13:37 -0700 (PDT) (envelope-from thomma@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id HAA16822; Thu, 3 Jun 1999 07:09:51 -0700 (PDT) Received: from fedex.engwest.baynetworks.com (fedex.engwest.baynetworks.com [134.177.110.46]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with SMTP id HAA05068; Thu, 3 Jun 1999 07:13:36 -0700 (PDT) Received: from carrera.engwest (carrera.engwest.baynetworks.com) by fedex.engwest.baynetworks.com (4.1/SMI-4.1) Received: from localhost by carrera.engwest (SMI-8.6/SMI-SVR4) id HAA23711; Thu, 3 Jun 1999 07:10:00 -0700 To: rb@gid.co.uk Cc: current@FreeBSD.ORG Subject: Re: Panic on reboot In-Reply-To: Your message of "Thu, 3 Jun 1999 11:49:06 +0000" References: X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990603071000E.thomma@baynetworks.com> Date: Thu, 03 Jun 1999 07:10:00 -0700 From: Tamiji Homma X-Dispatcher: imput version 971024 Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob, > For a few weeks, I've been seeing a double fault panic on rebooting after > building world followed by kernel. The panic hits right after "syncing > disks... done". It doesn't seem to happen if the machine hasn't done a fair > bit of work since last reboot, and it's happening on two separate machines > (one is SMP). Do you happen to have non-existing devices in kernel config file? I have been seeing the double fault panic on SMP system. It seemed to be related to non-existing device when I looked at it with debugger. When I got rid of unnecessary devices from config file, the panic went away. I didn't investigate which device was causing it, though. Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 3 7:15:35 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 7539D153A5 for ; Thu, 3 Jun 1999 07:15:31 -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 RAA18894; Thu, 3 Jun 1999 17:15:11 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id AC7E81F6F; Thu, 3 Jun 1999 17:15:28 +0300 (EEST) Date: Thu, 3 Jun 1999 17:15:28 +0300 From: Vallo Kallaste To: Jim Bryant Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP on Tyan Thunder2 and Thunder100 motherboards Message-ID: <19990603171528.B2575@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <199906031337.IAA00523@argus.tfs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199906031337.IAA00523@argus.tfs.net>; from Jim Bryant on Thu, Jun 03, 1999 at 08:37:56AM -0500 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jun 03, 1999 at 08:37:56AM -0500, Jim Bryant wrote: > > are there any known problems with the Tyan Thunder2 [1696DLUA] and > Thunder100 [1836DLUA] motherboards? The Thunder100 DLUAN I have works very well with two PII-400 and -current FreeBSD. For Thunder2 don't know. -- 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 Thu Jun 3 11:12:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 5AE7014CC4; Thu, 3 Jun 1999 11:12:28 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.2/8.9.2) id XAA85685; Wed, 2 Jun 1999 23:27:56 +0100 (BST) (envelope-from nik) Date: Wed, 2 Jun 1999 23:27:54 +0100 From: Nik Clayton To: Joe Abley Cc: Nate Williams , Julian Elischer , Matthew Hunt , kip@lyris.com, Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990602232753.A81106@catkin.nothing-going-on.org> Reply-To: nik@freebsd.org References: <19990601130331.A21176@wopr.caltech.edu> <199906012016.OAA15554@mt.sri.com> <19990602191911.A15558@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990602191911.A15558@clear.co.nz>; from Joe Abley on Wed, Jun 02, 1999 at 07:19:11PM +1200 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 02, 1999 at 07:19:11PM +1200, Joe Abley wrote: > I would take issue with that. All of the regional registries require > extremely good justification for allocating static IP addresses to > transient network connections. Demon (a big ISP in .uk) allocate static IP addresses for *.demon.co.uk). They have a number of class B's, and I believe that RIPE (European IP registry) are quite happy with Demon's very efficient use of this space. > Other times the reason is "so the customer can carry on downloading > after the line dropped" to which the answer is "maintain your access > servers properly and this won't happen". Noise on the line, house mates inadvertently picking up the 'phone, plain bad luck. . . > Anyway, this is off-topic. Back to your scheduled programming. Agreed, Reply-to: points back to me. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 3 16:20:21 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 CEE3C14EB3 for ; Thu, 3 Jun 1999 16:20:14 -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 TAA19792 for ; Thu, 3 Jun 1999 19:20:14 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA16677; Thu, 3 Jun 1999 19:19:43 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id TAA92819 for freebsd-current@freebsd.org; Thu, 3 Jun 1999 19:19:43 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199906032319.TAA92819@bb01f39.unx.sas.com> Subject: Double panic on reboot (4.0-19990527-SNAP) To: freebsd-current@freebsd.org Date: Thu, 3 Jun 1999 19:19:43 -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've installed 4.0-19990527-SNAP on some machines for testing. The system runs fine, but has some problems when trying to reboot. The system panics when starting to mount the file systems. It then prints out some information about the panic, and proceeds to panic a 2nd time and reboot. This happens so fast I cannot read the information. After the system has panic'd the 2nd time, the system reboots and fscks the file systems at which point everything comes up ok. I wonder if/how something is being/not being written to disk which causes the system to panic, and is fixed via the fsck. This happenned about 6 times today out of 20 reboots. I have rebuilt the kernel with debug and will attempt to replicate the problem with the current snap on the machine, and with todays/tonights snap on a 2nd machine. If anyone has any ideas about what might be going on here, I'd appreciate any pointers. I've included some dmesg output below. Thanks! John 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-19990527-SNAP #0: Mon Jan 10 15:16:54 EST 2000 root@bb01t02.unx.sas.com:/usr/src/sys/compile/BBKERN Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 264887824 Hz CPU: Pentium II (264.89-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping=3 Features=0x80f9ff real memory = 134217728 (131072K bytes) sio0: system console avail memory = 127418368 (124432K bytes) Preloaded elf kernel "kernel" at 0xc02ee000. Pentium Pro MTRR support enabled, default memory type is uncacheable ccd0-3: Concatenated disk drivers Probing for PnP devices: CSN 1 Vendor ID: CSC6835 [0x3568630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] 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 vga-pci0: at device 0.0 on pci1 isab0: at device 7.0 on pci0 ide_pci0: at device 7.1 on pci0 chip1: at device 7.3 on pci0 ti0: irq 11 at device 13.0 on pci0 ti0: Ethernet address: 00:60:cf:20:22:60 fxp0: irq 10 at device 14.0 on pci0 fxp0: Ethernet address 00:a0:c9:8b:09:7f xl0: <3Com 3c905-TX Fast Etherlink XL> irq 11 at device 17.0 on pci0 xl0: Ethernet address: 00:c0:4f:ac:72:7f xl0: autoneg not complete, no carrier (forcing half-duplex, 10Mbps) 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: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> 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 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port changing root device to wd0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 3 21:52:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 7F38314D9E for ; Thu, 3 Jun 1999 21:52:33 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40321>; Fri, 4 Jun 1999 14:36:22 +1000 Date: Fri, 4 Jun 1999 14:52:18 +1000 From: Peter Jeremy Subject: sysctl To: freebsd-current@FreeBSD.ORG Message-Id: <99Jun4.143622est.40321@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I notice that sysctl -d doesn't work, and I suspect it never did. Looking at the code, sbin/sysctl/sysctl.c uses MIB {0,5} to request the description of a variable, but the code in sys/kern/kern_sysctl.c only supports {0,0} through {0,4}. Additionally, the macro SYSCTL_OID doesn't reference the description string. I recall some months ago, there was a discussion about the description strings, but I don't think it went anywhere. My feeling is that the description strings should be put into an ELF segment which isn't loaded - sysctl(3) would return an offset into that segment and it would be up to the caller to extract the string from the relevent section of kern.bootfile. I know this is all relatively easy, but my system seems to be missing elf(5) :-), so I'm not sure of the details. kern_sysctl.c also states: * This interface is under work and consideration, and should probably * be killed with a big axe by the first person who can find the time. Is anyone actually working on this? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jun 3 22:48: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 11EFD151E8 for ; Thu, 3 Jun 1999 22:47:58 -0700 (PDT) (envelope-from adrian@freebsd.org) Received: (qmail 21250 invoked by uid 1008); 4 Jun 1999 05:47:54 -0000 Message-ID: <19990604054754.21248.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: Peter Jeremy Cc: freebsd-current@freebsd.org Subject: Re: sysctl In-reply-to: Your message of "Fri, 04 Jun 1999 14:52:18 +1000." <99Jun4.143622est.40321@border.alcanet.com.au> Date: Fri, 04 Jun 1999 13:47:53 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy writes: >I notice that sysctl -d doesn't work, and I suspect it never did. > >Looking at the code, sbin/sysctl/sysctl.c uses MIB {0,5} to request >the description of a variable, but the code in sys/kern/kern_sysctl.c >only supports {0,0} through {0,4}. Additionally, the macro SYSCTL_OID >doesn't reference the description string. > >I recall some months ago, there was a discussion about the description >strings, but I don't think it went anywhere. > >My feeling is that the description strings should be put into an ELF >segment which isn't loaded - sysctl(3) would return an offset into >that segment and it would be up to the caller to extract the string >from the relevent section of kern.bootfile. I know this is all >relatively easy, but my system seems to be missing elf(5) :-), so I'm >not sure of the details. > >kern_sysctl.c also states: > * This interface is under work and consideration, and should probably > * be killed with a big axe by the first person who can find the time. > >Is anyone actually working on this? No, not on the interface - I'm working on finishing up the descriptions of a whole heap of sysctl variables. A rather large patch was apparently commited a month or two ago with the beginnings of documenting sysctl variables, but I currently have a lack of time to finish this and consider perhaps attacking the sysctl interface (and a few things I want to fix beforehand..) There was talk of a script being written to walk the /usr/src/sys tree and generate a sysctl descriptions file. Is someone going to be nice enough to do this? :-) Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 0:45:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from gal.netlab.sk (gal.netlab.sk [195.168.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 2AE1C15038 for ; Fri, 4 Jun 1999 00:45:33 -0700 (PDT) (envelope-from tps@arc.netlab.sk) Received: from tps (nobody@qwyx.netlab.sk [195.168.0.2]) by gal.netlab.sk (8.9.3/8.9.3) with SMTP id JAA22469 for ; Fri, 4 Jun 1999 09:45:32 +0200 (CEST) From: "Tomas TPS Ulej" To: Subject: SOFTUPDATES? Date: Fri, 4 Jun 1999 09:45:31 +0200 Message-ID: <003a01beae5e$38ed7ec0$231da8c3@tps.tps.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I add "options SOFTUPDATES" and my kernel won't compile make depend => [snip] ort.c ../../libkern/random.c ../../libkern/rindex.c ../../libkern/scanc.c ../../libkern/skpc.c ../../libkern/strcat.c ../../libkern/strcmp.c ../../libkern/strcpy.c ../../libkern/strlen.c ../../libkern/strncmp.c ../../libkern/strncpy.c ../../libkern/udivdi3.c ../../libkern/umoddi3.c ../../pci/ide_pci.c ioconf.c param.c vnode_if.c config.c cc: ../../ufs/ffs/ffs_softdep.c: No such file or directory cvsup current ran before recompilation :( -- Tomas TPS Ulej System Administrator tps@internet.sk, tu36-ripe TELENOR Internet, NETLAB Network, Slovakia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 0:50:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from Wit401305.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id EF17C15038 for ; Fri, 4 Jun 1999 00:50:21 -0700 (PDT) (envelope-from daeron@Wit401305.student.utwente.nl) Received: from localhost (daeron@localhost) by Wit401305.student.utwente.nl (8.9.3/8.9.2) with ESMTP id JAA18847; Fri, 4 Jun 1999 09:50:18 +0200 (CEST) (envelope-from daeron@Wit401305.student.utwente.nl) Date: Fri, 4 Jun 1999 09:50:17 +0200 (CEST) From: Pascal Hofstee To: Tomas TPS Ulej Cc: current@FreeBSD.ORG Subject: Re: SOFTUPDATES? In-Reply-To: <003a01beae5e$38ed7ec0$231da8c3@tps.tps.sk> 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, 4 Jun 1999, Tomas TPS Ulej wrote: > I add "options SOFTUPDATES" and my kernel won't compile [snip] > cc: ../../ufs/ffs/ffs_softdep.c: No such file or directory cd /usr/src/sys/ufs/ffs ln -s /usr/src/contrib/sys/softupdates/ffs_softdep.c ffs_softdep.c ln -s /usr/src/contrib/sys/softupdates/softdep.h softdep.h then try to recompile your kernel ;-) -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 0:51:36 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 A9E0D15156 for ; Fri, 4 Jun 1999 00:51:34 -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 AAA58930; Fri, 4 Jun 1999 00:51:56 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Tomas TPS Ulej" Cc: current@FreeBSD.ORG Subject: Re: SOFTUPDATES? In-reply-to: Your message of "Fri, 04 Jun 1999 09:45:31 +0200." <003a01beae5e$38ed7ec0$231da8c3@tps.tps.sk> Date: Fri, 04 Jun 1999 00:51:56 -0700 Message-ID: <58926.928482716@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I add "options SOFTUPDATES" and my kernel won't compile Please don't simply turn options on without reading about them first - that is just foolish. Had you even bothered to look at LINT *before* you sent this message, you would have clearly seen the comment: # Soft updates is technique for improving file system speed and # making abrupt shutdown less risky. It is not enabled by default due # to copyright restraints on the code that implement it. # # Read ../../ufs/ffs/README.softupdates to learn what you need to # do to enable this. ../../../contrib/sys/softupdates/README gives # more details on how they actually work. # #options SOFTUPDATES By failing to do even this most basic of steps yourself, you only waste everyone's time with bogus failure reports. Don't. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 0:53: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 C3AE515038 for ; Fri, 4 Jun 1999 00:53:20 -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 10pomp-0001zb-00; Fri, 04 Jun 1999 09:53:07 +0200 From: Sheldon Hearn To: "Tomas TPS Ulej" Cc: current@FreeBSD.ORG Subject: Re: SOFTUPDATES? In-reply-to: Your message of "Fri, 04 Jun 1999 09:45:31 +0200." <003a01beae5e$38ed7ec0$231da8c3@tps.tps.sk> Date: Fri, 04 Jun 1999 09:53:06 +0200 Message-ID: <7662.928482786@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 04 Jun 1999 09:45:31 +0200, "Tomas TPS Ulej" wrote: > I add "options SOFTUPDATES" and my kernel won't compile Read the section in LINT that dscribes the SOFTUPDATES option. 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 4 0:55: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from gal.netlab.sk (gal.netlab.sk [195.168.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 1996D15038 for ; Fri, 4 Jun 1999 00:54:59 -0700 (PDT) (envelope-from tps@arc.netlab.sk) Received: from tps (nobody@qwyx.netlab.sk [195.168.0.2]) by gal.netlab.sk (8.9.3/8.9.3) with SMTP id JAA23072; Fri, 4 Jun 1999 09:54:55 +0200 (CEST) From: "Tomas TPS Ulej" To: "Jordan K. Hubbard" Cc: Subject: RE: SOFTUPDATES? Date: Fri, 4 Jun 1999 09:54:55 +0200 Message-ID: <003b01beae5f$88da8120$231da8c3@tps.tps.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 In-Reply-To: <58926.928482716@zippy.cdrom.com> Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I waste 2 nights with this and be sure I reed manual before :( Sorry after last review I found one missing symlink: ln -s /usr/src/contrib/sys/softupdates/softdep.h softdep.h but idea for checking comes from maillist :) So it was good idea send mail here I thing. Regardz -- Tomas TPS Ulej System Administrator tps@internet.sk, tu36-ripe TELENOR Internet, NETLAB Network, Slovakia > -----Original Message----- > From: Jordan K. Hubbard [mailto:jkh@zippy.cdrom.com] > Sent: Friday, June 04, 1999 9:52 AM > To: Tomas TPS Ulej > Cc: current@FreeBSD.ORG > Subject: Re: SOFTUPDATES? > By failing to do even this most basic of steps yourself, you only > waste everyone's time with bogus failure reports. Don't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 0:56:23 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 8AA0A153FD for ; Fri, 4 Jun 1999 00:56:22 -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 AAA58980; Fri, 4 Jun 1999 00:56:45 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Tomas TPS Ulej" Cc: current@freebsd.org Subject: Re: SOFTUPDATES? In-reply-to: Your message of "Fri, 04 Jun 1999 09:54:55 +0200." <003b01beae5f$88da8120$231da8c3@tps.tps.sk> Date: Fri, 04 Jun 1999 00:56:45 -0700 Message-ID: <58976.928483005@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > but idea for checking comes from maillist :) So it was good idea send mail > here I thing. No, it was not. :( If you don't know enough to check LINT when enabling new kernel features, you honestly should not be running -current and probably shouldn't even be changing your kernel. Sorry, but I'm getting more than a little fed up with people not reading the documentation. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 3:23:41 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 1817D153B0 for ; Fri, 4 Jun 1999 03:23:37 -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 UAA09018; Fri, 4 Jun 1999 20:23:32 +1000 (EST) To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: SOFTUPDATES? In-reply-to: Your message of "Fri, 04 Jun 1999 00:56:45 MST." <58976.928483005@zippy.cdrom.com> Date: Fri, 04 Jun 1999 20:23:32 +1000 Message-ID: <11983.928491812@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In all fairness, since the SOFTUPDATES comments in LINT point you to read the README, and this ask you to (paraphrased) "edit /etc/rc and disable update" I suggest that following the guidelines closely will prove challenging :-) Also, some commentary on the advisability of enabling softupdates on / for large single-partition configs would be useful: since it demands unmounted fs to apply tunefs to the device, this is "challenging" at first glance. cheers -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 4 4:12:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (mail.metropolitan.at [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 779051595A for ; Fri, 4 Jun 1999 04:12:09 -0700 (PDT) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Fri, 4 Jun 1999 13:14:58 +0200 Message-ID: <55586E7391ACD211B9730000C110027617963A@r-lmh-wi-100.corpnet.at> From: Ladavac Marino To: 'Garrett Wollman' , Bruce Evans Cc: dfr@nlsystems.com, current@FreeBSD.ORG, newton@atdot.dotat.org Subject: RE: IRQ sharing with newbus Date: Fri, 4 Jun 1999 13:09:41 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Garrett Wollman [SMTP:wollman@khavrinen.lcs.mit.edu] > Sent: Wednesday, June 02, 1999 9:13 PM > To: Bruce Evans > Cc: dfr@nlsystems.com; wollman@khavrinen.lcs.mit.edu; > current@FreeBSD.ORG; newton@atdot.dotat.org > Subject: Re: IRQ sharing with newbus > > < > said: > > >> But the sio non-multiport stuff should be able to use RF_TIMESHARE. > -- > >> If I'm not using my serial port, I should be able to use my > >> infrared.... > > > Preemptive timesharing would be hard to implement reasonably for > irqs. > > A uniform timeslice would have to be 86 usec to work properly for > > unbuffered sio devices at 115200 bps. > > You're talking intervals about six orders of magnitude smaller than I > am. [ML] If I understand you correctly, you want to resource track the IRQ's so if one device that uses one particular IRQ is active, another one cannot be activated? Example: I have a modem on sio1 and digicam on sio3 (both on IRQ3). I can either use my modem or download the photos, but not both at the same time. That would be nice. I don't known whether this is already supported as I don't have sio3 :) (I don't have sio1 either :) /Marino > -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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 5:54:21 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 7AFBD15259 for ; Fri, 4 Jun 1999 05:54:17 -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 OAA03931; Fri, 4 Jun 1999 14:54:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Cc: current@freebsd.org To: Roger Hardiman Subject: Re: cdevsw_add In-reply-to: Your message of "Fri, 04 Jun 1999 13:36:33 BST." <3757C851.446B@cs.strath.ac.uk> Date: Fri, 04 Jun 1999 14:54:15 +0200 Message-ID: <3929.928500855@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3757C851.446B@cs.strath.ac.uk>, Roger Hardiman writes: >Hi there, > >Just a quick question. >I'm about to fix the cdevsw_add(&bktr_cdevsw); >bug in the brooktree848.c driver. > >Bruce wondered if this should go into bktr_attatch rather >than bktr_probe? > >What do you think? >I think _attach is better. Otherwise we will call cdevsw_add() >even if you have the bktr driver in the kernel and have no bt848 >card fitted Today I don't much care where you put it. In the future we may want to think more about it though. The way I see it is that if the driver is there, it should check in at cdevsw[], which is why I generally put in *probe(). Of course if the hardware comes 'round later, attach will get called too. The next moves on my part are roughly: 1. Remove the difference between cdev/bdev dev_t's. I have a kernel running with this now, but there are bogons lurking which I have fumigated yes. 2. Enable doing "per dev_t" registration in the drivers. This will look pretty much like the devfs registration in there today, only more sane. After this the cdevsw_add() will only be kind of a "wildcard" registration method, for pseudo devices and such. After this point, a typical driver will probably do something like this: struct softc { int this; char that; bla bla bla }; /* some kind of probe/attach routine */ somefunction() { struct softc *sc; dev_t dt; dum di dah /* Aha, hardware! */ sc = MALLOC(...); bzero(sc, sizeof *sc); dt = mkdev( CDEV_MAJOR, /* Char major */ BDEV_MAJOR, /* Block major */ foomble_devices * 16, /* Minor */ &foomble_cdevsw, /* The cdevsw function vector */ "foomble%d", foomble_devices); /* printf like construction of name */ dt->driver1 = sc; dt->driver2 = foomble_devices; foomble_devices++; } foomble_open(dev_t dev, ...) { struct softc *sc = dev->driver1; int unit = dev->driver2; .... } -- 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 Fri Jun 4 6:21:56 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 DAB8D14D4F for ; Fri, 4 Jun 1999 06:21:53 -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 PAA04382; Fri, 4 Jun 1999 15:09:02 +0200 (MET DST) Date: Fri, 4 Jun 1999 15:09:01 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Poul-Henning Kamp Cc: Roger Hardiman , current@FreeBSD.ORG Subject: Re: cdevsw_add In-Reply-To: <3929.928500855@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 This should definitely go into attach IMNSHO. Probe: Check whether hardware is there (no side effects if possible). Attach:Get the device up and running and integrated into the kernel. With the priority probes this is even more distinct as a priority not equal to 0 means 'no side effects, just checking'. Nick. On Fri, 4 Jun 1999, Poul-Henning Kamp wrote: > In message <3757C851.446B@cs.strath.ac.uk>, Roger Hardiman writes: > >Hi there, > > > >Just a quick question. > >I'm about to fix the cdevsw_add(&bktr_cdevsw); > >bug in the brooktree848.c driver. > > > >Bruce wondered if this should go into bktr_attatch rather > >than bktr_probe? > > > >What do you think? > >I think _attach is better. Otherwise we will call cdevsw_add() > >even if you have the bktr driver in the kernel and have no bt848 > >card fitted > > Today I don't much care where you put it. In the future we may > want to think more about it though. > > The way I see it is that if the driver is there, it should check > in at cdevsw[], which is why I generally put in *probe(). > > Of course if the hardware comes 'round later, attach will get > called too. > > The next moves on my part are roughly: > > 1. Remove the difference between cdev/bdev dev_t's. I have a > kernel running with this now, but there are bogons lurking which > I have fumigated yes. > > 2. Enable doing "per dev_t" registration in the drivers. This will > look pretty much like the devfs registration in there today, only > more sane. After this the cdevsw_add() will only be kind of a > "wildcard" registration method, for pseudo devices and such. > > After this point, a typical driver will probably do something like this: > > struct softc { > int this; > char that; > bla > bla > bla > }; > > /* some kind of probe/attach routine */ > somefunction() > { > struct softc *sc; > dev_t dt; > > dum > di > dah > /* Aha, hardware! */ > sc = MALLOC(...); > bzero(sc, sizeof *sc); > dt = mkdev( > CDEV_MAJOR, /* Char major */ > BDEV_MAJOR, /* Block major */ > foomble_devices * 16, /* Minor */ > &foomble_cdevsw, /* The cdevsw function vector */ > "foomble%d", foomble_devices); /* printf like construction of name */ > dt->driver1 = sc; > dt->driver2 = foomble_devices; > foomble_devices++; > } > > foomble_open(dev_t dev, ...) > { > struct softc *sc = dev->driver1; > int unit = dev->driver2; > > .... > } > > -- > 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 > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 6:32:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id E891214D4F; Fri, 4 Jun 1999 06:32:10 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id PAA15589; Fri, 4 Jun 1999 15:32:03 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id D3A9AD21A; Fri, 4 Jun 1999 15:32:02 +0200 (CEST) Message-ID: <19990604153202.A17563@enst.fr> Date: Fri, 4 Jun 1999 15:32:02 +0200 From: Pierre Beyssac To: Matthew Dillon , Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <20883.928262460@critter.freebsd.dk> <199906012202.PAA84865@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199906012202.PAA84865@apollo.backplane.com>; from Matthew Dillon on Tue, Jun 01, 1999 at 03:02:47PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jun 01, 1999 at 03:02:47PM -0700, Matthew Dillon wrote: > I think keepalive's could easily be turned on by default. At BEST, one > of the first things I did 5 years ago was to turn them on permanently > on all of our machines. I'd like to disagree on the "by default" part, on the following assumptions: 1. If you turn on keepalive by default, you will have to increase the keepalive timeout value well over the current 2 hours (at least that's what most people suggest to alleviate the concerns about having keepalives on) 2. Changing this default value of 2 hours will affect ALL applications. Many of them (and their users) are more or less expecting a 2 hours value. For example that's the case for Telnet: probably you don't want to wait for ONE WEEK before a connection dies if you are currently using keepalives! I don't see what this fuss is all about. If for _some_ big servers there are many dead connections around after a while (*), why don't THEY use a sysctl at boot-time to change the default state, rather than impose on the rest of us a change that might not be as innocuous as it looks? (*) In theory, for a FTP server, most such connections will be when the user does a PUT, not a GET. In a GET, the server has data to push and will timeout anyway. In the case of the control connection, there's a application timeout in most ftpds who close the connection after some configurable amount of time. > This used to be a HUGE argument in the days where networks were less > reliable and dialup lines were scarse. It is not an argument now, > however. Go explain that to my cable provider :-). Keeping a long-lived connection through them is a real challenge; keepalives on would make my life even more difficult. > Whatever we do, we should not start messing around with the internals > of the kernel trying to 'fix' a non-problem. Keepalives work just dandy > as they are currently implemented, we do not have to mess with it beyond > possibly changing the default in rc.conf. "possibly", but *only* as a last resort if there are good reasons for it, IMHO. But I haven't seen any such reason yet. I also think that having at least a kernel-wide (or better, having it configurable on a per-socket basis), dynamically configurable keepalive would be a good thing. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 6:39: 4 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 5A952151D1; Fri, 4 Jun 1999 06:38:53 -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 10puAm-0003jT-00; Fri, 04 Jun 1999 15:38:12 +0200 From: Sheldon Hearn To: Pierre Beyssac Cc: Matthew Dillon , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 15:32:02 +0200." <19990604153202.A17563@enst.fr> Date: Fri, 04 Jun 1999 15:38:12 +0200 Message-ID: <14350.928503492@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, Since this isn't something everyone agrees on, how about adding a knob to the boot time config files? This would make the keep-alive issue more visible, and encourage folks to think about what they want. 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 4 6:42:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id B17E714E09 for ; Fri, 4 Jun 1999 06:42:18 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id OAA13807 Fri, 4 Jun 1999 14:28:17 +0100 (BST) Message-ID: <3757D472.167E@cs.strath.ac.uk> Date: Fri, 04 Jun 1999 14:28:18 +0100 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: Nick Hibma Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: cdevsw_add References: 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 wrote: > > cdevsw_add() > This should definitely go into attach IMNSHO. > > Probe: Check whether hardware is there (no side effects if possible). > Attach:Get the device up and running and integrated into the kernel. > > With the priority probes this is even more distinct as a priority not > equal to 0 means 'no side effects, just checking'. I've just fixed the bt848 driver (bktr) where the cdevsw_add() was accidentally added to the BSDI bktr_probe() and not the FreeBSD bktr_probe. Although Bruce and Nick said this really belongs, in the _attatch() function, I've kept it in the _probe() function for consistency with all the other drivers. Roger -- Roger Hardiman | Telepresence Research Group roger@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897 | Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557 | http://telepresence.dmem.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 6:55:14 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 1EF3614DB3 for ; Fri, 4 Jun 1999 06:55:11 -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 PAA05925; Fri, 4 Jun 1999 15:43:33 +0200 (MET DST) Date: Fri, 4 Jun 1999 15:43:32 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Roger Hardiman Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: cdevsw_add In-Reply-To: <3757D472.167E@cs.strath.ac.uk> 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 just fixed the bt848 driver (bktr) where the > cdevsw_add() was accidentally added to the BSDI bktr_probe() > and not the FreeBSD bktr_probe. > > Although Bruce and Nick said this really belongs, in the _attatch() > function, I've kept it in the _probe() function for consistency > with all the other drivers. Hm, I think this a bad choice. Which are 'all the other drivers'? The probe should really be as thin as possible to avoid unnecessary delays when probing in a kernel, like GENERIC, with a lot of device drivers compiled in. Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 7: 2:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 0670814DB3 for ; Fri, 4 Jun 1999 07:02:15 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id OAA14224 Fri, 4 Jun 1999 14:48:55 +0100 (BST) Message-ID: <3757D94A.2781@cs.strath.ac.uk> Date: Fri, 04 Jun 1999 14:48:58 +0100 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: Nick Hibma Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: cdevsw_add References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick > Hm, I think this a bad choice. Which are 'all the other drivers'? The > probe should really be as thin as possible to avoid unnecessary delays > when probing in a kernel, like GENERIC, with a lot of device drivers > compiled in. Well, in the PCI drivers, it is just the meteor, the brooktree848 and the Xilinx PGA driver (xrpu) In the /sys/i386/isa drivers, there were quite a few. Bye Roger -- Roger Hardiman | Telepresence Research Group roger@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897 | Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557 | http://telepresence.dmem.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 7:25:23 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 7D2DB14CA1 for ; Fri, 4 Jun 1999 07:25:18 -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 AAA00619; Sat, 5 Jun 1999 00:25:06 +1000 Date: Sat, 5 Jun 1999 00:25:06 +1000 From: Bruce Evans Message-Id: <199906041425.AAA00619@godzilla.zeta.org.au> To: nick.hibma@jrc.it, roger@cs.strath.ac.uk Subject: Re: cdevsw_add Cc: current@FreeBSD.ORG, phk@critter.freebsd.dk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Hm, I think this a bad choice. Which are 'all the other drivers'? The >> probe should really be as thin as possible to avoid unnecessary delays >> when probing in a kernel, like GENERIC, with a lot of device drivers >> compiled in. > >Well, in the PCI drivers, it is just the meteor, the brooktree848 >and the Xilinx PGA driver (xrpu) > >In the /sys/i386/isa drivers, there were quite a few. The isa drivers provide many bad examples. Most of them attached the devsw in a disgusting SYSINIT even if the device is disabled. I moved the devsw attach to the device attach function in some drivers that I worked on. This was necessary to support pcvt and syscons sharing a devsw entry. 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 4 8:17:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from bantu.cl.msu.edu (bantu.cl.msu.edu [35.8.3.18]) by hub.freebsd.org (Postfix) with ESMTP id 185B914C7F for ; Fri, 4 Jun 1999 08:17:16 -0700 (PDT) (envelope-from dervish@bantu.cl.msu.edu) Received: (from dervish@localhost) by bantu.cl.msu.edu (8.9.3/8.9.3) id LAA02168 for current@freebsd.org; Fri, 4 Jun 1999 11:13:16 -0400 (EDT) (envelope-from dervish) Date: Fri, 4 Jun 1999 11:13:16 -0400 From: bush doctor To: current@freebsd.org Subject: What is MTRR all about??? Message-ID: <19990604111316.A2066@bantu.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 35 95 F8 63 DA 5B 32 51 8F A9 AC 3C B4 74 F3 BA WWW-Home-Page: http://www.msu.edu/~ikhala Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After reading /sys/boot/README, I decided to sync up my -current boxes. I began playing around with loader, kld's and the splash screens. Now I have a few queries ... #;^) From dmesg on my -current box: Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #19: Thu Jun 3 13:54:15 EDT 1999 root@bantu.cl.msu.edu:/usr/src/sys/compile/BANTU Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 232672182 Hz CPU: Pentium Pro (232.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x616 Stepping=6 Features=0xf9ff real memory = 134217728 (131072K bytes) sio0: system console avail memory = 127488000 (124500K bytes) Preloaded elf kernel "kernel" at 0xc02ff000. Preloaded elf module "splash_bmp.ko" at 0xc02ff09c. Preloaded splash_image_data "/boot/logo-31.bmp" at 0xc02ff140. Preloaded elf module "cd9660.ko" at 0xc02ff190. Preloaded elf module "kernfs.ko" at 0xc02ff230. Preloaded elf module "msdos.ko" at 0xc02ff2d0. Preloaded elf module "procfs.ko" at 0xc02ff370. Pentium Pro MTRR support enabled, default memory type is uncacheable ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ What is MTRR? Using the web based cross referencing tool I came up with the following: 234 #define NPPROVMTRR 8 235 #define PPRO_VMTRRphysBase0 0x200 236 #define PPRO_VMTRRphysMask0 0x201 237 struct ppro_vmtrr { 238 u_int64_t base, mask; 239 }; 240 extern struct ppro_vmtrr PPro_vmtrr[NPPROVMTRR]; Could someone elaborate on the definitions? thanxs in advance ... #;^) -- So ya want ta here da roots? Dem that feels it knows it ... bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 9: 7: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 554CC14D34; Fri, 4 Jun 1999 09:07:01 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Date: Fri, 4 Jun 1999 17:06:54 +0100 From: David Malone To: Pierre Beyssac Cc: Matthew Dillon , Poul-Henning Kamp , current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990604170654.A8800@salmon.maths.tcd.ie> References: <20883.928262460@critter.freebsd.dk> <199906012202.PAA84865@apollo.backplane.com> <19990604153202.A17563@enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990604153202.A17563@enst.fr>; from Pierre Beyssac on Fri, Jun 04, 1999 at 03:32:02PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 04, 1999 at 03:32:02PM +0200, Pierre Beyssac wrote: > I don't see what this fuss is all about. If for _some_ big servers > there are many dead connections around after a while (*), why don't > THEY use a sysctl at boot-time to change the default state, rather > than impose on the rest of us a change that might not be as innocuous > as it looks? It might be nice to have two keepalive timeouts like Nate suggested. You'd have a short one, which applies if the application turns on keepalive or you have alwayskeepalive on. Then you'd have a long one, which applies to all connections regardless. Then: 1) To get the traditional behavior you set the long one to infinity and turn alwayskeepalive off. 2) To get the sort of behavior that phk is advocating, without upsetting the rest of us you leave alwayskeepalive off and then set the long one to 1 week. 3) For those of us with alwayskeepalive on, we'd get the traditional value of a few hours. Would this be a useful or a silly addition? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 9:14:10 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 53E0B14D34 for ; Fri, 4 Jun 1999 09:14:05 -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 SAA04588; Fri, 4 Jun 1999 18:12:28 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: David Malone Cc: Pierre Beyssac , Matthew Dillon , current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 17:06:54 BST." <19990604170654.A8800@salmon.maths.tcd.ie> Date: Fri, 04 Jun 1999 18:12:28 +0200 Message-ID: <4586.928512748@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990604170654.A8800@salmon.maths.tcd.ie>, David Malone writes: >It might be nice to have two keepalive timeouts like Nate suggested. >You'd have a short one, which applies if the application turns on >keepalive or you have alwayskeepalive on. Then you'd have a long >one, which applies to all connections regardless. Then: Then you might as well implement per socket adjustable keepalives. -- 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 Fri Jun 4 9:17:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A2FC914D34; Fri, 4 Jun 1999 09:17:24 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA07593; Fri, 4 Jun 1999 09:17:16 -0700 (PDT) (envelope-from dillon) Date: Fri, 4 Jun 1999 09:17:16 -0700 (PDT) From: Matthew Dillon Message-Id: <199906041617.JAA07593@apollo.backplane.com> To: Pierre Beyssac Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <20883.928262460@critter.freebsd.dk> <199906012202.PAA84865@apollo.backplane.com> <19990604153202.A17563@enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Tue, Jun 01, 1999 at 03:02:47PM -0700, Matthew Dillon wrote: :> I think keepalive's could easily be turned on by default. At BEST, one :> of the first things I did 5 years ago was to turn them on permanently :> on all of our machines. : :I'd like to disagree on the "by default" part, on the following :.. Pierre, let me make the suggestion to you that you try turning them on. I'll bet you dollars to donoughts that you will not notice the difference. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 9:22: 3 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 5020C15AB2; Fri, 4 Jun 1999 09:21:59 -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 MAA11067; Fri, 4 Jun 1999 12:21:43 -0400 (EDT) (envelope-from wollman) Date: Fri, 4 Jun 1999 12:21:43 -0400 (EDT) From: Garrett Wollman Message-Id: <199906041621.MAA11067@khavrinen.lcs.mit.edu> To: Matthew Dillon Cc: Pierre Beyssac , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <199906041617.JAA07593@apollo.backplane.com> References: <20883.928262460@critter.freebsd.dk> <199906012202.PAA84865@apollo.backplane.com> <19990604153202.A17563@enst.fr> <199906041617.JAA07593@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Pierre, let me make the suggestion to you that you try turning them > on. I'll bet you dollars to donoughts that you will not notice > the difference. Except when you happen to run into one of the inventors of TCP and he tells you what an dolt you appear to be... -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 9:22:30 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 2B73914D77 for ; Fri, 4 Jun 1999 09:22:22 -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 SAA10094; Fri, 4 Jun 1999 18:22:10 +0200 (CEST) (envelope-from des) To: George Michaelson Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: SOFTUPDATES? References: <11983.928491812@dstc.edu.au> From: Dag-Erling Smorgrav Date: 04 Jun 1999 18:22:09 +0200 In-Reply-To: George Michaelson's message of "Fri, 04 Jun 1999 20:23:32 +1000" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG George Michaelson writes: > Also, some commentary on the advisability of enabling softupdates on / > for large single-partition configs would be useful: since it demands > unmounted fs to apply tunefs to the device, this is "challenging" at > first glance. No. Boot in single-user mode, and type 'tunefs -n enable /' *before* mounting / read-write. Then proceed into multi-user mode. 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 Fri Jun 4 9:28:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id B254C14D77 for ; Fri, 4 Jun 1999 09:28:35 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie by salmon.maths.tcd.ie via local-salmon id ; 4 Jun 99 17:25:03 +0100 (BST) To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 18:12:28 +0200." <4586.928512748@critter.freebsd.dk> X-Request-Do: Date: Fri, 04 Jun 1999 17:25:02 +0100 From: David Malone Message-ID: <9906041725.aa11603@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <19990604170654.A8800@salmon.maths.tcd.ie>, David Malone writes: > > >It might be nice to have two keepalive timeouts like Nate suggested. > >You'd have a short one, which applies if the application turns on > >keepalive or you have alwayskeepalive on. Then you'd have a long > >one, which applies to all connections regardless. Then: > > Then you might as well implement per socket adjustable keepalives. While this is probably a good idea anyway, you still have the problem of setting these timeouts within applications for which you don't have source and for which the current default isn't useful. I guess this is the reason we have alwayskeepalive - if all applications set keepalive when they needed it we wouldn't have it at all. If you had per socket adjustable keepalives you'd also have to provide a tool which could set the keepalive timeout on a running process to get the sort of effect provided by alwayskeepalive. Having two timeouts would just be a compromise between these? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 9:36:10 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 788A314C14 for ; Fri, 4 Jun 1999 09:36:04 -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 CAA05571; Sat, 5 Jun 1999 02:05:52 +0930 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990604111316.A2066@bantu.cl.msu.edu> Date: Sat, 05 Jun 1999 02:05:51 +0930 (CST) From: "Daniel J. O'Connor" To: bush doctor Subject: RE: What is MTRR all about??? Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jun-99 bush doctor wrote: > Pentium Pro MTRR support enabled, default memory type is uncacheable > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > What is MTRR? Using the web based cross referencing tool I came up with MTRR's are a way to tell the processor how to cache regions of memory. Its commonly used to speed up video card access by disabling caching on the linear frame buffer, this makes writes to the card faster (around 0-30%). The penalty is that reading is slower, but since that doesn't happen very often the speed increase is good. Try man memcontrol - It doesn't yet work on SMP boxes though. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 9:46:16 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 9E2EB14E4B for ; Fri, 4 Jun 1999 09:46:13 -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 SAA04726; Fri, 4 Jun 1999 18:44:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Garrett Wollman Cc: Matthew Dillon , Pierre Beyssac , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 12:21:43 EDT." <199906041621.MAA11067@khavrinen.lcs.mit.edu> Date: Fri, 04 Jun 1999 18:44:26 +0200 Message-ID: <4724.928514666@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906041621.MAA11067@khavrinen.lcs.mit.edu>, Garrett Wollman writes: >< said: > >> Pierre, let me make the suggestion to you that you try turning them >> on. I'll bet you dollars to donoughts that you will not notice >> the difference. > >Except when you happen to run into one of the inventors of TCP and he >tells you what an dolt you appear to be... Just tell him, (and make sure he can hear the quotes): "32bit is enought for everthing" -- 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 Fri Jun 4 10: 4: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 3F497153FE for ; Fri, 4 Jun 1999 10:03:59 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA08090; Fri, 4 Jun 1999 10:03:55 -0700 (PDT) (envelope-from dillon) Date: Fri, 4 Jun 1999 10:03:55 -0700 (PDT) From: Matthew Dillon Message-Id: <199906041703.KAA08090@apollo.backplane.com> To: David Malone Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <9906041725.aa11603@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think people just like to argue sometimes. The reality is different. For all you people complaining: Just turn them on and I guarentee you will not even notice the difference, except you will stop getting ( even the occassional ) stale internet server process. That is what keepalives were designed to deal with. Keepalives are not supposed to be a network watchdog, they are simply supposed to be a catch-all. So having per-socket adjustment is kind of silly. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 10:40:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebase.sitaranetworks.com (unknown [199.103.150.64]) by hub.freebsd.org (Postfix) with ESMTP id 6E5301513D for ; Fri, 4 Jun 1999 10:40:50 -0700 (PDT) (envelope-from loverso@sitaranetworks.com) Received: from sitara.net (jamaica.sitaranetworks.com [199.103.141.147]) by freebase.sitaranetworks.com (8.8.8/8.8.8) with ESMTP id NAA12938 for ; Fri, 4 Jun 1999 13:40:50 -0400 (EDT) Message-ID: <37580F03.88EFB07A@sitara.net> Date: Fri, 04 Jun 1999 13:38:11 -0400 From: "John R. LoVerso" Organization: Sitara Networks, http://surf.to/loverso/ X-Mailer: Mozilla 4.6 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <4724.928514666@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "32bit is enought for everthing" Just mention the horrible header offset field. Lots of good TCP nits. Anyway, can't this argument be settled by separating the mechanism and policy. Adding a simple rc.conf tweak to enable them should be enough. But, consider going back to the discusssions leading up to the Host Requirements RFC (1122). The particular problem was that the original timeout value for keepalives was tiny (a few minutes). 1122 dictated the corrections for this. Here are the important points from section 4.2.3.6: 1. keepalives MUST default to off 2. the minimum timeout MUST be no less than two minutes 3. keep-alives SHOULD only be invoked in server applications This mostly says that always_keepalive should continue to default to off (but, perhaps, a easy hook in rc.conf should exist to turn them on). John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 10:56:47 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 1723E15A43 for ; Fri, 4 Jun 1999 10:56:44 -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 TAA04934; Fri, 4 Jun 1999 19:56:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "John R. LoVerso" Cc: current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 13:38:11 EDT." <37580F03.88EFB07A@sitara.net> Date: Fri, 04 Jun 1999 19:56:02 +0200 Message-ID: <4932.928518962@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <37580F03.88EFB07A@sitara.net>, "John R. LoVerso" writes: >But, consider going back to the discusssions leading up to the Host Requirements >RFC (1122). The particular problem was that the original timeout value for >keepalives was tiny (a few minutes). 1122 dictated the corrections for this. >Here are the important points from section 4.2.3.6: But RFC 1122 pretty much entirely predates the "modern internet user". While I fully supported the policy back then, I no longer do. I still think the right thing is: default to keepalives. set the timeout to a week. -- 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 Fri Jun 4 11:25:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from messenger.cacheflow.com (messenger.cacheflow.com [208.2.250.90]) by hub.freebsd.org (Postfix) with ESMTP id 6C93415432 for ; Fri, 4 Jun 1999 11:25:35 -0700 (PDT) (envelope-from krowett@rowett.org) Received: from rowettpc (208.2.250.25) by messenger.cacheflow.com (Worldmail 1.3.167); 4 Jun 1999 11:20:38 -0700 Message-Id: <4.2.0.56.19990604111235.00ae3ac0@rowett.org> X-Sender: krowett@freebsd.rowett.org (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta) Date: Fri, 04 Jun 1999 11:20:34 -0700 To: Matthew Dillon , David Malone From: "Kevin J. Rowett" Subject: Re: net.inet.tcp.always_keepalive on as default ? Cc: Poul-Henning Kamp , current@FreeBSD.ORG In-Reply-To: <199906041703.KAA08090@apollo.backplane.com> References: <9906041725.aa11603@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:03 AM 6/4/99 , Matthew Dillon wrote: > I think people just like to argue sometimes. The reality is different. > > For all you people complaining: Just turn them on and I guarentee > you will not even notice the difference, except you will stop getting > ( even the occassional ) stale internet server process. That is what > keepalives were designed to deal with. Keepalives are not supposed to > be a network watchdog, they are simply supposed to be a catch-all. This seems to be rather end-user, and short sighted. TCP and the underlying Internet has survived, and been able to scale (among other things), because of the work of many to balance end-user performance and overall network performance. All the TCP congestion avoidance algorithms and work done go towards managing a shared medium without a central point of control. If this work had not been done, then the Internet would not have grown as it did today. The central issue of keepalives is that, for one machine, they don't create a significant load. Multiplied by the number of machines on the Internet, it can become a problem. If freeBSD makes it a default, then other will adopt as well. Some less experienced and clueful implementors won't do as good a job with the overall TCP implementation, and we might see keepalives being sent every TCP timeout, for every connection, as a way to deal with a protocol error. :-) KR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 11:25:58 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 AF8B315B07 for ; Fri, 4 Jun 1999 11:25:53 -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 SAA08263; Fri, 4 Jun 1999 18:22:51 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19990604112019.009742a0@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 04 Jun 1999 11:20:19 -0700 To: Poul-Henning Kamp From: "Kurt D. Zeilenga" Subject: Re: net.inet.tcp.always_keepalive on as default ? Cc: current@FreeBSD.ORG In-Reply-To: <4932.928518962@critter.freebsd.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:56 PM 6/4/99 +0200, Poul-Henning Kamp wrote: >I still think the right thing is: > > default to keepalives. > set the timeout to a week. OpenLDAP slapd, like may other daemons, relies on timeouts being a reasonably short (a few hours) to deal with dead streams. Dead streams occur for a wide variety of reasons and erver applications need an effective mechanisms to deal with them. Changing the timeout to a week would render the SO_KEEPALIVE mechanism ineffective. Personally, I advocate using sysctl (in rc files) to set the default to on and leaving the kernel alone. Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 11:29:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 87D1C15432 for ; Fri, 4 Jun 1999 11:29:22 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id LAA29444; Fri, 4 Jun 1999 11:24:03 -0700 (PDT) Message-Id: <199906041824.LAA29444@implode.root.com> To: Poul-Henning Kamp Cc: "John R. LoVerso" , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 19:56:02 +0200." <4932.928518962@critter.freebsd.dk> From: David Greenman Reply-To: dg@root.com Date: Fri, 04 Jun 1999 11:24:02 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In message <37580F03.88EFB07A@sitara.net>, "John R. LoVerso" writes: > >>But, consider going back to the discusssions leading up to the Host Requirements >>RFC (1122). The particular problem was that the original timeout value for >>keepalives was tiny (a few minutes). 1122 dictated the corrections for this. >>Here are the important points from section 4.2.3.6: > >But RFC 1122 pretty much entirely predates the "modern internet user". While >I fully supported the policy back then, I no longer do. > >I still think the right thing is: > > default to keepalives. > set the timeout to a week. I don't support increasing the default timeout. That would cause problems for a lot of server systems that rely on the relatively short two hour default. The best I think you could do would be to increase it to something like 12-24 hours as a default, but even that might be problematical. Actually, I think we should leave it alone. I don't mind if people add an rc.conf variable, however. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 11:35:16 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 2274815AF0 for ; Fri, 4 Jun 1999 11:34: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 UAA05205; Fri, 4 Jun 1999 20:33:28 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Kevin J. Rowett" Cc: Matthew Dillon , David Malone , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 11:20:34 PDT." <4.2.0.56.19990604111235.00ae3ac0@rowett.org> Date: Fri, 04 Jun 1999 20:33:28 +0200 Message-ID: <5203.928521208@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4.2.0.56.19990604111235.00ae3ac0@rowett.org>, "Kevin J. Rowett" writes: >The central issue of keepalives is that, for one machine, they don't create >a significant load. Multiplied by the number of machines on the Internet, >it can become a problem. Reality home-work assignment to Kevin: If we send a total of 8 keep alive packets per week, for TCP connections that last that long. How many FreeBSD hackers with long lived telnet/ssh sessions does it take to generate as much trafic as one users IRC session ? >If freeBSD makes it a default, then other will adopt as well. Some less >experienced and clueful implementors won't do as good a job with the >overall TCP implementation, and we might see keepalives being sent >every TCP timeout, for every connection, as a way to deal with a protocol >error. :-) ... And the users, realizing this, will flock to FreeBSD and abandon all other inferior products. There we have it! The way to kill windows NT is to make tcp keepalives the default in FreeBSD, obviously, since NT is so bloddy unstable, Mickysoft will have to use much shorter timeouts and people will notice that NT soaks up all their bandwidth whereas FreeBSD doesn't. Great! And I guess we can corner Linux the same way, they have to reboot for every security fix, so they have to have shorter timeouts as well. -- 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 Fri Jun 4 12:29:13 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 198081520E for ; Fri, 4 Jun 1999 12:29:09 -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 VAA05421; Fri, 4 Jun 1999 21:27:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: dg@root.com Cc: "John R. LoVerso" , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 11:24:02 PDT." <199906041824.LAA29444@implode.root.com> Date: Fri, 04 Jun 1999 21:27:57 +0200 Message-ID: <5419.928524477@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906041824.LAA29444@implode.root.com>, David Greenman writes: >>In message <37580F03.88EFB07A@sitara.net>, "John R. LoVerso" writes: >> >>>But, consider going back to the discusssions leading up to the Host Requirements >>>RFC (1122). The particular problem was that the original timeout value for >>>keepalives was tiny (a few minutes). 1122 dictated the corrections for this. >>>Here are the important points from section 4.2.3.6: >> >>But RFC 1122 pretty much entirely predates the "modern internet user". While >>I fully supported the policy back then, I no longer do. >> >>I still think the right thing is: >> >> default to keepalives. >> set the timeout to a week. > > I don't support increasing the default timeout. That would cause problems >for a lot of server systems that rely on the relatively short two hour default. >The best I think you could do would be to increase it to something like >12-24 hours as a default, but even that might be problematical. > Actually, I think we should leave it alone. I don't mind if people add an >rc.conf variable, however. First of all, our current default is not two hours, but to kill after 4 hours idle followed by no response for 20min: net.inet.tcp.keepidle: 14400 net.inet.tcp.keepintvl: 150 So anyone depending on two hours are screwed already. How about this then: net.inet.tcp.always_keepidle: 86400 /* new variable */ net.inet.tcp.always_keepintvl: 64800 /* new variable */ net.inet.tcp.keepidle: 14400 net.inet.tcp.keepintvl: 150 net.inet.tcp.always_keepalive: 1 This will have all sockets have keepalives, but if the program specifically sets keepalives, it gets the shorter timeout. -- 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 Fri Jun 4 12:31:36 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 18D4E15438 for ; Fri, 4 Jun 1999 12:31:24 -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 VAA05446; Fri, 4 Jun 1999 21:31:15 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Jeremy Cc: freebsd-current@FreeBSD.ORG Subject: Re: sysctl In-reply-to: Your message of "Fri, 04 Jun 1999 14:52:18 +1000." <99Jun4.143622est.40321@border.alcanet.com.au> Date: Fri, 04 Jun 1999 21:31:15 +0200 Message-ID: <5444.928524675@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <99Jun4.143622est.40321@border.alcanet.com.au>, Peter Jeremy writes: >I notice that sysctl -d doesn't work, and I suspect it never did. right. My proposal: In the LINT kernel, the descriptions are compiled into a separate section and a small program converts this section into the sysctl(8) man page source (or maybe more correctly but less likely to be found: mib(8) man page source) -- 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 Fri Jun 4 12:31:51 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 7DC4215461 for ; Fri, 4 Jun 1999 12:31:30 -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 NAA20316; Fri, 4 Jun 1999 13:31:21 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA28493; Fri, 4 Jun 1999 13:31:20 -0600 Date: Fri, 4 Jun 1999 13:31:20 -0600 Message-Id: <199906041931.NAA28493@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: dg@root.com, "John R. LoVerso" , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <5419.928524477@critter.freebsd.dk> References: <199906041824.LAA29444@implode.root.com> <5419.928524477@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How about this then: > > net.inet.tcp.always_keepidle: 86400 /* new variable */ > net.inet.tcp.always_keepintvl: 64800 /* new variable */ > net.inet.tcp.keepidle: 14400 > net.inet.tcp.keepintvl: 150 > net.inet.tcp.always_keepalive: 1 > > This will have all sockets have keepalives, but if the program > specifically sets keepalives, it gets the shorter timeout. That's essentially what I proposed a couple days ago. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 12:41:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id C52FD1508F for ; Fri, 4 Jun 1999 12:41:45 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id PAA178656; Fri, 4 Jun 1999 15:36:24 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <199906041824.LAA29444@implode.root.com> References: Your message of "Fri, 04 Jun 1999 19:56:02 +0200." <4932.928518962@critter.freebsd.dk> Date: Fri, 4 Jun 1999 15:37:03 -0400 To: dg@root.com, Poul-Henning Kamp From: Garance A Drosihn Subject: Re: net.inet.tcp.always_keepalive on as default ? Cc: "John R. LoVerso" , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:24 AM -0700 6/4/99, David Greenman wrote: > someone else wrote: >> >> I still think the right thing is: >> default to keepalives. >> set the timeout to a week. > > I don't support increasing the default timeout. That would cause > problems for a lot of server systems that rely on the relatively > short two hour default. The best I think you could do would be to > increase it to something like 12-24 hours as a default, but even > that might be problematical. This may be a stupid question, but I haven't shied away from asking stupid questions before... Do we have to consider this as an "on/off" switch? Could we have it an "on/off/extended" switch? (or is the value stored as a bit somewhere, so that it can only be on or off?). What I'm thinking is that anything that explicitly asks for "on" would get the current 2-hour timeout, but that the "extended" setting would result in a 7-day timeout. We'd then set the system default to "extended" instead of either on or off. Or would this break things in subtle ways? --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 12:53:31 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 C96B915449 for ; Fri, 4 Jun 1999 12:53:29 -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 MAA50480; Fri, 4 Jun 1999 12:53:15 -0700 (PDT) Date: Fri, 4 Jun 1999 12:53:15 -0700 (PDT) From: Julian Elischer To: Bruce Evans Cc: nick.hibma@jrc.it, roger@cs.strath.ac.uk, current@FreeBSD.ORG, phk@critter.freebsd.dk Subject: Re: cdevsw_add In-Reply-To: <199906041425.AAA00619@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 Sat, 5 Jun 1999, Bruce Evans wrote: > > The isa drivers provide many bad examples. Most of them attached the > devsw in a disgusting SYSINIT even if the device is disabled. I moved > the devsw attach to the device attach function in some drivers that > I worked on. This was necessary to support pcvt and syscons sharing a > devsw entry. Firstly, the SYSINIT code was a stopgap. It will evolve with time.. The question is one of scope. THe devsw[] entry is added at the same time that the driver is activated in the kernel. This is neither at the first probe of a particular device, nor at the attach. Both of the latter cases an occur many times, both before (for probe) and after teh first hardware is found. This is why the SYSINIT was used.. The idea was that a loadable module would have an init() routine that is called when the module is loaded and linked in. This init() should also be called in an identical way during boot for a pre-loaded module. basically the case of a preloaded module (driver) is just a special case of the more general case of a loadable module. Drivers are just a special case of the more general case of loadable modules, so a driver should have all the features of a general module. e.g. an init() routine of some sort. It therefore makes sense that if a driver module has an init() routine that is called once before any other calls to the driver, tehn this is the obvious place to do things such as installing hooks for shutdown, or timeouts etc. and for installing itself into structures such as the devsw[] arrays. It is possible to SIMULATE this by making the first probe or attach calls do the work, but it seems to me rather artificial to do so because we have the ideal place to do the work anyhow. Remember that one of the long term aims that nearly all the FreeBSD developers have expressed at one time or another is to make FreeBSD almost completely dynamic. This means that nearly all components will eventually be loadable. Including boot drivers, which can be loaded and linked in by the boot loader. Making all drivers have the 'form' required, with an separate init() routine to be called at load time is therefore a positive thing. SYSINIT is just a way of making sure that these are called early, so that the driver need not know if it was loaded or was 'preloaded'. I therefore put it to the group that the right place to do devsw[] manipulation is neither in xxx-probe, or xxxx_attach, but in xxx_init(), which is only called once, and IS called at teh right time. It should also be noted that teh devsw[] extraction code should be run from the init() code when it is run with the 'shutdown' argument. (but only when the driver arees to allow itself to be unlinked). julian > > 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 4 12:55:46 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 67C51155AA for ; Fri, 4 Jun 1999 12:54:42 -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 UAA27132; Fri, 4 Jun 1999 20:54:53 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 4 Jun 1999 20:54:48 +0100 (BST) From: Doug Rabson To: Bruce Evans Cc: nick.hibma@jrc.it, roger@cs.strath.ac.uk, current@freebsd.org, phk@critter.freebsd.dk Subject: Re: cdevsw_add In-Reply-To: <199906041425.AAA00619@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 Sat, 5 Jun 1999, Bruce Evans wrote: > >> Hm, I think this a bad choice. Which are 'all the other drivers'? The > >> probe should really be as thin as possible to avoid unnecessary delays > >> when probing in a kernel, like GENERIC, with a lot of device drivers > >> compiled in. > > > >Well, in the PCI drivers, it is just the meteor, the brooktree848 > >and the Xilinx PGA driver (xrpu) > > > >In the /sys/i386/isa drivers, there were quite a few. > > The isa drivers provide many bad examples. Most of them attached the > devsw in a disgusting SYSINIT even if the device is disabled. I moved > the devsw attach to the device attach function in some drivers that > I worked on. This was necessary to support pcvt and syscons sharing a > devsw entry. If people feel that its wrong to put the cdev registration in a sysinit, please feel free to rip out the DEV_DRIVER_MODULE stuff and replace it with whatever the 'right thing' is. -- 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 Fri Jun 4 12:57:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from biggusdiskus.flyingfox.com (parker-T1-2-gw.sf3d.best.net [209.157.165.30]) by hub.freebsd.org (Postfix) with ESMTP id D2B3515032 for ; Fri, 4 Jun 1999 12:57:23 -0700 (PDT) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id OAA03028; Fri, 4 Jun 1999 14:01:36 -0700 (PDT) Date: Fri, 4 Jun 1999 14:01:36 -0700 (PDT) From: Jim Shankland Message-Id: <199906042101.OAA03028@biggusdiskus.flyingfox.com> To: dillon@apollo.backplane.com, dwmalone@maths.tcd.ie, krowett@rowett.org Subject: Re: net.inet.tcp.always_keepalive on as default ? Cc: current@FreeBSD.ORG, phk@critter.freebsd.dk In-Reply-To: <4.2.0.56.19990604111235.00ae3ac0@rowett.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kevin J. Rowett" writes: > The central issue of keepalives is that, for one machine, they don't > create a significant load. Multiplied by the number of machines on > the Internet, it can become a problem. No offense, but that is the most ludicrous assertion I've heard since Slobodan Milosevic claimed that all those bedraggled people streaming across the Albanian border were actually actors being paid $5.50 per day by NATO. Hint: If everybody turned on TCP keepalives, what percentage of the traffic on Internet backbones do you think would be keepalive packets? Jim Shankland NLynx Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 13: 7:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 84FA415B1E for ; Fri, 4 Jun 1999 13:07:39 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA09067; Fri, 4 Jun 1999 13:04:34 -0700 (PDT) (envelope-from dillon) Date: Fri, 4 Jun 1999 13:04:34 -0700 (PDT) From: Matthew Dillon Message-Id: <199906042004.NAA09067@apollo.backplane.com> To: Jim Shankland Cc: dwmalone@maths.tcd.ie, krowett@rowett.org, current@FreeBSD.ORG, phk@critter.freebsd.dk Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <199906042101.OAA03028@biggusdiskus.flyingfox.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hint: If everybody turned on TCP keepalives, what percentage of the :traffic on Internet backbones do you think would be keepalive :packets? : :Jim Shankland :NLynx Systems, Inc. Around 0.02%, using the stats from one of BEST's busier servers. That's percent. In otherwords, nobody would notice. You wouldn't notice, the backbones wouldn't notice... nobody would notice. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 13: 8:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 93AFB15595 for ; Fri, 4 Jun 1999 13:08:19 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA09127; Fri, 4 Jun 1999 13:08:18 -0700 (PDT) (envelope-from dillon) Date: Fri, 4 Jun 1999 13:08:18 -0700 (PDT) From: Matthew Dillon Message-Id: <199906042008.NAA09127@apollo.backplane.com> To: "Kevin J. Rowett" Cc: David Malone , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <9906041725.aa11603@salmon.maths.tcd.ie> <4.2.0.56.19990604111235.00ae3ac0@rowett.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :had not been done, then the Internet would not have grown as it did today. : :The central issue of keepalives is that, for one machine, they don't create :a significant load. Multiplied by the number of machines on the Internet, :it can become a problem. As I said. People are arguing about keepalives without knowing how they work. NO! I will repeat that: NO. There is NO significant bandwidth. Every single machine on the entire internet could turn on keepalives and you would not notice the difference. Someone give me a sledgehammer! No, make that two! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 13:19: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 83D7A14EEB for ; Fri, 4 Jun 1999 13:18:51 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id NAA29836; Fri, 4 Jun 1999 13:13:05 -0700 (PDT) Message-Id: <199906042013.NAA29836@implode.root.com> To: Poul-Henning Kamp Cc: "John R. LoVerso" , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 21:27:57 +0200." <5419.928524477@critter.freebsd.dk> From: David Greenman Reply-To: dg@root.com Date: Fri, 04 Jun 1999 13:13:05 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I don't support increasing the default timeout. That would cause problems >>for a lot of server systems that rely on the relatively short two hour default. >>The best I think you could do would be to increase it to something like >>12-24 hours as a default, but even that might be problematical. >> Actually, I think we should leave it alone. I don't mind if people add an >>rc.conf variable, however. > >First of all, our current default is not two hours, but to kill >after 4 hours idle followed by no response for 20min: > > net.inet.tcp.keepidle: 14400 > net.inet.tcp.keepintvl: 150 > >So anyone depending on two hours are screwed already. I believe the above numbers are in slowtimo ticks (500ms), so if you do the math, you come up with 2 hours. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 13:22:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5A7A414D47 for ; Fri, 4 Jun 1999 13:22:10 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA09260; Fri, 4 Jun 1999 13:18:34 -0700 (PDT) (envelope-from dillon) Date: Fri, 4 Jun 1999 13:18:34 -0700 (PDT) From: Matthew Dillon Message-Id: <199906042018.NAA09260@apollo.backplane.com> To: Jim Shankland , dwmalone@maths.tcd.ie, krowett@rowett.org, current@FreeBSD.ORG, phk@critter.freebsd.dk Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <199906042101.OAA03028@biggusdiskus.flyingfox.com> <199906042004.NAA09067@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : Around 0.02%, using the stats from one of BEST's busier servers. : That's percent. Oops, I wrong. It's actually less then that... the network counters overflowed. More around 0.001%. That's relative to outgoing traffic, not relative to network capacity. And, to be nice, I chose an administrative server instead of a web server. Web servers have even *lower* keepalive bandwidth utilization. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 13:22:21 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 7645214D47 for ; Fri, 4 Jun 1999 13:22:15 -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 WAA05665; Fri, 4 Jun 1999 22:21:05 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: dg@root.com Cc: "John R. LoVerso" , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 13:13:05 PDT." <199906042013.NAA29836@implode.root.com> Date: Fri, 04 Jun 1999 22:21:04 +0200 Message-ID: <5663.928527664@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906042013.NAA29836@implode.root.com>, David Greenman writes: >>> I don't support increasing the default timeout. That would cause problems >>>for a lot of server systems that rely on the relatively short two hour default. >>>The best I think you could do would be to increase it to something like >>>12-24 hours as a default, but even that might be problematical. >>> Actually, I think we should leave it alone. I don't mind if people add an >>>rc.conf variable, however. >> >>First of all, our current default is not two hours, but to kill >>after 4 hours idle followed by no response for 20min: >> >> net.inet.tcp.keepidle: 14400 >> net.inet.tcp.keepintvl: 150 >> >>So anyone depending on two hours are screwed already. > > I believe the above numbers are in slowtimo ticks (500ms), so if you do >the math, you come up with 2 hours. Oops, you're right. -- 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 Fri Jun 4 13:48:58 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 3EA6E14FA3 for ; Fri, 4 Jun 1999 13:48:51 -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 GAA25745; Sat, 5 Jun 1999 06:48:49 +1000 Date: Sat, 5 Jun 1999 06:48:49 +1000 From: Bruce Evans Message-Id: <199906042048.GAA25745@godzilla.zeta.org.au> To: bde@zeta.org.au, julian@whistle.com Subject: Re: cdevsw_add Cc: current@FreeBSD.ORG, nick.hibma@jrc.it, phk@critter.freebsd.dk, roger@cs.strath.ac.uk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The isa drivers provide many bad examples. Most of them attached the >> devsw in a disgusting SYSINIT even if the device is disabled. I moved >> the devsw attach to the device attach function in some drivers that >> I worked on. This was necessary to support pcvt and syscons sharing a >> devsw entry. > >Firstly, the SYSINIT code was a stopgap. It will evolve with time.. The Like most stogaps, it was there too long (3.5 years). It is mostly gone now. >... >I therefore put it to the group that the right place to do devsw[] >manipulation is neither in xxx-probe, or xxxx_attach, but in xxx_init(), >which is only called once, and IS called at teh right time. >It should also be noted that teh devsw[] extraction code should be run >from the init() code when it is run with the 'shutdown' argument. (but >only when the driver arees to allow itself to be unlinked). You're forgetting that devsw[] is another stopgap. The kernel should probably use something like devfs, where dev_t's only exist for devices that actually exist. xxx_init() is far too early to decide which hardware devices exist. 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 4 13:51:47 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 AECE615141 for ; Fri, 4 Jun 1999 13:51:41 -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 WAA05754; Fri, 4 Jun 1999 22:50:50 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: julian@whistle.com, current@FreeBSD.ORG, nick.hibma@jrc.it, roger@cs.strath.ac.uk Subject: Re: cdevsw_add In-reply-to: Your message of "Sat, 05 Jun 1999 06:48:49 +1000." <199906042048.GAA25745@godzilla.zeta.org.au> Date: Fri, 04 Jun 1999 22:50:50 +0200 Message-ID: <5752.928529450@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906042048.GAA25745@godzilla.zeta.org.au>, Bruce Evans writes: >You're forgetting that devsw[] is another stopgap. The kernel should >probably use something like devfs, where dev_t's only exist for devices >that actually exist. xxx_init() is far too early to decide which hardware >devices exist. Patience Bruce, I'm getting closer to that all the time... -- 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 Fri Jun 4 14:59:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from uop.cs.uop.edu (uop.cs.uop.edu [138.9.200.1]) by hub.freebsd.org (Postfix) with ESMTP id 531E315190; Fri, 4 Jun 1999 14:59:37 -0700 (PDT) (envelope-from bford@uop.cs.uop.edu) Received: (from bford@localhost) by uop.cs.uop.edu (8.8.8/8.8.8) id OAA17269; Fri, 4 Jun 1999 14:59:34 -0700 (PDT) From: Bret Ford Message-Id: <199906042159.OAA17269@uop.cs.uop.edu> Subject: Problems getting 3C597 up To: freebsd-questions@freebsd.org Date: Fri, 4 Jun 1999 14:59:31 -0700 (PDT) Cc: freebsd-current@freebsd.org X-Anon-Password: foobiebletch 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'm running 4.0 - current from the middle of May, approximately. I recently acquired an EISA 3COM network adapter that I'm now trying to install. Here's a snip from my dmesg output: vx0: <3Com 3C597-TX Network Adapter> at slot 5 on eisa0 vx0: No I/O space?! device_probe_and_attach: vx0 attach returned -1 So something is not working... :-( Anyone have any suggestions? I'm in a bind. I need a second ethernet card to get our new DSL line shared with our various household computers. Thanks very much for Any input! Bret Ford To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 15: 5:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 436A415190 for ; Fri, 4 Jun 1999 15:05:36 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.2/8.9.2) id UAA21499 for current@freebsd.org; Fri, 4 Jun 1999 20:38:21 +0100 (BST) (envelope-from nik) Date: Fri, 4 Jun 1999 20:38:19 +0100 From: Nik Clayton To: current@freebsd.org Subject: Review: Having aio.h include sys/time.h Message-ID: <19990604203818.A21265@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How do, -hackers was silent about this, so I'm resending it to -current. Any comments before I commit this (trivial) change? N == docs/11589 says that programs that include aio.h also need to include sys/time.h. I've had a chat with Terry Lambert, who wrote the aio_read.2 manual page, who says > And here is a section from the aio.h manual page (from the > Single UNIX Specification): > > Inclusion of the header may make visible symbols > defined in the headers , , > and . > > Basically, this means that the aio.h header is *defined* as > including sys/types.h (because of off_t and size_t), and is > defined as either including the other headers as well (bad) > or as forward declaring some types as opaque: > Since the Single UNIX Specification make no note of a header > other than aio.h, I'm afraid that the answer is that the aio.h > must include these headers, or directly define the respective > types itself. > > While I dislike promiscuous headers, I believe it is better to > be able to compile and run standards compliant UNIX code. So I want to apply the following very trivial patch; Index: aio.h =================================================================== RCS file: /home/ncvs/src/sys/sys/aio.h,v retrieving revision 1.9 diff -u -r1.9 aio.h --- aio.h 1999/01/17 22:33:08 1.9 +++ aio.h 1999/06/01 17:57:36 @@ -19,6 +19,7 @@ #ifndef _SYS_AIO_H_ #define _SYS_AIO_H_ +#include #include #include Any objections? I know nothing about the aio* stuff at all, which is why I'm checking first. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 15: 7: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 4C1CA15190; Fri, 4 Jun 1999 15:07:00 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id SAA21561; Fri, 4 Jun 1999 18:06:40 -0400 (EDT) Date: Fri, 4 Jun 1999 18:06:40 -0400 (EDT) From: "Matthew N. Dodd" To: Bret Ford Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Problems getting 3C597 up In-Reply-To: <199906042159.OAA17269@uop.cs.uop.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 On Fri, 4 Jun 1999, Bret Ford wrote: > vx0: <3Com 3C597-TX Network Adapter> at slot 5 on eisa0 > vx0: No I/O space?! > device_probe_and_attach: vx0 attach returned -1 This was fixed in version 1.45 of sys/i386/eisaconf.c -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 15:20:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id E5E3F15450 for ; Fri, 4 Jun 1999 15:20:46 -0700 (PDT) (envelope-from rgrimes@gndrsh.aac.dev.com) Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.9.3/8.9.3) id PAA22772; Fri, 4 Jun 1999 15:17:16 -0700 (PDT) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199906042217.PAA22772@gndrsh.aac.dev.com> Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <4932.928518962@critter.freebsd.dk> from Poul-Henning Kamp at "Jun 4, 1999 07:56:02 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Fri, 4 Jun 1999 22:17:16 +0000 (GMT) Cc: loverso@sitaranetworks.com (John R. LoVerso), 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 > In message <37580F03.88EFB07A@sitara.net>, "John R. LoVerso" writes: > > >But, consider going back to the discusssions leading up to the Host Requirements > >RFC (1122). The particular problem was that the original timeout value for > >keepalives was tiny (a few minutes). 1122 dictated the corrections for this. > >Here are the important points from section 4.2.3.6: > > But RFC 1122 pretty much entirely predates the "modern internet user". While > I fully supported the policy back then, I no longer do. > > I still think the right thing is: > > default to keepalives. > set the timeout to a week. Then lets go off a write RFCxxxx and get RFC1123 off the books, it's way over due for an overhaul anyway. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 15:25:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from messenger.cacheflow.com (messenger.cacheflow.com [208.2.250.90]) by hub.freebsd.org (Postfix) with ESMTP id 42FCD15469 for ; Fri, 4 Jun 1999 15:25:40 -0700 (PDT) (envelope-from krowett@rowett.org) Received: from rowettpc (208.2.250.25) by messenger.cacheflow.com (Worldmail 1.3.167) for current@FreeBSD.ORG; 4 Jun 1999 15:25:40 -0700 Message-Id: <4.2.0.56.19990604151956.00af7670@rowett.org> X-Sender: krowett@freebsd.rowett.org (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta) Date: Fri, 04 Jun 1999 15:25:37 -0700 To: current@FreeBSD.ORG From: "Kevin J. Rowett" Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <199906042008.NAA09127@apollo.backplane.com> References: <9906041725.aa11603@salmon.maths.tcd.ie> <4.2.0.56.19990604111235.00ae3ac0@rowett.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:08 PM 6/4/99 , Matthew Dillon wrote: >:had not been done, then the Internet would not have grown as it did today. >: >:The central issue of keepalives is that, for one machine, they don't create >:a significant load. Multiplied by the number of machines on the Internet, >:it can become a problem. > > As I said. People are arguing about keepalives without knowing how they > work. That's an excellent point! People with less correct implementations of TCP keepalives will use freeBSD's justification as their justification for turning on TCP keepalives by default. RFC1122 was written for a reason. Before we repeal it, we should consider why it was written in the first place. BTW, I'm in favor of making keepalives on by default. It will save me one line in the boot up sequence. KR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 15:33:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from peterw.yahoo.com (peterw.yahoo.com [206.132.89.237]) by hub.freebsd.org (Postfix) with ESMTP id 9A799154A0 for ; Fri, 4 Jun 1999 15:33:08 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost.yahoo.com [127.0.0.1]) by peterw.yahoo.com (8.9.3/8.9.2) with ESMTP id PAA02634; Fri, 4 Jun 1999 15:26:54 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <199906042226.PAA02634@peterw.yahoo.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nate Williams Cc: Poul-Henning Kamp , dg@root.com, "John R. LoVerso" , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 13:31:20 MDT." <199906041931.NAA28493@mt.sri.com> Date: Fri, 04 Jun 1999 15:26:54 -0700 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > > How about this then: > > > > net.inet.tcp.always_keepidle: 86400 /* new variable */ > > net.inet.tcp.always_keepintvl: 64800 /* new variable */ > > net.inet.tcp.keepidle: 14400 > > net.inet.tcp.keepintvl: 150 > > net.inet.tcp.always_keepalive: 1 > > > > This will have all sockets have keepalives, but if the program > > specifically sets keepalives, it gets the shorter timeout. > > That's essentially what I proposed a couple days ago. I think the always_keepintvl values above are pretty over the top.. We send a grand total of 8 keepalive packets every keepintvl slowtimeouts. In the SO_KEEPALIVE case, after nothing has been received for 2 hours, we send a keepalive packet every 75 seconds for a total of 8 times. If we still get nothing after 8 * 75 = 10 minutes, we drop the connection. The example above is a bit far out because after 12 hours we'd probe and retry every 540 minutes (9 hours) if there was no response for a total of 8 times - 8 * 9 = 72 hours. ie: it would take 3 days to clean a dead connection based on a lousy sample of 8 packets over those 3 days. I'd suggest always_keepidle = 86400 (12 hours) and always_keepinvl = 300 (20 minutes), and perhaps a new variable keepcnt and always_keepcnt so that we can retry more than 8 times if you have lossy links. IMHO, even the more aggressive existing keepalive values are so close to trivially small amounts of traffic, I'd much rather use the 14400/150 values for everything. I'd be really *really* suprised if long idle tcp sessions were statistically significant. I know I have telnet sessions that can have idle times of days, but compared to ftp/http/etc traffic it's a mere drop in the ocean. I can't think of any other common case of long idle open tcp sessions other than telnet and co. > Nate > Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 17:19: 3 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 5857014C3C; Fri, 4 Jun 1999 17:18:58 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id RAA85167; Fri, 4 Jun 1999 17:18:57 -0700 (PDT) From: Archie Cobbs Message-Id: <199906050018.RAA85167@bubba.whistle.com> Subject: subtle SIOCGIFCONF bug To: freebsd-current@freebsd.org Date: Fri, 4 Jun 1999 17:18:57 -0700 (PDT) Cc: freebsd-net@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 I've noticed that several programs have a subtle problem when scanning the list returned by the SIOCGIFCONF ioctl. The problem is that these programs do this computation to increment the pointer in the list: ifr = (struct ifreq *) ((char *) &ifr->ifr_addr + ifr->ifr_addr.sa_len); There are cases where some elements in the list (e.g., tunnel interfaces) have ifr->ifr_addr.sa_len set to a value LESS than sizeof(ifr->ifr_addr). This causes these programs to fail because the kernel always enforces a minimum length of (IFNAMSIZ + sizeof(ifr->ifr_addr)) for each entry in the list, even if ifr->ifr_addr.sa_len < sizeof(ifr->ifr_addr) (see net/if.c:ifconf()). First question: Should the kernel insure that ifr->ifr_addr.sa_len is always at least sizeof(ifr->ifr_addr), or should the user programs adjust their pointer increment algorithm? At first I assumed the latter answer (patches below) but now am not so sure. Second question: It doesn't appear the net/if.c:ifioctl() function is protected at all by splnet(), even though it is accessing all kinds of networking information. Is this a race condition? Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com Index: usr.sbin/arp/arp.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/arp/arp.c,v retrieving revision 1.15 diff -u -r1.15 arp.c --- arp.c 1999/03/10 10:11:43 1.15 +++ arp.c 1999/06/04 23:45:27 @@ -696,8 +696,8 @@ break; } nextif: - ifr = (struct ifreq *) - ((char *)&ifr->ifr_addr + ifr->ifr_addr.sa_len); + ifr = (struct ifreq *) ((char *)&ifr->ifr_addr + + MAX(ifr->ifr_addr.sa_len, sizeof(ifr->ifr_addr))); } if (ifr >= ifend) { @@ -725,8 +725,8 @@ printf("\n"); return dla->sdl_alen; } - ifr = (struct ifreq *) - ((char *)&ifr->ifr_addr + ifr->ifr_addr.sa_len); + ifr = (struct ifreq *) ((char *)&ifr->ifr_addr + + MAX(ifr->ifr_addr.sa_len, sizeof(ifr->ifr_addr))); } return 0; } Index: usr.sbin/pppd/sys-bsd.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/pppd/sys-bsd.c,v retrieving revision 1.15 diff -u -r1.15 sys-bsd.c --- sys-bsd.c 1998/06/21 04:47:21 1.15 +++ sys-bsd.c 1999/06/04 23:45:32 @@ -1378,8 +1378,9 @@ * address on the same subnet as `ipaddr'. */ ifend = (struct ifreq *) (ifc.ifc_buf + ifc.ifc_len); - for (ifr = ifc.ifc_req; ifr < ifend; ifr = (struct ifreq *) - ((char *)&ifr->ifr_addr + ifr->ifr_addr.sa_len)) { + for (ifr = ifc.ifc_req; ifr < ifend; + ifr = (struct ifreq *) ((char *)&ifr->ifr_addr + + MAX(ifr->ifr_addr.sa_len, sizeof(ifr->ifr_addr)))) { if (ifr->ifr_addr.sa_family == AF_INET) { ina = ((struct sockaddr_in *) &ifr->ifr_addr)->sin_addr.s_addr; strncpy(ifreq.ifr_name, ifr->ifr_name, sizeof(ifreq.ifr_name)); @@ -1425,7 +1426,8 @@ BCOPY(dla, hwaddr, dla->sdl_len); return 1; } - ifr = (struct ifreq *) ((char *)&ifr->ifr_addr + ifr->ifr_addr.sa_len); + ifr = (struct ifreq *) ((char *)&ifr->ifr_addr + + MAX(ifr->ifr_addr.sa_len, sizeof(ifr->ifr_addr))); } return 0; @@ -1468,8 +1470,9 @@ return mask; } ifend = (struct ifreq *) (ifc.ifc_buf + ifc.ifc_len); - for (ifr = ifc.ifc_req; ifr < ifend; ifr = (struct ifreq *) - ((char *)&ifr->ifr_addr + ifr->ifr_addr.sa_len)) { + for (ifr = ifc.ifc_req; ifr < ifend; + ifr = (struct ifreq *) ((char *)&ifr->ifr_addr + + MAX(ifr->ifr_addr.sa_len, sizeof(ifr->ifr_addr)))) { /* * Check the interface's internet address. */ Index: sbin/natd/natd.c =================================================================== RCS file: /home/ncvs/src/sbin/natd/natd.c,v retrieving revision 1.17 diff -u -r1.17 natd.c --- natd.c 1999/05/13 17:09:44 1.17 +++ natd.c 1999/06/04 23:54:32 @@ -762,6 +762,8 @@ } extra = ifPtr->ifr_addr.sa_len - sizeof (struct sockaddr); + if (extra < 0) + extra = 0; ifPtr++; ifPtr = (struct ifreq*) ((char*) ifPtr + extra); Index: sbin/route/route.c =================================================================== RCS file: /home/ncvs/src/sbin/route/route.c,v retrieving revision 1.30 diff -u -r1.30 route.c --- route.c 1999/06/01 13:14:07 1.30 +++ route.c 1999/06/04 23:54:36 @@ -794,7 +794,8 @@ (ifconf.ifc_buf + ifconf.ifc_len); ifr < ifr_end; ifr = (struct ifreq *) ((char *) &ifr->ifr_addr - + ifr->ifr_addr.sa_len)) { + + MAX(ifr->ifr_addr.sa_len, + sizeof(ifr->ifr_addr)))) { dl = (struct sockaddr_dl *)&ifr->ifr_addr; if (ifr->ifr_addr.sa_family == AF_LINK && (ifr->ifr_flags & IFF_POINTOPOINT) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 17:23:58 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 35CA115300; Fri, 4 Jun 1999 17:23:53 -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 UAA12466; Fri, 4 Jun 1999 20:23:48 -0400 (EDT) (envelope-from wollman) Date: Fri, 4 Jun 1999 20:23:48 -0400 (EDT) From: Garrett Wollman Message-Id: <199906050023.UAA12466@khavrinen.lcs.mit.edu> To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: subtle SIOCGIFCONF bug In-Reply-To: <199906050018.RAA85167@bubba.whistle.com> References: <199906050018.RAA85167@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Should the kernel insure that ifr->ifr_addr.sa_len is always at > least sizeof(ifr->ifr_addr), or should the user programs adjust > their pointer increment algorithm? At first I assumed the latter > answer (patches below) but now am not so sure. The user programs should not use SIOCGIFCONF. > It doesn't appear the net/if.c:ifioctl() function is protected > at all by splnet(), even though it is accessing all kinds of > networking information. Is this a race condition? No. ifioctl() should only be called from the ioctl syscall or other contexts where preemption is not an issue. -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 Fri Jun 4 17:30: 2 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 87EBE14DAA; Fri, 4 Jun 1999 17:29:59 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id RAA85352; Fri, 4 Jun 1999 17:29:27 -0700 (PDT) From: Archie Cobbs Message-Id: <199906050029.RAA85352@bubba.whistle.com> Subject: Re: subtle SIOCGIFCONF bug In-Reply-To: <199906050023.UAA12466@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jun 4, 99 08:23:48 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Fri, 4 Jun 1999 17:29:27 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG, freebsd-net@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 Garrett Wollman writes: > > Should the kernel insure that ifr->ifr_addr.sa_len is always at > > least sizeof(ifr->ifr_addr), or should the user programs adjust > > their pointer increment algorithm? At first I assumed the latter > > answer (patches below) but now am not so sure. > > The user programs should not use SIOCGIFCONF. I was hoping for a little more information than that. OK, imagine a world where you had no choice. THEN what would the answer be? In other words, I'd like to fix the problem but I don't have time to rewrite arp, natd, route, etc. -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 4 17:45:56 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 0F51E1516A; Fri, 4 Jun 1999 17:45:52 -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 UAA12551; Fri, 4 Jun 1999 20:45:50 -0400 (EDT) (envelope-from wollman) Date: Fri, 4 Jun 1999 20:45:50 -0400 (EDT) From: Garrett Wollman Message-Id: <199906050045.UAA12551@khavrinen.lcs.mit.edu> To: Archie Cobbs Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: subtle SIOCGIFCONF bug In-Reply-To: <199906050029.RAA85352@bubba.whistle.com> References: <199906050023.UAA12466@khavrinen.lcs.mit.edu> <199906050029.RAA85352@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> [I wrote:] >> The user programs should not use SIOCGIFCONF. > I was hoping for a little more information than that. > OK, imagine a world where you had no choice. THEN what would the answer be? 1) Implement sysctl net-route-iflist. 2) The user programs should not use SIOCGIFCONF. -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 Fri Jun 4 18:24:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C81D714E5A for ; Fri, 4 Jun 1999 18:24:26 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA10395; Fri, 4 Jun 1999 18:24:26 -0700 (PDT) (envelope-from dillon) Date: Fri, 4 Jun 1999 18:24:26 -0700 (PDT) From: Matthew Dillon Message-Id: <199906050124.SAA10395@apollo.backplane.com> To: Date:Fri@apollo.backplane.com, 04@FreeBSD.ORG, Jun@FreeBSD.ORG, 1999@FreeBSD.ORG, 15:25:37.-0700@apollo.backplane.com Cc: current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :At 01:08 PM 6/4/99 , Matthew Dillon wrote: :>:had not been done, then the Internet would not have grown as it did today. :>: :>:The central issue of keepalives is that, for one machine, they don't create :>:a significant load. Multiplied by the number of machines on the Internet, :>:it can become a problem. :> :> As I said. People are arguing about keepalives without knowing how they :> work. : :That's an excellent point! People with less correct implementations of TCP :keepalives will use freeBSD's justification as their justification for :turning on TCP keepalives by default. Umm... that is about as twisted a reasoning as I could imagine. I don't consider it a useful argument. The sky might be falling too, better not go outside! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 18:46:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 508E614D1F for ; Fri, 4 Jun 1999 18:46:44 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Fri, 4 Jun 1999 18:46:42 -0700 From: "David Schwartz" To: "Matthew Dillon" Cc: Subject: RE: net.inet.tcp.always_keepalive on as default ? Date: Fri, 4 Jun 1999 18:46:41 -0700 Message-ID: <000501beaef5$42938fe0$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <199906050124.SAA10395@apollo.backplane.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You know, I was going to buy a pickup truck, but I was afraid my neighbors would figure that if I bought a pickup truck, they should buy one too. And maybe a pickup truck isn't the right vehicle for them -- perhaps they didn't even know how to drive one safely. So I bought an Explorer instead. DS > :That's an excellent point! People with less correct > implementations of TCP > :keepalives will use freeBSD's justification as their justification for > :turning on TCP keepalives by default. > > Umm... that is about as twisted a reasoning as I could > imagine. I don't > consider it a useful argument. The sky might be falling too, > better not > go outside! > > -Matt > Matthew Dillon > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 19:19: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from niseko.junichi.org (niseko.junichi.org [210.238.191.91]) by hub.freebsd.org (Postfix) with ESMTP id 07C1914F29; Fri, 4 Jun 1999 19:18:46 -0700 (PDT) (envelope-from nao@junichi.org) Received: (from nao@localhost) by niseko.junichi.org (8.9.2+3.1W/3.7W-MQH-3.0) id LAA06955; Sat, 5 Jun 1999 11:18:24 +0900 (JST) To: Jordan Hubbard Cc: freebsd-mobile@freebsd.org, freebsd-current@freebsd.org Subject: Re: pccard boot.flp for *plain* 3.2-RELEASE References: <10710.928404651.1@peewee> From: Naoki Hamada Date: 05 Jun 1999 11:18:23 +0900 In-Reply-To: Jordan Hubbard's message of Thu, 03 Jun 1999 03:10:51 -0700 Message-ID: Lines: 20 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard writes: >1. Put pccardd on the mfsroot floppy and add a few things to > sysinstall (this may already be done by his patches, I haven't > had time to check) which enable its use during installation. > >2. Bring in message catalog and BIG5 support so that the standard > installer supports English, Japanese, Korean and Chinese by > default. Definitely cool! >3. Figure out why I couldn't get the isc-dhcp client to work > before 3.2's release (causing me to abandon the idea of adding > this feature for 3.2) and get DHCP support into 3.3. FreeBSD's isc-dhcp client was based on v2.0b1pl18 before May 8. It had some bugs, which were fatal in many environments. Now it is based on v2.0b1pl27, which works greatly. - nao To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 21:29:18 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 AC77F14DDF for ; Fri, 4 Jun 1999 21:29:13 -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 GAA54202; Sat, 5 Jun 1999 06:27:58 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Rodney W. Grimes" Cc: loverso@sitaranetworks.com (John R. LoVerso), current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 22:17:16 -0000." <199906042217.PAA22772@gndrsh.aac.dev.com> Date: Sat, 05 Jun 1999 06:27:58 +0200 Message-ID: <54200.928556878@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906042217.PAA22772@gndrsh.aac.dev.com>, "Rodney W. Grimes" writes: >> In message <37580F03.88EFB07A@sitara.net>, "John R. LoVerso" writes: >> >> >But, consider going back to the discusssions leading up to the Host Requirements >> >RFC (1122). The particular problem was that the original timeout value for >> >keepalives was tiny (a few minutes). 1122 dictated the corrections for this. >> >Here are the important points from section 4.2.3.6: >> >> But RFC 1122 pretty much entirely predates the "modern internet user". While >> I fully supported the policy back then, I no longer do. >> >> I still think the right thing is: >> >> default to keepalives. >> set the timeout to a week. > >Then lets go off a write RFCxxxx and get RFC1123 off the books, it's way >over due for an overhaul anyway. > I think it has been attempted, but gaining rough concensus on a document which declares N implementations "junk" is hard to get. -- 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 Fri Jun 4 22:35:50 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 98A6814DC9 for ; Fri, 4 Jun 1999 22:35:47 -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 HAA54653 for ; Sat, 5 Jun 1999 07:35:43 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 15:26:54 PDT." <199906042226.PAA02634@peterw.yahoo.com> Date: Sat, 05 Jun 1999 07:35:42 +0200 Message-ID: <54651.928560942@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, we've heard various opinions and I think we can conclude that: 1. Even with the current timeouts, there is no significant increase in network trafic, even with the market share FreeBSD has. 2. That server applications should have keepalives enabled. 3. That the few people, for whom it could become a problem if it is enabled by default, are prefectly capable of changing a variable in /etc/rc.conf. 4. It would be desirable to have per socket timeouts, but would require application changes which are unlikely to happen. 5. Changing the timeouts would potentially mean trouble for certain applications. QED: The following patch. If you don't like this, remember to change that variable in /etc/rc.conf in the future. Poul-Henning Index: rc.network =================================================================== RCS file: /home/ncvs/src/etc/rc.network,v retrieving revision 1.44 diff -u -r1.44 rc.network --- rc.network 1999/04/12 15:26:41 1.44 +++ rc.network 1999/06/05 05:25:51 @@ -180,6 +180,11 @@ sysctl -w net.inet.ip.accept_sourceroute=1 >/dev/null 2>&1 fi + if [ "X$tcp_keepalive" = X"YES" ]; then + echo -n ' TCP keepalive=YES' + sysctl -w net.inet.tcp.always_keepalive=1 >/dev/null 2>&1 + fi + if [ "X$ipxgateway_enable" = X"YES" ]; then echo -n ' IPX gateway=YES' sysctl -w net.ipx.ipx.ipxforwarding=1 >/dev/null 2>&1 Index: defaults/rc.conf =================================================================== RCS file: /home/ncvs/src/etc/defaults/rc.conf,v retrieving revision 1.9 diff -u -r1.9 rc.conf --- rc.conf 1999/05/16 09:19:44 1.9 +++ rc.conf 1999/06/05 05:26:26 @@ -41,6 +41,7 @@ natd_flags="" # Additional flags for natd. tcp_extensions="NO" # Set to Yes to turn on RFC1323 extensions. log_in_vain="NO" # Disallow bad connection logging (or YES). +tcp_keepalive="YES" # Kill dead TCP connections (or NO). network_interfaces="lo0" # List of network interfaces (lo0 is loopback). ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration. #ifconfig_lo0_alias0="inet 127.0.0.254 netmask 0xffffffff" # Sample alias entry. -- 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 Fri Jun 4 22:48:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 5751F14E8A for ; Fri, 4 Jun 1999 22:48:18 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Fri, 4 Jun 1999 22:48:17 -0700 From: "David Schwartz" To: "Poul-Henning Kamp" , Subject: RE: net.inet.tcp.always_keepalive on as default ? Date: Fri, 4 Jun 1999 22:48:17 -0700 Message-ID: <000101beaf17$026896f0$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal In-Reply-To: <54651.928560942@critter.freebsd.dk> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, we've heard various opinions and I think we can conclude that: > > 2. That server applications should have keepalives enabled. Well, I certainly don't agree with that. Many server applications (web servers, mail servers, etcetera) already have data timeouts, which makes keepalives redundant. In my opinion, in the vast majority of cases, data timeouts are more logical than keepalives. 'telnetd' being the most obvious exception. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jun 4 23: 5:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.gglb.com (unknown [202.103.237.142]) by hub.freebsd.org (Postfix) with ESMTP id 180B514F2A for ; Fri, 4 Jun 1999 23:04:59 -0700 (PDT) (envelope-from gglb@public.nn.gx.cn) Received: from mail pickup service by www.gglb.com with Microsoft SMTPSVC; Sat, 5 Jun 1999 13:50:49 +0800 From: To: Subject: ¹ã¸æÁª°î¸üпìµÝ Date: Sat, 5 Jun 1999 13:50:49 +0800 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Message-ID: <00ae24950050569WWW@www.gglb.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ¹ã¸æÁª°î¸üпìµÝ---------------- http://www.gglb.com 1¡¢È«ÐÂÍƳö¡°Ãâ·Ñ·ÖÀà¹ã¸æ¡°À¸Ä¿ http://ad.gglb.com Äú¿ÉÒÔÔÚ´Ë·¢²¼ÄúµÄÒ»ÇÐ ºÏ·¨ÐÅ¡£ 2¡¢È«¹úΨһµÄ¡°¹ã¸æÈËÁÄÌìÊÒ¡±³ÏÑûÄúÔÚ´ËÇãÌý¹ã¸æÈ˵ÄÐÄÉù£¬½»Á÷¹ã¸æÈ˵ľ­ Ñé¡£ 3¡¢ÔÚ¡°¹ã¸æÂÛ̳¡±£¬Äã¿ÉÒÔÕÒµ½Ò»¸ö¹ã¸æÈËÕæÕý½»Á÷µÄ¿Õ¼ä¡£ 4¡¢¹ã¸æÁª°îÊÕ¼ÁËÈ«¹úÖøÃûµÄ¹ã¸æ¹«Ë¾£¬¹ã¸æ²ÄÁϹ«Ë¾£¬¹ã¸æÉ豸¹«Ë¾£¬²éѯ¸ü¿ì ½Ý£¬Ôö¼Ó¸ü·½±ã¡£ 5¡¢×îйúÄÚ¹ã¸æÐÂÎÅ£¬¹ã¸æ¶¯Ì¬¡£ 6¡¢È«ÐÂÍƳöÆ»¹ûÈí¼þ´óÔùËÍ£º¶àÖÖÉè¼Æ¡¢Í¼ÐÎÈí¼þÎÞÏÞÖƸßËÙÏÂÔØ¡£ 7¡¢´óÁ¿¹úÄÚÓÅÐã¹ã¸æͼ¿â£¬½ÔΪȫ¹ú¸÷µØµÄ»§Íâ¹ã¸æͼÐΣ¬Ô­°æÔùËÍ£¬Ï£ÍûÄܸøÄú ´øÀ´Áé¸Ð¡£ À´¹ã¸æÁª°î£¬×öÁª°î¹ã¸æ............ http://www.gglb.com ¹ã¸æÁª°îÏÂÔØÕ¾µã£º................ http://download.gglb.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 4 23:49: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from peterw.yahoo.com (peterw.yahoo.com [206.132.89.237]) by hub.freebsd.org (Postfix) with ESMTP id E693B14FEF for ; Fri, 4 Jun 1999 23:49:05 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost.yahoo.com [127.0.0.1]) by peterw.yahoo.com (8.9.3/8.9.2) with ESMTP id XAA07499; Fri, 4 Jun 1999 23:44:16 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <199906050644.XAA07499@peterw.yahoo.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "David Schwartz" Cc: "Poul-Henning Kamp" , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 22:48:17 PDT." <000101beaf17$026896f0$021d85d1@whenever.youwant.to> Date: Fri, 04 Jun 1999 23:44:16 -0700 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David Schwartz" wrote: > > > Well, we've heard various opinions and I think we can conclude that: > > > > 2. That server applications should have keepalives enabled. > > Well, I certainly don't agree with that. Many server applications (web > servers, mail servers, etcetera) already have data timeouts, which makes > keepalives redundant. Huh? The keepalive option *is* a kind of data timeout.. It's a failsafe so that if nothing has been heard for a while then it explicitly does a check to see if the network connection is still valid. Of course a server app is free to implement it's own data timeouts, but it shouldn't have to reinvent what the kernel can do very well already and is very difficult to do in userland. There are several sorts of timeouts that server apps *may* want: - Some sort of upper bound on a session time, eg: a fingerd session may not last more than 1 hour, regardless of whether it's doing something. Something like a http server might put an upper limit of something like 24 hours - if it is too small and it will interfere with large downloads. - Some sort of idle timeout, eg: a smtp server may want to time out after 10 minutes of not recieving a command. - A way of detecting a stalled or rebooted client. This is what keepalive does. It lets you detect a lost connection before some other longer timeout (eg: 24 hours) kicks in. > In my opinion, in the vast majority of cases, data timeouts are more > logical than keepalives. 'telnetd' being the most obvious exception. Telnetd is the worst example. Just because I have not typed something for two hours is no indication that the session should be closed. Only the kernel can test the validity of the network link in this case. However, of I drop a link or reboot, then I do want it cleaned up in a timely fashion. > DS Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 1:39:57 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 BA24E14FD3; Sat, 5 Jun 1999 01:39:52 -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 KAA19203; Sat, 5 Jun 1999 10:39:41 +0200 (MET DST) Date: Sat, 5 Jun 1999 10:39:40 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Bruce Evans Cc: current@FreeBSD.ORG, FreeBSD hackers mailing list Subject: Re: cdevsw_add In-Reply-To: <199906042048.GAA25745@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 While on the topic: Who is working on devfs and why not? I'd like to know whether there is some interest in getting that work underway again. More than interested to help. > You're forgetting that devsw[] is another stopgap. The kernel should > probably use something like devfs, where dev_t's only exist for devices > that actually exist. xxx_init() is far too early to decide which hardware > devices exist. > > Bruce Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 2:28:39 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 755F514FBB; Sat, 5 Jun 1999 02:28:35 -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 LAA55282; Sat, 5 Jun 1999 11:27:22 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Nick Hibma Cc: Bruce Evans , current@FreeBSD.ORG, FreeBSD hackers mailing list Subject: Re: cdevsw_add In-reply-to: Your message of "Sat, 05 Jun 1999 10:39:40 +0200." Date: Sat, 05 Jun 1999 11:27:21 +0200 Message-ID: <55280.928574841@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Nick Hibma writes: > >While on the topic: Who is working on devfs and why not? > >I'd like to know whether there is some interest in getting that work >underway again. More than interested to help. I'm not currently working on devfs, but I am building the infrastructure it should be based on in the kernel. -- 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 5 3: 0:59 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 A67CB14E5A; Sat, 5 Jun 1999 03:00:56 -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 LAA19478; Sat, 5 Jun 1999 11:48:02 +0200 (MET DST) Date: Sat, 5 Jun 1999 11:48:02 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Poul-Henning Kamp Cc: Bruce Evans , current@FreeBSD.ORG, FreeBSD hackers mailing list Subject: Re: cdevsw_add In-Reply-To: <55280.928574841@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 > >While on the topic: Who is working on devfs and why not? > > I'm not currently working on devfs, but I am building the infrastructure > it should be based on in the kernel. Anymore information available on where you are with this? Cheers, Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 4:15: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [194.152.58.71]) by hub.freebsd.org (Postfix) with ESMTP id 0895A14C88 for ; Sat, 5 Jun 1999 04:15:05 -0700 (PDT) (envelope-from graichen@innominate.de) Received: from innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (8.9.3/8.9.3) with SMTP id NAA05188 for ; Sat, 5 Jun 1999 13:15:03 +0200 Received: (qmail 1973 invoked from network); 5 Jun 1999 11:15:26 -0000 Received: from presto.innominate.local (192.168.0.213) by lingo01.innominate.local with SMTP; 5 Jun 1999 11:15:26 -0000 Received: from localhost (graichen@localhost) by presto.innominate.local (8.9.3/8.9.3) with ESMTP id NAA05162 for ; Sat, 5 Jun 1999 13:12:21 +0200 (CEST) (envelope-from graichen@innominate.de) X-Authentication-Warning: presto.innominate.local: graichen owned process doing -bs Date: Sat, 5 Jun 1999 13:12:21 +0200 (CEST) From: Thomas Graichen X-Sender: graichen@presto.innominate.local To: freebsd-current@FreeBSD.org Subject: SOFTUPDATES stability 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 just would like to know about the state of SOFTUPDATES in -current and in -stable (are there differences ?) for heavy load situations ... is anyone here running SOFTUPDATES in such situations without trouble ? i'm asking because i noticed some problems then high load benchmarking a FreeBSD machine with SOFTUPDATES enabled (ended up in an unusable filesystem) - but i'm not shure if it was due to the SOFTUPDATES or maybe due to other kernel options or the ata driver (but i did not use busmastering ...) so it would be nice if someone could post here or mail me some experiences with SOFTUPDATES in "production" environments (yes i know its labeled alpha :-) t -- graichen@innominate.de innominate GmbH networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 4:41:21 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 37E1D14EEA; Sat, 5 Jun 1999 04:41: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 NAA55582; Sat, 5 Jun 1999 13:39:58 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Nick Hibma Cc: Bruce Evans , current@FreeBSD.ORG, FreeBSD hackers mailing list Subject: Re: cdevsw_add In-reply-to: Your message of "Sat, 05 Jun 1999 11:48:02 +0200." Date: Sat, 05 Jun 1999 13:39:58 +0200 Message-ID: <55580.928582798@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Nick Hibma writes: > > >While on the topic: Who is working on devfs and why not? > > > > I'm not currently working on devfs, but I am building the infrastructure > > it should be based on in the kernel. > >Anymore information available on where you are with this? I currently have a kernel running where dev_t is a pointer to a "struct dev" and where char and block devs are collapsed at the dev_t level. There are some bogons i need to fumigate, but I'm off to give a course in Stockholm much of this coming week, so don't expect any commits just now. (I may actually postpone/abandon this step for now, since some of the changes pulls rugs away which cover what looks to me like holes in the floor). Next is to integrate the dev_t anti-aliasing and vnode anti-aliasing code. When I have that bit down and done, the next step is for device drivers to register individual dev_t's rather than blanket cdevsw entries. The later ability will be retained for pseudo drivers and other (pseudo)magic. This registration will look pretty much like the current #ifdef'ed DEVFS stuff, and in addition it will allow the driver to hang two fields of the dev_t, typically a pointer to the struct softc and maybe a unit number or something. This will obsolete all of the magic minor -> {unit|softc} converters in our drivers and make the "NFOO" configuration obsolete. That is, as such the end of this little project, and where a future DEVFS could take off from. Basically all that is needed for a DEVFS to do, is to hook into the dev_t maintenance code and construct the directory tree. -- 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 5 6:37:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 9289A14CE1 for ; Sat, 5 Jun 1999 06:37:57 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id JAA12226; Sat, 5 Jun 1999 09:34:21 -0400 (EDT) From: Mikhail Teterin Message-Id: <199906051334.JAA12226@kot.ne.mediaone.net> Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <54651.928560942@critter.freebsd.dk> from Poul-Henning Kamp at "Jun 5, 1999 07:35:42 am" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sat, 5 Jun 1999 09:34:21 -0400 (EDT) Cc: current@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Sat, 5 Jun 1999 06:52:34 -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 PAA55848; Sat, 5 Jun 1999 15:51:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mikhail Teterin Cc: current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Sat, 05 Jun 1999 09:34:21 EDT." <199906051334.JAA12226@kot.ne.mediaone.net> Date: Sat, 05 Jun 1999 15:51:57 +0200 Message-ID: <55846.928590717@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906051334.JAA12226@kot.ne.mediaone.net>, Mikhail Teterin writes: >Poul-Henning Kamp once stated: > >=+tcp_keepalive="YES" # Kill dead TCP connections (or NO). > >Mmm, "probably dead TCP connections"? After 8 attempts at reaching other end: "Dead TCP connections". -- 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 5 7: 3:32 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 78FC114CE1 for ; Sat, 5 Jun 1999 07:03:30 -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 PAA20682; Sat, 5 Jun 1999 15:51:51 +0200 (MET DST) Date: Sat, 5 Jun 1999 15:51:50 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Mikhail Teterin Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <199906051334.JAA12226@kot.ne.mediaone.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 > =+tcp_keepalive="YES" # Kill dead TCP connections (or NO). > > Mmm, "probably dead TCP connections"? 'inactive or dead' ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 7:26: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 1C63914F42 for ; Sat, 5 Jun 1999 07:26:01 -0700 (PDT) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id KAA13259; Sat, 5 Jun 1999 10:21:43 -0400 (EDT) From: Mikhail Teterin Message-Id: <199906051421.KAA13259@kot.ne.mediaone.net> Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <55846.928590717@critter.freebsd.dk> from Poul-Henning Kamp at "Jun 5, 1999 03:51:57 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sat, 5 Jun 1999 10:21:43 -0400 (EDT) Cc: current@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"=+tcp_keepalive="YES" # Kill dead TCP connections (or NO). => =>Mmm, "probably dead TCP connections"? = =After 8 attempts at reaching other end: "Dead TCP connections". Perhaps "very probably dead"? I'm just trying to prevent questions in users' minds: "why the heck could anyone want to set this to NO"? If there is a hint some of this connections _may_ really be alive... May be a pointer to a more detailed explanation should go into the rc.conf's comment? -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 5 8:45:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from arc.netlab.sk (arc.netlab.sk [195.168.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 42F3F14F1D for ; Sat, 5 Jun 1999 08:45:23 -0700 (PDT) (envelope-from tps@arc.netlab.sk) Received: from tps (root@qwyx.netlab.sk [195.168.0.2]) by arc.netlab.sk (8.9.3/8.9.3) with SMTP id RAA08908 for ; Sat, 5 Jun 1999 17:44:02 +0200 (CEST) From: "Tomas TPS Ulej" To: Subject: natd problem Date: Sat, 5 Jun 1999 17:43:43 +0200 Message-ID: <011b01beaf6a$31a76240$231da8c3@tps.tps.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG r4 and natd: natd -dynamic -verbose -u -n ep1 In [UDP] [UDP] 192.168.1.5:127 -> 192.168.1.31:125 aliased to [UDP] 192.168.1.5:127 -> 192.168.1.31:125 In [UDP] [UDP] 192.168.1.5:127 -> 192.168.1.31:125 aliased to [UDP] 192.168.1.5:127 -> 192.168.1.31:125 In [UDP] [UDP] 192.168.1.6:138 -> 192.168.1.31:138 aliased to [UDP] 192.168.1.6:138 -> 192.168.1.31:138 In [UDP] [UDP] 192.168.1.5:127 -> 192.168.1.31:125 aliased to [UDP] 192.168.1.5:127 -> 192.168.1.31:125 ep1 has IP 195.168.78.186, ep0 192.168.1.1 -- Tomas TPS Ulej System Administrator tps@internet.sk, tu36-ripe TELENOR Internet, NETLAB Network, Slovakia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 11:11:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 735CC14E6A for ; Sat, 5 Jun 1999 11:11:50 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Sat, 5 Jun 1999 11:11:49 -0700 From: "David Schwartz" To: "Peter Wemm" Cc: "Poul-Henning Kamp" , Subject: RE: net.inet.tcp.always_keepalive on as default ? Date: Sat, 5 Jun 1999 11:11:48 -0700 Message-ID: <000201beaf7e$e0e8dd10$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal In-Reply-To: <199906050644.XAA07499@peterw.yahoo.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "David Schwartz" wrote: > > > > > Well, we've heard various opinions and I think we can conclude that: > > > > > > 2. That server applications should have keepalives enabled. > > > > Well, I certainly don't agree with that. Many server > applications (web > > servers, mail servers, etcetera) already have data timeouts, which makes > > keepalives redundant. > > Huh? The keepalive option *is* a kind of data timeout.. It's a failsafe > so that if nothing has been heard for a while then it explicitly does > a check to see if the network connection is still valid. Of > course a server > app is free to implement it's own data timeouts, but it shouldn't have > to reinvent what the kernel can do very well already and is very difficult > to do in userland. It's trivial to do in userland, just wrap your read in a select. If the select times out, bail. In many cases, the one-size-fits-all approach of keepalives doesn't fit. Why should someone be allowed to stay connected to my web server for _two_hours_ without sending one byte of data? > There are several sorts of timeouts that server apps *may* want: > - Some sort of upper bound on a session time, eg: a fingerd > session may not > last more than 1 hour, regardless of whether it's doing > something. Something > like a http server might put an upper limit of something like 24 > hours - if it > is too small and it will interfere with large downloads. Most web servers implement two different time outs. One is a 'request' timeout that typically is in the 2 to 5 minute range. Another is an output timeout that limits how long a connection can go without receiving at least a certain amount of data. Hard session limits are generally not useful -- after all, someone might put a 600Mb file up there and someone might want to retrieve it over a 28.8Kbps connection. Keepalives do not eliminate the need for _either_ timeout. Two hours is too long to wait for a request. Since the TCP connection may work even though the remote end's userland program is not receiving any data, the send timeout is still needed as well. There is no logical reason for a well-designed web server to enable keepalives. Of course, they don't hurt anything. > - Some sort of idle timeout, eg: a smtp server may want to time out > after 10 minutes of not recieving a command. > - A way of detecting a stalled or rebooted client. This is what > keepalive > does. It lets you detect a lost connection before some other > longer timeout > (eg: 24 hours) kicks in. There are very few server applications where 24 hour timeouts make sense. In the vast majortity of cases (again, telnetd excepted), timeouts are in the 1-5 minute range. Even web servers sending data use timeouts less than 10 minutes. The timeout, though, is on the current block of data, not the whole file. > > In my opinion, in the vast majority of cases, data timeouts are more > > logical than keepalives. 'telnetd' being the most obvious exception. > > Telnetd is the worst example. Just because I have not typed something for > two hours is no indication that the session should be closed. Only the > kernel can test the validity of the network link in this case. > However, of > I drop a link or reboot, then I do want it cleaned up in a timely fashion. Agreed. Telnetd is the exception, keepalives are great for it. For everything else, almost, data timeouts make far more sense. And keepalives will do nothing, but won't hurt anything. As I have said before, any application that does not implement data timeouts for all states, and does not enable keepalives is BROKEN. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 11:33:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C9C6214EBD for ; Sat, 5 Jun 1999 11:33:14 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA15517; Sat, 5 Jun 1999 11:33:12 -0700 (PDT) (envelope-from dillon) Date: Sat, 5 Jun 1999 11:33:12 -0700 (PDT) From: Matthew Dillon Message-Id: <199906051833.LAA15517@apollo.backplane.com> To: "David Schwartz" Cc: "Peter Wemm" , "Poul-Henning Kamp" , Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? References: <000201beaf7e$e0e8dd10$021d85d1@whenever.youwant.to> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : There is no logical reason for a well-designed web server to enable :keepalives. Of course, they don't hurt anything. : :... : : Agreed. Telnetd is the exception, keepalives are great for it. For :everything else, almost, data timeouts make far more sense. And keepalives :will do nothing, but won't hurt anything. : : As I have said before, any application that does not implement data :timeouts for all states, and does not enable keepalives is BROKEN. You are missing the point, big time. There are hundreds of programmers writing hundreds of servers, most written by third-parties. New ones pop up every day. Nobody is going to go through and make sure all of them turn on keepalives. Nobody is going to go and try to contact all the authors involved to try to get them to implement their own timeouts. There are, in fact, many servers where implementing a timeout is *inappropriate*. ssh, rsh, and telnet for example. nntp is an example of a server where the timeout depends on the use. Some ISP's might want to implement a timeout, others might not. At BEST I decided to *not* have a timeout... people can stay connected and idle for hours if they want. Your 'solution' is no solution at all. You aren't thinking through the problem carefully enough. The Keepalive capability exists for a reason. The original reasons for not turning them on by default all those years ago no longer exist, and the only reasons people come up with now are extremely shallow and uninformed. I have yet to hear a single informed opinion against turning on keepalives. All I hear is mob-mentality stuff: people with opinions not backed by real facts, or people with opinions based on assumptions that are incorrect. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 12:47:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from news.kiev.sovam.com (news.kiev.sovam.com [194.186.143.16]) by hub.freebsd.org (Postfix) with ESMTP id 1A19F14C20 for ; Sat, 5 Jun 1999 12:47:42 -0700 (PDT) (envelope-from mail@news.kiev.sovam.com) Received: from mail by news.kiev.sovam.com with local (Exim 2.12 #1) id 10qMPu-000P17-00 for freebsd-current@freebsd.org; Sat, 5 Jun 1999 22:47:42 +0300 From: Vladimir Litovka To: freebsd-current@freebsd.org Reply-To: Vladimir Litovka Subject: New 4's features Date: 5 Jun 1999 19:47:42 GMT Message-ID: <7jbust$2tov$1@news.kiev.sovam.com> References: X-Organization: Sovam Teleport Kiev (post does not reflect views of Sovam Teleport) X-Gated-By: news2list v1.3-pl1, (c) Vladimir Litovka X-Gated-Date: Sat Jun 5 19:47:42 1999 GMT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Where I can get info about all new features, introduced in FreeBSD 4? I've heard about JAILING - virtual machines inside one physical host with own root, etc. It is quite useful and I need this now :-) What about other new features? Or point me to the source (except CVS tree :-) of this information. Thank you. -- doka To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 13:13: 7 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 51B19155BF for ; Sat, 5 Jun 1999 13:12:41 -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 QAA50321; Sat, 5 Jun 1999 16:09:00 -0400 (EDT) Date: Sat, 5 Jun 1999 16:09:00 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon Cc: David Schwartz , Peter Wemm , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <199906051833.LAA15517@apollo.backplane.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 FWIW, I think only a fool would want a computer to NOT drop dead connections. Any "connection" that doesn't respond after 8 $^&! tries spaced FAR apart does NOT deserve to stay. Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 Sat Jun 5 13:25:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (Postfix) with ESMTP id 6072F14C21 for ; Sat, 5 Jun 1999 13:25:19 -0700 (PDT) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with ESMTP id OAA13478; Sat, 5 Jun 1999 14:23:12 -0600 (MDT) (envelope-from brett@peloton.physics.montana.edu) Date: Sat, 5 Jun 1999 14:23:12 -0600 (MDT) From: Brett Taylor To: Tomer Weller Cc: "" Subject: Re: KDE programs won't compile In-Reply-To: <99060521105700.05202@Tomer.DrugsAreGood.org> 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, > every small kde program i try to install (right now i tried Knewmail > and Kover) i get : checking for kde headers installed... configure: > error: your system is not able to compile a small KDE application! > Check, if you installed the KDE header files correctly. i'm using a > current machine as if last night, installed kde from ports (yes, > kde-libs was compiled with -CURRENT and EGCS) I can only assume that we install our KDE headers somewhere different than the developers (primarily on Linux machines). Dig around and figure out where the headers are on the FreeBSD machines and then you'll have to probably add a configure argument like: --with_kde_includes= /some/dir/where/kde/includes/are Dig through the knewmail configure script at the top and look for an option like this. Brett *********************************************************** Brett Taylor brett@peloton.physics.montana.edu * brett@daemonnews.org * * http://www.daemonnews.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 5 13:49:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-48.ppp.wenet.net [206.15.85.48]) by hub.freebsd.org (Postfix) with ESMTP id DB04114E05 for ; Sat, 5 Jun 1999 13:49:08 -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 NAA06776; Sat, 5 Jun 1999 13:48:58 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 5 Jun 1999 13:48:58 -0700 (PDT) From: Alex Zepeda To: Brett Taylor Cc: Tomer Weller , "" Subject: Re: KDE programs won't compile 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, 5 Jun 1999, Brett Taylor wrote: > I can only assume that we install our KDE headers somewhere different than > the developers (primarily on Linux machines). Dig around and figure out > where the headers are on the FreeBSD machines and then you'll have to > probably add a configure argument like: > > --with_kde_includes= /some/dir/where/kde/includes/are > > Dig through the knewmail configure script at the top and look for an > option like this. Yes, for better or for worse (I'd vote for worse), the FreeBSD ports install the kde headers in /usr/local/include.. However a simple --prefix=/usr/local *should* fix any configure problems, and if this is to make it into a FreeBSD port, use --prefix=$(PREFIX). - 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 5 14:18:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from devils.int.maquina.com (rcu127.rnl.ist.utl.pt [193.136.154.127]) by hub.freebsd.org (Postfix) with ESMTP id BE84114F37 for ; Sat, 5 Jun 1999 14:18:02 -0700 (PDT) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by devils.int.maquina.com (8.9.3/8.9.3) with ESMTP id WAA12518 for ; Sat, 5 Jun 1999 22:18:00 +0100 (WEST) (envelope-from gabriel@maquina.com) X-Authentication-Warning: devils.int.maquina.com: gabriel owned process doing -bs Date: Sat, 5 Jun 1999 22:17:59 +0100 (WEST) From: Jose Gabriel Marcelino X-Sender: gabriel@devils.int.maquina.com To: freebsd-current@freebsd.org Subject: Gtk trouble.. 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! Since upgrading to the gtk-1.2 ports I've been having some problems with programs compiled with it (like Gimp or e-conf) If I run them as a regular user I get the following errors during startup or during execution at random intervals (sometimes it takes longer than other times..) However if I run them as root everything works perfectly. ---- DUMP HERE devils% gimp Message: Passed serialization test IMLIB ERROR: SHM can't attach SHM Segment for Shared Pixmap mask Wrapper Falling back on Shared XImages Imlib ERROR: SHM can't attach SHM Segment for Shared XImage mask Falling back on XImages Gdk-ERROR **: BadAccess (attempt to access private resource denied) serial 2147 error_code 10 request_code 129 minor_code 1 aborting... gimp terminated: sigabrt caught Gdk-ERROR (recursed) **: BadShmSeg (invalid shared segment parameter) serial 2148 error_code 128 request_code 129 minor_code 5 aborting... gimp terminated: sigabrt caught ---- END DUMP I also noticed that the shared memory blocks are not released after this crash so they tend to use up resources. ---- BEGIN DUMP (gimp started without any previously assigned shm blocks) devils% ipcs Message Queues: T ID KEY MODE OWNER GROUP Shared Memory: T ID KEY MODE OWNER GROUP m 14090246 0 --rwarwarwa gabriel gabriel m 2424839 0 --rwarwarwa gabriel gabriel m 131080 0 --rwarwarwa gabriel gabriel Semaphores: T ID KEY MODE OWNER GROUP ---- END DUMP My 4.0-CURRENT (Jun 3) kernel conf has the following SYSV options options SYSVSHM options SYSVMSG options SYSVSEM options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) options SHMMAXPGS=4097 (The SHMMAX options were added when trying to fix the problem, but weren't useful) ktrace shows the problem starting: ---- BEGIN DUMP 12319 gimp CALL shmsys(0x3,0,0x40,0x3ff) 12319 gimp RET shmsys 2555913/0x270009 12319 gimp CALL shmsys(0,0x270009,0,0) 12319 gimp RET shmsys 805814272/0x3007c000 12319 gimp CALL shmsys(0x3,0,0x40,0x3ff) 12319 gimp RET shmsys 131083/0x2000b 12319 gimp CALL shmsys(0,0x2000b,0,0) 12319 gimp RET shmsys -1 errno 24 Too many open files <<< 12319 gimp CALL write(0x2,0xbfbfcc10,0x49) 12319 gimp GIO fd 2 wrote 73 bytes "IMLIB ERROR: SHM can't attach SHM Segment for Shared Pixmap mask Wrapp\ er " 12319 gimp RET write 73/0x49 12319 gimp CALL write(0x2,0xbfbfcc08,0x2c) 12319 gimp GIO fd 2 wrote 44 bytes " Falling back on Shared XImages " ---- END DUMP I tried playing around with the maxfiles in sysctl (kern.maxfiles and kern.maxfilesperproc) but to no effect :-\ I've sincerily run out of ideas :-( Can anyone help me fix this? Is this a limit problem?? How can I increase it? My full kernel conf file is at: http://www.maquina.com/pessoas/gabriel/DEVILS Thanks Jose Marcelino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 14:37:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from bantu.cl.msu.edu (bantu.cl.msu.edu [35.8.3.18]) by hub.freebsd.org (Postfix) with ESMTP id 0BCB414F37 for ; Sat, 5 Jun 1999 14:36:22 -0700 (PDT) (envelope-from dervish@bantu.cl.msu.edu) Received: (from dervish@localhost) by bantu.cl.msu.edu (8.9.3/8.9.3) id RAA09370; Sat, 5 Jun 1999 17:32:20 -0400 (EDT) (envelope-from dervish) Date: Sat, 5 Jun 1999 17:32:20 -0400 From: bush doctor To: "Daniel J. O'Connor" Cc: freebsd-current@freebsd.org Subject: Re: What is MTRR all about??? Message-ID: <19990605173220.A8620@bantu.cl.msu.edu> References: <19990604111316.A2066@bantu.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Daniel J. O'Connor on Sat, Jun 05, 1999 at 02:05:51AM +0930 X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 35 95 F8 63 DA 5B 32 51 8F A9 AC 3C B4 74 F3 BA WWW-Home-Page: http://www.msu.edu/~ikhala Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Daniel J. O'Connor (darius@dons.net.au): > > On 04-Jun-99 bush doctor wrote: > > Pentium Pro MTRR support enabled, default memory type is uncacheable > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > What is MTRR? Using the web based cross referencing tool I came up with > > MTRR's are a way to tell the processor how to cache regions of memory. Its > commonly used to speed up video card access by disabling caching on the linear > frame buffer, this makes writes to the card faster (around 0-30%). The penalty > is that reading is slower, but since that doesn't happen very often the speed > increase is good. > > Try man memcontrol - It doesn't yet work on SMP boxes though. Hmmm ... bantu.cl.msu.edu:dervish> more /usr/src/usr.sbin/memcontrol/Makefile PROG= memcontrol NOMAN= yes .include No man page yet. No horrors tho'. Man pages and info files are great, but there's nothing like reading through the sources ... #;^) > > --- > 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 > #;^) -- So ya want ta here da roots? Dem that feels it knows it ... bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 14:42:40 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 75F7F14BD5; Sat, 5 Jun 1999 14:42:36 -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 OAA02335; Sat, 5 Jun 1999 14:42:16 -0700 (PDT) Date: Sat, 5 Jun 1999 14:42:15 -0700 (PDT) From: Julian Elischer To: Poul-Henning Kamp Cc: Nick Hibma , Bruce Evans , current@FreeBSD.ORG, FreeBSD hackers mailing list Subject: Re: cdevsw_add In-Reply-To: <55580.928582798@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, 5 Jun 1999, Poul-Henning Kamp wrote: > In message , Nick Hibma writes: > > > >While on the topic: Who is working on devfs and why not? > > > > > > I'm not currently working on devfs, but I am building the infrastructure > > > it should be based on in the kernel. > > > >Anymore information available on where you are with this? > > I currently have a kernel running where dev_t is a pointer to a > "struct dev" and where char and block devs are collapsed at the > dev_t level. There are some bogons i need to fumigate, but I'm > off to give a course in Stockholm much of this coming week, so > don't expect any commits just now. (I may actually postpone/abandon > this step for now, since some of the changes pulls rugs away which > cover what looks to me like holes in the floor). > > Next is to integrate the dev_t anti-aliasing and vnode anti-aliasing > code. > > When I have that bit down and done, the next step is for device > drivers to register individual dev_t's rather than blanket cdevsw > entries. The later ability will be retained for pseudo drivers > and other (pseudo)magic. > > This registration will look pretty much like the current #ifdef'ed > DEVFS stuff, and in addition it will allow the driver to hang two > fields of the dev_t, typically a pointer to the struct softc and > maybe a unit number or something. This will obsolete all of > the magic minor -> {unit|softc} converters in our drivers and > make the "NFOO" configuration obsolete. > > That is, as such the end of this little project, and where a future > DEVFS could take off from. Basically all that is needed for a DEVFS > to do, is to hook into the dev_t maintenance code and construct > the directory tree. DEVFS has always meant to do exactly this. there is already a place in the structure for these two fields, and when devfs is running, the devsw[] table is not consulted. The vnode already contains a direct pointer to the devsw entry and a cookie (minor number), and these are called directly. there is already a node type for the 'unified' device type. there are three types of device in devfs BDEV, CDEV and DDEV. DDEV has only a pointer to teh methods and a cookie. (as you suggest above) > > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 14:44: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 6EDAF14BD5; Sat, 5 Jun 1999 14:44: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 OAA01924; Sat, 5 Jun 1999 14:37:30 -0700 (PDT) Date: Sat, 5 Jun 1999 14:37:29 -0700 (PDT) From: Julian Elischer To: Nick Hibma Cc: Poul-Henning Kamp , Bruce Evans , current@FreeBSD.ORG, FreeBSD hackers mailing list Subject: Re: cdevsw_add 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 Basically I'm not working on devfs at the moment since the bit that made it workable was ripped out with extreme prejudice by someone. I'm still absolutly convinced that a dynamic device registration and export framework is required in the long run, but I'm not fussed if it's based on the current devfs or an successor. I'd feel a bit happier about spending more time on it If I had any thought that the result would not be ripped out by the throat as soon as it works again, by a maniac that doesn't understand that it's a working subsystem (it was fully working at the time it was vandaliased but the nice fellow didn't even try it, and I got no warning except the commit message). There were two known problems that were based in other parts of the code (mfs and some vfs/module stuff) And the install software couldn't install with it. If PHK is working an a framework to make this easier, I'd love to get a white-paper on the topic because it's all unknown stuff at the moment. To get it going, you basically need to reverse the backout commits done by SOS a year ago. DEVSF itself works, but it needs a different disk subsystem to be able to represent dynamic disk partitions properly. julian On Sat, 5 Jun 1999, Nick Hibma wrote: > > >While on the topic: Who is working on devfs and why not? > > > > I'm not currently working on devfs, but I am building the infrastructure > > it should be based on in the kernel. > > Anymore information available on where you are with this? > > Cheers, > > Nick > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 14:54:13 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 C414014BD5 for ; Sat, 5 Jun 1999 14:54:08 -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 OAA02715; Sat, 5 Jun 1999 14:47:18 -0700 (PDT) Date: Sat, 5 Jun 1999 14:47:17 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: David Schwartz , Peter Wemm , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <199906051833.LAA15517@apollo.backplane.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 I think part of the solution is a new class of keepalives.. With this new class, a keepalive is sent every N second (3600?) but if no response is heard, no action is taken. The only action that is taken is if a NAK is recieved in response. Most IP addresses woudl be re-used within a few days, so even if someonen hangs up, in most cases SOMETHING will respond with a NACK withinthe next day or two. julian On Sat, 5 Jun 1999, Matthew Dillon wrote: > : There is no logical reason for a well-designed web server to enable > :keepalives. Of course, they don't hurt anything. > : > :... > : > : Agreed. Telnetd is the exception, keepalives are great for it. For > :everything else, almost, data timeouts make far more sense. And keepalives > :will do nothing, but won't hurt anything. > : > : As I have said before, any application that does not implement data > :timeouts for all states, and does not enable keepalives is BROKEN. > > You are missing the point, big time. > > There are hundreds of programmers writing hundreds of servers, most > written by third-parties. New ones pop up every day. Nobody > is going to go through and make sure all of them turn on keepalives. > Nobody is going to go and try to contact all the authors involved to > try to get them to implement their own timeouts. There are, in fact, > many servers where implementing a timeout is *inappropriate*. > > ssh, rsh, and telnet for example. nntp is an example of a server where > the timeout depends on the use. Some ISP's might want to implement a > timeout, others might not. At BEST I decided to *not* have a timeout... > people can stay connected and idle for hours if they want. > > Your 'solution' is no solution at all. You aren't thinking through the > problem carefully enough. > > The Keepalive capability exists for a reason. The original reasons for > not turning them on by default all those years ago no longer exist, and > the only reasons people come up with now are extremely shallow and > uninformed. > > I have yet to hear a single informed opinion against turning on > keepalives. > > All I hear is mob-mentality stuff: people with opinions not backed by > real facts, or people with opinions based on assumptions that are > incorrect. > > -Matt > Matthew Dillon > > > > 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 5 16:42:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.noc.netcom.net (mail1.noc.netcom.net [204.31.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 70642150EA for ; Sat, 5 Jun 1999 16:42:47 -0700 (PDT) (envelope-from kprater@industrysearch.com) Received: from webserver.industrysearch.com (webserver.industrysearch.com [207.95.128.10]) by mail1.noc.netcom.net (8.9.1/8.9.1/(NETCOM v2.00)) with ESMTP id QAA15351 for ; Sat, 5 Jun 1999 16:42:36 -0700 (PDT) Message-Id: <199906052342.QAA15351@mail1.noc.netcom.net> Received: from PB-S607 by webserver.industrysearch.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1458.49) id L9MBWCW2; Sat, 5 Jun 1999 19:32:44 -0400 To: freebsd-current@FreeBSD.ORG From: "Ken Prater, IndustrySearch.Com" Date: Sat, 5 Jun 99 19:42:22 +0000 Subject: "Link Your Web Site" To IndustrySearch.Com X-Mailer: WM - IndustrySearch.Com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Increase traffic to your company's web site with a FREE Hyperlink to IndustrySearch.Com. Thousands of industrial purchasing agents, buyers, engineers and others searching for suppliers and services can locate your business easily with our USA Industrial Directory. You can visit IndustrySearch.Com at http://industrysearch.com "Link Your Web Site" to our USA Industrial Directory Data Base today! Visit IndustrySearch.Com at http://industrysearch.com and click on "Link Your Web Site" Thank you, K. Prater USA INDUSTRIAL DATA BASE MANAGEMENT To be removed from our mailing list, please click Reply and type "REMOVE" in the subject field To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 16:44:51 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 33E49151FE for ; Sat, 5 Jun 1999 16:44:48 -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 TAA19843; Sat, 5 Jun 1999 19:44:40 -0400 (EDT) (envelope-from wollman) Date: Sat, 5 Jun 1999 19:44:40 -0400 (EDT) From: Garrett Wollman Message-Id: <199906052344.TAA19843@khavrinen.lcs.mit.edu> To: Brian Feldman Cc: Matthew Dillon , David Schwartz , Peter Wemm , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? In-Reply-To: References: <199906051833.LAA15517@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > FWIW, I think only a fool would want a computer to NOT drop dead connections. > Any "connection" that doesn't respond after 8 $^&! tries spaced FAR apart does > NOT deserve to stay. If they are spaced too far apart, it is possible for perfectly legitimate connections to get shot down as a result of external periodicities. (Does somebody's router reset every day at 2:45? If so, better hope no keepalives are scheduled for then!) -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 5 17:10:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from qix.jmz.org (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (Postfix) with ESMTP id EFE5F14C40 for ; Sat, 5 Jun 1999 17:10:33 -0700 (PDT) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.3) id CAA56894; Sun, 6 Jun 1999 02:12:27 +0200 (MET DST) (envelope-from jmz@FreeBSD.ORG) Date: Sun, 6 Jun 1999 02:12:27 +0200 (MET DST) Message-Id: <199906060012.CAA56894@qix.jmz.org> From: Jean-Marc Zucconi To: current@FreeBSD.ORG Subject: Mmap problem in -current? X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just noticed (kernel&world from friday) that locate always cores dump: $ locate xxxxxxxxxxxxxxxxxxxxxxx Segmentation fault (core dumped) $ gdb -c locate.core /usr/bin/locate Program terminated with signal 11, Segmentation fault. (gdb) bt #0 0x804964b in ___tolower () #1 0x235000 in ?? () #2 0x8049166 in ___tolower () #3 0x8048f93 in ___tolower () #4 0x80489f5 in ___tolower () The problem disappears if I recompile locate without the -DMMAP option. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.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 5 17:17: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 7DA7114C40 for ; Sat, 5 Jun 1999 17:17: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 UAA53918; Sat, 5 Jun 1999 20:13:56 -0400 (EDT) Date: Sat, 5 Jun 1999 20:13:56 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Garrett Wollman Cc: Matthew Dillon , David Schwartz , Peter Wemm , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <199906052344.TAA19843@khavrinen.lcs.mit.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 On Sat, 5 Jun 1999, Garrett Wollman wrote: > < said: > > > FWIW, I think only a fool would want a computer to NOT drop dead connections. > > Any "connection" that doesn't respond after 8 $^&! tries spaced FAR apart does > > NOT deserve to stay. > > If they are spaced too far apart, it is possible for perfectly > legitimate connections to get shot down as a result of external > periodicities. (Does somebody's router reset every day at 2:45? If > so, better hope no keepalives are scheduled for then!) But remember that the idea is the keepalive would keep trying for a certain amount of time, and this would be finely configureable. > > -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 > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 Sat Jun 5 17:18:25 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 3146314C40; Sat, 5 Jun 1999 17:18:24 -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 UAA53979; Sat, 5 Jun 1999 20:18:29 -0400 (EDT) Date: Sat, 5 Jun 1999 20:18:29 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Jean-Marc Zucconi Cc: current@FreeBSD.ORG Subject: Re: Mmap problem in -current? In-Reply-To: <199906060012.CAA56894@qix.jmz.org> 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, 6 Jun 1999, Jean-Marc Zucconi wrote: > I just noticed (kernel&world from friday) that locate always cores > dump: > $ locate xxxxxxxxxxxxxxxxxxxxxxx > Segmentation fault (core dumped) > $ gdb -c locate.core /usr/bin/locate > Program terminated with signal 11, Segmentation fault. > (gdb) bt > #0 0x804964b in ___tolower () > #1 0x235000 in ?? () > #2 0x8049166 in ___tolower () > #3 0x8048f93 in ___tolower () > #4 0x80489f5 in ___tolower () > > The problem disappears if I recompile locate without the -DMMAP > option. > > Jean-Marc Running on the very latest current, it does not work for me. > > -- > Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.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 Sat Jun 5 17:30: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from matrix.42.org (matrix.42.org [194.246.250.200]) by hub.freebsd.org (Postfix) with ESMTP id 41FE514BF7 for ; Sat, 5 Jun 1999 17:29:59 -0700 (PDT) (envelope-from sec@42.org) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.5) id CAA19179 (sender ); Sun, 6 Jun 1999 02:29:56 +0200 (CEST) Date: Sun, 6 Jun 1999 02:29:55 +0200 From: Stefan `Sec` Zehl To: freebsd-current@freebsd.org Cc: Matthew Dillon Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990606022955.C17345@matrix.42.org> References: <199906042101.OAA03028@biggusdiskus.flyingfox.com> <199906042004.NAA09067@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199906042004.NAA09067@apollo.backplane.com>; from Matthew Dillon on Fri, Jun 04, 1999 at 10:21:05PM +0200 I-love-doing-this: really Accept-Languages: de, en X-URL: http://sec.42.org/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 04, 1999 at 10:21:05PM +0200, Matthew Dillon wrote: > Around 0.02%, using the stats from one of BEST's busier servers. > That's percent. > > In otherwords, nobody would notice. You wouldn't notice, the backbones > wouldn't notice... nobody would notice. I would. I have several long-lived connections, with a few of them are sometimes unreachable for quote some time. I like that they survive, and would hate it, if some brain-dead default would ruin my perfectly set up connections. Even more, it would ruin dial-on-demand for a lot of people, i think. CU, Sec -- The Feynman problem solving Algorithm 1) Write down the problem 2) Think real hard 3) Write down the answer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 17:43:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from hydrogen.fircrest.net (metriclient-3.uoregon.edu [128.223.172.3]) by hub.freebsd.org (Postfix) with ESMTP id 431A714CBE for ; Sat, 5 Jun 1999 17:43:37 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.fircrest.net (8.9.1/8.8.7) id RAA05915; Sat, 5 Jun 1999 17:43:24 -0700 (PDT) Message-ID: <19990605174323.10313@hydrogen.nike.efn.org> Date: Sat, 5 Jun 1999 17:43:23 -0700 From: John-Mark Gurney To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? References: <199906051833.LAA15517@apollo.backplane.com> <199906052344.TAA19843@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199906052344.TAA19843@khavrinen.lcs.mit.edu>; from Garrett Wollman on Sat, Jun 05, 1999 at 07:44:40PM -0400 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman scribbled this message on Jun 5: > < said: > > > FWIW, I think only a fool would want a computer to NOT drop dead connections. > > Any "connection" that doesn't respond after 8 $^&! tries spaced FAR apart does > > NOT deserve to stay. > > If they are spaced too far apart, it is possible for perfectly > legitimate connections to get shot down as a result of external > periodicities. (Does somebody's router reset every day at 2:45? If > so, better hope no keepalives are scheduled for then!) yes, but are routers normally down for a couple hours?? if they are, you have other problems than worring about connections... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 17:44:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from matrix.42.org (matrix.42.org [194.246.250.200]) by hub.freebsd.org (Postfix) with ESMTP id BAADA14DEF for ; Sat, 5 Jun 1999 17:44:23 -0700 (PDT) (envelope-from sec@42.org) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.5) id CAA19459 (sender ); Sun, 6 Jun 1999 02:44:22 +0200 (CEST) Date: Sun, 6 Jun 1999 02:44:21 +0200 From: Stefan `Sec` Zehl To: freebsd-current@freebsd.org Cc: Poul-Henning Kamp Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990606024421.D17345@matrix.42.org> References: <199906042226.PAA02634@peterw.yahoo.com> <54651.928560942@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <54651.928560942@critter.freebsd.dk>; from Poul-Henning Kamp on Sat, Jun 05, 1999 at 07:37:57AM +0200 I-love-doing-this: really Accept-Languages: de, en X-URL: http://sec.42.org/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 05, 1999 at 07:37:57AM +0200, Poul-Henning Kamp wrote: > QED: The following patch. [...] > +tcp_keepalive="YES" # Kill dead TCP connections (or NO). I still don't understand why you insist on making it YES by default. It works fine like it is for most of the people right now. So why shouldn't the few servers which have problems without it, enable it? Make it a knob in rc.conf but off by default. As I understand it, It suffices if the server requests the keepalives. So if every FreeBSD-box has it on by default, I simply can not choose to have no keepalifes anymore, even if I turn them off locally. So this change is going to hurt somebody, somewhere. CU, Sec -- One of the main causes of the fall of the Roman Empire was that, lacking zero, they had now way to indicate successful termination of their C Programs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 17:57:32 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 3C02014D01 for ; Sat, 5 Jun 1999 17:57:30 -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 UAA20103; Sat, 5 Jun 1999 20:57:29 -0400 (EDT) (envelope-from wollman) Date: Sat, 5 Jun 1999 20:57:29 -0400 (EDT) From: Garrett Wollman Message-Id: <199906060057.UAA20103@khavrinen.lcs.mit.edu> To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? In-Reply-To: References: <199906052344.TAA19843@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> If they are spaced too far apart, it is possible for perfectly >> legitimate connections to get shot down as a result of external >> periodicities. (Does somebody's router reset every day at 2:45? If >> so, better hope no keepalives are scheduled for then!) > But remember that the idea is the keepalive would keep trying for a certain > amount of time, and this would be finely configureable. This wouldn't help the poor sod whose connection gets shot down every eight days while he's not there and doesn't know what hit him. A fundamental principle of protocol design is that synchronization effects can arise totally unexpectedly, with dangerous consequences for the stability of the Internet as a whole. It is necessary to introduce some amount of randomness in order to break up this unintentional synchronization. Modern (post-Van Jacobson) TCP is not directly subject to this effect unless you do something stupid like cause TCP to send a packet like clockwork every X units of time! (TCP can still fall prey to self-synchronization in the applications running on top of it, which is one of the reasons why routers are strongly encouraged to implement a RED queueing discipline by default.) I would withdraw my objection if keepalives were fixed to use a random distribution over [t - t/2, t + t/2]. -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 5 18:27:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from mordred.cs.ucla.edu (Mordred.CS.UCLA.EDU [131.179.192.128]) by hub.freebsd.org (Postfix) with ESMTP id D2B8A14FB4 for ; Sat, 5 Jun 1999 18:27:25 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Received: from mordred.cs.ucla.edu (localhost [127.0.0.1]) by mordred.cs.ucla.edu (8.9.3/8.9.3) with ESMTP id SAA00862; Sat, 5 Jun 1999 18:27:17 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Message-Id: <199906060127.SAA00862@mordred.cs.ucla.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Garrett Wollman Cc: freebsd-current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: Your message of "Sat, 05 Jun 1999 20:57:29 EDT." <199906060057.UAA20103@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Jun 1999 18:27:17 -0700 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This wouldn't help the poor sod whose connection gets shot down every > eight days while he's not there and doesn't know what hit him. One thing that no one points out is that this "idle" connection is potentially a security threat. Even if the physical connection is iced and is reconnected later using the same IP and the TCP connection is restored because it was kept alive, this presents a whole new world of interesting exploits. It's non-trivial, but that doesn't stop people like Network Associates' Labs from publishing papers on the subject. It seems to me that the keepalive might improve the security situation in the case in addition to doing something about connections with unknown status. The "poor sod" in this situation deserves something untoward, IMNSHO. Protocols like ssh do send something periodically whereas telnet doesn't. Telnet is a well-known security problem. As others have pointed out, this is an endemic problem in applications generally speaking, where a long-term "idle" connection isn't treated as an exception or an an error. Your point on randomization is well taken and is generally what's taught in graduate Internet architecture related courses (ok, Lixia Zhang will drill this into your head here at UCLA, YMMV elsewhere.) Although a more conservative distibution would be [t-t/2, t + 2t]. :-) -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 20:28:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-109.camalott.com [208.229.74.109]) by hub.freebsd.org (Postfix) with ESMTP id E382114D35; Sat, 5 Jun 1999 20:28:50 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id WAA16899; Sat, 5 Jun 1999 22:28:57 -0500 (CDT) (envelope-from joelh) To: Dag-Erling Smorgrav Cc: , Julian Elischer , Nate Williams , Matthew Hunt , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: From: Joel Ray Holveck Date: 05 Jun 1999 22:28:56 -0500 In-Reply-To: Dag-Erling Smorgrav's message of "02 Jun 1999 19:34:41 +0200" Message-ID: <86pv3ac8hz.fsf@detlev.UUCP> Lines: 16 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't know what's worse; that Microsoft themselves can't keep > Windows running for 50 days, or that they're incapable of manually > bumping the counter to a value close to UINT_MAX and wait a few > minutes for it to roll over. What's worst is probably that the bug doesn't affect operation. Nobody I've talked to has ever seen a Windows 95 machine stay up for over a week or so, let alone a month. joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 20:50: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-109.camalott.com [208.229.74.109]) by hub.freebsd.org (Postfix) with ESMTP id B8A5C14DF7 for ; Sat, 5 Jun 1999 20:49:59 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id WAA17011; Sat, 5 Jun 1999 22:50:12 -0500 (CDT) (envelope-from joelh) To: "Kevin J. Rowett" Cc: Matthew Dillon , David Malone , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <9906041725.aa11603@salmon.maths.tcd.ie> <4.2.0.56.19990604111235.00ae3ac0@rowett.org> From: Joel Ray Holveck Date: 05 Jun 1999 22:50:11 -0500 In-Reply-To: "Kevin J. Rowett"'s message of "Fri, 04 Jun 1999 11:20:34 -0700" Message-ID: <86n1yec7ik.fsf@detlev.UUCP> Lines: 14 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The central issue of keepalives is that, for one machine, they don't create > a significant load. Multiplied by the number of machines on the Internet, > it can become a problem. Divided by the combined bandwidth of the networks these machines are using, it ceases to be a problem. joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 21: 1:13 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 6D222152C9 for ; Sat, 5 Jun 1999 21:01:09 -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 NAA11893; Sun, 6 Jun 1999 13:30:58 +0930 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990605173220.A8620@bantu.cl.msu.edu> Date: Sun, 06 Jun 1999 13:30:58 +0930 (CST) From: "Daniel J. O'Connor" To: bush doctor Subject: Re: What is MTRR all about??? Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Jun-99 bush doctor wrote: > No man page yet. No horrors tho'. Man pages and info files are great, > but there's nothing like reading through the sources ... #;^) Well given that the source contains help information its not a bad problem.. I think the author is a tad busy at the moment :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 21: 7: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-109.camalott.com [208.229.74.109]) by hub.freebsd.org (Postfix) with ESMTP id E0B72152C9 for ; Sat, 5 Jun 1999 21:07:06 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id XAA17060; Sat, 5 Jun 1999 23:04:19 -0500 (CDT) (envelope-from joelh) To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <54651.928560942@critter.freebsd.dk> From: Joel Ray Holveck Date: 05 Jun 1999 23:04:18 -0500 In-Reply-To: Poul-Henning Kamp's message of "Sat, 05 Jun 1999 07:35:42 +0200" Message-ID: <86lndyc6v1.fsf@detlev.UUCP> Lines: 19 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 4. It would be desirable to have per socket timeouts, but would > require application changes which are unlikely to happen. Huh? I was just considering writing the patch for this. What application problems would this create? The worst thing I can see is that it would mean that changing the timeout value on a running system wouldn't affect already opened sockets. Even that may be changable by an external utility if I can think of a way to handle the locking in userland. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 22: 6:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-107.camalott.com [208.229.74.107]) by hub.freebsd.org (Postfix) with ESMTP id 97EF715003 for ; Sat, 5 Jun 1999 22:06:31 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id AAA20353; Sun, 6 Jun 1999 00:06:20 -0500 (CDT) (envelope-from joelh) To: Scott Michel Cc: Garrett Wollman , freebsd-current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <199906060127.SAA00862@mordred.cs.ucla.edu> From: Joel Ray Holveck Date: 06 Jun 1999 00:06:16 -0500 In-Reply-To: Scott Michel's message of "Sat, 05 Jun 1999 18:27:17 -0700" Message-ID: <86iu91dik6.fsf@detlev.UUCP> Lines: 48 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> This wouldn't help the poor sod whose connection gets shot down every >> eight days while he's not there and doesn't know what hit him. > One thing that no one points out is that this "idle" connection > is potentially a security threat. Even if the physical connection > is iced and is reconnected later using the same IP and the TCP > connection is restored because it was kept alive, this presents a > whole new world of interesting exploits. It's non-trivial, but > that doesn't stop people like Network Associates' Labs from > publishing papers on the subject. Keepalives are not particularly useful against connection hijacking, as far as I can tell, except perhaps that a keepalive packet may disclose the current TCP sequence number to the new assignee of a dynamic IP. (This, of course, presents an argument for the opposite stance.) As near as I can tell, you're saying that if a transient outage is restored, then after it's restored, an idle connection may be used by an intruder. How does the transient outage affect this? If the transient outage has the side effect of changing routing, then an attacker (or somebody else) is moving cables around, or a dynamic link with a dynamic IP is being changed. In the former case, then the long delay between keepalive packets should not make them a valid protection. (If it takes an attacker more than a week to move a cable, then may I suggest your attacker needs to refine his technique.) In the latter case, then the attacker who now holds the destination IP can respond to the keepalive packets masquerading as the legitimate recipient as easily as they can do any other work involved in hijacking your connection. If the outage did not cause a reconfiguration, then the attacker generally has no different access to your network than before, and no more means to hijack an open connection than before. I've got some whiskey in me right now, so I may be unclear on what you're saying. Am I missing something here? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 22:28:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-107.camalott.com [208.229.74.107]) by hub.freebsd.org (Postfix) with ESMTP id EF91514D10 for ; Sat, 5 Jun 1999 22:28:53 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id AAA20783; Sun, 6 Jun 1999 00:29:06 -0500 (CDT) (envelope-from joelh) To: Alex Zepeda Cc: Brett Taylor , Tomer Weller , "" Subject: Re: KDE programs won't compile References: From: Joel Ray Holveck Date: 06 Jun 1999 00:29:03 -0500 In-Reply-To: Alex Zepeda's message of "Sat, 5 Jun 1999 13:48:58 -0700 (PDT)" Message-ID: <86g145dhi8.fsf@detlev.UUCP> Lines: 38 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I can only assume that we install our KDE headers somewhere different than >> the developers (primarily on Linux machines). By default, KDE installs to /usr/local/kde. On RedHat, the RPM installs it to /opt/kde. All the includes are in /usr/local/kde/include, the libs in /usr/local/kde/lib, etc. >> where the headers are on the FreeBSD machines and then you'll have to >> probably add a configure argument like: >> --with_kde_includes= /some/dir/where/kde/includes/are Most KDE programs, including the configure scripts, look for the KDEDIR environment variable. I believe that the correct thing to do with FreeBSD's KDE install is to set KDEDIR to /usr/local. I do this in /etc/profile and /etc/csh.cshrc here. (I have KDE in /usr/local/kde here, too, so I haven't tested it as /usr/local.) > Yes, for better or for worse (I'd vote for worse), the FreeBSD ports > install the kde headers in /usr/local/include.. However a simple > --prefix=/usr/local *should* fix any configure problems, and if this > is to make it into a FreeBSD port, use --prefix=$(PREFIX). --prefix specifies where it should install to. However, this app needs to find some 3rd-party include files, so --prefix is not appropriate. FWIW, I've found that using /usr/local/kde instead of /usr/local has, in my case, been most helpful. I don't advocate it for every tiny library, but for something as large and complex as KDE, it works well. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 22:31:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-107.camalott.com [208.229.74.107]) by hub.freebsd.org (Postfix) with ESMTP id 1E5AE14D10; Sat, 5 Jun 1999 22:31:17 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id AAA20815; Sun, 6 Jun 1999 00:31:26 -0500 (CDT) (envelope-from joelh) To: Brian Feldman Cc: Jean-Marc Zucconi , current@FreeBSD.ORG Subject: Re: Mmap problem in -current? References: From: Joel Ray Holveck Date: 06 Jun 1999 00:31:23 -0500 In-Reply-To: Brian Feldman's message of "Sat, 5 Jun 1999 20:18:29 -0400 (EDT)" Message-ID: <86emjpdheb.fsf@detlev.UUCP> Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I just noticed (kernel&world from friday) that locate always cores >> dump: >> $ locate xxxxxxxxxxxxxxxxxxxxxxx >> Segmentation fault (core dumped) >> The problem disappears if I recompile locate without the -DMMAP >> option. > Running on the very latest current, it does not work for me. By 'it', do you mean that locate does not work, that the failure test does not work (ie, locate is fine for you), or that the workaround does not work? Thanks, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 22:32:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-48.ppp.wenet.net [206.15.85.48]) by hub.freebsd.org (Postfix) with ESMTP id 37AC4150E0 for ; Sat, 5 Jun 1999 22:32:27 -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 WAA07868; Sat, 5 Jun 1999 22:32:15 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 5 Jun 1999 22:32:15 -0700 (PDT) From: Alex Zepeda To: Joel Ray Holveck Cc: Brett Taylor , Tomer Weller , "" Subject: Re: KDE programs won't compile In-Reply-To: <86g145dhi8.fsf@detlev.UUCP> 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 6 Jun 1999, Joel Ray Holveck wrote: > By default, KDE installs to /usr/local/kde. On RedHat, the RPM > installs it to /opt/kde. All the includes are in > /usr/local/kde/include, the libs in /usr/local/kde/lib, etc. Yup. > Most KDE programs, including the configure scripts, look for the > KDEDIR environment variable. I believe that the correct thing to do > with FreeBSD's KDE install is to set KDEDIR to /usr/local. I do this > in /etc/profile and /etc/csh.cshrc here. (I have KDE in > /usr/local/kde here, too, so I haven't tested it as /usr/local.) KDEDIR is depreciated. > --prefix specifies where it should install to. However, this app > needs to find some 3rd-party include files, so --prefix is not > appropriate. Uh no. The prefix is also used by the configuration script to figure out where the kdelibs were installed to. From configure: ac_default_prefix=${KDEDIR:-/usr/local/kde} [...] includedir='${prefix}/include' [...] echo $ac_n "checking for KDE""... $ac_c" 1>&6 echo "configure:4014: checking for KDE" >&5 if test "${prefix}" != NONE; then kde_includes=${prefix}/include ac_kde_includes=$prefix/include > FWIW, I've found that using /usr/local/kde instead of /usr/local has, > in my case, been most helpful. I don't advocate it for every tiny > library, but for something as large and complex as KDE, it works well. Yes, KDE scatters too many things too many places to really be a good fit in /usr/local/kde. Plus putting it in its own directory makes for easy removal and switching between versions of KDE. - 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 5 23: 8:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1B3AF14BB8 for ; Sat, 5 Jun 1999 23:08:41 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA17573; Sat, 5 Jun 1999 23:08:32 -0700 (PDT) (envelope-from dillon) Date: Sat, 5 Jun 1999 23:08:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199906060608.XAA17573@apollo.backplane.com> To: Garrett Wollman Cc: Brian Feldman , David Schwartz , Peter Wemm , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? References: <199906051833.LAA15517@apollo.backplane.com> <199906052344.TAA19843@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> FWIW, I think only a fool would want a computer to NOT drop dead connections. :> Any "connection" that doesn't respond after 8 $^&! tries spaced FAR apart does :> NOT deserve to stay. : :If they are spaced too far apart, it is possible for perfectly :legitimate connections to get shot down as a result of external :periodicities. (Does somebody's router reset every day at 2:45? If :so, better hope no keepalives are scheduled for then!) : :-GAWollman : :Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same Irrelevant. If data is transmitted from either side at 'just the wrong time', you have the same problem. Keepalives do not make it worse. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 23:14: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A25BD15400 for ; Sat, 5 Jun 1999 23:14:04 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA17631; Sat, 5 Jun 1999 23:14:02 -0700 (PDT) (envelope-from dillon) Date: Sat, 5 Jun 1999 23:14:02 -0700 (PDT) From: Matthew Dillon Message-Id: <199906060614.XAA17631@apollo.backplane.com> To: Brian Feldman Cc: Garrett Wollman , David Schwartz , Peter Wemm , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> If they are spaced too far apart, it is possible for perfectly :> legitimate connections to get shot down as a result of external :> periodicities. (Does somebody's router reset every day at 2:45? If :> so, better hope no keepalives are scheduled for then!) : :But remember that the idea is the keepalive would keep trying for a certain :amount of time, and this would be finely configureable. : Brian Feldman _ __ ___ ____ ___ ___ ___ Adjusting the keepalive's retry period after activation is also irrelevant. As they currently stand, keepalives operate in virtually the same fashion as sending a byte of data. Extending the retry period for a keepalive is no more a reliable solution then extending ( or shortening ) the initial timeout because you are only effecting one small aspect of the TCP protocol. You are not effecting timeouts associated with normal data transmitted ( from either side ) over TCP. Unless the entire purpose of the connection is to simply be connected, with no data flow ever, being able to finely tune keepalive values does not really help. The existing rough tuning is as much as anyone will ever need to mess with. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 23:17:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from detlev.UUCP (tex-63.camalott.com [208.229.74.63]) by hub.freebsd.org (Postfix) with ESMTP id 8697A14CBE for ; Sat, 5 Jun 1999 23:17:34 -0700 (PDT) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.3/8.9.3) id BAA21050; Sun, 6 Jun 1999 01:17:09 -0500 (CDT) (envelope-from joelh) To: Alex Zepeda Cc: Brett Taylor , Tomer Weller , "" Subject: Re: KDE programs won't compile References: From: Joel Ray Holveck Date: 06 Jun 1999 01:17:08 -0500 In-Reply-To: Alex Zepeda's message of "Sat, 5 Jun 1999 22:32:15 -0700 (PDT)" Message-ID: <86909xdfa3.fsf@detlev.UUCP> Lines: 44 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Most KDE programs, including the configure scripts, look for the >> KDEDIR environment variable. I believe that the correct thing to do >> with FreeBSD's KDE install is to set KDEDIR to /usr/local. I do this >> in /etc/profile and /etc/csh.cshrc here. (I have KDE in >> /usr/local/kde here, too, so I haven't tested it as /usr/local.) > KDEDIR is depreciated. How do you mean "depreciated"? Should users not set it, or applications not check for it, or what? The 2.0 kdelibs/README states: IMPORTANT: most applications need KDEDIR as the directory where KDE is installed. Please set this in your login file. Of course, this could be out-of-date. I do not know of an alternate mechanism. A brief examination of the 2.0 kdebase and koffice configure.in's do not immediately reveal one either, other than --prefix. Is this the accepted method, then? What if a user wants to install something in a different place than the rest of KDE? >> --prefix specifies where it should install to. However, this app >> needs to find some 3rd-party include files, so --prefix is not >> appropriate. > Uh no. The prefix is also used by the configuration script to figure out > where the kdelibs were installed to. From configure: I apologize, I did not examine the source before I spoke. I will maintain that --prefix is, in general, a target specifier rather than a source specifier. In the case of the configure script you quoted (and probably all KDE configure scripts), and if they coincide (as they usually will), then --prefix will DTRT. Which configure script did you take this from? I see the same code in many bits of KDE itself. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 23:20:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1C6E814CBE for ; Sat, 5 Jun 1999 23:20:24 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA17657; Sat, 5 Jun 1999 23:20:20 -0700 (PDT) (envelope-from dillon) Date: Sat, 5 Jun 1999 23:20:20 -0700 (PDT) From: Matthew Dillon Message-Id: <199906060620.XAA17657@apollo.backplane.com> To: Stefan `Sec` Zehl Cc: freebsd-current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <199906042101.OAA03028@biggusdiskus.flyingfox.com> <199906042004.NAA09067@apollo.backplane.com> <19990606022955.C17345@matrix.42.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> wouldn't notice... nobody would notice. : :I would. I have several long-lived connections, with a few of them :are sometimes unreachable for quote some time. I like that they survive, :and would hate it, if some brain-dead default would ruin my perfectly :set up connections. : :Even more, it would ruin dial-on-demand for a lot of people, i think. : :CU, : Sec Turn on keepalives and see if you actually notice. I can virtually guarentee that you will not notice. As far as dial-on-demand goes, that also makes no real difference. There are very few two-way dial-on-demand systems. Usually dial-on-demand is outgoing only. Incoming packets cannot activate them. There are a few ISDN-based links and ISPs that implement it in both directions both those are rapidly dying away. This means that incoming data on the undialed link will cause a disconnect, making holding such connections over an undialed link so unreliable that depending on the effect is stupid. If you have an active connection to somewhere, the link needs to be up for that connection to remain reliable whether keepalives are turned on or not. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 23:26:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D66E314C19 for ; Sat, 5 Jun 1999 23:26:30 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA17701; Sat, 5 Jun 1999 23:26:28 -0700 (PDT) (envelope-from dillon) Date: Sat, 5 Jun 1999 23:26:28 -0700 (PDT) From: Matthew Dillon Message-Id: <199906060626.XAA17701@apollo.backplane.com> To: Garrett Wollman Cc: Brian Feldman , current@FreeBSD.ORG Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? References: <199906052344.TAA19843@khavrinen.lcs.mit.edu> <199906060057.UAA20103@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :< said: : :>> If they are spaced too far apart, it is possible for perfectly :>> legitimate connections to get shot down as a result of external :>> periodicities. (Does somebody's router reset every day at 2:45? If :>> so, better hope no keepalives are scheduled for then!) : :> But remember that the idea is the keepalive would keep trying for a certain :> amount of time, and this would be finely configureable. : :This wouldn't help the poor sod whose connection gets shot down every :eight days while he's not there and doesn't know what hit him. If the poor sod hasn't touched his xterm for 8 days, he's either dead or he doesn't care if it goes away. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 23:28: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B9C941539A for ; Sat, 5 Jun 1999 23:28:07 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA17722; Sat, 5 Jun 1999 23:27:23 -0700 (PDT) (envelope-from dillon) Date: Sat, 5 Jun 1999 23:27:23 -0700 (PDT) From: Matthew Dillon Message-Id: <199906060627.XAA17722@apollo.backplane.com> To: Joel Ray Holveck Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <54651.928560942@critter.freebsd.dk> <86lndyc6v1.fsf@detlev.UUCP> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> 4. It would be desirable to have per socket timeouts, but would :> require application changes which are unlikely to happen. : :Huh? I was just considering writing the patch for this. What :application problems would this create? : :The worst thing I can see is that it would mean that changing the :timeout value on a running system wouldn't affect already opened :sockets. Even that may be changable by an external utility if I can :think of a way to handle the locking in userland. : :Cheers, :joelh I see no use whatsoever for being able to specify per-socket keepalive timeouts. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jun 5 23:28:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5882C1544C for ; Sat, 5 Jun 1999 23:28:48 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA17693; Sat, 5 Jun 1999 23:25:41 -0700 (PDT) (envelope-from dillon) Date: Sat, 5 Jun 1999 23:25:41 -0700 (PDT) From: Matthew Dillon Message-Id: <199906060625.XAA17693@apollo.backplane.com> To: Stefan `Sec` Zehl Cc: freebsd-current@FreeBSD.ORG, Poul-Henning Kamp Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <199906042226.PAA02634@peterw.yahoo.com> <54651.928560942@critter.freebsd.dk> <19990606024421.D17345@matrix.42.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Sat, Jun 05, 1999 at 07:37:57AM +0200, Poul-Henning Kamp wrote: :> QED: The following patch. :[...] :> +tcp_keepalive="YES" # Kill dead TCP connections (or NO). : :I still don't understand why you insist on making it YES by default. It :works fine like it is for most of the people right now. :So why shouldn't the few servers which have problems without it, enable :it? Make it a knob in rc.conf but off by default. :As I understand it, It suffices if the server requests the keepalives. :So if every FreeBSD-box has it on by default, I simply can not choose to :have no keepalifes anymore, even if I turn them off locally. So this :change is going to hurt somebody, somewhere. : :CU, : Sec The problem is that certain classes of connections or network instabilities can leave stale daemons. FreeBSD boxes operating as servers in any real capacity for certain services will want keepalives on. The system defaults should result in stability. For a significant percentage of machines, leaving keepalives off results in a slow buildup of processes sitting on dead connections. i.e. long term instability. This is especially true of machines which people log into with telnet, NNTP, and a number of other servers. When you leave a machine on 24 hours a day, these sorts of things can become important. The machine needs to be able to clean up after itself. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 6 0: 9:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id 39A0414D2E for ; Sun, 6 Jun 1999 00:09:39 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost.nibb.ac.jp [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id PAA03587; Sun, 6 Jun 1999 15:57:42 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: dillon@apollo.backplane.com Cc: sec@42.org, freebsd-current@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: net.inet.tcp.always_keepalive on as default ? From: Tomoaki NISHIYAMA In-Reply-To: <199906060620.XAA17657@apollo.backplane.com> References: <199906042101.OAA03028@biggusdiskus.flyingfox.com> <199906042004.NAA09067@apollo.backplane.com> <19990606022955.C17345@matrix.42.org> <199906060620.XAA17657@apollo.backplane.com> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990606155741R.tomoaki@moss.nibb.ac.jp> Date: Sun, 06 Jun 1999 15:57:41 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 18 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Matthew Dillon Subject: Re: net.inet.tcp.always_keepalive on as default ? Date: Sat, 5 Jun 1999 23:20:20 -0700 (PDT) Message-ID: <199906060620.XAA17657@apollo.backplane.com> dillon> As far as dial-on-demand goes, that also makes no real difference. dillon> There are very few two-way dial-on-demand systems. Usually Two-way dial-on-demand systems may be few but actually exist. In that case, a keep alive packet may cause an extra charge of 10 yen (about US$0.08), which can be significant if the amount of other traffic is small. Note that I am not necessarily against keep alive, if there is a benefit over that charge. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 6 0:20:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 6620E14DD3 for ; Sun, 6 Jun 1999 00:20:36 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 34761 invoked by uid 1001); 6 Jun 1999 07:20:35 +0000 (GMT) To: dillon@apollo.backplane.com Cc: joelh@gnu.org, phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 5 Jun 1999 23:27:23 -0700 (PDT)" References: <199906060627.XAA17722@apollo.backplane.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 06 Jun 1999 09:20:35 +0200 Message-ID: <34759.928653635@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :Huh? I was just considering writing the patch for this. What > :application problems would this create? > : > :The worst thing I can see is that it would mean that changing the > :timeout value on a running system wouldn't affect already opened > :sockets. Even that may be changable by an external utility if I can > :think of a way to handle the locking in userland. > : > > I see no use whatsoever for being able to specify per-socket keepalive > timeouts. Well, if it was implemented with the TCP_KEEPALIVE option, it would be one more part of the system that complied with the X/Open specifications. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 6 0:23:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id D602514C9B for ; Sun, 6 Jun 1999 00:23:38 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 34794 invoked by uid 1001); 6 Jun 1999 07:23:37 +0000 (GMT) To: scottm@cs.ucla.edu Cc: wollman@khavrinen.lcs.mit.edu, freebsd-current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 05 Jun 1999 18:27:17 -0700" References: <199906060127.SAA00862@mordred.cs.ucla.edu> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 06 Jun 1999 09:23:37 +0200 Message-ID: <34792.928653817@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The "poor sod" in this situation deserves something untoward, > IMNSHO. Protocols like ssh do send something periodically whereas > telnet doesn't. Telnet is a well-known security problem. As others > have pointed out, this is an endemic problem in applications > generally speaking, where a long-term "idle" connection isn't > treated as an exception or an an error. Some of us use only ssh for remote login *and* specifically turn off ssh keepalives, in order to keep login sessions up for weeks at at time. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message