From owner-freebsd-current Sun Oct 17 9:14:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail3.netcom.com (mail3.netcom.com [199.183.9.133]) by hub.freebsd.org (Postfix) with ESMTP id C557114DAF for ; Sun, 17 Oct 1999 09:14:34 -0700 (PDT) (envelope-from jy@netcom.com) Received: from hopper2.jy.intra (jy@netcom19.netcom.com [199.183.9.119]) by mail3.netcom.com (8.8.5-r-beta/8.8.5/(NETCOM v1.02)) with ESMTP id JAA01464 for ; Sun, 17 Oct 1999 09:14:30 -0700 (PDT) Received: from hopper2.jy.intra (jy@localhost [127.0.0.1]) by hopper2.jy.intra (8.9.1/8.8.5) with ESMTP id JAA02722 for ; Sun, 17 Oct 1999 09:18:23 -0700 Message-Id: <199910171618.JAA02722@hopper2.jy.intra> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Oct 1999 09:18:23 -0700 From: jy@netcom.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth a73d5537 unsubscribe freebsd-current jy@netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 9:14:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.netcom.com (mail.netcom.com [199.183.9.131]) by hub.freebsd.org (Postfix) with ESMTP id B36F81513F for ; Sun, 17 Oct 1999 09:14:47 -0700 (PDT) (envelope-from jy@netcom.com) Received: from hopper2.jy.intra (jy@netcom19.netcom.com [199.183.9.119]) by mail.netcom.com (8.8.5-r-beta/8.8.5/(NETCOM v1.02)) with ESMTP id JAA22806 for ; Sun, 17 Oct 1999 09:14:34 -0700 (PDT) Received: from hopper2.jy.intra (jy@localhost [127.0.0.1]) by hopper2.jy.intra (8.9.1/8.8.5) with ESMTP id JAA02731 for ; Sun, 17 Oct 1999 09:18:35 -0700 Message-Id: <199910171618.JAA02731@hopper2.jy.intra> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Oct 1999 09:18:35 -0700 From: jy@netcom.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 80b21ad8 unsubscribe freebsd-security jy@netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 9:22:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from modemcable156.106-200-24.mtl.mc.videotron.net (modemcable156.106-200-24.mtl.mc.videotron.net [24.200.106.156]) by hub.freebsd.org (Postfix) with SMTP id 2E29C14C3D for ; Sun, 17 Oct 1999 09:22:04 -0700 (PDT) (envelope-from patrick@mindstep.com) Received: (qmail 509 invoked from network); 17 Oct 1999 15:55:22 -0000 Received: from unknown (HELO patrak) (192.168.10.25) by jacuzzi.local.mindstep.com with SMTP; 17 Oct 1999 15:55:22 -0000 Message-ID: <001101bf18b8$049e5e40$190aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "Cy Schubert - ITSD Open Systems Group" , , References: <011801bf159c$f80630e0$190aa8c0@local.mindstep.com> <199910161454.HAA46310@cwsys.cwsent.com> Subject: Re: make.conf options (was Re: package-like feature for the base distrib (was Re: FreeSSH)) Date: Sun, 17 Oct 1999 11:55:21 -0400 Organization: MindStep Corporation 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.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, From: Cy Schubert - ITSD Open Systems Group > > I was not talking about things that constitute the "real" core of the > > distribution (kernel, basic libraries etc.). I was more thinking about > > "userland" stuff that is included in the distribution but might not be > > required by everybody. Sendmail for example is something I don't want since > > I user qmail. However I have to remove it by hand... Other examples are bind > > or perl. > > You don't need to install them. Just put these in make.conf. > > NO_SENDMAIL= true > NOPERL= true > NOGAMES= true > > It might be a good idea to support NONAMED, NOUUCP, and NONFS, > defines in make.conf. Since some like to use Qmail, Postfix, SSH, and > Kerberos V, like BUILD_PORTS='postfix ssh krb5 XFree86' in make.conf > would fetch new copies of distfiles (if you don't have them), de-install > old versions, build and install the listed ports each time a make world > is performed. This is going in the right direction, but here is a question (and I don't have the answer). Is it so much more easier to create new compile time directive than to go the extra step and use packages where they are available ? For example "bind8" is available as a package. Why not have the base install process use that instead of using its own source ? After all the package system is good, and we should capitalize on it. For things that don't have an equivalent (yet) in the ports, then there are 2 approaches: - the component is "optional enough" that it could be made as a package - or it is really required, in which case it belongs to the core installation. By optional enough, I mean something that: (this is likely not complete) a/ is not required by everybody (UUCP, YP) nore by the kernel to run properly b/ does not rely on other kernel components to be built properly c/ ... Again, I think that "sendmail" definitelly falls in that category as well as "bind". As far as the BUILD_PORTS variable. This is a great idea... Again why not take it to the next level which could be to have a new "target" in the ports' makefile: something like "make pkg_update" which would go and build/install the new version of all the installed packages/ports ? If I can help moving things in that direction, I will hapily land a hand... Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 9:26:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 83F4F14A13 for ; Sun, 17 Oct 1999 09:26:51 -0700 (PDT) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.03 #1) id 11ct91-0005jp-00 for freebsd-current@freebsd.org; Sun, 17 Oct 1999 09:26:51 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: k4 in current Message-Id: Date: Sun, 17 Oct 1999 09:26:51 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG anyone out there using kerberos4 in current? i am not succeeding in a mixed current/stable/bsdi/... environment. o the current systen is the keyserver o anyone of the systems can get a tgt o given a tgt, the stable/bsdi systems can all rlogin/rsh to eachother just fine o a user on the current system rlogging in to a stable or bsdi system succeeds with the rlogin, but typing produces garbage, e.g. here is an "ls" test.psg.com:/usr/randy> \303t o a bsdi or stable system can not rlogin/rsh into the current system psg.com:/usr/home/randy> rlogin -x rip rlogin: krcmd_mutual: Generic kerberos error (kfailure) rlogin: the -x flag requires Kerberos authentication and the syslog on the current/server system shows Oct 17 09:24:49 rlogind[21997]: usage: rlogind [-Dalnx] Oct 17 09:24:49 rlogind[21997]: Connection from 147.28.0.62 \ on illegal port randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 9:31: 2 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 CCBD114A13; Sun, 17 Oct 1999 09:30:58 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA46571; Sun, 17 Oct 1999 12:30:51 -0400 (EDT) (envelope-from wollman) Date: Sun, 17 Oct 1999 12:30:51 -0400 (EDT) From: Garrett Wollman Message-Id: <199910171630.MAA46571@khavrinen.lcs.mit.edu> To: "Patrick Bihan-Faou" Cc: "Cy Schubert - ITSD Open Systems Group" , , Subject: Re: make.conf options (was Re: package-like feature for the base distrib (was Re: FreeSSH)) In-Reply-To: <001101bf18b8$049e5e40$190aa8c0@local.mindstep.com> References: <011801bf159c$f80630e0$190aa8c0@local.mindstep.com> <199910161454.HAA46310@cwsys.cwsent.com> <001101bf18b8$049e5e40$190aa8c0@local.mindstep.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > This is going in the right direction, but here is a question (and I don't > have the answer). Is it so much more easier to create new compile time > directive than to go the extra step and use packages where they are > available ? For example "bind8" is available as a package. Why not have the > base install process use that instead of using its own source ? Because one of the fundamental principles is that a default installation, with no third-party packages, should still be a complete system, and -- most importantly -- be able to regenerate itself precisely from source. Hence, the default system needs to contain *an* MTA (not necessarily sendmail, but that's not a question we want to reopen), and *a* name server (not necessarily bind, but there are no other choices). -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 Sun Oct 17 9:37:52 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 8072C14E0E for ; Sun, 17 Oct 1999 09:37:38 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA46596; Sun, 17 Oct 1999 12:37:37 -0400 (EDT) (envelope-from wollman) Date: Sun, 17 Oct 1999 12:37:37 -0400 (EDT) From: Garrett Wollman Message-Id: <199910171637.MAA46596@khavrinen.lcs.mit.edu> To: Randy Bush Cc: FreeBSD Current Subject: k4 in current In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > anyone out there using kerberos4 in current? i am not succeeding in a mixed > current/stable/bsdi/... environment. > o the current systen is the keyserver You mean KDC, of course. > o a user on the current system rlogging in to a stable or bsdi system > succeeds with the rlogin, but typing produces garbage, e.g. here is an > "ls" > test.psg.com:/usr/randy> \303t I'm not having this problem. wollman@khavrinen$ rlogin -x kuragara This rlogin session is using DES encryption for all transmissions. Last login: Sun Oct 17 00:16:22 from khavrinen Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 3.3-RELEASE (GENERIC) #0: Thu Sep 16 23:40:35 GMT 1999 bash$ exit exirlogin: connection closed. wollman@khavrinen$ klist Ticket file: /tmp/tkt_12369 Principal: wollman@LCS.MIT.EDU Issued Expires Principal Oct 17 12:32:25 Oct 17 22:32:25 krbtgt.LCS.MIT.EDU@LCS.MIT.EDU Oct 17 12:32:33 Oct 17 22:32:33 rcmd.kuragara@LCS.MIT.EDU wollman@khavrinen$ uname -a FreeBSD khavrinen.lcs.mit.edu 4.0-CURRENT FreeBSD 4.0-CURRENT #593: Fri Sep 10 12:26:52 EDT 1999 root@khavrinen.lcs.mit.edu:/usr/src/sys/compile/KHAVRINEN i386 What's more, khavrinen (my machine) is using our new v5 KDC in v4-compatibility mode, whereas kuragara (a random e-machine out in the hallway) is using the old v4 KDC. -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 Sun Oct 17 9:45:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail3.netcom.com (mail3.netcom.com [199.183.9.133]) by hub.freebsd.org (Postfix) with ESMTP id 37F9614A13 for ; Sun, 17 Oct 1999 09:45:08 -0700 (PDT) (envelope-from jy@netcom.com) Received: from hopper2.jy.intra (jy@netcom19.netcom.com [199.183.9.119]) by mail3.netcom.com (8.8.5-r-beta/8.8.5/(NETCOM v1.02)) with ESMTP id JAA04940 for ; Sun, 17 Oct 1999 09:45:04 -0700 (PDT) Received: from hopper2.jy.intra (jy@localhost [127.0.0.1]) by hopper2.jy.intra (8.9.1/8.8.5) with ESMTP id JAA03278 for ; Sun, 17 Oct 1999 09:47:52 -0700 Message-Id: <199910171647.JAA03278@hopper2.jy.intra> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Oct 1999 09:47:52 -0700 From: jy@netcom.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth a73d5537 unsubscribe freebsd-current jy@netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 10:17: 0 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 8039A14CA1 for ; Sun, 17 Oct 1999 10:16:56 -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.3) with ESMTP id KAA02163; Sun, 17 Oct 1999 10:16:50 -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 KAA17170; Sun, 17 Oct 1999 10:16:49 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 17 Oct 1999 10:16:49 -0700 (PDT) Message-Id: <199910171716.KAA17170@vashon.polstra.com> To: patl@phoenix.volant.org Subject: Re: Weak symbols (Was: World breakage in libc_r?) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , wrote: > On 15-Oct-99 at 15:05, John Birrell (jb@cimlogic.com.au) wrote: > > > A weak symbol is like an alias for another (strong) symbol. The > > linker will link to strong symbols first, then, for any unresolved > > references, it will try to resolve against the weak symbols before > > going on to the next library. Weak symbols are a good way to hide > > things in order to stop polluting the name space. But they can > > cause problems too. > > If so, then the definition has changed since they were first > invented. (Around 20 years ago, IIRC.) Weak symbols were/are used > to refer to external objects that may or may not actually be linked > in. The difference between a weak and a strong symbol is/was that > a strong symbol would cause the appropriate library to be loaded > to ensure that it would be defined (and generate errors if still > unresolved at the end of the link) whereas a weak symbol would not > cause a library module to be loaded and would not cause an error if > left unresolved. You are both right. There are weak definitions (which jb described) and there are weak references (which patl described). Both are unfortunately specified by the same assembler directive ".weak". The distinction is made based on whether the symbol is defined in the current module or not. I have a couple of additions to the above. A weak definition needn't be an alias for another symbol, strictly speaking. But that's how they are normally used. Regarding weak references, if such a reference is still undefined at the end of a link, it is treated as if it were defined with the value 0. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 11:25: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id B10C114C28 for ; Sun, 17 Oct 1999 11:24:56 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id UAA23527 for ; Sun, 17 Oct 1999 20:24:54 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id UAA13247 for current@freebsd.org; Sun, 17 Oct 1999 20:24:54 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id UAA00623 for ; Sun, 17 Oct 1999 20:24:53 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sun, 17 Oct 1999 20:24:53 +0200 (CEST) From: Michael Reifenberger To: FreeBSD-Current Subject: -current problems with the lates pccard changes? Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1198591489-940184693=:603" 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-1198591489-940184693=:603 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, after upgrading my Tecra-8000 to -current as of -now I get the attached output during boot. And the ep0 driver doesnt get attached with the following message: Cannot allocate ports 0x240-0x24f Does the output look normal? Particularly the muliple attaches worries me. Does anyone else see this? BTW: I have machdep.pccard.pcic_irq="11" in loader.conf.local if it matters. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis --0-1198591489-940184693=:603 Content-Type: APPLICATION/octet-stream; name="dmesg.out.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dmesg.out.gz" H4sICB4SCjgCA2RtZXNnLm91dACdV9tu40gOfV59BZF9SQDZulq+oBOsfEla SDs2IqeReWrIUsmujaxSqyQn7q9fsiQ78WRnBjNBoChVJItFHh5SE1EcSr7Z VnAZX4E1HNodfAxhtWVwWzI2DqewLMV/WVx1tcnvhAe2Tk9PPYf0HFrq6Wj/ IgOPbMPySoJIocJ/n3K+Z6Xk1YFWJlHGU1HmPOqCn2WgDEsomWTlniVd7Xi8 2zU7k6fHx9nDCv5tjiCsc1jEFVh9PGpk9UauC5NZuKKDhxrgTylE9Z+cb3nW LbKorroJGxm1LA1ZxoY8SCMWu4JnzFAy2orvWCzqvGIlXPCB3XMvANKS/axZ Hh/AsoaONbDh6y9tsnwawRLvxOsdBIHxzERuTFjGSpHDpe15Xc/uzL/+Am/g deIskhJQ5QqdWuD1eA7XcHHH8prnLMDjMjwnSHDRfPN6NkBYsaLg+QZXbNS5 ZVFVYzyuzTdr4KTDNP1yu3zSv89n+nSmL8OZvgon+jx81Jf+TJ9PZvrkeaCH s6U+Xz3i4h0t+vpkvviOEivScDx9Pn/Wb5/DxxutZFEGO7YT5QHoSNOyPcvs eXBpDb2e697D+lAxeaVF+4ifJK8xztZg2PdMEwUHfdc0T4LLkmUiSlgCLEvh hZU5y+Ci+XsBUYUXjU3HXJum2f0gXGPKY5GnfPNDxiUvKrgw1phDo9Hs0t6Z +jDuat9noT+Cvd01dbDdoffSOqhDmkUbOTLfcGMnEgZVtM7YiHTttTO0bXQb HTBt+6o1Mo82PL4ro2ILNl7f/w50+eXj7FswDx78x9+0Y86xFICCC7IuClFW wHIynmh58YbQ/LKLqi0UpYiZlKK8AYTFTiD2y7WIyqNUgEC2POAEuDSKmRYV O1L2l3MYB4vwkxrujyBFhCZwlIG91cXqw8jkWJoYQ4wOLWlFzNdkTOELBrbr OuNn2ApZQSVgOQlgXfJkw+DSv1tCwqXy/+rTmWiHzCiFWqptZVrbb6JOu/nA hAqdCnMGGNMefL/zO1ReUcXRMB2AJXiAhO15zG6Alz+xoMjbZoWqu7VtauTM R9+dvuWPlc/oehD6res3H9R75+pKmwRbl5VFLapOLjeml0Hw7EIwnVEAq1Jk WMHnVq2T1XflcS13kcSkUYlO5/4RBJh+FDIbgJpWaja3dMnEUZskrKNEv5Xo nUnU248utrc3ZmO4VO5ewVM4PvP3Uyx7Xfvkdi3Xf8sY6ikH0I2aNBvFp68Y fKJTwFWEm6K0oYGVVbI9WF3TNOihQ5QkJVhHZRsoLhJeOZaDjbI7sSec6SCJ GArxykqMWrzlhfU537QLuyiPNmyHdfeHOXJOl23yU+cvuXjNIUb8wuWe5Yko iTutPvYm1MJ3s29aV2Rk2G1zYJFybKMXKyG3fB3BSiyDybBPuOtM0BSmHcaf gGdZH5BHJpx/YuIdZmkSq5KaTaDvITBKDLbIG3nFNOabk5odevaV5x4k+LRb lDc4xReMZ5QhsycHDPuGE1yJHSTh7CRk/4XQy7rx5oUdFBt8SAFc8oHp2lcf HfPILy/94AoaUIy2gvvWRAvXBvHKvlZIRXvL0LBhLrAJtDL2Z6GGYO4ynrCl QOLUjzEMpqAoiQxhZ8XajBVTIA2dhW6tQpekwAW2CVyJqAXg2jrFn5PnUl07 PGBEdnRpKTJ2c76LluEL0veel1WNDbSVkm3fQZDZpnmjSS7Ms9wNVO5SdUW3 kcV1y3y3jhojqA4FIsPr9UyfVjCdTWesKUOk60CO5YizxJpXu6igUQobzrrZ RZOkhfkloXb98sTytOf80V5RxGce95XH/cbj/slj991j0hjBMexUzZLhbDib LI1laBsPwXj8bXZFvk4Wc5xAAvxXpbLVvA1uFw1HWJ6hfptBAqdFHHu2Iku0 rKgoI5v2jKJUXbNpRwWyPN63ESEOKcu6qDpJiWNmrq6B5/Az9aiMEMQZcEOc 2SgKqaBYZ5JBgSiXOBFiu8XRkMg+OLbqc6VY4Xex/OZ0Qv8NLn+b3/at4Vlp 9BwCWc/p6/QcqPehimhP1a91imtsNR2jiSwSyjt940zqeD1lVhWI80GOyM5S jRqIaajzQacDL1lNTV7N2yI/tu/4qGH/bY0RppFXOLP/ooCoGJdyBKzQgiXG NX7BzKc8a7sjyXISZgmWKsmeRiVsHXXGOutIIvzwA+AVjSuTLRB1yMRmQysZ Bp9GG2z+OLC1h0gDWwKOoWuaKdKoziotUlwTjOedqT/1O7bnDkzDn3oL37WR BfyV33HJ/AsFsOnUEppO3uh61tCdY2vE+XfQ8wYmZb8SpbzCjxnHtV2IDxnW N/brLXImvnkOhMZKhx5y1dgIGyuIXtSThqInE70rENj4DVFj23vCccFxtAly bqWmhyC8x55p/m7lNVEUXXCcSRfT2Y9w9hDOfoyDO+jA00Owwrus8DMoWDyA RG6+9vAm8bU9pD8/rzFGWALU89x/YmXwf6zEKrSTace23ZnR7/YwnpPp42Le IKANqPUxoEqFegu4GLz7sSHh8vhGAbUH92PEXJqyUqcpqtU4zVKNLtEgwgtP ftTpOT3K+XXCxQhoqNTVtL4XWb1jkLE9y2QrNGfxNsq5xLGZ0acrAQuqMjqc 9hOc5hvzeBfLNnc7SPAmBJMYms8SHQeKTCDmklMJqMmC5/i5UtG+zJBIzT/d tSgTP3AgxnkGRSr81BR1Ba8RV1lH/DffAcRcGjmtkK8mrrbDIfoRFtKOtEmU E3Mjg4k4qlg7Y2G/cYljbDfV/gfFx6CYzg8AAA== --0-1198591489-940184693=:603-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 12:33: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 0E2801509D for ; Sun, 17 Oct 1999 12:32:57 -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.3) with ESMTP id MAA34373; Sun, 17 Oct 1999 12:32:33 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Message-ID: <380A245B.84B593E1@MexComUSA.NET> Date: Sun, 17 Oct 1999 12:32:44 -0700 From: Edwin Culp Organization: EnContacto.NET X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Michael Reifenberger Cc: FreeBSD-Current Subject: Re: -current problems with the lates pccard changes? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Reifenberger wrote: > Hi, > after upgrading my Tecra-8000 to -current as of -now I get the attached output > during boot. > And the ep0 driver doesnt get attached with the following message: > Cannot allocate ports 0x240-0x24f I have been getting the same with yesterday's and today's world but since I have another problem with ed0 I was blaming it on some of my tests with the driver. Friday's world is working fin for me except for a change especially for ed0. ciao, ed > > > Does the output look normal? Particularly the muliple attaches worries me. > > Does anyone else see this? > > BTW: I have machdep.pccard.pcic_irq="11" in loader.conf.local if it matters. > > Bye! > ---- > Michael Reifenberger > Plaut Software GmbH, R/3 Basis > > ------------------------------------------------------------------------ > Name: dmesg.out.gz > dmesg.out.gz Type: unspecified type (APPLICATION/octet-stream) > Encoding: BASE64 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 12:44:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from gate.etoile.net (gate.etoile.net [205.210.70.252]) by hub.freebsd.org (Postfix) with ESMTP id 4A50C150BE for ; Sun, 17 Oct 1999 12:43:33 -0700 (PDT) (envelope-from dana@etoile.net) Received: from etoile.net (dana@celeron.etoile.net [205.210.70.205]) by gate.etoile.net (8.9.2.Beta4/8.9.2.Beta4) with ESMTP id MAA07981 for ; Sun, 17 Oct 1999 12:43:16 -0700 (PDT) Message-ID: <380A26D6.41B6E243@etoile.net> Date: Sun, 17 Oct 1999 12:43:18 -0700 From: Dana Huggard X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Current Development Subject: make world failing on 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've been trying a make world for the last few days. I finally removed my src tree and CVSup'ed the complete tree again but it i still failing in the same place. I don't know how to get past this. Can anyone offer some enlightenment? :) Thanks. Output of make world: ===> f77doc /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH /usr/obj/usr/src/gnu/lib/libgcc/GRTAGS /usr/obj/usr/src/gnu/lib/libgcc/GSYMS /usr/obj/usr/src/gnu/lib/libgcc/GTAGS echo '#include ' > config.h echo '#include ' >> config.h echo '#include "i386/xm-i386.h"' > tconfig.h echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c *** Signal 12 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Script done, output file is /data/system/builds/1710991157/build_world.out To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 13: 7:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from kiwi.mail.easynet.net (kiwi.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (Postfix) with ESMTP id B5B7D14A2D; Sun, 17 Oct 1999 13:07:25 -0700 (PDT) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (alister.w.easynet.co.uk [212.212.251.86]) by kiwi.mail.easynet.net (Postfix) with ESMTP id 40423DAF84; Sun, 17 Oct 1999 21:07:23 +0100 (BST) Message-ID: <380A3C38.8C4311E4@freenet.co.uk> Date: Sun, 17 Oct 1999 21:14:32 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-emulation@freebsd.org, freebsd-current@freebsd.org Subject: duplicate filenames under Linux emulation Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed that I often get duplicate filenames when running programs under Linux emulation. Attached below is a directory listing, in which the file bxutils-c.c is listed twice under Linux. I don't think the problem is ls(1) related, as I remember seeing duplicate names in file selection boxes as well, therefore it must be a bug in the mapping of the getdirentries(2) syscall. current:~/prog/motif/GUITests/Test2$ ls -l total 237 -rw-r--r-- 1 ak users 5626 Oct 17 20:38 #uil.uil# -rw-r--r-- 1 ak users 1127 Oct 17 20:23 Imakefile -rw-r--r-- 1 ak users 20103 Oct 17 20:28 Makefile -rw-r--r-- 1 ak users 495 Oct 17 20:23 app-defaults -rw-r--r-- 1 ak users 102042 Oct 17 20:23 bxutils-c.c -rw-r--r-- 1 ak users 23244 Oct 17 20:34 bxutils-c.o -rw-r--r-- 1 ak users 1822 Oct 17 20:27 callbacks-c.c -rw-r--r-- 1 ak users 896 Oct 17 20:34 callbacks-c.o -rw-r--r-- 1 ak users 8382 Oct 17 20:39 creation-c.c -rw-r--r-- 1 ak users 8156 Oct 17 20:23 creation-c.c~ -rw-r--r-- 1 ak users 4728 Oct 17 20:34 creation-c.o -rwxr-xr-x 1 ak users 32275 Oct 17 20:34 main-c -rw-r--r-- 1 ak users 3416 Oct 17 20:23 main-c.c -rw-r--r-- 1 ak users 1588 Oct 17 20:34 main-c.o -rw-r--r-- 1 ak users 1188 Oct 17 20:23 makefile-c -rw-r--r-- 1 ak users 7198 Oct 17 20:20 uil.uil current:~/prog/motif/GUITests/Test2$ /compat/linux/bin/bash current:~/prog/motif/GUITests/Test2$ ls -l total 349 -rw-r--r-- 1 ak users 5626 Oct 17 20:38 #uil.uil# -rw-r--r-- 1 ak users 1127 Oct 17 20:23 Imakefile -rw-r--r-- 1 ak users 20103 Oct 17 20:28 Makefile -rw-r--r-- 1 ak users 495 Oct 17 20:23 app-defaults -rw-r--r-- 1 ak users 102042 Oct 17 20:23 bxutils-c.c -rw-r--r-- 1 ak users 102042 Oct 17 20:23 bxutils-c.c -rw-r--r-- 1 ak users 23244 Oct 17 20:34 bxutils-c.o -rw-r--r-- 1 ak users 1822 Oct 17 20:27 callbacks-c.c -rw-r--r-- 1 ak users 896 Oct 17 20:34 callbacks-c.o -rw-r--r-- 1 ak users 8382 Oct 17 20:39 creation-c.c -rw-r--r-- 1 ak users 8156 Oct 17 20:23 creation-c.c~ -rw-r--r-- 1 ak users 4728 Oct 17 20:34 creation-c.o -rwxr-xr-x 1 ak users 32275 Oct 17 20:34 main-c -rw-r--r-- 1 ak users 3416 Oct 17 20:23 main-c.c -rw-r--r-- 1 ak users 1588 Oct 17 20:34 main-c.o -rw-r--r-- 1 ak users 1188 Oct 17 20:23 makefile-c -rw-r--r-- 1 ak users 7198 Oct 17 20:20 uil.uil I would be happy to provide additional info. My kernel is -current as of 11 Oct: -r-xr-xr-x 1 root wheel 1804310 Oct 11 18:42 /kernel (the Linux module compiled in). Thanks, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 13:37:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from george.spottydogs.org (George.SpottyDogs.Org [209.31.147.130]) by hub.freebsd.org (Postfix) with ESMTP id A940014E84 for ; Sun, 17 Oct 1999 13:37:25 -0700 (PDT) (envelope-from mnewell@newell.arlington.va.us) Received: from localhost (mnewell@localhost) by george.spottydogs.org (8.9.3/8.9.3) with ESMTP id QAA01490 for ; Sun, 17 Oct 1999 16:38:53 -0400 (EDT) (envelope-from mnewell@newell.arlington.va.us) Date: Sun, 17 Oct 1999 16:38:53 -0400 (EDT) From: Mike Newell X-Sender: mnewell@george.spottydogs.org To: freebsd-current@freebsd.org Subject: Signal 12 during build of -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'm installing -current on a FreeBSD-3.3-stable system. I've done the sup (which succeeded with no problems). When I try the "make buildworld" I get "signal 12" crashes during the gcc lib build. In specific: -- echo '#include ' > config.h echo '#include ' >> config.h echo '#include "i386/xm-i386.h"' > tconfig.h echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c *** Signal 12 -- I tried searching the Web site archives for details, but I kept getting back "Web page is not accessible" messages. Help??? Thanks!! Mike PS - Are the mailing list archives available for download? My ISP (BA.NET DSL service) seriuosly sucks; I become unreachable for several hours periodically and apparently that's enough to drop me from the FreeBSD mailing lists. :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 13:43:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id 5666B14F23 for ; Sun, 17 Oct 1999 13:43:20 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id WAA23848 for ; Sun, 17 Oct 1999 22:43:20 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id WAA13549 for current@freebsd.org; Sun, 17 Oct 1999 22:43:19 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id WAA00805 for ; Sun, 17 Oct 1999 22:42:51 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sun, 17 Oct 1999 22:42:51 +0200 (CEST) From: Michael Reifenberger To: FreeBSD-Current Subject: -current crash Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1037762941-940192971=:784" 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-1037762941-940192971=:784 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I got the following crash since a couple of time since upgrading one machine to -current as of today. It seems to occurs during somewhat heavier diskaccess. Sorry no detailed backtrace for now because I deleted my kernel.debug since the last crash and dumping 256MB takes a long time... Does the crash trigger anything. SMP 2 cpus IdlePTD 3194880 initial pcb at 282c40 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 fault virtual address = 0xdeadc0e6 fault code = supervisor read, page not present instruction pointer = 0x8:0xc101891b stack pointer = 0x10:0xce004d3c frame pointer = 0x10:0xce004d4c 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 = 6296 (bash) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 boot() called on cpu#0 Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis --0-1037762941-940192971=:784 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="crash_bt.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="crash_bt.txt" R05VIGdkYiA0LjE4DQpDb3B5cmlnaHQgMTk5OCBGcmVlIFNvZnR3YXJlIEZv dW5kYXRpb24sIEluYy4NCkdEQiBpcyBmcmVlIHNvZnR3YXJlLCBjb3ZlcmVk IGJ5IHRoZSBHTlUgR2VuZXJhbCBQdWJsaWMgTGljZW5zZSwgYW5kIHlvdSBh cmUNCndlbGNvbWUgdG8gY2hhbmdlIGl0IGFuZC9vciBkaXN0cmlidXRlIGNv cGllcyBvZiBpdCB1bmRlciBjZXJ0YWluIGNvbmRpdGlvbnMuDQpUeXBlICJz aG93IGNvcHlpbmciIHRvIHNlZSB0aGUgY29uZGl0aW9ucy4NClRoZXJlIGlz IGFic29sdXRlbHkgbm8gd2FycmFudHkgZm9yIEdEQi4gIFR5cGUgInNob3cg d2FycmFudHkiIGZvciBkZXRhaWxzLg0KVGhpcyBHREIgd2FzIGNvbmZpZ3Vy ZWQgYXMgImkzODYtdW5rbm93bi1mcmVlYnNkIi4uLihubyBkZWJ1Z2dpbmcg c3ltYm9scyBmb3VuZCkuLi4NClNNUCAyIGNwdXMNCklkbGVQVEQgMzE5NDg4 MA0KaW5pdGlhbCBwY2IgYXQgMjgyYzQwDQpwYW5pY3N0cjogcGFnZSBmYXVs dA0KcGFuaWMgbWVzc2FnZXM6DQotLS0NCkZhdGFsIHRyYXAgMTI6IHBhZ2Ug ZmF1bHQgd2hpbGUgaW4ga2VybmVsIG1vZGUNCm1wX2xvY2sgPSAwMDAwMDAw MjsgY3B1aWQgPSAwOyBsYXBpYy5pZCA9IDAxMDAwMDAwDQpmYXVsdCB2aXJ0 dWFsIGFkZHJlc3MJPSAweGRlYWRjMGU2DQpmYXVsdCBjb2RlCQk9IHN1cGVy dmlzb3IgcmVhZCwgcGFnZSBub3QgcHJlc2VudA0KaW5zdHJ1Y3Rpb24gcG9p bnRlcgk9IDB4ODoweGMxMDE4OTFiDQpzdGFjayBwb2ludGVyCSAgICAgICAg PSAweDEwOjB4Y2UwMDRkM2MNCmZyYW1lIHBvaW50ZXIJICAgICAgICA9IDB4 MTA6MHhjZTAwNGQ0Yw0KY29kZSBzZWdtZW50CQk9IGJhc2UgMHgwLCBsaW1p dCAweGZmZmZmLCB0eXBlIDB4MWINCgkJCT0gRFBMIDAsIHByZXMgMSwgZGVm MzIgMSwgZ3JhbiAxDQpwcm9jZXNzb3IgZWZsYWdzCT0gaW50ZXJydXB0IGVu YWJsZWQsIHJlc3VtZSwgSU9QTCA9IDANCmN1cnJlbnQgcHJvY2VzcwkJPSA2 Mjk2IChiYXNoKQ0KaW50ZXJydXB0IG1hc2sJCT0gbm9uZSA8LSBTTVA6IFhY WA0KdHJhcCBudW1iZXIJCT0gMTINCnBhbmljOiBwYWdlIGZhdWx0DQptcF9s b2NrID0gMDAwMDAwMDI7IGNwdWlkID0gMDsgbGFwaWMuaWQgPSAwMTAwMDAw MA0KYm9vdCgpIGNhbGxlZCBvbiBjcHUjMA0KDQpzeW5jaW5nIGRpc2tzLi4u IDEwIDIgMSAxIDEgMSAxIDEgMSAxIDEgMSAxIDEgMSAxIDEgMSAxIDEgZ2l2 aW5nIHVwDQoNCmR1bXBpbmcgdG8gZGV2ICNkYS8weDIwMDAxLCBvZmZzZXQg NTQwNjk2DQpkdW1wIDI1NSAyNTQgMjUzIDI1MiAyNTEgMjUwIDI0OSAyNDgg MjQ3IDI0NiAyNDUgMjQ0IDI0MyAyNDIgMjQxIDI0MCAyMzkgMjM4IDIzNyAy MzYgMjM1IDIzNCAyMzMgMjMyIDIzMSAyMzAgMjI5IDIyOCAyMjcgMjI2IDIy NSAyMjQgMjIzIDIyMiAyMjEgMjIwIDIxOSAyMTggMjE3IDIxNiAyMTUgMjE0 IDIxMyAyMTIgMjExIDIxMCAyMDkgMjA4IDIwNyAyMDYgMjA1IDIwNCAyMDMg MjAyIDIwMSAyMDAgMTk5IDE5OCAxOTcgMTk2IDE5NSAxOTQgMTkzIDE5MiAx OTEgMTkwIDE4OSAxODggMTg3IDE4NiAxODUgMTg0IDE4MyAxODIgMTgxIDE4 MCAxNzkgMTc4IDE3NyAxNzYgMTc1IDE3NCAxNzMgMTcyIDE3MSAxNzAgMTY5 IDE2OCAxNjcgMTY2IDE2NSAxNjQgMTYzIDE2MiAxNjEgMTYwIDE1OSAxNTgg MTU3IDE1NiAxNTUgMTU0IDE1MyAxNTIgMTUxIDE1MCAxNDkgMTQ4IDE0NyAx NDYgMTQ1IDE0NCAxNDMgMTQyIDE0MSAxNDAgMTM5IDEzOCAxMzcgMTM2IDEz NSAxMzQgMTMzIDEzMiAxMzEgMTMwIDEyOSAxMjggMTI3IDEyNiAxMjUgMTI0 IDEyMyAxMjIgMTIxIDEyMCAxMTkgMTE4IDExNyAxMTYgMTE1IDExNCAxMTMg MTEyIDExMSAxMTAgMTA5IDEwOCAxMDcgMTA2IDEwNSAxMDQgMTAzIDEwMiAx MDEgMTAwIDk5IDk4IDk3IDk2IDk1IDk0IDkzIDkyIDkxIDkwIDg5IDg4IDg3 IDg2IDg1IDg0IDgzIDgyIDgxIDgwIDc5IDc4IDc3IDc2IDc1IDc0IDczIDcy IDcxIDcwIDY5IDY4IDY3IDY2IDY1IDY0IDYzIDYyIDYxIDYwIDU5IDU4IDU3 IDU2IDU1IDU0IDUzIDUyIDUxIDUwIDQ5IDQ4IDQ3IDQ2IDQ1IDQ0IDQzIDQy IDQxIDQwIDM5IDM4IDM3IDM2IDM1IDM0IDMzIDMyIDMxIDMwIDI5IDI4IDI3 IDI2IDI1IDI0IDIzIDIyIDIxIDIwIDE5IDE4IDE3IDE2IDE1IDE0IDEzIDEy IDExIDEwIDkgOCA3IDYgNSA0IDMgMiAxIDAgDQotLS0NCiMwICAweGMwMTUy MzY4IGluIGJvb3QgKCkNCiMwICAweGMwMTUyMzY4IGluIGJvb3QgKCkNCiMx ICAweGMwMTUyNzQxIGluIHBhbmljICgpDQojMiAgMHhjMDIxMWI0MCBpbiB0 cmFwX2ZhdGFsICgpDQojMyAgMHhjMDIxMTdiMSBpbiB0cmFwX3BmYXVsdCAo KQ0KIzQgIDB4YzAyMTEzMTMgaW4gdHJhcCAoKQ0KIzUgIDB4YzEwMTg5MWIg aW4gPz8gKCkNCiM2ICAweGMxMDE4NzUyIGluID8/ICgpDQojNyAgMHhjMTAx ODU0ZSBpbiA/PyAoKQ0KIzggIDB4YzAxODZhNjYgaW4gc3BlY19zdHJhdGVn eSAoKQ0KIzkgIDB4YzAxODYwMWQgaW4gc3BlY192bm9wZXJhdGUgKCkNCiMx MCAweGMwMWJiMzUxIGluIHVmc192bm9wZXJhdGVzcGVjICgpDQojMTEgMHhj MDE3M2JmNyBpbiBicmVhZCAoKQ0KIzEyIDB4YzAxYWMwNWIgaW4gZmZzX3Vw ZGF0ZSAoKQ0KIzEzIDB4YzAxYjYwZDYgaW4gdWZzX2luYWN0aXZlICgpDQoj MTQgMHhjMDFiYjMyMSBpbiB1ZnNfdm5vcGVyYXRlICgpDQojMTUgMHhjMDE3 YmY4MSBpbiB2cmVsZSAoKQ0KIzE2IDB4YzAxODI1N2IgaW4gdm5fY2xvc2Ug KCkNCiMxNyAweGMwMTgyZGU4IGluIHZuX2Nsb3NlZmlsZSAoKQ0KIzE4IDB4 YzAxNGE4MWQgaW4gZmRyb3AgKCkNCiMxOSAweGMwMTRhN2QzIGluIGNsb3Nl ZiAoKQ0KIzIwIDB4YzAxNDllMGMgaW4gY2xvc2UgKCkNCiMyMSAweGMwMjEx ZGYxIGluIHN5c2NhbGwgKCkNCiMyMiAweDIwMGQ0NGYxIGluID8/ICgpDQoj MjMgMHg0MjFmNiBpbiA/PyAoKQ0KIzI0IDB4NDFlZWEgaW4gPz8gKCkNCiMy NSAweDQxMDlhIGluID8/ICgpDQojMjYgMHg0MTg5MyBpbiA/PyAoKQ0KIzI3 IDB4NDBhNjggaW4gPz8gKCkNCiMyOCAweDNiYzRjIGluID8/ICgpDQojMjkg MHgzYmE3MiBpbiA/PyAoKQ0KIzMwIDB4M2JhZTEgaW4gPz8gKCkNCiMzMSAw eDNiODU4IGluID8/ICgpDQojMzIgMHg1NWU1IGluID8/ICgpDQojMzMgMHg1 NTE2IGluID8/ICgpDQojMzQgMHg1ZDIxIGluID8/ICgpDQojMzUgMHg2NTg3 IGluID8/ICgpDQojMzYgMHg2MjI1IGluID8/ICgpDQojMzcgMHg0NWQxIGlu ID8/ICgpDQojMzggMHgzMzI0IGluID8/ICgpDQojMzkgMHgzM2QzIGluID8/ ICgpDQojNDAgMHgzMTQ2IGluID8/ICgpDQojNDEgMHgxYzJhIGluID8/ICgp DQojNDIgMHgxMDk2IGluID8/ICgpDQooa2dkYikgcXVpdA0K --0-1037762941-940192971=:784-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 13:50:42 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 D5F07150D2 for ; Sun, 17 Oct 1999 13:50:37 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA18141; Sun, 17 Oct 1999 13:50:28 -0700 Date: Sun, 17 Oct 1999 13:50:27 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Michael Reifenberger Cc: FreeBSD-Current Subject: Re: -current crash 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 Well, a DDB traceback would help. Failing that, at least what does 0xc101891b correspond to.... otherwise, it's all ENOGUESS.... On Sun, 17 Oct 1999, Michael Reifenberger wrote: > Hi, > I got the following crash since a couple of time since upgrading one machine to > -current as of today. It seems to occurs during somewhat heavier diskaccess. > Sorry no detailed backtrace for now because I deleted my kernel.debug since the > last crash and dumping 256MB takes a long time... > > Does the crash trigger anything. > > SMP 2 cpus > IdlePTD 3194880 > initial pcb at 282c40 > panicstr: page fault > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 > fault virtual address = 0xdeadc0e6 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc101891b > stack pointer = 0x10:0xce004d3c > frame pointer = 0x10:0xce004d4c > 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 = 6296 (bash) > interrupt mask = none <- SMP: XXX > trap number = 12 > panic: page fault > mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 > boot() called on cpu#0 > > > Bye! > ---- > Michael Reifenberger > Plaut Software GmbH, R/3 Basis > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 14: 9: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from guru.phone.net (guru.phone.net [216.240.39.120]) by hub.freebsd.org (Postfix) with SMTP id D4493150B6 for ; Sun, 17 Oct 1999 14:09:02 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 15753 invoked by uid 100); 17 Oct 1999 21:08:58 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Oct 1999 21:08:58 -0000 Date: Sun, 17 Oct 1999 14:08:58 -0700 (PDT) From: Mike Meyer To: freebsd-ports@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: make.conf options (was Re: package-like feature for the base distrib (was Re: FreeSSH)) In-Reply-To: <199910171630.MAA46571@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 Sun, 17 Oct 1999, Garrett Wollman wrote: ;->< said: ;-> ;->> This is going in the right direction, but here is a question (and I don't ;->> have the answer). Is it so much more easier to create new compile time ;->> directive than to go the extra step and use packages where they are ;->> available ? For example "bind8" is available as a package. Why not have the ;->> base install process use that instead of using its own source ? ;-> ;->Because one of the fundamental principles is that a default ;->installation, with no third-party packages, should still be a complete ;->system, and -- most importantly -- be able to regenerate itself ;->precisely from source. Hence, the default system needs to contain ;->*an* MTA (not necessarily sendmail, but that's not a question we want ;->to reopen), and *a* name server (not necessarily bind, but there are ;->no other choices). Much better put than I was going to do it. Is it possible to arrange things so that this principle can be adhered to, while at the same time making such replaceable components easier to deal with than disabling part of the default installation and installing a package? For instance, do we have to consider anything in a package as "third-party" software? Why can't we use the port/package technology on things that are part of FreeBSD? That way, instead of a compile-time NOFOO option, you have a compile-time FOO= option. The build process would have to be extended to rebuild packages (a good thing in any case). The installation process would need to be able to add "port" source based on the package name. We'd probably want another port category (FreeBsd?) to identify ports that aren't third-party software. Looking back at your principle, the default installation would include nothing that wasn't in the FreeBSD category. So it has no third-party packages. The built system - whether default or not - would be able to regenerate itself precisely from sources. ; Sun, 17 Oct 1999 14:58:16 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id XAA23963; Sun, 17 Oct 1999 23:58:15 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id XAA13639; Sun, 17 Oct 1999 23:58:15 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id XAA00976; Sun, 17 Oct 1999 23:58:15 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sun, 17 Oct 1999 23:58:15 +0200 (CEST) From: Michael Reifenberger To: Matthew Jacob Cc: FreeBSD-Current Subject: Re: -current crash 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, 17 Oct 1999, Matthew Jacob wrote: ... > Well, a DDB traceback would help. Failing that, at least what does > 0xc101891b correspond to.... otherwise, it's all ENOGUESS.... Next try, next crash. No problem. Easy crashing :-) I tried to find the address 0xc101891b using nm(1) but can't seem to find it. Whats the preffered method for finding? GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... SMP 2 cpus IdlePTD 3194880 initial pcb at 282c20 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 fault virtual address = 0xdeadc0e6 fault code = supervisor read, page not present instruction pointer = 0x8:0xc101e91b stack pointer = 0x10:0xce042cbc frame pointer = 0x10:0xce042ccc 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 = 16328 (dbv) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 syncing disks... 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 done dumping to dev #da/0x20001, offset 540696 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 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:280 280 dumppcb.pcb_cr3 = rcr3(); #0 boot (howto=256) at ../../kern/kern_shutdown.c:280 #1 0xc015275d in panic (fmt=0xc02520cf "page fault") at ../../kern/kern_shutdown.c:530 #2 0xc0211b30 in trap_fatal (frame=0xce042c7c, eva=3735929062) at ../../i386/i386/trap.c:907 #3 0xc02117a1 in trap_pfault (frame=0xce042c7c, usermode=0, eva=3735929062) at ../../i386/i386/trap.c:800 #4 0xc0211303 in trap (frame={tf_fs = -1057095656, tf_es = -1052377072, tf_ds = -1056112624, tf_edi = -559038242, tf_esi = -1052325860, tf_ebp = -838587188, tf_isp = -838587224, tf_ebx = -1056083712, tf_edx = -1070995904, tf_ecx = 16777217, tf_eax = -16162, tf_trapno = 12, tf_err = 0, tf_eip = -1056839397, tf_cs = 8, tf_eflags = 66182, tf_esp = -1055894172, tf_ss = -969961680}) at ../../i386/i386/trap.c:426 #5 0xc101e91b in ?? () #6 0xc101e752 in ?? () #7 0xc101e54e in ?? () #8 0xc0186a82 in spec_strategy (ap=0xce042d4c) at ../../miscfs/specfs/spec_vnops.c:686 #9 0xc0186039 in spec_vnoperate (ap=0xce042d4c) at ../../miscfs/specfs/spec_vnops.c:133 #10 0xc01bb371 in ufs_vnoperatespec (ap=0xce042d4c) at ../../ufs/ufs/ufs_vnops.c:2313 #11 0xc01bad70 in ufs_strategy (ap=0xce042dd4) at vnode_if.h:940 #12 0xc01bb341 in ufs_vnoperate (ap=0xce042dd4) at ../../ufs/ufs/ufs_vnops.c:2295 #13 0xc0177e06 in cluster_read (vp=0xce16f380, filesize=1258299392, lblkno=137260, size=8192, cred=0x0, totread=8192, seqcount=127, bpp=0xce042e70) at vnode_if.h:940 #14 0xc01b4517 in ffs_read (ap=0xce042e98) at ../../ufs/ufs/ufs_readwrite.c:249 #15 0xc0182800 in vn_read (fp=0xc121cac0, uio=0xce042ee8, cred=0xc1224c80, flags=0, p=0xcdfc8500) at vnode_if.h:330 #16 0xc015fdf4 in dofileread (p=0xcdfc8500, fp=0xc121cac0, fd=4, buf=0x28418cd0, nbyte=8192, offset=-1, flags=0) at ../../sys/file.h:135 #17 0xc015fcfb in read (p=0xcdfc8500, uap=0xce042f80) at ../../kern/sys_generic.c:110 #18 0xc0211de1 in syscall (frame={tf_fs = 65583, tf_es = 47, tf_ds = -1078001617, tf_edi = 137217, tf_esi = 0, tf_ebp = -1077947392, tf_isp = -838586412, tf_ebx = 4, tf_edx = 8192, tf_ecx = 675384528, tf_eax = 3, tf_trapno = 7, tf_err = 2, tf_eip = 674927924, tf_cs = 31, tf_eflags = 658, tf_esp = -1077947420, tf_ss = 47}) at ../../i386/i386/trap.c:1056 #19 0xc01fe9b1 in Xint0x80_syscall () (kgdb) quit Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 15: 4:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 6170814C8C for ; Sun, 17 Oct 1999 15:04:37 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id AAA23902; Mon, 18 Oct 1999 00:00:41 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id AAA53018; Mon, 18 Oct 1999 00:05:27 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id AAA24223; Mon, 18 Oct 1999 00:05:40 +0200 (CEST) (envelope-from ticso) Date: Mon, 18 Oct 1999 00:05:39 +0200 From: Bernd Walter To: Michael Reifenberger Cc: FreeBSD-Current Subject: Re: -current crash Message-ID: <19991018000538.A24204@cicely8.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Michael Reifenberger on Sun, Oct 17, 1999 at 10:42:51PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 17, 1999 at 10:42:51PM +0200, Michael Reifenberger wrote: [...] > #3 0xc02117b1 in trap_pfault () > #4 0xc0211313 in trap () > #5 0xc101891b in ?? () > #6 0xc1018752 in ?? () > #7 0xc101854e in ?? () > #8 0xc0186a66 in spec_strategy () > #9 0xc018601d in spec_vnoperate () [...] What kind of modules were you running? Are these in sync with the kernel? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 15: 8:20 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 62E2114DFD for ; Sun, 17 Oct 1999 15:08:15 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA18439; Sun, 17 Oct 1999 15:08:11 -0700 Date: Sun, 17 Oct 1999 15:08:10 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Michael Reifenberger Cc: FreeBSD-Current Subject: Re: -current crash 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 Doesn't tell *me* a lot.... maybe a broken driver that's a KLD? It looks like something from spec_strategy is being called that's not in the /kernel space- could be a KLD- are your KLDs up to date for the new kernel? Like, is this vinum perhaps? > On Sun, 17 Oct 1999, Matthew Jacob wrote: > ... > > Well, a DDB traceback would help. Failing that, at least what does > > 0xc101891b correspond to.... otherwise, it's all ENOGUESS.... > Next try, next crash. No problem. Easy crashing :-) > > I tried to find the address 0xc101891b using nm(1) but can't seem to find it. > Whats the preffered method for finding? > > GNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"... > SMP 2 cpus > IdlePTD 3194880 > initial pcb at 282c20 > panicstr: page fault > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 > fault virtual address = 0xdeadc0e6 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc101e91b > stack pointer = 0x10:0xce042cbc > frame pointer = 0x10:0xce042ccc > 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 = 16328 (dbv) > interrupt mask = none <- SMP: XXX > trap number = 12 > panic: page fault > mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 > boot() called on cpu#1 > > syncing disks... 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 done > > dumping to dev #da/0x20001, offset 540696 > 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 > --- > #0 boot (howto=256) at ../../kern/kern_shutdown.c:280 > 280 dumppcb.pcb_cr3 = rcr3(); > #0 boot (howto=256) at ../../kern/kern_shutdown.c:280 > #1 0xc015275d in panic (fmt=0xc02520cf "page fault") at ../../kern/kern_shutdown.c:530 > #2 0xc0211b30 in trap_fatal (frame=0xce042c7c, eva=3735929062) at ../../i386/i386/trap.c:907 > #3 0xc02117a1 in trap_pfault (frame=0xce042c7c, usermode=0, eva=3735929062) > at ../../i386/i386/trap.c:800 > #4 0xc0211303 in trap (frame={tf_fs = -1057095656, tf_es = -1052377072, tf_ds = -1056112624, > tf_edi = -559038242, tf_esi = -1052325860, tf_ebp = -838587188, tf_isp = -838587224, > tf_ebx = -1056083712, tf_edx = -1070995904, tf_ecx = 16777217, tf_eax = -16162, > tf_trapno = 12, tf_err = 0, tf_eip = -1056839397, tf_cs = 8, tf_eflags = 66182, > tf_esp = -1055894172, tf_ss = -969961680}) at ../../i386/i386/trap.c:426 > #5 0xc101e91b in ?? () > #6 0xc101e752 in ?? () > #7 0xc101e54e in ?? () > #8 0xc0186a82 in spec_strategy (ap=0xce042d4c) at ../../miscfs/specfs/spec_vnops.c:686 > #9 0xc0186039 in spec_vnoperate (ap=0xce042d4c) at ../../miscfs/specfs/spec_vnops.c:133 > #10 0xc01bb371 in ufs_vnoperatespec (ap=0xce042d4c) at ../../ufs/ufs/ufs_vnops.c:2313 > #11 0xc01bad70 in ufs_strategy (ap=0xce042dd4) at vnode_if.h:940 > #12 0xc01bb341 in ufs_vnoperate (ap=0xce042dd4) at ../../ufs/ufs/ufs_vnops.c:2295 > #13 0xc0177e06 in cluster_read (vp=0xce16f380, filesize=1258299392, lblkno=137260, size=8192, > cred=0x0, totread=8192, seqcount=127, bpp=0xce042e70) at vnode_if.h:940 > #14 0xc01b4517 in ffs_read (ap=0xce042e98) at ../../ufs/ufs/ufs_readwrite.c:249 > #15 0xc0182800 in vn_read (fp=0xc121cac0, uio=0xce042ee8, cred=0xc1224c80, flags=0, > p=0xcdfc8500) at vnode_if.h:330 > #16 0xc015fdf4 in dofileread (p=0xcdfc8500, fp=0xc121cac0, fd=4, buf=0x28418cd0, nbyte=8192, > offset=-1, flags=0) at ../../sys/file.h:135 > #17 0xc015fcfb in read (p=0xcdfc8500, uap=0xce042f80) at ../../kern/sys_generic.c:110 > #18 0xc0211de1 in syscall (frame={tf_fs = 65583, tf_es = 47, tf_ds = -1078001617, > tf_edi = 137217, tf_esi = 0, tf_ebp = -1077947392, tf_isp = -838586412, tf_ebx = 4, > tf_edx = 8192, tf_ecx = 675384528, tf_eax = 3, tf_trapno = 7, tf_err = 2, > tf_eip = 674927924, tf_cs = 31, tf_eflags = 658, tf_esp = -1077947420, tf_ss = 47}) > at ../../i386/i386/trap.c:1056 > #19 0xc01fe9b1 in Xint0x80_syscall () > (kgdb) quit > > Bye! > ---- > Michael Reifenberger > Plaut Software GmbH, R/3 Basis > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 15:16:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id AF00B14DFD for ; Sun, 17 Oct 1999 15:16:15 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id AAA24013; Mon, 18 Oct 1999 00:16:14 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id AAA13696; Mon, 18 Oct 1999 00:16:14 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id AAA01022; Mon, 18 Oct 1999 00:16:08 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Mon, 18 Oct 1999 00:16:08 +0200 (CEST) From: Michael Reifenberger To: Bernd Walter Cc: FreeBSD-Current Subject: Re: -current crash In-Reply-To: <19991018000538.A24204@cicely8.cicely.de> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-249161613-940198568=:930" 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-249161613-940198568=:930 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 18 Oct 1999, Bernd Walter wrote: ... > What kind of modules were you running? (nullum)(root)# kldstat Id Refs Address Size Name 1 7 0xc0100000 1eb518 kernel 2 1 0xc02ec000 cdbc bktr.ko 3 1 0xc1011000 c3000 vinum.ko 4 1 0xc1111000 6000 procfs.ko 5 1 0xc1118000 8000 if_xl.ko 6 1 0xc1121000 7000 miibus.ko 7 1 0xc131e000 4c000 nfs.ko > Are these in sync with the kernel? Yes. Configuration hasnt changed for weeks. boottext is attached. Softupdates is on on all FS. (Wasn't a problem so far) (nullum)(root)# mount /dev/da0s1a on / (ufs, local, soft-updates, writes: sync 5 async 274) /dev/da0s1d on /usr (ufs, NFS exported, local, soft-updates, writes: sync 172 async 5230) /dev/vinum/data on /mnt/data (ufs, NFS exported, local, soft-updates, writes: sync 2 async 0) /dev/vinum/oracle on /oracle (ufs, NFS exported, local, soft-updates, writes: sync 2 async 0) /dev/vinum/sapdaten on /oracle/NIL/sapdaten (ufs, local, soft-updates, writes: sync 2 async 0) /dev/vinum/sapmnt on /sapmnt (ufs, local, soft-updates, writes: sync 2 async 0) /dev/vinum/usr_sap on /usr/sap (ufs, NFS exported, local, soft-updates, writes: sync 2 async 0) procfs on /proc (procfs, local) Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis --0-249161613-940198568=:930 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dmesg.txt" T2N0IDE3IDE1OjEyOjE3IG51bGx1bSAva2VybmVsOiBDb3B5cmlnaHQgKGMp IDE5OTItMTk5OSBUaGUgRnJlZUJTRCBQcm9qZWN0Lg0KT2N0IDE3IDE1OjEy OjE3IG51bGx1bSAva2VybmVsOiBDb3B5cmlnaHQgKGMpIDE5ODIsIDE5ODYs IDE5ODksIDE5OTEsIDE5OTMNCk9jdCAxNyAxNToxMjoxNyBudWxsdW0gL2tl cm5lbDogVGhlIFJlZ2VudHMgb2YgdGhlIFVuaXZlcnNpdHkgb2YgQ2FsaWZv cm5pYS4gQWxsIHJpZ2h0cyByZXNlcnZlZC4NCk9jdCAxNyAxNToxMjoxNyBu dWxsdW0gL2tlcm5lbDogRnJlZUJTRCA0LjAtQ1VSUkVOVCAjMDogU3VuIE9j dCAxNyAxNTowNjo0MCBDRVNUIDE5OTkNCk9jdCAxNyAxNToxMjoxNyBudWxs dW0gL2tlcm5lbDogcm9vdEBudWxsdW0ucGxhdXQuZGU6L3Vzci9zcmMvc3lz L2NvbXBpbGUvbnVsbHVtDQpPY3QgMTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJu ZWw6IFRpbWVjb3VudGVyICJpODI1NCIgIGZyZXF1ZW5jeSAxMTkzMTgyIEh6 DQpPY3QgMTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6IENQVTogUGVudGl1 bSBJSUkvWGVvbiAoNDUxLjAyLU1IeiA2ODYtY2xhc3MgQ1BVKQ0KT2N0IDE3 IDE1OjEyOjE3IG51bGx1bSAva2VybmVsOiBPcmlnaW4gPSAiR2VudWluZUlu dGVsIiAgSWQgPSAweDY3MiAgU3RlcHBpbmcgPSAyDQpPY3QgMTcgMTU6MTI6 MTcgbnVsbHVtIC9rZXJuZWw6IEZlYXR1cmVzPTB4MzgzZmJmZjxGUFUsVk1F LERFLFBTRSxUU0MsTVNSLFBBRSxNQ0UsQ1g4LEFQSUMsU0VQLE1UUlIsUEdF LE1DQSxDTU9WLFBBVCxQU0UzNixNTVgsRlhTUixYTU0+DQpPY3QgMTcgMTU6 MTI6MTcgbnVsbHVtIC9rZXJuZWw6IHJlYWwgbWVtb3J5ICA9IDI2ODQyMzE2 OCAoMjYyMTMySyBieXRlcykNCk9jdCAxNyAxNToxMjoxNyBudWxsdW0gL2tl cm5lbDogY29uZmlnPiAjZmxhZ3Mgd2RjMCAweGEwZmZhMGZmDQpPY3QgMTcg MTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6IEludmFsaWQgY29tbWFuZCBvciBz eW50YXguICBUeXBlIGA/JyBmb3IgaGVscC4NCk9jdCAxNyAxNToxMjoxNyBu dWxsdW0gL2tlcm5lbDogY29uZmlnPiAjZmxhZ3Mgd2RjMSAweGEwZmZhMGZm DQpPY3QgMTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6IEludmFsaWQgY29t bWFuZCBvciBzeW50YXguICBUeXBlIGA/JyBmb3IgaGVscC4NCk9jdCAxNyAx NToxMjoxNyBudWxsdW0gL2tlcm5lbDogY29uZmlnPiAjaXJxIGlzaWMwIDEw DQpPY3QgMTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6IEludmFsaWQgY29t bWFuZCBvciBzeW50YXguICBUeXBlIGA/JyBmb3IgaGVscC4NCk9jdCAxNyAx NToxMjoxNyBudWxsdW0gL2tlcm5lbDogY29uZmlnPiAjcG5wIDEgMCBiaW9z IGVuYWJsZSBwb3J0MCAweDIyMCBpcnEwIDUgZHJxMCAxIGRycTEgMw0KT2N0 IDE3IDE1OjEyOjE3IG51bGx1bSAva2VybmVsOiBJbnZhbGlkIGNvbW1hbmQg b3Igc3ludGF4LiAgVHlwZSBgPycgZm9yIGhlbHAuDQpPY3QgMTcgMTU6MTI6 MTcgbnVsbHVtIC9rZXJuZWw6IGNvbmZpZz4gI3BucCAxIDAgYmlvcyBlbmFi bGUgcG9ydDAgMHhkODAgaXJxMCAxMQ0KT2N0IDE3IDE1OjEyOjE3IG51bGx1 bSAva2VybmVsOiBJbnZhbGlkIGNvbW1hbmQgb3Igc3ludGF4LiAgVHlwZSBg PycgZm9yIGhlbHAuDQpPY3QgMTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6 IGNvbmZpZz4gcG5wIDEgMSBvcyBlbmFibGUgaXJxMCA1IGRycTAgMSBwb3J0 MCAweDIyMA0KT2N0IDE3IDE1OjEyOjE3IG51bGx1bSAva2VybmVsOiBJbnZh bGlkIGNvbW1hbmQgb3Igc3ludGF4LiAgVHlwZSBgPycgZm9yIGhlbHAuDQpP Y3QgMTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6IGNvbmZpZz4gI2lvc2l6 IG5weDAgMjYyMTQ0DQpPY3QgMTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6 IEludmFsaWQgY29tbWFuZCBvciBzeW50YXguICBUeXBlIGA/JyBmb3IgaGVs cC4NCk9jdCAxNyAxNToxMjoxNyBudWxsdW0gL2tlcm5lbDogY29uZmlnPiBx dWl0DQpPY3QgMTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6IGF2YWlsIG1l bW9yeSA9IDI1NzIyNDcwNCAoMjUxMTk2SyBieXRlcykNCk9jdCAxNyAxNTox MjoxNyBudWxsdW0gL2tlcm5lbDogUHJvZ3JhbW1pbmcgMjQgcGlucyBpbiBJ T0FQSUMgIzANCk9jdCAxNyAxNToxMjoxNyBudWxsdW0gL2tlcm5lbDogRnJl ZUJTRC9TTVA6IE11bHRpcHJvY2Vzc29yIG1vdGhlcmJvYXJkDQpPY3QgMTcg MTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6IGNwdTAgKEJTUCk6IGFwaWMgaWQ6 ICAxLCB2ZXJzaW9uOiAweDAwMDQwMDExLCBhdCAweGZlZTAwMDAwDQpPY3Qg MTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6IGNwdTEgKEFQKTogIGFwaWMg aWQ6ICAwLCB2ZXJzaW9uOiAweDAwMDQwMDExLCBhdCAweGZlZTAwMDAwDQpP Y3QgMTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6IGlvMCAoQVBJQyk6IGFw aWMgaWQ6ICAyLCB2ZXJzaW9uOiAweDAwMTcwMDExLCBhdCAweGZlYzAwMDAw DQpPY3QgMTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6IFByZWxvYWRlZCBl bGYga2VybmVsICJrZXJuZWwiIGF0IDB4YzAyZmEwMDAuDQpPY3QgMTcgMTU6 MTI6MTcgbnVsbHVtIC9rZXJuZWw6IFByZWxvYWRlZCB1c2VyY29uZmlnX3Nj cmlwdCAiL2Jvb3Qva2VybmVsLmNvbmYiIGF0IDB4YzAyZmEwOWMuDQpPY3Qg MTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6IFByZWxvYWRlZCBlbGYgbW9k dWxlICJia3RyLmtvIiBhdCAweGMwMmZhMGVjLg0KT2N0IDE3IDE1OjEyOjE3 IG51bGx1bSAva2VybmVsOiBWRVNBOiB2Mi4wLCA4MTkyayBtZW1vcnksIGZs YWdzOjB4MSwgbW9kZSB0YWJsZToweGMwMjljMmMyICgxMDAwMDIyKQ0KT2N0 IDE3IDE1OjEyOjE3IG51bGx1bSAva2VybmVsOiBWRVNBOiBNYXRyb3ggR3Jh cGhpY3MgSW5jLg0KT2N0IDE3IDE1OjEyOjE3IG51bGx1bSAva2VybmVsOiBQ ZW50aXVtIFBybyBNVFJSIHN1cHBvcnQgZW5hYmxlZA0KT2N0IDE3IDE1OjEy OjE3IG51bGx1bSAva2VybmVsOiBucHgwOiA8bWF0aCBwcm9jZXNzb3I+IG9u IG1vdGhlcmJvYXJkDQpPY3QgMTcgMTU6MTI6MTcgbnVsbHVtIC9rZXJuZWw6 IG5weDA6IElOVCAxNiBpbnRlcmZhY2UNCk9jdCAxNyAxNToxMjoxNyBudWxs dW0gL2tlcm5lbDogcGNpYjA6IDxJbnRlbCA4MjQ0M0JYICg0NDAgQlgpIGhv c3QgdG8gUENJIGJyaWRnZT4gb24gbW90aGVyYm9hcmQNCk9jdCAxNyAxNTox MjoxNyBudWxsdW0gL2tlcm5lbDogcGNpMDogPFBDSSBidXM+IG9uIHBjaWIw DQpPY3QgMTcgMTU6MTI6MTggbnVsbHVtIC9rZXJuZWw6IHBjaWIxOiA8SW50 ZWwgODI0NDNCWCAoNDQwIEJYKSBQQ0ktUENJIChBR1ApIGJyaWRnZT4gYXQg ZGV2aWNlIDEuMCBvbiBwY2kwDQpPY3QgMTcgMTU6MTI6MTggbnVsbHVtIC9r ZXJuZWw6IHBjaTE6IDxQQ0kgYnVzPiBvbiBwY2liMQ0KT2N0IDE3IDE1OjEy OjE4IG51bGx1bSAva2VybmVsOiB2Z2EtcGNpMDogPE1hdHJveCBtb2RlbCAw NTIxIGdyYXBoaWNzIGFjY2VsZXJhdG9yPiBpcnEgMTYgYXQgZGV2aWNlIDAu MCBvbiBwY2kxDQpPY3QgMTcgMTU6MTI6MTggbnVsbHVtIC9rZXJuZWw6IGlz YWIwOiA8SW50ZWwgODIzNzFBQiBQQ0kgdG8gSVNBIGJyaWRnZT4gYXQgZGV2 aWNlIDQuMCBvbiBwY2kwDQpPY3QgMTcgMTU6MTI6MTggbnVsbHVtIC9rZXJu ZWw6IGlzYTA6IDxJU0EgYnVzPiBvbiBpc2FiMA0KT2N0IDE3IDE1OjEyOjE4 IG51bGx1bSAva2VybmVsOiBhdGEtcGNpMDogPEludGVsIFBJSVg0IElERSBj b250cm9sbGVyPiBhdCBkZXZpY2UgNC4xIG9uIHBjaTANCk9jdCAxNyAxNTox MjoxOCBudWxsdW0gL2tlcm5lbDogYXRhLXBjaTA6IEJ1c21hc3RlcmluZyBE TUEgbm90IGVuYWJsZWQNCk9jdCAxNyAxNToxMjoxOCBudWxsdW0gL2tlcm5l bDogdWhjaTA6IDxJbnRlbCA4MjM3MUFCL0VCIChQSUlYNCkgVVNCIGNvbnRy b2xsZXI+IGlycSAxOSBhdCBkZXZpY2UgNC4yIG9uIHBjaTANCk9jdCAxNyAx NToxMjoxOCBudWxsdW0gL2tlcm5lbDogdXNiMDogPEludGVsIDgyMzcxQUIv RUIgKFBJSVg0KSBVU0IgY29udHJvbGxlcj4gb24gdWhjaTANCk9jdCAxNyAx NToxMjoxOCBudWxsdW0gL2tlcm5lbDogdWh1YjA6IEludGVsIFVIQ0kgcm9v dCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRkciAxDQpPY3Qg MTcgMTU6MTI6MTggbnVsbHVtIC9rZXJuZWw6IHVodWIwOiAyIHBvcnRzIHdp dGggMiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZA0KT2N0IDE3IDE1OjEyOjE4 IG51bGx1bSAva2VybmVsOiBpbnRwbTA6IDxJbnRlbCA4MjM3MUFCIFBvd2Vy IG1hbmFnZW1lbnQgY29udHJvbGxlcj4gYXQgZGV2aWNlIDQuMyBvbiBwY2kw DQpPY3QgMTcgMTU6MTI6MTggbnVsbHVtIC9rZXJuZWw6IGludHBtMDogQ291 bGQgbm90IGFsbG9jYXRlIEJ1cyBzcGFjZQ0KT2N0IDE3IDE1OjEyOjE4IG51 bGx1bSAva2VybmVsOiBkZXZpY2VfcHJvYmVfYW5kX2F0dGFjaDogaW50cG0w IGF0dGFjaCByZXR1cm5lZCA2DQpPY3QgMTcgMTU6MTI6MTggbnVsbHVtIC9r ZXJuZWw6IGFoYzA6IDxBZGFwdGVjIGFpYzc4OTAvOTEgVWx0cmEyIFNDU0kg YWRhcHRlcj4gaXJxIDE5IGF0IGRldmljZSA2LjAgb24gcGNpMA0KT2N0IDE3 IDE1OjEyOjE4IG51bGx1bSAva2VybmVsOiBhaGMwOiBhaWM3ODkwLzkxIFdp ZGUgQ2hhbm5lbCBBLCBTQ1NJIElkPTcsIDE2LzI1NSBTQ0JzDQpPY3QgMTcg MTU6MTI6MTggbnVsbHVtIC9rZXJuZWw6IHBjaTA6IHVua25vd24gY2FyZCAo dmVuZG9yPTB4MTBiNywgZGV2PTB4OTA1NSkgYXQgOS4wIGlycSAxOQ0KT2N0 IDE3IDE1OjEyOjE4IG51bGx1bSAva2VybmVsOiBia3RyMDogPEJyb29rVHJl ZSA4Nzg+IGlycSAxOCBhdCBkZXZpY2UgMTAuMCBvbiBwY2kwDQpPY3QgMTcg MTU6MTI6MTggbnVsbHVtIC9rZXJuZWw6IGJrdHIwOiBIYXVwcGF1Z2UgTW9k ZWwgNjEzNDQgRDEyMQ0KT2N0IDE3IDE1OjEyOjE4IG51bGx1bSAva2VybmVs OiBia3RyMDogRGV0ZWN0ZWQgYSBNU1AzNDEwRC1CNCBhdCAweDgwDQpPY3Qg MTcgMTU6MTI6MTggbnVsbHVtIC9rZXJuZWw6IEhhdXBwYXVnZSBXaW5DYXN0 L1RWLCBQaGlsaXBzIEZSMTIxNiBQQUwgRk0gdHVuZXIsIG1zcDM0MDBjIHN0 ZXJlbywgcmVtb3RlIGNvbnRyb2wuDQpPY3QgMTcgMTU6MTI6MTggbnVsbHVt IC9rZXJuZWw6IHBjaTA6IHVua25vd24gY2FyZCAodmVuZG9yPTB4MTA5ZSwg ZGV2PTB4MDg3OCkgYXQgMTAuMSBpcnEgMTgNCk9jdCAxNyAxNToxMjoxOCBu dWxsdW0gL2tlcm5lbDogbmNyMDogPG5jciA1M2M4OTUgZmFzdDQwIHdpZGUg c2NzaT4gaXJxIDE3IGF0IGRldmljZSAxMS4wIG9uIHBjaTANCk9jdCAxNyAx NToxMjoxOCBudWxsdW0gL2tlcm5lbDogbmNyMTogPG5jciA1M2M4MTAgZmFz dDEwIHNjc2k+IGlycSAxNiBhdCBkZXZpY2UgMTIuMCBvbiBwY2kwDQpPY3Qg MTcgMTU6MTI6MTggbnVsbHVtIC9rZXJuZWw6IGZkYzA6IDxORUMgNzIwNjVC IG9yIGNsb25lPiBhdCBwb3J0IDB4M2YwLTB4M2Y3IGlycSA2IGRycSAyIG9u IGlzYTANCk9jdCAxNyAxNToxMjoxOCBudWxsdW0gL2tlcm5lbDogZmRjMDog RklGTyBlbmFibGVkLCA4IGJ5dGVzIHRocmVzaG9sZA0KT2N0IDE3IDE1OjEy OjE4IG51bGx1bSAva2VybmVsOiBmZDA6IDwxNDQwLUtCIDMuNSIgZHJpdmU+ IG9uIGZkYzAgZHJpdmUgMA0KT2N0IDE3IDE1OjEyOjE4IG51bGx1bSAva2Vy bmVsOiBhdGtiZGMwOiA8a2V5Ym9hcmQgY29udHJvbGxlciAoaTgwNDIpPiBh dCBwb3J0IDB4NjAtMHg2ZiBvbiBpc2EwDQpPY3QgMTcgMTU6MTI6MTggbnVs bHVtIC9rZXJuZWw6IGF0a2JkMDogPEFUIEtleWJvYXJkPiBpcnEgMSBvbiBh dGtiZGMwDQpPY3QgMTcgMTU6MTI6MTggbnVsbHVtIC9rZXJuZWw6IHZnYTA6 IDxHZW5lcmljIElTQSBWR0E+IGF0IHBvcnQgMHgzYjAtMHgzZGYgaW9tZW0g MHhhMDAwMC0weGJmZmZmIG9uIGlzYTANCk9jdCAxNyAxNToxMjoxOCBudWxs dW0gL2tlcm5lbDogc2MwOiA8U3lzdGVtIGNvbnNvbGU+IG9uIGlzYTANCk9j dCAxNyAxNToxMjoxOCBudWxsdW0gL2tlcm5lbDogc2MwOiBWR0EgPDE2IHZp cnR1YWwgY29uc29sZXMsIGZsYWdzPTB4MjAwPg0KT2N0IDE3IDE1OjEyOjE4 IG51bGx1bSAva2VybmVsOiBzaW8wIGF0IHBvcnQgMHgzZjgtMHgzZmYgaXJx IDQgZmxhZ3MgMHgxMCBvbiBpc2EwDQpPY3QgMTcgMTU6MTI6MTggbnVsbHVt IC9rZXJuZWw6IHNpbzA6IHR5cGUgMTY1NTBBDQpPY3QgMTcgMTU6MTI6MTgg bnVsbHVtIC9rZXJuZWw6IHNpbzEgYXQgcG9ydCAweDJmOC0weDJmZiBpcnEg MyBvbiBpc2EwDQpPY3QgMTcgMTU6MTI6MTggbnVsbHVtIC9rZXJuZWw6IHNp bzE6IHR5cGUgMTY1NTBBDQpPY3QgMTcgMTU6MTI6MTggbnVsbHVtIC9rZXJu ZWw6IHNpbzI6IGNvbmZpZ3VyZWQgaXJxIDE5IG5vdCBpbiBiaXRtYXAgb2Yg cHJvYmVkIGlycXMgMA0KT2N0IDE3IDE1OjEyOjE4IG51bGx1bSAva2VybmVs OiBzaW8zOiBjb25maWd1cmVkIGlycSAxOSBub3QgaW4gYml0bWFwIG9mIHBy b2JlZCBpcnFzIDANCk9jdCAxNyAxNToxMjoxOCBudWxsdW0gL2tlcm5lbDog cHBjMCBhdCBwb3J0IDB4Mzc4LTB4MzdmIGlycSA3IGZsYWdzIDB4NDAgb24g aXNhMA0KT2N0IDE3IDE1OjEyOjE4IG51bGx1bSAva2VybmVsOiBwcGMwOiBT TUMtbGlrZSBjaGlwc2V0IChFQ1AvRVBQL1BTMi9OSUJCTEUpIGluIENPTVBB VElCTEUgbW9kZQ0KT2N0IDE3IDE1OjEyOjE4IG51bGx1bSAva2VybmVsOiBw cGMwOiBGSUZPIHdpdGggMTYvMTYvOSBieXRlcyB0aHJlc2hvbGQNCk9jdCAx NyAxNToxMjoxOCBudWxsdW0gL2tlcm5lbDogbHB0MDogPGdlbmVyaWMgcHJp bnRlcj4gb24gcHBidXMgMA0KT2N0IDE3IDE1OjEyOjE4IG51bGx1bSAva2Vy bmVsOiBscHQwOiBJbnRlcnJ1cHQtZHJpdmVuIHBvcnQNCk9jdCAxNyAxNTox MjoxOSBudWxsdW0gL2tlcm5lbDogcHBpMDogPGdlbmVyaWMgcGFyYWxsZWwg aS9vPiBvbiBwcGJ1cyAwDQpPY3QgMTcgMTU6MTI6MTkgbnVsbHVtIC9rZXJu ZWw6IHBwczA6IDxQdWxzZSBwZXIgc2Vjb25kIFRpbWluZyBJbnRlcmZhY2U+ IG9uIHBwYnVzIDANCk9jdCAxNyAxNToxMjoxOSBudWxsdW0gL2tlcm5lbDog dW5rbm93bjA6IDxFU1MgRVMxODY4IFBsdWcgYW5kIFBsYXkgQXVkaW9Ecml2 ZT4gYXQgcG9ydCAweDgwMC0weDgwNyBvbiBpc2EwDQpPY3QgMTcgMTU6MTI6 MTkgbnVsbHVtIC9rZXJuZWw6IHBjbTE6IDxFU1MxODY4PiBhdCBwb3J0IDB4 MjIwLTB4MjJmLDB4Mzg4LTB4MzhiLDB4MzMwLTB4MzMxIGlycSA1IGRycSAx LDAgb24gaXNhMA0KT2N0IDE3IDE1OjEyOjE5IG51bGx1bSAva2VybmVsOiB1 bmtub3duMTogPEVTUyBFUzE4NjggUGx1ZyBhbmQgUGxheSBBdWRpb0RyaXZl PiBhdCBwb3J0IDB4MjAxIG9uIGlzYTANCk9jdCAxNyAxNToxMjoxOSBudWxs dW0gL2tlcm5lbDogdW5rbm93bjI6IDxHZW5lcmljIEVTREkvSURFL0FUQSBj b250cm9sbGVyPiBhdCBwb3J0IDB4MTY4LTB4MTZmLDB4MzZlLTB4MzZmIGly cSAxMiBvbiBpc2EwDQpPY3QgMTcgMTU6MTI6MTkgbnVsbHVtIC9rZXJuZWw6 IEFQSUNfSU86IFRlc3RpbmcgODI1NCBpbnRlcnJ1cHQgZGVsaXZlcnkNCk9j dCAxNyAxNToxMjoxOSBudWxsdW0gL2tlcm5lbDogQVBJQ19JTzogcm91dGlu ZyA4MjU0IHZpYSBwaW4gMg0KT2N0IDE3IDE1OjEyOjE5IG51bGx1bSAva2Vy bmVsOiBJUCBwYWNrZXQgZmlsdGVyaW5nIGluaXRpYWxpemVkLCBkaXZlcnQg ZW5hYmxlZCwgcnVsZS1iYXNlZCBmb3J3YXJkaW5nIGRpc2FibGVkLCBsb2dn aW5nIGxpbWl0ZWQgdG8gMTAwIHBhY2tldHMvZW50cnkgYnkgZGVmYXVsdA0K T2N0IDE3IDE1OjEyOjE5IG51bGx1bSAva2VybmVsOiBXYWl0aW5nIDIgc2Vj b25kcyBmb3IgU0NTSSBkZXZpY2VzIHRvIHNldHRsZQ0KT2N0IDE3IDE1OjEy OjE5IG51bGx1bSAva2VybmVsOiBTTVA6IEFQIENQVSAjMSBMYXVuY2hlZCEN Ck9jdCAxNyAxNToxMjoxOSBudWxsdW0gL2tlcm5lbDogQ3JlYXRpbmcgRElT SyBkYTANCk9jdCAxNyAxNToxMjoxOSBudWxsdW0gL2tlcm5lbDogQ3JlYXRp bmcgRElTSyBkYTENCk9jdCAxNyAxNToxMjoxOSBudWxsdW0gL2tlcm5lbDog Q3JlYXRpbmcgRElTSyBkYTINCk9jdCAxNyAxNToxMjoxOSBudWxsdW0gL2tl cm5lbDogQ3JlYXRpbmcgRElTSyBkYTMNCk9jdCAxNyAxNToxMjoxOSBudWxs dW0gL2tlcm5lbDogQ3JlYXRpbmcgRElTSyBkYTQNCk9jdCAxNyAxNToxMjox OSBudWxsdW0gL2tlcm5lbDogQ3JlYXRpbmcgRElTSyBjZDANCk9jdCAxNyAx NToxMjoxOSBudWxsdW0gL2tlcm5lbDogY2hhbmdpbmcgcm9vdCBkZXZpY2Ug dG8gZGEwczFhDQpPY3QgMTcgMTU6MTI6MTkgbnVsbHVtIC9rZXJuZWw6IGRh MCBhdCBhaGMwIGJ1cyAwIHRhcmdldCAwIGx1biAwDQpPY3QgMTcgMTU6MTI6 MTkgbnVsbHVtIC9rZXJuZWw6IGRhMDogPElCTSBERFJTLTM0NTYwRCBEQzFC PiBGaXhlZCBEaXJlY3QgQWNjZXNzIFNDU0ktMiBkZXZpY2UgDQpPY3QgMTcg MTU6MTI6MTkgbnVsbHVtIC9rZXJuZWw6IGRhMDogODAuMDAwTUIvcyB0cmFu c2ZlcnMgKDQwLjAwME1Ieiwgb2Zmc2V0IDE1LCAxNmJpdCksIFRhZ2dlZCBR dWV1ZWluZyBFbmFibGVkDQpPY3QgMTcgMTU6MTI6MTkgbnVsbHVtIC9rZXJu ZWw6IGRhMDogNDM1N01CICg4OTI1MDAwIDUxMiBieXRlIHNlY3RvcnM6IDI1 NUggNjNTL1QgNTU1QykNCk9jdCAxNyAxNToxMjoxOSBudWxsdW0gL2tlcm5l bDogZGEyIGF0IG5jcjAgYnVzIDAgdGFyZ2V0IDIgbHVuIDANCk9jdCAxNyAx NToxMjoxOSBudWxsdW0gL2tlcm5lbDogZGEyOiA8SUJNIEREUlMtMzkxMzBE IERDMUI+IEZpeGVkIERpcmVjdCBBY2Nlc3MgU0NTSS0yIGRldmljZSANCk9j dCAxNyAxNToxMjoxOSBudWxsdW0gL2tlcm5lbDogZGEyOiA0MC4wMDBNQi9z IHRyYW5zZmVycyAoMjAuMDAwTUh6LCBvZmZzZXQgMTUsIDE2Yml0KSwgVGFn Z2VkIFF1ZXVlaW5nIEVuYWJsZWQNCk9jdCAxNyAxNToxMjoxOSBudWxsdW0g L2tlcm5lbDogZGEyOiA4NzE1TUIgKDE3ODUwMDAwIDUxMiBieXRlIHNlY3Rv cnM6IDI1NUggNjNTL1QgMTExMUMpDQpPY3QgMTcgMTU6MTI6MTkgbnVsbHVt IC9rZXJuZWw6IGRhMSBhdCBuY3IwIGJ1cyAwIHRhcmdldCAxIGx1biAwDQpP Y3QgMTcgMTU6MTI6MTkgbnVsbHVtIC9rZXJuZWw6IGRhMTogPElCTSBERFJT LTM5MTMwRCBEQzFCPiBGaXhlZCBEaXJlY3QgQWNjZXNzIFNDU0ktMiBkZXZp Y2UgDQpPY3QgMTcgMTU6MTI6MTkgbnVsbHVtIC9rZXJuZWw6IGRhMTogNDAu MDAwTUIvcyB0cmFuc2ZlcnMgKDIwLjAwME1Ieiwgb2Zmc2V0IDE1LCAxNmJp dCksIFRhZ2dlZCBRdWV1ZWluZyBFbmFibGVkDQpPY3QgMTcgMTU6MTI6MTkg bnVsbHVtIC9rZXJuZWw6IGRhMTogODcxNU1CICgxNzg1MDAwMCA1MTIgYnl0 ZSBzZWN0b3JzOiAyNTVIIDYzUy9UIDExMTFDKQ0KT2N0IDE3IDE1OjEyOjE5 IG51bGx1bSAva2VybmVsOiBkYTMgYXQgbmNyMCBidXMgMCB0YXJnZXQgMyBs dW4gMA0KT2N0IDE3IDE1OjEyOjE5IG51bGx1bSAva2VybmVsOiBkYTM6IDxJ Qk0gRERSUy0zOTEzMEQgREMxQj4gRml4ZWQgRGlyZWN0IEFjY2VzcyBTQ1NJ LTIgZGV2aWNlIA0KT2N0IDE3IDE1OjEyOjE5IG51bGx1bSAva2VybmVsOiBk YTM6IDQwLjAwME1CL3MgdHJhbnNmZXJzICgyMC4wMDBNSHosIG9mZnNldCAx NSwgMTZiaXQpLCBUYWdnZWQgUXVldWVpbmcgRW5hYmxlZA0KT2N0IDE3IDE1 OjEyOjE5IG51bGx1bSAva2VybmVsOiBkYTM6IDg3MTVNQiAoMTc4NTAwMDAg NTEyIGJ5dGUgc2VjdG9yczogMjU1SCA2M1MvVCAxMTExQykNCk9jdCAxNyAx NToxMjoxOSBudWxsdW0gL2tlcm5lbDogZGE0IGF0IG5jcjAgYnVzIDAgdGFy Z2V0IDQgbHVuIDANCk9jdCAxNyAxNToxMjoxOSBudWxsdW0gL2tlcm5lbDog ZGE0OiA8SUJNIEREUlMtMzkxMzBEIERDMUI+IEZpeGVkIERpcmVjdCBBY2Nl c3MgU0NTSS0yIGRldmljZSANCk9jdCAxNyAxNToxMjoxOSBudWxsdW0gL2tl cm5lbDogZGE0OiA0MC4wMDBNQi9zIHRyYW5zZmVycyAoMjAuMDAwTUh6LCBv ZmZzZXQgMTUsIDE2Yml0KSwgVGFnZ2VkIFF1ZXVlaW5nIEVuYWJsZWQNCk9j dCAxNyAxNToxMjoxOSBudWxsdW0gL2tlcm5lbDogZGE0OiA4NzE1TUIgKDE3 ODUwMDAwIDUxMiBieXRlIHNlY3RvcnM6IDI1NUggNjNTL1QgMTExMUMpDQpP Y3QgMTcgMTU6MTI6MTkgbnVsbHVtIC9rZXJuZWw6IHZpbnVtOiBsb2FkZWQN Ck9jdCAxNyAxNToxMjoxOSBudWxsdW0gL2tlcm5lbDogdmludW06IHJlYWRp bmcgY29uZmlndXJhdGlvbiBmcm9tIC9kZXYvZGEzczFkDQpPY3QgMTcgMTU6 MTI6MTkgbnVsbHVtIC9rZXJuZWw6IHZpbnVtOiB1cGRhdGluZyBjb25maWd1 cmF0aW9uIGZyb20gL2Rldi9kYTRzMWQNCk9jdCAxNyAxNToxMjoxOSBudWxs dW0gL2tlcm5lbDogdmludW06IHVwZGF0aW5nIGNvbmZpZ3VyYXRpb24gZnJv bSAvZGV2L2RhMXMxZA0KT2N0IDE3IDE1OjEyOjE5IG51bGx1bSAva2VybmVs OiB2aW51bTogdXBkYXRpbmcgY29uZmlndXJhdGlvbiBmcm9tIC9kZXYvZGEy czFkDQpPY3QgMTcgMTU6MTI6MjAgbnVsbHVtIC9rZXJuZWw6IGludHBtMDog PEludGVsIDgyMzcxQUIgUG93ZXIgbWFuYWdlbWVudCBjb250cm9sbGVyPiBh dCBkZXZpY2UgNC4zIG9uIHBjaTANCk9jdCAxNyAxNToxMjoyMCBudWxsdW0g L2tlcm5lbDogaW50cG0wOiBDb3VsZCBub3QgYWxsb2NhdGUgQnVzIHNwYWNl DQpPY3QgMTcgMTU6MTI6MjAgbnVsbHVtIC9rZXJuZWw6IGRldmljZV9wcm9i ZV9hbmRfYXR0YWNoOiBpbnRwbTAgYXR0YWNoIHJldHVybmVkIDYNCk9jdCAx NyAxNToxMjoyMCBudWxsdW0gL2tlcm5lbDogeGwwOiA8M0NvbSAzYzkwNUIt VFggRmFzdCBFdGhlcmxpbmsgWEw+IGlycSAxOSBhdCBkZXZpY2UgOS4wIG9u IHBjaTANCk9jdCAxNyAxNToxMjoyMCBudWxsdW0gL2tlcm5lbDogeGwwOiBF dGhlcm5ldCBhZGRyZXNzOiAwMDoxMDo1YTpkNTo5Yjo0Mw0KT2N0IDE3IDE1 OjEyOjIwIG51bGx1bSAva2VybmVsOiBwY2kwOiB1bmtub3duIGNhcmQgKHZl bmRvcj0weDEwOWUsIGRldj0weDA4NzgpIGF0IDEwLjEgaXJxIDE4DQpPY3Qg MTcgMTU6MTI6MjAgbnVsbHVtIC9rZXJuZWw6IG1paWJ1czA6IDxNSUkgYnVz PiBvbiB4bDANCk9jdCAxNyAxNToxMjoyMCBudWxsdW0gL2tlcm5lbDogeGxw aHkwOiA8M0NvbSBpbnRlcm5hbCBtZWRpYSBpbnRlcmZhY2U+IG9uIG1paWJ1 czANCk9jdCAxNyAxNToxMjoyMCBudWxsdW0gL2tlcm5lbDogeGxwaHkwOiAg MTBiYXNlVCwgMTBiYXNlVC1GRFgsIDEwMGJhc2VUWCwgMTAwYmFzZVRYLUZE WCwgYXV0bw0KT2N0IDE3IDE1OjEyOjIwIG51bGx1bSAva2VybmVsOiBjZDAg YXQgYWhjMCBidXMgMCB0YXJnZXQgMyBsdW4gMA0KT2N0IDE3IDE1OjEyOjIw IG51bGx1bSAva2VybmVsOiBjZDA6IDxQTEVYVE9SIENELVJPTSBQWC00MFRT IDEuMDA+IFJlbW92YWJsZSBDRC1ST00gU0NTSS0yIGRldmljZSANCk9jdCAx NyAxNToxMjoyMCBudWxsdW0gL2tlcm5lbDogY2QwOiAyMC4wMDBNQi9zIHRy YW5zZmVycyAoMjAuMDAwTUh6LCBvZmZzZXQgMTUpDQpPY3QgMTcgMTU6MTI6 MjAgbnVsbHVtIC9rZXJuZWw6IGNkMDogY2QgcHJlc2VudCBbMzI3Njg5IHgg MjA0OCBieXRlIHJlY29yZHNdDQo= --0-249161613-940198568=:930-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 15:19:54 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 9C8FB14E44 for ; Sun, 17 Oct 1999 15:19:51 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA18474; Sun, 17 Oct 1999 15:19:43 -0700 Date: Sun, 17 Oct 1999 15:19:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Michael Reifenberger Cc: Bernd Walter , FreeBSD-Current Subject: Re: -current crash 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 Try it w/o vinum, procfs and nfs kernel objects. On Mon, 18 Oct 1999, Michael Reifenberger wrote: > On Mon, 18 Oct 1999, Bernd Walter wrote: > ... > > What kind of modules were you running? > (nullum)(root)# kldstat > Id Refs Address Size Name > 1 7 0xc0100000 1eb518 kernel > 2 1 0xc02ec000 cdbc bktr.ko > 3 1 0xc1011000 c3000 vinum.ko > 4 1 0xc1111000 6000 procfs.ko > 5 1 0xc1118000 8000 if_xl.ko > 6 1 0xc1121000 7000 miibus.ko > 7 1 0xc131e000 4c000 nfs.ko > > Are these in sync with the kernel? > Yes. > > Configuration hasnt changed for weeks. > > boottext is attached. > > Softupdates is on on all FS. (Wasn't a problem so far) > (nullum)(root)# mount > /dev/da0s1a on / (ufs, local, soft-updates, writes: sync 5 async 274) > /dev/da0s1d on /usr (ufs, NFS exported, local, soft-updates, writes: sync 172 > async 5230) > /dev/vinum/data on /mnt/data (ufs, NFS exported, local, soft-updates, writes: > sync 2 async 0) > /dev/vinum/oracle on /oracle (ufs, NFS exported, local, soft-updates, writes: > sync 2 async 0) > /dev/vinum/sapdaten on /oracle/NIL/sapdaten (ufs, local, soft-updates, writes: > sync 2 async 0) > /dev/vinum/sapmnt on /sapmnt (ufs, local, soft-updates, writes: sync 2 async 0) > /dev/vinum/usr_sap on /usr/sap (ufs, NFS exported, local, soft-updates, writes: > sync 2 async 0) > procfs on /proc (procfs, local) > > Bye! > ---- > Michael Reifenberger > Plaut Software GmbH, R/3 Basis > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 15:44:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id C094B14DFB for ; Sun, 17 Oct 1999 15:44:10 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id AAA24065; Mon, 18 Oct 1999 00:43:32 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id AAA13734; Mon, 18 Oct 1999 00:43:31 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id AAA01064; Mon, 18 Oct 1999 00:43:21 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Mon, 18 Oct 1999 00:43:21 +0200 (CEST) From: Michael Reifenberger To: Matthew Jacob Cc: FreeBSD-Current , grog@lemis.com Subject: Re: -current crash 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, 17 Oct 1999, Matthew Jacob wrote: > Date: Sun, 17 Oct 1999 15:08:10 -0700 (PDT) > From: Matthew Jacob > To: Michael Reifenberger > Cc: FreeBSD-Current > Subject: Re: -current crash > > > Doesn't tell *me* a lot.... maybe a broken driver that's a KLD? It looks > like something from spec_strategy is being called that's not in the > /kernel space- could be a KLD- are your KLDs up to date for the new > kernel? Like, is this vinum perhaps? Seems so. After using the .gdbinit* stuff from modules/vinum I get the missing pices: ... #5 0xc101e91b in launch_requests (rq=0xc17d3f00, reviveok=0x0) at /usr/src/sys/modules/vinum/../../dev/vinum/vinumrequest.c:387 #6 0xc101e752 in vinumstart (bp=0xc62f8f30, reviveok=0x0) at /usr/src/sys/modules/vinum/../../dev/vinum/vinumrequest.c:299 #7 0xc101e54e in vinumstrategy (bp=0xc62f8f30) at /usr/src/sys/modules/vinum/../../dev/vinum/vinnumrequest.c:164 ... > > > > On Sun, 17 Oct 1999, Matthew Jacob wrote: > > ... > > > Well, a DDB traceback would help. Failing that, at least what does > > > 0xc101891b correspond to.... otherwise, it's all ENOGUESS.... > > Next try, next crash. No problem. Easy crashing :-) > > > > I tried to find the address 0xc101891b using nm(1) but can't seem to find it. > > Whats the preffered method for finding? > > > > GNU gdb 4.18 > > Copyright 1998 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you are > > welcome to change it and/or distribute copies of it under certain conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > This GDB was configured as "i386-unknown-freebsd"... > > SMP 2 cpus > > IdlePTD 3194880 > > initial pcb at 282c20 > > panicstr: page fault > > panic messages: > > --- > > Fatal trap 12: page fault while in kernel mode > > mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 > > fault virtual address = 0xdeadc0e6 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xc101e91b > > stack pointer = 0x10:0xce042cbc > > frame pointer = 0x10:0xce042ccc > > 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 = 16328 (dbv) > > interrupt mask = none <- SMP: XXX > > trap number = 12 > > panic: page fault > > mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 > > boot() called on cpu#1 > > > > syncing disks... 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 done > > > > dumping to dev #da/0x20001, offset 540696 > > 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 > > --- > > #0 boot (howto=256) at ../../kern/kern_shutdown.c:280 > > 280 dumppcb.pcb_cr3 = rcr3(); > > #0 boot (howto=256) at ../../kern/kern_shutdown.c:280 > > #1 0xc015275d in panic (fmt=0xc02520cf "page fault") at ../../kern/kern_shutdown.c:530 > > #2 0xc0211b30 in trap_fatal (frame=0xce042c7c, eva=3735929062) at ../../i386/i386/trap.c:907 > > #3 0xc02117a1 in trap_pfault (frame=0xce042c7c, usermode=0, eva=3735929062) > > at ../../i386/i386/trap.c:800 > > #4 0xc0211303 in trap (frame={tf_fs = -1057095656, tf_es = -1052377072, tf_ds = -1056112624, > > tf_edi = -559038242, tf_esi = -1052325860, tf_ebp = -838587188, tf_isp = -838587224, > > tf_ebx = -1056083712, tf_edx = -1070995904, tf_ecx = 16777217, tf_eax = -16162, > > tf_trapno = 12, tf_err = 0, tf_eip = -1056839397, tf_cs = 8, tf_eflags = 66182, > > tf_esp = -1055894172, tf_ss = -969961680}) at ../../i386/i386/trap.c:426 > > #5 0xc101e91b in ?? () > > #6 0xc101e752 in ?? () > > #7 0xc101e54e in ?? () > > #8 0xc0186a82 in spec_strategy (ap=0xce042d4c) at > ../../miscfs/specfs/spec_vnops.c:686 > > #9 0xc0186039 in spec_vnoperate (ap=0xce042d4c) at ../../miscfs/specfs/spec_vnops.c:133 > > #10 0xc01bb371 in ufs_vnoperatespec (ap=0xce042d4c) at ../../ufs/ufs/ufs_vnops.c:2313 > > #11 0xc01bad70 in ufs_strategy (ap=0xce042dd4) at vnode_if.h:940 > > #12 0xc01bb341 in ufs_vnoperate (ap=0xce042dd4) at ../../ufs/ufs/ufs_vnops.c:2295 > > #13 0xc0177e06 in cluster_read (vp=0xce16f380, filesize=1258299392, lblkno=137260, size=8192, > > cred=0x0, totread=8192, seqcount=127, bpp=0xce042e70) at vnode_if.h:940 > > #14 0xc01b4517 in ffs_read (ap=0xce042e98) at ../../ufs/ufs/ufs_readwrite.c:249 > > #15 0xc0182800 in vn_read (fp=0xc121cac0, uio=0xce042ee8, cred=0xc1224c80, flags=0, > > p=0xcdfc8500) at vnode_if.h:330 > > #16 0xc015fdf4 in dofileread (p=0xcdfc8500, fp=0xc121cac0, fd=4, buf=0x28418cd0, nbyte=8192, > > offset=-1, flags=0) at ../../sys/file.h:135 > > #17 0xc015fcfb in read (p=0xcdfc8500, uap=0xce042f80) at ../../kern/sys_generic.c:110 > > #18 0xc0211de1 in syscall (frame={tf_fs = 65583, tf_es = 47, tf_ds = -1078001617, > > tf_edi = 137217, tf_esi = 0, tf_ebp = -1077947392, tf_isp = -838586412, tf_ebx = 4, > > tf_edx = 8192, tf_ecx = 675384528, tf_eax = 3, tf_trapno = 7, tf_err = 2, > > tf_eip = 674927924, tf_cs = 31, tf_eflags = 658, tf_esp = -1077947420, tf_ss = 47}) > > at ../../i386/i386/trap.c:1056 > > #19 0xc01fe9b1 in Xint0x80_syscall () > > (kgdb) quit > > > > Bye! > > ---- > > Michael Reifenberger > > Plaut Software GmbH, R/3 Basis > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 16:35:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id 52E8414A12 for ; Sun, 17 Oct 1999 16:35:45 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id BAA24177; Mon, 18 Oct 1999 01:35:44 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id BAA13837; Mon, 18 Oct 1999 01:35:43 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id BAA01184; Mon, 18 Oct 1999 01:35:16 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Mon, 18 Oct 1999 01:35:16 +0200 (CEST) From: Michael Reifenberger To: Greg Lehey Cc: Matthew Jacob , FreeBSD-Current Subject: Re: -current crash In-Reply-To: <19991018121619.01344@mojave.worldwide.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 Mon, 18 Oct 1999, Greg Lehey wrote: > Date: Mon, 18 Oct 1999 12:16:19 +1300 > From: Greg Lehey > To: Michael Reifenberger , Matthew Jacob > Cc: FreeBSD-Current > Subject: Re: -current crash ... > Have you rebuilt the kld? kernel,modules,world are in sync. The same configuration worked for several weeks without problems. BTW: where does the 0xdeadc0de (0xDeadCode ?) below come from? Info to frame5: (kgdb) rq Request: { bp = 0xdeadc0de, flags = 0xc0261140, volplex = { volno = 0xdeadc0de, plexno = 0xdeadc0de }, error = 0xc121c800, sdno = 0xdeadc0de, isplex = 0xc0de, active = 0xdead, rqg = 0xdeadc0de, lrqg = 0xdeadc0de, next = 0xdeadc0de } Cannot access memory at address 0xdeadc136. (kgdb) rqe sdoffset 0x0, useroffset 0x0, dataoffset 0x0, datalen 0x0, groupoffset 0x0, grouplen 0x0, buflen 0x0 Flags 0x0, Subdisk 0 Drive 0 Buffer at 0xc146c81c: dev (none) data 0x0 bcount 0x0 blkno 0x0 resid 0x0 flags 0xdeadc0de: busy call phys (kgdb) meminfo Block Sequence size address line file 0 2 1760 0xc10d7800 106 vinumrequest.c 1 5 256 0xc10d9800 129 2 7 256 0xc10d8500 129 3 9 256 0xc10d9600 129 4 11 256 0xc10d9000 129 5 13 2048 0xc10d7000 114 6 15 2048 0xc1104800 943 7 16 3680 0xc1105000 114 8 22 32 0xc0a5e040 114 9 23 32 0xc0a5e020 114 10 24 32 0xc0a5e000 114 11 25 32 0xc1106fe0 114 12 26 5888 0xc1107000 114 13 27 32 0xc1106fc0 114 14 28 16 0xc0f83fe0 770 15 29 16 0xc0f83ee0 770 16 30 16 0xc0f83780 770 17 31 16 0xc0f83740 770 18 32 16 0xc0f836a0 770 19 33 16 0xc0f830f0 770 20 34 16 0xc0f830c0 770 21 35 16 0xc0f83120 770 22 36 16 0xc0f83150 770 23 37 16 0xc0ffbf10 770 24 38 16 0xc0ffbf00 770 25 39 16 0xc0ffbef0 770 26 40 16 0xc0ffbee0 770 27 41 16 0xc0ffbed0 770 28 42 16 0xc0ffbec0 770 Hope it helps. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 16:52:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 2B96414CC7 for ; Sun, 17 Oct 1999 16:52:27 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id BAA28138; Mon, 18 Oct 1999 01:48:18 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id BAA53260; Mon, 18 Oct 1999 01:53:09 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id BAA24337; Mon, 18 Oct 1999 01:53:12 +0200 (CEST) (envelope-from ticso) Date: Mon, 18 Oct 1999 01:53:12 +0200 From: Bernd Walter To: Michael Reifenberger , grog@lemis.com Cc: Bernd Walter , FreeBSD-Current Subject: Re: -current crash Message-ID: <19991018015311.A24322@cicely8.cicely.de> References: <19991018000538.A24204@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Michael Reifenberger on Mon, Oct 18, 1999 at 12:16:08AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 18, 1999 at 12:16:08AM +0200, Michael Reifenberger wrote: The combination of vinum raid5 and softupdates is known to trigger a bug which may look just as you described. I might help if you disable softupdates on the vinum volumes. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 16:59:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id C32ED14CC7 for ; Sun, 17 Oct 1999 16:59:15 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id BAA24212; Mon, 18 Oct 1999 01:59:14 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id BAA13910; Mon, 18 Oct 1999 01:59:14 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id BAA01248; Mon, 18 Oct 1999 01:58:25 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Mon, 18 Oct 1999 01:58:25 +0200 (CEST) From: Michael Reifenberger To: Bernd Walter Cc: grog@lemis.com, FreeBSD-Current Subject: Re: -current crash In-Reply-To: <19991018015311.A24322@cicely8.cicely.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, 18 Oct 1999, Bernd Walter wrote: ... > On Mon, Oct 18, 1999 at 12:16:08AM +0200, Michael Reifenberger wrote: > The combination of vinum raid5 and softupdates is known to trigger a bug > which may look just as you described. > I might help if you disable softupdates on the vinum volumes. Right. But nix raid5. The volumes are raid0 or raid0+1 Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 17:10: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id D4F8A14DE9 for ; Sun, 17 Oct 1999 17:09:55 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id CAA24298; Mon, 18 Oct 1999 02:09:55 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id CAA14026; Mon, 18 Oct 1999 02:09:54 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id CAA01280; Mon, 18 Oct 1999 02:09:49 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Mon, 18 Oct 1999 02:09:49 +0200 (CEST) From: Michael Reifenberger To: Greg Lehey Cc: Matthew Jacob , FreeBSD-Current Subject: Re: -current crash In-Reply-To: <19991018125004.25271@mojave.worldwide.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 Mon, 18 Oct 1999, Greg Lehey wrote: > Date: Mon, 18 Oct 1999 12:50:04 +1300 > From: Greg Lehey > To: Michael Reifenberger > Cc: Matthew Jacob , FreeBSD-Current > Subject: Re: -current crash ... > OK, this is what I was afraid of. I'm committing some fixes. Thanks. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 17:32:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id 5D00114E52 for ; Sun, 17 Oct 1999 17:32:37 -0700 (PDT) (envelope-from will@shadow.blackdawn.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=shadow.blackdawn.com) by neptune.psn.net with esmtp (PSN Internet Service 2.12 #3) for current@FreeBSD.ORG id 11d0j6-0003Qh-00; Sun, 17 Oct 1999 17:32:36 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id UAA44147 for current@FreeBSD.ORG; Sun, 17 Oct 1999 20:32:33 -0400 (EDT) (envelope-from will) 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, 17 Oct 1999 20:32:33 -0400 (EDT) Reply-To: Will Andrews From: Will Andrews To: current@FreeBSD.ORG Subject: -CURRENT `make world` fails.. (ucontext.h?) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On a fresh cvsup of the -CURRENT sources, I've been trying to do a `make world`. I've gotten all the way through (past signal 12 errors, which were fixed by reading the -CURRENT archives and recompiling an up-to-date kernel) to the boot loader. Since the errors are on another box (which is in singleuser mode), I can't produce the exact log, however, I'll do my best copying it off its screen 10 feet from here..: ==> sys/boot/i386/libi386 cc -O -pipe -I/usr/src/sys/boot/i386/libi386 [...] In file from ... from ... from/usr/src/sys/boot/i386/libi386/aout_freebsd.c:29: /usr/src/sys/boot/i386/libi386/../../../sys/ucontext.h:34: machine/ucontext.h: No such file or directory. [...] *** Error code 1 --- I've looked around the src for a machine/ucontext.h. The particular including file, /usr/src/sys/sys/ucontext.h includes , so if it's looking at /usr/include/machine/ucontext.h, that's not there.. is this the correct file to be #include'ing? Is there any additional information I can provide (I noticed a related thread, but DCS's reply didn't seem to help..)? -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 17:42:14 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 03EA914A14 for ; Sun, 17 Oct 1999 17:42:12 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id RAA59594; Sun, 17 Oct 1999 17:42:05 -0700 (PDT) Date: Sun, 17 Oct 1999 17:42:05 -0700 (PDT) From: Julian Elischer To: Michael Reifenberger Cc: Bernd Walter , FreeBSD-Current Subject: Re: -current crash 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 vinum module looks to have been the problem.. not ethat you had stack elements at 0xc101exxx vinum starts at 0c1011000, On Mon, 18 Oct 1999, Michael Reifenberger wrote: > On Mon, 18 Oct 1999, Bernd Walter wrote: > ... > > What kind of modules were you running? > (nullum)(root)# kldstat > Id Refs Address Size Name > 1 7 0xc0100000 1eb518 kernel > 2 1 0xc02ec000 cdbc bktr.ko > 3 1 0xc1011000 c3000 vinum.ko > 4 1 0xc1111000 6000 procfs.ko > 5 1 0xc1118000 8000 if_xl.ko > 6 1 0xc1121000 7000 miibus.ko > 7 1 0xc131e000 4c000 nfs.ko > > Are these in sync with the kernel? > Yes. > > Configuration hasnt changed for weeks. > > boottext is attached. > > Softupdates is on on all FS. (Wasn't a problem so far) > (nullum)(root)# mount > /dev/da0s1a on / (ufs, local, soft-updates, writes: sync 5 async 274) > /dev/da0s1d on /usr (ufs, NFS exported, local, soft-updates, writes: sync 172 > async 5230) > /dev/vinum/data on /mnt/data (ufs, NFS exported, local, soft-updates, writes: > sync 2 async 0) > /dev/vinum/oracle on /oracle (ufs, NFS exported, local, soft-updates, writes: > sync 2 async 0) > /dev/vinum/sapdaten on /oracle/NIL/sapdaten (ufs, local, soft-updates, writes: > sync 2 async 0) > /dev/vinum/sapmnt on /sapmnt (ufs, local, soft-updates, writes: sync 2 async 0) > /dev/vinum/usr_sap on /usr/sap (ufs, NFS exported, local, soft-updates, writes: > sync 2 async 0) > procfs on /proc (procfs, local) > > Bye! > ---- > Michael Reifenberger > Plaut Software GmbH, R/3 Basis > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 18: 0:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id 85DDB14A14 for ; Sun, 17 Oct 1999 18:00:14 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id DAA24410; Mon, 18 Oct 1999 03:00:13 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id DAA14159; Mon, 18 Oct 1999 03:00:13 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id CAA01432; Mon, 18 Oct 1999 02:59:00 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Mon, 18 Oct 1999 02:59:00 +0200 (CEST) From: Michael Reifenberger To: Greg Lehey Cc: FreeBSD-Current Subject: Re: -current crash In-Reply-To: <19991018134027.30965@mojave.worldwide.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 Mon, 18 Oct 1999, Greg Lehey wrote: > Date: Mon, 18 Oct 1999 13:40:27 +1300 > From: Greg Lehey > To: Michael Reifenberger > Subject: Re: -current crash Ok, seems to be fixed. A few stress tests which paniced reliable before do new work. Thanks for the fast response. And now have a nice and relaxed trip to the FreeBSDCon. BTW: could you remind Jordan to put the slides and docs online for those who are not there in SF. I've not seen anything else except the agenda on the webpage. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 18: 0:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id 322CA14C09 for ; Sun, 17 Oct 1999 18:00:15 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id DAA24414; Mon, 18 Oct 1999 03:00:14 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id DAA14160; Mon, 18 Oct 1999 03:00:14 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id DAA01443; Mon, 18 Oct 1999 03:00:15 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Mon, 18 Oct 1999 03:00:15 +0200 (CEST) From: Michael Reifenberger To: Julian Elischer Cc: Bernd Walter , FreeBSD-Current Subject: Re: -current crash 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, 17 Oct 1999, Julian Elischer wrote: ... > the vinum module looks to have been the problem.. > not ethat you had stack elements at 0xc101exxx > vinum starts at 0c1011000, Yes. But you are too late :-) The fix is allready commited. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 19:15:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from kiwi.mail.easynet.net (kiwi.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (Postfix) with ESMTP id EC3D314C13; Sun, 17 Oct 1999 19:15:23 -0700 (PDT) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (alister.w.easynet.co.uk [212.212.251.86]) by kiwi.mail.easynet.net (Postfix) with ESMTP id 005EDDAF59; Mon, 18 Oct 1999 03:15:20 +0100 (BST) Message-ID: <380A9278.638D7FC2@freenet.co.uk> Date: Mon, 18 Oct 1999 03:22:32 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Kurt D. Zeilenga" , freebsd-emulation@freebsd.org, freebsd-current@freebsd.org Subject: Re: duplicate filenames under Linux emulation References: <3.0.5.32.19991017140045.00948160@localhost> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kurt D. Zeilenga" wrote: > > might be informative to provide output of "ls -li" to the list. Sure... it doesn't change one thing, but here goes: current:~/prog/motif/GUITests/Test2$ ls -li total 237 444972 -rw-r--r-- 1 ak users 5626 Oct 17 20:38 #uil.uil# 444961 -rw-r--r-- 1 ak users 1127 Oct 17 20:23 Imakefile 444966 -rw-r--r-- 1 ak users 20103 Oct 17 20:28 Makefile 444965 -rw-r--r-- 1 ak users 495 Oct 17 20:23 app-defaults 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 bxutils-c.c 444970 -rw-r--r-- 1 ak users 23244 Oct 17 20:34 bxutils-c.o 444962 -rw-r--r-- 1 ak users 1822 Oct 17 20:27 callbacks-c.c 444969 -rw-r--r-- 1 ak users 896 Oct 17 20:34 callbacks-c.o 444976 -rw-r--r-- 1 ak users 8382 Oct 17 20:39 creation-c.c 444963 -rw-r--r-- 1 ak users 8156 Oct 17 20:23 creation-c.c~ 444968 -rw-r--r-- 1 ak users 4728 Oct 17 20:34 creation-c.o 444971 -rwxr-xr-x 1 ak users 32275 Oct 17 20:34 main-c 444952 -rw-r--r-- 1 ak users 3416 Oct 17 20:23 main-c.c 444946 -rw-r--r-- 1 ak users 1588 Oct 17 20:34 main-c.o 444960 -rw-r--r-- 1 ak users 1188 Oct 17 20:23 makefile-c 444947 -rw-r--r-- 1 ak users 7198 Oct 17 20:20 uil.uil current:~/prog/motif/GUITests/Test2$ /compat/linux/bin/bash current:~/prog/motif/GUITests/Test2$ ls -li total 349 444972 -rw-r--r-- 1 ak users 5626 Oct 17 20:38 #uil.uil# 444961 -rw-r--r-- 1 ak users 1127 Oct 17 20:23 Imakefile 444966 -rw-r--r-- 1 ak users 20103 Oct 17 20:28 Makefile 444965 -rw-r--r-- 1 ak users 495 Oct 17 20:23 app-defaults 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 bxutils-c.c 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 bxutils-c.c 444970 -rw-r--r-- 1 ak users 23244 Oct 17 20:34 bxutils-c.o 444962 -rw-r--r-- 1 ak users 1822 Oct 17 20:27 callbacks-c.c 444969 -rw-r--r-- 1 ak users 896 Oct 17 20:34 callbacks-c.o 444976 -rw-r--r-- 1 ak users 8382 Oct 17 20:39 creation-c.c 444963 -rw-r--r-- 1 ak users 8156 Oct 17 20:23 creation-c.c~ 444968 -rw-r--r-- 1 ak users 4728 Oct 17 20:34 creation-c.o 444971 -rwxr-xr-x 1 ak users 32275 Oct 17 20:34 main-c 444952 -rw-r--r-- 1 ak users 3416 Oct 17 20:23 main-c.c 444946 -rw-r--r-- 1 ak users 1588 Oct 17 20:34 main-c.o 444960 -rw-r--r-- 1 ak users 1188 Oct 17 20:23 makefile-c 444947 -rw-r--r-- 1 ak users 7198 Oct 17 20:20 uil.uil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 19:55:12 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 1533114D49; Sun, 17 Oct 1999 19:55:00 -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 MAA73538; Mon, 18 Oct 1999 12:23:59 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199910180253.MAA73538@gizmo.internode.com.au> Subject: Re: duplicate filenames under Linux emulation To: ak@freenet.co.uk (Alex) Date: Mon, 18 Oct 1999 12:23:58 +0930 (CST) Cc: kurt@boolean.net, freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: <380A9278.638D7FC2@freenet.co.uk> from "Alex" at Oct 18, 99 03:22:32 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 Alex wrote: > 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 > bxutils-c.c > 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 > bxutils-c.c For what it's worth, I have this bug in the to-do list for the SVR4 emulator too. It's caused by the fact that dirent structures for BSD and SysVR4 are of different sizes, so svr4_getdents() (and svr4_getdents64(), its 64-bit counterpart) fetches a buffer full of BSD dirent structures from disk (usually more than the number which have actually been requested) with VOP_READDIR(), rewrites them into another buffer full of svr4_dirent structures, and returns the contents of the second buffer to userspace. Next time getdents() is called the emulated version continues from where it left off in the first buffer until it has been exhaused, at which point it issues another VOP_READDIR() call to refresh it. It looks like the duplicates are the entries which appear on the boundaries of the buffer first buffer (i.e.: the last directory entry in a buffer will be re-read into the beginning of the buffer when VOP_READDIR() is called again). I haven't had time to examine it in detail, but I suspect that incrementing an offset parameter for VOP_READDIR() aio request will fix this bug. If it does, let me know and I'll fold the result into svr4_getdents() as well :-) - 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 Sun Oct 17 19:55:33 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 83A1A1515F for ; Sun, 17 Oct 1999 19:55:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA19542 for ; Sun, 17 Oct 1999 19:55:18 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: Is it just me or is sys/signal.h just completely screwed up now? Date: Sun, 17 Oct 1999 19:55:18 -0700 Message-ID: <19538.940215318@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a box running yesterday's -current and it can't compile or install things like XFree86 or ImageMagik due to syntax errors in this file. Investigating further, I find that the trouble begins around line 127, where we see: #if defined(_P1003_1B_VISIBLE) || defined(KERNEL) .. #endif around some declarations for sigval and siginfo_t. The problem is that these typedefs are later used to define other structures like sigevent sig_t but *without* the aformentioned #if clause so they essentially get referenced without being defined. I also find it hard to believe that I'm the first to run into this since the signal changes went in. Has no one else experienced this? Oh, and yes, I made sure I was working with the very latest sources and I rebuilt everything in sight before raising this complaint. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 20:18:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta3.rcsntx.swbell.net (mta3.rcsntx.swbell.net [151.164.30.27]) by hub.freebsd.org (Postfix) with ESMTP id B4E4214D49; Sun, 17 Oct 1999 20:18:42 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta3.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FJS002N33UCD1@mta3.rcsntx.swbell.net>; Sun, 17 Oct 1999 22:18:13 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id WAA09605; Sun, 17 Oct 1999 22:18:29 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Sun, 17 Oct 1999 22:18:29 -0500 From: Chris Costello Subject: Re: duplicate filenames under Linux emulation In-reply-to: <380A9278.638D7FC2@freenet.co.uk> To: Alex Cc: "Kurt D. Zeilenga" , freebsd-emulation@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991017221828.H452@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <3.0.5.32.19991017140045.00948160@localhost> <380A9278.638D7FC2@freenet.co.uk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 18, 1999, Alex wrote: > 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 bxutils-c.c > 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 > bxutils-c.c > 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 Two different versions of ls. You seem to have the GNU version of ls(1) installed for the Linux emulation listing. I would say that it is that ls(1) or perhaps the Linux libc's fts(3) that is broken. -- |Chris Costello |It is easier to write an incorrect program than understand a correct one. `------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 17 21:18:28 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 B5DCB14A09 for ; Sun, 17 Oct 1999 21:18:24 -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 AAA20424; Mon, 18 Oct 1999 00:18:07 -0400 (EDT) Date: Mon, 18 Oct 1999 00:18:06 -0400 (EDT) From: "Matthew N. Dodd" To: Andreas Klemm Cc: current@FreeBSD.ORG Subject: Re: -current problem: Network cards doesn't run In-Reply-To: <19991017005544.B973@titan.klemm.gtn.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, 17 Oct 1999, Andreas Klemm wrote: > See ed0.... > When running a current kernel of some days ago, no problems. > Were there perhaps changes in the last days that introduce > this, that some NICs doesn't run ? > Even the xl0 interface didn't run (DMZ). Ping to hosts in > internet didn't succeed. I believe I've tracked this down. I'll commit a fix once I've verified it. > 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 Oct 17 00:40:49 CEST 1999 > root@titan.klemm.gtn.com:/usr/src/sys/compile/TITAN > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium Pro (199.43-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x619 Stepping = 9 > Features=0xfbff > real memory = 159383552 (155648K bytes) > avail memory = 151044096 (147504K bytes) > Programming 24 pins in IOAPIC #0 > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > Preloaded elf kernel "kernel" at 0xc030c000. > Pentium Pro MTRR support enabled > ccd0-3: Concatenated disk drivers > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > isab0: at device 7.0 on pci0 > isa0: on isab0 > chip1: at device 7.1 on pci0 > vga-pci0: at device 10.0 on pci0 > xl0: <3Com 3c900-COMBO Etherlink XL> irq 19 at device 11.0 on pci0 > xl0: Ethernet address: 00:60:97:aa:3a:db > xl0: selecting 10baseT transceiver, half duplex > pci0: unknown card (vendor=0x1102, dev=0x0002) at 12.0 irq 18 > pci0: unknown card (vendor=0x1102, dev=0x7002) at 12.1 > ahc0: irq 17 at device 13.0 on pci0 > ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs > ahc1: irq 16 at device 14.0 on pci0 > ahc1: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > 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: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <4 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/15 bytes threshold > plip0: on ppbus 0 > lpt0: on ppbus 0 > lpt0: Interrupt-driven port > ppi0: on ppbus 0 > ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 > ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: routing 8254 via pin 2 > IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry by default > DUMMYNET initialized (990811) > Waiting 8 seconds for SCSI devices to settle > SMP: AP CPU #1 Launched! > Creating DISK da0 > Creating DISK da1 > Creating DISK da2 > Creating DISK da3 > sa0 at ahc1 bus 0 target 4 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 4.807MB/s transfers (4.807MHz, offset 8) > Creating DISK cd0 > Creating DISK cd1 > changing root device to da0s2a > cd1 at ahc1 bus 0 target 5 lun 0 > cd1: Removable CD-ROM SCSI-2 device > cd1: 10.000MB/s transfers (10.000MHz, offset 8) > cd1: Attempt to query device size failed: NOT READY, Medium not present > cd0 at ahc0 bus 0 target 6 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 10.000MB/s transfers (10.000MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium not present > da3 at ahc0 bus 0 target 3 lun 0 > da3: Fixed Direct Access SCSI-2 device > da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da3: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) > da1 at ahc0 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: 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: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) > da2 at ahc0 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) > ed0: remote transmit DMA failed to complete > ^^^^ > ed0: NIC memory corrupt - invalid packet length 11564 > ^^^^ > xl0: promiscuous mode enabled > > > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 0:26:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id 5B03E14A2D; Mon, 18 Oct 1999 00:26:20 -0700 (PDT) (envelope-from will@shadow.blackdawn.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=shadow.blackdawn.com) by neptune.psn.net with esmtp (PSN Internet Service 2.12 #3) id 11d7BS-0004ey-00; Mon, 18 Oct 1999 00:26:18 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id DAA64055; Mon, 18 Oct 1999 03:26:14 -0400 (EDT) (envelope-from will) From: Will Andrews Message-Id: <199910180726.DAA64055@shadow.blackdawn.com> Subject: pcic.ko & recent changes to sys/pccard/* To: imp@FreeBSD.ORG, current@FreeBSD.ORG Date: Mon, 18 Oct 1999 03:26:14 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm running FreeBSD 4.0-CURRENT on my laptop, a Dell Inspiron 7000. I successfully got my 3Com Megahertz 3C574B Ethernet PC-Card to work under 4.0-CURRENT (sources as of September 29, 1999 @ 10AM EDT, before marcel's infamous signal.h commits). CVSup'ing recently and finally successfully remaking world, I find that the sys/pccard/* has changed somewhat. Looking through the cvsweb changes, I see Warner's message about changing the PCMCIA support lines in the kernel configfile, so I did that. (see cvs log messages for src/sys/pccard/pccard.c,v 1.89) But it doesn't work. I'm assuming that my kernel config file's settings do not affect make world in any way, and thus it seems that pcic.ko is not being built by make world anymore... Thus, /dev/card0 is reported as "Device not configured" upon boot (because kldload can't find pcic.ko in /modules or elsewhere). What's going on here? Is the Makefile in src/sys/modules/pcic borked somehow (Makefile v1.9, 1999/08/28)? Doesn't seem likely, as the last time it was changed was for the $Id$ -> $FreeBSD$ change, which of course was mostly propagated by Peter Wemm. And it wasn't relevant to pcic anyway. So where is it breaking? It's either breaking in a Makefile I missed somewhere, or the pcic code is broken, or I'm broken (being egotistical, I doubt it ;). --Will Andrews To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 0:36:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6]) by hub.freebsd.org (Postfix) with ESMTP id 3965A14EA1 for ; Mon, 18 Oct 1999 00:35:50 -0700 (PDT) (envelope-from shigeru@iij.ad.jp) Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8]) by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id QAA04622 for ; Mon, 18 Oct 1999 16:35:43 +0900 (JST) Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id QAA19592 for ; Mon, 18 Oct 1999 16:35:43 +0900 (JST) Received: from mercury.iij.ad.jp (mercury.iij.ad.jp [192.168.4.89]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id QAA21716 for ; Mon, 18 Oct 1999 16:35:43 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by mercury.iij.ad.jp (8.8.5/3.5W) with ESMTP id QAA12624 for ; Mon, 18 Oct 1999 16:35:42 +0900 (JST) To: current@freebsd.org Subject: how to allocate a resource at new-bus architecture? X-Mailer: Mew version 1.93b38 on XEmacs 21.2 (Aeolus) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991018163541T.shigeru@iij.ad.jp> Date: Mon, 18 Oct 1999 16:35:41 +0900 From: YAMAMOTO Shigeru X-Dispatcher: imput version 980522 Lines: 34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, all. I have a question about a resource allocation at a child device of PCI device. I'm thinking about to write a CardBud device driver. CardBus is attached at PCI bus. So I think CardBus is a child device of PCI device. Before revision 1.122 of @src/sys/pci/pci.c, I can allocate a resouce when I set rid 0 and call bus_alloc_resource(). CardBus driver is a child of PCI driver, so bus_alloc_resource(), called at CardBus driver, call pci_alloc_resource(). When rid == 0, pci_alloc_resource() call an resource allocation method of parent bus. But revision 1.122 or later, pci_alloc_resource() was rewritten very simply. pci_alloc_resource() only call resource_list_alloc() and resource_list_alloc() returns 0 when requested resource is not registered nor reserved. It seems me new PCI driver assume all resources are assigned by BIOS. But a BIOS of my notebood, VAIO 818/Phoenix BIOS, does not assign a resource for a CardBus socket/ExCA base address register. #of cource, I set a BIOS as 'Plug & Play O/S: No'. I can't allocate a resource using bus_alloc_resource(). How to allocate a resource for a device which resources are not assigned by BIOS? What is a right way to allocate a resource in a new-bus device driver? Thanks, ------- YAMAMOTO Shigeru Internet Initiative Japan Inc. Network Engineering Div. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 1:25:41 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 CBA2014D8C for ; Mon, 18 Oct 1999 01:25:33 -0700 (PDT) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id KAA07782; Mon, 18 Oct 1999 10:25:14 +0200 (CEST) Date: Mon, 18 Oct 1999 10:25:14 +0200 From: Martin Cracauer To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Is it just me or is sys/signal.h just completely screwed up now? Message-ID: <19991018102513.A7736@cons.org> References: <19538.940215318@localhost> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=X1bOJ3K7DJ5YkBrT X-Mailer: Mutt 0.95.1i In-Reply-To: <19538.940215318@localhost>; from Jordan K. Hubbard on Sun, Oct 17, 1999 at 07:55:18PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii In <19538.940215318@localhost>, Jordan K. Hubbard wrote: > I've got a box running yesterday's -current and it can't compile [...] > #if defined(_P1003_1B_VISIBLE) || defined(KERNEL) > .. > #endif I use the appended C file and compilation shell script to test include file changes. I recommend it to everyone working on headers. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=run #! /bin/sh set -e set -x cc -D_ANSI_SOURCE -Wall -Werror -o/dev/null test1.c cc -D_POSIX_SOURCE -Wall -Werror -o/dev/null test1.c cc -Wall -Werror -o/dev/null test1.c --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="test1.c" #include int main(void) { return 0; } --X1bOJ3K7DJ5YkBrT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 1:38: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 760D214BF9 for ; Mon, 18 Oct 1999 01:38:46 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-lind-6.netcologne.de [195.14.250.6]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id KAA24095; Mon, 18 Oct 1999 10:38:43 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id KAA02398; Mon, 18 Oct 1999 10:38:59 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Mon, 18 Oct 1999 10:38:59 +0200 (CEST) Message-Id: <199910180838.KAA02398@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: mnewell@newell.arlington.va.us Cc: freebsd-current@FreeBSD.ORG In-reply-to: (message from Mike Newell on Sun, 17 Oct 1999 16:38:53 -0400 (EDT)) Subject: Re: Signal 12 during build of -current Reply-To: van.woerkom@netcologne.de References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm installing -current on a FreeBSD-3.3-stable system. I've done the sup > (which succeeded with no problems). When I try the "make buildworld" I > get "signal 12" crashes during the gcc lib build. In specific: I had the same problem (see my mail from 12th October). One of the present requirements is to build, install and boot the new kernel before doing the make world. Please read src/UPDATING, an excellent reference for major events in the source tree: 19990929: The sigset_t datatype has been changed from an integral type to a compound type and can hold 128 signals. Syscalls directly or indirectly using the new sigset_t have been added as to maintain compatible with existing binaries. A new kernel must be made and installed and booted with before a make world can be done. As you start from a v3 system, the v4 kernel might not work with v3 user land. I would suggest to grab an older v4 tree (e.g. as of September, 14th) and to move your v3 to that older v4 first. If this succeded, grab the latest v4 and try to jump over the sigset_t hurdle as described. 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 Oct 18 1:41:17 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 0DE8314BF9 for ; Mon, 18 Oct 1999 01:41:12 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-lind-6.netcologne.de [195.14.250.6]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id KAA24332; Mon, 18 Oct 1999 10:41:11 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id KAA02406; Mon, 18 Oct 1999 10:41:26 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Mon, 18 Oct 1999 10:41:26 +0200 (CEST) Message-Id: <199910180841.KAA02406@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: sthaug@nethelp.no Cc: freebsd-current@FreeBSD.ORG In-reply-to: <38975.940094971@verdi.nethelp.no> (sthaug@nethelp.no) Subject: Re: current unable to attach USB, Power Mgmt, sound Reply-To: van.woerkom@netcologne.de References: <38975.940094971@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > pcm0: unable to map register space > > device_probe_and_attach: pcm0 attach returned 6 > > This is an Abit BP6 board with two Celeron 366, 256 MByte memory, one > Soundblaster PCI 128 (pcm0) and one Hoontech (pcm1) sound card. Below is > the complete dmesg from today's current, and the kernel config. I reported the same problem. PCI 128 uses the same ES1370 chip as the Audio PCI. 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 Oct 18 1:44: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 6A6FD14E96 for ; Mon, 18 Oct 1999 01:44:10 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id KAA43372; Mon, 18 Oct 1999 10:43:59 +0200 (CEST) (envelope-from des) To: Jacques Vidrine Cc: Julian Elischer , freebsd-current@FreeBSD.ORG Subject: Re: QIC ft0 driver support in 4.0-CURRENT gone? References: <19991015224553.5494A1D65@bone.nectar.com> From: Dag-Erling Smorgrav Date: 18 Oct 1999 10:43:59 +0200 In-Reply-To: Jacques Vidrine's message of "Fri, 15 Oct 1999 17:45:53 -0500" Message-ID: Lines: 12 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jacques Vidrine writes: > I have one (colorado thing). I _will not_ adopt it :-) but I'd > happily send it to a committer that wanted to support it. I haven't > used it in years, but AFAIK it still works. I have an old Conner drive and three 40MB tapes which I will happily donate to any poor S.O.B. who hates life enough to take it upon himself to maintain the ft0 driver. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 1:47:42 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 2125D14E96 for ; Mon, 18 Oct 1999 01:47:39 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-lind-6.netcologne.de [195.14.250.6]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id KAA24782; Mon, 18 Oct 1999 10:47:38 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id KAA02419; Mon, 18 Oct 1999 10:47:54 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Mon, 18 Oct 1999 10:47:54 +0200 (CEST) Message-Id: <199910180847.KAA02419@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: jkh@zippy.cdrom.com Cc: current@FreeBSD.ORG In-reply-to: <19538.940215318@localhost> (jkh@zippy.cdrom.com) Subject: Re: Is it just me or is sys/signal.h just completely screwed up now? Reply-To: van.woerkom@netcologne.de References: <19538.940215318@localhost> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got a box running yesterday's -current and it can't compile > or install things like XFree86 or ImageMagik due to syntax errors > in this file. See the mails from October 15th, esp. the ones from Marcel Moolenaar and Sheldon Hearn. It seems this patch has not been commited yet. Anyone got problems? 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 Oct 18 1:53: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 3B3C314BF9 for ; Mon, 18 Oct 1999 01:53:11 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA21887; Mon, 18 Oct 1999 01:52:57 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: van.woerkom@netcologne.de Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: Is it just me or is sys/signal.h just completely screwed up now? In-reply-to: Your message of "Mon, 18 Oct 1999 10:47:54 +0200." <199910180847.KAA02419@oranje.my.domain> Date: Mon, 18 Oct 1999 01:52:57 -0700 Message-ID: <21883.940236777@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > See the mails from October 15th, esp. the ones from Marcel Moolenaar > and Sheldon Hearn. I did, but they don't fix the XFree86 3.3.5 build problem. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 2:11:14 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 A7FC51501A for ; Mon, 18 Oct 1999 02:11: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.040 #1) id 11d8oT-0001cx-00; Mon, 18 Oct 1999 11:10:41 +0200 From: Sheldon Hearn To: "Jordan K. Hubbard" Cc: van.woerkom@netcologne.de, current@FreeBSD.ORG Subject: Re: Is it just me or is sys/signal.h just completely screwed up now? In-reply-to: Your message of "Mon, 18 Oct 1999 01:52:57 MST." <21883.940236777@localhost> Date: Mon, 18 Oct 1999 11:10:41 +0200 Message-ID: <6258.940237841@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Oct 1999 01:52:57 MST, "Jordan K. Hubbard" wrote: > > See the mails from October 15th, esp. the ones from Marcel Moolenaar > > and Sheldon Hearn. > > I did, but they don't fix the XFree86 3.3.5 build problem. Hmmm, that's odd, because the patch Marcel sent me was later committed to signal.h as rev 1.22 -- and it did indeed fix the Xfree86 3.3.5 ``make install'' problem for me. 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 Oct 18 2:39:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 83F5714CEF for ; Mon, 18 Oct 1999 02:39:16 -0700 (PDT) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999070600) with ESMTP id LAA20710; Mon, 18 Oct 1999 11:39:04 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id LAA20058; Mon, 18 Oct 1999 11:38:58 +0200 (CEST) Received: from wurzelausix.cs.uni-sb.de (IDENT:JYzDDPKYRC7F0ZlwqDLO1H2Gg+EI8OnN@localhost [127.0.0.1]) by wurzelausix.cs.uni-sb.de (8.9.1/8.9.1/wjp-SVR4/1998063000) with ESMTP id LAA27246; Mon, 18 Oct 1999 11:38:56 +0200 (CEST) Message-Id: <199910180938.LAA27246@wurzelausix.cs.uni-sb.de> Date: Mon, 18 Oct 1999 11:38:51 +0200 (CEST) From: Alexander Leidinger Subject: Re: Is it just me or is sys/signal.h just completely screwed up now ? To: jkh@zippy.cdrom.com Cc: current@FreeBSD.ORG In-Reply-To: <21883.940236777@localhost> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Oct, Jordan K. Hubbard wrote: >> See the mails from October 15th, esp. the ones from Marcel Moolenaar >> and Sheldon Hearn. > > I did, but they don't fix the XFree86 3.3.5 build problem. I build 3.3.5 at Oct 16th (~8pm CET, cvsup & world ~3pm?), no 3rd-party patches applied. Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ WJPServer.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 Oct 18 2:41:13 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 60F7514CEF for ; Mon, 18 Oct 1999 02:41:10 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-lind-6.netcologne.de [195.14.250.6]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id LAA28904; Mon, 18 Oct 1999 11:41:05 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id LAA02982; Mon, 18 Oct 1999 11:41:21 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Mon, 18 Oct 1999 11:41:21 +0200 (CEST) Message-Id: <199910180941.LAA02982@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: sheldonh@uunet.co.za Cc: jkh@zippy.cdrom.com, van.woerkom@netcologne.de, current@FreeBSD.ORG In-reply-to: <6258.940237841@axl.noc.iafrica.com> (message from Sheldon Hearn on Mon, 18 Oct 1999 11:10:41 +0200) Subject: Re: Is it just me or is sys/signal.h just completely screwed up now? Reply-To: van.woerkom@netcologne.de References: <6258.940237841@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmmm, that's odd, because the patch Marcel sent me was later committed > to signal.h as rev 1.22 Thanks. I did falsely check the log for src/include/signal.h instead of the one in src/sys/sys > and it did indeed fix the Xfree86 3.3.5 ``make install'' problem for me. That's what I understood from your post and someone else's post (Amancio?). I myself have some important stuff to finish, and can't risk X not working, so I will not test this fix out before. 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 Oct 18 3:31: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 264F414BCF for ; Mon, 18 Oct 1999 03:31:36 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id DAA22275; Mon, 18 Oct 1999 03:31:15 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Sheldon Hearn Cc: "Jordan K. Hubbard" , van.woerkom@netcologne.de, current@FreeBSD.ORG Subject: Re: Is it just me or is sys/signal.h just completely screwed up now? In-reply-to: Your message of "Mon, 18 Oct 1999 11:10:41 +0200." <6258.940237841@axl.noc.iafrica.com> Date: Mon, 18 Oct 1999 03:31:15 -0700 Message-ID: <22271.940242675@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmmm, that's odd, because the patch Marcel sent me was later committed > to signal.h as rev 1.22 -- and it did indeed fix the Xfree86 3.3.5 > ``make install'' problem for me. Hmmmm.. root@test-> ident /usr/include/sys/signal.h /usr/include/sys/signal.h: $FreeBSD: src/sys/sys/signal.h,v 1.22 1999/10/16 12:18:10 marcel Exp $ Ummm. Now I can't reproduce it, and I'd swear this was the same file as before! Erm. Maybe it's just too damn late. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 5:58:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from ints.ru (ints.ru [194.67.173.1]) by hub.freebsd.org (Postfix) with ESMTP id C09131511A for ; Mon, 18 Oct 1999 05:58:19 -0700 (PDT) (envelope-from ilmar@ints.ru) Received: (from uucp@localhost) by ints.ru (8.9.2/8.9.2) id QAA28073; Mon, 18 Oct 1999 16:58:14 +0400 (MSD) Received: from ws-ilmar.ints.ru(194.67.173.16) via SMTP by ints.ru, id smtpdB28071; Mon Oct 18 16:58:13 1999 Received: from localhost (localhost [127.0.0.1]) by ws-ilmar.ints.ru (8.9.3/8.9.3) with ESMTP id QAA31055; Mon, 18 Oct 1999 16:58:09 +0400 (MSD) Date: Mon, 18 Oct 1999 16:58:08 +0400 (MSD) From: "Ilmar S. Habibulin" To: "Daniel C. Sobral" Cc: freebsd-current@FreeBSD.ORG Subject: Re: jumping from 3.1 to 4.0 In-Reply-To: <38096F7E.3065767E@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1355534614-940251488=:21590" 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-1355534614-940251488=:21590 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 17 Oct 1999, Daniel C. Sobral wrote: > You could do that, and it would load your kernel. Your best option, > though, it's to jump first to 3.3-stable. I've got the -currents' snap loader for the 10th of october. It works fine - i've managed to load 3.x and 4.x kernels. > But before you do that, could you please give me the error log? > Loader should have *not* been affected by the signal changes! I don't know. I think there was some headers include absence. Error log is in attachment. --0-1355534614-940251488=:21590 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=log Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=log PT09PiBmaWNsDQpjYyAtTyAtcGlwZSAtSS91c3Ivc3JjL3N5cy9ib290L2Zp Y2wgLURGSUNMX1RSQUNFIC1jIC91c3Ivc3JjL3N5cy9ib290L2ZpY2wvZGlj dC5jIC1vIGRpY3Qubw0KY2MgLU8gLXBpcGUgLUkvdXNyL3NyYy9zeXMvYm9v dC9maWNsIC1ERklDTF9UUkFDRSAtYyAvdXNyL3NyYy9zeXMvYm9vdC9maWNs L2ZpY2wuYyAtbyBmaWNsLm8NCmNjIC1PIC1waXBlIC1JL3Vzci9zcmMvc3lz L2Jvb3QvZmljbCAtREZJQ0xfVFJBQ0UgLWMgL3Vzci9zcmMvc3lzL2Jvb3Qv ZmljbC9tYXRoNjQuYyAtbyBtYXRoNjQubw0KY2MgLU8gLXBpcGUgLUkvdXNy L3NyYy9zeXMvYm9vdC9maWNsIC1ERklDTF9UUkFDRSAtYyAvdXNyL3NyYy9z eXMvYm9vdC9maWNsL3N0YWNrLmMgLW8gc3RhY2subw0KY2MgLU8gLXBpcGUg LUkvdXNyL3NyYy9zeXMvYm9vdC9maWNsIC1ERklDTF9UUkFDRSAtYyAvdXNy L3NyYy9zeXMvYm9vdC9maWNsL3N5c2RlcC5jIC1vIHN5c2RlcC5vDQpjYyAt TyAtcGlwZSAtSS91c3Ivc3JjL3N5cy9ib290L2ZpY2wgLURGSUNMX1RSQUNF IC1jIC91c3Ivc3JjL3N5cy9ib290L2ZpY2wvdm0uYyAtbyB2bS5vDQpjYyAt TyAtcGlwZSAtSS91c3Ivc3JjL3N5cy9ib290L2ZpY2wgLURGSUNMX1RSQUNF IC1jIC91c3Ivc3JjL3N5cy9ib290L2ZpY2wvd29yZHMuYyAtbyB3b3Jkcy5v DQooY2QgL3Vzci9zcmMvc3lzL2Jvb3QvZmljbC9zb2Z0d29yZHM7IGNhdCBz b2Z0Y29yZS5mciBqaGxvY2FsLmZyIG1hcmtlci5mciBmcmVlYnNkLmZyIGZp Y2xsb2NhbC5mciAgaWZicmFjay5mciB8IGF3ayAtZiBzb2Z0Y29yZS5hd2sp ID4gc29mdGNvcmUuYw0KY2MgLU8gLXBpcGUgLUkvdXNyL3NyYy9zeXMvYm9v dC9maWNsIC1ERklDTF9UUkFDRSAtYyBzb2Z0Y29yZS5jIC1vIHNvZnRjb3Jl Lm8NCmJ1aWxkaW5nIHN0YW5kYXJkIGZpY2wgbGlicmFyeQ0KcmFubGliIGxp YmZpY2wuYQ0KPT09PiBpMzg2DQo9PT0+IGkzODYvbWJyDQooY2QgL3Vzci9z cmMvc3lzL2Jvb3QvaTM4Ni9tYnI7IG00IG1ici5tNCBtYnIucykgfCAgYXMg IC1vIG1ici5vDQpsZCAtTiAtZSBzdGFydCAtVHRleHQgMHg2MDAgLW8gbWJy Lm91dCBtYnIubw0Kb2JqY29weSAtUyAtTyBiaW5hcnkgbWJyLm91dCBtYnIN Cj09PT4gaTM4Ni9ib290MA0KKGNkIC91c3Ivc3JjL3N5cy9ib290L2kzODYv Ym9vdDA7IG00IC1ERkxBR1M9MHhmIC1EVElDS1M9MHhiNiAgYm9vdDAubTQg Ym9vdDAucykgfCBhcyAgLW8gYm9vdDAubw0KbGQgLU4gLWUgc3RhcnQgLVR0 ZXh0IDB4NjAwIC1vIGJvb3QwLm91dCBib290MC5vDQpvYmpjb3B5IC1TIC1P IGJpbmFyeSBib290MC5vdXQgYm9vdDANCj09PT4gaTM4Ni9rZ3psZHINCihj ZCAvdXNyL3NyYy9zeXMvYm9vdC9pMzg2L2tnemxkcjsgbTQgIC1EU0lPUFJU PTB4M2Y4IC91c3Ivc3JjL3N5cy9ib290L2kzODYva2d6bGRyL3N0YXJ0LnMp IHwgYXMgIC1vIHN0YXJ0Lm8NCmNjIC1mbm8tYnVpbHRpbiAtTyAtREtaSVAg ICAtYyAvdXNyL3NyYy9zeXMvYm9vdC9pMzg2L2tnemxkci9ib290LmMNCmNj IC1mbm8tYnVpbHRpbiAtTyAtREtaSVAgICAtYyAvdXNyL3NyYy9zeXMvYm9v dC9pMzg2L2tnemxkci8uLi8uLi8uLi9rZXJuL2luZmxhdGUuYw0KY2MgLWZu by1idWlsdGluIC1PIC1ES1pJUCAgIC1jIC91c3Ivc3JjL3N5cy9ib290L2kz ODYva2d6bGRyL2xpYi5jDQooY2QgL3Vzci9zcmMvc3lzL2Jvb3QvaTM4Ni9r Z3psZHI7IG00ICAtRFNJT1BSVD0weDNmOCAvdXNyL3NyYy9zeXMvYm9vdC9p Mzg2L2tnemxkci9jcnQucykgfCBhcyAgLW8gY3J0Lm8NCihjZCAvdXNyL3Ny Yy9zeXMvYm9vdC9pMzg2L2tnemxkcjsgbTQgIC1EU0lPUFJUPTB4M2Y4IC91 c3Ivc3JjL3N5cy9ib290L2kzODYva2d6bGRyL3Npby5zKSB8IGFzICAtbyBz aW8ubw0KY2MgLW5vc3RkbGliIC1zdGF0aWMgLXIgLW8ga2d6bGRyLm8gc3Rh cnQubyBib290Lm8gaW5mbGF0ZS5vIGxpYi5vIGNydC5vIHNpby5vDQo9PT0+ IGkzODYvYnR4DQo9PT0+IGkzODYvYnR4L2J0eA0KKGNkIC91c3Ivc3JjL3N5 cy9ib290L2kzODYvYnR4L2J0eDsgbTQgIGJ0eC5tNCBidHgucykgfCAgYXMg IC1vIGJ0eC5vDQpsZCAtTiAtZSBzdGFydCAtVHRleHQgMHg5MDAwIC1vIGJ0 eC5vdXQgYnR4Lm8NCm9iamNvcHkgLVMgLU8gYmluYXJ5IGJ0eC5vdXQgYnR4 DQo9PT0+IGkzODYvYnR4L2J0eGxkcg0KY2MgIC0tYXNzZW1ibGVyLXdpdGgt Y3BwIC1jIC1vIGJ0eGxkci5vIC91c3Ivc3JjL3N5cy9ib290L2kzODYvYnR4 L2J0eGxkci9idHhsZHIucw0KbGQgLU4gLWUgc3RhcnQgLVR0ZXh0IDB4MTAw MDAwIC1vIGJ0eGxkci5vdXQgYnR4bGRyLm8NCm9iamNvcHkgLVMgLU8gYmlu YXJ5IGJ0eGxkci5vdXQgYnR4bGRyDQo9PT0+IGkzODYvYnR4L2xpYg0KYXMg IC1lbGYgLW8gYnR4Y3N1Lm8gL3Vzci9zcmMvc3lzL2Jvb3QvaTM4Ni9idHgv bGliL2J0eGNzdS5zDQphcyAgLWVsZiAtbyBidHhzeXMubyAvdXNyL3NyYy9z eXMvYm9vdC9pMzg2L2J0eC9saWIvYnR4c3lzLnMNCmFzICAtZWxmIC1vIGJ0 eHY4Ni5vIC91c3Ivc3JjL3N5cy9ib290L2kzODYvYnR4L2xpYi9idHh2ODYu cw0KbGQgIC1lbGYgLWkgLW8gY3J0MC5vIGJ0eGNzdS5vIGJ0eHN5cy5vIGJ0 eHY4Ni5vIA0KPT09PiBpMzg2L2Jvb3QyDQooY2QgL3Vzci9zcmMvc3lzL2Jv b3QvaTM4Ni9ib290MjsgbTQgLURGTEFHUz0wIGJvb3QxLm00IGJvb3QxLnMp IHwgIGFzICAtbyBib290MS5vDQpsZCAtbm9zdGRsaWIgLXN0YXRpYyAtTiAt ZSBzdGFydCAtVHRleHQgMHg3YzAwIC1vIGJvb3QxLm91dCBib290MS5vDQpv Ympjb3B5IC1TIC1PIGJpbmFyeSBib290MS5vdXQgYm9vdDENCmRkIGlmPS9k ZXYvemVybyBvZj1ib290Mi5sZHIgYnM9NTEyIGNvdW50PTEgMj4vZGV2L251 bGwNCmNjIC1lbGYgLUkvdXNyL3NyYy9zeXMvYm9vdC9pMzg2L2Jvb3QyLy4u L2J0eC9saWIgLUkuIC1mbm8tYnVpbHRpbiAgLU8gLW1hbGlnbi1mdW5jdGlv bnM9MCAtbWFsaWduLWp1bXBzPTAgLW1hbGlnbi1sb29wcz0wIC1tcnRkICAt V2FsbCAtV2FnZ3JlZ2F0ZS1yZXR1cm4gLVdiYWQtZnVuY3Rpb24tY2FzdCAt V2Nhc3QtYWxpZ24gIC1XbWlzc2luZy1kZWNsYXJhdGlvbnMgLVdtaXNzaW5n LXByb3RvdHlwZXMgLVduZXN0ZWQtZXh0ZXJucyAgLVdwb2ludGVyLWFyaXRo IC1Xc2hhZG93IC1Xc3RyaWN0LXByb3RvdHlwZXMgLVd3cml0ZS1zdHJpbmdz ICAgLWMgL3Vzci9zcmMvc3lzL2Jvb3QvaTM4Ni9ib290Mi9ib290Mi5jDQoo Y2QgL3Vzci9zcmMvc3lzL2Jvb3QvaTM4Ni9ib290MjsgbTQgLURTSU9QUlQ9 MHgzZjggIC1EU0lPRk1UPTB4MyAgLURTSU9TUEQ9OTYwMCBzaW8ucykgfCAg YXMgIC1vIHNpby5vDQpsZCAtbm9zdGRsaWIgLXN0YXRpYyAtTiAtVHRleHQg MHgxMDAwIC1vIGJvb3QyLm91dCAgL3Vzci9vYmovdXNyL3NyYy9zeXMvYm9v dC9pMzg2L2Jvb3QyLy4uL2J0eC9saWIvY3J0MC5vIGJvb3QyLm8gc2lvLm8N Cm9iamNvcHkgLVMgLU8gYmluYXJ5IGJvb3QyLm91dCBib290Mi5iaW4NCmJ0 eGxkIC12IC1FIDB4MTAwMCAtZiBiaW4gLWIgL3Vzci9vYmovdXNyL3NyYy9z eXMvYm9vdC9pMzg2L2Jvb3QyLy4uL2J0eC9idHgvYnR4IC1sIGJvb3QyLmxk ciAgLW8gYm9vdDIubGQgLVAgMSBib290Mi5iaW4NCmtlcm5lbDogdmVyPTEu MDEgc2l6ZT03MDAgbG9hZD05MDAwIGVudHJ5PTkwMTAgbWFwPTE2TSBwZ2N0 bD0xOjENCmNsaWVudDogZm10PWJpbiBzaXplPTE0NTggdGV4dD0wIGRhdGE9 MCBic3M9MCBlbnRyeT0wDQpvdXRwdXQ6IGZtdD1iaW4gc2l6ZT0xZDU4IHRl eHQ9MjAwIGRhdGE9MWI1OCBvcmc9MCBlbnRyeT0wDQoxNjggYnl0ZXMgYXZh aWxhYmxlDQpkZCBpZj1ib290Mi5sZCBvZj1ib290MiBvYnM9NzY4MCBjb252 PW9zeW5jIDI+L2Rldi9udWxsDQo9PT0+IGkzODYvbGliaTM4Ng0KY2MgLU8g LXBpcGUgLUkvdXNyL3NyYy9zeXMvYm9vdC9pMzg2L2xpYmkzODYvLi4vLi4v Y29tbW9uIC1JL3Vzci9zcmMvc3lzL2Jvb3QvaTM4Ni9saWJpMzg2Ly4uL2J0 eC9saWIgIC1JL3Vzci9zcmMvc3lzL2Jvb3QvaTM4Ni9saWJpMzg2Ly4uLy4u Ly4uIC1JLiAtRENPTVBPUlQ9MHgzZjggLURDT01TUEVFRD05NjAwIC1EVEVS TV9FTVUgLWMgL3Vzci9zcmMvc3lzL2Jvb3QvaTM4Ni9saWJpMzg2L2FvdXRf ZnJlZWJzZC5jIC1vIGFvdXRfZnJlZWJzZC5vDQoqKiogRXJyb3IgY29kZSAx DQoNClN0b3AuDQoqKiogRXJyb3IgY29kZSAxDQoNClN0b3AuDQoqKiogRXJy b3IgY29kZSAxDQoNClN0b3AuDQo= --0-1355534614-940251488=:21590 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="log.err" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="log.err" SW4gZmlsZSBpbmNsdWRlZCBmcm9tIC91c3Ivc3JjL3N5cy9ib290L2kzODYv bGliaTM4Ni8uLi8uLi8uLi9zeXMvc2lnbmFsLmg6MjM2LA0KICAgICAgICAg ICAgICAgICBmcm9tIC91c3Ivc3JjL3N5cy9ib290L2kzODYvbGliaTM4Ni8u Li8uLi8uLi9zeXMvcGFyYW0uaDo5MCwNCiAgICAgICAgICAgICAgICAgZnJv bSAvdXNyL3NyYy9zeXMvYm9vdC9pMzg2L2xpYmkzODYvYW91dF9mcmVlYnNk LmM6Mjk6DQovdXNyL3NyYy9zeXMvYm9vdC9pMzg2L2xpYmkzODYvLi4vLi4v Li4vc3lzL3Vjb250ZXh0Lmg6MzQ6IG1hY2hpbmUvdWNvbnRleHQuaDogTm8g c3VjaCBmaWxlIG9yIGRpcmVjdG9yeQ0KSW4gZmlsZSBpbmNsdWRlZCBmcm9t IC91c3Ivc3JjL3N5cy9ib290L2kzODYvbGliaTM4Ni8uLi8uLi8uLi9zeXMv c2lnbmFsLmg6MjM2LA0KICAgICAgICAgICAgICAgICBmcm9tIC91c3Ivc3Jj L3N5cy9ib290L2kzODYvbGliaTM4Ni8uLi8uLi8uLi9zeXMvcGFyYW0uaDo5 MCwNCiAgICAgICAgICAgICAgICAgZnJvbSAvdXNyL3NyYy9zeXMvYm9vdC9p Mzg2L2xpYmkzODYvYW91dF9mcmVlYnNkLmM6Mjk6DQovdXNyL3NyYy9zeXMv Ym9vdC9pMzg2L2xpYmkzODYvLi4vLi4vLi4vc3lzL3Vjb250ZXh0Lmg6NDY6 IHBhcnNlIGVycm9yIGJlZm9yZSBgbWNvbnRleHRfdCcNCi91c3Ivc3JjL3N5 cy9ib290L2kzODYvbGliaTM4Ni8uLi8uLi8uLi9zeXMvdWNvbnRleHQuaDo0 Njogd2FybmluZzogbm8gc2VtaWNvbG9uIGF0IGVuZCBvZiBzdHJ1Y3Qgb3Ig dW5pb24NCi91c3Ivc3JjL3N5cy9ib290L2kzODYvbGliaTM4Ni8uLi8uLi8u Li9zeXMvdWNvbnRleHQuaDo1MTogcGFyc2UgZXJyb3IgYmVmb3JlIGB9Jw0K L3Vzci9zcmMvc3lzL2Jvb3QvaTM4Ni9saWJpMzg2Ly4uLy4uLy4uL3N5cy91 Y29udGV4dC5oOjUxOiB3YXJuaW5nOiBkYXRhIGRlZmluaXRpb24gaGFzIG5v IHR5cGUgb3Igc3RvcmFnZSBjbGFzcw0K --0-1355534614-940251488=:21590-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 6:40: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 929E314C13 for ; Mon, 18 Oct 1999 06:40:30 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id JAA27263 for current@freebsd.org; Mon, 18 Oct 1999 09:40:29 -0400 (EDT) (envelope-from luoqi) Date: Mon, 18 Oct 1999 09:40:29 -0400 (EDT) From: Luoqi Chen Message-Id: <199910181340.JAA27263@lor.watermarkgroup.com> To: current@freebsd.org Subject: aic driver camified Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After the recent signal related changes, the pre-cam kernel I saved a long time ago no longer works with (even statically compiled) user applications, which meant I had no way to access my files on an old disk hanging off an aic6360 card. So I decided to bite the bullet and camify the aic driver myself (I've long given up hope someone else would do it.) The source is at http://www.freebsd.org/~luoqi/aic. Copy the source files into sys/dev/aic, apply the patch files.diff to sys/conf/files. Don't forget to add the controller aic0 line back to your config file. Since I don't have *any* documentation on the chip or card, except for the existing source code (FreeBSD/NetBSD/Linux), and my knowledge of our cam implementation is quite limited, so consider this code extremely experimental and use at your own risk. DMA is not supported, sync transfer is supported but not tested, neither pnp nor pccard is supported. My card doesn't support any of these, so there's not much I could do, I hope sopme of you could fill in the blanks. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 7:26: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id 602B114A16 for ; Mon, 18 Oct 1999 07:26:02 -0700 (PDT) (envelope-from bleez@netaxs.com) Received: from unix3.netaxs.com (mail@unix3.netaxs.com [207.8.186.5]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id KAA23926 for ; Mon, 18 Oct 1999 10:26:01 -0400 (EDT) Received: (from bleez@localhost) by unix3.netaxs.com (8.8.7/8.8.4) id KAA15365; Mon, 18 Oct 1999 10:26:01 -0400 (EDT) Date: Mon, 18 Oct 1999 10:26:00 -0400 (EDT) From: Bryan Liesner To: freebsd-current@freebsd.org Subject: Promise Ultra66 IDE adapter Message-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 the Promise Ultra66 IDE adapter supported? I cannot get 3.3 or 4.0 kernels to see the card at all. The mailing list archive details are sketchy at best. The pci_ide source seems to only do support for the Ultra33. Thanks, Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 7:42:31 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 518D714BC2 for ; Mon, 18 Oct 1999 07:42:18 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 84278 invoked by uid 1001); 18 Oct 1999 14:42:12 +0000 (GMT) To: van.woerkom@netcologne.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: current unable to attach USB, Power Mgmt, sound From: sthaug@nethelp.no In-Reply-To: Your message of "Mon, 18 Oct 1999 10:41:26 +0200 (CEST)" References: <199910180841.KAA02406@oranje.my.domain> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 18 Oct 1999 16:42:12 +0200 Message-ID: <84276.940257732@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > pcm0: unable to map register space > > > device_probe_and_attach: pcm0 attach returned 6 > > > > This is an Abit BP6 board with two Celeron 366, 256 MByte memory, one > > Soundblaster PCI 128 (pcm0) and one Hoontech (pcm1) sound card. Below is > > the complete dmesg from today's current, and the kernel config. > > I reported the same problem. PCI 128 uses the same ES1370 chip as the > Audio PCI. The following patch from Doug Rabson fixed the USB and sound problem for me. It has already bee committed to -current. It did not fix the power management (intpm0) problem. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- RCS file: /home/ncvs/src/sys/pci/pci.c,v retrieving revision 1.122 diff -u -r1.122 pci.c --- pci.c 1999/10/14 21:38:31 1.122 +++ pci.c 1999/10/16 19:11:27 @@ -1032,7 +1032,7 @@ #endif if (type == SYS_RES_IOPORT && !pci_porten(cfg)) continue; - if (type == SYS_RES_IOPORT && !pci_memen(cfg)) + if (type == SYS_RES_MEMORY && !pci_memen(cfg)) continue; resource_list_add(rl, type, reg, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 8:30:42 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 73D2E14EF7 for ; Mon, 18 Oct 1999 08:30:37 -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 JAA05953; Mon, 18 Oct 1999 09:30:36 -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 JAA04534; Mon, 18 Oct 1999 09:30:08 -0600 (MDT) Message-Id: <199910181530.JAA04534@harmony.village.org> To: Will Andrews Subject: Re: pcic.ko & recent changes to sys/pccard/* Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 18 Oct 1999 03:26:14 EDT." <199910180726.DAA64055@shadow.blackdawn.com> References: <199910180726.DAA64055@shadow.blackdawn.com> Date: Mon, 18 Oct 1999 09:30:08 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199910180726.DAA64055@shadow.blackdawn.com> Will Andrews writes: : But it doesn't work. I'm assuming that my kernel : config file's settings do not affect make world in any way, : and thus it seems that pcic.ko is not being built by make world : anymore... What doesn't work? Can you give some error messages as well as a complete dmesg? : What's going on here? Is the Makefile in src/sys/modules/pcic : borked somehow (Makefile v1.9, 1999/08/28)? Doesn't seem : likely, as the last time it was changed was for the $Id$ -> : $FreeBSD$ change, which of course was mostly propagated : by Peter Wemm. And it wasn't relevant to pcic anyway. The pcic module is borked and hasn't worked for a long time. I'm off to FreeBSD con here in a few minutes, but will read your reply when I get there. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 9: 9: 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 2F6AA14E25; Mon, 18 Oct 1999 09:09:03 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p28-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.157]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id BAA18839; Tue, 19 Oct 1999 01:08:54 +0900 (JST) Message-ID: <380B41FF.C4CB44D8@newsguy.com> Date: Tue, 19 Oct 1999 00:51:27 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Will Andrews Cc: current@FreeBSD.ORG, marcel@freebsd.org, msmith@freebsd.org, peter@freebsd.org Subject: Re: -CURRENT `make world` fails.. (ucontext.h?) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [cc'ing Marcel just in case he wants to volunteer any suggestion... :)] [also cc'ing Mike Smith since aout_freebsd.c seems to be his] [and cc'ing Peter too, since he dabbed a lot in that file] Will Andrews wrote: > ... > Is there any additional information I can provide (I noticed a related thread, > but DCS's reply didn't seem to help..)? I'm tracking this now. Well, I'll start tracking as soon as I finish my mail. I suggested first upgrading to 3.3 (or even 3.2), and only then to current. That _will_ work, as it will upgrade the loader. Alas, you need not even go to such pains. Just cvsup to -stable, cd /sys/boot; make depend && make all install, and then cvsup to -current, make the kernel, etc, etc. The person who first reported the problem said he succesfully used the loader from a recent snap. That will work. Go to a near FreeBSD ftp site, get the "loader" binary from a snapshot, copy it to /boot, and that will be able to load a -current kernel. Alternatively (I just thought of it), you might want to interrupt the boot at boot2 (press any key while the | is being displayed), and boot the kernel directly from there, avoiding going through loader. I'd be interested in hearing whether this can be used as a work-around or not. As for the problem it goes like this: FreeBSD 3.1's loader was not capable of loading a kernel at a different base address than the one FreeBSD used up to that point. Unfortunately, this resulted in an annoying bug that affected machines with lots of RAM and big maxusers (like, for instance, 256). This was corrected by moving the base address of kernel, which required modifications to loader. Thus, FreeBSD's 3.1 loader is not capable of booting a current kernel. Now, aout_freebsd.c (and possibly other files) in sys/boot/i386/libi386 includes sys/param.h, which, in turn, includes sys/signal.h. The later requires machine/ucontext.h, which is not present. Why the newer signal.h is found but not ucontext.h, I'll find out shortly (I hope :). For now, I'm working with the hypothesis of a "file.h" instead of #include. All things considered, this isn't much of a problem in itself. There is a huge problem here,though. Generally speaking, loader is immune to world troubles, since it uses libstand. But, are we not risking chicken-and-egg problems such as this by including standard sys/*.h? Situations where newer loaders are needed to boot a new kernel (as much as we would like loader to be able to handle all future kernels), but not being able to build them until a newer kernel is booted? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 9:26: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from saturn.psn.net (saturn.psn.net [207.211.58.15]) by hub.freebsd.org (Postfix) with ESMTP id D00DE14BC5 for ; Mon, 18 Oct 1999 09:26:00 -0700 (PDT) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (5042-243.008.popsite.net [209.224.140.243]) by saturn.psn.net (8.9.3/8.9.3) with ESMTP id JAA18654; Mon, 18 Oct 1999 09:38:07 -0700 (MST) Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id MAA76654; Mon, 18 Oct 1999 12:25:48 -0400 (EDT) (envelope-from will) 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: <199910181530.JAA04534@harmony.village.org> Date: Mon, 18 Oct 1999 12:25:48 -0400 (EDT) Reply-To: Will Andrews From: Will Andrews To: Warner Losh Subject: Re: pcic.ko & recent changes to sys/pccard/* Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Oct-99 Warner Losh wrote: > In message <199910180726.DAA64055@shadow.blackdawn.com> Will Andrews writes: >: But it doesn't work. I'm assuming that my kernel >: config file's settings do not affect make world in any way, >: and thus it seems that pcic.ko is not being built by make world >: anymore... > > What doesn't work? Can you give some error messages as well as a > complete dmesg? I could give you a complete dmesg and error messages.. but I'll have to read them off argon (the laptop sitting next to me), since argon's only Internet connection _was_ through that PC-Card Ethernet card. :-) Let me try...: 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: Mon Oct 18 03:13:00 EDT 1999 root@argon.blackdawn.com:/usr/src/sys/compile/ARGON Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (300.00-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 127410176 (124424K bytes) Preloaded elf kernel "kernel" at 0xc028b000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc028b09c. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 11 at device 0.0 on pci1 pcic0: at device 4.0 on pci0 pcic1: at device 4.1 on pci0 isab0: at device 7.0 on pci0 devclass_alloc_unit: pcic0 already exists, using next available unit number devclass_alloc_unit: pcic1 already exists, using next available unit number isa0: on isab0 ide_pci0: at device 7.1 on pci0 chip1: irq 11 at device 7.2 on pci0 chip2: at device 7.3 on pci0 pci0: unknown card (vendor=0x125d, dev=0x1968) at 8.0 irq 5 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S atkbdc0: at port 0x60-0x6f on isa atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) on COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold plip0: on ppbus 0 pccard: initializing drivers: ep changing root device to wd0s2a --- Here's /usr/src/sys/i386/conf/ARGON: # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.192 1999/09/22 05:07:49 wpaul Exp $ machine i386 cpu I586_CPU cpu I686_CPU ident ARGON maxusers 100 makeoptions DEBUG=-g options INET options FFS options FFS_ROOT options MSDOSFS options CD9660 options CD9660_ROOT options PROCFS options COMPAT_43 options SCSI_DELAY=15000 options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options SOFTUPDATES options NO_F00F_HACK options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options IDE_DELAY=8000 device pcm0 controller isa0 controller pnp0 controller pci0 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 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 device wcd0 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? options XSERVER device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? disable flags 0x31 controller pcic0 at isa? controller pcic1 at isa? controller card0 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 device lpt0 device plip0 device ppi0 device ep0 at isa? port 0x300 irq 10 pseudo-device loop pseudo-device ether pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 32 pseudo-device gzip pseudo-device bpf 4 pseudo-device snp 4 --- I trimmed out the comments and other irrelevant stuff. So what you see here is the precise order in which my kernel configfile lists everything. :) --- Error messages: after /dev/rwd0s2e is marked clean: kldload: can't load pcic: No such file or directory pccardc: /dev/card0: Device not configured Enable PC-card.Doing initial network setup: hostname. --- It doesn't look like there's any other relevant error messages. My original evaluation was that the above was caused by the lack of a pcic.ko in /modules. Which, to me, seemed to be `make world`'s fault, since it is obviously not built when you build a kernel. If you don't believe me when I say that pcic _was_ working for the Sept. 29 sources: [after bootup] pccard-ep0: at port 0x240-0x25f irq 10 slot 0 and pccard0 ep0: [*UTP*] address 00:50:04:8b:74:ac >: What's going on here? Is the Makefile in src/sys/modules/pcic >: borked somehow (Makefile v1.9, 1999/08/28)? Doesn't seem >: likely, as the last time it was changed was for the $Id$ -> >: $FreeBSD$ change, which of course was mostly propagated >: by Peter Wemm. And it wasn't relevant to pcic anyway. > > The pcic module is borked and hasn't worked for a long time. Actually, it worked for me in my last world - September 29, 1999 @ 10AM EDT. I eagerly await your reply. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 9:38:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from saturn.psn.net (saturn.psn.net [207.211.58.15]) by hub.freebsd.org (Postfix) with ESMTP id 24F6914BC5; Mon, 18 Oct 1999 09:38:35 -0700 (PDT) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (5042-243.008.popsite.net [209.224.140.243]) by saturn.psn.net (8.9.3/8.9.3) with ESMTP id JAA20926; Mon, 18 Oct 1999 09:50:39 -0700 (MST) Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id MAA77002; Mon, 18 Oct 1999 12:38:24 -0400 (EDT) (envelope-from will) 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: <380B41FF.C4CB44D8@newsguy.com> Date: Mon, 18 Oct 1999 12:38:24 -0400 (EDT) Reply-To: Will Andrews From: Will Andrews To: "Daniel C. Sobral" Subject: Re: -CURRENT `make world` fails.. (ucontext.h?) Cc: peter@FreeBSD.ORG, msmith@FreeBSD.ORG, marcel@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Oct-99 Daniel C. Sobral wrote: > I'm tracking this now. Well, I'll start tracking as soon as I finish > my mail. I suggested first upgrading to 3.3 (or even 3.2), and only > then to current. That _will_ work, as it will upgrade the loader. > Alas, you need not even go to such pains. Just cvsup to -stable, cd > /sys/boot; make depend && make all install, and then cvsup to > -current, make the kernel, etc, etc. Yes, that's how I did it. Actually, I had 3.3-RELEASE.. I downloaded the entire -CURRENT CVS repository so I could get sources for September 29, before marcel's changes. Then I burned those sources to a CD-R, and loaded it on my laptop. Made world, rebooted, and I'm in 4.0-CURRENT. Then after several unsuccessful attempts to do a newer world, I finally got it. argon.blackdawn.com (my laptop) is _NOW_ running 4.0-CURRENT as of October 17, 1999 @ 9PM EDT. Only one problem is left - my pccard isn't working. I'm working with Warner Losh on that... (hopefully something good will come out of that.) > The person who first reported the problem said he succesfully used > the loader from a recent snap. That will work. Go to a near FreeBSD > ftp site, get the "loader" binary from a snapshot, copy it to /boot, > and that will be able to load a -current kernel. Interesting. All I did was rebuild the kernel again and tried another make world. For some reason, the system wanted me to build the same kernel twice. Or maybe I cvsup'd more than once, and didn't build a new kernel the second or third time. I don't know. :) I didn't try a bootloader off the ftp sites.. that wouldn't have worked for me anyway, since pccard support broke around the time I got to the bootloader in `make world`. I mean, it broke 'cause I lost my old Sept. 29 kernel. I forgot to keep a backup copy of it.. :\ > As for the problem it goes like this: > > FreeBSD 3.1's loader was not capable of loading a kernel at a > different base address than the one FreeBSD used up to that point. > Unfortunately, this resulted in an annoying bug that affected > machines with lots of RAM and big maxusers (like, for instance, > 256). This was corrected by moving the base address of kernel, which > required modifications to loader. > > Thus, FreeBSD's 3.1 loader is not capable of booting a current > kernel. Perhaps people need to install a new boot loader first (one that is of 4.0-CURRENT lineage), as you suggested. Then perhaps building a -CURRENT kernel, and rebooting. Of course, I dunno if that'd work, given the differing kernel and world.. > Now, aout_freebsd.c (and possibly other files) in > sys/boot/i386/libi386 includes sys/param.h, which, in turn, includes > sys/signal.h. The later requires machine/ucontext.h, which is not > present. Why the newer signal.h is found but not ucontext.h, I'll > find out shortly (I hope :). For now, I'm working with the > hypothesis of a "file.h" instead of #include. Yes, I thought the was the problem. Is "machine/ucontext.h" under /usr/src somewhere? I thought I saw one, but couldn't seem to finger its precise path. > All things considered, this isn't much of a problem in itself. > > There is a huge problem here,though. Generally speaking, loader is > immune to world troubles, since it uses libstand. But, are we not > risking chicken-and-egg problems such as this by including standard > sys/*.h? Situations where newer loaders are needed to boot a new > kernel (as much as we would like loader to be able to handle all > future kernels), but not being able to build them until a newer > kernel is booted? Like I said above, a -CURRENT kernel may have problems with a -STABLE world. I'm honestly not fully aware of the dependencies regarding the signal changes (i.e., ucontext.h), so my thoughts may be completely wrong. :-) Comments? -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 9:41:17 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 8C73914BC5 for ; Mon, 18 Oct 1999 09:41:10 -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 MAA04221; Mon, 18 Oct 1999 12:41:09 -0400 (EDT) Date: Mon, 18 Oct 1999 12:41:08 -0400 (EDT) From: "Matthew N. Dodd" To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: aic driver camified In-Reply-To: <199910181340.JAA27263@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 Mon, 18 Oct 1999, Luoqi Chen wrote: > DMA is not supported, sync transfer is supported but not tested, neither > pnp nor pccard is supported. My card doesn't support any of these, so > there's not much I could do, I hope sopme of you could fill in the blanks. Looks pretty good. I'll whip up an MCA front end and try it out when I get home. I suspect someone will want a PCCARD front end as well. I'll write it if someone will work with me on testing. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 9:56:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from tuden.freebsd.dk (picasso.transbay.net [209.133.53.6]) by hub.freebsd.org (Postfix) with ESMTP id DC3D814F31 for ; Mon, 18 Oct 1999 09:56:09 -0700 (PDT) (envelope-from sos@tuden.freebsd.dk) Received: (from sos@localhost) by tuden.freebsd.dk (8.9.3/8.9.2) id SAA00420; Mon, 18 Oct 1999 18:55:38 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <199910181655.SAA00420@tuden.freebsd.dk> Subject: Re: Promise Ultra66 IDE adapter In-Reply-To: from Bryan Liesner at "Oct 18, 1999 10:26:00 am" To: bleez@netaxs.com (Bryan Liesner) Date: Mon, 18 Oct 1999 18:55:37 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bryan Liesner wrote: > > Is the Promise Ultra66 IDE adapter supported? I cannot get 3.3 or 4.0 > kernels to see the card at all. The mailing list archive details are > sketchy at best. The pci_ide source seems to only do support for the > Ultra33. The Ultra66 should be supported in -current, but only upto UDMA33. I should have one lying on the table back home, when I return from FreeBSDCon, then support will be coming into -current. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 10:10: 6 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 2B61D14E40 for ; Mon, 18 Oct 1999 10:09:59 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p01-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.130]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id CAA26930; Tue, 19 Oct 1999 02:09:50 +0900 (JST) Message-ID: <380B53ED.20B3DC5C@newsguy.com> Date: Tue, 19 Oct 1999 02:07:57 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Will Andrews Cc: current@FreeBSD.ORG Subject: Re: -CURRENT `make world` fails.. (ucontext.h?) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [removing cc's, since I addressed them in another message in another thread in another list :] Will Andrews wrote: > > Yes, that's how I did it. Actually, I had 3.3-RELEASE.. I downloaded the entire If you had 3.3-RELEASE, you wouldn't need a new loader to load the -current kernel. That's not true of someone who had 3.1-RELEASE. > > Now, aout_freebsd.c (and possibly other files) in > > sys/boot/i386/libi386 includes sys/param.h, which, in turn, includes > > sys/signal.h. The later requires machine/ucontext.h, which is not > > present. Why the newer signal.h is found but not ucontext.h, I'll > > find out shortly (I hope :). For now, I'm working with the > > hypothesis of a "file.h" instead of #include. > > Yes, I thought the was the problem. Is > "machine/ucontext.h" under /usr/src somewhere? I thought I saw one, but > couldn't seem to finger its precise path. Actually, now that I spent a few minutes witht he code, it's obvious that I was way short-sighted in this. The analysis above is too naive, and, to be blunt, dumb. :-) Obviously, /usr/src/sys/machine/* cannot be found, because it does not exist. /usr/include/machine/* is generated from /usr/src/sys/${MACHINE_ARCH}/include. The makefile uses -I so that files will be found under /usr/src/sys (well, not exactly -- it uses a relative path, but that's the gist of it :), but the files included by those cannot be found. Thus, we have a situation in which some of the include files are the latest (), and some are not (). The problem is triggered by , but it could have been triggered by a number of other files. It's just not a simple problem to solve. :-( > Like I said above, a -CURRENT kernel may have problems with a -STABLE world. > > I'm honestly not fully aware of the dependencies regarding the signal changes > (i.e., ucontext.h), so my thoughts may be completely wrong. :-) > > Comments? You ought to say that a -STABLE world will have problems with a -CURRENT kernel. The kernel ought to be immune to -STABLE world's problems. :-) In a perfect world, anyway. :-) Anyway, there are problems a -STABLE world will have with a -CURRENT kernel, but they are not likely to be crippling (ie, you should be able to make world after booting the new kernel). One thing that *can* bite is the use of klds. Bad ju ju may result from the use of old klds with a new kernel. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 11:39:52 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 C268B14BD8 for ; Mon, 18 Oct 1999 11:39:48 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id LAA19168; Mon, 18 Oct 1999 11:39:44 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 18 Oct 1999 11:39:43 -0700 (PDT) From: Doug White To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: aic driver camified In-Reply-To: <199910181340.JAA27263@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 Mon, 18 Oct 1999, Luoqi Chen wrote: > After the recent signal related changes, the pre-cam kernel I saved a long > time ago no longer works with (even statically compiled) user applications, > which meant I had no way to access my files on an old disk hanging off an > aic6360 card. So I decided to bite the bullet and camify the aic driver > myself (I've long given up hope someone else would do it.) Luoqi, you are a god. I bow to thee. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Oct 18 11:56:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (Postfix) with ESMTP id 9B58214EFE for ; Mon, 18 Oct 1999 11:56:26 -0700 (PDT) (envelope-from sto@stat.Duke.EDU) Received: from cayenne.isds.duke.edu (cayenne.isds.duke.edu [152.3.22.11]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id OAA00889 for ; Mon, 18 Oct 1999 14:56:23 -0400 (EDT) Received: (from sto@localhost) by cayenne.isds.duke.edu (8.8.8/8.8.8) id OAA06540 for freebsd-current@FreeBSD.ORG; Mon, 18 Oct 1999 14:56:22 -0400 (EDT) Message-ID: <19991018145622.A6476@stat.Duke.EDU> Date: Mon, 18 Oct 1999 14:56:22 -0400 From: "Sean O'Connell" To: FreeBSD current Subject: Re: workaround for ata driver woes on alpha Reply-To: "Sean O'Connell" References: <14347.23151.744866.110836@grits.cs.duke.edu> <199910181741.TAA99649@freebsd.dk> <14347.24351.390250.179176@grits.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 In-Reply-To: <14347.24351.390250.179176@grits.cs.duke.edu>; from Andrew Gallatin on Mon, Oct 18, 1999 at 01:58:03PM -0400 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999 Oct 18, Andrew Gallatin (aka gallatin@cs.duke.edu) wrote: > > BTW -- I just talked to a collegue here who's getting screwed by > ad_timeout() with a very slow disk on a pc. It sounds like it could > be the same problem. Hi- I would be that induhvidual. I have x86 box at home running current as of last night that began to behave this way: FreeBSD bobzilla 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sun Oct 17 21:45:50 EDT 1999 sto@bobzilla:/usr/src/sys/compile/BOBZILLA i386 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 ad0: ATA-4 disk at ata0 as master ad1: ATA-? disk at ata1 as slave acd0: CDROM drive at ata1 as master ata1-slave: ad_timeout: lost disk contact - resetting ata1: resetting devices .. done Once this ad_timeout happened, I was hosed. I had to power cycle my way out of a shutdown.. and upon reboot, the file system was completely toast. newfs was my only way out... fortunately, this was just my /usr/obj directory, so I am not too concerned about the lost data. Of course, this could just be a sign of the imminent demise of this drive. Hope this helps. S -- ----------------------------------------------------------------------- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 13:16:18 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 8444315156 for ; Mon, 18 Oct 1999 13:16:08 -0700 (PDT) (envelope-from leif@neland.dk) Received: from gina.neland.dk (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id WAA26129 for ; Mon, 18 Oct 1999 22:15:59 +0200 (CEST) (envelope-from leif@neland.dk) Date: Mon, 18 Oct 1999 22:16:29 +0200 (CEST) From: Leif Neland To: freebsd-current@freebsd.org Subject: adv hanging at boot Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Current, cvsup'ed daily. My adv is hanging now at "Waiting 5 seconds for SCSI devices to settle" Two weeks or so it then gave 4 messages about "bus timeout" or so (Sorry I can't remember the exact wording; it doesn't say so now.) It has ben non-functional for a month or so. I only have a HP4020i cd-writer on the bus, so it's not that important... It works nicely under windows, and also used to work under Fbsd. I can still boot an older kernel, but it won't run with the current userland. Here is a dmesg with adv disabled in userconfig to get something to send you. 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 #118: Sat Oct 16 04:42:50 CEST 1999 root@gina.neland.dk:/usr/src/sys/compile/GINA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (337.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 67096576 (65524K bytes) VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc00c0e38 (c0000e38) VESA: S3 Incorporated Trio3D. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: at device 0.0 on pci1 isab0: at device 4.0 on pci0 isa0: on isab0 ata-pci0: at device 4.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 9 at device 4.2 on pci0 uhci0: could not map ports device_probe_and_attach: uhci0 attach returned 6 intpm0: at device 4.3 on pci0 intpm0: Could not allocate Bus space device_probe_and_attach: intpm0 attach returned 6 pcm0: irq 5 at device 11.0 on pci0 pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 ed1: irq 10 at device 12.0 on pci0 ed1: address 00:80:ad:50:40:cf, type NE2000 (16 bit) fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ----> adv0: not probed (disabled) 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: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: 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 ppi0: on ppbus 0 pca0 at port 0x40 on isa0 pca0: PC speaker audio driver devclass_alloc_unit: pcf0 already exists, using next available unit number pcf0 at port 0x320 irq 5 on isa0 Gets detected here --->unknown0: at port 0x110-0x11f iomem 0xc8000-0xc807f irq 11 drq 5 on isa0 ad0: ATA-4 disk at ata0 as master ad0: 8207MB (16809660 sectors), 16676 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 ad1: ATA-4 disk at ata0 as slave ad1: 6197MB (12692295 sectors), 13431 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 31 depth queue, UDMA33 Creating DISK ad1 Creating DISK wd1 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: CDROM drive at ata1 as slave acd0: read 343KB/s (7562KB/s), 128KB buffer, DMA acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked changing root device to wd1s3a My config: machine i386 cpu I686_CPU ident "GINA" maxusers 32 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options NFS #Network Filesystem 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 USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options DDB controller isa0 controller pnp0 # PnP support for ISA controller eisa0 controller pci0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 controller adv0 at isa? port ? irq ? controller scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI access) controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 options ATKBD_DFLT_KEYMAP # specify the built-in keymap makeoptions ATKBD_DFLT_KEYMAP="danish.cp865" device vga0 at isa? port ? conflicts options VGA_WIDTH90 # support 90 column modes options VESA pseudo-device splash device sc0 at isa? options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT=cp865 device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? disable flags 0x31 # Advanced Power Management 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 ppi0 at ppbus? device ed0 at isa? port 0x2c0 irq 5 iomem 0xd8000 pseudo-device loop pseudo-device ether pseudo-device tun 2 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's options KTRACE #kernel tracing options SYSVSHM options SYSVMSG options SYSVSEM pseudo-device bpf 4 #Berkeley packet filter controller uhci0 controller ohci0 controller usb0 device ugen0 device uhid0 device ukbd0 device ulpt0 controller umass0 device ums0 device pcm0 device pca0 at isa? port IO_TIMER1 controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives options SOFTUPDATES pseudo-device sppp #Generic Synchronous PPP controller smbus0 controller intpm0 controller alpm0 device smb0 at smbus? controller iicbus0 controller iicbb0 device ic0 at iicbus? device iic0 at iicbus? device iicsmb0 at iicbus? controller pcf0 at isa? port 0x320 irq 5 Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 13:41:55 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 C781414EFE for ; Mon, 18 Oct 1999 13:41:48 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA53787; Mon, 18 Oct 1999 13:41:47 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA33606; Mon, 18 Oct 1999 13:41:46 -0700 (PDT) (envelope-from obrien) Date: Mon, 18 Oct 1999 13:41:46 -0700 From: "David O'Brien" To: Will Andrews Cc: current@FreeBSD.ORG Subject: Re: pcic.ko & recent changes to sys/pccard/* Message-ID: <19991018134146.A16641@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199910181530.JAA04534@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT 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 Mon, Oct 18, 1999 at 12:25:48PM -0400, Will Andrews wrote: > If you don't believe me when I say that pcic _was_ working for the Sept. 29 > sources: The pcic modules is *KNOWN* to have and cause problems. Warner told you this and you still insist on pushing the issue. Why? NO FreeBSD developer uses the pcic *module*, thus it is quite unwise for you to be using it as we no longer test it or keep it in sync with the rest of the kernel. > >: What's going on here? Is the Makefile in src/sys/modules/pcic > >: borked somehow (Makefile v1.9, 1999/08/28)? Doesn't seem > >: likely, as the last time it was changed was for the $Id$ -> The building of modules/pcic was removed from /sys/modules/Makefile. Check the history on that file. > > The pcic module is borked and hasn't worked for a long time. > > Actually, it worked for me in my last world - September 29, 1999 @ 10AM EDT. STOP USING IT!!! I disabled it in -STABLE and -CURRENT quite some time ago. How is it you are even compiling and installing it? Please statically compile it into your kernel so developer's time isn't wasted on this. We have known problems for PCIMCA modems and that is where the pccard developer's time needs to be spent. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 13:43:31 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 4D22515130 for ; Mon, 18 Oct 1999 13:43:28 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA53802; Mon, 18 Oct 1999 13:43:27 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA35730; Mon, 18 Oct 1999 13:43:27 -0700 (PDT) (envelope-from obrien) Date: Mon, 18 Oct 1999 13:43:27 -0700 From: "David O'Brien" To: "Matthew N. Dodd" Cc: current@FreeBSD.ORG Subject: Re: aic driver camified Message-ID: <19991018134326.B16641@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199910181340.JAA27263@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT 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 suspect someone will want a PCCARD front end as well. I'll write it if > someone will work with me on testing. You have a guinie pig^W^Wtester. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 14:44:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from saturn.psn.net (saturn.psn.net [207.211.58.15]) by hub.freebsd.org (Postfix) with ESMTP id C930114E3E; Mon, 18 Oct 1999 14:44:10 -0700 (PDT) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (5042-243.008.popsite.net [209.224.140.243]) by saturn.psn.net (8.9.3/8.9.3) with ESMTP id OAA16256; Mon, 18 Oct 1999 14:56:20 -0700 (MST) Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id RAA06573; Mon, 18 Oct 1999 17:43:56 -0400 (EDT) (envelope-from will) 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: <19991018134146.A16641@dragon.nuxi.com> Date: Mon, 18 Oct 1999 17:43:56 -0400 (EDT) Reply-To: Will Andrews From: Will Andrews To: "David O'Brien" Subject: Re: pcic.ko & recent changes to sys/pccard/* Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Oct-99 David O'Brien wrote: > On Mon, Oct 18, 1999 at 12:25:48PM -0400, Will Andrews wrote: >> If you don't believe me when I say that pcic _was_ working for the Sept. 29 >> sources: > > The pcic modules is *KNOWN* to have and cause problems. Warner told you > this and you still insist on pushing the issue. Why? NO FreeBSD > developer uses the pcic *module*, thus it is quite unwise for you to be > using it as we no longer test it or keep it in sync with the rest of the > kernel. No, no... see below. >> >: What's going on here? Is the Makefile in src/sys/modules/pcic >> >: borked somehow (Makefile v1.9, 1999/08/28)? Doesn't seem >> >: likely, as the last time it was changed was for the $Id$ -> > > The building of modules/pcic was removed from /sys/modules/Makefile. > Check the history on that file. > >> > The pcic module is borked and hasn't worked for a long time. >> >> Actually, it worked for me in my last world - September 29, 1999 @ 10AM EDT. > > STOP USING IT!!! I disabled it in -STABLE and -CURRENT quite some time > ago. How is it you are even compiling and installing it? > > Please statically compile it into your kernel so developer's time isn't > wasted on this. We have known problems for PCIMCA modems and that is > where the pccard developer's time needs to be spent. I apologize for causing undue freaking-out... I am confused. :) First things first. After this message, I'm going to read the -current archives regarding pccard. Second, it should be noted that I don't see how I could ever have used the pcic module.. if you disabled it before September 29, then it must have been kernel support. My old logs show no indication that any module was loaded before, so if the 9/29 kernel worked, why doesn't the current kernel work with my pccard? I made the appropriate changes that Warner mentioned in the cvs logs for src/sys/pccard/pccard.c, v1.89, as I said before. Third, part of my confusion is due to /etc/rc.pccard, which seems to attempt to load the module. Since I received no errors before (in the 9/29 world/kernel) about kldload failing, it seems like there WAS indeed a pcic.ko module (because now, since there is no module, kldload gives an error on booting up: "can't find module pcic".) I would never use any deprecated software. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 14:46:22 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 0CA3014F36 for ; Mon, 18 Oct 1999 14:46:14 -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.3) with ESMTP id QAA93543; Mon, 18 Oct 1999 16:46:02 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 18 Oct 1999 16:46:02 -0500 (CDT) From: Chris Dillon To: Marc van Woerkom Cc: sthaug@nethelp.no, freebsd-current@FreeBSD.ORG Subject: Re: current unable to attach USB, Power Mgmt, sound In-Reply-To: <199910180841.KAA02406@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 Mon, 18 Oct 1999, Marc van Woerkom wrote: > > > pcm0: unable to map register space > > > device_probe_and_attach: pcm0 attach returned 6 > > > > This is an Abit BP6 board with two Celeron 366, 256 MByte memory, one > > Soundblaster PCI 128 (pcm0) and one Hoontech (pcm1) sound card. Below is > > the complete dmesg from today's current, and the kernel config. > > I reported the same problem. PCI 128 uses the same ES1370 chip as the > Audio PCI. The Vibra128 (which is PCI) uses the Ensoniq chip, but I'm not so sure the PCI128 does. I just found this out the hard way on 56 new systems. I wanted the SB16 ISA, couldn't get that, so I was going to get an AWE64 ISA, couldn't get that either (curse you, Creative, for discontinuing those cards). Got what I THOUGHT was the PCI128, which turned out to be the Vibra128, which is a very different animal as far as the Windows drivers are concerned. It hasn't done too bad so far, though we're running Win95, not FreeBSD (yet). The wavetable samples don't appear to exist in any kind of onboard RAM, so I'm not entirely sure just how "hardware" the wavetable is at all. -- 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 Mon Oct 18 14:49:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.keycomp.net (www.keycomp.net [207.44.1.33]) by hub.freebsd.org (Postfix) with ESMTP id D0E5D152BB; Mon, 18 Oct 1999 14:49:15 -0700 (PDT) (envelope-from billieakay@yahoo.com) Received: from bopper (kc-rmt10.keycomp.net [207.44.1.12]) by www.keycomp.net (8.8.5/SCO5) with SMTP id RAA17775; Mon, 18 Oct 1999 17:55:52 -0400 (EDT) Message-ID: <002d01bf19b2$92354160$0c012ccf@bopper> From: "Bill A. K." To: "Steve O'Hara-Smith" Cc: , "FreeBSD Questions" References: Subject: Re: PCI Hardware Modem (Really) Date: Mon, 18 Oct 1999 17:47:48 -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.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, Windows 98 recognizes it as a PCI Serial Controller before I install a driver, is there any way to direct the sio to look at the pci bus? Bill billieakay@yahoo.com ----- Original Message ----- From: Steve O'Hara-Smith To: Bill A. K. Cc: ; FreeBSD Questions Sent: Monday, October 18, 1999 8:03 AM Subject: RE: PCI Hardware Modem (Really) > > On 15-Oct-99 Bill A. K. wrote: > > Hi, > > I've got a Rockwell PCI Modem thats full hardware, and I was wondering > > if anybody has written a driver for this kind yet. > > If it really is a full hardware modem then the driver has been around > for a while, called sio. If you mean something like the Lucent which has all > the signal processing hardware but no serial port or command processing, then > there is an alpha work in progress going on. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 15:29: 3 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 ECE23150ED for ; Mon, 18 Oct 1999 15:29:00 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial8-228.netcologne.de [195.14.235.228]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id AAA14160; Tue, 19 Oct 1999 00:28:57 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id AAA01066; Tue, 19 Oct 1999 00:29:09 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Tue, 19 Oct 1999 00:29:09 +0200 (CEST) Message-Id: <199910182229.AAA01066@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: sthaug@nethelp.no Cc: van.woerkom@netcologne.de, freebsd-current@FreeBSD.ORG In-reply-to: <84276.940257732@verdi.nethelp.no> (sthaug@nethelp.no) Subject: Re: current unable to attach USB, Power Mgmt, sound Reply-To: van.woerkom@netcologne.de References: <199910180841.KAA02406@oranje.my.domain> <84276.940257732@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The following patch from Doug Rabson fixed the USB and sound problem for > me. It has already bee committed to -current. Thanks for that hint. 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 Oct 18 15:55:39 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 AFD7114A26 for ; Mon, 18 Oct 1999 15:55:21 -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.3) with ESMTP id RAA93895; Mon, 18 Oct 1999 17:55:19 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 18 Oct 1999 17:55:19 -0500 (CDT) From: Chris Dillon To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: aic driver camified In-Reply-To: <199910181340.JAA27263@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 Mon, 18 Oct 1999, Luoqi Chen wrote: > After the recent signal related changes, the pre-cam kernel I saved a long > time ago no longer works with (even statically compiled) user applications, > which meant I had no way to access my files on an old disk hanging off an > aic6360 card. So I decided to bite the bullet and camify the aic driver > myself (I've long given up hope someone else would do it.) WOOHOO!! I'll be your guinea pig for trying this on -stable if you like. All I have is a ZIP drive to test things with. If it would make any difference, I could also borrow a Yamaha 4260 CD writer and a Sony SDT-S5200 DDS2 drive. > The source is at http://www.freebsd.org/~luoqi/aic. Copy the source files > into sys/dev/aic, apply the patch files.diff to sys/conf/files. Don't > forget to add the controller aic0 line back to your config file. Should this apply cleanly to -stable? If so, I'll give it a shot when I get home. -- 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 Mon Oct 18 16:52:22 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id DBF5A15234; Mon, 18 Oct 1999 16:52:19 -0700 (PDT) To: announce@FreeBSD.org Date: Mon, 18 Oct 1999 21:42:02 +0200 From: Remco Moolenaar Message-ID: <380B780A.F3BBCA1@scc.nl> Organization: SCC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: remco@scc.nl Subject: BSD Applications database To: FreeBSD-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good afternoon, Last month we announced the Linux Applications database for BSD Unix systems. This database has been generalized to include ALL Unix applications and has been moved to its own domain http://www.bsdapps.org/ The generalization is especially import for the NetBSD and OpenBSD groups as these platforms are able to run several Unix applications (from Alpha and Sparc systems for instance) as well. An example in the database can be found here: http://www.bsdapps.org/db/owa/bsdapps$apps.queryview?P_BSDAPPS_ID=109&Z_CHK=3989 6 This database is open to anybody. This means that anybody is allowed to insert new applications and/or support notes. This will create an Open Internet initiative in order to support BSD systems in general. Thanks for the support, Remco Moolenaar -- Remco Moolenaar mailto:remco@scc.nl SCC Internetworking & Databases http://www.scc.nl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 16:57: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from wombat.cs.rmit.edu.au (wombat.cs.rmit.edu.au [131.170.24.41]) by hub.freebsd.org (Postfix) with ESMTP id D001B152AC for ; Mon, 18 Oct 1999 16:56:51 -0700 (PDT) (envelope-from brettw@cs.rmit.edu.au) Received: from yallara.cs.rmit.edu.au (brettw@yallara.cs.rmit.edu.au [131.170.24.42]) by wombat.cs.rmit.edu.au (8.9.3/8.9.3/cshub) with ESMTP id JAA12462 for ; Tue, 19 Oct 1999 09:56:49 +1000 (EST) Received: (from brettw@localhost) by yallara.cs.rmit.edu.au (8.9.3/8.9.3/csnode) id JAA17064 for freebsd-current@freebsd.org; Tue, 19 Oct 1999 09:56:49 +1000 (EST) Date: Tue, 19 Oct 1999 09:56:49 +1000 From: Brett White To: freebsd-current@freebsd.org Subject: 4.0-19991012-CURRENT Message-ID: <19991019095649.A14736@cs.rmit.edu.au> 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 Has anyone tried using the 4.0-19991012-CURRENT snapshot? I need to confirm that this snapshot is a "good one" before I update my 3.3R installation to it in a last ditch effort to compile USB modem support into the kernel. Thanks, -- Brett White Duty Programmer, CS130 tutor, 4thYr D/Degree SSCC & CQAT rep. "Like the naked leads the blind. I know I'm selfish, I'm unkind." -Placebo 'Every You, Every Me' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 17: 4:21 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 B6C821536C for ; Mon, 18 Oct 1999 17:04:16 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial8-228.netcologne.de [195.14.235.228]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id CAA16558; Tue, 19 Oct 1999 02:04:09 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id CAA02619; Tue, 19 Oct 1999 02:04:24 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Tue, 19 Oct 1999 02:04:24 +0200 (CEST) Message-Id: <199910190004.CAA02619@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: cdillon@wolves.k12.mo.us Cc: van.woerkom@netcologne.de, sthaug@nethelp.no, freebsd-current@FreeBSD.ORG In-reply-to: (message from Chris Dillon on Mon, 18 Oct 1999 16:46:02 -0500 (CDT)) Subject: The Unofficial AudioPCI/PCI64 Support Page Reply-To: van.woerkom@netcologne.de References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The Vibra128 (which is PCI) uses the Ensoniq chip, but I'm not so sure > the PCI128 does. Walter Lord has set up (and still maintains) a home page when the Ensoniq Audio PCI came out: http://www.netexcite.com/audiopci/index.html You find lots of drivers, the 8 MB wave table sets for the Windows driver and other useful information there. Wish we could use that wave tables for a midi device.. To make a long story short. The original Ensoniq Audio PCI card used the ES1370 chip (PCI & control) and the AK4531 codec for AD/DA. Later they made Audio PCI cards with the ES1371 chip. This one seems to be able to use lots of different codecs (that is where the driver fun comes in) that comply to some Intel spec (AC 97), among them the AK4540. All this time, Ensoniq also sold their chips to OEMS, who in turn might have used the same codec or even other stuff. Then Creative came up and bought Ensoniq to get some decent PCI card. The PCI 128 seems to be more or less the same like the Audio PCI (I am not 100% sure, because the latest greatest Win drivers do not work for me anymore), the PCI 64 is reported to have at least a lesser quality code. And more fun: recently people reported an ES1374 chip - I have no clue yet where this one is different. Specs for ES1370 and ES1371: http://www.ensoniq.com/multimedia/semi_html/index.htm Specs for Ashai Kasei AK4531 and AK4543: http://www.akm.com/Text/pdflist.html http://www.asahi-kasei.co.jp/akm/english/p_i/pdf/EK4351.pdf http://www.akm.com/pdf/4543.pdf Specs for Audio Codec '97: http://developer.intel.com/pc-supp/platform/ac97 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 Oct 18 17:13:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 8A9AC153D3 for ; Mon, 18 Oct 1999 17:13:23 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id RAA78407; Mon, 18 Oct 1999 17:12:41 -0700 (PDT) Date: Mon, 18 Oct 1999 17:12:41 -0700 (PDT) From: David Wolfskill Message-Id: <199910190012.RAA78407@pau-amma.whistle.com> To: brettw@cs.rmit.edu.au, freebsd-current@FreeBSD.ORG Subject: Re: 4.0-19991012-CURRENT In-Reply-To: <19991019095649.A14736@cs.rmit.edu.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Tue, 19 Oct 1999 09:56:49 +1000 >From: Brett White >Has anyone tried using the 4.0-19991012-CURRENT snapshot? I >need to confirm that this snapshot is a "good one" before I >update my 3.3R installation to it in a last ditch effort to >compile USB modem support into the kernel. I'm currently using 4.0-19991012-CURRENT and trying -- so far, unsuccessfully -- to break it (as I broke(*) 3.2-R & 3.3-R) with a script that does some fairly aggressive file creation/deletion. I haven't done much more than that with it, though. (Well, I persuaded it to "play nice" in our Engineering net, NIS and all. And it uses amd OK.) (I'm stress-testing the machine because I'm trying to set up a new amanda server, and I want to do a better job of it than I did last time. The script is kinda dumb, but moderately effective, at simulating the kind of load an active amanda server puts on ts "holding disk".) *"Broke" as in panic. Called Julian over to have a look; he suggested trying 3.3-R, then a recent CURRENT snap. Panic, as I recall, was whimpering about an attempt to free a vnode that was already marked free. Hope that's useful, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 17:48:32 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 EB8CC1558D for ; Mon, 18 Oct 1999 17:48:23 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA23054; Tue, 19 Oct 1999 10:18:09 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 19 Oct 1999 10:18:08 +0930 (CST) From: "Daniel O'Connor" To: Chris Dillon Subject: Re: current unable to attach USB, Power Mgmt, sound Cc: freebsd-current@FreeBSD.ORG, sthaug@nethelp.no, Marc van Woerkom Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Oct-99 Chris Dillon wrote: > though we're running Win95, not FreeBSD (yet). The wavetable samples > don't appear to exist in any kind of onboard RAM, so I'm not entirely > sure just how "hardware" the wavetable is at all. Probably not at all.. Since Vibra 128's are REALLY cheap, then the 'hardware' wavetable would probably mean that it DMA's wavetable samples from physical RAM when it needs them. --- 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 Mon Oct 18 19:41:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from mirriwinni.cse.rmit.edu.au (pm.cse.rmit.edu.au [131.170.118.50]) by hub.freebsd.org (Postfix) with ESMTP id 8B48115918 for ; Mon, 18 Oct 1999 19:41:01 -0700 (PDT) (envelope-from brettw@mirriwinni.cse.rmit.edu.au) Received: (from brettw@localhost) by mirriwinni.cse.rmit.edu.au (8.9.3/8.9.3) id MAA53242 for freebsd-current@freebsd.org; Tue, 19 Oct 1999 12:40:59 +1000 (EST) (envelope-from brettw) Date: Tue, 19 Oct 1999 12:40:59 +1000 From: Brett White To: freebsd-current@freebsd.org Subject: USB Modem?? Message-ID: <19991019124059.A53220@mirriwinni.cse.rmit.edu.au> 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 Hey there, Has anyone managed to get USB modem support compiled into the 4.0 kernel using the patches from the projects site?? Or can it be done another way?? Unfortunately my 33.6K internal has rolled over and died and now I just have a 56.6K external USB modem which I haven't been able to get the support for yet (hence I can't cvsup to 4.0 like most ppl have suggested, but thanks for the responses anyway!!). See Ya! -- Brett White How many Tux could the Daemon Chuck slay if the Daemon Chuck could slay Tux? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 18 20:44:25 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 37A4C15B98 for ; Mon, 18 Oct 1999 20:44:18 -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.3) with ESMTP id WAA95415; Mon, 18 Oct 1999 22:44:16 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 18 Oct 1999 22:44:15 -0500 (CDT) From: Chris Dillon To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: aic driver camified 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, 18 Oct 1999, Chris Dillon wrote: > Should this apply cleanly to -stable? If so, I'll give it a shot when > I get home. I'll answer my own question (which, oddly enough, still hasn't made it to the list after about two hours). I forgot about newbus. It doesn't work, of course, and my Clue Quotient(TM) isn't high enough to backport this to -stable. I think I'll teach myself how to do this next weekend, if nobody else gets to 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 Mon Oct 18 21:55: 2 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 A71D215D7B; Mon, 18 Oct 1999 21:53:19 -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 WAA07991; Mon, 18 Oct 1999 22:53:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: (from imp@localhost) by harmony.village.org (8.9.3/8.8.3) id WAA03278; Mon, 18 Oct 1999 22:52:44 -0600 (MDT) Date: Mon, 18 Oct 1999 22:52:44 -0600 (MDT) From: Warner Losh Message-Id: <199910190452.WAA03278@harmony.village.org> To: current@freebsd.org, mobile@freebsd.org Subject: FreeBSD CON and laptops Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG During this week I have two goals here at FreeBSD con. 1 is to kludge up a working sio driver. The second is to help fix those folks I've broken by my latest changes. Please trip me while I'm here if youare seeing problems. I have most of the sio driver mods done, but I'm doing something silly in newbus so need to talk to dfr, et al, about it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 0:19:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 31F9D160E1 for ; Tue, 19 Oct 1999 00:19:53 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1713 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Tue, 19 Oct 1999 09:19:53 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Smail3.1.29.0 #13) id m11dTYm-0003cyC; Tue, 19 Oct 99 09:19 METDST Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: [Call for review]: newsyslog - new option To: freebsd-current@freebsd.org (FreeBSD Current) Date: Tue, 19 Oct 1999 09:19:52 +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: 1005 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please have a look at http://www.freebsd.org/~hm/newsyslog.tar.gz I've added a new option (-o directory) to newsyslog to move the old logfiles into another directory than the original ones. This option was introduced, because it is not possible to move old logfiles out of the way without potentially interfering with newsyslogs operation (and finally parsing its configuration file before doing something). Directory may be either relative (in that case the old logfiles are placed in a directory below the one the current logfile is in) or absolute to collect all old logfiles in a single directory. A missing directory or any of its components will be created if not present. 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 Oct 19 0:23:44 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 7ED031610A for ; Tue, 19 Oct 1999 00:23:39 -0700 (PDT) (envelope-from erik@habatech.no) Received: from bsdbox.habatech.no ([62.92.133.3]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id JAA21471; Tue, 19 Oct 1999 09:23:21 +0200 (CEST) (envelope-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: <199910190004.CAA02619@oranje.my.domain> Date: Tue, 19 Oct 1999 09:23:03 +0200 (CEST) From: "Erik H. Bakke" To: Marc van Woerkom Subject: RE: The Unofficial AudioPCI/PCI64 Support Page Cc: freebsd-current@FreeBSD.ORG, sthaug@nethelp.no, cdillon@wolves.k12.mo.us Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Oct-99 Marc van Woerkom wrote: >> The Vibra128 (which is PCI) uses the Ensoniq chip, but I'm not so sure >> the PCI128 does. > > [Some lines deleted] > Then Creative came up and bought Ensoniq to get some decent PCI > card. The PCI 128 seems to be more or less the same like the Audio > PCI (I am not 100% sure, because the latest greatest Win drivers > do not work for me anymore), the PCI 64 is reported to have at > least a lesser quality code. The PCI 128 uses the original ES1370, and is indeed the same card as the original Ensoniq one. I have three of these cards in different computers, and one of them has a SoundBlaster sticker on top of the original Ensoniq marking. The PCI 64's I have seen (Have one PCI64 and one PCI64V myself) are based on ES1371 and 1373 chips. I believe both these chips are AC97 compatible, and can be mixed and matched. I have picked these cards out of my FreeBSD computers now, but I seem to recall that the card with the 1373 chip identified itself with the same PCI ID as the 1371, but I am not 100% sure about this. I needed a variety of these cards for a driver development project I was doing. > > And more fun: recently people reported an ES1374 chip - I have > no clue yet where this one is different. > It probably isn't. It will probably have the same programming interface as the earlier ES1371/1373 chips. The differences is probably mostly in the physical interface. (Lower power consumption, etc.) Unless you design sound cards around these chips, this will probably not matter. This is purely my own understanding of the chips, and I may very well proven to be wrong, so don't go betting all your money on this :) ===========================+================+=============================== Erik H. Bakke | | To be or not to be... Senior Consultant/Developer|erik@habatech.no| Is simply a question of Habatech AS | | binary logic ===========================+================+============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 0:24: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id E652D1612A for ; Tue, 19 Oct 1999 00:24:02 -0700 (PDT) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id JAA60452 for current@FreeBSD.org; Tue, 19 Oct 1999 09:14:59 +0200 (CEST) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Tue, 19 Oct 1999 09:14:59 +0200 From: Remco Moolenaar Message-ID: <380C1A73.D9470235@scc.nl> Organization: SCC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <380B780A.F3BBCA1@scc.nl> Reply-To: remco@scc.nl Subject: Re: BSD Applications database Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Remco Moolenaar wrote: > Good afternoon, Sorry about this, but I'm a 100% sure I've send it to freebsd-announce. I was surprised myself this morning. Remco. -- Remco Moolenaar mailto:remco@scc.nl SCC Internetworking & Databases http://www.scc.nl/ Amsterdam, The Netherlands mailto:remco@bsdapps.org Maintainer of the BSD Applications database at http://www.bsdapps.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 5:40: 3 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 F223C16DD5 for ; Tue, 19 Oct 1999 05:39:49 -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.3) with ESMTP id QAA94105; Tue, 19 Oct 1999 16:39:39 +0400 (MSD) (envelope-from camel@avias.com) Date: Tue, 19 Oct 1999 16:39:39 +0400 (MSD) From: Ilya Naumov To: luoqi@watermarkgroup.com Cc: current@FreeBSD.ORG Subject: luoqi's aic 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 i've tried new "camfied" aic driver today and failed. here is a brief report. my configuration: Chaintech 6BTM mainboard with Celeron 416A processor and 128 Mb of memory Adaptec AIC-6360 SCSI controller (port 0x340 irq 9), irq 9 is reserved for Legacy/ISA card in bios setup Pinnacle 1000 CD writer (with SCSI device ID set to 0) kernel settings: options "CD9660" options "CD9660_ROOT" options SCSI_DELAY=15000 controller scbus0 controller aic0 at isa? port 0x340 irq 9 device cd0 at aic? results: aic controller was successfully found by the kernel, but after "Waiting 15 seconds for SCSI devices to settle" message it said the following: (probe0:aic0:0:0:0): REQUEST SENSE. CDB: 3 0 0 0 20 0 (probe0:aic0:0:0:0): UNIT ATTENTION info?:1 asc:29,0 (probe0:aic0:0:0:0): Power on, reset, or bus device reset occured (probe0:aic0:0:0:1): REQUEST SENSE. CDB: 3 4 0 0 12 0 (probe0:aic0:0:0:1): ILLEGAL REQEST asc:25,0 (probe0:aic0:0:0:1): Logical unit not supported (probe0:aic0:0:0:2): ccb 0xc09c3000 - timed out (probe0:aic0:0:0:2): ccb 0xc09c3000 - timed out after that my system just hangs. what is possible reason of such behaviour and what should i try to do to make my aic/cdrom combination working? thank you in advance. 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 Oct 19 9:20: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from egr.msu.edu (jeeves.egr.msu.edu [35.9.37.127]) by hub.freebsd.org (Postfix) with ESMTP id 9A28E1761D for ; Tue, 19 Oct 1999 09:20:01 -0700 (PDT) (envelope-from mcdouga9@egr.msu.edu) Received: from miyagi (miyagi [35.9.40.242]) by egr.msu.edu (8.9.3/8.9.3) with ESMTP id MAA09044; Tue, 19 Oct 1999 12:19:54 -0400 (EDT) Date: Tue, 19 Oct 1999 12:19:52 -0400 (EDT) From: Adam McDougall X-Sender: mcdouga9@miyagi To: wpaul@skynet.ctr.columbia.edu Cc: current@freebsd.org Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Okay. I committed the fix to the length calculation to -current and :-stable (I just love one-line patches that stop panics). I just got :done patching my NFS server machines and they all seem to get along :nicely with the SGI now. Now I can upgrade the other SGIs without :worrying about them clobbering my FreeBSD machines. : :Hm. I wonder what would happen if the FreeBSD host was the client :and the SGI was the server. Have you ever tried this since? I caught whiff of a hardcore debain user unsure about linux's nfs client connecting to IRIX nfs servers and I'm looking to provide a datapoint for FreeBSD. : :-Bill :============================================================================= :-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 9:21:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from egr.msu.edu (jeeves.egr.msu.edu [35.9.37.127]) by hub.freebsd.org (Postfix) with ESMTP id 0798C17644 for ; Tue, 19 Oct 1999 09:21:26 -0700 (PDT) (envelope-from mcdouga9@egr.msu.edu) Received: from miyagi (miyagi [35.9.40.242]) by egr.msu.edu (8.9.3/8.9.3) with ESMTP id MAA09232; Tue, 19 Oct 1999 12:21:21 -0400 (EDT) Date: Tue, 19 Oct 1999 12:21:18 -0400 (EDT) From: Adam McDougall X-Sender: mcdouga9@miyagi To: wpaul@skynet.ctr.columbia.edu Cc: current@freebsd.org Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm 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 Ah crap nevermind; I haven't had my coffee today. On Tue, 19 Oct 1999, Adam McDougall wrote: > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 10:31:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.keycomp.net (www.keycomp.net [207.44.1.33]) by hub.freebsd.org (Postfix) with ESMTP id 1A320177B1; Tue, 19 Oct 1999 10:31:44 -0700 (PDT) (envelope-from billieakay@yahoo.com) Received: from bopper (kc-rmt08.keycomp.net [207.44.1.10]) by www.keycomp.net (8.8.5/SCO5) with SMTP id NAA02580; Tue, 19 Oct 1999 13:38:24 -0400 (EDT) Message-ID: <000a01bf1a57$c486aaa0$0a012ccf@bopper> From: "Bill A. K." To: "FreeBSD Current ML" , "FreeBSD Questions" Subject: Solaris Binaries on FreeBSD Date: Tue, 19 Oct 1999 13:31:22 -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.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was wondering if we can run Solaris Binaries on our great OS? I've heard that OpenBSD can do it. If FreeBSD will, what do I need to do this? Thanks Bill billieakay@yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 11:33:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id ED86A178AA; Tue, 19 Oct 1999 11:33:43 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id OAA71321; Tue, 19 Oct 1999 14:33:28 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <199910191833.OAA71321@blackhelicopters.org> Subject: Re: Solaris Binaries on FreeBSD In-Reply-To: <000a01bf1a57$c486aaa0$0a012ccf@bopper> from "Bill A. K." at "Oct 19, 1999 1:31:22 pm" To: billieakay@yahoo.com (Bill A. K.) Date: Tue, 19 Oct 1999 14:33:28 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG, questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill, Yes, you can. You will need a copy of the Solaris shared libraries, which are not freely available. Poke around Sun's site for their $10 personal edition of Solaris X86. This will give you the libraries. Then search the freebsd-emulation archives for details on how to make this work. Regards, Michael > Hi, > I was wondering if we can run Solaris Binaries on our great OS? I've > heard that OpenBSD can do it. If FreeBSD will, what do I need to do this? > > Thanks > > Bill > billieakay@yahoo.com > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 12:25:40 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 5DD7C17A3F for ; Tue, 19 Oct 1999 12:25:32 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id PAA22615; Tue, 19 Oct 1999 15:25:27 -0400 (EDT) (envelope-from luoqi) Date: Tue, 19 Oct 1999 15:25:27 -0400 (EDT) From: Luoqi Chen Message-Id: <199910191925.PAA22615@lor.watermarkgroup.com> To: camel@avias.com Subject: Re: luoqi's aic driver problem Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > i've tried new "camfied" aic driver today and failed. here is a brief > report. > > my configuration: > > Chaintech 6BTM mainboard with Celeron 416A processor and 128 Mb of memory > Adaptec AIC-6360 SCSI controller (port 0x340 irq 9), irq 9 is reserved for > Legacy/ISA card in bios setup > Pinnacle 1000 CD writer (with SCSI device ID set to 0) > > kernel settings: > > options "CD9660" > options "CD9660_ROOT" > options SCSI_DELAY=15000 > controller scbus0 > controller aic0 at isa? port 0x340 irq 9 > device cd0 at aic? should be just "device cd0" > results: > > aic controller was successfully found by the kernel, but after "Waiting 15 > seconds for SCSI devices to settle" message it said the following: > > (probe0:aic0:0:0:0): REQUEST SENSE. CDB: 3 0 0 0 20 0 > (probe0:aic0:0:0:0): UNIT ATTENTION info?:1 asc:29,0 > (probe0:aic0:0:0:0): Power on, reset, or bus device reset occured > (probe0:aic0:0:0:1): REQUEST SENSE. CDB: 3 4 0 0 12 0 > (probe0:aic0:0:0:1): ILLEGAL REQEST asc:25,0 > (probe0:aic0:0:0:1): Logical unit not supported The request sense command clobbered the original command, I've changed the code from doing that, please download a new copy of aic.c file. > (probe0:aic0:0:0:2): ccb 0xc09c3000 - timed out > (probe0:aic0:0:0:2): ccb 0xc09c3000 - timed out Was there a long period between these two messages and the previous ones? Please try the new aic.c file, it will print out if a different command is holding up the scsi bus. > > after that my system just hangs. The timeout handling code is flaky, I need to understand how it should work a little better. > > what is possible reason of such behaviour and what should i try to do to > make my aic/cdrom combination working? > For now you could add a quirk entry for this drive to prevent multi-lun probing, until we figure out what went wrong. > thank you in advance. > > > sincerely, > ilya naumov (at work) > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 15:24:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from s5.elec.uq.edu.au (s5.elec.uq.edu.au [130.102.96.5]) by hub.freebsd.org (Postfix) with ESMTP id D0CE917AE8; Tue, 19 Oct 1999 15:24:47 -0700 (PDT) (envelope-from clary@s5.elec.uq.edu.au) Received: (from clary@localhost) by s5.elec.uq.edu.au (8.8.8/8.8.5) id IAA12877; Wed, 20 Oct 1999 08:24:46 +1000 (EST) From: Clary Harridge Message-Id: <199910192224.IAA12877@s5.elec.uq.edu.au> Subject: RAID V driver for DPT SCSI host adapter To: freebsd-current@freebsd.org, freebsd-scsi@freebsd.org Date: Wed, 20 Oct 1999 08:24:46 +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 Hi I have been told by Susan Handley at DPT Tech Support "that you can obtain a copy of our beta driver via the FreeBSD User News Group." Does anyone know where the driver can be obtained ? I need a driver for a DPT PM1554U2. Thanks! -- regards Department of Computer Science and Electrical Engineering, Clary Harridge University of Queensland, QLD, Australia, 4072 Phone: +61-7-3365-3636 Fax: +61-7-3365-4999 INTERNET: clary@csee.uq.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 15:29:30 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 09D4517F73; Tue, 19 Oct 1999 15:29:01 -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 HAA86016; Wed, 20 Oct 1999 07:58:57 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199910192228.HAA86016@gizmo.internode.com.au> Subject: Re: Solaris Binaries on FreeBSD To: billieakay@yahoo.com (Bill A. K.) Date: Wed, 20 Oct 1999 07:58:57 +0930 (CST) Cc: freebsd-current@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <000a01bf1a57$c486aaa0$0a012ccf@bopper> from "Bill A. K." at Oct 19, 99 01:31:22 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 Bill A. K. wrote: > I was wondering if we can run Solaris Binaries on our great OS? I've > heard that OpenBSD can do it. If FreeBSD will, what do I need to do this? Grab a copy of the Solaris/x86 libraries from Sun (they'll ship you a CD set for $10 which includes SPARC and x86 binaries). Then look at http://www.freebsd.org/~newton/freebsd-svr4/ to see how to make it work. Note that the module sources on the web page have not been tested with 3.x for a very long time. You really ought to be running -current to expect this to work. - 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 Tue Oct 19 16: 0:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id DFD0617FED; Tue, 19 Oct 1999 16:00:14 -0700 (PDT) (envelope-from andrews@technologist.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=wandrews) by neptune.psn.net with smtp (PSN Internet Service 2.12 #3) id 11diEn-0000Ql-00; Tue, 19 Oct 1999 16:00:14 -0700 Message-Id: <3.0.6.32.19991019190003.007ba100@mail.psn.net> X-Sender: andrews@mail.psn.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 19 Oct 1999 19:00:03 -0400 To: Peter Wemm From: Will Andrews Subject: Re: cvs commit: src/sys/i386/i386 nexus.c Cc: current@FreeBSD.ORG In-Reply-To: <199910191712.KAA68841@freefall.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 At 10:12 AM 10/19/99 -0700, you wrote: >peter 1999/10/19 10:12:29 PDT > > Modified files: > sys/i386/i386 nexus.c > Log: > Remove pccard attachment stub, this caused pccard unit 0 to be allocated > and unusable by the pccard system since pccard doesn't attach to the > nexus any more. This was stopping my 3c589D from working as pccard unit > 0 is used directly for resource allocation and this fails when unit 0 > isn't actually attached to anything. > > Revision Changes Path > 1.21 +1 -6 src/sys/i386/i386/nexus.c Thanks. While I do not really understand the implications that the code you removed from nexus has upon the pccard drivers, it seems that with this patch, I still can't get my PC-Card (3Com 3C574B, which worked under an earlier -CURRENT build) to work (i.e., I am still getting devclass problems that ignore pcic0, pcic1, and instead use the next device.. as you indicate your problem was). I suspect it may be because of a problem during the kernel build: in dev/ep/if_ep_pccard.c, line 239, in function ep_pccard_intr, there is a return with no value whereas the function is non-void..: static int ep_pccard_intr(devi) struct pccard_devinfo *devi; { struct ep_softc *sc = ep_softc[devi->isahd.id_unit]; if (sc->gone) { return; // This should have a return value. Suggest 0? But I'd // have to do a cxref to see what funcs call this. } ep_intr((void *)sc); return(1); // like this one. } Thus, if ep_pccard_intr (my 3C574B depends on the ep0 driver, so I figured this may have some effect on it not working) is an important function (I suspect your 3C589 depends on it), then perhaps this is why I'm unable to get my pccards working? However, since this is a fundamental pccard problem and does not appear limited to the ep driver, it seems like something else broke between September 29 (10:00 AM) and today. I will look through the last 2-3 weeks of commit logs on the kernel relating to pccard to see if i can dredge anything up. Thanks. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 17:12:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 7EBD21825C for ; Tue, 19 Oct 1999 17:12:38 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id CAA29870 for freebsd-current@FreeBSD.ORG; Wed, 20 Oct 1999 02:12:37 +0200 (CEST) (envelope-from olli) Date: Wed, 20 Oct 1999 02:12:37 +0200 (CEST) From: Oliver Fromme Message-Id: <199910200012.CAA29870@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: luoqi's aic driver problem Organization: Administration Heim 3 Reply-To: olli@incogni.to MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ilya Naumov wrote in list.freebsd-current: > Chaintech 6BTM mainboard with Celeron 416A processor and 128 Mb of memory Please excuse me -- what is a "Celeron 416A"? Regards Oliver Fromme -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 17:40: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 A0ED218311 for ; Tue, 19 Oct 1999 17:40: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; Tue, 19 Oct 1999 17:40:49 -0700 From: "David Schwartz" To: , Subject: RE: luoqi's aic driver problem Date: Tue, 19 Oct 1999 17:40:49 -0700 Message-ID: <000001bf1a93$c13c1c40$021d85d1@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: <199910200012.CAA29870@dorifer.heim3.tu-clausthal.de> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Probably a Celeron 333a running at an 83.5Mhz FSB. DS > Ilya Naumov wrote in list.freebsd-current: > > Chaintech 6BTM mainboard with Celeron 416A processor and 128 > Mb of memory > > Please excuse me -- what is a "Celeron 416A"? > > Regards > Oliver Fromme To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 18: 9:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.keycomp.net (www.keycomp.net [207.44.1.33]) by hub.freebsd.org (Postfix) with ESMTP id 7156F183DA; Tue, 19 Oct 1999 18:09:40 -0700 (PDT) (envelope-from billieakay@yahoo.com) Received: from bopper (kc-rmt09.keycomp.net [207.44.1.11]) by www.keycomp.net (8.8.5/SCO5) with SMTP id VAA05788; Tue, 19 Oct 1999 21:16:09 -0400 (EDT) Message-ID: <003001bf1a97$b9010960$0b012ccf@bopper> From: "Bill A. K." To: "Mark Newton" Cc: , References: <199910192228.HAA86016@gizmo.internode.com.au> Subject: Re: Solaris Binaries on FreeBSD Date: Tue, 19 Oct 1999 21:09:06 -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.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you the author of this emulation? I was wondering because Sun is now shipping Solaris 7.0, will this work? BTW I am running CURRENT Bill billieakay@yahoo.com ----- Original Message ----- From: Mark Newton To: Bill A. K. Cc: ; Sent: Tuesday, October 19, 1999 6:28 PM Subject: Re: Solaris Binaries on FreeBSD > Bill A. K. wrote: > > > I was wondering if we can run Solaris Binaries on our great OS? I've > > heard that OpenBSD can do it. If FreeBSD will, what do I need to do this? > > Grab a copy of the Solaris/x86 libraries from Sun (they'll ship you a > CD set for $10 which includes SPARC and x86 binaries). Then look > at http://www.freebsd.org/~newton/freebsd-svr4/ to see how to make it > work. > > Note that the module sources on the web page have not been tested with > 3.x for a very long time. You really ought to be running -current to > expect this to work. > > - 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 20:24:20 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 80E23184F9; Tue, 19 Oct 1999 20:24:07 -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 MAA86702; Wed, 20 Oct 1999 12:53:56 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199910200323.MAA86702@gizmo.internode.com.au> Subject: Re: Solaris Binaries on FreeBSD To: billieakay@yahoo.com (Bill A. K.) Date: Wed, 20 Oct 1999 12:53:56 +0930 (CST) Cc: newton@internode.com.au, freebsd-current@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <003001bf1a97$b9010960$0b012ccf@bopper> from "Bill A. K." at Oct 19, 99 09:09:06 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 Bill A. K. wrote: > Are you the author of this emulation? I'm the maintainer and the guy who ported it to FreeBSD. It's very heavily derived from code originally authored by Christos Zoulas for NetBSD. > I was wondering because Sun is now > shipping Solaris 7.0, will this work? Yup. - 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 Tue Oct 19 21:41:27 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 43EDC1A86C for ; Tue, 19 Oct 1999 21:41:12 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id AAA29426; Wed, 20 Oct 1999 00:40:36 -0400 (EDT) (envelope-from luoqi) Date: Wed, 20 Oct 1999 00:40:36 -0400 (EDT) From: Luoqi Chen Message-Id: <199910200440.AAA29426@lor.watermarkgroup.com> To: cdillon@wolves.k12.mo.us Subject: Re: aic driver camified Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 18 Oct 1999, Chris Dillon wrote: > > > Should this apply cleanly to -stable? If so, I'll give it a shot when > > I get home. > > I'll answer my own question (which, oddly enough, still hasn't made it > to the list after about two hours). I forgot about newbus. It > doesn't work, of course, and my Clue Quotient(TM) isn't high enough to > backport this to -stable. I think I'll teach myself how to do this > next weekend, if nobody else gets to it. :-) > I've ported it to -stable, but I don't have a machine to test it, please if you could. The code is in http://www.freebsd.org/~luoqi/aic/stable, apply patch files.diff, copy aic_isa.c to i386/isa, the rest goes to dev/aic. > > -- 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." > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 19 22:43:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id C52B71ACE8; Tue, 19 Oct 1999 22:43:18 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id HAA16808; Wed, 20 Oct 1999 07:42:52 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id HAA13557; Wed, 20 Oct 1999 07:42:51 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199910192224.IAA12877@s5.elec.uq.edu.au> References: <199910192224.IAA12877@s5.elec.uq.edu.au> Date: Wed, 20 Oct 1999 00:38:30 -0400 To: Clary Harridge , freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG From: Brad Knowles Subject: Re: RAID V driver for DPT SCSI host adapter Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:24 AM +1000 1999/10/20, Clary Harridge wrote: > I have been told by Susan Handley at DPT Tech Support > "that you can obtain a copy of our beta driver via the FreeBSD User >News Group." > > Does anyone know where the driver can be obtained ? This might be true (they were originally shooting for a 15 Oct release date), but I was supposed to get a copy of the drivers and a loaner card to benchmark about a month before release. Since I haven't seen or heard hide nor hair of this, I would be rather doubtful that the drivers have actually been released. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 2:19: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from www.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id AD57317775 for ; Wed, 20 Oct 1999 02:18:52 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by www.matti.ee (8.9.3/8.9.3) with ESMTP id MAA10068; Wed, 20 Oct 1999 12:18:12 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 22BA8FF; Wed, 20 Oct 1999 12:18:11 +0300 (EEST) Date: Wed, 20 Oct 1999 12:18:11 +0300 From: Vallo Kallaste To: Brett White Cc: freebsd-current@FreeBSD.ORG Subject: Re: 4.0-19991012-CURRENT Message-ID: <19991020121811.A9456@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <19991019095649.A14736@cs.rmit.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19991019095649.A14736@cs.rmit.edu.au>; from Brett White on Tue, Oct 19, 1999 at 09:56:49AM +1000 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 19, 1999 at 09:56:49AM +1000, Brett White wrote: > Has anyone tried using the 4.0-19991012-CURRENT snapshot? I > need to confirm that this snapshot is a "good one" before I > update my 3.3R installation to it in a last ditch effort to > compile USB modem support into the kernel. I have our mp3 machine running this snapshot, doing quite heavy NFS serving and of course runs Samba. The machine has one 37GB IBM ide disk and 32MB of memory, processor is good old 150Mhz PPro. No problems so far. -- 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 Wed Oct 20 3:12:59 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 650F61B2D8 for ; Wed, 20 Oct 1999 03:12:09 -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.3) with ESMTP id OAA02590; Wed, 20 Oct 1999 14:11:53 +0400 (MSD) (envelope-from camel@avias.com) Date: Wed, 20 Oct 1999 14:11:53 +0400 (MSD) From: Ilya Naumov To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: luoqi's aic driver problem In-Reply-To: <199910191925.PAA22615@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 Tue, 19 Oct 1999, Luoqi Chen wrote: > > i've tried new "camfied" aic driver today and failed. here is a brief > > report. > > > > results: > > > > aic controller was successfully found by the kernel, but after "Waiting 15 > > seconds for SCSI devices to settle" message it said the following: > > The request sense command clobbered the original command, I've changed the > code from doing that, please download a new copy of aic.c file. i have just tried it. the kernel boots successfully: aic0 at port 0x340-0x35f irq 9 on isa0 ... Waiting 15 seconds for SCSI devices to settle [here the CD-ROM drive flashes with its busy LED] (probe0:aic0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:aic0:0:0:0): UNIT ATTENTION info?:1 asc:29,0 (probe0:aic0:0:0:0): Power on, reset, or bus device reset occurred (probe0:aic0:0:0:1): INQUIRY. CDB: 12 20 0 0 24 0 (probe0:aic0:0:0:1): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:1): Logical unit not supported (probe0:aic0:0:0:2): INQUIRY. CDB: 12 40 0 0 24 0 (probe0:aic0:0:0:2): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:2): Logical unit not supported (probe0:aic0:0:0:3): INQUIRY. CDB: 12 60 0 0 24 0 (probe0:aic0:0:0:3): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:3): Logical unit not supported (probe0:aic0:0:0:4): INQUIRY. CDB: 12 80 0 0 24 0 (probe0:aic0:0:0:4): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:4): Logical unit not supported (probe0:aic0:0:0:5): INQUIRY. CDB: 12 a0 0 0 24 0 (probe0:aic0:0:0:5): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:5): Logical unit not supported (probe0:aic0:0:0:6): INQUIRY. CDB: 12 c0 0 0 24 0 (probe0:aic0:0:0:6): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:6): Logical unit not supported (probe0:aic0:0:0:7): INQUIRY. CDB: 12 e0 0 0 24 0 (probe0:aic0:0:0:7): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:7): Logical unit not supported ... cd0 at aic0 bus 0 target 0 lun 0 cd0: Removable Worm SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [1 x 77747 byte records] but, unfortunately, scsi probe precedure seems to be relatively unstable. _sometimes_ (often enough) the kernel doesn't boot with the following diagnostics: (probe0:aic0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:aic0:0:0:0): UNIT ATTENTION info?:1 asc:29,0 (probe0:aic0:0:0:0): Power on, reset, or bus device reset occured (probe0:aic0:0:0:1): INQURY. CDB: 12 20 0 0 24 0 (probe0:aic0:0:0:1): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:1): Logical unit not supported (probe0:aic0:0:0:2): INQURY. CDB: 12 40 0 0 24 0 (probe0:aic0:0:0:2): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:2): Logical unit not supported ccb 0xc0a23400 - timed out ccb 0xc0a23400 - timed out however, even after successful boot, the kernel traps after attempts to mount CD-ROM (mount_cd9660 /dev/cd0c /mnt). here is debug diags: (cd0:aic0:0:0:0): Vendor Specific Command. CDB: 43 0 0 0 0 0 b5 0 64 0 (cd0:aic0:0:0:0): ILLEGAL REQUEST asc:25,0 (cd0:aic0:0:0:0): Logical unit not supported (cd0:aic0:0:0:0): Vendor Specific Command. CDB: 43 0 0 0 0 0 b5 0 64 0 (cd0:aic0:0:0:0): ILLEGAL REQUEST asc:25,0 (cd0:aic0:0:0:0): Logical unit not supported (cd0:aic0:0:0:0): ccb 0xc0a23400 - timed out (cd0:aic0:0:0:0): ccb 0xc0a23400 - timed out then mount_cd9660 dies (cannot be killed with kill -9). > > (probe0:aic0:0:0:2): ccb 0xc09c3000 - timed out > > (probe0:aic0:0:0:2): ccb 0xc09c3000 - timed out > > Was there a long period between these two messages and the previous ones? yes, it was. > > what is possible reason of such behaviour and what should i try to do to > > make my aic/cdrom combination working? > > > For now you could add a quirk entry for this drive to prevent multi-lun > probing, ok, but how? :) 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 Oct 20 3:45:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.tue.nl (mailhost.tue.nl [131.155.2.5]) by hub.freebsd.org (Postfix) with ESMTP id DCA2A1B0AA for ; Wed, 20 Oct 1999 03:45:47 -0700 (PDT) (envelope-from K.R.A.M.Schreel@wtb.tue.nl) Received: from wop5.wop.wtb.tue.nl [131.155.56.55] by mailhost.tue.nl (8.9.3) id MAA06644 (ESMTP); Wed, 20 Oct 1999 12:45:46 +0200 (MDT) Received: from wtb.tue.nl (wop24.wop.wtb.tue.nl [131.155.56.116]) by wop5.wop.wtb.tue.nl (8.8.8/8.6.9) with ESMTP id KAA16912; Wed, 20 Oct 1999 10:45:45 GMT Message-ID: <380D9D5C.7A8F41FB@wtb.tue.nl> Date: Wed, 20 Oct 1999 12:45:48 +0200 From: Koen Schreel Organization: Eindhoven University of Technology X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Luoqi Chen Cc: current@freebsd.org Subject: Re: aic driver camified References: <199910181340.JAA27263@lor.watermarkgroup.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 also tried to experiment with the aic driver (and also failed, little similar to Ilya's problems) Configuration: Asus P2B-DS motherboard with dual PII-350, 128 Mb of memory, running 4.0-19990918-CURRENT. Adaptec AIC 7890 on-board U2W SCSI controller. Adaptec AVA 1505 (AIC 6360Q) isa SCSI controller. Connected to the isa card is a scanner (Genius Colorpage-I, announcing itself as a Microtek Scanmaker II) which is properly terminated and has SCSI id6. Kernel settings: controller aic0 at isa? port 0x340 irq 11 The controller is successfully found at boot time, but the boot `hangs' (or has a laaaarge timeout) with: (probe21:aic0:0:6:0)ccb 0xc0c01e00 - timed out (probe21:aic0:0:6:0)ccb 0xc0c01e00 - timed out Both messages appear shortly after each other and then the scanner seems to reinitialize. If I boot with the scanner switched off, the startup is completed normally. If I then switch on the scanner, let it initialize, and issue a `camcontrol rescan 1', the command never completes and is not killable. The command `camcontrol rescan 0' completes normally after which a `camcontrol devlist' correctly lists at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 2 lun 0 (pass1,cd0) as devices. What puzzles me is why the probe at the aic0 wants to look at bus 0. Shouldn't that be bus 1? Or should I add a scbus1 line in my config file (I think of this while I type, I will try this when I have sent this message) TIA Koen. -- Dr. K.R.A.M. Schreel | Eindhoven University of Technology | Faculty of Mechanical Engineering Combustion Research | Section Energy Technology | P. O. Box 513 K.R.A.M.Schreel@wtb.tue.nl | 5600 MB Eindhoven, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 4: 7: 5 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 397771B47B for ; Wed, 20 Oct 1999 04:07:02 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial8-232.netcologne.de [195.14.235.232]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id NAA01134; Wed, 20 Oct 1999 13:06:58 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id NAA00891; Wed, 20 Oct 1999 13:07:05 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Wed, 20 Oct 1999 13:07:05 +0200 (CEST) Message-Id: <199910201107.NAA00891@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: sthaug@nethelp.no Cc: van.woerkom@netcologne.de, freebsd-current@FreeBSD.ORG In-reply-to: <84276.940257732@verdi.nethelp.no> (sthaug@nethelp.no) Subject: Re: current unable to attach USB, Power Mgmt, sound Reply-To: van.woerkom@netcologne.de References: <199910180841.KAA02406@oranje.my.domain> <84276.940257732@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The following patch from Doug Rabson fixed the USB and sound problem for > me. It has already bee committed to -current. My AudioPCI card works again. Thanx! 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 Oct 20 5:54:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.tue.nl (mailhost.tue.nl [131.155.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 39A311B7AB for ; Wed, 20 Oct 1999 05:54:30 -0700 (PDT) (envelope-from K.R.A.M.Schreel@wtb.tue.nl) Received: from wop5.wop.wtb.tue.nl [131.155.56.55] by mailhost.tue.nl (8.9.3) id OAA16663 (ESMTP); Wed, 20 Oct 1999 14:54:28 +0200 (MDT) Received: from wtb.tue.nl (wop24.wop.wtb.tue.nl [131.155.56.116]) by wop5.wop.wtb.tue.nl (8.8.8/8.6.9) with ESMTP id MAA17744; Wed, 20 Oct 1999 12:54:27 GMT Message-ID: <380DBB85.BF035F2E@wtb.tue.nl> Date: Wed, 20 Oct 1999 14:54:29 +0200 From: Koen Schreel Organization: Eindhoven University of Technology X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Luoqi Chen Cc: cdillon@wolves.k12.mo.us, current@FreeBSD.ORG Subject: Re: aic driver camified References: <199910200440.AAA29426@lor.watermarkgroup.com> 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 wrote: > > I've ported it to -stable, but I don't have a machine to test it, please > if you could. The code is in http://www.freebsd.org/~luoqi/aic/stable, > apply patch files.diff, copy aic_isa.c to i386/isa, the rest goes to dev/aic. > I cannot compile a kernel. It reports the following errors: loading kernel aic_isa.o: In function `aic_isa_probe': aic_isa.o(.text+0x51): undefined reference to `aic_unit' aic_isa.o(.text+0x6c): undefined reference to `aic_probe' aic_isa.o(.text+0xeb): undefined reference to `aic_unit' aic_isa.o(.text+0xf4): undefined reference to `aic_unit' aic_isa.o: In function `aic_isa_attach': aic_isa.o(.text+0x125): undefined reference to `aic_softcs' aic_isa.o(.text+0x12b): undefined reference to `aic_softcs' aic_isa.o(.text+0x13e): undefined reference to `aic_attach' aic_isa.o: In function `aic_isa_intr': aic_isa.o(.text+0x15f): undefined reference to `aic_softcs' aic_isa.o(.text+0x165): undefined reference to `aic_intr' *** Error code 1 Stop. It looks as though aic.c is not compiled in. B.T.W., in fist line of aic.c a reference to aic.h is placed, but that file is not present in your directory. TIA Koen. -- Dr. K.R.A.M. Schreel | Eindhoven University of Technology | Faculty of Mechanical Engineering Combustion Research | Section Energy Technology | P. O. Box 513 K.R.A.M.Schreel@wtb.tue.nl | 5600 MB Eindhoven, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 7:54:11 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 E66021B3C2 for ; Wed, 20 Oct 1999 07:54:08 -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 KAA03070 for ; Wed, 20 Oct 1999 10:54:03 -0400 (EDT) Date: Wed, 20 Oct 1999 10:54:02 -0400 (EDT) From: "Matthew N. Dodd" To: current@freebsd.org Subject: 3c509 testers wanted! Message-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 rewritten the ISA bus front end code for if_ep and would like to solicit testers. ftp://ftp.jurai.net/users/winter/patches/if_ep.diff You'll have to edit sys/i386/isa/isa_compat.h and remove all the references to epdriver and NEP. Right now 'wired' devices aren't supported so use device ep0 in your config file. I'd especially like people with 3c509Bs to put them in PnP mode and try booting with this patch. I'd also like someome with several adapters to stuff a box with them and try booting. Of interest is the case where a 3c509B in PnP mode is installed as well as an older non-PnP 3c509. I suspect this combination will have 'issues' but am not sure. Boot verbosely and mail me the output, as well as the output of 'pnpinfo' if you're running a 3c509B. Thanks. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 8:17:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id 7229F1BBB2 for ; Wed, 20 Oct 1999 08:16:52 -0700 (PDT) (envelope-from steveroo@mothra.bri.hp.com) Received: from mothra.bri.hp.com (steveroo@mothra.bri.hp.com [15.144.1.185]) by atlrel2.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id LAA21992 for ; Wed, 20 Oct 1999 11:15:56 -0400 (EDT) Received: from localhost (steveroo@localhost) by mothra.bri.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id QAA14060 for ; Wed, 20 Oct 1999 16:15:30 +0100 (BST) Date: Wed, 20 Oct 1999 16:15:30 +0100 (BST) From: Stephen Roome To: current@freebsd.org Subject: Anyone adding "support" for Athlons. Message-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 the title says, is anyone working on support for Athlons, and when can we expect it to arrive back in -stable ? (I can't find anything in the latest versions of sys/i386/i386/identcpu.c) Also, what actually needs to be done, it doesn't look difficult to add code to recognise the cpu, what extra stuff to do may be harder, but I've not got round to reading the specs anyway. (egcs development seems to have athlon support now, I've not tried it and I've only seen patches so far by searching the mailing list) It would be great to find all the benefits of my shiny new hardware (actually it's beige =( ), if indeed there are that many. (perhaps the 3DNow stuff would give some advantages!) Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 8:33:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (picasso.transbay.net [209.133.53.6]) by hub.freebsd.org (Postfix) with ESMTP id 9E89014A13 for ; Wed, 20 Oct 1999 08:33:47 -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 IAA00886; Wed, 20 Oct 1999 08:23:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910201523.IAA00886@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Stephen Roome Cc: current@freebsd.org Subject: Re: Anyone adding "support" for Athlons. In-reply-to: Your message of "Wed, 20 Oct 1999 16:15:30 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Oct 1999 08:23:55 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > As the title says, is anyone working on support for Athlons, and when can we > expect it to arrive back in -stable ? > > (I can't find anything in the latest versions of sys/i386/i386/identcpu.c) You should try looking harder: CPU: AMD-K7(tm) Processor (499.03-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x612 Stepping = 2 Features=0x81f9ff AMD Features=0xc0400000<,,3DNow!> ... Pentium Pro MTRR support enabled > Also, what actually needs to be done, it doesn't look difficult to add code to > recognise the cpu, what extra stuff to do may be harder, but I've not got round > to reading the specs anyway. > > (egcs development seems to have athlon support now, I've not tried it and I've > only seen patches so far by searching the mailing list) > > It would be great to find all the benefits of my shiny new hardware (actually > it's beige =( ), if indeed there are that many. (perhaps the 3DNow stuff would > give some advantages!) I suggest you go read the documentation before you come back. No offense, just a caution to check more carefully first. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 9:35: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.worldwide.lemis.com (picasso.transbay.net [209.133.53.6]) by hub.freebsd.org (Postfix) with ESMTP id B41E714D6D for ; Wed, 20 Oct 1999 09:34:18 -0700 (PDT) (envelope-from grog@lemis.com) Received: (grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.6.12) id NAA01103; Mon, 18 Oct 1999 13:14:13 +1300 (NZDT) Message-ID: <19991018131412.28805@mojave.worldwide.lemis.com> Date: Mon, 18 Oct 1999 13:14:12 +1300 From: Greg Lehey To: Michael Reifenberger Cc: Matthew Jacob , FreeBSD-Current Subject: Re: -current crash References: <19991018125004.25271@mojave.worldwide.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Michael Reifenberger on Mon, Oct 18, 1999 at 02:09:49AM +0200 WWW-Home-Page: http://www.lemis.com/~grog 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, 18 October 1999 at 2:09:49 +0200, Michael Reifenberger wrote: > On Mon, 18 Oct 1999, Greg Lehey wrote: > >> Date: Mon, 18 Oct 1999 12:50:04 +1300 >> From: Greg Lehey >> To: Michael Reifenberger >> Cc: Matthew Jacob , FreeBSD-Current >> Subject: Re: -current crash > ... >> OK, this is what I was afraid of. I'm committing some fixes. > > Thanks. I'm leaving for the USA in a few hours. If you could test that before, it would help; otherwise it might be a while before I can look at it again. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 9:35: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.worldwide.lemis.com (picasso.transbay.net [209.133.53.6]) by hub.freebsd.org (Postfix) with ESMTP id 21F3014DB0 for ; Wed, 20 Oct 1999 09:34:18 -0700 (PDT) (envelope-from grog@lemis.com) Received: (grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.6.12) id MAA01019; Mon, 18 Oct 1999 12:50:05 +1300 (NZDT) Message-ID: <19991018125004.25271@mojave.worldwide.lemis.com> Date: Mon, 18 Oct 1999 12:50:04 +1300 From: Greg Lehey To: Michael Reifenberger Cc: Matthew Jacob , FreeBSD-Current Subject: Re: -current crash References: <19991018121619.01344@mojave.worldwide.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Michael Reifenberger on Mon, Oct 18, 1999 at 01:35:16AM +0200 WWW-Home-Page: http://www.lemis.com/~grog 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, 18 October 1999 at 1:35:16 +0200, Michael Reifenberger wrote: > On Mon, 18 Oct 1999, Greg Lehey wrote: > >> Date: Mon, 18 Oct 1999 12:16:19 +1300 >> From: Greg Lehey >> To: Michael Reifenberger , > Matthew Jacob >> Cc: FreeBSD-Current >> Subject: Re: -current crash > ... >> Have you rebuilt the kld? > > kernel,modules,world are in sync. > > The same configuration worked for several weeks without problems. > > BTW: where does the 0xdeadc0de (0xDeadCode ?) below come from? > > Info to frame5: > (kgdb) rq > Request: > { > bp = 0xdeadc0de, > flags = 0xc0261140, > volplex = { > volno = 0xdeadc0de, > plexno = 0xdeadc0de > }, > error = 0xc121c800, > sdno = 0xdeadc0de, > isplex = 0xc0de, > active = 0xdead, > rqg = 0xdeadc0de, > lrqg = 0xdeadc0de, > next = 0xdeadc0de > } > Cannot access memory at address 0xdeadc136. OK, this is what I was afraid of. I'm committing some fixes. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 9:35:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.worldwide.lemis.com (picasso.transbay.net [209.133.53.6]) by hub.freebsd.org (Postfix) with ESMTP id 07CA214DC2 for ; Wed, 20 Oct 1999 09:34:18 -0700 (PDT) (envelope-from grog@lemis.com) Received: (grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.6.12) id MAA00939; Mon, 18 Oct 1999 12:16:19 +1300 (NZDT) Message-ID: <19991018121619.01344@mojave.worldwide.lemis.com> Date: Mon, 18 Oct 1999 12:16:19 +1300 From: Greg Lehey To: Michael Reifenberger , Matthew Jacob Cc: FreeBSD-Current Subject: Re: -current crash References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Michael Reifenberger on Mon, Oct 18, 1999 at 12:43:21AM +0200 WWW-Home-Page: http://www.lemis.com/~grog 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, 18 October 1999 at 0:43:21 +0200, Michael Reifenberger wrote: > On Sun, 17 Oct 1999, Matthew Jacob wrote: > >> Date: Sun, 17 Oct 1999 15:08:10 -0700 (PDT) >> From: Matthew Jacob >> To: Michael Reifenberger >> Cc: FreeBSD-Current >> Subject: Re: -current crash >> >> >> Doesn't tell *me* a lot.... maybe a broken driver that's a KLD? It looks >> like something from spec_strategy is being called that's not in the >> /kernel space- could be a KLD- are your KLDs up to date for the new >> kernel? Like, is this vinum perhaps? > Seems so. After using the .gdbinit* stuff from modules/vinum I get the missing pices: > ... > #5 0xc101e91b in launch_requests (rq=0xc17d3f00, reviveok=0x0) > at /usr/src/sys/modules/vinum/../../dev/vinum/vinumrequest.c:387 > #6 0xc101e752 in vinumstart (bp=0xc62f8f30, reviveok=0x0) > at /usr/src/sys/modules/vinum/../../dev/vinum/vinumrequest.c:299 > #7 0xc101e54e in vinumstrategy (bp=0xc62f8f30) at > /usr/src/sys/modules/vinum/../../dev/vinum/vinnumrequest.c:164 > ... Have you rebuilt the kld? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 9:35:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.worldwide.lemis.com (picasso.transbay.net [209.133.53.6]) by hub.freebsd.org (Postfix) with ESMTP id 2EE9714E34 for ; Wed, 20 Oct 1999 09:34:18 -0700 (PDT) (envelope-from grog@lemis.com) Received: (grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.6.12) id MAA00858; Mon, 18 Oct 1999 12:09:58 +1300 (NZDT) Message-ID: <19991018120957.31058@mojave.worldwide.lemis.com> Date: Mon, 18 Oct 1999 12:09:57 +1300 From: Greg Lehey To: Michael Reifenberger , FreeBSD-Current , mjacob@feral.com Subject: Re: -current crash References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Michael Reifenberger on Sun, Oct 17, 1999 at 10:42:51PM +0200 WWW-Home-Page: http://www.lemis.com/~grog 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, 17 October 1999 at 22:42:51 +0200, Michael Reifenberger wrote: > Hi, > I got the following crash since a couple of time since upgrading one machine to > -current as of today. It seems to occurs during somewhat heavier diskaccess. > Sorry no detailed backtrace for now because I deleted my kernel.debug since the > last crash and dumping 256MB takes a long time... > > Does the crash trigger anything. > --- > #0 0xc0152368 in boot () > #0 0xc0152368 in boot () > #1 0xc0152741 in panic () > #2 0xc0211b40 in trap_fatal () > #3 0xc02117b1 in trap_pfault () > #4 0xc0211313 in trap () > #5 0xc101891b in ?? () > #6 0xc1018752 in ?? () > #7 0xc101854e in ?? () > #8 0xc0186a66 in spec_strategy () > #9 0xc018601d in spec_vnoperate () > #10 0xc01bb351 in ufs_vnoperatespec () > #11 0xc0173bf7 in bread () > #12 0xc01ac05b in ffs_update () > #13 0xc01b60d6 in ufs_inactive () > #14 0xc01bb321 in ufs_vnoperate () > #15 0xc017bf81 in vrele () > #16 0xc018257b in vn_close () > #17 0xc0182de8 in vn_closefile () > #18 0xc014a81d in fdrop () > #19 0xc014a7d3 in closef () > #20 0xc0149e0c in close () > #21 0xc0211df1 in syscall () > #22 0x200d44f1 in ?? () > > (kgdb) quit Well, without debugging symbols it's difficult to guess what's going on here. Frames 5 to 7 are interesting. Either you've run into the woods, or you're using a kld. Is this with Vinum, perhaps? If so, you should read vinum(4) or http://www.lemis.com/vinum/how-to-debug.html. Otherwise you should at least build a debug kernel; the references could help there too. On Sunday, 17 October 1999 at 13:50:27 -0700, Matthew Jacob wrote: > > Well, a DDB traceback would help. Failing that, at least what does > 0xc101891b correspond to.... otherwise, it's all ENOGUESS.... A ddb traceback will give you a little more information (some parameters), but I don't think that it's much better. -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 11:34:53 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 475DD14CBB for ; Wed, 20 Oct 1999 11:34:43 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id OAA10422 for ; Wed, 20 Oct 1999 14:34:40 -0400 (EDT) Message-Id: <3.0.5.32.19991020143339.016e0210@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 20 Oct 1999 14:33:39 -0400 To: freebsd-current@freebsd.org From: Mike Tancsa Subject: AMRD (MegaRAID) BIOS rev another other questions 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 else playing with the MegaRAID series of controllers ? I just started testing one out today (My Mylex comes later this week). I noticed the BIOS is V 1.38 dated June 10 1996. Should I upgrade it ? What have others tested / used? I have been playing for now with RAID 0 to get a sense of various performance settings, which can dramatically effect bonnie and iozone results. e.g. Write Back vs write through and stripe size. The eventual purpose will be for a SQUID server in a couple of months once the drivers are back ported. e.g. same drives, but with Write back and a 128K stripe size vs. the default -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 40 16341 99.1 20746 38.3 20307 52.7 14187 100.0 94033 98.2 9744.2 99.8 v.s. Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 40 10952 66.9 11622 22.6 9564 30.1 14230 100.0 63604 100.0 6944.5 99.8 ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 11:50:51 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 10B4514CE5 for ; Wed, 20 Oct 1999 11:50:40 -0700 (PDT) (envelope-from camel@avias.com) Received: from 192.168.2.2 (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.3) with ESMTP id WAA06728; Wed, 20 Oct 1999 22:49:04 +0400 (MSD) (envelope-from camel@avias.com) Date: Wed, 20 Oct 1999 22:45:01 +0400 From: Ilya Naumov X-Mailer: The Bat! (v1.36) UNREG / CD5BF9353B3B7091 Reply-To: Ilya Naumov X-Priority: 3 (Normal) Message-ID: <8947.991020@avias.com> To: Oliver Fromme Cc: freebsd-current@FreeBSD.ORG, olli@incogni.to Subject: Re[2]: luoqi's aic driver problem In-reply-To: <199910200012.CAA29870@dorifer.heim3.tu-clausthal.de> References: <199910200012.CAA29870@dorifer.heim3.tu-clausthal.de> 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 Oliver, Wednesday, October 20, 1999, 4:12:37 AM, you wrote: OF> > Chaintech 6BTM mainboard with Celeron 416A processor and 128 Mb of memory it is just Celeron 333A overclocked up to 416 MHz (5 x 83.5). 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 Oct 20 11:58:19 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 1A7C914D3D for ; Wed, 20 Oct 1999 11:58:16 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id OAA10099; Wed, 20 Oct 1999 14:57:55 -0400 (EDT) (envelope-from luoqi) Date: Wed, 20 Oct 1999 14:57:55 -0400 (EDT) From: Luoqi Chen Message-Id: <199910201857.OAA10099@lor.watermarkgroup.com> To: camel@avias.com Subject: Re: luoqi's aic driver problem Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > cd0 at aic0 bus 0 target 0 lun 0 > cd0: Removable Worm SCSI-2 device > cd0: 3.300MB/s transfers > cd0: cd present [1 x 77747 byte records] ^^^^^^^^^ These numbers don't look right... > but, unfortunately, scsi probe precedure seems to be relatively > unstable. _sometimes_ (often enough) the kernel doesn't boot with the > following diagnostics: > I have fixed a few places that might have caused the timeout problem. Could you download the new code and try again? Would you also add these debug options to your config file? 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" > > > what is possible reason of such behaviour and what should i try to do to > > > make my aic/cdrom combination working? > > > > > For now you could add a quirk entry for this drive to prevent multi-lun > > probing, > > ok, but how? :) > Add this entry to the xpt_quirk_table in cam/cam_xpt.c, { { T_WORM, SIP_MEDIA_REMOVABLE, "PINNACLE", "RCD*", "*" }, CAM_QUIRK_NOLUNS, /*mintags*/0, /*maxtags*/0 }, > sincerely, > ilya naumov (at work) > Thanks for trying the driver out, I really appreciate your patience. Since I don't have the hardware myself, I have to rely on your help. Thanks -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 12:18: 4 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 A1D7814CD1 for ; Wed, 20 Oct 1999 12:18:02 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id PAA10353; Wed, 20 Oct 1999 15:17:30 -0400 (EDT) (envelope-from luoqi) Date: Wed, 20 Oct 1999 15:17:30 -0400 (EDT) From: Luoqi Chen Message-Id: <199910201917.PAA10353@lor.watermarkgroup.com> To: K.R.A.M.Schreel@wtb.tue.nl Subject: Re: aic driver camified Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I also tried to experiment with the aic driver (and also failed, little > similar to Ilya's problems) > Could you download the new set of files and see if it helps? > as devices. What puzzles me is why the probe at the aic0 wants to look > at bus 0. Shouldn't that be bus 1? Or should I add a scbus1 line in my > config file (I think of this while I type, I will try this when I have > sent this message) I think this bus number is only used to differentiate the individual channels of multi-channel cards. What people usually refer to as bus id is actually the path id, unique for each hba + bus number combination. > > TIA > > Koen. > > > -- > Dr. K.R.A.M. Schreel | Eindhoven University of Technology > | Faculty of Mechanical Engineering > Combustion Research | Section Energy Technology > | P. O. Box 513 > K.R.A.M.Schreel@wtb.tue.nl | 5600 MB Eindhoven, The Netherlands > Thanks -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 12:22:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 7303614C11 for ; Wed, 20 Oct 1999 12:22:29 -0700 (PDT) (envelope-from kbyanc@alcnet.com) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from kbyanc (ws-41.alcnet.com [63.69.28.41]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id PAA37420; Wed, 20 Oct 1999 15:22:15 -0400 (EDT) From: "Kelly Yancey" To: Cc: Subject: Re: Anyone adding "support" for Athlons. Date: Wed, 20 Oct 1999 15:22:14 -0400 Message-ID: <007301bf1b30$6ac5eec0$291c453f@kbyanc.alcnet.com> 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 V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As the title says, is anyone working on support for Athlons, and when > can we expect it to arrive back in -stable ? > > (I can't find anything in the latest versions of sys/i386/i386/identcpu.c) > > Also, what actually needs to be done, it doesn't look difficult to add > code to recognise the cpu, what extra stuff to do may be harder, but I've > not got round to reading the specs anyway. > > (egcs development seems to have athlon support now, I've not tried it and > I've only seen patches so far by searching the mailing list) > > It would be great to find all the benefits of my shiny new hardware > (actually it's beige =( ), if indeed there are that many. (perhaps the > 3DNow stuff would give some advantages!) > > Steve Steve, could you try out the patches in PR i386/14438 and PR i386/14440 and see if your K7 is reported correctly? i386/14440 should cause it to display "Athlon" on boot; i386/14438 should cause all of the K7 feature bits to be reported. Kelly ~kbyanc@posi.net~ FreeBSD - The Power To Serve - http://www.freebsd.org/ Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 12:26: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 F286314C97 for ; Wed, 20 Oct 1999 12:26:34 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id PAA10475; Wed, 20 Oct 1999 15:25:31 -0400 (EDT) (envelope-from luoqi) Date: Wed, 20 Oct 1999 15:25:31 -0400 (EDT) From: Luoqi Chen Message-Id: <199910201925.PAA10475@lor.watermarkgroup.com> To: K.R.A.M.Schreel@wtb.tue.nl Subject: Re: aic driver camified Cc: cdillon@wolves.k12.mo.us, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luoqi Chen wrote: > > > > I've ported it to -stable, but I don't have a machine to test it, please > > if you could. The code is in http://www.freebsd.org/~luoqi/aic/stable, > > apply patch files.diff, copy aic_isa.c to i386/isa, the rest goes to dev/aic. > > > > I cannot compile a kernel. It reports the following errors: > Did the patch files.diff apply cleanly? It should add one line to each of the sys/conf/files and sys/i386/conf/files.i386, please make sure they are there. > It looks as though aic.c is not compiled in. B.T.W., in fist line of > aic.c a reference to aic.h is placed, but that file is not present in > your directory. > aic.h is generated by config, it should be present in the kernel compile directory. I compiled a kernel for -stable, but was unable to boot from it. Does anyone know if there is any incompatibility between the -current boot loader and a -stable kernel? > TIA > > Koen. > > > -- > Dr. K.R.A.M. Schreel | Eindhoven University of Technology > | Faculty of Mechanical Engineering > Combustion Research | Section Energy Technology > | P. O. Box 513 > K.R.A.M.Schreel@wtb.tue.nl | 5600 MB Eindhoven, The Netherlands > Thanks -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 14:44:58 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 B7FF014A0D for ; Wed, 20 Oct 1999 14:44:49 -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 RAA10959 for current@freebsd.org; Wed, 20 Oct 1999 17:49:12 -0400 From: Bill Paul Message-Id: <199910202149.RAA10959@skynet.ctr.columbia.edu> Subject: Texas Chainsaw Monday To: current@freebsd.org Date: Wed, 20 Oct 1999 17:49:11 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1592 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doing nightly build attempt for 4.0-19991020-CURRENT at Wed Oct 20 02:06:54 CDT 1999 Updating source tree... ? release.out Making release... Release build of 4.0-19991020-CURRENT was an abject failure. [...] ===> sbin/tunefs install -c -s -o root -g wheel -m 555 tunefs /vol2/release/sbin ===> sbin/umount install -c -s -o root -g wheel -m 555 umount /vol2/release/sbin ===> sbin/vinum install -c -s -o root -g wheel -m 555 vinum /vol2/release/sbin ===> sbin/kget install -c -s -o root -g wheel -m 555 kget /vol2/release/sbin ===> sbin/mount_nwfs install -c -s -o root -g wheel -m 555 mount_nwfs /vol2/release/sbin install: mount_nwfs: No such file or directory *** Error code 71 [...] Can somebody please explain this to me? The fact that mount_nwfs doesn't exist seems to indicate that compiling mount_nwfs failed. Yet if compiling mount_nwfs failed, why didn't it stop at the compilation failure? I suspect the answer has to do with some sort of obj directory problem, but it's impossible to tell that based on the build report. -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 Wed Oct 20 18:30:18 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 5402F14CAC for ; Wed, 20 Oct 1999 18:30:12 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA46224 for ; Wed, 20 Oct 1999 21:30:27 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 20 Oct 1999 21:30:27 -0400 (EDT) From: Chuck Robey To: current@freebsd.org Subject: call graph Message-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 wondering, is there any way to get a call-graph of the startup of FreeBSD (current) up until, say, the end of signle-user startup? One annotated with file/line info regarding funciton location? Not a line by line thing, but function call by function call? I was wondering if maybe there could be such a thing arising from the profiling code, or something like that. Sure would do me a *whole* lot of good, if I could get such a thing. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 18:57:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id 71AC114E1E for ; Wed, 20 Oct 1999 18:57:06 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 11e7Tj-000BNY-00; Thu, 21 Oct 1999 08:57:19 +0700 Date: Thu, 21 Oct 1999 08:57:19 +0700 (ALMST) From: Boris Popov To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: Texas Chainsaw Monday In-Reply-To: <199910202149.RAA10959@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 On Wed, 20 Oct 1999, Bill Paul wrote: > install -c -s -o root -g wheel -m 555 mount_nwfs /vol2/release/sbin > install: mount_nwfs: No such file or directory Ok, it seems that I found why mount_nwfs failed to build: I'm use 'install' instead of ${INSTALL} in the libncp. > Can somebody please explain this to me? The fact that mount_nwfs doesn't > exist seems to indicate that compiling mount_nwfs failed. Yet if compiling > mount_nwfs failed, why didn't it stop at the compilation failure? Yep, that strange why build isn't failed. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 20 23:54:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id 64BD814E93 for ; Wed, 20 Oct 1999 23:54:49 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id JAA13238; Thu, 21 Oct 1999 09:53:06 +0300 (EEST) (envelope-from will) To: Stephen Roome Cc: current@freebsd.org Subject: Re: Anyone adding "support" for Athlons. References: From: Ville-Pertti Keinonen Date: 21 Oct 1999 09:53:06 +0300 In-Reply-To: Stephen Roome's message of "20 Oct 1999 18:18:17 +0300" Message-ID: <86zoxd19yl.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 Stephen Roome writes: > As the title says, is anyone working on support for Athlons, and when can we > expect it to arrive back in -stable ? Athlons don't need any special support, they are fully compatible with Intel's latest processors. > (I can't find anything in the latest versions of sys/i386/i386/identcpu.c) The identification for AMD processors models that can report their name using cpuid is redundant, even for cpus that are currently listed there. I don't know whether this is intentional. It seems that currently, the policy of identcpu.c is to prefer the cpuid string, so the patch in pr i386/14440 should be a no-op. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 1:44:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 3623414EE1 for ; Thu, 21 Oct 1999 01:44:28 -0700 (PDT) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 3A90A1DBF; Thu, 21 Oct 1999 10:44:37 +0200 (CEST) Date: Thu, 21 Oct 1999 10:44:37 +0200 From: "Dave J. Boers" To: freebsd-current@freebsd.org Subject: ata - disk "contact" lost.... Message-ID: <19991021104437.A66476@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been having strange problems with the ata drivers (again). At seemingly random moments "disk contact" seems to be lost. I've been seeing these messages before a few weeks ago. The problem is *not* there if I use the wd drivers. Also the problem seems only to appear after a few days of uptime. Below follows the info. Any help would be much appreciated. Should I worry about disk integrity? If you need more info, please let me know. Best regards, Dave Boers. -- Dave J. Boers djb@relativity.student.utwente.nl I will *NOT* read email sent to Graduate student of Theoretical Physics d.j.boers@student.utwente.nl -------------------------------------------------------------------------- *** uname -a: FreeBSD relativity.student.utwente.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Mon Oct 18 10:53:01 CEST 1999 root@:/usr/src/sys/compile/RELATIVITY1 i386 *** uptime: 10:33AM up 3 days, 1:37, 7 users, load averages: 0.04, 0.03, 0.00 NOTE: the messages below are the *only* ones since the boot of the system three days ago. Also, the messages are (to within a minute) twelve hours apart. It is unlikely that there is some sort of power glitch; the system is hooked up to an ups. Finally, the messages appeared when the machine was idle. Power management is turned off of course. *** /var/log/messages: Oct 20 22:06:39 relativity /kernel: ata0-master: ad_timeout: lost disk contact - resetting Oct 20 22:06:51 relativity /kernel: ata0: resetting devices .. done Oct 20 22:06:51 relativity /kernel: ata0-master: ad_timeout: lost disk contact - resetting Oct 20 22:06:51 relativity /kernel: ata0: resetting devices .. done Oct 20 22:06:51 relativity /kernel: ata0-master: ad_timeout: lost disk contact - resetting Oct 20 22:06:51 relativity /kernel: ata0: resetting devices .. done Oct 20 22:06:51 relativity /kernel: ata0-master: ad_timeout: lost disk contact - resetting Oct 20 22:06:51 relativity /kernel: ata0: resetting devices .. done Oct 20 22:06:51 relativity /kernel: ata0-master: ad_timeout: lost disk contact - resetting Oct 20 22:06:51 relativity /kernel: ata0: resetting devices .. done Oct 21 10:07:24 relativity /kernel: ata0-master: ad_timeout: lost disk contact - resetting Oct 21 10:07:24 relativity /kernel: ata0: resetting devices .. done *** bootup: 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: Fri Oct 15 14:33:44 CEST 1999 root@:/usr/src/sys/compile/RELATIVITY1 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Celeron (450.00-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 134152192 (131008K bytes) avail memory = 126935040 (123960K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc030e000. Preloaded elf module "vesa.ko" at 0xc030e09c. VESA: v3.0, 7936k memory, flags:0x1, mode table:0xc030b102 (1000022) VESA: NVidia Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 16 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ide_pci0: at device 7.1 on pci0 chip1: at device 7.2 on pci0 intpm0: at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 ed0: irq 19 at device 9.0 on pci0 ed0: address 00:20:18:2d:d5:2b, type NE2000 (16 bit) ahc0: irq 18 at device 11.0 on pci0 ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs pci0: unknown card (vendor=0x10b7, dev=0x9055) at 13.0 irq 17 pci0: unknown card (vendor=0x1103, dev=0x0004) at 19.0 irq 18 pci0: unknown card (vendor=0x1103, dev=0x0004) at 19.1 irq 18 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 17206MB (35239680 sectors), 34960 cyls, 16 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: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: HP ENHANCED PCL5,PJL plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pcm0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 unknown0: at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 unknown1: at port 0x100 on isa0 unknown2: at port 0x200-0x207 on isa0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging limited to 100 packets/entry by default Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! Creating DISK da0 Creating DISK cd0 Creating DISK cd1 changing root device to wd0s1a cd0 at ahc0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: cd present [338924 x 2048 byte records] cd1 at ahc0 bus 0 target 4 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 8) cd1: 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: 20.000MB/s transfers (20.000MHz, offset 15) da0: 4157MB (8515173 512 byte sectors: 255H 63S/T 530C) xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 17 at device 13.0 on pci0 xl0: Ethernet address: 00:10:5a:65:33:80 pci0: unknown card (vendor=0x1103, dev=0x0004) at 19.0 irq 18 pci0: unknown card (vendor=0x1103, dev=0x0004) at 19.1 irq 18 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto The end. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 2: 1:24 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 4DD6814EB3 for ; Thu, 21 Oct 1999 02:01:18 -0700 (PDT) (envelope-from erik@habatech.no) Received: from bsdbox.habatech.no ([62.92.133.3]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id LAA03707; Thu, 21 Oct 1999 11:01:10 +0200 (CEST) (envelope-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: <19991021104437.A66476@relativity.student.utwente.nl> Date: Thu, 21 Oct 1999 11:00:59 +0200 (CEST) From: "Erik H. Bakke" To: "Dave J. Boers" Subject: RE: ata - disk "contact" lost.... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Oct-99 Dave J. Boers wrote: > I've been having strange problems with the ata drivers (again). At seemingly > random moments "disk contact" seems to be lost. I've been seeing these > messages before a few weeks ago. The problem is *not* there if I use the wd > drivers. Also the problem seems only to appear after a few days of uptime. > Below follows the info. > > Any help would be much appreciated. Should I worry about disk integrity? > > If you need more info, please let me know. > This seems to be the same problem some other people on this list have been suffering, including me. Some days ago there was posted a patch that seems to solve the problem. The patch is still being tested, but hopefully, the person responsible will commit it soon. If you can't find it, give me a word and I'll dig it up for you. ===========================+================+=============================== Erik H. Bakke | | To be or not to be... Senior Consultant/Developer|erik@habatech.no| Is simply a question of Habatech AS | | binary logic ===========================+================+============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 2:18:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (Postfix) with ESMTP id D614514ED1 for ; Thu, 21 Oct 1999 02:18:28 -0700 (PDT) (envelope-from freebsd@xaa.iae.nl) Received: by esmeralda.xaa.iae.nl (Postfix, from userid 1008) id 4A008BA03; Thu, 21 Oct 1999 11:18:27 +0200 (MET DST) Date: Thu, 21 Oct 1999 11:18:27 +0200 From: Mark Huizer To: Roelof Osinga Cc: John Polstra , current@FreeBSD.ORG Subject: Re: New CVSup mirror sites Message-ID: <19991021111827.A89051@esmeralda.xaa.iae.nl> References: <37FBA256.E7E2F148@nisser.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <37FBA256.E7E2F148@nisser.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One common misconception is that cvsup(N+1).FreeBSD.org is somehow > > less up-to-date than or not as good as cvsup(N).FreeBSD.org. That's > > not the case at all -- the numbers mean nothing. For example, all 7 > > of the US mirror sites get their updates hourly from the same master > > site. (So do most of the non-US mirrors.) The only reasons to choose > > Most, but not all. Is it possible to list that information too. As well > as an on easily found place. > > The link on the mainform gives http://www.nl.freebsd.org/support.html#cvs > which does not list that information. A search gives over 25 documents, > one of which is http://www.freebsd.org/handbook/mirrors-cvsup.html > which also does not list that tidbit. > > I switched from the dutch mirror to an UK one because the latter was > more up to date. So now there is a new dutch mirror. However, it is > not clear how up to date it is. > Huh what? I have some trouble building the www site but I will work on that after my holiday. But the mirror is update every four hours at the moment. Should it be every hour? No problem with me Mark -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 2:35:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from trans.germany.net (trans.germany.net [151.189.0.16]) by hub.freebsd.org (Postfix) with ESMTP id 9BC7114C81 for ; Thu, 21 Oct 1999 02:35:11 -0700 (PDT) (envelope-from bsd@picard.mandrakesoft.de) Received: from picard.mandrakesoft.de (root@picard.mandrakesoft.de [151.189.96.131]) by trans.germany.net (8.8.8/8.8.8) with ESMTP id LAA15737; Thu, 21 Oct 1999 11:35:08 +0200 (MET DST) Received: from localhost (bsd@localhost) by picard.mandrakesoft.de (8.9.3/8.9.3) with ESMTP id LAA16881; Thu, 21 Oct 1999 11:38:28 +0200 Date: Thu, 21 Oct 1999 11:38:28 +0200 (CEST) From: Bernhard Rosenkraenzer To: Brett White Cc: freebsd-current@FreeBSD.ORG Subject: Re: 4.0-19991012-CURRENT In-Reply-To: <19991019095649.A14736@cs.rmit.edu.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 Tue, 19 Oct 1999, Brett White wrote: > Has anyone tried using the 4.0-19991012-CURRENT snapshot? It's ok here on a K6 and on a dual Pentium III, but it won't even boot on a notebook with a Mobile Celeron processor. LLaP bero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 2:57: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 9BD4014EF5 for ; Thu, 21 Oct 1999 02:57:12 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id CAA95452 for ; Thu, 21 Oct 1999 02:57:11 -0700 (PDT) Date: Thu, 21 Oct 1999 02:57:11 -0700 (PDT) From: Julian Elischer To: current@freebsd.org Subject: Small HEADS UP! Message-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.e. only for those with small heads.. I just checked in a relatively large set of new files and a few patches. The are the 'Netgraph' link layer networking infrastructure. They SHOULDN'T cause problems if not compiled in, but.... As I write a "make world" is proceding but has not finished yet. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 3: 3:18 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 4E45C14EF5 for ; Thu, 21 Oct 1999 03:03:15 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 0C03B1926; Thu, 21 Oct 1999 12:03:18 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 0B25C49CF; Thu, 21 Oct 1999 12:03:18 +0200 (CEST) Date: Thu, 21 Oct 1999 12:03:17 +0200 (CEST) From: Andrzej Bialecki To: Julian Elischer Cc: current@freebsd.org Subject: Re: Small HEADS UP! 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, 21 Oct 1999, Julian Elischer wrote: > > i.e. only for those with small heads.. > > I just checked in a relatively large set of new files and a few patches. > The are the 'Netgraph' link layer networking infrastructure. > They SHOULDN'T cause problems if not compiled in, but.... > > As I write a "make world" is proceding but has not finished yet. Excellent! At last! Thank you and Whistle for making this code available! 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 Thu Oct 21 6: 2:56 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 F083914EA2; Thu, 21 Oct 1999 06:02:19 -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.3) with ESMTP id RAA14023; Thu, 21 Oct 1999 17:02:12 +0400 (MSD) (envelope-from camel@avias.com) Date: Thu, 21 Oct 1999 17:02:12 +0400 (MSD) From: Ilya Naumov To: luoqi@freebsd.org Cc: current@freebsd.org Subject: hooray! aic driver works! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i have just tried the latest version of aic cam driver by Luoqi, and it seems that all significant problems were solved. aic0 at port 0x340-0x35f irq 9 on isa0 ... Waiting 15 seconds for SCSI devices to settle (probe0:aic0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:aic0:0:0:0): UNIT ATTENTION info?:1 asc:29,0 (probe0:aic0:0:0:0): Power on, reset, or bus device reset occurred (probe0:aic0:0:0:1): INQUIRY. CDB: 12 20 0 0 24 0 (probe0:aic0:0:0:1): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:1): Logical unit not supported (probe0:aic0:0:0:2): INQUIRY. CDB: 12 40 0 0 24 0 (probe0:aic0:0:0:2): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:2): Logical unit not supported (probe0:aic0:0:0:3): INQUIRY. CDB: 12 60 0 0 24 0 (probe0:aic0:0:0:3): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:3): Logical unit not supported (probe0:aic0:0:0:4): INQUIRY. CDB: 12 80 0 0 24 0 (probe0:aic0:0:0:4): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:4): Logical unit not supported (probe0:aic0:0:0:5): INQUIRY. CDB: 12 a0 0 0 24 0 (probe0:aic0:0:0:5): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:5): Logical unit not supported (probe0:aic0:0:0:6): INQUIRY. CDB: 12 c0 0 0 24 0 (probe0:aic0:0:0:6): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:6): Logical unit not supported (probe0:aic0:0:0:7): INQUIRY. CDB: 12 e0 0 0 24 0 (probe0:aic0:0:0:7): ILLEGAL REQUEST asc:25,0 (probe0:aic0:0:0:7): Logical unit not supported ... Creating DISK cd0 cd0 at aic0 bus 0 target 0 lun 0 cd0: Removable Worm SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [261890 x 2048 byte records] drive mounts without any problems and correctly reads data from CD-ROMS. great work, Luoqi! thank you very much! 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 Thu Oct 21 6:49:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from nisser.com (c1870039.telekabel.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 2D4FC14C03 for ; Thu, 21 Oct 1999 06:49:23 -0700 (PDT) (envelope-from roelof@nisser.com) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id PAA14524; Thu, 21 Oct 1999 15:52:17 +0200 (CEST) (envelope-from roelof@nisser.com) Message-ID: <380F19CA.21ADA68B@nisser.com> Date: Thu, 21 Oct 1999 15:48:58 +0200 From: Roelof Osinga Organization: eboa - engineering buro Office Automation X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Mark Huizer Cc: John Polstra , current@FreeBSD.ORG Subject: Re: New CVSup mirror sites References: <37FBA256.E7E2F148@nisser.com> <19991021111827.A89051@esmeralda.xaa.iae.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Huizer wrote: > > Huh what? > I have some trouble building the www site but I will work on that after > my holiday. > But the mirror is update every four hours at the moment. Should it be > every hour? No problem with me Why not? I don't think it is that big a drain. Once it's up to date it's up to date. The frequency should not impact the amount of transfer significantly, barring the extra handshake activities. Mayhap a future version will even signal the dependents much like BIND 8 does. As to my remarks regarding the dutch mirror. That was the status then. Don't know the current state of affairs. Roelof -- Home is where the (@) http://eboa.com/ is. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 7: 4: 2 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 3F07E14A28 for ; Thu, 21 Oct 1999 07:03:59 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p24-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.153]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id XAA23109; Thu, 21 Oct 1999 23:03:44 +0900 (JST) Message-ID: <380ED764.D12571CE@newsguy.com> Date: Thu, 21 Oct 1999 18:05:40 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Luoqi Chen Cc: K.R.A.M.Schreel@wtb.tue.nl, cdillon@wolves.k12.mo.us, current@FreeBSD.ORG Subject: Re: aic driver camified References: <199910201925.PAA10475@lor.watermarkgroup.com> 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 wrote: > > I compiled a kernel for -stable, but was unable to boot from it. Does anyone > know if there is any incompatibility between the -current boot loader and a > -stable kernel? AFAIK, there is no difference between them (the loaders :). Try from boot2. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "People call him Neutron Star, 'cuz he's so dense lights bends around him." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 7: 4:10 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 4570814CC8 for ; Thu, 21 Oct 1999 07:04:02 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p24-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.153]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id XAA23139; Thu, 21 Oct 1999 23:03:50 +0900 (JST) Message-ID: <380ED764.D12571CE@newsguy.com> Date: Thu, 21 Oct 1999 18:05:40 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Luoqi Chen Cc: K.R.A.M.Schreel@wtb.tue.nl, cdillon@wolves.k12.mo.us, current@FreeBSD.ORG Subject: Re: aic driver camified References: <199910201925.PAA10475@lor.watermarkgroup.com> 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 wrote: > > I compiled a kernel for -stable, but was unable to boot from it. Does anyone > know if there is any incompatibility between the -current boot loader and a > -stable kernel? AFAIK, there is no difference between them (the loaders :). Try from boot2. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "People call him Neutron Star, 'cuz he's so dense lights bends around him." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 7:20:23 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 634E814DCA for ; Thu, 21 Oct 1999 07:20:19 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA11956; Thu, 21 Oct 1999 10:20:18 -0400 (EDT) (envelope-from luoqi) Date: Thu, 21 Oct 1999 10:20:18 -0400 (EDT) From: Luoqi Chen Message-Id: <199910211420.KAA11956@lor.watermarkgroup.com> To: dcs@newsguy.com Subject: Re: aic driver camified Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luoqi Chen wrote: > > > > I compiled a kernel for -stable, but was unable to boot from it. Does anyone > > know if there is any incompatibility between the -current boot loader and a > > -stable kernel? > > AFAIK, there is no difference between them (the loaders :). > > Try from boot2. > It was not the loader, it was the config file. I used a -current config file without those spl levels, no wonder the machine hung at its earliest convenience... > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "People call him Neutron Star, 'cuz he's so dense lights bends > around him." > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 7:57:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id D28C714EA7 for ; Thu, 21 Oct 1999 07:57:30 -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 dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id HAA65370 for ; Thu, 21 Oct 1999 07:57:09 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Message-ID: <380F2A04.3D268C54@MexComUSA.NET> Date: Thu, 21 Oct 1999 07:58:13 -0700 From: Edwin Culp Organization: EnContacto.NET X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: Make world this morning Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just saw my log file from this mornings make world. ed cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc/../libc/gen/getcwd.c -o getcwd.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc/../libc/gen/getdomainname.c -o getdomainname.o cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc/../libc/gen/getgrent.c -o getgrent.o In file included from /usr/obj/usr/src/tmp/usr/include/rpc/auth.h:47, from /usr/obj/usr/src/tmp/usr/include/rpc/rpc.h:50, from /usr/src/lib/libc/../libc/gen/getgrent.c:49: /usr/obj/usr/src/tmp/usr/include/sys/socket.h:133: syntax error before `interface' /usr/obj/usr/src/tmp/usr/include/sys/socket.h:146: syntax error before `}' *** Error code 1 Stop in /usr/src/lib/libc. *** Error code 1 Stop in /usr/src. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 8: 4:59 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 3378C14D12 for ; Thu, 21 Oct 1999 08:04:58 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id IAA00328; Thu, 21 Oct 1999 08:04:56 -0700 (PDT) Date: Thu, 21 Oct 1999 08:04:55 -0700 (PDT) From: Julian Elischer To: Edwin Culp Cc: "current@FreeBSD.ORG" Subject: Re: Make world this morning In-Reply-To: <380F2A04.3D268C54@MexComUSA.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 re-sup On Thu, 21 Oct 1999, Edwin Culp wrote: > I just saw my log file from this mornings make world. > > ed > > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include > -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE > -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP > -I/usr/obj/usr/src/tmp/usr/include -c > /usr/src/lib/libc/../libc/gen/getcwd.c -o getcwd.o > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include > -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE > -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP > -I/usr/obj/usr/src/tmp/usr/include -c > /usr/src/lib/libc/../libc/gen/getdomainname.c -o getdomainname.o > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include > -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE > -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP > -I/usr/obj/usr/src/tmp/usr/include -c > /usr/src/lib/libc/../libc/gen/getgrent.c -o getgrent.o > In file included from /usr/obj/usr/src/tmp/usr/include/rpc/auth.h:47, > from /usr/obj/usr/src/tmp/usr/include/rpc/rpc.h:50, > from /usr/src/lib/libc/../libc/gen/getgrent.c:49: > /usr/obj/usr/src/tmp/usr/include/sys/socket.h:133: syntax error before > `interface' > /usr/obj/usr/src/tmp/usr/include/sys/socket.h:146: syntax error before > `}' > *** Error code 1 > > Stop in /usr/src/lib/libc. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > > > > 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 Oct 21 8:10:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 3D8A814D01 for ; Thu, 21 Oct 1999 08:10:08 -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 dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id IAA65414; Thu, 21 Oct 1999 08:09:46 -0700 (PDT) (envelope-from eculp@MexComUSA.NET) Message-ID: <380F2CFA.B1AA7246@MexComUSA.NET> Date: Thu, 21 Oct 1999 08:10:50 -0700 From: Edwin Culp Organization: EnContacto.NET X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: "current@FreeBSD.ORG" Subject: Re: Make world this morning References: 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 in the process, thank you. ed Julian Elischer wrote: > re-sup > > On Thu, 21 Oct 1999, Edwin Culp wrote: > > > I just saw my log file from this mornings make world. > > > > ed > > > > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include > > -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE > > -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP > > -I/usr/obj/usr/src/tmp/usr/include -c > > /usr/src/lib/libc/../libc/gen/getcwd.c -o getcwd.o > > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include > > -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE > > -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP > > -I/usr/obj/usr/src/tmp/usr/include -c > > /usr/src/lib/libc/../libc/gen/getdomainname.c -o getdomainname.o > > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include > > -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE > > -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP > > -I/usr/obj/usr/src/tmp/usr/include -c > > /usr/src/lib/libc/../libc/gen/getgrent.c -o getgrent.o > > In file included from /usr/obj/usr/src/tmp/usr/include/rpc/auth.h:47, > > from /usr/obj/usr/src/tmp/usr/include/rpc/rpc.h:50, > > from /usr/src/lib/libc/../libc/gen/getgrent.c:49: > > /usr/obj/usr/src/tmp/usr/include/sys/socket.h:133: syntax error before > > `interface' > > /usr/obj/usr/src/tmp/usr/include/sys/socket.h:146: syntax error before > > `}' > > *** Error code 1 > > > > Stop in /usr/src/lib/libc. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > > > > > > > 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 Thu Oct 21 10: 5: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id A511E14F5B for ; Thu, 21 Oct 1999 10:04:58 -0700 (PDT) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.10 1999/10/20 18:19:05 spurcell Exp $) with ESMTP id KAA19613 for ; Thu, 21 Oct 1999 10:04:57 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.8 1999/04/16 15:25:49 steved Exp steved $) with ESMTP id KAA08533 for ; Thu, 21 Oct 1999 10:04:56 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id NAA24207; Thu, 21 Oct 1999 13:05:10 -0400 (EDT) From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14351.18373.418811.886740@hip186.ch.intel.com> Date: Thu, 21 Oct 1999 10:05:09 -0700 (MST) To: freebsd-current@freebsd.org Subject: Intel PRO/1000 Gigabit driver X-Mailer: VM 6.75 under Emacs 19.34.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A friend just passed this along: http://www.newsalert.com/bin/story?StoryId=Coa6pWbKbyte0mtu Intel PRO/1000 Gigabit support for Linux. Source code too (non-GPL'ed very much like a BSD-ish license). I don't have the technicals to understand how hard it would be to port, but the code is there for those who do! :) -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds CEG, CCE, Next Generation Flows, HLA | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 10: 8:24 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 18F2314CC5 for ; Thu, 21 Oct 1999 10:08:22 -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 KAA10226; Thu, 21 Oct 1999 10:08:20 -0700 Date: Thu, 21 Oct 1999 10:08:21 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Reynolds~ Cc: freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit driver In-Reply-To: <14351.18373.418811.886740@hip186.ch.intel.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 Odd you should mention this. I have two cards and a plea from a customer to port it... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 10:21:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from cx281057-a.irvn1.occa.home.com (cx281057-a.irvn1.occa.home.com [24.5.32.114]) by hub.freebsd.org (Postfix) with ESMTP id 424E514E2F for ; Thu, 21 Oct 1999 10:21:50 -0700 (PDT) (envelope-from housel@cx281057-a.irvn1.occa.home.com) Received: from cx281057-a.irvn1.occa.home.com (localhost [127.0.0.1]) by cx281057-a.irvn1.occa.home.com (8.9.3/8.9.3) with ESMTP id KAA08545 for ; Thu, 21 Oct 1999 10:20:34 -0700 (PDT) (envelope-from housel@cx281057-a.irvn1.occa.home.com) Message-Id: <199910211720.KAA08545@cx281057-a.irvn1.occa.home.com> From: "Peter S. Housel" To: current@FreeBSD.org Subject: ed0 problems for PCI Date: Thu, 21 Oct 1999 10:20:34 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been having problems with -current not recognizing my RealTek 8029-based PCI Ethernet card. It worked fine in my previous machine running -current from July, but neither the late September snapshot that I installed on the new machine nor the cvsup version from about a week ago can configure the card. The pciconf and dmesg output are shown below: chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x71908086 rev=0x03 hdr=0x00 pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x71918086 rev=0x03 hdr=0x01 isab0@pci0:7:0: class=0x060100 card=0x00000000 chip=0x71108086 rev=0x02 hdr=0x00 ide_pci0@pci0:7:1: class=0x010180 card=0x00000000 chip=0x71118086 rev=0x01 hdr=0x00 chip1@pci0:7:2: class=0x0c0300 card=0x00000000 chip=0x71128086 rev=0x01 hdr=0x00 chip2@pci0:7:3: class=0x068000 card=0x00000000 chip=0x71138086 rev=0x02 hdr=0x00 none0@pci0:14:0: class=0x040100 card=0x33565053 chip=0x000212eb rev=0xfe hdr=0x00 ed0@pci0:17:0: class=0x020000 card=0x03001186 chip=0x802910ec rev=0x00 hdr=0x00 vga-pci0@pci1:0:0: class=0x030000 card=0x5a001092 chip=0x002810de rev=0x11 hdr=0x00 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 #2: Tue Oct 19 21:20:08 PDT 1999 root@cx281057-a.irvn1.occa.home.com:/usr/src/sys/compile/MONDAY Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Xeon (598.62-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 134217728 (131072K bytes) avail memory = 127332352 (124348K bytes) Preloaded elf kernel "kernel" at 0xc02bd000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 11 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ide_pci0: at device 7.1 on pci0 chip1: irq 9 at device 7.2 on pci0 chip2: at device 7.3 on pci0 pci0: unknown card (vendor=0x12eb, dev=0x0002) at 14.0 irq 3 ed0: irq 9 at device 17.0 on pci0 device_probe_and_attach: ed0 attach returned 2 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 12982MB (26588016 sectors), 26377 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (atapi): , removable, accel, dma, iordis wcd0: drive speed 2412 - 6890KB/sec, 512KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA, packet track wcd0: Audio: play, 256 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: CD-ROM 120mm data disc loaded, unlocked wdc1: unit 1 (atapi): , removable, intr, iordis wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio2: not probed (disabled) sio3: not probed (disabled) 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 ppb0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: PRINTER HP ENHANCED PCL5,PJL plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 changing root device to wd0s2a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 10:23:30 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 260AF14D31 for ; Thu, 21 Oct 1999 10:23:25 -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 NAA12122; Thu, 21 Oct 1999 13:26:26 -0400 From: Bill Paul Message-Id: <199910211726.NAA12122@skynet.ctr.columbia.edu> Subject: Re: Intel PRO/1000 Gigabit driver To: jreynold@sedona.ch.intel.com (John Reynolds~) Date: Thu, 21 Oct 1999 13:26:24 -0400 (EDT) Cc: freebsd-current@freebsd.org In-Reply-To: <14351.18373.418811.886740@hip186.ch.intel.com> from "John Reynolds~" at Oct 21, 99 10:05:09 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1476 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, John Reynolds~ had to walk into mine and say: > > A friend just passed this along: > > http://www.newsalert.com/bin/story?StoryId=Coa6pWbKbyte0mtu > > Intel PRO/1000 Gigabit support for Linux. Source code too (non-GPL'ed very > much like a BSD-ish license). Just in case anyone is wondering, I refuse to create BSD drivers based soley on information from Linux drivers. I don't want any damn Linux source: I want the programming manual used to create the driver in the first place. Why? If Intel is willing to release unencumbered Linux source, then they should be willing to release the manual as well. If they're not willing, then I don't want anything to do with them. > I don't have the technicals to understand how hard it would be to port, but > the code is there for those who do! :) You work for Intel yet claim technical ignorance? I dunno man... :) -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 Thu Oct 21 10:25:22 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 017FE14D31 for ; Thu, 21 Oct 1999 10:25:20 -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 KAA10360; Thu, 21 Oct 1999 10:25:05 -0700 Date: Thu, 21 Oct 1999 10:25:07 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Bill Paul Cc: John Reynolds~ , freebsd-current@FreeBSD.ORG Subject: Re: Intel PRO/1000 Gigabit driver In-Reply-To: <199910211726.NAA12122@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 > Of all the gin joints in all the towns in all the world, John Reynolds~ > had to walk into mine and say: > > > > A friend just passed this along: > > > > http://www.newsalert.com/bin/story?StoryId=Coa6pWbKbyte0mtu > > > > Intel PRO/1000 Gigabit support for Linux. Source code too (non-GPL'ed very > > much like a BSD-ish license). > > Just in case anyone is wondering, I refuse to create BSD drivers based > soley on information from Linux drivers. I don't want any damn Linux > source: I want the programming manual used to create the driver in > the first place. Why? If Intel is willing to release unencumbered > Linux source, then they should be willing to release the manual as well. > If they're not willing, then I don't want anything to do with them. Okay, I'll do it then. > > > I don't have the technicals to understand how hard it would be to port, but > > the code is there for those who do! :) > > You work for Intel yet claim technical ignorance? I dunno man... :) Big company. Usual story. Lighten up. > -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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 10:30:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id B0F1214D31 for ; Thu, 21 Oct 1999 10:30:35 -0700 (PDT) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id NAA00827 for ; Thu, 21 Oct 1999 13:29:00 -0400 (EDT) (envelope-from culverk@culverk.student.umd.edu) Date: Thu, 21 Oct 1999 13:28:59 -0400 (EDT) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: latest kernel doesn't compile. Message-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 cvsupped 5 minutes ago, and tried to rebuild my kernel, when this happened: culverk:/usr/src/sys/compile/MYKERNEL# make depend cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -UKERNEL ../../i386/i386/genassym.c In file included from ../../i386/i386/genassym.c:49: ../../sys/socket.h:132: warning: `/*' within comment In file included from ../../i386/i386/genassym.c:49: ../../sys/socket.h:133: syntax error before `interface' ../../sys/socket.h:146: syntax error before `}' *** Error code 1 Any suggestions? Just thought I'd let someone know. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 10:32:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id E3D4014F5E for ; Thu, 21 Oct 1999 10:32:33 -0700 (PDT) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.10 1999/10/20 18:19:05 spurcell Exp $) with ESMTP id KAA21179; Thu, 21 Oct 1999 10:32:22 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.8 1999/04/16 15:25:49 steved Exp steved $) with ESMTP id KAA11744; Thu, 21 Oct 1999 10:32:20 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id NAA24505; Thu, 21 Oct 1999 13:32:34 -0400 (EDT) From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14351.20015.691962.888252@hip186.ch.intel.com> Date: Thu, 21 Oct 1999 10:32:31 -0700 (MST) To: Bill Paul Cc: freebsd-current@freebsd.org Subject: Re: Intel PRO/1000 Gigabit driver In-Reply-To: <199910211726.NAA12122@skynet.ctr.columbia.edu> References: <14351.18373.418811.886740@hip186.ch.intel.com> <199910211726.NAA12122@skynet.ctr.columbia.edu> X-Mailer: VM 6.75 under Emacs 19.34.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Thursday, October 21, Bill Paul wrote: ] > Of all the gin joints in all the towns in all the world, John Reynolds~ > had to walk into mine and say: > > > Just in case anyone is wondering, I refuse to create BSD drivers based > soley on information from Linux drivers. I don't want any damn Linux > source: I want the programming manual used to create the driver in > the first place. Why? If Intel is willing to release unencumbered > Linux source, then they should be willing to release the manual as well. > If they're not willing, then I don't want anything to do with them. hey, I'm just the messenger ... I don't even work in the same division as the network peripherals people much less know who to talk to about it. Yes, I work for the company, but I do not condone the act of keeping all this hardware information "secret" ... after having been screwed on many projects over this very issue, you'd think the "suits" would figure it out, but alas, they don't. > You work for Intel yet claim technical ignorance? I dunno man... :) DOH! In network card drivers, linux kernel code, and gory FreeBSD internals, yes. In ASIC design, VHDL synthesis, and working on old Mustangs, no. ;-) -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds CEG, CCE, Next Generation Flows, HLA | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 10:35:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id 75AA614D31 for ; Thu, 21 Oct 1999 10:35:48 -0700 (PDT) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.10 1999/10/20 18:19:05 spurcell Exp $) with ESMTP id KAA21286 for ; Thu, 21 Oct 1999 10:35:48 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.8 1999/04/16 15:25:49 steved Exp steved $) with ESMTP id KAA12418 for ; Thu, 21 Oct 1999 10:35:46 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id NAA24550; Thu, 21 Oct 1999 13:36:00 -0400 (EDT) From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14351.20223.573568.463190@hip186.ch.intel.com> Date: Thu, 21 Oct 1999 10:35:59 -0700 (MST) To: freebsd-current@freebsd.org Subject: Re: Intel PRO/1000 Gigabit driver In-Reply-To: References: <199910211726.NAA12122@skynet.ctr.columbia.edu> X-Mailer: VM 6.75 under Emacs 19.34.1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Thursday, October 21, Matthew Jacob wrote: ] > > Big company. Usual story. Lighten up. > 'zactly ... we plebes here in the trenches do as much as we can to get the "suits" to support FreeBSD and Linux (they usually opt for the latter based solely on how many articles they read about Linux in the Wall Street Journal that morning) ... it's a tough battle, but things like this are at least some evidence of a positive trend. Just for CYA points, #include -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds CEG, CCE, Next Generation Flows, HLA | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 15:27:14 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 921A514C46 for ; Thu, 21 Oct 1999 15:27:05 -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 SAA11956; Thu, 21 Oct 1999 18:27:03 -0400 (EDT) Date: Thu, 21 Oct 1999 18:27:03 -0400 (EDT) From: "Matthew N. Dodd" To: "Peter S. Housel" Cc: current@FreeBSD.ORG Subject: Re: ed0 problems for PCI In-Reply-To: <199910211720.KAA08545@cx281057-a.irvn1.occa.home.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, 21 Oct 1999, Peter S. Housel wrote: > I've been having problems with -current not recognizing my RealTek > 8029-based PCI Ethernet card. It worked fine in my previous machine > running -current from July, but neither the late September snapshot > that I installed on the new machine nor the cvsup version from about a > week ago can configure the card. The pciconf and dmesg output are > shown below: Can you add debuging output to if_ed_pci.c:ed_pci_attach() so we can find out what is failing? > ed0: irq 9 at device 17.0 on pci0 > device_probe_and_attach: ed0 attach returned 2 The only thing that I can see that returns error 2 (ENOENT) is in the various ed_alloc_foo() calls. I suspect that for some reason the driver isn't able to allocate the IOPORT. Please check to make sure that 'PnP OS' is set to 'No' in your BIOS. Thanks. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 19: 1:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 93A3914EB6 for ; Thu, 21 Oct 1999 19:01:12 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (pm3b-40.cybcon.com [205.147.75.105]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id TAA05351 for ; Thu, 21 Oct 1999 19:01:11 -0700 (PDT) From: william woods Reply-To: wwoods@cybcon.com To: freebsd-current@freebsd.org Subject: snapshots..... Date: Thu, 21 Oct 1999 18:58:37 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99102119011400.00309@freebsd.cybcon.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where is the best place to get -current snapshots from? I am running 4.0-19990915-CURRENT FreeBSD 4.0-19990915-CURRENT #0: Mon Oct 18 19:00:56 PDT 1999 and was wondering to get the latest snaps.... William --BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT 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 Thu Oct 21 19: 8: 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 3C74E14A21 for ; Thu, 21 Oct 1999 19:07:56 -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 KAA19607 for ; Fri, 22 Oct 1999 10:06:11 +0800 (WST) Received: from ariadne.prth.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id KAA17720 for ; Fri, 22 Oct 1999 10:07:51 +0800 (WST) Received: from ariadne.prth.tensor.pgs.com by ariadne.prth.tensor.pgs.com (8.9.1b+Sun/SMI-SVR4) id KAA17094; Fri, 22 Oct 1999 10:07:56 +0800 (WST) Message-Id: <199910220207.KAA17094@ariadne.prth.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Why I hate RealTek ethernet cards Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Oct 1999 10:07:56 +0800 From: Stephen Hocking-Senior Programmer PGS Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After much to-ing & fro-ing ealier this year, I ended up using a Realtek on an otherwise respectable machine. For the most part it seemed alright. Then just before I went on an extended overseas trip 7 weeks ago, it started doing odd things. Small transfers worked OK, but larger ones just trickled through. The effect was immediately observable with tcpblast. Once you sent a number of 1k blocks that was over the tcp_sendspace & tcp_recvspace limits, the transfer rate dropped dramatically. Adjusting the tcp_sendspace etc parameters affected when this would happen. UDP seemed quite happy (thank goodness for that, as otherwise NFS would've gone down the drain) Anyway, there were NetGear cards going cheap, so I replaced the Realtek with that and all is well. 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 Oct 21 19:14:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (Postfix) with ESMTP id 678B714D69 for ; Thu, 21 Oct 1999 19:14:26 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Received: from smarter.than.nu (ida-89-77.Reshall.Berkeley.EDU [169.229.89.77]) by soda.CSUA.Berkeley.EDU (8.8.8/) via ESMTP id TAA26434; Thu, 21 Oct 1999 19:14:22 -0700 (PDT) env-from (brian@CSUA.Berkeley.EDU) Date: Thu, 21 Oct 1999 19:14:22 -0700 (PDT) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: william woods Cc: freebsd-current@FreeBSD.ORG Subject: Re: snapshots..... In-Reply-To: <99102119011400.00309@freebsd.cybcon.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, 21 Oct 1999, william woods wrote: > Where is the best place to get -current snapshots from? I am > running 4.0-19990915-CURRENT FreeBSD 4.0-19990915-CURRENT #0: > Mon Oct 18 19:00:56 PDT 1999 and was wondering to get the latest snaps.... ftp://current.freebsd.org or see "Staying Current with FreeBSD" in the handbook. -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- 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 Oct 21 19:23: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 758B214D69; Thu, 21 Oct 1999 19:22:59 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (william@pm3b-40.cybcon.com [205.147.75.105]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id TAA06662; Thu, 21 Oct 1999 19:22:51 -0700 (PDT) From: william woods Reply-To: wwoods@cybcon.com To: freebsd-current@freebsd.org Subject: Re: snapshots..... Date: Thu, 21 Oct 1999 19:21:28 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: In-Reply-To: Cc: freebsd-alpha@freebsd.org MIME-Version: 1.0 Message-Id: <99102119224101.00309@freebsd.cybcon.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ahh...that is the X86 -current, not the Alpha current...how often are alpha -currents made? On Thu, 21 Oct 1999, you wrote: > current.freebsd.org > > Pull down the file > > ftp://current.freebsd.org/pub/FreeBSD/snapshots/19991012.tar > > (or something similar) > > It is a tar file (created on the fly) and will contain everything you > need for an installation. Drop the files kern.flp and mfsroot.flp in > ./floppies/ on a floppy reboot and choose as the media 'file system' > > Hope this helps. > > Nick > > > On Thu, 21 Oct 1999, william woods wrote: > > > Where is the best place to get -current snapshots from? I am > > running 4.0-19990915-CURRENT FreeBSD 4.0-19990915-CURRENT #0: > > Mon Oct 18 19:00:56 PDT 1999 and was wondering to get the latest snaps.... > > > > William > > > > --BEGIN GEEK CODE BLOCK----- > > Version: 3.1 > > GIT 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 > > > > -- William Woods FreeBSD 3.3-Stable -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT 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 Thu Oct 21 19:56:50 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 ED4F814D06 for ; Thu, 21 Oct 1999 19:56:48 -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 WAA16945; Thu, 21 Oct 1999 22:46:56 -0400 (EDT) Date: Thu, 21 Oct 1999 22:46:55 -0400 (EDT) From: "Matthew N. Dodd" To: "Peter S. Housel" Cc: current@FreeBSD.ORG Subject: Re: ed0 problems for PCI In-Reply-To: <199910211720.KAA08545@cx281057-a.irvn1.occa.home.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, 21 Oct 1999, Peter S. Housel wrote: > I've been having problems with -current not recognizing my RealTek > 8029-based PCI Ethernet card. It worked fine in my previous machine > running -current from July, but neither the late September snapshot > that I installed on the new machine nor the cvsup version from about a > week ago can configure the card. The pciconf and dmesg output are > shown below: Ok, I found a PCI NE2000 board and put it in a scratch box: ed0: irq 14 at device 12.0 on pci0 ed0: address 00:20:78:11:87:8c, type NE2000 (16 bit) I suspect that the card is failing to to allocate an IRQ; if you could add printf()s in the right places we'll know for sure. I think its time to force the PCI newbus code to automatically make IRQs RF_SHAREABLE. I did this with the MCA code since you can't have unshared IRQs on a PS/2 (not on the MCA bus anyways.) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 21 20:33:25 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 27FB614D41 for ; Thu, 21 Oct 1999 20:33:21 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA06328 for ; Fri, 22 Oct 1999 13:03:19 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 22 Oct 1999 13:03:19 +0930 (CST) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Subject: sys/socket.h broken.. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lines 131-134 read -> #define pseudo_AF_HDRCMPLT 31 /* Used by BPF to not rewrite headers #define AF_NETGRAPH 32 /* Netgraph sockets */ * in interface output routine */ Which doesn't work.. They probably should be -> #define pseudo_AF_HDRCMPLT 31 /* Used by BPF to not rewrite headers */ #define AF_NETGRAPH 32 /* Netgraph sockets * in interface output routine */ Err.. also sys/mount.h defined AF_MAX which causes lots of nice warnings. --- 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 Thu Oct 21 20:40:39 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 E2D5414FFE for ; Thu, 21 Oct 1999 20:40:03 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA06413; Fri, 22 Oct 1999 13:09:52 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 22 Oct 1999 13:09:52 +0930 (CST) From: "Daniel O'Connor" To: "Daniel O'Connor" Subject: RE: sys/socket.h broken.. Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm.. well it looks fixed now :) I think I had an old patch which was being screwy. (and wpaul fixed sys/socket.h) --- 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 Thu Oct 21 21:35:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 510BB14F30 for ; Thu, 21 Oct 1999 21:35:46 -0700 (PDT) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id GAA19786; Fri, 22 Oct 1999 06:35:42 +0200 (MET DST) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id GAA06055; Fri, 22 Oct 1999 06:35:41 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <3.0.5.32.19991020143339.016e0210@staff.sentex.ca> References: <3.0.5.32.19991020143339.016e0210@staff.sentex.ca> Date: Thu, 21 Oct 1999 23:33:36 -0400 To: Mike Tancsa , freebsd-current@FreeBSD.ORG From: Brad Knowles Subject: Re: AMRD (MegaRAID) BIOS rev another other questions Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:33 PM -0400 1999/10/20, Mike Tancsa wrote: > I have been playing for now with RAID 0 to get a sense of various > performance settings, which can dramatically effect bonnie and iozone > results. e.g. Write Back vs write through and stripe size. The eventual > purpose will be for a SQUID server in a couple of months once the drivers > are back ported. Have you done any benchmarking with any other tools (e.g., rawio and postmark), as I've gotten started at )? I think it would be very useful to have similar sets of benchmarks run across a wide variety of hardware combinations, so that we'd be closer to being able to compare apples to apples. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 4: 2:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id 57CF014D39 for ; Fri, 22 Oct 1999 04:01:34 -0700 (PDT) (envelope-from steveroo@mothra.bri.hp.com) Received: from mothra.bri.hp.com (steveroo@mothra.bri.hp.com [15.144.1.185]) by atlrel2.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id HAA27732 for ; Fri, 22 Oct 1999 07:00:32 -0400 (EDT) Received: from localhost (steveroo@localhost) by mothra.bri.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id MAA28060; Fri, 22 Oct 1999 12:00:06 +0100 (BST) Date: Fri, 22 Oct 1999 12:00:05 +0100 (BST) From: Stephen Roome To: Ville-Pertti Keinonen Cc: current@freebsd.org Subject: Re: Anyone adding "support" for Athlons. In-Reply-To: <86zoxd19yl.fsf@not.demophon.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 21 Oct 1999, Ville-Pertti Keinonen wrote: > Stephen Roome writes: > > > As the title says, is anyone working on support for Athlons, and when can we > > expect it to arrive back in -stable ? > > Athlons don't need any special support, they are fully compatible with > Intel's latest processors. I realise that special support is not required, but better optimised support would be nice. > > (I can't find anything in the latest versions of sys/i386/i386/identcpu.c) > > The identification for AMD processors models that can report their > name using cpuid is redundant, even for cpus that are currently listed > there. Yup, I noticed this, I was concerned not just that the name came up properly, but that the identification would then cause the chip to be utilised differently. Anyway... To this, and all those that have responded to me with regards to specific Athlon support, I should probably rephrase my question: The issues I was trying to raise were really about better optimization for Athlons, and later generations of CPU's, as follows : 1) Cache size changes are already accounted for in the case of 1Mb or 512k L2 cache, however the Athlon can have up to 8M cache. Although there's no Athlons shipping at the moment with more than 512k cache this will apparently change, and the vm system ought to know about this, perhaps instead of using the PQ_****CACHE definitions we ought to consider having PQ_L1CACHESIZE and PQ_L2CACHESIZE definitions instead. (The currently Athlons have L1/L2 of 128k/512K, also, depending on the bios the clock speeds and ratios for these are different to what can be assumed from a 486 or 386 or even a PIII.) 2) Alignment. By default if code is compiled without -m486 we end up with different alignment strategies taken by gcc. Should the 386 strategy still be the default ? (i.e. Should 386 still be considered the expected hardware for FreeBSD) 3) Use of SIMD instructions, (MMX and 3DNow!). Are these used by anything ? 4) Treating different CPU's differently by the compiler : Addition of scheduling parameters for Pentium and Pentium Pro wasn't added to gcc until 2.8. 3.2-RELEASE is 2.7.2.1 (what's the version in other releases ?) Overall, it looks very much to me like a PII, PIII or Athlon is generally treated as quicker 486, and at worst as a quick 386. Although there's kernel code to say do bzero/copy differently, the general case, it's a quick 386. But MMX and 3DNow! really could be used (better), and CPU architecture has changed a lot. There was a time when people were using pentium optimised gcc for a while, but I still don't see a -mpentium or -mppro, or -arch= option to our version of gcc. If none of this is relevant, then I'd be interested to know why, but it seems pretty relevant to me! Thanks for all the feedback so far, Steve The Athlon code optimization guide can be found here : http://www.amd.com/products/cpg/athlon/techdocs/pdf/22007.pdf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 4:58: 7 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 E2E4C14CB6 for ; Fri, 22 Oct 1999 04:57:52 -0700 (PDT) (envelope-from mike@sentex.net) Received: from ospf-mdt.sentex.net (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id HAA22085; Fri, 22 Oct 1999 07:57:50 -0400 (EDT) From: mike@sentex.net (Mike Tancsa) To: blk@skynet.be (Brad Knowles) Cc: current@freebsd.org Subject: Re: AMRD (MegaRAID) BIOS rev another other questions Date: Fri, 22 Oct 1999 11:57:50 GMT Message-ID: <38104f40.86321443@mail.sentex.net> References: <3.0.5.32.19991020143339.016e0210@staff.sentex.ca> In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22 Oct 1999 00:37:41 -0400, in sentex.lists.freebsd.current you wrote: >At 2:33 PM -0400 1999/10/20, Mike Tancsa wrote: > >> I have been playing for now with RAID 0 to get a sense of various >> performance settings, which can dramatically effect bonnie and iozone >> results. e.g. Write Back vs write through and stripe size. The eventual >> purpose will be for a SQUID server in a couple of months once the drivers >> are back ported. > > Have you done any benchmarking with any other tools (e.g., rawio >and postmark), as I've gotten started at >)? I think it would be >very useful to have similar sets of benchmarks run across a wide >variety of hardware combinations, so that we'd be closer to being >able to compare apples to apples. I went to compile rawio out of the ports, but a declaration needs to be changed and I havent had time to figure it out. (Alas, I am not a programmer) cc -O -pipe -g rawio.c -o rawio rawio.c: In function `dochild': rawio.c:496: incompatible types in initialization *** Error code 1 For now I have mostly been doing tests with bonnie and iozone testing out the various configurations and settings in RAID 0,1,3 and 5. Generally, as expected, the controller only really shows off when there are multiple things going on. e.g. two or more copies of bonnie running at the same time. I also have a Mylex 960 that I will test out next. ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 6: 9:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 9E10514D9B for ; Fri, 22 Oct 1999 06:09:52 -0700 (PDT) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id OAA82446; Fri, 22 Oct 1999 14:09:50 +0100 (BST) (envelope-from geoffb) Date: Fri, 22 Oct 1999 14:09:49 +0100 From: Geoff Buckingham To: Mike Tancsa Cc: freebsd-current@FreeBSD.ORG Subject: Re: AMRD (MegaRAID) BIOS rev another other questions Message-ID: <19991022140949.A82396@chuggalug.clues.com> References: <3.0.5.32.19991020143339.016e0210@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <3.0.5.32.19991020143339.016e0210@staff.sentex.ca>; from Mike Tancsa on Wed, Oct 20, 1999 at 02:33:39PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec > %CPU > 40 16341 99.1 20746 38.3 20307 52.7 14187 100.0 94033 98.2 > 9744.2 99.8 > > v.s. > > Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... > -------Sequential Output-------- ---Sequential Input-- > --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- > --Seeks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec > %CPU > 40 10952 66.9 11622 22.6 9564 30.1 14230 100.0 63604 100.0 > 6944.5 99.8 > The near 100 CPU use during the seek test combined with very high numbers of seeks per second indicated your test data size wasn't large enough and you have the test data entirely cached in RAM, try bonnies -s 1024 (patience required) Also when using UFS on striped disks of any kind beware of interactions between stripe size and cluster size which can concentrate meta-data on half or fewer of your disks. Where sequential read/write performance is not critical you can stripe at cluster size to avoid this. Other wise using an odd number of spindles for a stripe and an even number for a RAID3 or RAID5 or stripeing at an interval which is not a power of two should work (12,24,48,76 etc) The problem arise from UFS's use of cylinder groups that are intended to put inodes on a single disk near the blocks that they reference. (THis is explained far better than I can in section 8.2 of the Design and Implementation of the 4.4BSD operating system) -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 7: 8:22 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 091C115012 for ; Fri, 22 Oct 1999 07:08:15 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id KAA28736; Fri, 22 Oct 1999 10:08:09 -0400 (EDT) Message-Id: <3.0.5.32.19991022100711.01dd8c90@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 22 Oct 1999 10:07:11 -0400 To: Geoff Buckingham From: Mike Tancsa Subject: Re: AMRD (MegaRAID) BIOS rev another other questions Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19991022140949.A82396@chuggalug.clues.com> References: <3.0.5.32.19991020143339.016e0210@staff.sentex.ca> <3.0.5.32.19991020143339.016e0210@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:09 PM 10/22/99 +0100, Geoff Buckingham wrote: >The near 100 CPU use during the seek test combined with very high numbers of Thanks for the pointers. It certainly gives me direction to look in. This is my first foray into RAID, so I am just starting exploring the technology. Also, my first venture into current. I must say I am bit suprised at how... well stable it all is so far. I am almost tempted to put it into the mix as a test proxy server for our customers after I get a little better sense of the various RAID params to tweak. Here are some results using 5 Seagate 1gig 5400 RPM drives (bought at onsale for $25 each BTW! cheap way for me test things out!) RAID 5, Writeback cache, 128K stripe, 16M of cache on the controller, 64M of RAM on the PII 300. First result is the array (R), second (I) is a wdc0: unit 0 (wd0): , LBA, DMA, 32-bit, multi-block-16 Both drives are mounted async, noatime -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU R200 14879 93.8 16137 32.0 2231 5.6 10548 76.9 12749 17.0 107.8 1.8 I200 9759 61.4 9759 18.5 3894 10.1 12328 91.4 12839 17.8 133.3 2.1 R768 14844 93.3 15495 31.1 2029 5.1 10935 79.8 13031 17.5 75.3 1.4 I768 9787 61.9 9915 19.0 4265 10.9 12714 94.5 15604 21.9 73.3 1.3 ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 8: 1:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (Postfix) with SMTP id E86EB150C9; Fri, 22 Oct 1999 08:01:17 -0700 (PDT) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: mobile@freebsd.org, current@freebsd.org Subject: /etc/pccard_ether "improvement" From: "Robert V. Baron" Date: 22 Oct 1999 11:00:31 -0400 Message-ID: Lines: 26 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm going to be using either a wavelanII (wi0) or a 3com (ep0) on my laptop. I'd like to have the rc.conf's specify how to configure each. Then I'd like to have the one that is in the machine to be configured. In the current /etc/ether_pccard there is $pccard_ifconfig which is used as args to ifconfig if $pccard_ifconfig is not NO. But I need a different ifconfig for each device. So I'd like to propose fixing pccard_ether as: --- /etc/pccard_ether.BAK Mon Oct 4 10:38:32 1999 +++ /etc/pccard_ether Mon Oct 4 11:09:18 1999 @@ -35,7 +35,14 @@ else interface=$1 shift - ifconfig $interface $pccard_ifconfig $* + if [ "x$pccard_ifconfig" = "xYES" ] ; then + eval ifconfig_args=\$ifconfig_${interface} + if [ -n "${ifconfig_args}" ] ; then + ifconfig ${interface} ${ifconfig_args} $* + fi + else + ifconfig $interface $pccard_ifconfig $* + fi fi fi This way pccard devices are initialized just like other devices To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 8: 9:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.2.7]) by hub.freebsd.org (Postfix) with ESMTP id 5C6AE15039 for ; Fri, 22 Oct 1999 08:09:30 -0700 (PDT) (envelope-from K.R.A.M.Schreel@wtb.tue.nl) Received: from wop5.wop.wtb.tue.nl [131.155.56.55] by kweetal.tue.nl (8.9.3) id RAA05812 (ESMTP); Fri, 22 Oct 1999 17:09:22 +0200 (MDT) Received: from wtb.tue.nl (wop24.wop.wtb.tue.nl [131.155.56.116]) by wop5.wop.wtb.tue.nl (8.8.8/8.6.9) with ESMTP id PAA11806; Fri, 22 Oct 1999 15:09:21 GMT Message-ID: <38107E21.59FC54D0@wtb.tue.nl> Date: Fri, 22 Oct 1999 17:09:21 +0200 From: Koen Schreel Organization: Eindhoven University of Technology X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: aic driver camified References: <199910201925.PAA10475@lor.watermarkgroup.com> 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 wrote: > > > I cannot compile a kernel. It reports the following errors: > > Did the patch files.diff apply cleanly? It should add one line to each of > the sys/conf/files and sys/i386/conf/files.i386, please make sure they > are there. > The patches did not apply cleanly (maybe I should take a better look at the patch command), but a quick glance at the diff file revealed the two lines to be added. I added them manually, but still the problem exists. Then I took it another step further, and added aic.c and aic.o in the Makefile in the compile directory. This is not how it is supposed to be, I think, but now it compiles. I used the latest files on the site (21 october), and some improvement is noticed, but it still does not work. I only tested the new code under STABLE. When booting with the scanner switched on, it is being recognised and the boot continues, but sane does not recognise it (which it does when the scanner is connected to the on-board controller). When sane is trying to recognise the scanner, a the following line is written in the logs: Oct 22 16:04:39 diabolo /kernel: ccb 0xc0dec800 sense failed 2 A camcontrol rescan times out with the following message: (probe6:aic0:0:6:0): ccb 0xc0df1c00 - timed out I moved then the Philips CD writer (not the greatest of all SCSI devices, but it works) to the aic controller, but then the machine hangs at boot time with a lot of time out messages like: (probe17:aic0:0:2:2): ccb 0xc0dffe00 - timed out (probe17:aic0:0:2:2): ccb 0xc0dffe00 - timed out (probe17:aic0:0:2:3): ccb 0xc0dffe00 - timed out (probe17:aic0:0:2:3): ccb 0xc0dffe00 - timed out ... (probe17:aic0:0:2:7): ccb 0xc0dffe00 - timed out (probe17:aic0:0:2:7): ccb 0xc0dffe00 - timed out Between each set of identical lines the CD recorder reinitializes and there is some time (~15s) between the two identical lines. Hope this helps a bit :-) Koen. -- Dr. K.R.A.M. Schreel | Eindhoven University of Technology | Faculty of Mechanical Engineering Combustion Research | Section Energy Technology | P. O. Box 513 K.R.A.M.Schreel@wtb.tue.nl | 5600 MB Eindhoven, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 8: 9:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.binep.ac.ru (ns.binep.ac.ru [193.233.37.5]) by hub.freebsd.org (Postfix) with ESMTP id 4456915033 for ; Fri, 22 Oct 1999 08:09:20 -0700 (PDT) (envelope-from goshik@binep.ac.ru) Received: from serv2.binep.ac.ru (serv2 [193.233.44.77]) by ns.binep.ac.ru (8.9.2/8.8.8) with SMTP id TAA04863; Fri, 22 Oct 1999 19:05:37 +0400 (MSD) (envelope-from goshik@binep.ac.ru) Reply-To: "Igor B. Bykhalo" From: "Igor B. Bykhalo" To: Cc: "-current@FreeBSD" Subject: Re: 3c509 testers wanted! Date: Fri, 22 Oct 1999 19:07:25 +0300 Message-ID: <01bf1ca7$879d1c80$0000e9c1@serv2.binep.ac.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0913.2206 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0913.2200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: "Matthew N. Dodd" >Subject: 3c509 testers wanted! > >I've rewritten the ISA bus front end code for if_ep and would like to >solicit testers. > >ftp://ftp.jurai.net/users/winter/patches/if_ep.diff > >You'll have to edit sys/i386/isa/isa_compat.h and remove all the >references to epdriver and NEP. > >Right now 'wired' devices aren't supported so use > >device ep0 > >in your config file. > >I'd especially like people with 3c509Bs to put them in PnP mode and try >booting with this patch. > >I'd also like someome with several adapters to stuff a box with them and >try booting. Of interest is the case where a 3c509B in PnP mode is >installed as well as an older non-PnP 3c509. I suspect this combination >will have 'issues' but am not sure. Boot verbosely and mail me the >output, as well as the output of 'pnpinfo' if you're running a 3c509B. Can it be applied to: ns: {1} uname -a FreeBSD ns.binep.ac.ru 3.1-STABLE FreeBSD 3.1-STABLE #0: Wed Sep 29 21:54:10 MSD 1999 goshik@ns.binep.ac.ru :/usr/src/sys/compile/BINEP.ega i386 with (from dmesg) Oct 20 19:36:32 ns /kernel: ep0 at 0x300-0x30f irq 12 on isa Oct 20 19:36:32 ns /kernel: ep0: aui/bnc[*BNC*] address 00:20:af:56:35:ac Oct 20 19:36:32 ns /kernel: ep1 at 0x320-0x32f irq 11 on isa Oct 20 19:36:32 ns /kernel: ep1: aui/bnc[*BNC*] address 00:20:af:8f:76:61 Oct 20 19:36:32 ns /kernel: ep2 at 0x340-0x34f irq 10 on isa Oct 20 19:36:32 ns /kernel: ep2: aui/bnc[*BNC*] address 00:20:af:8f:93:a9 These are Etherlinks III 3C509B ASSY 03-0021-100-REV-B, and they are probably PnP, don't remember... But the machine itself is 486DX2 with VLB m/b, it's definitely not PnP. Runs as internet gateway, web server and IPXrouted (yes...) Or should i upgrade to 3.3? (no-no, not to current, been there 8-)) > >Thanks. > >- -- >| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | >| winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | >| http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | > Regards, Goshik _____________________________________________________ Windows 2001: "Sorry, pal, i just can't do this" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 8:10:26 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 0805B15023 for ; Fri, 22 Oct 1999 08:10:18 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id JAA16956; Fri, 22 Oct 1999 09:57:59 -0500 (CDT) (envelope-from dan) Date: Fri, 22 Oct 1999 09:57:59 -0500 From: Dan Nelson To: Stephen Roome Cc: Ville-Pertti Keinonen , current@FreeBSD.ORG Subject: Re: Anyone adding "support" for Athlons. Message-ID: <19991022095759.A16787@dan.emsphone.com> References: <86zoxd19yl.fsf@not.demophon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from steveroo@mothra.bri.hp.com on Fri, Oct 22, 1999 at 12:00:05PM +0100 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 22), Stephen Roome said: > The issues I was trying to raise were really about better > optimization for Athlons, and later generations of CPU's, as follows Optimization issues should be brought up on the egcs mailinglists, since that is the compiler we use. > 2) Alignment. By default if code is compiled without -m486 we end up > with different alignment strategies taken by gcc. Should the 386 > strategy still be the default ? (i.e. Should 386 still be considered > the expected hardware for FreeBSD) yes. Edit /etc/make.conf and add -march=i586 if you want to compile your machine with pentium-specific code. > 3) Use of SIMD instructions, (MMX and 3DNow!). Are these used by > anything ? Don't the MMX instructions stomp on the floating-point regs? -- 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 Fri Oct 22 8:11: 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 C2107150A9 for ; Fri, 22 Oct 1999 08:10:54 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id JAA16956; Fri, 22 Oct 1999 09:57:59 -0500 (CDT) (envelope-from dan) Date: Fri, 22 Oct 1999 09:57:59 -0500 From: Dan Nelson To: Stephen Roome Cc: Ville-Pertti Keinonen , current@FreeBSD.ORG Subject: Re: Anyone adding "support" for Athlons. Message-ID: <19991022095759.A16787@dan.emsphone.com> References: <86zoxd19yl.fsf@not.demophon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from steveroo@mothra.bri.hp.com on Fri, Oct 22, 1999 at 12:00:05PM +0100 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 22), Stephen Roome said: > The issues I was trying to raise were really about better > optimization for Athlons, and later generations of CPU's, as follows Optimization issues should be brought up on the egcs mailinglists, since that is the compiler we use. > 2) Alignment. By default if code is compiled without -m486 we end up > with different alignment strategies taken by gcc. Should the 386 > strategy still be the default ? (i.e. Should 386 still be considered > the expected hardware for FreeBSD) yes. Edit /etc/make.conf and add -march=i586 if you want to compile your machine with pentium-specific code. > 3) Use of SIMD instructions, (MMX and 3DNow!). Are these used by > anything ? Don't the MMX instructions stomp on the floating-point regs? -- 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 Fri Oct 22 8:32:19 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 71EA415028 for ; Fri, 22 Oct 1999 08:31:51 -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 LAA01020; Fri, 22 Oct 1999 11:31:22 -0400 (EDT) Date: Fri, 22 Oct 1999 11:31:21 -0400 (EDT) From: "Matthew N. Dodd" To: "Igor B. Bykhalo" Cc: "-current@FreeBSD" Subject: Re: 3c509 testers wanted! In-Reply-To: <01bf1ca7$879d1c80$0000e9c1@serv2.binep.ac.ru> Message-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, 22 Oct 1999, Igor B. Bykhalo wrote: > Can it be applied to: > ns: {1} uname -a > FreeBSD ns.binep.ac.ru 3.1-STABLE FreeBSD 3.1-STABLE #0: Wed Sep 29 21:54:10 MSD 1999 > goshik@ns.binep.ac.ru :/usr/src/sys/compile/BINEP.ega i386 Nope. :/ Email me your kernel config file and I'll send you a -current kernel you can boot to test if you like. > with (from dmesg) > > Oct 20 19:36:32 ns /kernel: ep0 at 0x300-0x30f irq 12 on isa > Oct 20 19:36:32 ns /kernel: ep0: aui/bnc[*BNC*] address 00:20:af:56:35:ac > Oct 20 19:36:32 ns /kernel: ep1 at 0x320-0x32f irq 11 on isa > Oct 20 19:36:32 ns /kernel: ep1: aui/bnc[*BNC*] address 00:20:af:8f:76:61 > Oct 20 19:36:32 ns /kernel: ep2 at 0x340-0x34f irq 10 on isa > Oct 20 19:36:32 ns /kernel: ep2: aui/bnc[*BNC*] address 00:20:af:8f:93:a9 > > These are Etherlinks III 3C509B ASSY 03-0021-100-REV-B, > and they are probably PnP, don't remember... Likely they are PnP but not running in PnP mode. > But the machine itself is 486DX2 with VLB m/b, it's definitely > not PnP. Runs as internet gateway, web server and IPXrouted (yes...) That doesn't matter. FreeBSD's PnP code doesn't rely on the BIOS to setup the devices (well, current anyway.) > Or should i upgrade to 3.3? (no-no, not to current, been there 8-)) I just need you to boot a -current kernel and capture the dmesg output if you can; easiest way to do this would be to hook the box in question up to another machine and boot via serial console. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 10: 9:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id CD69314C26 for ; Fri, 22 Oct 1999 10:09:08 -0700 (PDT) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id BEA351DBF; Fri, 22 Oct 1999 19:09:04 +0200 (CEST) Date: Fri, 22 Oct 1999 19:09:04 +0200 From: "Dave J. Boers" To: "Erik H. Bakke" Cc: freebsd-current@freebsd.org Subject: Re: ata - disk "contact" lost.... Message-ID: <19991022190904.A42099@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <19991021112435.A66609@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 21, 1999 at 05:41:40PM +0200, Erik H. Bakke wrote: > Here is the patch as I got it. > I can't give you any guarantees of anything, though, but it should be worth > a try. > If it solves your problem, drop a message on -current and let us know. Thanks for the patch. I applied it, recompiled this morning and for the occasion I copied my /usr/src to my ide disk (it usually resides on my scsi disk) and I did a "make -j 12 buildworld" to put some strain on the disk. I haven't seen the problem again, so I guess this solves the problem. The patch doesn't seem to have any negative side effects on my system. Thanks again, Dave. -- Dave J. Boers djb@relativity.student.utwente.nl I will *NOT* read email sent to Graduate student of Theoretical Physics d.j.boers@student.utwente.nl -> 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 Oct 22 10:40:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 10CC814BD2 for ; Fri, 22 Oct 1999 10:40:16 -0700 (PDT) (envelope-from steveroo@mothra.bri.hp.com) Received: from mothra.bri.hp.com (mothra.bri.hp.com [15.144.1.185]) by palrel1.hp.com (Postfix) with ESMTP id 18F1C1E5; Fri, 22 Oct 1999 10:40:06 -0700 (PDT) Received: from localhost (steveroo@localhost) by mothra.bri.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id SAA02526; Fri, 22 Oct 1999 18:38:52 +0100 (BST) Date: Fri, 22 Oct 1999 18:38:52 +0100 (BST) From: Stephen Roome To: Dan Nelson Cc: Ville-Pertti Keinonen , current@FreeBSD.ORG Subject: Re: Anyone adding "support" for Athlons. In-Reply-To: <19991022095759.A16787@dan.emsphone.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, 22 Oct 1999, Dan Nelson wrote: > In the last episode (Oct 22), Stephen Roome said: > > The issues I was trying to raise were really about better > > optimization for Athlons, and later generations of CPU's, as follows > > Optimization issues should be brought up on the egcs mailinglists, > since that is the compiler we use. I agree, although I'd still be concerned wether extra support needs to be added, for example to : /usr/src/sys/i386/i386/support.s (perhaps some Athlon optimized bzero/bcopy - or is it totally unnecessary ?) > > 2) Alignment. By default if code is compiled without -m486 we end up > > with different alignment strategies taken by gcc. Should the 386 > > strategy still be the default ? (i.e. Should 386 still be considered > > the expected hardware for FreeBSD) > > yes. Edit /etc/make.conf and add -march=i586 if you want to compile > your machine with pentium-specific code. I've not got an up to date version of gcc available at the moment (will get -current over the weekend however and see how things change) > > 3) Use of SIMD instructions, (MMX and 3DNow!). Are these used by > > anything ? > > Don't the MMX instructions stomp on the floating-point regs? Think so. Although gas can use them. (Not sure why we have two version of gas in the source tree though ?) -rw-r--r-- 1 root wheel 43061 Sep 6 1998 /usr/src/contrib/binutils/include/opcode/i386.h -rw-r--r-- 1 root wheel 34662 Mar 29 1998 /usr/src/gnu/usr.bin/as/opcode/i386.h One doesn't define the emms instruction and one does (this is, I believe, an mmx instr), it seems the default version does have this, so I can't figure what the other version is for. On the other hand. How about 3DNow! support ? although I've seen some patches for egcs to give this support on Athlons. (Again, I'll try this over the weekend with -current when I can install it..) But they don't yet seem to be in even the egcs cvs tree. (well they weren't on Wednesday) Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 10:42:40 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 5CB5814BD2 for ; Fri, 22 Oct 1999 10:42:34 -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 NAA13645; Fri, 22 Oct 1999 13:46:28 -0400 From: Bill Paul Message-Id: <199910221746.NAA13645@skynet.ctr.columbia.edu> Subject: Re: Texas Chainsaw Monday To: bp@butya.kz (Boris Popov) Date: Fri, 22 Oct 1999 13:46:27 -0400 (EDT) Cc: current@FreeBSD.ORG In-Reply-To: from "Boris Popov" at Oct 21, 99 08:57:19 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1054 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, Boris Popov had to walk into mine and say: > On Wed, 20 Oct 1999, Bill Paul wrote: > > > install -c -s -o root -g wheel -m 555 mount_nwfs /vol2/release/sbin > > install: mount_nwfs: No such file or directory > > Ok, it seems that I found why mount_nwfs failed to build: I'm use > 'install' instead of ${INSTALL} in the libncp. Unfortunately, this has not fixed the problem: the build report for today (Oct 22) shows the same error. *sigh* -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 Fri Oct 22 13:13:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (Postfix) with SMTP id 1230E14BD3 for ; Fri, 22 Oct 1999 13:13:52 -0700 (PDT) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: freebsd-current@freebsd.org Subject: sysinstall tweak From: "Robert V. Baron" Date: 22 Oct 1999 16:13:22 -0400 In-Reply-To: "John W. DeBoskey"'s message of "Fri, 10 Sep 1999 15:01:18 -0400 (EDT)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Suppose I need to install on a bunch of machines. What I'd do, is install once, get all the pieces/ports/customizations right and then make a tarball of the system. To install the next machine, I'd use sysinstall to partition and label the new machine and then just nfs mount the machine with the tarball, unroll it and just fix rc.conf as necessary. But when you go this way, there are no commands available available at the holographic shell. Could this be fixed by letting the commands be linked/copied into the chroot env? (As a workaround I just put a good copy of tar with the tarball in nfs, and used that tar.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 13:23:19 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 3F33C14BD3 for ; Fri, 22 Oct 1999 13:23:12 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id QAA22178 for ; Fri, 22 Oct 1999 16:23:11 -0400 (EDT) Message-Id: <3.0.5.32.19991022162211.01d2c930@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 22 Oct 1999 16:22:11 -0400 To: freebsd-current@freebsd.org From: Mike Tancsa Subject: Mylex 960 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 just started to play with the Mylex Controler and I get "attempt to write beyond end of drive" When trying to write to the drive. mlx0: irq 15 at device 10.0 on pci0 mlx0: Mylex DAC960P/PD, 1 channel, firmware 3.51, 4MB RAM mlxd0: on mlx0 mlxd0: 4040MB (8273920 sectors), RAID 5 (online) I did the following to prep it dd if=/dev/zero of=/dev/rmlxd0 bs=1k count=1 disklabel -Brw mlxd0 auto newfs /dev/rmlxd0e Oct 22 15:57:28 slag2a /kernel: t to write beyond end of drive Oct 22 15:57:28 slag2a /kernel: mlx0: I/O error - attempt to write beyond end of drive Oct 22 15:57:57 slag2a last message repeated 529 times Oct 22 15:57:59 slag2a /kernel: t to write beyond end of drive Oct 22 15:57:59 slag2a /kernel: mlx0: I/O error - attempt to write beyond end of drive FreeBSD 4.0-CURRENT #0: Thu Oct 21 09:37:02 EDT 1999 The array consists of 5 segate drives that were working fine with the MegaRAID controller. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 13:29: 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 E640814BD3 for ; Fri, 22 Oct 1999 13:28:46 -0700 (PDT) (envelope-from camel@avias.com) Received: from 192.168.2.2 (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.3) with ESMTP id AAA26744 for ; Sat, 23 Oct 1999 00:28:43 +0400 (MSD) (envelope-from camel@avias.com) Date: Sat, 23 Oct 1999 00:25:05 +0400 From: Ilya Naumov X-Mailer: The Bat! (v1.36) UNREG / CD5BF9353B3B7091 Reply-To: Ilya Naumov X-Priority: 3 (Normal) Message-ID: <1317.991023@avias.com> To: current@FreeBSD.ORG Subject: proftpd problem 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, recently i've got the following problem with proftpd. this daemon (pre8) worked ok until one of recent "make world"s. after that it started to deny any non-anonymous logins with the following diags: Oct 23 00:18:11 camel proftpd[76540]: PAM(camel): Authentication failure Oct 23 00:18:11 camel proftpd[76540]: USER camel: incorrect password from 192.168.2.2 [192.168.2.2] to xxx.xxx.xxx.xxx:21 Oct 23 00:18:00 camel proftpd[76540]: FTP session closed. entries in pam.conf related to ftp are correct and proftpd.conf is ok too (i guess :). so, is it a problem connected to changes in PAM or anything else? thank you. 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 Fri Oct 22 13:36:26 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 E7C3C14C89 for ; Fri, 22 Oct 1999 13:36:23 -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 NAA00680; Fri, 22 Oct 1999 13:16:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910222016.NAA00680@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Stephen Roome Cc: Ville-Pertti Keinonen , current@freebsd.org Subject: Re: Anyone adding "support" for Athlons. In-reply-to: Your message of "Fri, 22 Oct 1999 12:00:05 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Oct 1999 13:16:55 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG *sigh* > > Athlons don't need any special support, they are fully compatible with > > Intel's latest processors. > > I realise that special support is not required, but better optimised support > would be nice. You are, as always, welcome to contribute. > > > (I can't find anything in the latest versions of sys/i386/i386/identcpu.c) > > > > The identification for AMD processors models that can report their > > name using cpuid is redundant, even for cpus that are currently listed > > there. > > Yup, I noticed this, I was concerned not just that the name came up properly, > but that the identification would then cause the chip to be utilised > differently. CPU features are keyed off the CPUs feature codes, not surprisingly, not it's marketing name. > Anyway... > > To this, and all those that have responded to me with regards to specific > Athlon support, I should probably rephrase my question: > > The issues I was trying to raise were really about better optimization for > Athlons, and later generations of CPU's, as follows : > > 1) Cache size changes are already accounted for in the case of 1Mb or 512k L2 > cache, however the Athlon can have up to 8M cache. > > Although there's no Athlons shipping at the moment with more than 512k cache > this will apparently change, and the vm system ought to know about this, > perhaps instead of using the PQ_****CACHE definitions we ought to consider > having PQ_L1CACHESIZE and PQ_L2CACHESIZE definitions instead. (The currently > Athlons have L1/L2 of 128k/512K, also, depending on the bios the clock speeds > and ratios for these are different to what can be assumed from a 486 or 386 or > even a PIII.) Page colouring has been shown to have little or no real effect; again, if you care, feel free to fix the code and submit same. > 2) Alignment. By default if code is compiled without -m486 we end up with > different alignment strategies taken by gcc. Should the 386 strategy still be > the default ? (i.e. Should 386 still be considered the expected hardware for > FreeBSD) Please read preceeding threads on this topic. > 3) Use of SIMD instructions, (MMX and 3DNow!). Are these used by anything ? Shouldn't you be answering this question yourself before demanding support? Do you even think that the kernel needs to be involved with "Multi Media eXtensions" or 3D graphics primitives? > 4) Treating different CPU's differently by the compiler : Addition of > scheduling parameters for Pentium and Pentium Pro wasn't added to gcc until > 2.8. 3.2-RELEASE is 2.7.2.1 (what's the version in other releases ?) Perhaps you should be talking to the egcs folks about this, since as you well know they're the ones responsible for this sort of work. > Overall, it looks very much to me like a PII, PIII or Athlon is generally > treated as quicker 486, and at worst as a quick 386. Although there's kernel > code to say do bzero/copy differently, the general case, it's a quick 386. Surprise, surprise. > But MMX and 3DNow! really could be used (better), It could? You could justify this claim better too. > and CPU architecture has > changed a lot. There was a time when people were using pentium optimised gcc > for a while, but I still don't see a -mpentium or -mppro, or -arch= option to > our version of gcc. And you think that there's no reason at all for this? > If none of this is relevant, then I'd be interested to know why, but it seems > pretty relevant to me! You could try reading the many preceeding threads on this topic already. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 13:57:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id 5B70B14CC0 for ; Fri, 22 Oct 1999 13:57:39 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id WAA11432 for ; Fri, 22 Oct 1999 22:57:36 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id WAA22248 for current@freebsd.org; Fri, 22 Oct 1999 22:57:36 +0200 (MET DST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id WAA01011 for ; Fri, 22 Oct 1999 22:57:35 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Fri, 22 Oct 1999 22:57:35 +0200 (CEST) From: Michael Reifenberger To: FreeBSD-Current Subject: -current pccard/ep0 & apm after some suspends Message-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, my current attaches during boot on my Tecra8000 NB as: 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: Tue Oct 19 23:20:40 CEST 1999 root@nihil.plaut.de:/usr/src/sys/compile/nihil ... config> irq pcic0 11 ... pcic2: at device 11.0 on pci0 pcic3: at device 11.1 on pci0 ... pcic0: at irq 13 on isa0 pccard0: on pcic0 pccard1: on pcic0 pccard: initalizing drivers: ep ... pccard: card inserted, slot 0 pccard: card inserted, slot 1 ... pccard-ep0: at port 0x240-0x24f irq 10 slot 0 on pccard0 ep0: utp/bnc[*UTP*] address 00:60:97:88:84:9e ... Besides that I get irq13 (I wanted a shared irq11) it all works. Now after the first resume I get: ... ep0: unload stray irq 10 pccard: card disabled, slot 0 pccard: card disabled, slot 1 resumed from suspended mode (slept 12:11:22) ata0: resetting devices .. done ata1: resetting devices .. done pccard: card inserted, slot 0 pccard: card inserted, slot 1 devclass_alloc_unit: pccard-ep0 already exists, using next available unit number pccard-ep1: at port 0x240-0x24f irq 10 slot 0 on pccard0 ep0: utp/bnc[*UTP*] address 00:60:97:88:84:9e ... And still ep0 works as expected. After the next suspend/resume ep0 does not attach anymore and I have to reboot to play the game from the beginning. Does anyone else see this? Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 13:57:58 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 4804F15057 for ; Fri, 22 Oct 1999 13:57: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 NAA00912; Fri, 22 Oct 1999 13:49:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910222049.NAA00912@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Tancsa Cc: freebsd-current@freebsd.org Subject: Re: Mylex 960 In-reply-to: Your message of "Fri, 22 Oct 1999 16:22:11 EDT." <3.0.5.32.19991022162211.01d2c930@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Oct 1999 13:49:18 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have just started to play with the Mylex Controler and I get > > "attempt to write beyond end of drive" > > When trying to write to the drive. This is the bug that Chris Csanady just uncovered; I've committed his patches, they should show up shortly. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 16: 9:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp5.mindspring.com (smtp5.mindspring.com [207.69.200.82]) by hub.freebsd.org (Postfix) with ESMTP id A7A3E14CB6 for ; Fri, 22 Oct 1999 16:09:52 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa17-24.ix.netcom.com [207.93.156.24]) by smtp5.mindspring.com (8.8.5/8.8.5) with ESMTP id TAA02983 for ; Fri, 22 Oct 1999 19:09:49 -0400 (EDT) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id QAA77047; Fri, 22 Oct 1999 16:09:44 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Fri, 22 Oct 1999 16:09:44 -0700 (PDT) Message-Id: <199910222309.QAA77047@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: Profiling Problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running SMP 4.0-current as of Oct 18. I attempted to profile an application, using 'gcc -pg ...'. Compiling/linking worked OK. When I attempt to run the application, it reports a stack overflow. gschem and libgeda.so.5 were built with 'gcc -pg ...'. # gschem ERROR: Stack overflow When I do this with a smaller application, it works OK. What can I do to remedy this situation? tomdean # limits -B Resource limits (current): cputime infinity secs filesize infinity kb datasize 524288 kb stacksize 65536 kb <== kernel max? coredumpsize infinity kb memoryuse infinity kb memorylocked infinity kb maxprocesses 819 openfiles 1640 sbsize infinity bytes # ldd gschem gschem: libguile.so.4 => /usr/local/lib/libguile.so.4 (0x280d7000) libreadline.so.4 => /usr/lib/libreadline.so.4 (0x28136000) libncurses.so.5 => /usr/lib/libncurses.so.5 (0x2817d000) libm.so.2 => /usr/lib/libm.so.2 (0x281bb000) libgeda.so.5 => /usr/home/tomdean/cad/gEDA/lib/libgeda.so.5(0x281d7000) libgtk12.so.1 => /usr/X11R6/lib/libgtk12.so.1 (0x281fe000) libgdk12.so.1 => /usr/X11R6/lib/libgdk12.so.1 (0x2830d000) libgmodule12.so.1 => /usr/local/lib/libgmodule12.so.1 (0x2833d000) libglib12.so.1 => /usr/local/lib/libglib12.so.1 (0x28340000) libintl.so.1 => /usr/local/lib/libintl.so.1 (0x28360000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x28364000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x2836e000) libc.so.4 => /usr/lib/libc.so.4 (0x28404000) libc.so.3 => /usr/lib/libc.so.3 (0x28489000) I don't understand why the two libc entries. libc.so is linked to libc.so.4. None of the Makefiles calls for libc.so.3, only libc.so. # gcc --version egcs-2.91.66 # gmake --version GNU Make version 3.77, by Richard Stallman and Roland McGrath. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 17:10: 8 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 4213214C97; Fri, 22 Oct 1999 17:09:50 -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 RAA12035; Fri, 22 Oct 1999 17:09:26 -0700 (PDT) (envelope-from mantar@pacbell.net) Message-Id: <4.2.1.10.19991022170330.00a9a3f0@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1.10 (Beta) Date: Fri, 22 Oct 1999 17:09:25 -0700 To: Ilya Naumov , current@FreeBSD.ORG, ports@FreeBSD.ORG From: Manfred Antar Subject: Re: proftpd problem In-Reply-To: <1317.991023@avias.com> 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 12:25 AM 10/23/99 +0400, Ilya Naumov wrote: >Hello, > >recently i've got the following problem with proftpd. > >this daemon (pre8) worked ok until one of recent "make world"s. after >that it started to deny any non-anonymous logins with the following >diags: > >Oct 23 00:18:11 camel proftpd[76540]: PAM(camel): Authentication failure >Oct 23 00:18:11 camel proftpd[76540]: USER camel: incorrect password >from 192.168.2.2 [192.168.2.2] to xxx.xxx.xxx.xxx:21 >Oct 23 00:18:00 camel proftpd[76540]: FTP session closed. > >entries in pam.conf related to ftp are correct and proftpd.conf is >ok too (i guess :). > >so, is it a problem connected to changes in PAM or anything else? >thank you. > I had the same problem and hacked at it for few hours. the only way I could get it to work was to put PersistentPasswd On in the /usr/local/etc/proftpd.conf file. It stopped working about last weekend. With the above line added it works fine. 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 Fri Oct 22 19:41:18 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 3D60014F64; Fri, 22 Oct 1999 19:41:13 -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 UAA21589; Fri, 22 Oct 1999 20:41:11 -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 UAA26689; Fri, 22 Oct 1999 20:41:26 -0600 (MDT) Message-Id: <199910230241.UAA26689@harmony.village.org> To: current@freebsd.org, mobile@freebsd.org Subject: sio working Date: Fri, 22 Oct 1999 20:41:26 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK. I managed to get sio and ep working on the plane back from FreeBSDCon'99. There are some problems with card eject at the moment, but will be committing things to the tree shortly. Basically, I completely gutted the compatibilty layer and it became much easier. More later after I've had a chance to spend time with my wife and unwind from the drive back. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 20:52:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 1609614D28 for ; Fri, 22 Oct 1999 20:52:16 -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 UAA00815 for ; Fri, 22 Oct 1999 20:52:11 -0700 (PDT) Date: Fri, 22 Oct 1999 20:52:10 -0700 (PDT) From: Dennis Glatting To: freebsd-current@freebsd.org Subject: Need help with vinum (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having a problem with vinum. Clue for the clue-less would be appreciated. My config file: drive a device /dev/da3 drive b device /dev/da4 volume vol1 plex org striped 16k sd length 2777m drive a sd length 2777m drive b When I create a config within vinum I get: vinum -> create -f drv 1: drive a device /dev/da3 ** 1 Drive a has invalid partition type: Inappropriate file type or format 2: drive b device /dev/da4 ** 2 Drive b has invalid partition type: Inappropriate file type or format Configuration summary Drives: 0 (4 configured) Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 2 (16 configured) D a State: referenced Device /dev/da3 Avail: 0/0 MB D b State: referenced Device /dev/da4 Avail: 0/0 MB V vol1 State: down Plexes: 1 Size: 5554 MB P vol1.p0 S State: faulty Subdisks: 2 Size: 5554 MB S vol1.p0.s0 State: crashed PO: 0 B Size: 2777 MB S vol1.p0.s1 State: crashed PO: 16 kB Size: 2777 MB I have tried variations of the disk drive, such as da3h, sd3, etc. Previously these disks were mounted as UFS volumes. Specifically: #/dev/da3s1 /ExternalDisk4 ufs rw 2 2 #/dev/da4s1 /ExternalDisk3 ufs rw 2 2 Here's what dmesg contains after reboot (it crashes if I do an init): 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.3-STABLE #23: Sat Sep 25 08:27:04 PDT 1999 root@btw:/ExternalDisk/FreeBSD-btw-3.x/src/sys/compile/BTW Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 333347147 Hz CPU: Pentium II/Xeon/Celeron (333.35-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping = 0 Features=0x183f9ff real memory = 402653184 (393216K bytes) avail memory = 388628480 (379520K bytes) Preloaded elf kernel "kernel" at 0xc02fa000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x01 on pci0.7.3 xl0: <3Com 3c905-TX Fast Etherlink XL> rev 0x00 int a irq 10 on pci0.13.0 xl0: Ethernet address: 00:60:08:b0:3d:a6 xl0: autoneg complete, link status good (half-duplex, 10Mbps) xl1: <3Com 3c905B-TX Fast Etherlink XL> rev 0x64 int a irq 9 on pci0.14.0 xl1: Ethernet address: 00:50:04:d2:9f:c6 xl1: autoneg complete, link status good (half-duplex, 10Mbps) ahc0: rev 0x00 int a irq 3 on pci0.15.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 11 on pci0.16.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on PCI bus 1: vga0: rev 0x21 int a irq 9 on pci1.0.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model IntelliMouse, device ID 3 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis wst0: Drive empty, readonly, reverse, qfa, ecc, 512b wst0: Max speed=600Kb/s, Transfer limit=52 blocks, Buffer size=728 blocks ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 256 packets/entry by default IP Filter: initialized. Default = pass all, Logging = enabled Waiting 15 seconds for SCSI devices to settle sa0 at ahc1 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-CCS device sa0: 3.300MB/s transfers da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8759MB (17938986 512 byte sectors: 255H 63S/T 1116C) da2 at ahc0 bus 0 target 12 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8669MB (17755614 512 byte sectors: 255H 63S/T 1105C) cd0 at ahc1 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: cd present [295082 x 2048 byte records] changing root device to da0s1a da4 at ahc1 bus 0 target 2 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da4: 2777MB (5688447 512 byte sectors: 255H 63S/T 354C) da3 at ahc1 bus 0 target 1 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da3: 2777MB (5688447 512 byte sectors: 255H 63S/T 354C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: 4095MB (8388314 512 byte sectors: 255H 63S/T 522C) WARNING: / was not properly dismounted vinum: loaded vinum: no drives found xl0: promiscuous mode enabled vinum: vol1.p0.s0 is crashed vinum: vol1.p0 is faulty vinum: vol1.p0.s1 is crashed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 21:15: 7 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 204A214D28 for ; Fri, 22 Oct 1999 21:15:01 -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.3/8.9.1) with ESMTP id VAA36854 for ; Fri, 22 Oct 1999 21:09:50 -0700 (PDT) Date: Fri, 22 Oct 1999 21:09:50 -0700 (PDT) From: Annelise Anderson To: freebsd-current@freebsd.org Subject: aic driver (thanks!) and cdrom Message-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 very much for this driver, Luoqi. I am using it in a -current built from October 14 sources, with a new kernel of course. The cdrom produces the following, though: Oct 22 14:14:35 two /kernel: Waiting 15 seconds for SCSI devices to settle Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:2): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:2): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:3): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:3): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:4): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:4): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:5): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: (probe2:aic0:0:2:5): ccb 0xc0c90c00 - timed out Oct 22 14:14:35 two /kernel: Creating DISK da0 Oct 22 14:14:35 two /kernel: Creating DISK da1 Oct 22 14:14:35 two /kernel: Creating DISK cd0 Oct 22 14:14:35 two /kernel: changing root device to da1s2a Oct 22 14:14:35 two /kernel: da0 at aic0 bus 0 target 0 lun 0 Oct 22 14:14:35 two /kernel: da0: Fixed Direct Access SCSI-2 device Oct 22 14:14:35 two /kernel: da0: 5.000MB/s transfers (5.000MHz, offset 8) Oct 22 14:14:35 two /kernel: da0: 4345MB (8899737 512 byte sectors: 64H 32S/T 4345C) Oct 22 14:14:35 two /kernel: da1 at aic0 bus 0 target 1 lun 0 Oct 22 14:14:35 two /kernel: da1: Fixed Direct Access SCSI-2 device Oct 22 14:14:35 two /kernel: da1: 5.000MB/s transfers (5.000MHz, offset 8) Oct 22 14:14:35 two /kernel: da1: 2069MB (4238640 512 byte sectors: 64H 32S/T 2069C) Oct 22 14:14:35 two /kernel: (cd0:aic0:0:2:0): got CAM status 0x20c Oct 22 14:14:35 two /kernel: (cd0:aic0:0:2:0): fatal error, failed to attach to device Oct 22 14:14:35 two /kernel: (cd0:aic0:0:2:0): lost device Oct 22 14:14:35 two /kernel: (cd0:aic0:0:2:0): removing device entry Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 22 23:44:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DCA2414C21; Fri, 22 Oct 1999 23:44:20 -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 AAA22001; Sat, 23 Oct 1999 00: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 AAA27296; Sat, 23 Oct 1999 00:44:23 -0600 (MDT) Message-Id: <199910230644.AAA27296@harmony.village.org> To: mobile@freebsd.org, current@freebsd.org, committers@freebsd.org Reply-To: mobile@freebsd.org Subject: Massive pccard disruptions to continue Date: Sat, 23 Oct 1999 00:44:23 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK. I'm getting ready to commit the sio modem changes to make it work with pccard. This is a heads up that how ep is configured has changed to be more sane for pccard, and also that things may be massively unstable for a few days. That's the nature of current. I have a couple of minor issues to take care of before I actually do the commit. To summarize the changes, I killed the legacy PCCARD_MODULE macro and all things associated with it. It is not longer emulated, even in the slightest. Everything is done via newbus. This kills lots and lots lines and makes it possible for newbus attachments, and only newbus attachments. Also, pccardd no longer sets the unit number, so the unit numbers have changed. The ep driver is hit by this since it checks against NEP (this should be fixed, btw) in places. This breaks all PCCARD drivers, except those that have been converted. I've converted ep and sio. Ed will follow by me or someone else very shortly. I've also heard that people are interested in getting the pccard support for floppy as well. Look at sio or ep for a cut and paste model of how to do things. Neither is perfect, but can be used if you absolutely MUST upgrade the driver before the new pccard code can be committed, ported and stabilized. If you are dying to try out the sio patches before they make it into the tree, one can grab a snapshot I just made from http://www.freebsd.org/~imp/pccard-snap.patch [**] which contain many known problems that I'm working on correcting. I have some debug writes I need to remove, one minor issue with the message ep0: eeprom failed to come ready issued twice, but it seems to work none the less. Cards cannot be ejected for reasons unknown at this time. DO NOT RUN THESE PATCHES UNLESS YOU HAVE A BACKUP KERNEL IN CASE I'VE BROKEN YOUR LAPTOP. READ THE PATCH FOR MINOR, BUT IMPORTANT CHANGES TO HOW EP IS CONFIGURED. Many thanks to Doug Rabson and Peter Wemm for their help, patient explainations and goading while at FreeBSD Con '99. Without this, I wouldn't have been able to make this work. Thanks also to Peter for the patches that helped me understand sio's problem better and allowed me to make this work. I appologize to them that I was unable to get them done at FreeBSD CON'99. Comments to me... Warner P.S. I wish I could add pictures of the happy dance I did after seeing the many pictures of this on the FreeBSD CON pictures web site... [*] Unless absolutely necessary... [**] Keep trying if this file isn't there... I'm generating it now as I type. I'm generating them from my laptop connected via the ep driver... They may also contain other things as well, but should be fairly clean: wc pccard-snap.patch 3389 12760 91407 pccard-snap.patch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 0:19:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 46CBF14FB9 for ; Sat, 23 Oct 1999 00:19:10 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id JAA05739; Sat, 23 Oct 1999 09:12:29 +0200 (MET DST) Received: (from ticso@localhost) by mail.cicely.de (8.9.0/8.9.0) id JAA07651; Sat, 23 Oct 1999 09:18:41 +0200 (CEST) Date: Sat, 23 Oct 1999 09:18:41 +0200 From: Bernd Walter To: Dennis Glatting Cc: freebsd-current@FreeBSD.ORG Subject: Re: Need help with vinum (fwd) Message-ID: <19991023091840.A7601@cicely7.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Dennis Glatting on Fri, Oct 22, 1999 at 08:52:10PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 22, 1999 at 08:52:10PM -0700, Dennis Glatting wrote: > > drive a device /dev/da3 > drive b device /dev/da4 You need to label the drive first and use such as da3e in vinum. The Handbook tells you how to do. > vinum -> create -f drv > 1: drive a device /dev/da3 > ** 1 Drive a has invalid partition type: Inappropriate file type or The label need to say vinum not 4.2BSD as for normal partitions. > vinum: loaded > vinum: no drives found > xl0: promiscuous mode enabled > vinum: vol1.p0.s0 is crashed > vinum: vol1.p0 is faulty > vinum: vol1.p0.s1 is crashed > This might be a result of the above. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 8:54:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id 8838114BC2 for ; Sat, 23 Oct 1999 08:54:41 -0700 (PDT) (envelope-from bleez@netaxs.com) Received: from dyn-3.blackbox-2.netaxs.com (dyn-3.blackbox-2.netaxs.com [207.106.60.3]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id LAA23018 for ; Sat, 23 Oct 1999 11:54:38 -0400 (EDT) Date: Sat, 23 Oct 1999 11:54:37 -0400 (EDT) From: Bryan Liesner To: freebsd-current@freebsd.org Subject: ata driver and mounting CDROMs, missing tape drives Message-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 having trouble mounting my ATAPI CDROM using the new ATA drivers When I do a: %mount /cdrom, the system complains: cd9660: Block device required This is my fstab entry: /dev/acd0a /cdrom cd9660 ro,noauto 0 0 And here is the relevant part of my kernel config: controller ata0 device atadisk0 device atapicd0 device atapist0 And here are my /dev entries: brw-r----- 1 root operator 19, 0 Oct 22 01:34 /dev/acd0a brw-r----- 1 root operator 19, 2 Oct 22 01:34 /dev/acd0c brw-r----- 1 root operator 19, 8 Oct 22 01:34 /dev/acd1a brw-r----- 1 root operator 19, 10 Oct 22 01:34 /dev/acd1c They look like block devices to me! I have the CDROM configured as master, and a HP Travan 8G tape drive as slave. The dmesg shows only the CDROM, and the kernel doesn't see the tape drive at all, although the dmesg says there are two devices on the channel. Here is the last 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: Fri Oct 22 00:01:27 EDT 1999 bryan@gravy.kishka.net:/usr/src/sys/compile/GRAVY Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 249414302 Hz CPU: Cyrix 6x86MX (249.41-MHz 686-class CPU) Origin = "CyrixInstead" Id = 0x601 Stepping = 1 DIR=0x1353 Features=0x80a135 real memory = 134217728 (131072K bytes) avail memory = 127672320 (124680K bytes) Preloaded elf kernel "kernel" at 0xc0274000. Preloaded elf module "linux.ko" at 0xc027409c. Preloaded elf module "warp_saver.ko" at 0xc027413c. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 2.0 on pci0 isa0: on isab0 ata-pci0: irq 11 at device 5.0 on pci0 ata-pci0: Busmastering DMA supported ata2 at 0xeff0 irq 11 on ata-pci0 vga-pci0: irq 0 at device 6.0 on pci0 ata-pci1: irq 0 at device 11.0 on pci0 ata-pci1: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci1 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 pcm0: at irq 5 drq 1 flags 0x15 on isa0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 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: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio2: at port 0x3e8-0x3ef irq 10 on isa0 sio2: type 16550A ad0: ATA-4 disk at ata2 as master ad0: 8693MB (17803440 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 31 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 ad1: ATA-? disk at ata2 as slave ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue, DMA Creating DISK ad1 Creating DISK wd1 ata0: Aladdin: two atapi devices on this channel, DMA disabled atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: CDROM drive at ata0 as master acd0: read 2062KB/s (6875KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked changing root device to wd0s1a WARNING: driver snd should register devices with make_dev() (dev_t = "#snd/4") To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 9:15:33 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 E5B6D14BF9 for ; Sat, 23 Oct 1999 09:15:24 -0700 (PDT) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id MAA07525; Sat, 23 Oct 1999 12:44:10 -0400 (EDT) (envelope-from dervish) Date: Sat, 23 Oct 1999 12:44:10 -0400 From: Bush Doctor To: freebsd-current@FreeBSD.ORG Cc: bleez@netaxs.com Subject: Re: ata driver and mounting CDROMs, missing tape drives Message-ID: <19991023124410.A7388@ikhala.tcimet.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Bryan Liesner on Sat, Oct 23, 1999 at 11:54:37AM -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 Bryan Liesner (bleez@netaxs.com): > I've been having trouble mounting my ATAPI CDROM using the new ATA drivers > When I do a: > > %mount /cdrom, the system complains: %mount_cd9660 /cdrom or %mount -t cd9660 /cdrom #:^) -- bush doctor 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 Sat Oct 23 9:16:25 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 5765B14F08; Sat, 23 Oct 1999 09:16:10 -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 MAA29350; Sat, 23 Oct 1999 12:16:09 -0400 (EDT) Date: Sat, 23 Oct 1999 12:16:09 -0400 (EDT) From: "Matthew N. Dodd" To: mobile@FreeBSD.ORG Cc: current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: Massive pccard disruptions to continue In-Reply-To: <199910230644.AAA27296@harmony.village.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, 23 Oct 1999, Warner Losh wrote: > To summarize the changes, I killed the legacy PCCARD_MODULE macro and > all things associated with it. It is not longer emulated, even in the > slightest. Everything is done via newbus. This kills lots and lots > lines and makes it possible for newbus attachments, and only newbus > attachments. Also, pccardd no longer sets the unit number, so the > unit numbers have changed. The ep driver is hit by this since it > checks against NEP (this should be fixed, btw) in places. Send your changes to me. I've been rewriting if_ep. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 9:47:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 100AB14C25 for ; Sat, 23 Oct 1999 09:47:04 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.3/8.9.3) with ESMTP id MAA32796; Sat, 23 Oct 1999 12:46:55 -0400 (EDT) Date: Sat, 23 Oct 1999 12:46:55 -0400 (EDT) From: jack To: Bryan Liesner Cc: freebsd-current@FreeBSD.ORG Subject: Re: ata driver and mounting CDROMs, missing tape drives 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 Today Bryan Liesner wrote: > I've been having trouble mounting my ATAPI CDROM using the new ATA drivers > And here are my /dev entries: > > brw-r----- 1 root operator 19, 0 Oct 22 01:34 /dev/acd0a > brw-r----- 1 root operator 19, 2 Oct 22 01:34 /dev/acd0c > brw-r----- 1 root operator 19, 8 Oct 22 01:34 /dev/acd1a > brw-r----- 1 root operator 19, 10 Oct 22 01:34 /dev/acd1c > > They look like block devices to me! They sure are but the major number has changed, it should be 31. Make sure you've got an up to date MAKEDEV and remake the devices. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 10: 4:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 301D014C25 for ; Sat, 23 Oct 1999 10:04:43 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA72518 for ; Sat, 23 Oct 1999 10:04:39 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: Are we going to fix -current's ed driver anytime soon? Date: Sat, 23 Oct 1999 10:04:39 -0700 Message-ID: <72514.940698279@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From current.freebsd.org's release build log: linking BOOTMFS if_ed_isa.o: In function `ed_isa_probe': if_ed_isa.o(.text+0x45): undefined reference to `ed_probe_WD80x3' if_ed_isa.o(.text+0x54): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x5a): undefined reference to `ed_probe_3Com' if_ed_isa.o(.text+0x69): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x6f): undefined reference to `ed_probe_Novell' if_ed_isa.o(.text+0x7e): undefined reference to `ed_release_resources' It's time to either fix this or back out the changes which broke it. If nobody finds the time to do the former in the next 48 hours, I'll do the latter myself. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 10:16: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 A71F814C35 for ; Sat, 23 Oct 1999 10:16:32 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA72600; Sat, 23 Oct 1999 10:16:13 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Robert V. Baron" Cc: freebsd-current@FreeBSD.ORG Subject: Re: sysinstall tweak In-reply-to: Your message of "22 Oct 1999 16:13:22 EDT." Date: Sat, 23 Oct 1999 10:16:13 -0700 Message-ID: <72597.940698973@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Suppose I need to install on a bunch of machines. What I'd do, is > install once, get all the pieces/ports/customizations right and then > make a tarball of the system. To install the next machine, I'd use > sysinstall to partition and label the new machine and then just nfs > mount the machine with the tarball, unroll it and just fix rc.conf as > necessary. But when you go this way, there are no commands available > available at the holographic shell. Could this be fixed by letting > the commands be linked/copied into the chroot env? Um. But the chroot directory, e.g. where all your filesystems are mounted, is where you're also supposed to extract the bits or you'd be attempting to whap this NFS-mounted tarball onto your MFS. :) This question doesn't quite make sense to me, 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 Sat Oct 23 10:33:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7256514C3E for ; Sat, 23 Oct 1999 10:33:21 -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 KAA22239 for ; Sat, 23 Oct 1999 10:33:15 -0700 Date: Sat, 23 Oct 1999 10:33:17 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: does anybody but me have this problem (vgrind grinds forever...) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 853 ?? Is 0:00.02 /bin/sh -c $HOME/bin/Nightly-FreeBSD-Build 855 ?? I 0:00.01 /bin/sh /home/mjacob/bin/Nightly-FreeBSD-Build 857 ?? I 0:00.02 sh ./DOMAKE buildworld 858 ?? I 0:00.03 make buildworld 861 ?? I 0:00.00 /bin/sh -ec cd /usr/src; make -f Makefile.inc0 -m /u 862 ?? I 0:00.03 make -f Makefile.inc0 -m /usr/src/share/mk buildworld 865 ?? I 0:00.00 /bin/sh -ec cd /usr/src; make -m /usr/src/share/mk - 866 ?? I 0:00.13 make -m /usr/src/share/mk -f Makefile.inc1 buildworld 1268 ?? I 0:00.00 /bin/sh -ec cd /usr/src; PATH=/usr/obj/usr/src/tmp/sb 1269 ?? I 0:00.08 /usr/obj/usr/src/tmp/usr/bin/make DESTDIR -f Makefile 1272 ?? I 0:00.01 /bin/sh -ec for entry in share/info include lib bin 21573 ?? I 0:00.03 /usr/obj/usr/src/tmp/usr/bin/make all SUBDIR_CHANGE D 21577 ?? I 0:00.01 /bin/sh -ec for entry in colldef dict doc examples in 21602 ?? I 0:00.03 /usr/obj/usr/src/tmp/usr/bin/make all SUBDIR_CHANGE D 21606 ?? I 0:00.01 /bin/sh -ec for entry in psd smm usd papers ; do (if 22824 ?? I 0:00.03 /usr/obj/usr/src/tmp/usr/bin/make all SUBDIR_CHANGE D 22828 ?? I 0:00.01 /bin/sh -ec for entry in beyond4.3 diskperf fsinterfa 22865 ?? I 0:00.04 /usr/obj/usr/src/tmp/usr/bin/make all SUBDIR_CHANGE D 22871 ?? I 0:00.00 /bin/sh -ec vgrind -f < /usr/src/share/doc/papers/ker 22872 ?? R 81:53.05 /bin/csh -f /usr/obj/usr/src/tmp/usr/bin/vgrind -f 22873 ?? Z 0:00.00 (vfontedpr) 22874 ?? Z 0:00.00 (cat) It really is vgring hanging on a file: vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms A plain vgrind -f on this file also hangs. Anyone have a clue on this? This happens for me on an alpha. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 10:56:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6356F14C23 for ; Sat, 23 Oct 1999 10:56:24 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA00844; Sat, 23 Oct 1999 10:56:19 -0700 (PDT) (envelope-from dillon) Date: Sat, 23 Oct 1999 10:56:19 -0700 (PDT) From: Matthew Dillon Message-Id: <199910231756.KAA00844@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: does anybody but me have this problem (vgrind grinds forever...) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :It really is vgring hanging on a file: : :vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms : :A plain vgrind -f on this file also hangs. Anyone have a clue on this? : :This happens for me on an alpha. : :-matt The vgrind command above does not hang on my PIII test box. It takes about a second to run. I tried both an old binary and a new binary of vgrind. Both worked. I recommend compiling vgrind up w/ full debugging and attaching a debugger to it to see what is up. test3:/tmp# vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms test3:/tmp# md5 /usr/src/share/doc/papers/kernmalloc/appendix.t MD5 (/usr/src/share/doc/papers/kernmalloc/appendix.t) = bd78df7b99cbaddae3cf952b6898fe1d -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 Oct 23 10:56:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id B29EC14CF4; Sat, 23 Oct 1999 10:56:16 -0700 (PDT) (envelope-from will@shadow.blackdawn.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=shadow.blackdawn.com) by neptune.psn.net with esmtp (PSN Internet Service 2.12 #3) id 11f5Oh-0001Me-00; Sat, 23 Oct 1999 10:56:08 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id NAA86693; Sat, 23 Oct 1999 13:55:43 -0400 (EDT) (envelope-from will) 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: <199910230241.UAA26689@harmony.village.org> Date: Sat, 23 Oct 1999 13:55:43 -0400 (EDT) Reply-To: Will Andrews From: Will Andrews To: Warner Losh Subject: RE: sio working Cc: mobile@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Oct-99 Warner Losh wrote: > OK. I managed to get sio and ep working on the plane back from > FreeBSDCon'99. There are some problems with card eject at the moment, > but will be committing things to the tree shortly. I will be your guinea pig, if you like. :-) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 10:57: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 ED4EC15085 for ; Sat, 23 Oct 1999 10:57:31 -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 KAA22384; Sat, 23 Oct 1999 10:57:29 -0700 Date: Sat, 23 Oct 1999 10:57:31 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: does anybody but me have this problem (vgrind grinds forever...) In-Reply-To: <199910231756.KAA00844@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 On Sat, 23 Oct 1999, Matthew Dillon wrote: > :It really is vgring hanging on a file: > : > :vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms > : > :A plain vgrind -f on this file also hangs. Anyone have a clue on this? > : > :This happens for me on an alpha. > : > :-matt > > The vgrind command above does not hang on my PIII test box. It takes > about a second to run. I tried both an old binary and a new binary of > vgrind. Both worked. > > I recommend compiling vgrind up w/ full debugging and attaching a > debugger to it to see what is up. Sigh. Yes. > > test3:/tmp# vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms > test3:/tmp# md5 /usr/src/share/doc/papers/kernmalloc/appendix.t > MD5 (/usr/src/share/doc/papers/kernmalloc/appendix.t) = bd78df7b99cbaddae3cf952b6898fe1d > > -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 Oct 23 11: 2:18 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 C3C6914BC5; Sat, 23 Oct 1999 11:02:03 -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 MAA25416; Sat, 23 Oct 1999 12:02:01 -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 MAA32825; Sat, 23 Oct 1999 12:02:24 -0600 (MDT) Message-Id: <199910231802.MAA32825@harmony.village.org> To: Will Andrews Subject: Re: sio working Cc: mobile@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Sat, 23 Oct 1999 13:55:43 EDT." References: Date: Sat, 23 Oct 1999 12:02:24 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Will Andrews writes: : I will be your guinea pig, if you like. :-) Grab the current patches from http://www.freebsd.org/~imp/pccard-snap.patch but read my other posting about the warnings and such. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 13: 0:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (Postfix) with ESMTP id 7BAE714E96 for ; Sat, 23 Oct 1999 13:00:24 -0700 (PDT) (envelope-from mike@sentex.net) Received: from gravel (ospf-mdt.sentex.net [205.211.164.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id QAA22918 for ; Sat, 23 Oct 1999 16:00:14 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <4.1.19991023155842.043bde60@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 23 Oct 1999 16:00:05 -0400 To: freebsd-current@freebsd.org From: Mike Tancsa Subject: CVSUP ? 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 something up with the cvsup servers or is my repository hosed? I havent seen any updates in over a day. How do I go about checking if something is messed up on my end ? ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 13: 3:58 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 10F4A14C40 for ; Sat, 23 Oct 1999 13:03:56 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA10223; Sat, 23 Oct 1999 13:03:54 -0700 (PDT) Date: Sat, 23 Oct 1999 13:03:54 -0700 (PDT) From: Julian Elischer To: Mike Tancsa Cc: freebsd-current@FreeBSD.ORG Subject: Re: CVSUP ? In-Reply-To: <4.1.19991023155842.043bde60@granite.sentex.ca> Message-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's hosed. There are several emails in -hackers on this. so we're just waiting for a human to go fix it. On Sat, 23 Oct 1999, Mike Tancsa wrote: > > Is there something up with the cvsup servers or is my repository hosed? I > havent seen any updates in over a day. How do I go about checking if > something is messed up on my end ? > > ---Mike > ********************************************************************** > Mike Tancsa, Network Admin * mike@sentex.net > Sentex Communications Corp, * http://www.sentex.net/mike > Cambridge, Ontario * 01.519.651.3400 > Canada * > > > 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 Oct 23 13:52:59 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 C5FAE14DE3 for ; Sat, 23 Oct 1999 13:52:52 -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 NAA07629; Sat, 23 Oct 1999 13:44:29 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910232044.NAA07629@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer Cc: Mike Tancsa , freebsd-current@FreeBSD.ORG Subject: Re: CVSUP ? In-reply-to: Your message of "Sat, 23 Oct 1999 13:03:54 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 23 Oct 1999 13:44:28 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's hosed. There are several emails in -hackers on this. so we're just > waiting for a human to go fix it. Someone or something has broken cvsupd on freefall. Until jdp gets back from FreeBSD Con (or someone gives him connectivity there, since we had to pack up the terminal room), there's not going to be any more updates. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 14:20:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mpp.pro-ns.net (pppdsle45.mpls.uswest.net [216.160.23.45]) by hub.freebsd.org (Postfix) with ESMTP id D25F014C24 for ; Sat, 23 Oct 1999 14:20:53 -0700 (PDT) (envelope-from mpp@mpp.pro-ns.net) Received: (from mpp@localhost) by mpp.pro-ns.net (8.9.3/8.9.3) id QAA12105; Sat, 23 Oct 1999 16:19:39 -0500 (CDT) (envelope-from mpp) Date: Sat, 23 Oct 1999 16:19:39 -0500 From: Mike Pritchard To: Mike Smith Cc: Julian Elischer , Mike Tancsa , freebsd-current@FreeBSD.ORG Subject: Re: CVSUP ? Message-ID: <19991023161939.A12089@mpp.pro-ns.net> References: <199910232044.NAA07629@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199910232044.NAA07629@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 23, 1999 at 01:44:28PM -0700, Mike Smith wrote: > > It's hosed. There are several emails in -hackers on this. so we're just > > waiting for a human to go fix it. > > Someone or something has broken cvsupd on freefall. Until jdp gets back > from FreeBSD Con (or someone gives him connectivity there, since we had > to pack up the terminal room), there's not going to be any more updates. After we did some more playing on freefall, it looks more like an NFS problem. "ls -l /" hangs on nfsrcv, just like cvsupd is doing right now. -- Mike Pritchard mpp@FreeBSD.org or mpp@mpp.pro-ns.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 14:23: 1 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 4514014E83 for ; Sat, 23 Oct 1999 14:22:59 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id OAA12912; Sat, 23 Oct 1999 14:22:52 -0700 (PDT) Date: Sat, 23 Oct 1999 14:22:52 -0700 (PDT) From: Julian Elischer To: Mike Smith Cc: Mike Tancsa , freebsd-current@FreeBSD.ORG Subject: Re: CVSUP ? In-Reply-To: <199910232044.NAA07629@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 NFS on freefall. is hosed.. it needs to be rebooted but no root types are around.. now where are those script kiddies when you need them! On Sat, 23 Oct 1999, Mike Smith wrote: > > It's hosed. There are several emails in -hackers on this. so we're just > > waiting for a human to go fix it. > > Someone or something has broken cvsupd on freefall. Until jdp gets back > from FreeBSD Con (or someone gives him connectivity there, since we had > to pack up the terminal room), there's not going to be any more updates. > > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-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 Oct 23 14:31:11 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 2F25814A2C for ; Sat, 23 Oct 1999 14:31:10 -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 OAA23416; Sat, 23 Oct 1999 14:31:06 -0700 Date: Sat, 23 Oct 1999 14:31:08 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: NOTE NOTE NOTE:Re: does anybody but me (..vgrinds forever...) In-Reply-To: <199910231756.KAA00844@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 On Sat, 23 Oct 1999, Matthew Dillon wrote: > :It really is vgring hanging on a file: > : > :vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms > : > :A plain vgrind -f on this file also hangs. Anyone have a clue on this? > : > :This happens for me on an alpha. > : > :-matt > > The vgrind command above does not hang on my PIII test box. It takes > about a second to run. I tried both an old binary and a new binary of > vgrind. Both worked. > > I recommend compiling vgrind up w/ full debugging and attaching a > debugger to it to see what is up. Not an executable... but I finally figured it out... Pipes possibly broken as set up by csh- csh was an old (Oct 1) csh. Until I updated csh from the current build tree, what actually was happening was vfontedpr was piping to 'cat -'.... and this was hanging..... Wierd city, but all better now I believe... possibly related to the signal changes(?).... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 19:31:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D023314E14 for ; Sat, 23 Oct 1999 19:31:45 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA03955; Sat, 23 Oct 1999 19:31:44 -0700 (PDT) (envelope-from dillon) Date: Sat, 23 Oct 1999 19:31:44 -0700 (PDT) From: Matthew Dillon Message-Id: <199910240231.TAA03955@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: NOTE NOTE NOTE:Re: does anybody but me (..vgrinds forever...) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Not an executable... but I finally figured it out... Pipes possibly broken :as set up by csh- csh was an old (Oct 1) csh. Until I updated csh from the :current build tree, what actually was happening was vfontedpr was piping :to 'cat -'.... and this was hanging..... Wierd city, but all better now I :believe... possibly related to the signal changes(?).... : :-matt Weird. I did fix a few pipe bugs a number of weeks ago but this sounds like something different. -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 Oct 23 20:43:16 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 53F941502E for ; Sat, 23 Oct 1999 20:43:13 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id XAA26831 for ; Sat, 23 Oct 1999 23:43:12 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA01244; Sat, 23 Oct 1999 23:42:42 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id XAA00541 for freebsd-current@freebsd.org; Sat, 23 Oct 1999 23:42:42 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199910240342.XAA00541@bb01f39.unx.sas.com> Subject: make release failure -- ed0 in PCCARD To: freebsd-current@freebsd.org Date: Sat, 23 Oct 1999 23:42: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, Make release has been failing for awhile now and I just started to take a look at it. If I remove 'ed0' from i386/conf/PCCARD then the BOOTMFS kernel for pccard links correctly. With ed0 present, the following link errors occur: linking BOOTMFS if_ed_isa.o: In function `ed_isa_probe': if_ed_isa.o(.text+0x45): undefined reference to `ed_probe_WD80x3' if_ed_isa.o(.text+0x54): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x5a): undefined reference to `ed_probe_3Com' if_ed_isa.o(.text+0x69): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x6f): undefined reference to `ed_probe_Novell' if_ed_isa.o(.text+0x7e): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x84): undefined reference to `ed_probe_HP_pclanp' if_ed_isa.o(.text+0x93): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0xa4): undefined reference to `ed_alloc_irq' if_ed_isa.o(.text+0xaf): undefined reference to `ed_release_resources' if_ed_isa.o: In function `ed_isa_attach': if_ed_isa.o(.text+0xef): undefined reference to `ed_alloc_port' if_ed_isa.o(.text+0x109): undefined reference to `ed_alloc_memory' if_ed_isa.o(.text+0x11a): undefined reference to `ed_alloc_irq' if_ed_isa.o(.text+0x127): undefined reference to `edintr' if_ed_isa.o(.text+0x152): undefined reference to `ed_attach' if_ed_isa.o(.text+0x15a): undefined reference to `ed_release_resources' *** Error code 1 The above functions are found in a few places: dev/ed/if_ed.c i386/isa/if_ed pc98/pc98/if_ed.c Ok, pc98 isn't used here... I'm not sure about the 1st two.. However, it appears that in dev/ed/if_ed.c, 'ed_probe_Novell' is defined and globally visible... but, in i386/isa/if_ed.c, 'ed_probe_Novell' is declared static... I don't know if this is the problem, but it's a difference... I'm continuing to look into this. If anyone has any comments, please let me know. Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 20:53:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5AC2715037 for ; Sat, 23 Oct 1999 20:53:43 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA12397; Sat, 23 Oct 1999 20:53:43 -0700 (PDT) (envelope-from dillon) Date: Sat, 23 Oct 1999 20:53:43 -0700 (PDT) From: Matthew Dillon Message-Id: <199910240353.UAA12397@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: trek73 References: <199910240342.XAA00541@bb01f39.unx.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found a copy of the C version of trek73 in my Amiga archives. This is the trek73 originally written in HP-2000 Basic that was rewritten by Dave Pare and Chris Williams in C and seriously enhanced by a bunch of people including me in my early college years circa 1985. I don't think any of the authors would mind if it went into /usr/games, but tracking them down is close to impossible since ucbvax no longer exists. If nobody knows different, I would like to clean it up (fairly easy since it's already in C) and commit it in. I've included the docs below. -Matt Originally written (in HP-2000 BASIC) by William K. Char, Perry Lee, and Dan Gee Rewritten in C by Dave Pare (sdcsvax!sdamos!mr-frog) and Christopher Williams (ucbvax!ucbmerlin!williams) Corrected, Completed, and Enhanced by Jeff Okamoto (ucbvax!okamoto) Peter Yee (ucbvax!yee) Matt Dillon (ucbvax!dillon) Dave Sharnoff (ucbvax!ucbcory!muir) and Joel Duisman (ucbvax!duisman) T R E K 7 3 A Star Trek(R) Battle Simulation Trek73 is a computer-simulated battle based on the famous Star Trek television series and the game Star Fleet Battles. Via computer terminal, you can clash with enemy battle cruisers, such as Klingon D-7's and Romulan Sparrowhawks, and use the same stra- tegies that Captain Kirk has used. Like Kirk, you control a Federation vessel similar to the Enterprise; a computer program directs the enemy. Victory can fall into several categories: Decisive Victory -- You completely destroy or cripple the attacking force. Tactical Victory -- You out-maneuver the enemy using high- speed escapes, corbomite bluffs, `play dead' tactics; or the enemy surrenders. Moral Victory -- You surrender or self-destruct and destroy each other. All distances are measured in megameters, one million meters (abbreviated `M'). Speed is expressed in `warp factors'. Each warp factor equals 100M per second. All angles are expressed in common degrees from zero to 360, measured counter-clockwise from the x-axis, similar to reading a protractor. Only two dimensions are used. Play is as follows: 1. You issue one of a number of commands (fire phasers, change course, launch antimatter pods, surrender, etc.) by typing the appropriate code number into the keyboard; 2. The enemy, under programmed instructions, issues a simi- lar command; 3. Both your commands are executed (phasers are fired, probes are launched, damages are assessed, courses changed, etc.) while the vessels move through space; 4. Unless certain end-game conditions are met (you destroy the enemy, the enemy destroys you, your out-maneuver the enemy, you both destroy each other, or one party surrenders) the above steps are repeated. __________________________ Star Trek is a registered trademark of Paramount Pictures. Although technically incorrect, it does save the player from having to compute cube roots. This saves the player from having to work out problems in spherical geometry. - 1 - STAR TREK Appendix 1 displays certain weapon and shield angles. Appendix 2 depicts the Enterprise's power circuits. Appendix 3 lists certain weapon and vessel specifications. Appendix 4 lists initial deployment of resources. CODE COMMAND ==== ======= 1 Fire Phasers 2 Fire Photon Torpedos 3 Lock Phasers Onto Target 4 Lock Tubes Onto Target 5 Manually Rotate Phasers 6 Manually Rotate Tubes 7 *Phaser Status 8 *Tube Status 9 Load/Unload Torpedo Tubes 10 Launch Antimatter Probe 11 Probe Control (Detonate, Direct, Lock) 12 *Position Report 13 *Position Display 14 Pursue An Enemy Vessel 15 Run From An Enemy Vessel 16 Manually Change Course And Speed 17 *Damage Report 18 Scan Enemy (Damage Report Of Enemy) 19 Alter Power Distribution 20 Alter Torpedo And Phaser Firing Parameters 21 Jettison Engineering 22 Detonate Engineering 23 Attempt Defenseless Ruse 24 Attempt Corbomite Bluff(s) 25 Surrender 26 Ask Enemy to Surrender 27 Initiate Self-Destruct Sequence 28 Abort Self-Destruct 29 Survivors Report 30 *Reprints Above List *Does Not Use A Turn - 2 - STAR TREK Detailed Descriptions of Each Command What follows is a detailed description of each command. Each command is referred to by a number from 1 to 30. After the name of the command is given, a synopsis of the arguments the command requires is given, if any. These arguments can be entered on the command line, separated by a space, if you wish. For instance, to fire phasers 1 through 4 with a spread of 15, you could type '1 1234 15' on the command line. 1. Fire Phasers. [Phasers] [Spread] Phasers are pure energy units which emit a beam similar to lasers, but of a pulsating nature which can be `phased' to inter- fere with the wave pattern of any molecular form. Phasers get their power from phaser banks, which in turn, derive their power from the ship's engines. Each phaser bank is capable of holding a charge of 10 units. When firing, these banks discharge, simi- lar to batteries, to spread their destructive power through space. After discharging, these banks are then recharged by the engines. Each phaser can be set to automatically track a target or can be manually rotated. Unless engineering is jettisoned (code 21), phasers only fire from 0-125 and 235-360 degrees, relative to the ship's course. In other words, each vessel has a 110 degree blind side in back of it in which phasers cannot fire. If phasers fired into this blind side, they would destroy the ship's engineering section. The Captain also designates a wide or narrow phaser beam: a wide beam to disrupt many targets; a narrow beam to inflict max- imum damage on a single target. The maximum spread of phasers is 45 degrees, the minimum is 10 degrees. The total beam width is twice the designated spread. The firing percentage of each bank is preset to 100. In other words, the bank fully discharges when firing. This can be changed, however, using code 22. The maximum range of phasers is 1000M; the maximum hit fac- tor is 45 with a ten degree spread, 10 with a forty-five degree spread. Phaser hit factors are calculated by the following for- mula: hit = (bankunits)(firing%)sqrt(1-range/1000)(45/spread) Phasers fire in .2-second intervals starting with bank one. Phasers inflict heavy damage and casualties, but do not destroy shields as much as antimatter explosions do. A phaser is unable to fire if damaged, if firing into your blind side, or if completely discharged. 2. Fire Photon Torpedos. [Tubes] - 3 - STAR TREK The Enterprise is equipped with six torpedo tubes, which, as phasers, can be set to automatically track a target or be manu- ally rotated. Unless engineering is jettisoned, tubes only fire from 0-135 and 225-360 degrees. Each tube fires all its antimatter pods, which are temporarily held suspended in a magno-photon force field. Photon torpedos can be fired directly at an enemy, laid out as a mine field, or scattered in an attacker's path as depth charges. Tubes must be loaded (code 9) prior to firing. Each tube will be automatically loaded with 10 units or whatever remains in the engines, whichever is less. Normally, torpedos are launched at warp 12 in .2-second intervals, beginning with tube one. Pho- ton torpedos have a proximity fuse of 200M. All of these values can be changed by using code 22. Torpedos must be launched with care since the antimatter pods which are fired can never be recovered. It is suggested that you not fire more than four torpedos at any one time, since a certain number of them do miss, or are destroyed by the enemy firing phasers at them. It is also suggested that you fire them at distant targets, beyond 1100M, to avoid the explosion radii of your own weapons. Hit factors resulting from antimatter explo- sions are calculated as follows: hit = 5(#podscontained)sqrt(1-range/(55(#podscontained))) The maximum hit factor of an antimatter device is five times the number of pods contained (in the case of torpedos, 50); its explosion radius is 50 time the number of pods contained (in the case of torpedos, 500). Antimatter explosions heavily weaken shields but do not damage equipment as much as phasers do. This formula also applies to vessels, engineering sections, and antimatter probe explosions. Tubes are unable to fire if damaged, if firing into your blind side, or if unloaded. 3. Lock Phasers. [Phasers] [Target Name] Phasers locked on an enemy vessel will automatically aim towards it. Although phasers may track a vessel which is in the firing blind side, they will not fire unless engineering is jet- tisoned. To fire at vessels behind, simply change course at least 50 degrees. Once a phaser is locked, it is not disengaged until the target is destroyed (in which case it is then rotated to zero degrees relative), relocked, manually over-ridden, or damaged. 4. Lock Tubes. [Tubes] [Target Name] Tubes lock and unlock in the same manner that phasers do. 5. Manually Rotate Phasers. - 4 - STAR TREK [Phasers] [Bearing] Manually rotating phasers disengages any previous locks and positions them as directed, relative to your course. For exam- ple, if your course is 30, and phasers are rotated 45 degrees, they will hit a target bearing 75 degrees. Rotating phasers into you blind side is permissible, however, they will not fire. 6. Manually Rotate Tubes. [Tubes] [Bearing] Manually rotating tubes is similar to rotating phasers. 7. Phaser Status. Phaser status reports the control (locks and damages), deployment, levels, firing percentages (normally 100), and charge/discharge rates (normally +10) of all phasers. 8. Tube Status. Tube status reports the control, deployment, tube levels, launch speeds (normally 12), proximity delays (normally 200), and the time delays (normally 10). 9. Load/Unload Tubes. [l | u] [Tubes] Tubes are loaded with 10 charged antimatter pods until your fuel runs out. Tubes can also be unloaded if the need arises. 10. Launch Antimatter Probe. [Pods] [Time] [Proximity] [Target | [ Course]] Probes are slow-moving devices equipped with internal gui- dance systems which allow them to chase an enemy vessel. Probes consist of at least ten antimatter pods which are launched from an undamaged probe launcher at warp three. As with torpedos, probes are set with time and proximity fuses, and use the same hit factor formula as do torpedos. 11. Probe Control. [y | [n [Probe] [y | [n [Target | [ Course]]]]]] Probe control allows you to detonate or redirect probes which may have missed. 12. Position Report. Position reports are vital since valuable information on courses, bearings and ranges are given to aid the formation of good strategy. This order does not use a turn. 13. Position Display. [Radius of scan] Position displays, similar to radar scans, show objects which surround your vessel. The Enterprise is indicated by a `+', jettisoned engineering sections by a `#', probes by a `*', torpedos by a `:', and enemy vessels by the first letter of their names. 14. Pursue An Enemy Vessel. - 5 - STAR TREK [Target Name] [Warp Factor] This order instructs the ship's navigation to face an enemy vessel whenever possible. 15. Run From An Enemy Vessel. [Target Name] [Warp Factor] This order, just the opposite of order #14, instructs the navigation to keep the stern of the Enterprise towards an enemy vessel whenever possible. 16. Manually Change Course and Speed. [Course] [Warp Factor] This order instructs navigation to maintain a fixed course and speed. The following information applies to the above three orders: Your maximum rotation rate when turning is: degrees per sec = 5 * (12 - desired warp) Accordingly, you can turn 55 degrees at warp one, 50 at warp two, ..., up to 15 degrees at warp nine. In other words, the faster your speed, the less maneuverable you are. You are also less maneuverable if you lose your warp drive. Your maximum speed is warp nine, the enemy's is warp eleven. 17. Damage Report. This report informs you of certain equipment status. A mal- functioning computer (very rare) make orders 3 (lock phasers), 4 (lock torpedos), 14 (pursue), 15 (run), 27 (initiate self- destruct), and 28 (abort self-destruct) impossible to execute. You will be required to manually rotate phasers and torpedos, and manually change course and speed. Damaged sensors (rare) makes orders 13 (position report) and 18 (scan) impossible. A damaged probe launcher (sometimes) prevents you from launching probes. A disabled warp drive (common) slows your speed and maneuverabil- ity. See order #20 about jettisoned engineering section. When your crew of 450 dies, your vessel is as good as dead. There are 350 men aboard each enemy vessel. Shield percentage is calculated by its energy drain times its operating efficiency. Efficiency starts at 100 and declines with each hit. No damages of any kind are incurred when a shield absorbs its first hit, no matter how great the hit. Shield one is 1.5 times as strong as the other three shields. `Efficiency' indicates the number of energy units being burned per warp-second. This number is initially one (.75 for enemy) and increases per hit. `Regeneration' indicates the number of energy units being gained per second. Initially set at 10, this number decreases per hit. `Fuel capacity' indicates the number of matter-antimatter - 6 - STAR TREK pods a vessel has aboard. This number rapidly decreases with each torpedo or probe fired. `Fuel' indicates the number of matter-antimatter pods which are filled with energy. This number rapidly decreases when main- taining high warp speeds or firing phasers. 18. Scan Enemy (Damage Report of Enemy). [Ship Name] An enemy damage report is essentially the same as the Enterprise's. 19. Alter Power Distribution. [Shld 1 drain [* | ... Sh 4]] [Phsr 1 drain [* | ... Ph 4]] The synopsis of this command can be confusing. The first set of numbers gives the drains for each shield. All four shield drains can be specified, but if a star is used immediately after a shield drain (eg, 19 0.5 1*), then the remaining shields will all be given a drain equal to the number preceding the '*'. (Thus, in the above example, shield 1's drain is 0.5, whereas shields 2, 3, and 4 have a drain of 1). The same applies to the phaser drains. The power circuits of all vessels are illustrated in appen- dix 2. Dilithium crystals produce energy much like generators. This power is then used to maintain warp speeds, recharge antimatter pods in the engine reserve, recharge phaser banks, or maintain shield power. Your initial regeneration is ten, how- ever, shields normally drain four units and engines burn one unit per each warp-second. Shields can be thought of as electro-magnets. The more energy put into them, the stringer their force field becomes. Therefore, a shield's overall percentage is calculated by the following formula: shield percentage = (energy in)(effective %) Notice that dropping power to a shield has the same effect as having it hit. Notice also that if your regeneration drops below four, you may have to discharge your phaser banks to main- tain full shield power. Phaser banks, similar to batteries, not only discharge (when firing), but also recharge. Initially, they are set to recharge fully in one second (+10) so that you can continually use them. However, they can discharge fully (-10) in one second to provide extra power to shields, warp engines, or engine reserve. Under most conditions, you need not concern yourself with power distribution unless some special need arises. Distribu- tion, for the most part, is automatic. Regeneration is calcu- lated first; that power is placed in reserve, along with any discharged phaser units. Shield drain is calculated next, then - 7 - STAR TREK phaser and engine drains. Be concerned with wasting power by indiscriminately firing phasers and torpedos, maintaining speeds over warp three, or dumping scores of units onto antimatter probes. Huge power losses cannot be made up in battle. 20. Jettison Engineering. Although this order was never executed in the television series, it is quite possible, according to its producer. Jettis- oning engineering has serious consequences, but it may be your only course of action. One would jettison engineering if being pursed by vessels, probes or torpedos, or as a suicidal gesture. The following things happen when engineering is jettisoned: A: You lose all your fuel and reserve capacity; B: you lose your regeneration; C: you lose your warp drive; D: your lose your probe launcher; E: you lose your shields until you designate phasers to discharge; F: the engineering section itself decelerates to a stop; G: a ten second time delay on it is set; H: hopefully, when it does explode, you are far from its effects; I: your phasers and torpedos are now free to fire in any direc- tion. 21. Detonate Engineering. [nothing | [y | n]] This order, issued after the previous one, manually detonates your engineering section. It may also be issued without the previous order, in which case you will be asked to confirm your (crazy) order. 22. Alter Torpedo And Phaser Firing Parameters. [[y [Launch Speed] [Time Delay] [Proximity Fuse]] | n] [[y [Firing Percentage]] | n] This option allows you to change the launch speeds, time and proximity delays of all torpedos. At the beginning of play, tor- pedos are launched at warp twelve, have ten second time fuses, and 200M proximity fuses. Any vessel or engineering section which comes within the proximity range will cause the torpedo to explode. Phaser firing percentages can also be altered. A phaser bank need not fire its full charge. 23. Defenseless Ruse. [e | p] Another name for this tactic is `playing dead'. When issued, your shields are dropped to zero, and power is diverted to your engines or phaser banks. Hopefully, the enemy will believe you dead and come too close or break off their attack. You should then be able to fire or run in the opposite direction. - 8 - STAR TREK 24. Attempt Corbomite Bluff(s). There were two corbomite bluffs in the television series; one was against a midget operating a huge space vessel the other was against Romulan attackers. Both have been incorporated into this game. Whichever bluff issued is selected randomly. 25. Surrender, If Possible. This order sends a message to the enemy, saying that you wish to surrender. The enemy will then decide whether or not take you alive. You will have difficulty surrendering to Romu- lans, who have never accepted one. 26. Ask Enemy To Surrender. This order ends a message to the enemy demanding that they surrender. Please bear in mind that Romulans are the most suici- dal. 27. Initiate Self-Destruct. This order activates a twenty-second self-destruct sequence. Because final destruct does not occur until ten turns after ini- tialization, it is best to start it early, if at all. When you do explode, you hope that you explosive force will also destroy your attackers. 28. Abort Self-Destruct. This order, issued after the previous one, halts the des- truct sequence. Self-destruct cannot be aborted withing five seconds to detonation. 29. Survivors Report This order prints out the number of survivors on board all the ships. This order does not use a turn. 30. Reprint Above List. This option, which does not use a turn, lists code numbers and associated descriptions of each. 31 And Up. Future options, currently being designed in Trek74, will include Dr. Daystrom's paranoid, M5 multi-tronics computer which will take over while you relax; or battle someone else who is on another terminal; or battle in teams; or have a free-for-all against nine other starships. - 9 - STAR TREK Options In TREK73, all the names are taken from the series Star Trek. Through the use of options, the names can be changed to whatever you want. To use the options, you must add the variable TREK73OPTS to your environment. A sample would be (using the C-shell): setenv TREK73OPTS 'name=Jerk, ship=Boobyprize, terse' The option string is a list of comma-separated options. Options are designated as either boolean or string options. Boolean options are turned on by typing their name and turned off by prepending 'no' to them. String options are set equal to the string which follows the "=". There follows a list of all the options, what type it is, and an explanation of what they mean. The default for the option is in square brackets following the option. terse BOOLEAN [noterse]This option, when set, turns off the information regarding the ship's purpose in the area. It thus reduces the amount of drek on the screen. If you are on a slow terminal, this is a nice option to have set. shipname STRING [Enterprise]This option names your ship. name STRINGThis option names the captain of the ship. If this option is not set, then the program will ask for a name. The captain is the one who must make all the decisions of strategy and tactics for the ship. sex STRINGThis option gives the captain a gender. If this option is not set, the program will ask for it's value. If you respond with something that starts with other than "m" or "f", beware! science STRING [Spock]This option names the science officer, who is responsible for checking the parameters of the captain's commands. It is also this officer's duty to report damage to the ship as well as scan for enemy damage. engineer STRING [Scott]This option names the chief engineer of the ship. It is this officer's duty to report on the status of the ship, especially its energy supply and distribution of the same. The officer also controls the launching of anti-matter probes. helmsman STRING [Sulu]This option names the ship's helmsman. This officer's duty is to control the speed of the ship and also controls the firing of the ship's weapons. - 10 - STAR TREK nav STRING [Chekov]This option names the ship's navigator, who is responsible for the navigation of the ship. This officer makes changes to the ship's course as directed by the cap- tain. This officer also controls any anti-matter probes after they have been launched. com STRING [Uhura]This option names the ship's communications officer. It is the duty of this officer to handle all com- munications between the ship and the rest of the universe. ships STRINGThis option, if set, tells the program how many ships you wish to fight. If it is not set, then the program will ask. enemy STRING [random]If this option is set, it tells the program which race you wish to fight. The available races are: Klingon, Romulan, Kzinti, Gorn, Orion, Hydran, Lyran, or Tholian. If the option is not set, the race you will fight is chosen at random. foename STRING [random]If this option is set, it specifies the name of the commander of the enemy ship(s). If this option is not specified, the name is chosen at random. silly BOOLEAN [nosilly]If this option is set, an additional race is added to the list of possible races to fight. This race is the Monty Pythons. Note that if you wish to always fight the Monty Python's, you merely have to set the enemy option above. - 11 - STAR TREK Simple Strategy If you are a beginner, a simple strategy to follow is A: fight only one attacker; B: pursue him (code 14) at warp factor one; C: lock on all phasers (code 3); D: continuously take posi- tion reports (code 12) and watch his range; E: when he gets within 1000M, fire all phasers (code 1) and keep on firing when he is in range; F: When the enemy is out of range, take damage reports and scans of the enemy (codes 17 and 18). After a few trial games using the above strategy, you will want to become as efficient as the enemy at firing photon tor- pedos. Finally, when you master launching antimatter probes, you can designate more that one attacker. Trek73's History Trek73 was programmed on a Hewlett-Packard 2000C system by William K. Char, Perry Lee, and Dan Gee. In January, 1973, Mr. Char started with a few ideas and five months later, in May, introduced $SPACE, his first version. Space had only 14 commands and comprised one 10K program. Response was so great that new ideas flooded in and in June, work on Trek73 was begun. Over 70 recordings of past shows were reviewed to reconstruct dialogue and vessels. On October 8, 1973, Trek73 was introduced. In 1984, Dave Pare at Univeristy of California at San Diego and Chris Williams at the University of California at Berkeley independently translated the BASIC code into C to run under BSD UNIX. In April 1985, Jeff Okamoto and Peter Yee, both at the University of California at Berkeley combined the two versions into one, fixing bugs and adding new commands. The user-settable options were also added. Ideas and bug reports should be sent to: ARPA: okamoto@BERKELEY and yee@BERKELEY UUCP: ..!ucbvax!okamoto and ..!ucbvax!yee __________________________ UNIX is a registered trademark of Bell Laboratories. - 12 - STAR TREK APPENDIX 1 Secondary Hull Primary Hull (engineering) ------- :-----------------------------------------\ | .5 | . . . . :: N C C - 1 7 0 1 |} |0 / 1|---< . . . . . ::________________________________________/ | | . . . . warp engines ^ | .5 | . . . . +++ |0 / 1|---< . . . . . ===== | fuel | | . . . . |+| + OOOOO reserve | .5 | . . . . |+| ---------> +++ ---> OOOOO --- +++ ---> |0 / 1|---< . . . . . ------- + ***** | | . . . . | | ***** shield | .5 | . . . . ------- | \ control |0 / 1|---< . . . . . dilithium * \ ------- . . . . crystal *** +++ shields generator * \phaser control | -------- : : : | |-10/10|-OOOO>. . : : : | : : <***: <[=====| <---+ |-10/10|-**OO>. . : : : : probe launcher | |-10/10|-****> V |-10/10|-****> =*******= -------- phaser banks photon =*****=== torpedo =**====== tubes =======****** ========= ******* ========= ******** + Energy unit O Matter-anti-matter pod * Filled matter-anti-matter pod ---+++---> Energy transfer ---***---> Pod transfer - 13 - STAR TREK APPENDIX 2 Shield 2 | 135 90 \\,,,,,,,,''-``,,,,,,,, ,,''\ .Phaser.Firing An``,, 45 ,' \ \125 gles`,/ ,' \. . Torpedo. . `, :------------------------\ \135_-----_ Fir . , :________________________/ _- 1 -_ ing . ` | || / 0 \ Angles . | Shield | ,_^^_____/| _ 7 | . . | Shield -180| [ { (o) 1 } . . |0- 3 | `-vv-----\| - C | . . | 1 | || \ C / . . | :-----------------------\ -_ N _- . . , :_______________________/ -_____- . . ' `, /225. . . . . . . ,' `, / . ,' \ ``,/ /235. . . . . . . . ,,'' 315 /`````````,,_,,'''''''' 225 270 | Shield 4 - 14 - STAR TREK APPENDIX 3 Weapon And Vessel Specifications Enemy exceptions are enclosed within [brackets] Phasers Number of banks 4 Max range 1000 megameters Max spread 90 degrees (45+45) Min spread 20 degrees (10+10) Max hit with 45 degree spread 10 Max hit with 10 degree spread 45 Loss of shield 1 per hit hit/4.5 Loss of shields 2-3-4 per hit hit/3 Firing angles with engineering 0-125, 235-360 degrees Max charge per bank 10 units Min charge or discharge time 1 sec Tubes Number of tubes 6 Max range 12,000 megameters max launch speed warp 12 Max time delay 10 seconds Max proximity delay 500M Max explosion radius 500M Max number of pods launched 10 Max hit factor 50 Loss of shield 1 per hit hit/3 Loss of shields 2-3-4 per hit hit/2 Firing angles with engineering 0-135, 225-360 degrees Probes Number of probe launchers 1 Max range 3000M Max launch speed 2 Max time delay 15 sec Max proximity delay any Max explosion radius 50 times number of pods Max pods launched fuel available Max hit factor 10 times number of pods Loss of shields per hit same as torpedos Firing angles with engineering all Vessels Max turning rate 50 degrees Max speed warp 99 [11] Min units burned per warp-second 1 [.75] Crew 450 d[350] APPENDIX 4 Initial Settings - 15 - STAR TREK Enemy exceptions are enclosed within [brackets] Crew 450 [350] Speed 1000 megameters Course 0 [0-360] degrees Engine Efficiency 1 [.75] Fuel Level 150 Fuel Capacity 200 Regeneration Rate per Second 10 Helm Lock None [Federation Vessel] Phaser Deployment 90, 0, 0, 270 Phaser Bank Levels 4 x 10 units Phaser Charge/Discharge Rates 4 x 10 units Shield Drain 4 x 1 units Shield Percentage 4 x 100 Torpedo Deployment 120, 60, 0, 0, 300, 240 Tube Levels 6 x Zero Total Charged Pods Available 190 - 16 - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 21: 3:58 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 4B3C514C1D for ; Sat, 23 Oct 1999 21:03:44 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id VAA26395; Sat, 23 Oct 1999 21:03:39 -0700 (PDT) Date: Sat, 23 Oct 1999 21:03:39 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: trek73 In-Reply-To: <199910240353.UAA12397@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 a port? On Sat, 23 Oct 1999, Matthew Dillon wrote: > I found a copy of the C version of trek73 in my Amiga archives. This > is the trek73 originally written in HP-2000 Basic that was rewritten > by Dave Pare and Chris Williams in C and seriously enhanced by a bunch > of people including me in my early college years circa 1985. > > I don't think any of the authors would mind if it went into /usr/games, > but tracking them down is close to impossible since ucbvax no longer > exists. If nobody knows different, I would like to clean it up (fairly > easy since it's already in C) and commit it in. > > I've included the docs below. > > -Matt > > > > > Originally written (in HP-2000 BASIC) by > William K. Char, Perry Lee, and Dan Gee > > Rewritten in C by > Dave Pare (sdcsvax!sdamos!mr-frog) > and > Christopher Williams (ucbvax!ucbmerlin!williams) > > Corrected, Completed, and Enhanced by > Jeff Okamoto (ucbvax!okamoto) > Peter Yee (ucbvax!yee) > Matt Dillon (ucbvax!dillon) > Dave Sharnoff (ucbvax!ucbcory!muir) > and > Joel Duisman (ucbvax!duisman) > > > T R E K 7 3 > A Star Trek(R) Battle Simulation > > Trek73 is a computer-simulated battle based on the famous > Star Trek television series and the game Star Fleet Battles. Via > computer terminal, you can clash with enemy battle cruisers, such > as Klingon D-7's and Romulan Sparrowhawks, and use the same stra- > tegies that Captain Kirk has used. Like Kirk, you control a > Federation vessel similar to the Enterprise; a computer program > directs the enemy. Victory can fall into several categories: > > Decisive Victory -- You completely destroy or cripple the > attacking force. > > Tactical Victory -- You out-maneuver the enemy using high- > speed escapes, corbomite bluffs, `play dead' tactics; or the > enemy surrenders. > > Moral Victory -- You surrender or self-destruct and destroy > each other. > > All distances are measured in megameters, one million meters > (abbreviated `M'). Speed is expressed in `warp factors'. Each > warp factor equals 100M per second. All angles are expressed in > common degrees from zero to 360, measured counter-clockwise from > the x-axis, similar to reading a protractor. Only two dimensions > are used. > > Play is as follows: > > 1. You issue one of a number of commands (fire phasers, > change course, launch antimatter pods, surrender, etc.) by typing > the appropriate code number into the keyboard; > > 2. The enemy, under programmed instructions, issues a simi- > lar command; > > 3. Both your commands are executed (phasers are fired, > probes are launched, damages are assessed, courses changed, etc.) > while the vessels move through space; > > 4. Unless certain end-game conditions are met (you destroy > the enemy, the enemy destroys you, your out-maneuver the enemy, > you both destroy each other, or one party surrenders) the above > steps are repeated. > > __________________________ > Star Trek is a registered trademark of Paramount > Pictures. > Although technically incorrect, it does save the player > from having to compute cube roots. > This saves the player from having to work out problems > in spherical geometry. > > > > > - 1 - > > > > > > STAR TREK > > > Appendix 1 displays certain weapon and shield angles. > > Appendix 2 depicts the Enterprise's power circuits. > > Appendix 3 lists certain weapon and vessel specifications. > > Appendix 4 lists initial deployment of resources. > > > CODE COMMAND > ==== ======= > > 1 Fire Phasers > 2 Fire Photon Torpedos > 3 Lock Phasers Onto Target > 4 Lock Tubes Onto Target > 5 Manually Rotate Phasers > 6 Manually Rotate Tubes > 7 *Phaser Status > 8 *Tube Status > 9 Load/Unload Torpedo Tubes > 10 Launch Antimatter Probe > > 11 Probe Control (Detonate, Direct, Lock) > 12 *Position Report > 13 *Position Display > 14 Pursue An Enemy Vessel > 15 Run From An Enemy Vessel > 16 Manually Change Course And Speed > 17 *Damage Report > 18 Scan Enemy (Damage Report Of Enemy) > 19 Alter Power Distribution > 20 Alter Torpedo And Phaser Firing Parameters > > 21 Jettison Engineering > 22 Detonate Engineering > 23 Attempt Defenseless Ruse > 24 Attempt Corbomite Bluff(s) > 25 Surrender > 26 Ask Enemy to Surrender > 27 Initiate Self-Destruct Sequence > 28 Abort Self-Destruct > 29 Survivors Report > 30 *Reprints Above List > > *Does Not Use A Turn > > > > > > > > > > > > - 2 - > > > > > > STAR TREK > > > Detailed Descriptions of Each Command > > What follows is a detailed description of each command. > Each command is referred to by a number from 1 to 30. After the > name of the command is given, a synopsis of the arguments the > command requires is given, if any. These arguments can be > entered on the command line, separated by a space, if you wish. > For instance, to fire phasers 1 through 4 with a spread of 15, > you could type '1 1234 15' on the command line. > > 1. Fire Phasers. > [Phasers] [Spread] > Phasers are pure energy units which emit a beam similar to > lasers, but of a pulsating nature which can be `phased' to inter- > fere with the wave pattern of any molecular form. Phasers get > their power from phaser banks, which in turn, derive their power > from the ship's engines. Each phaser bank is capable of holding > a charge of 10 units. When firing, these banks discharge, simi- > lar to batteries, to spread their destructive power through > space. After discharging, these banks are then recharged by the > engines. Each phaser can be set to automatically track a target > or can be manually rotated. Unless engineering is jettisoned > (code 21), phasers only fire from 0-125 and 235-360 degrees, > relative to the ship's course. In other words, each vessel has a > 110 degree blind side in back of it in which phasers cannot fire. > If phasers fired into this blind side, they would destroy the > ship's engineering section. > > The Captain also designates a wide or narrow phaser beam: a > wide beam to disrupt many targets; a narrow beam to inflict max- > imum damage on a single target. The maximum spread of phasers is > 45 degrees, the minimum is 10 degrees. The total beam width is > twice the designated spread. > > The firing percentage of each bank is preset to 100. In > other words, the bank fully discharges when firing. This can be > changed, however, using code 22. > > The maximum range of phasers is 1000M; the maximum hit fac- > tor is 45 with a ten degree spread, 10 with a forty-five degree > spread. Phaser hit factors are calculated by the following for- > mula: > > hit = (bankunits)(firing%)sqrt(1-range/1000)(45/spread) > > Phasers fire in .2-second intervals starting with bank one. > Phasers inflict heavy damage and casualties, but do not destroy > shields as much as antimatter explosions do. > > A phaser is unable to fire if damaged, if firing into your > blind side, or if completely discharged. > > 2. Fire Photon Torpedos. > [Tubes] > > > > - 3 - > > > > > > STAR TREK > > > The Enterprise is equipped with six torpedo tubes, which, as > phasers, can be set to automatically track a target or be manu- > ally rotated. Unless engineering is jettisoned, tubes only fire > from 0-135 and 225-360 degrees. Each tube fires all its > antimatter pods, which are temporarily held suspended in a > magno-photon force field. Photon torpedos can be fired directly > at an enemy, laid out as a mine field, or scattered in an > attacker's path as depth charges. > > Tubes must be loaded (code 9) prior to firing. Each tube > will be automatically loaded with 10 units or whatever remains in > the engines, whichever is less. Normally, torpedos are launched > at warp 12 in .2-second intervals, beginning with tube one. Pho- > ton torpedos have a proximity fuse of 200M. All of these values > can be changed by using code 22. > > Torpedos must be launched with care since the antimatter > pods which are fired can never be recovered. It is suggested > that you not fire more than four torpedos at any one time, since > a certain number of them do miss, or are destroyed by the enemy > firing phasers at them. It is also suggested that you fire them > at distant targets, beyond 1100M, to avoid the explosion radii of > your own weapons. Hit factors resulting from antimatter explo- > sions are calculated as follows: > > hit = 5(#podscontained)sqrt(1-range/(55(#podscontained))) > > The maximum hit factor of an antimatter device is five times > the number of pods contained (in the case of torpedos, 50); its > explosion radius is 50 time the number of pods contained (in the > case of torpedos, 500). Antimatter explosions heavily weaken > shields but do not damage equipment as much as phasers do. This > formula also applies to vessels, engineering sections, and > antimatter probe explosions. > > Tubes are unable to fire if damaged, if firing into your > blind side, or if unloaded. > > 3. Lock Phasers. > [Phasers] [Target Name] > Phasers locked on an enemy vessel will automatically aim > towards it. Although phasers may track a vessel which is in the > firing blind side, they will not fire unless engineering is jet- > tisoned. To fire at vessels behind, simply change course at > least 50 degrees. Once a phaser is locked, it is not disengaged > until the target is destroyed (in which case it is then rotated > to zero degrees relative), relocked, manually over-ridden, or > damaged. > > 4. Lock Tubes. > [Tubes] [Target Name] > Tubes lock and unlock in the same manner that phasers do. > > 5. Manually Rotate Phasers. > > > > - 4 - > > > > > > STAR TREK > > > [Phasers] [Bearing] > Manually rotating phasers disengages any previous locks and > positions them as directed, relative to your course. For exam- > ple, if your course is 30, and phasers are rotated 45 degrees, > they will hit a target bearing 75 degrees. Rotating phasers into > you blind side is permissible, however, they will not fire. > > 6. Manually Rotate Tubes. > [Tubes] [Bearing] > Manually rotating tubes is similar to rotating phasers. > > 7. Phaser Status. > Phaser status reports the control (locks and damages), > deployment, levels, firing percentages (normally 100), and > charge/discharge rates (normally +10) of all phasers. > > 8. Tube Status. > Tube status reports the control, deployment, tube levels, > launch speeds (normally 12), proximity delays (normally 200), and > the time delays (normally 10). > > 9. Load/Unload Tubes. > [l | u] [Tubes] > Tubes are loaded with 10 charged antimatter pods until your > fuel runs out. Tubes can also be unloaded if the need arises. > > 10. Launch Antimatter Probe. > [Pods] [Time] [Proximity] [Target | [ Course]] > Probes are slow-moving devices equipped with internal gui- > dance systems which allow them to chase an enemy vessel. Probes > consist of at least ten antimatter pods which are launched from > an undamaged probe launcher at warp three. As with torpedos, > probes are set with time and proximity fuses, and use the same > hit factor formula as do torpedos. > > 11. Probe Control. > [y | [n [Probe] [y | [n [Target | [ Course]]]]]] > Probe control allows you to detonate or redirect probes > which may have missed. > > 12. Position Report. > Position reports are vital since valuable information on > courses, bearings and ranges are given to aid the formation of > good strategy. This order does not use a turn. > > 13. Position Display. > [Radius of scan] > Position displays, similar to radar scans, show objects > which surround your vessel. The Enterprise is indicated by a > `+', jettisoned engineering sections by a `#', probes by a `*', > torpedos by a `:', and enemy vessels by the first letter of their > names. > > 14. Pursue An Enemy Vessel. > > > > - 5 - > > > > > > STAR TREK > > > [Target Name] [Warp Factor] > This order instructs the ship's navigation to face an enemy > vessel whenever possible. > > 15. Run From An Enemy Vessel. > [Target Name] [Warp Factor] > This order, just the opposite of order #14, instructs the > navigation to keep the stern of the Enterprise towards an enemy > vessel whenever possible. > > 16. Manually Change Course and Speed. > [Course] [Warp Factor] > This order instructs navigation to maintain a fixed course > and speed. The following information applies to the above three > orders: > > Your maximum rotation rate when turning is: > degrees per sec = 5 * (12 - desired warp) > > Accordingly, you can turn 55 degrees at warp one, 50 at warp > two, ..., up to 15 degrees at warp nine. In other words, the > faster your speed, the less maneuverable you are. You are also > less maneuverable if you lose your warp drive. Your maximum > speed is warp nine, the enemy's is warp eleven. > > 17. Damage Report. > This report informs you of certain equipment status. A mal- > functioning computer (very rare) make orders 3 (lock phasers), 4 > (lock torpedos), 14 (pursue), 15 (run), 27 (initiate self- > destruct), and 28 (abort self-destruct) impossible to execute. > You will be required to manually rotate phasers and torpedos, and > manually change course and speed. Damaged sensors (rare) makes > orders 13 (position report) and 18 (scan) impossible. A damaged > probe launcher (sometimes) prevents you from launching probes. A > disabled warp drive (common) slows your speed and maneuverabil- > ity. See order #20 about jettisoned engineering section. When > your crew of 450 dies, your vessel is as good as dead. There are > 350 men aboard each enemy vessel. > > Shield percentage is calculated by its energy drain times > its operating efficiency. Efficiency starts at 100 and declines > with each hit. No damages of any kind are incurred when a shield > absorbs its first hit, no matter how great the hit. Shield one > is 1.5 times as strong as the other three shields. > > `Efficiency' indicates the number of energy units being > burned per warp-second. This number is initially one (.75 for > enemy) and increases per hit. > > `Regeneration' indicates the number of energy units being > gained per second. Initially set at 10, this number decreases > per hit. > > `Fuel capacity' indicates the number of matter-antimatter > > > > - 6 - > > > > > > STAR TREK > > > pods a vessel has aboard. This number rapidly decreases with > each torpedo or probe fired. > > `Fuel' indicates the number of matter-antimatter pods which > are filled with energy. This number rapidly decreases when main- > taining high warp speeds or firing phasers. > > 18. Scan Enemy (Damage Report of Enemy). > [Ship Name] > An enemy damage report is essentially the same as the > Enterprise's. > > 19. Alter Power Distribution. > [Shld 1 drain [* | ... Sh 4]] [Phsr 1 drain [* | ... Ph 4]] > The synopsis of this command can be confusing. The first > set of numbers gives the drains for each shield. All four shield > drains can be specified, but if a star is used immediately after > a shield drain (eg, 19 0.5 1*), then the remaining shields will > all be given a drain equal to the number preceding the '*'. > (Thus, in the above example, shield 1's drain is 0.5, whereas > shields 2, 3, and 4 have a drain of 1). The same applies to the > phaser drains. > > The power circuits of all vessels are illustrated in appen- > dix 2. Dilithium crystals produce energy much like generators. > This power is then used to maintain warp speeds, recharge > antimatter pods in the engine reserve, recharge phaser banks, or > maintain shield power. Your initial regeneration is ten, how- > ever, shields normally drain four units and engines burn one unit > per each warp-second. > > Shields can be thought of as electro-magnets. The more > energy put into them, the stringer their force field becomes. > Therefore, a shield's overall percentage is calculated by the > following formula: > > shield percentage = (energy in)(effective %) > > Notice that dropping power to a shield has the same effect > as having it hit. Notice also that if your regeneration drops > below four, you may have to discharge your phaser banks to main- > tain full shield power. > > Phaser banks, similar to batteries, not only discharge (when > firing), but also recharge. Initially, they are set to recharge > fully in one second (+10) so that you can continually use them. > However, they can discharge fully (-10) in one second to provide > extra power to shields, warp engines, or engine reserve. > > Under most conditions, you need not concern yourself with > power distribution unless some special need arises. Distribu- > tion, for the most part, is automatic. Regeneration is calcu- > lated first; that power is placed in reserve, along with any > discharged phaser units. Shield drain is calculated next, then > > > > - 7 - > > > > > > STAR TREK > > > phaser and engine drains. > > Be concerned with wasting power by indiscriminately firing > phasers and torpedos, maintaining speeds over warp three, or > dumping scores of units onto antimatter probes. Huge power > losses cannot be made up in battle. > > 20. Jettison Engineering. > Although this order was never executed in the television > series, it is quite possible, according to its producer. Jettis- > oning engineering has serious consequences, but it may be your > only course of action. > > One would jettison engineering if being pursed by vessels, > probes or torpedos, or as a suicidal gesture. > > The following things happen when engineering is jettisoned: > A: You lose all your fuel and reserve capacity; B: you lose your > regeneration; C: you lose your warp drive; D: your lose your > probe launcher; E: you lose your shields until you designate > phasers to discharge; F: the engineering section itself > decelerates to a stop; G: a ten second time delay on it is set; > H: hopefully, when it does explode, you are far from its effects; > I: your phasers and torpedos are now free to fire in any direc- > tion. > > 21. Detonate Engineering. > [nothing | [y | n]] > This order, issued after the previous one, manually > detonates your engineering section. It may also be issued > without the previous order, in which case you will be asked to > confirm your (crazy) order. > > 22. Alter Torpedo And Phaser Firing Parameters. > [[y [Launch Speed] [Time Delay] [Proximity Fuse]] | n] [[y > [Firing Percentage]] | n] > This option allows you to change the launch speeds, time and > proximity delays of all torpedos. At the beginning of play, tor- > pedos are launched at warp twelve, have ten second time fuses, > and 200M proximity fuses. Any vessel or engineering section > which comes within the proximity range will cause the torpedo to > explode. > > Phaser firing percentages can also be altered. A phaser > bank need not fire its full charge. > > 23. Defenseless Ruse. > [e | p] > Another name for this tactic is `playing dead'. When > issued, your shields are dropped to zero, and power is diverted > to your engines or phaser banks. Hopefully, the enemy will > believe you dead and come too close or break off their attack. > You should then be able to fire or run in the opposite direction. > > > > > - 8 - > > > > > > STAR TREK > > > 24. Attempt Corbomite Bluff(s). There were two corbomite bluffs > in the television series; one was against a midget operating a > huge space vessel the other was against Romulan attackers. Both > have been incorporated into this game. Whichever bluff issued is > selected randomly. > > 25. Surrender, If Possible. > This order sends a message to the enemy, saying that you > wish to surrender. The enemy will then decide whether or not > take you alive. You will have difficulty surrendering to Romu- > lans, who have never accepted one. > > 26. Ask Enemy To Surrender. > This order ends a message to the enemy demanding that they > surrender. Please bear in mind that Romulans are the most suici- > dal. > > 27. Initiate Self-Destruct. > This order activates a twenty-second self-destruct sequence. > Because final destruct does not occur until ten turns after ini- > tialization, it is best to start it early, if at all. When you > do explode, you hope that you explosive force will also destroy > your attackers. > > 28. Abort Self-Destruct. > This order, issued after the previous one, halts the des- > truct sequence. Self-destruct cannot be aborted withing five > seconds to detonation. > > 29. Survivors Report > This order prints out the number of survivors on board all > the ships. This order does not use a turn. > > 30. Reprint Above List. > This option, which does not use a turn, lists code numbers > and associated descriptions of each. > > 31 And Up. > Future options, currently being designed in Trek74, will > include Dr. Daystrom's paranoid, M5 multi-tronics computer which > will take over while you relax; or battle someone else who is on > another terminal; or battle in teams; or have a free-for-all > against nine other starships. > > > > > > > > > > > > > > > - 9 - > > > > > > STAR TREK > > > Options > > In TREK73, all the names are taken from the series Star > Trek. Through the use of options, the names can be changed to > whatever you want. > > To use the options, you must add the variable TREK73OPTS to > your environment. A sample would be (using the C-shell): > > setenv TREK73OPTS 'name=Jerk, ship=Boobyprize, terse' > > The option string is a list of comma-separated options. > Options are designated as either boolean or string options. > Boolean options are turned on by typing their name and turned off > by prepending 'no' to them. String options are set equal to the > string which follows the "=". > > There follows a list of all the options, what type it is, > and an explanation of what they mean. The default for the option > is in square brackets following the option. > > terse BOOLEAN [noterse]This option, when set, turns off the > information regarding the ship's purpose in the area. It > thus reduces the amount of drek on the screen. If you are > on a slow terminal, this is a nice option to have set. > > shipname STRING [Enterprise]This option names your ship. > > name STRINGThis option names the captain of the ship. If this > option is not set, then the program will ask for a name. > The captain is the one who must make all the decisions of > strategy and tactics for the ship. > > sex STRINGThis option gives the captain a gender. If this option > is not set, the program will ask for it's value. If you > respond with something that starts with other than "m" or > "f", beware! > > science STRING [Spock]This option names the science officer, who > is responsible for checking the parameters of the captain's > commands. It is also this officer's duty to report damage > to the ship as well as scan for enemy damage. > > engineer STRING [Scott]This option names the chief engineer of > the ship. It is this officer's duty to report on the status > of the ship, especially its energy supply and distribution > of the same. The officer also controls the launching of > anti-matter probes. > > helmsman STRING [Sulu]This option names the ship's helmsman. > This officer's duty is to control the speed of the ship and > also controls the firing of the ship's weapons. > > > > > > - 10 - > > > > > > STAR TREK > > > nav STRING [Chekov]This option names the ship's navigator, who is > responsible for the navigation of the ship. This officer > makes changes to the ship's course as directed by the cap- > tain. This officer also controls any anti-matter probes > after they have been launched. > > com STRING [Uhura]This option names the ship's communications > officer. It is the duty of this officer to handle all com- > munications between the ship and the rest of the universe. > > ships STRINGThis option, if set, tells the program how many ships > you wish to fight. If it is not set, then the program will > ask. > > enemy STRING [random]If this option is set, it tells the program > which race you wish to fight. The available races are: > Klingon, Romulan, Kzinti, Gorn, Orion, Hydran, Lyran, or > Tholian. If the option is not set, the race you will fight > is chosen at random. > > foename STRING [random]If this option is set, it specifies the > name of the commander of the enemy ship(s). If this option > is not specified, the name is chosen at random. > > silly BOOLEAN [nosilly]If this option is set, an additional race > is added to the list of possible races to fight. This race > is the Monty Pythons. Note that if you wish to always fight > the Monty Python's, you merely have to set the enemy option > above. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - 11 - > > > > > > STAR TREK > > > Simple Strategy > > If you are a beginner, a simple strategy to follow is A: > fight only one attacker; B: pursue him (code 14) at warp factor > one; C: lock on all phasers (code 3); D: continuously take posi- > tion reports (code 12) and watch his range; E: when he gets > within 1000M, fire all phasers (code 1) and keep on firing when > he is in range; F: When the enemy is out of range, take damage > reports and scans of the enemy (codes 17 and 18). > > After a few trial games using the above strategy, you will > want to become as efficient as the enemy at firing photon tor- > pedos. Finally, when you master launching antimatter probes, you > can designate more that one attacker. > > > > Trek73's History > > Trek73 was programmed on a Hewlett-Packard 2000C system by > William K. Char, Perry Lee, and Dan Gee. In January, 1973, Mr. > Char started with a few ideas and five months later, in May, > introduced $SPACE, his first version. > > Space had only 14 commands and comprised one 10K program. > Response was so great that new ideas flooded in and in June, work > on Trek73 was begun. Over 70 recordings of past shows were > reviewed to reconstruct dialogue and vessels. On October 8, > 1973, Trek73 was introduced. > > In 1984, Dave Pare at Univeristy of California at San Diego > and Chris Williams at the University of California at Berkeley > independently translated the BASIC code into C to run under BSD > UNIX. > > In April 1985, Jeff Okamoto and Peter Yee, both at the > University of California at Berkeley combined the two versions > into one, fixing bugs and adding new commands. The user-settable > options were also added. > > Ideas and bug reports should be sent to: > ARPA: okamoto@BERKELEY and yee@BERKELEY > UUCP: ..!ucbvax!okamoto and ..!ucbvax!yee > > > > > > > > > __________________________ > UNIX is a registered trademark of Bell Laboratories. > > > > > - 12 - > > > > > > STAR TREK > > > APPENDIX 1 > > > > > Secondary Hull Primary Hull > (engineering) > ------- > :-----------------------------------------\ | .5 | . . . . > :: N C C - 1 7 0 1 |} |0 / 1|---< . . . . . > ::________________________________________/ | | . . . . > warp engines ^ | .5 | . . . . > +++ |0 / 1|---< . . . . . > ===== | fuel | | . . . . > |+| + OOOOO reserve | .5 | . . . . > |+| ---------> +++ ---> OOOOO --- +++ ---> |0 / 1|---< . . . . . > ------- + ***** | | . . . . > | | ***** shield | .5 | . . . . > ------- | \ control |0 / 1|---< . . . . . > dilithium * \ ------- . . . . > crystal *** +++ shields > generator * \phaser control > | -------- : : : > | |-10/10|-OOOO>. . : : : | : : > <***: <[=====| <---+ |-10/10|-**OO>. . : : : : > probe launcher | |-10/10|-****> > V |-10/10|-****> > =*******= -------- phaser banks > photon =*****=== > torpedo =**====== > tubes =======****** > ========= ******* > ========= ******** > + Energy unit > O Matter-anti-matter pod > * Filled matter-anti-matter pod > ---+++---> Energy transfer > ---***---> Pod transfer > > > > > > > > > > > > > > > > > > > > - 13 - > > > > > > STAR TREK > > > APPENDIX 2 > > > > > > > > Shield 2 > | > 135 90 > \\,,,,,,,,''-``,,,,,,,, > ,,''\ .Phaser.Firing An``,, 45 > ,' \ \125 gles`,/ > ,' \. . Torpedo. . `, > :------------------------\ \135_-----_ Fir . , > :________________________/ _- 1 -_ ing . ` > | || / 0 \ Angles . | > Shield | ,_^^_____/| _ 7 | . . | Shield > -180| [ { (o) 1 } . . |0- > 3 | `-vv-----\| - C | . . | 1 > | || \ C / . . | > :-----------------------\ -_ N _- . . , > :_______________________/ -_____- . . ' > `, /225. . . . . . . ,' > `, / . ,' \ > ``,/ /235. . . . . . . . ,,'' 315 > /`````````,,_,,'''''''' > 225 270 > | > Shield 4 > > > > > > > > > > > > > > > > > > > > > > > > > > > - 14 - > > > > > > STAR TREK > > > APPENDIX 3 > Weapon And Vessel Specifications > Enemy exceptions are enclosed within [brackets] > > > Phasers > Number of banks 4 > Max range 1000 megameters > Max spread 90 degrees (45+45) > Min spread 20 degrees (10+10) > Max hit with 45 degree spread 10 > Max hit with 10 degree spread 45 > Loss of shield 1 per hit hit/4.5 > Loss of shields 2-3-4 per hit hit/3 > Firing angles with engineering 0-125, 235-360 degrees > Max charge per bank 10 units > Min charge or discharge time 1 sec > > Tubes > Number of tubes 6 > Max range 12,000 megameters > max launch speed warp 12 > Max time delay 10 seconds > Max proximity delay 500M > Max explosion radius 500M > Max number of pods launched 10 > Max hit factor 50 > Loss of shield 1 per hit hit/3 > Loss of shields 2-3-4 per hit hit/2 > Firing angles with engineering 0-135, 225-360 degrees > > Probes > Number of probe launchers 1 > Max range 3000M > Max launch speed 2 > Max time delay 15 sec > Max proximity delay any > Max explosion radius 50 times number of pods > Max pods launched fuel available > Max hit factor 10 times number of pods > Loss of shields per hit same as torpedos > Firing angles with engineering all > > Vessels > Max turning rate 50 degrees > Max speed warp 99 [11] > Min units burned per warp-second 1 [.75] > Crew 450 d[350] > > APPENDIX 4 > > > Initial Settings > > > > > - 15 - > > > > > > STAR TREK > > > Enemy exceptions are enclosed within [brackets] > > > Crew 450 [350] > Speed 1000 megameters > Course 0 [0-360] degrees > Engine Efficiency 1 [.75] > Fuel Level 150 > Fuel Capacity 200 > Regeneration Rate per Second 10 > Helm Lock None [Federation Vessel] > Phaser Deployment 90, 0, 0, 270 > Phaser Bank Levels 4 x 10 units > Phaser Charge/Discharge Rates 4 x 10 units > Shield Drain 4 x 1 units > Shield Percentage 4 x 100 > Torpedo Deployment 120, 60, 0, 0, 300, 240 > Tube Levels 6 x Zero > Total Charged Pods Available 190 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - 16 - > > > > > 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 Oct 23 21: 7:57 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 A31A5150B1 for ; Sat, 23 Oct 1999 21:07:38 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA58662; Sat, 23 Oct 1999 21:07:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: trek73 In-reply-to: Your message of "Sat, 23 Oct 1999 20:53:43 PDT." <199910240353.UAA12397@apollo.backplane.com> Date: Sat, 23 Oct 1999 21:07:19 -0700 Message-ID: <58658.940738039@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't think any of the authors would mind if it went into /usr/games, I certainly wouldn't. It would be an old game returning home to the Berkeley world, and I also used to play it a lot on the HP-2000. The 'ol HP 2000 access, now that brings back memories... Did you know I once wrote an entire multi-user BBS (emeryville's HP-BBS) in HP basic? But I digress.. :) - Jordan > but tracking them down is close to impossible since ucbvax no longer > exists. If nobody knows different, I would like to clean it up (fairly > easy since it's already in C) and commit it in. > > I've included the docs below. > > -Matt > > > > > Originally written (in HP-2000 BASIC) by > William K. Char, Perry Lee, and Dan Gee > > Rewritten in C by > Dave Pare (sdcsvax!sdamos!mr-frog) > and > Christopher Williams (ucbvax!ucbmerlin!williams) > > Corrected, Completed, and Enhanced by > Jeff Okamoto (ucbvax!okamoto) > Peter Yee (ucbvax!yee) > Matt Dillon (ucbvax!dillon) > Dave Sharnoff (ucbvax!ucbcory!muir) > and > Joel Duisman (ucbvax!duisman) > > > T R E K 7 3 > A Star Trek(R) Battle Simulation > > Trek73 is a computer-simulated battle based on the famous > Star Trek television series and the game Star Fleet Battles. Via > computer terminal, you can clash with enemy battle cruisers, such > as Klingon D-7's and Romulan Sparrowhawks, and use the same stra- > tegies that Captain Kirk has used. Like Kirk, you control a > Federation vessel similar to the Enterprise; a computer program > directs the enemy. Victory can fall into several categories: > > Decisive Victory -- You completely destroy or cripple the > attacking force. > > Tactical Victory -- You out-maneuver the enemy using high- > speed escapes, corbomite bluffs, `play dead' tactics; or the > enemy surrenders. > > Moral Victory -- You surrender or self-destruct and destroy > each other. > > All distances are measured in megameters, one million meters > (abbreviated `M'). Speed is expressed in `warp factors'. Each > warp factor equals 100M per second. All angles are expressed in > common degrees from zero to 360, measured counter-clockwise from > the x-axis, similar to reading a protractor. Only two dimensions > are used. > > Play is as follows: > > 1. You issue one of a number of commands (fire phasers, > change course, launch antimatter pods, surrender, etc.) by typing > the appropriate code number into the keyboard; > > 2. The enemy, under programmed instructions, issues a simi- > lar command; > > 3. Both your commands are executed (phasers are fired, > probes are launched, damages are assessed, courses changed, etc.) > while the vessels move through space; > > 4. Unless certain end-game conditions are met (you destroy > the enemy, the enemy destroys you, your out-maneuver the enemy, > you both destroy each other, or one party surrenders) the above > steps are repeated. > > __________________________ > Star Trek is a registered trademark of Paramount > Pictures. > Although technically incorrect, it does save the player > from having to compute cube roots. > This saves the player from having to work out problems > in spherical geometry. > > > > > - 1 - > > > > > > STAR TREK > > > Appendix 1 displays certain weapon and shield angles. > > Appendix 2 depicts the Enterprise's power circuits. > > Appendix 3 lists certain weapon and vessel specifications. > > Appendix 4 lists initial deployment of resources. > > > CODE COMMAND > ==== ======= > > 1 Fire Phasers > 2 Fire Photon Torpedos > 3 Lock Phasers Onto Target > 4 Lock Tubes Onto Target > 5 Manually Rotate Phasers > 6 Manually Rotate Tubes > 7 *Phaser Status > 8 *Tube Status > 9 Load/Unload Torpedo Tubes > 10 Launch Antimatter Probe > > 11 Probe Control (Detonate, Direct, Lock) > 12 *Position Report > 13 *Position Display > 14 Pursue An Enemy Vessel > 15 Run From An Enemy Vessel > 16 Manually Change Course And Speed > 17 *Damage Report > 18 Scan Enemy (Damage Report Of Enemy) > 19 Alter Power Distribution > 20 Alter Torpedo And Phaser Firing Parameters > > 21 Jettison Engineering > 22 Detonate Engineering > 23 Attempt Defenseless Ruse > 24 Attempt Corbomite Bluff(s) > 25 Surrender > 26 Ask Enemy to Surrender > 27 Initiate Self-Destruct Sequence > 28 Abort Self-Destruct > 29 Survivors Report > 30 *Reprints Above List > > *Does Not Use A Turn > > > > > > > > > > > > - 2 - > > > > > > STAR TREK > > > Detailed Descriptions of Each Command > > What follows is a detailed description of each command. > Each command is referred to by a number from 1 to 30. After the > name of the command is given, a synopsis of the arguments the > command requires is given, if any. These arguments can be > entered on the command line, separated by a space, if you wish. > For instance, to fire phasers 1 through 4 with a spread of 15, > you could type '1 1234 15' on the command line. > > 1. Fire Phasers. > [Phasers] [Spread] > Phasers are pure energy units which emit a beam similar to > lasers, but of a pulsating nature which can be `phased' to inter- > fere with the wave pattern of any molecular form. Phasers get > their power from phaser banks, which in turn, derive their power > from the ship's engines. Each phaser bank is capable of holding > a charge of 10 units. When firing, these banks discharge, simi- > lar to batteries, to spread their destructive power through > space. After discharging, these banks are then recharged by the > engines. Each phaser can be set to automatically track a target > or can be manually rotated. Unless engineering is jettisoned > (code 21), phasers only fire from 0-125 and 235-360 degrees, > relative to the ship's course. In other words, each vessel has a > 110 degree blind side in back of it in which phasers cannot fire. > If phasers fired into this blind side, they would destroy the > ship's engineering section. > > The Captain also designates a wide or narrow phaser beam: a > wide beam to disrupt many targets; a narrow beam to inflict max- > imum damage on a single target. The maximum spread of phasers is > 45 degrees, the minimum is 10 degrees. The total beam width is > twice the designated spread. > > The firing percentage of each bank is preset to 100. In > other words, the bank fully discharges when firing. This can be > changed, however, using code 22. > > The maximum range of phasers is 1000M; the maximum hit fac- > tor is 45 with a ten degree spread, 10 with a forty-five degree > spread. Phaser hit factors are calculated by the following for- > mula: > > hit = (bankunits)(firing%)sqrt(1-range/1000)(45/spread) > > Phasers fire in .2-second intervals starting with bank one. > Phasers inflict heavy damage and casualties, but do not destroy > shields as much as antimatter explosions do. > > A phaser is unable to fire if damaged, if firing into your > blind side, or if completely discharged. > > 2. Fire Photon Torpedos. > [Tubes] > > > > - 3 - > > > > > > STAR TREK > > > The Enterprise is equipped with six torpedo tubes, which, as > phasers, can be set to automatically track a target or be manu- > ally rotated. Unless engineering is jettisoned, tubes only fire > from 0-135 and 225-360 degrees. Each tube fires all its > antimatter pods, which are temporarily held suspended in a > magno-photon force field. Photon torpedos can be fired directly > at an enemy, laid out as a mine field, or scattered in an > attacker's path as depth charges. > > Tubes must be loaded (code 9) prior to firing. Each tube > will be automatically loaded with 10 units or whatever remains in > the engines, whichever is less. Normally, torpedos are launched > at warp 12 in .2-second intervals, beginning with tube one. Pho- > ton torpedos have a proximity fuse of 200M. All of these values > can be changed by using code 22. > > Torpedos must be launched with care since the antimatter > pods which are fired can never be recovered. It is suggested > that you not fire more than four torpedos at any one time, since > a certain number of them do miss, or are destroyed by the enemy > firing phasers at them. It is also suggested that you fire them > at distant targets, beyond 1100M, to avoid the explosion radii of your own weapons. Hit factors resulting from antimatter explo- > sions are calculated as follows: > > hit = 5(#podscontained)sqrt(1-range/(55(#podscontained))) > > The maximum hit factor of an antimatter device is five times > the number of pods contained (in the case of torpedos, 50); its > explosion radius is 50 time the number of pods contained (in the > case of torpedos, 500). Antimatter explosions heavily weaken > shields but do not damage equipment as much as phasers do. This > formula also applies to vessels, engineering sections, and > antimatter probe explosions. > > Tubes are unable to fire if damaged, if firing into your > blind side, or if unloaded. > > 3. Lock Phasers. > [Phasers] [Target Name] > Phasers locked on an enemy vessel will automatically aim > towards it. Although phasers may track a vessel which is in the > firing blind side, they will not fire unless engineering is jet- > tisoned. To fire at vessels behind, simply change course at > least 50 degrees. Once a phaser is locked, it is not disengaged > until the target is destroyed (in which case it is then rotated > to zero degrees relative), relocked, manually over-ridden, or > damaged. > > 4. Lock Tubes. > [Tubes] [Target Name] > Tubes lock and unlock in the same manner that phasers do. > > 5. Manually Rotate Phasers. > > > > - 4 - > > > > > > STAR TREK > > > [Phasers] [Bearing] > Manually rotating phasers disengages any previous locks and > positions them as directed, relative to your course. For exam- > ple, if your course is 30, and phasers are rotated 45 degrees, > they will hit a target bearing 75 degrees. Rotating phasers into > you blind side is permissible, however, they will not fire. > > 6. Manually Rotate Tubes. > [Tubes] [Bearing] > Manually rotating tubes is similar to rotating phasers. > > 7. Phaser Status. > Phaser status reports the control (locks and damages), > deployment, levels, firing percentages (normally 100), and > charge/discharge rates (normally +10) of all phasers. > > 8. Tube Status. > Tube status reports the control, deployment, tube levels, > launch speeds (normally 12), proximity delays (normally 200), and > the time delays (normally 10). > > 9. Load/Unload Tubes. > [l | u] [Tubes] > Tubes are loaded with 10 charged antimatter pods until your > fuel runs out. Tubes can also be unloaded if the need arises. > > 10. Launch Antimatter Probe. > [Pods] [Time] [Proximity] [Target | [ Course]] > Probes are slow-moving devices equipped with internal gui- > dance systems which allow them to chase an enemy vessel. Probes > consist of at least ten antimatter pods which are launched from > an undamaged probe launcher at warp three. As with torpedos, > probes are set with time and proximity fuses, and use the same > hit factor formula as do torpedos. > > 11. Probe Control. > [y | [n [Probe] [y | [n [Target | [ Course]]]]]] > Probe control allows you to detonate or redirect probes > which may have missed. > > 12. Position Report. > Position reports are vital since valuable information on > courses, bearings and ranges are given to aid the formation of > good strategy. This order does not use a turn. > > 13. Position Display. > [Radius of scan] > Position displays, similar to radar scans, show objects > which surround your vessel. The Enterprise is indicated by a > `+', jettisoned engineering sections by a `#', probes by a `*', > torpedos by a `:', and enemy vessels by the first letter of their > names. > > 14. Pursue An Enemy Vessel. > > > > - 5 - > > > > > > STAR TREK > > > [Target Name] [Warp Factor] > This order instructs the ship's navigation to face an enemy > vessel whenever possible. > > 15. Run From An Enemy Vessel. > [Target Name] [Warp Factor] > This order, just the opposite of order #14, instructs the > navigation to keep the stern of the Enterprise towards an enemy > vessel whenever possible. > > 16. Manually Change Course and Speed. > [Course] [Warp Factor] > This order instructs navigation to maintain a fixed course > and speed. The following information applies to the above three > orders: > > Your maximum rotation rate when turning is: > degrees per sec = 5 * (12 - desired warp) > > Accordingly, you can turn 55 degrees at warp one, 50 at warp > two, ..., up to 15 degrees at warp nine. In other words, the > faster your speed, the less maneuverable you are. You are also > less maneuverable if you lose your warp drive. Your maximum > speed is warp nine, the enemy's is warp eleven. > > 17. Damage Report. > This report informs you of certain equipment status. A mal- > functioning computer (very rare) make orders 3 (lock phasers), 4 > (lock torpedos), 14 (pursue), 15 (run), 27 (initiate self- > destruct), and 28 (abort self-destruct) impossible to execute. > You will be required to manually rotate phasers and torpedos, and > manually change course and speed. Damaged sensors (rare) makes > orders 13 (position report) and 18 (scan) impossible. A damaged > probe launcher (sometimes) prevents you from launching probes. A > disabled warp drive (common) slows your speed and maneuverabil- > ity. See order #20 about jettisoned engineering section. When > your crew of 450 dies, your vessel is as good as dead. There are > 350 men aboard each enemy vessel. > > Shield percentage is calculated by its energy drain times > its operating efficiency. Efficiency starts at 100 and declines > with each hit. No damages of any kind are incurred when a shield > absorbs its first hit, no matter how great the hit. Shield one > is 1.5 times as strong as the other three shields. > > `Efficiency' indicates the number of energy units being > burned per warp-second. This number is initially one (.75 for > enemy) and increases per hit. > > `Regeneration' indicates the number of energy units being > gained per second. Initially set at 10, this number decreases > per hit. > > `Fuel capacity' indicates the number of matter-antimatter > > > > - 6 - > > > > > > STAR TREK > > > pods a vessel has aboard. This number rapidly decreases with > each torpedo or probe fired. > > `Fuel' indicates the number of matter-antimatter pods which > are filled with energy. This number rapidly decreases when main- > taining high warp speeds or firing phasers. > > 18. Scan Enemy (Damage Report of Enemy). > [Ship Name] > An enemy damage report is essentially the same as the > Enterprise's. > > 19. Alter Power Distribution. > [Shld 1 drain [* | ... Sh 4]] [Phsr 1 drain [* | ... Ph 4]] > The synopsis of this command can be confusing. The first > set of numbers gives the drains for each shield. All four shield > drains can be specified, but if a star is used immediately after > a shield drain (eg, 19 0.5 1*), then the remaining shields will > all be given a drain equal to the number preceding the '*'. > (Thus, in the above example, shield 1's drain is 0.5, whereas > shields 2, 3, and 4 have a drain of 1). The same applies to the > phaser drains. > > The power circuits of all vessels are illustrated in appen- > dix 2. Dilithium crystals produce energy much like generators. > This power is then used to maintain warp speeds, recharge > antimatter pods in the engine reserve, recharge phaser banks, or > maintain shield power. Your initial regeneration is ten, how- > ever, shields normally drain four units and engines burn one unit > per each warp-second. > > Shields can be thought of as electro-magnets. The more > energy put into them, the stringer their force field becomes. > Therefore, a shield's overall percentage is calculated by the > following formula: > > shield percentage = (energy in)(effective %) > > Notice that dropping power to a shield has the same effect > as having it hit. Notice also that if your regeneration drops > below four, you may have to discharge your phaser banks to main- > tain full shield power. > > Phaser banks, similar to batteries, not only discharge (when > firing), but also recharge. Initially, they are set to recharge > fully in one second (+10) so that you can continually use them. > However, they can discharge fully (-10) in one second to provide > extra power to shields, warp engines, or engine reserve. > > Under most conditions, you need not concern yourself with > power distribution unless some special need arises. Distribu- > tion, for the most part, is automatic. Regeneration is calcu- > lated first; that power is placed in reserve, along with any > discharged phaser units. Shield drain is calculated next, then > > > > - 7 - > > > > > > STAR TREK > > > phaser and engine drains. > > Be concerned with wasting power by indiscriminately firing > phasers and torpedos, maintaining speeds over warp three, or > dumping scores of units onto antimatter probes. Huge power > losses cannot be made up in battle. > > 20. Jettison Engineering. > Although this order was never executed in the television > series, it is quite possible, according to its producer. Jettis- > oning engineering has serious consequences, but it may be your > only course of action. > > One would jettison engineering if being pursed by vessels, > probes or torpedos, or as a suicidal gesture. > > The following things happen when engineering is jettisoned: > A: You lose all your fuel and reserve capacity; B: you lose your > regeneration; C: you lose your warp drive; D: your lose your > probe launcher; E: you lose your shields until you designate > phasers to discharge; F: the engineering section itself > decelerates to a stop; G: a ten second time delay on it is set; > H: hopefully, when it does explode, you are far from its effects; > I: your phasers and torpedos are now free to fire in any direc- > tion. > > 21. Detonate Engineering. > [nothing | [y | n]] > This order, issued after the previous one, manually > detonates your engineering section. It may also be issued > without the previous order, in which case you will be asked to > confirm your (crazy) order. > > 22. Alter Torpedo And Phaser Firing Parameters. > [[y [Launch Speed] [Time Delay] [Proximity Fuse]] | n] [[y > [Firing Percentage]] | n] > This option allows you to change the launch speeds, time and > proximity delays of all torpedos. At the beginning of play, tor- > pedos are launched at warp twelve, have ten second time fuses, > and 200M proximity fuses. Any vessel or engineering section > which comes within the proximity range will cause the torpedo to > explode. > > Phaser firing percentages can also be altered. A phaser > bank need not fire its full charge. > > 23. Defenseless Ruse. > [e | p] > Another name for this tactic is `playing dead'. When > issued, your shields are dropped to zero, and power is diverted > to your engines or phaser banks. Hopefully, the enemy will > believe you dead and come too close or break off their attack. > You should then be able to fire or run in the opposite direction. > > > > > - 8 - > > > > > > STAR TREK > > > 24. Attempt Corbomite Bluff(s). There were two corbomite bluffs > in the television series; one was against a midget operating a > huge space vessel the other was against Romulan attackers. Both > have been incorporated into this game. Whichever bluff issued is > selected randomly. > > 25. Surrender, If Possible. > This order sends a message to the enemy, saying that you > wish to surrender. The enemy will then decide whether or not > take you alive. You will have difficulty surrendering to Romu- > lans, who have never accepted one. > > 26. Ask Enemy To Surrender. > This order ends a message to the enemy demanding that they > surrender. Please bear in mind that Romulans are the most suici- > dal. > > 27. Initiate Self-Destruct. > This order activates a twenty-second self-destruct sequence. > Because final destruct does not occur until ten turns after ini- > tialization, it is best to start it early, if at all. When you > do explode, you hope that you explosive force will also destroy > your attackers. > > 28. Abort Self-Destruct. > This order, issued after the previous one, halts the des- > truct sequence. Self-destruct cannot be aborted withing five > seconds to detonation. > > 29. Survivors Report > This order prints out the number of survivors on board all > the ships. This order does not use a turn. > > 30. Reprint Above List. > This option, which does not use a turn, lists code numbers > and associated descriptions of each. > > 31 And Up. > Future options, currently being designed in Trek74, will > include Dr. Daystrom's paranoid, M5 multi-tronics computer which > will take over while you relax; or battle someone else who is on > another terminal; or battle in teams; or have a free-for-all > against nine other starships. > > > > > > > > > > > > > > > - 9 - > > > > > > STAR TREK > > > Options > > In TREK73, all the names are taken from the series Star > Trek. Through the use of options, the names can be changed to > whatever you want. > > To use the options, you must add the variable TREK73OPTS to > your environment. A sample would be (using the C-shell): > > setenv TREK73OPTS 'name=Jerk, ship=Boobyprize, terse' > > The option string is a list of comma-separated options. > Options are designated as either boolean or string options. > Boolean options are turned on by typing their name and turned off > by prepending 'no' to them. String options are set equal to the > string which follows the "=". > > There follows a list of all the options, what type it is, > and an explanation of what they mean. The default for the option > is in square brackets following the option. > > terse BOOLEAN [noterse]This option, when set, turns off the > information regarding the ship's purpose in the area. It > thus reduces the amount of drek on the screen. If you are > on a slow terminal, this is a nice option to have set. > > shipname STRING [Enterprise]This option names your ship. > > name STRINGThis option names the captain of the ship. If this > option is not set, then the program will ask for a name. > The captain is the one who must make all the decisions of > strategy and tactics for the ship. > > sex STRINGThis option gives the captain a gender. If this option > is not set, the program will ask for it's value. If you > respond with something that starts with other than "m" or > "f", beware! > > science STRING [Spock]This option names the science officer, who > is responsible for checking the parameters of the captain's > commands. It is also this officer's duty to report damage > to the ship as well as scan for enemy damage. > > engineer STRING [Scott]This option names the chief engineer of > the ship. It is this officer's duty to report on the status > of the ship, especially its energy supply and distribution > of the same. The officer also controls the launching of > anti-matter probes. > > helmsman STRING [Sulu]This option names the ship's helmsman. > This officer's duty is to control the speed of the ship and > also controls the firing of the ship's weapons. > > > > > > - 10 - > > > > > > STAR TREK > > > nav STRING [Chekov]This option names the ship's navigator, who is > responsible for the navigation of the ship. This officer > makes changes to the ship's course as directed by the cap- > tain. This officer also controls any anti-matter probes > after they have been launched. > > com STRING [Uhura]This option names the ship's communications > officer. It is the duty of this officer to handle all com- > munications between the ship and the rest of the universe. > > ships STRINGThis option, if set, tells the program how many ships > you wish to fight. If it is not set, then the program will > ask. > > enemy STRING [random]If this option is set, it tells the program > which race you wish to fight. The available races are: > Klingon, Romulan, Kzinti, Gorn, Orion, Hydran, Lyran, or > Tholian. If the option is not set, the race you will fight > is chosen at random. > > foename STRING [random]If this option is set, it specifies the > name of the commander of the enemy ship(s). If this option > is not specified, the name is chosen at random. > > silly BOOLEAN [nosilly]If this option is set, an additional race > is added to the list of possible races to fight. This race > is the Monty Pythons. Note that if you wish to always fight > the Monty Python's, you merely have to set the enemy option > above. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - 11 - > > > > > > STAR TREK > > > Simple Strategy > > If you are a beginner, a simple strategy to follow is A: > fight only one attacker; B: pursue him (code 14) at warp factor > one; C: lock on all phasers (code 3); D: continuously take posi- > tion reports (code 12) and watch his range; E: when he gets > within 1000M, fire all phasers (code 1) and keep on firing when > he is in range; F: When the enemy is out of range, take damage > reports and scans of the enemy (codes 17 and 18). > > After a few trial games using the above strategy, you will > want to become as efficient as the enemy at firing photon tor- > pedos. Finally, when you master launching antimatter probes, you > can designate more that one attacker. > > > > Trek73's History > > Trek73 was programmed on a Hewlett-Packard 2000C system by > William K. Char, Perry Lee, and Dan Gee. In January, 1973, Mr. > Char started with a few ideas and five months later, in May, > introduced $SPACE, his first version. > > Space had only 14 commands and comprised one 10K program. > Response was so great that new ideas flooded in and in June, work > on Trek73 was begun. Over 70 recordings of past shows were > reviewed to reconstruct dialogue and vessels. On October 8, > 1973, Trek73 was introduced. > > In 1984, Dave Pare at Univeristy of California at San Diego > and Chris Williams at the University of California at Berkeley > independently translated the BASIC code into C to run under BSD > UNIX. > > In April 1985, Jeff Okamoto and Peter Yee, both at the > University of California at Berkeley combined the two versions > into one, fixing bugs and adding new commands. The user-settable > options were also added. > > Ideas and bug reports should be sent to: > ARPA: okamoto@BERKELEY and yee@BERKELEY > UUCP: ..!ucbvax!okamoto and ..!ucbvax!yee > > > > > > > > > __________________________ > UNIX is a registered trademark of Bell Laboratories. > > > > > - 12 - > > > > > > STAR TREK > > > APPENDIX 1 > > > > > Secondary Hull Primary Hull > (engineering) > ------- > :-----------------------------------------\ | .5 | . . . . > :: N C C - 1 7 0 1 |} |0 / 1|---< . . . . . > ::________________________________________/ | | . . . . > warp engines ^ | .5 | . . . . > +++ |0 / 1|---< . . . . . > ===== | fuel | | . . . . > |+| + OOOOO reserve | .5 | . . . . > |+| ---------> +++ ---> OOOOO --- +++ ---> |0 / 1|---< . . . . . > ------- + ***** | | . . . . > | | ***** shield | .5 | . . . . > ------- | \ control |0 / 1|---< . . . . . > dilithium * \ ------- . . . . > crystal *** +++ shields > generator * \phaser control > | -------- : : : > | |-10/10|-OOOO>. . : : : | : : > <***: <[=====| <---+ |-10/10|-**OO>. . : : : : > probe launcher | |-10/10|-****> > V |-10/10|-****> > =*******= -------- phaser banks > photon =*****=== > torpedo =**====== > tubes =======****** > ========= ******* > ========= ******** > + Energy unit > O Matter-anti-matter pod > * Filled matter-anti-matter pod > ---+++---> Energy transfer > ---***---> Pod transfer > > > > > > > > > > > > > > > > > > > > - 13 - > > > > > > STAR TREK > > > APPENDIX 2 > > > > > > > > Shield 2 > | > 135 90 > \\,,,,,,,,''-``,,,,,,,, > ,,''\ .Phaser.Firing An``,, 45 > ,' \ \125 gles`,/ > ,' \. . Torpedo. . `, > :------------------------\ \135_-----_ Fir . , > :________________________/ _- 1 -_ ing . ` > | || / 0 \ Angles . | > Shield | ,_^^_____/| _ 7 | . . | Shield > -180| [ { (o) 1 } . . |0- > 3 | `-vv-----\| - C | . . | 1 > | || \ C / . . | > :-----------------------\ -_ N _- . . , > :_______________________/ -_____- . . ' > `, /225. . . . . . . ,' > `, / . ,' \ > ``,/ /235. . . . . . . . ,,'' 315 > /`````````,,_,,'''''''' > 225 270 > | > Shield 4 > > > > > > > > > > > > > > > > > > > > > > > > > > > - 14 - > > > > > > STAR TREK > > > APPENDIX 3 > Weapon And Vessel Specifications > Enemy exceptions are enclosed within [brackets] > > > Phasers > Number of banks 4 > Max range 1000 megameters > Max spread 90 degrees (45+45) > Min spread 20 degrees (10+10) > Max hit with 45 degree spread 10 > Max hit with 10 degree spread 45 > Loss of shield 1 per hit hit/4.5 > Loss of shields 2-3-4 per hit hit/3 > Firing angles with engineering 0-125, 235-360 degrees > Max charge per bank 10 units > Min charge or discharge time 1 sec > > Tubes > Number of tubes 6 > Max range 12,000 megameters > max launch speed warp 12 > Max time delay 10 seconds > Max proximity delay 500M > Max explosion radius 500M > Max number of pods launched 10 > Max hit factor 50 > Loss of shield 1 per hit hit/3 > Loss of shields 2-3-4 per hit hit/2 > Firing angles with engineering 0-135, 225-360 degrees > > Probes > Number of probe launchers 1 > Max range 3000M > Max launch speed 2 > Max time delay 15 sec > Max proximity delay any > Max explosion radius 50 times number of pods > Max pods launched fuel available > Max hit factor 10 times number of pods > Loss of shields per hit same as torpedos > Firing angles with engineering all > > Vessels > Max turning rate 50 degrees > Max speed warp 99 [11] > Min units burned per warp-second 1 [.75] > Crew 450 d[350] > > APPENDIX 4 > > > Initial Settings > > > > > - 15 - > > > > > > STAR TREK > > > Enemy exceptions are enclosed within [brackets] > > > Crew 450 [350] > Speed 1000 megameters > Course 0 [0-360] degrees > Engine Efficiency 1 [.75] > Fuel Level 150 > Fuel Capacity 200 > Regeneration Rate per Second 10 > Helm Lock None [Federation Vessel] > Phaser Deployment 90, 0, 0, 270 > Phaser Bank Levels 4 x 10 units > Phaser Charge/Discharge Rates 4 x 10 units > Shield Drain 4 x 1 units > Shield Percentage 4 x 100 > Torpedo Deployment 120, 60, 0, 0, 300, 240 > Tube Levels 6 x Zero > Total Charged Pods Available 190 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - 16 - > > > > > 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 Oct 23 21: 9:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 02C071507D for ; Sat, 23 Oct 1999 21:09:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA12515; Sat, 23 Oct 1999 21:09:52 -0700 (PDT) (envelope-from dillon) Date: Sat, 23 Oct 1999 21:09:52 -0700 (PDT) From: Matthew Dillon Message-Id: <199910240409.VAA12515@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Subject: Re: trek73 References: <58658.940738039@localhost> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> I don't think any of the authors would mind if it went into /usr/games, : :I certainly wouldn't. It would be an old game returning home to the :Berkeley world, and I also used to play it a lot on the HP-2000. : :The 'ol HP 2000 access, now that brings back memories... Did you know :I once wrote an entire multi-user BBS (emeryville's HP-BBS) in HP :basic? But I digress.. :) : :- Jordan Heh, I think I heard about that BBS but the only HP 2000 I ever used was the one Berkeley High had. Oh, and LHS had one too - though that might have been a higher powered model. I guess the real question is: /usr/games or /usr/ports? I don't care which, but I would personally prefer /usr/games because it really is an old-time berkeley program. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 21:23:26 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 0341014C14 for ; Sat, 23 Oct 1999 21:23:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA58797; Sat, 23 Oct 1999 21:23:11 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: trek73 In-reply-to: Your message of "Sat, 23 Oct 1999 21:09:52 PDT." <199910240409.VAA12515@apollo.backplane.com> Date: Sat, 23 Oct 1999 21:23:11 -0700 Message-ID: <58793.940738991@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I guess the real question is: /usr/games or /usr/ports? I don't care > which, but I would personally prefer /usr/games because it really is > an old-time berkeley program. Perhaps we should ask Kirk... ;) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 21:25: 1 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 D3AB514C14 for ; Sat, 23 Oct 1999 21:24:05 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id AAA88190; Sun, 24 Oct 1999 00:18:07 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Sun, 24 Oct 1999 00:17:12 -0400 (EDT) From: Chuck Robey To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: trek73 In-Reply-To: <199910240353.UAA12397@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 On Sat, 23 Oct 1999, Matthew Dillon wrote: > I found a copy of the C version of trek73 in my Amiga archives. This > is the trek73 originally written in HP-2000 Basic that was rewritten > by Dave Pare and Chris Williams in C and seriously enhanced by a bunch > of people including me in my early college years circa 1985. > > I don't think any of the authors would mind if it went into /usr/games, > but tracking them down is close to impossible since ucbvax no longer > exists. If nobody knows different, I would like to clean it up (fairly > easy since it's already in C) and commit it in. > > I've included the docs below. Remembering from ancient history, didn't this make the rounds to just about anyone who wanted to learn code? I think it was even in a DEC games book. I think putting this into games is safe, but there's another trek in games already ... I haven't played trek in a looong time, is this one better in some way than the one already there? If it doesn't get into /usr/games, anyhow, it can certainly go into ports. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 22: 2: 2 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 BAD6914C09 for ; Sat, 23 Oct 1999 22:02: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 VAA09641; Sat, 23 Oct 1999 21:53:44 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910240453.VAA09641@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: trek73 In-reply-to: Your message of "Sat, 23 Oct 1999 21:23:11 PDT." <58793.940738991@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 23 Oct 1999 21:53:43 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I guess the real question is: /usr/games or /usr/ports? I don't care > > which, but I would personally prefer /usr/games because it really is > > an old-time berkeley program. > > Perhaps we should ask Kirk... ;) No. Make it a port. Policy, remember? 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 22: 4:39 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 68B8B14C94 for ; Sat, 23 Oct 1999 22:04:37 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00592; Sat, 23 Oct 1999 22:04:29 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Mike Smith Cc: "Jordan K. Hubbard" , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: trek73 In-reply-to: Your message of "Sat, 23 Oct 1999 21:53:43 PDT." <199910240453.VAA09641@dingo.cdrom.com> Date: Sat, 23 Oct 1999 22:04:29 -0700 Message-ID: <588.940741469@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No. Make it a port. Policy, remember? 8) I guess the anti-bloatists would have a point on this one... I would not object to a port. It certainly eliminates the bike shed arguments over it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 22: 9:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 3CD9014C94 for ; Sat, 23 Oct 1999 22:09:28 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id WAA15378; Sat, 23 Oct 1999 22:08:16 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199910240508.WAA15378@gndrsh.dnsmgr.net> Subject: Re: trek73 In-Reply-To: <588.940741469@localhost> from "Jordan K. Hubbard" at "Oct 23, 1999 10:04:29 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sat, 23 Oct 1999 22:08:15 -0700 (PDT) Cc: mike@smith.net.au (Mike Smith), dillon@apollo.backplane.com (Matthew Dillon), 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 > > No. Make it a port. Policy, remember? 8) > > I guess the anti-bloatists would have a point on this one... > > I would not object to a port. It certainly eliminates the > bike shed arguments over it. Did anyone bother to look at /usr/src/games/trek/main.c: ** C version by Eric P. Allman 5/76 (U.C. Berkeley) with help ** from Jeff Poskanzer and Pete Rubinstein. ** ... This is the original UCB BSD version of trek as has been shipping since the BSD 2.x days.... -- 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 Sat Oct 23 22:14:21 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 7A1EC14C94 for ; Sat, 23 Oct 1999 22:14:19 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00660; Sat, 23 Oct 1999 22:14:04 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Rodney W. Grimes" Cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), mike@smith.net.au (Mike Smith), dillon@apollo.backplane.com (Matthew Dillon), freebsd-current@FreeBSD.ORG Subject: Re: trek73 In-reply-to: Your message of "Sat, 23 Oct 1999 22:08:15 PDT." <199910240508.WAA15378@gndrsh.dnsmgr.net> Date: Sat, 23 Oct 1999 22:14:04 -0700 Message-ID: <656.940742044@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Did anyone bother to look at /usr/src/games/trek/main.c: trek != trek73. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 23 23:14:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id 089A014DF6; Sat, 23 Oct 1999 23:14:49 -0700 (PDT) (envelope-from will@shadow.blackdawn.com) Received: from [209.224.140.243] (helo=shadow.blackdawn.com) by neptune.psn.net with esmtp (PSN Internet Service 2.12 #3) id 11fGvW-0002P6-00; Sat, 23 Oct 1999 23:14:48 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id CAA08978; Sun, 24 Oct 1999 02:13:20 -0400 (EDT) (envelope-from will) 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: <199910231802.MAA32825@harmony.village.org> Date: Sun, 24 Oct 1999 02:13:20 -0400 (EDT) Reply-To: Will Andrews From: Will Andrews To: Warner Losh Subject: Re: sio working Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Oct-99 Warner Losh wrote: > In message Will Andrews > writes: >: I will be your guinea pig, if you like. :-) > > Grab the current patches from > http://www.freebsd.org/~imp/pccard-snap.patch > but read my other posting about the warnings and such. As of yet, I haven't tested your code. I will be, in a few. I took the opportunity to go over the patch first. I noticed a little discrepancy in ep_pccard_identify, where the switch() does not offer a default: case. You should put something like that in there and call the card "Unknown 3Com card" or somesuch. Same for ep_pccard_card_attach(). That's all I can manage from a quick skim of your code. Well, I'm gonna test out this kernel patch. (after safely backing up sys/). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message