From owner-freebsd-current Sun Nov 22 00:52:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17434 for freebsd-current-outgoing; Sun, 22 Nov 1998 00:52:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org (dialup3.gaffaneys.com [208.155.161.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17428 for ; Sun, 22 Nov 1998 00:52:00 -0800 (PST) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id IAA00915; Sun, 22 Nov 1998 08:50:54 GMT (envelope-from zach) Message-ID: <19981122025053.A830@znh.org> Date: Sun, 22 Nov 1998 02:50:53 -0600 From: Zach Heilig To: Chan Yiu Wah , freebsd-current@FreeBSD.ORG Subject: Re: how to solve open tagging...64 References: <199811220644.OAA14251@b1.hkstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811220644.OAA14251@b1.hkstar.com>; from Chan Yiu Wah on Sun, Nov 22, 1998 at 02:44:55PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 22, 1998 at 02:44:55PM +0800, Chan Yiu Wah wrote: > Hello, > > I recenlty upgrade my system upto src-cur.3627.gz and found that the > system report open tagging ... 64. Is it harmful to the system and how > to solve it. I do think it had been talking about but I missed it (sorry). You mean a message like this:? (da1:ahc0:0:1:0): tagged openings now 15 [ It's an older quantum disk ] It merely states the number of tagged commands the drive supports. It is one indicator of how good the drive is. 64 is good, 15 (like my disk) is pretty bad. What are tagged commands good for? They allow the operating system to send multiple commands to the device, and let the device send back results as the commands complete (in any order). The only time you might need to be concerned is if you see something like: (da1:ahc0:0:1:0): tagged openings now 64 (da1:ahc0:0:1:0): tagged openings now 63 (da1:ahc0:0:1:0): tagged openings now 62 (da1:ahc0:0:1:0): tagged openings now 61 (da1:ahc0:0:1:0): tagged openings now 60 (da1:ahc0:0:1:0): tagged openings now 59 (da1:ahc0:0:1:0): tagged openings now 58 (da1:ahc0:0:1:0): tagged openings now 57 (da1:ahc0:0:1:0): tagged openings now 56 (da1:ahc0:0:1:0): tagged openings now 55 (da1:ahc0:0:1:0): tagged openings now 54 (da1:ahc0:0:1:0): tagged openings now 53 (da1:ahc0:0:1:0): tagged openings now 52 ... (da1:ahc0:0:1:0): tagged openings now 0 Perhaps this patch to cam_xpt.c might be in order: :-) Index: cam_xpt.c =================================================================== RCS file: /home/ncvs/src/sys/cam/cam_xpt.c,v retrieving revision 1.26 diff -u -r1.26 cam_xpt.c --- cam_xpt.c 1998/11/04 19:56:24 1.26 +++ cam_xpt.c 1998/11/22 08:41:17 @@ -2939,7 +2939,8 @@ if (bootverbose || 1) { xpt_print_path(crs->ccb_h.path); printf("tagged openings " - "now %d\n", + "now %d [ignorable " + "message]\n", crs->openings); } } -- Zach Heilig (zach@gaffaneys.com) Woah! Put me down as absolutely against this position. Put my face on your dart board, if you must! (Stephen McKay) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 01:07:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18533 for freebsd-current-outgoing; Sun, 22 Nov 1998 01:07:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18528; Sun, 22 Nov 1998 01:07:22 -0800 (PST) (envelope-from dmm125@bellatlantic.net) Received: from client201-122-2.bellatlantic.net (client201-122-2.bellatlantic.net [151.201.122.2]) by iconmail.bellatlantic.net (IConNet Sendmail) with ESMTP id EAA06002; Sun, 22 Nov 1998 04:05:23 -0500 (EST) Date: Sun, 22 Nov 1998 04:04:15 +0000 (GMT) From: Donn Miller X-Sender: dmm125@localhost To: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Distortion/RealPlayer 5.0 Message-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, has anyone solved the problem of distortion and bad video playback on FreeBSD-current? Video frames won't play back smooth, sound is distorted/raspy. Maybe some sys/IO calls aren't being made correctly? Also, while I'm at it, can anyone tell me if using cvsup with default release=cvs will be the same as running -current? Thanks Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 02:08:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22846 for freebsd-current-outgoing; Sun, 22 Nov 1998 02:08:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22840 for ; Sun, 22 Nov 1998 02:08:13 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA28878; Sun, 22 Nov 1998 10:09:19 GMT Date: Sun, 22 Nov 1998 10:09:19 +0000 (GMT) From: Doug Rabson To: Amancio Hasty cc: Jake , current@FreeBSD.ORG Subject: Re: kernel make failure in smbus In-Reply-To: <199811220145.RAA03548@rah.star-gate.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, 21 Nov 1998, Amancio Hasty wrote: > > Post on the multimedia mailing list and request a patch to disable smb support > in bktr it should not be difficult to generate since the code > to talk to the I2C interface is still in the driver. > > I isolated the problem to : > /sys/sys/bus.h and the recently commit : > > 1.7 Sat Nov 14 21:58:41 1998 UTC by wollman > > CVS Tags: HEAD > Diffs to 1.6 > > My changes to the new device interface: > > - Interface wth the new resource manager. > - Allow for multiple drivers implementing a single devclass. > - Remove ordering dependencies between header files. > - Style cleanup. > - Add DEVICE_SUSPEND and DEVICE_RESUME methods. > - Move to a single-phase interrupt setup scheme. > > Kernel builds on the Alpha are brken until Doug gets a chance to incorporate > these changes on that side. This patch or something similar to it should fix it. I haven't tested it. Index: smbus.c =================================================================== RCS file: /home/ncvs/src/sys/dev/smbus/smbus.c,v retrieving revision 1.2 diff -u -r1.2 smbus.c --- smbus.c 1998/10/31 11:39:54 1.2 +++ smbus.c 1998/11/22 10:08:20 @@ -81,8 +81,8 @@ DEVMETHOD(bus_print_child, smbus_print_child), DEVMETHOD(bus_read_ivar, smbus_read_ivar), DEVMETHOD(bus_write_ivar, bus_generic_write_ivar), - DEVMETHOD(bus_create_intr, bus_generic_create_intr), - DEVMETHOD(bus_connect_intr, bus_generic_connect_intr), + DEVMETHOD(bus_setup_intr, bus_generic_setup_intr), + DEVMETHOD(bus_teardown_intr, bus_generic_teardown_intr), { 0, 0 } }; -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 02:22:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23552 for freebsd-current-outgoing; Sun, 22 Nov 1998 02:22:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23545 for ; Sun, 22 Nov 1998 02:22:05 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id CAA21971 for ; Sun, 22 Nov 1998 02:23:03 -0800 (PST) To: current@FreeBSD.ORG Subject: Breakage in -current for the ALPHA Date: Sun, 22 Nov 1998 02:23:03 -0800 Message-ID: <21968.911730183@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG gzip -cn /usr/src/usr.sbin/moused/moused.8 > moused.8.gz /usr/src/usr.sbin/moused/moused.c:206: `MOUSE_MODEL_KIDSPAD' undeclared here (not in a function) /usr/src/usr.sbin/moused/moused.c:206: initializer element for `rmodels[7].val' is not constant /usr/src/usr.sbin/moused/moused.c:224: `MOUSE_PROTO_KIDSPAD' undeclared here (not in a function) /usr/src/usr.sbin/moused/moused.c:224: initializer element for `pnpprod[5].val' is not constant /usr/src/usr.sbin/moused/moused.c:224: `MOUSE_MODEL_KIDSPAD' undeclared here (not in a function) /usr/src/usr.sbin/moused/moused.c:224: initializer element for `pnpprod[5].val2' ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 02:56:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25236 for freebsd-current-outgoing; Sun, 22 Nov 1998 02:56:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25229 for ; Sun, 22 Nov 1998 02:56:28 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:dImbVJOwmFiiS6YMi9ZRT3TmZGesE0oI@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id MAA28264; Sun, 22 Nov 1998 12:55:38 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:AuZV4EJYr5mpMO7kMslyuaOphdbywmJm@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id MAA61606; Sun, 22 Nov 1998 12:55:37 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199811221055.MAA61606@greenpeace.grondar.za> To: Doug Rabson cc: Amancio Hasty , Jake , current@FreeBSD.ORG Subject: Re: kernel make failure in smbus In-Reply-To: Your message of " Sun, 22 Nov 1998 10:09:19 GMT." References: Date: Sun, 22 Nov 1998 12:55:36 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > This patch or something similar to it should fix it. I haven't tested it. It fixes the compile. Something similar needs to be done in iicbus.c. I'll yell if it actually works. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 03:39:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00583 for freebsd-current-outgoing; Sun, 22 Nov 1998 03:39:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00578 for ; Sun, 22 Nov 1998 03:39:09 -0800 (PST) (envelope-from regnauld@EU.org) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id MAA16643; Sun, 22 Nov 1998 12:42:34 +0100 (CET) (envelope-from regnauld@EU.org) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id MAA06061; Sun, 22 Nov 1998 12:29:06 +0100 (CET) Received: (from uucp@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) with UUCP id MAA22890; Sun, 22 Nov 1998 12:31:35 +0100 (CET) Received: (from regnauld@localhost) by stimpy.prosa.dk (8.9.1/8.9.1/stimpy-1.0) id SAA04351; Sat, 21 Nov 1998 18:17:21 +0100 (CET) (envelope-from regnauld) Message-ID: <19981121181720.40825@stimpy.prosa.dk> Date: Sat, 21 Nov 1998 18:17:20 +0100 From: Phil Regnauld To: "Roman V. Palagin" Cc: current@FreeBSD.ORG, pb@fasterix.freenix.org Subject: Re: IPv6 and -current References: <19981116224929.52241@stimpy.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Roman V. Palagin on Tue, Nov 17, 1998 at 03:02:12PM +0300 X-Operating-System: FreeBSD 3.0-CURRENT i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roman V. Palagin writes: > > > > Actually the INRIA stuff (from Francis Dupont/INRIA in fact) > > was ported to -current twice by Pierre Beyssac. > > Yes, it was, but it's outdated now. Pierre said he would do another port soon, I think. Pierre ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 04:07:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05398 for freebsd-current-outgoing; Sun, 22 Nov 1998 04:07:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05391 for ; Sun, 22 Nov 1998 04:07:33 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:SFmD715G5RkeCVcXL4xEypOMRBtMWpqB@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id VAA24749; Sun, 22 Nov 1998 21:06:57 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id VAA09068; Sun, 22 Nov 1998 21:08:37 +0900 (JST) Message-Id: <199811221208.VAA09068@zodiac.mech.utsunomiya-u.ac.jp> To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Breakage in -current for the ALPHA In-reply-to: Your message of "Sun, 22 Nov 1998 02:23:03 PST." <21968.911730183@zippy.cdrom.com> References: <21968.911730183@zippy.cdrom.com> Date: Sun, 22 Nov 1998 21:08:36 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >gzip -cn /usr/src/usr.sbin/moused/moused.8 > moused.8.gz >/usr/src/usr.sbin/moused/moused.c:206: `MOUSE_MODEL_KIDSPAD' undeclared here ( >not in a function) >/usr/src/usr.sbin/moused/moused.c:206: initializer element for `rmodels[7].val >' is not constant >/usr/src/usr.sbin/moused/moused.c:224: `MOUSE_PROTO_KIDSPAD' undeclared here ( >not in a function) >/usr/src/usr.sbin/moused/moused.c:224: initializer element for `pnpprod[5].val >' is not constant >/usr/src/usr.sbin/moused/moused.c:224: `MOUSE_MODEL_KIDSPAD' undeclared here ( >not in a function) >/usr/src/usr.sbin/moused/moused.c:224: initializer element for `pnpprod[5].val >2' >... Oops, I must have forgot to update /sys/alpha/include/mouse.h when I updated moused recently. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 05:37:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08684 for freebsd-current-outgoing; Sun, 22 Nov 1998 05:37:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08679 for ; Sun, 22 Nov 1998 05:37:12 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id IAA07410 for freebsd-current@FreeBSD.org; Sun, 22 Nov 1998 08:36:31 -0500 (EST) Date: Sun, 22 Nov 1998 08:36:31 -0500 (EST) From: Daniel Eischen Message-Id: <199811221336.IAA07410@pcnet1.pcnet.com> To: freebsd-current@FreeBSD.ORG Subject: aout-to-elf-build failure in libpam Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From sources updated Saturday, a make aout-to-elf-build fails in: building shared pam library (version 1) ===> libpam/modules ===> libpam/modules/pam_cleartext_pass_ok cc -O2 -pipe -I/opt/b/src/src/lib/libpam/modules/pam_cleartext_pass_ok/../../../../contrib/libpam/libpam/include -fpic -Wall -I/usr/obj/elf/opt/b/src/src/tmp/usr/include -c /opt/b/src/src/lib/libpam/modules/pam_cleartext_pass_ok/pam_cleartext_pass_ok.c cc -O2 -pipe -I/opt/b/src/src/lib/libpam/modules/pam_cleartext_pass_ok/../../../../contrib/libpam/libpam/include -fpic -Wall -I/usr/obj/elf/opt/b/src/src/tmp/usr/include -shared -o pam_cleartext_pass_ok.so pam_cleartext_pass_ok.o -lskey -lgcc_pic /usr/obj/aout/opt/b/src/src/tmp/usr/libexec/elf/ld: cannot open -lskey: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 05:43:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09312 for freebsd-current-outgoing; Sun, 22 Nov 1998 05:43:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09303 for current; Sun, 22 Nov 1998 05:43:33 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199811221343.FAA09303@hub.freebsd.org> Subject: buildworld breakage? YP_SOCKNAME To: current Date: Sun, 22 Nov 1998 05:43:33 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG havent seen any mail on this...anyone else seeing this? cc -O -pipe -I/home/src/usr.bin/chpass/../../usr.sbin/pwd_mkdb -I/home/src/usr.bin/chpass/../../usr.sbin/vipw -DYP -I. -I/home/src/usr.bin/chpass/../../libexec/ypxfr -I/home/src/usr.bin/chpass/../../usr.sbin/rpc.yppasswdd -Dyp_error=warnx -I/usr/obj/elf/home/src/tmp/usr/include -c /home/src/usr.bin/chpass/pw_yp.c /home/src/usr.bin/chpass/pw_yp.c:68: yppasswd_private.h: No such file or directory /home/src/usr.bin/chpass/pw_yp.c: In function `get_yp_master': /home/src/usr.bin/chpass/pw_yp.c:341: `YP_SOCKNAME' undeclared (first use this function) /home/src/usr.bin/chpass/pw_yp.c:341: (Each undeclared identifier is reported only once /home/src/usr.bin/chpass/pw_yp.c:341: for each function it appears in.) /home/src/usr.bin/chpass/pw_yp.c: In function `yp_submit': /home/src/usr.bin/chpass/pw_yp.c:419: storage size of `master_yppasswd' isn't known /home/src/usr.bin/chpass/pw_yp.c:424: `YP_SOCKNAME' undeclared (first use this function) /home/src/usr.bin/chpass/pw_yp.c:477: `MASTER_YPPASSWDPROG' undeclared (first use this function) /home/src/usr.bin/chpass/pw_yp.c:478: `MASTER_YPPASSWDVERS' undeclared (first use this function) /home/src/usr.bin/chpass/pw_yp.c:498: warning: assignment makes pointer from integer without a cast seems that /usr/src/usr.sbin/rpc_yppasswd/yppasswd_private.x is not being processed by rpcgen to create the required .h file. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 06:59:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14021 for freebsd-current-outgoing; Sun, 22 Nov 1998 06:59:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14013 for ; Sun, 22 Nov 1998 06:59:37 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id KAA28910; Sun, 22 Nov 1998 10:01:59 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 22 Nov 1998 10:01:59 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Kazutaka YOKOTA cc: current@FreeBSD.ORG Subject: Re: Breakage in -current for the ALPHA In-Reply-To: <199811221208.VAA09068@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 Nov 1998, Kazutaka YOKOTA wrote: > >/usr/src/usr.sbin/moused/moused.c:224: `MOUSE_MODEL_KIDSPAD' undeclared here ( > >not in a function) > >/usr/src/usr.sbin/moused/moused.c:224: initializer element for `pnpprod[5].val > >2' > >... > > Oops, I must have forgot to update /sys/alpha/include/mouse.h when I updated > moused recently. Am i being overly niave in suggesting a common directory for some includes on all platforms? Mice are kinda universal no? -Alfred > > Kazu > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 07:08:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA14569 for freebsd-current-outgoing; Sun, 22 Nov 1998 07:08:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA14564 for ; Sun, 22 Nov 1998 07:08:25 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (juana-21.pagesz.net [208.213.126.21]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id KAA26693 for ; Sun, 22 Nov 1998 10:07:54 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id KAA08248; Sun, 22 Nov 1998 10:08:30 -0500 (EST) (envelope-from rhh) Message-ID: <19981122100830.A7061@pagesz.net> Date: Sun, 22 Nov 1998 10:08:30 -0500 From: Randall Hopper To: current@FreeBSD.ORG Subject: 3.0-RELEASE Feedback Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kudos to those that worked on 3.0-RELEASE. The install went well, and I'm in the process of trying to get back set up to the level I was on with 971208-SNAP. I've hit a few snags though. Some of them may or may not be bugs, so I thought I'd mention them here first (rather than file PRs) and get feedback first: 1) lpd stalls As with 9771208-SNAP, my "ps" (ghostscript conversion) queue gets backed up and doesn't realize it has more to process if I put multiple items in the queue. I still have to "lpc start ps" to give it a kick and make it process other queued jobs (which converts them from PostScript to Lastjet, and relay them to the "lp" queue). 2) MAKEDEV doesn't seem to support cd1 stealth : /dev # sh MAKEDEV rcd1c rcd1c - no such device name stealth : /dev # sh MAKEDEV cd1c [: 1c: trailing non-numeric characters [: 1c: trailing non-numeric characters cd1c is invalid -- can't have more than 32 cd devices stealth : /dev sh MAKEDEV cd1 stealth : /dev # ls -l rcd1* /opt/bin/colorls: No match. stealth : /dev # mknod rcd1a c 15 8 stealth : /dev # mknod rcd1c c 15 10 3) cd1 probes printed 10 seconds or so after the console comes up to the login prompt after booting. cd1 at ncr0 bus 0 target 0 lun 0 cd1: Removable CD-ROM SCSI2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present I don't know if this is a bug or not, but it is a little surprising to have this stomp on the login prompt. Are device probes/drivers processed in parallel now? Should these be completing before certain system boot-up scripts are processed (rc.local, etc.)? 4) ldd(1) man page has a ref to ld.so(1), which doesn't exist. 5) sysinstall nit When you ^C to get out of installing packages in sysinstall, it prompts are you sure, you say yes, it exits, it doesn't umount the CD from /dist. Future runs of sysinstall won't use the CD until you manually unmount /dist. 6) Had to add IO_WD3 to isa.h to pick up my Tertiary IDE controller 7) Emacs 20.3 package is broken emacs 20.3 complains about Warning: Lisp directory `/usr/local/share/emacs/20.3/leim' does not exist. and ediff is unusable: Symbol's function definition is void: ediff-convert-standard-filename so I've bailed for emacs 19. 8) The VOXWARE SB16 audio code seems to have gone downhill a bit since 971208-SNAP. Samples do play, but I get pops at the start and end of playing audio samples (open/close of audio device. E.g.: cat drip.au > /dev/audio). Haven't tried Luigi's yet, but I don't want to lose AWE32 MIDI support. 9) And the bigger snag I've hit so far I'll put in a separate post. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 07:15:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15027 for freebsd-current-outgoing; Sun, 22 Nov 1998 07:15:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15022 for ; Sun, 22 Nov 1998 07:15:49 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (juana-21.pagesz.net [208.213.126.21]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id KAA27167 for ; Sun, 22 Nov 1998 10:15:19 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id KAA08735; Sun, 22 Nov 1998 10:15:55 -0500 (EST) (envelope-from rhh) Message-ID: <19981122101554.A8319@pagesz.net> Date: Sun, 22 Nov 1998 10:15:54 -0500 From: Randall Hopper To: current@FreeBSD.ORG Subject: SANE & 3.0-RELEASE? Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just installed 3.0-RELEASE, and needing my Microtek Scanner back in operation, I grabbed the SANE port from FreeBSD-current/ports: 1) stealth > make install ===> sane-0.74 is broken for ELF: build. No SANE? Ouch! I use it all the time on my 3.0 SNAP system (pre-CAM). What are my options here? Also, on a related note: 2) sh MAKEDEV uk0 - doesn't produce a uk0 device file This was needed by SANE in 971208-SNAP. Possibly related to CAM. 3) Missing the superscsi devices Likely related to CAM. Guess I'll boot over to the 3.0-971208-SNAP side for the current scanner job I need to take care of. Hopefully someone has a solution so I can eventually convert to 3.0-RELEASE. Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 07:41:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16996 for freebsd-current-outgoing; Sun, 22 Nov 1998 07:41:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www0m.netaddress.usa.net (www0m.netaddress.usa.net [204.68.24.42]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA16991 for ; Sun, 22 Nov 1998 07:41:53 -0800 (PST) (envelope-from slpalmer@netscape.net) Received: (qmail 14713 invoked by uid 60001); 22 Nov 1998 15:41:21 -0000 Message-ID: <19981122154121.14712.qmail@www0m.netaddress.usa.net> Received: from 204.68.24.42 by www0m via web-mailer(R2.6) on Sun Nov 22 15:41:21 GMT 1998 Date: 22 Nov 98 07:41:21 PST From: Stephen Palmer To: freebsd-current@FreeBSD.ORG Subject: Make world fails on machine/ansi.h Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA16992 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sources are current as of 2:00 AM CST, Nov 22, 1998 'make world' fails with the following on a AMD K6 233mhz machine / Gigabyte TX-2 motherboard. I had done a 'make clean' a few days ago to clear disk space there shouldn't be anything floating around in the src dirs.. I have not been reading -current lately though. Did I miss something important? slpalmer [...] objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x1000 -f bin -b /usr/obj/elf/usr/src/sys/boot/i386/boot2/../btx/btx /btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=0.87 size=6d0 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=143c text=0 data=0 bss=0 entry=0 output: fmt=bin size=1d0c text=200 data=1b0c org=0 entry=0 244 bytes available dd if=boot2.ld of=boot2 obs=7680 conv=osync 2>/dev/null ===> sys/boot/i386/libi386 make: don't know how to make machine/ansi.h. Stop *** Error code 2 Stop. *** Error code 1 --- Stephen L. Palmer slpalmer@netscape.net ____________________________________________________________________ More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 07:43:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17153 for freebsd-current-outgoing; Sun, 22 Nov 1998 07:43:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17147 for ; Sun, 22 Nov 1998 07:43:30 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id HAA27909; Sun, 22 Nov 1998 07:42:56 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id HAA04166; Sun, 22 Nov 1998 07:42:54 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id HAA01025; Sun, 22 Nov 1998 07:42:53 -0800 (PST) From: Don Lewis Message-Id: <199811221542.HAA01025@salsa.gv.tsc.tdk.com> Date: Sun, 22 Nov 1998 07:42:53 -0800 In-Reply-To: "David O'Brien" "Re: snprintf() in the kernel" (Nov 19, 8:30pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: obrien@NUXI.com, Archie Cobbs Subject: Re: snprintf() in the kernel Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 19, 8:30pm, "David O'Brien" wrote: } Subject: Re: snprintf() in the kernel } > The only subtle gotcha with snprintf() is that it returns } > the number of characters that *would* have been printed, } > not the number that actually were printed. } } So, create a new function called ksprintf() that has the calling semantics } of sprintf(), but the return semantics you like. I think the correct thing to do in many cases is to trap this and return the appropriate error. Silent truncation may introduce other bugs. --- Truck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 09:36:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24854 for freebsd-current-outgoing; Sun, 22 Nov 1998 09:36:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24849 for ; Sun, 22 Nov 1998 09:36:09 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 22 Nov 1998 12:35:13 -0500 (EST) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 22 Nov 1998 09:35:10 -0800 (PST) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 22 Nov 1998 12:35:10 -0500 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: Harlan.Stenn@pfcs.com (Harlan Stenn), current@FreeBSD.ORG Subject: Re: objcopy in /usr/libexec/aout/objcopy? In-Reply-To: John Birrell's (jb@cimlogic.com.au) message dated Sun, 22 Nov 1998 17:44:01. <199811220644.RAA00219@cimlogic.com.au> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Nov 1998 12:35:10 -0500 Message-ID: <2457.911756110@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did a "make buildworld ; make installworld" first. Then I updated whatever had changed in src/etc, and rebuilt and installed a new kernel. /usr/libexec/aout/ contains: ar gdb nm size strip as ld ranlib strings H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 09:53:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26268 for freebsd-current-outgoing; Sun, 22 Nov 1998 09:53:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (29-sweet.camalott.com [208.239.153.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26263 for ; Sun, 22 Nov 1998 09:53:18 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id LAA04043; Sun, 22 Nov 1998 11:52:10 -0600 (CST) (envelope-from joelh) To: Randall Hopper Cc: current@FreeBSD.ORG Subject: Re: 3.0-RELEASE Feedback References: <19981122100830.A7061@pagesz.net> From: Joel Ray Holveck Date: 22 Nov 1998 11:52:08 -0600 In-Reply-To: Randall Hopper's message of "Sun, 22 Nov 1998 10:08:30 -0500" Message-ID: <861zmvpqd3.fsf@detlev.UUCP> Lines: 63 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 2) MAKEDEV doesn't seem to support cd1 > stealth : /dev # sh MAKEDEV rcd1c > rcd1c - no such device name > stealth : /dev # sh MAKEDEV cd1c > [: 1c: trailing non-numeric characters > [: 1c: trailing non-numeric characters > cd1c is invalid -- can't have more than 32 cd devices > stealth : /dev sh MAKEDEV cd1 > stealth : /dev # ls -l rcd1* > /opt/bin/colorls: No match. Don't try to make rcd1, cd1c, etc, using MAKEDEV. Use only the basic device name, and MAKEDEV will create all the raw devices and slices that are needed. stealth : /dev # ./MAKEDEV cd1 > 3) cd1 probes printed 10 seconds or so after the console comes up > to the login prompt after booting. > cd1 at ncr0 bus 0 target 0 lun 0 > cd1: Removable CD-ROM SCSI2 device > cd1: 3.300MB/s transfers > cd1: Attempt to query device size failed: NOT READY, Medium not present > I don't know if this is a bug or not, but it is a little surprising to > have this stomp on the login prompt. Are device probes/drivers > processed in parallel now? The CAM stuff is handled in async parallel. > Should these be completing before certain system boot-up scripts are > processed (rc.local, etc.)? If you want them to. It'll probably be semi-trivial to make this happen. I'm considering making a change so that cd's are not probed for size. > 4) ldd(1) man page has a ref to ld.so(1), which doesn't exist. Interesting. There is still a rtld.1 in the source tree; I'm suprised it doesn't get installed. > 7) Emacs 20.3 package is broken > emacs 20.3 complains about > Warning: Lisp directory `/usr/local/share/emacs/20.3/leim' does > not exist. > and ediff is unusable: > Symbol's function definition is void: > ediff-convert-standard-filename Both of these are working fine here. Even though I build Emacs from source instead of the port, I don't see anywhere in the port (as of -current or 3.0-release) that should cause these problems. Was this message before or after installation? Do you have a copy of any ediff files in /usr/local/share/emacs/site-lisp? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 10:06:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27279 for freebsd-current-outgoing; Sun, 22 Nov 1998 10:06:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-44-dbn.dial-up.net [196.34.155.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27246 for ; Sun, 22 Nov 1998 10:05:59 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id UAA07862; Sun, 22 Nov 1998 20:03:20 +0200 (SAT) From: Robert Nordier Message-Id: <199811221803.UAA07862@ceia.nordier.com> Subject: Re: objcopy in /usr/libexec/aout/objcopy? In-Reply-To: <2457.911756110@brown.pfcs.com> from Harlan Stenn at "Nov 22, 98 12:35:10 pm" To: Harlan.Stenn@pfcs.com (Harlan Stenn) Date: Sun, 22 Nov 1998 20:03:16 +0200 (SAT) Cc: jb@cimlogic.com.au, Harlan.Stenn@pfcs.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Harlan Stenn wrote: > I did a "make buildworld ; make installworld" first. > > Then I updated whatever had changed in src/etc, and rebuilt and installed a > new kernel. > > /usr/libexec/aout/ contains: > > ar gdb nm size strip > as ld ranlib strings [Context restored:] > > I thought it would be a good idea to also upgrade /stand/sysinstall, and in > > doing so the make died because /boot was empty. I went in to /usr/src/sys/ > > boot/i386 and tried a make there, which died as follows: > > > > objcopy -S -O binary boot1.out boot1 > > objcopy: could not exec aout/objcopy in /usr/libexec: No such file or directory > > > > Sure enough, while there are a number of files in /usr/libexec/aout/, > > objcopy is not one of them. > > > > What did I miss? Most of the new boot code needs OBJFORMAT=elf. Sysinstall requires only boot0; and this can be built in an aout world as well. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 10:17:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28350 for freebsd-current-outgoing; Sun, 22 Nov 1998 10:17:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28345 for ; Sun, 22 Nov 1998 10:17:11 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (juana-8.pagesz.net [208.213.126.8]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id NAA04911; Sun, 22 Nov 1998 13:16:39 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id NAA01163; Sun, 22 Nov 1998 13:17:14 -0500 (EST) (envelope-from rhh) Message-ID: <19981122131714.A632@pagesz.net> Date: Sun, 22 Nov 1998 13:17:14 -0500 From: Randall Hopper To: Joel Ray Holveck Cc: current@FreeBSD.ORG Subject: Re: 3.0-RELEASE Feedback Mail-Followup-To: Joel Ray Holveck , current@FreeBSD.ORG References: <19981122100830.A7061@pagesz.net> <861zmvpqd3.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <861zmvpqd3.fsf@detlev.UUCP>; from Joel Ray Holveck on Sun, Nov 22, 1998 at 11:52:08AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck: |> 2) MAKEDEV doesn't seem to support cd1 |> stealth : /dev # sh MAKEDEV rcd1c |> rcd1c - no such device name |> stealth : /dev # sh MAKEDEV cd1c |> [: 1c: trailing non-numeric characters |> [: 1c: trailing non-numeric characters |> cd1c is invalid -- can't have more than 32 cd devices |> stealth : /dev sh MAKEDEV cd1 |> stealth : /dev # ls -l rcd1* |> /opt/bin/colorls: No match. | |Don't try to make rcd1, cd1c, etc, using MAKEDEV. Use only the basic |device name, and MAKEDEV will create all the raw devices and slices |that are needed. | stealth : /dev # ./MAKEDEV cd1 No dice: stealth : /dev > ls -l *cd1* brw-r----- 1 root wheel 6, 10 Nov 20 19:19 cd1c crw-r--r-- 1 root wheel 15, 8 Nov 20 20:19 rcd1a crw-r--r-- 1 root wheel 15, 10 Nov 20 20:19 rcd1c stealth : /dev # cd /dev stealth : /dev # rm *cd1* stealth : /dev # sh MAKEDEV cd1 stealth : /dev # ls -l *cd1* /opt/bin/colorls: No match. |> 7) Emacs 20.3 package is broken |> emacs 20.3 complains about |> Warning: Lisp directory `/usr/local/share/emacs/20.3/leim' does |> not exist. |> and ediff is unusable: |> Symbol's function definition is void: |> ediff-convert-standard-filename | |Both of these are working fine here. Even though I build Emacs from |source instead of the port, I don't see anywhere in the port (as of |-current or 3.0-release) that should cause these problems. Was this |message before or after installation? Do you have a copy of any ediff |files in /usr/local/share/emacs/site-lisp? No. I haven't modified anything in /usr/local. Just a pkg_add emacs-20.3*. Thanks for the reply. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 10:33:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29479 for freebsd-current-outgoing; Sun, 22 Nov 1998 10:33:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29474 for ; Sun, 22 Nov 1998 10:33:01 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (juana-8.pagesz.net [208.213.126.8]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id NAA05884 for ; Sun, 22 Nov 1998 13:32:31 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id NAA00716; Sun, 22 Nov 1998 13:33:06 -0500 (EST) (envelope-from rhh) Message-ID: <19981122133306.A529@pagesz.net> Date: Sun, 22 Nov 1998 13:33:06 -0500 From: Randall Hopper To: current@FreeBSD.ORG Subject: 1st 3.0-REL Lock-up (mounting) Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just had 3.0-RELEASE lock up on me for the first time. I'd just formatted a 1.0M Primary DOS FAT partition, and I mount it read-only in my fstab. I'd just booted into FreeBSD and: > umount /e > mount /dev/wd2s1 /e # oops - mistake > mount -t msdos /dev/wd2s1 /e Booting back up and performing these steps without the first mount works fine. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 10:39:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00307 for freebsd-current-outgoing; Sun, 22 Nov 1998 10:39:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (29-sweet.camalott.com [208.239.153.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00301 for ; Sun, 22 Nov 1998 10:39:14 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id MAA20590; Sun, 22 Nov 1998 12:38:30 -0600 (CST) (envelope-from joelh) To: Randall Hopper Cc: current@FreeBSD.ORG Subject: Re: 3.0-RELEASE Feedback References: <19981122100830.A7061@pagesz.net> <861zmvpqd3.fsf@detlev.UUCP> <19981122131714.A632@pagesz.net> From: Joel Ray Holveck Date: 22 Nov 1998 12:38:27 -0600 In-Reply-To: Randall Hopper's message of "Sun, 22 Nov 1998 13:17:14 -0500" Message-ID: <86ww4no9ng.fsf@detlev.UUCP> Lines: 40 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> 2) MAKEDEV doesn't seem to support cd1 >> Don't try to make rcd1, cd1c, etc, using MAKEDEV. Use only the basic >> device name, and MAKEDEV will create all the raw devices and slices >> that are needed. > No dice: > stealth : /dev > ls -l *cd1* > brw-r----- 1 root wheel 6, 10 Nov 20 19:19 cd1c > crw-r--r-- 1 root wheel 15, 8 Nov 20 20:19 rcd1a > crw-r--r-- 1 root wheel 15, 10 Nov 20 20:19 rcd1c > stealth : /dev # cd /dev > stealth : /dev # rm *cd1* > stealth : /dev # sh MAKEDEV cd1 > stealth : /dev # ls -l *cd1* > /opt/bin/colorls: No match. Sorry, I omitted one minor detail. MAKEDEV syntax means that you use the number of devices. If you want to create cd0 and cd1's stuff, you must MAKEDEV cd2 (ie, 2 devices). >>> 7) Emacs 20.3 package is broken >> Both of these are working fine here. Even though I build Emacs from >> source instead of the port, I don't see anywhere in the port (as of >> -current or 3.0-release) that should cause these problems. Was this >> message before or after installation? Do you have a copy of any ediff >> files in /usr/local/share/emacs/site-lisp? > No. > I haven't modified anything in /usr/local. Just a pkg_add emacs-20.3*. > Thanks for the reply. I'll investigate this. I'm not sure about the ediff; the leim I suspect may be a bug in pkg_add. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 10:48:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01366 for freebsd-current-outgoing; Sun, 22 Nov 1998 10:48:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01361 for ; Sun, 22 Nov 1998 10:48:10 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (juana-8.pagesz.net [208.213.126.8]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id NAA06806; Sun, 22 Nov 1998 13:47:36 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id NAA01904; Sun, 22 Nov 1998 13:48:11 -0500 (EST) (envelope-from rhh) Message-ID: <19981122134811.A1167@pagesz.net> Date: Sun, 22 Nov 1998 13:48:11 -0500 From: Randall Hopper To: Joel Ray Holveck Cc: current@FreeBSD.ORG Subject: Re: 3.0-RELEASE Feedback Mail-Followup-To: Joel Ray Holveck , current@FreeBSD.ORG References: <19981122100830.A7061@pagesz.net> <861zmvpqd3.fsf@detlev.UUCP> <19981122131714.A632@pagesz.net> <86ww4no9ng.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <86ww4no9ng.fsf@detlev.UUCP>; from Joel Ray Holveck on Sun, Nov 22, 1998 at 12:38:27PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck: |> stealth : /dev # sh MAKEDEV cd1 | |Sorry, I omitted one minor detail. MAKEDEV syntax means that you use |the number of devices. If you want to create cd0 and cd1's stuff, you |must MAKEDEV cd2 (ie, 2 devices). Ok, that works, but it seems odd. And it appears it isn't applied across the board. For example, when I needed to make my hard drive slice partitions, I needed to explicitly specify the hard drive, slice, and partition to get them. For example: stealth : /dev # rm wd4s1* stealth : /dev # sh MAKEDEV wd4 stealth : /dev # ls -l wd4s1* brw-r----- 1 root operator 0, 0x00020022 Nov 22 13:43 wd4s1 stealth : /dev # sh MAKEDEV wd4s1 stealth : /dev # ls -l wd4s1* brw-r----- 1 root operator 0, 0x00020022 Nov 22 13:43 wd4s1 stealth : /dev # sh MAKEDEV wd4s1e stealth : /dev # ls -l wd4s1* brw-r----- 1 root operator 0, 0x00020022 Nov 22 13:43 wd4s1 brw-r----- 1 root operator 0, 0x00020020 Nov 22 13:43 wd4s1a brw-r----- 1 root operator 0, 0x00020021 Nov 22 13:43 wd4s1b brw-r----- 1 root operator 0, 0x00020022 Nov 22 13:43 wd4s1c brw-r----- 1 root operator 0, 0x00020023 Nov 22 13:43 wd4s1d brw-r----- 1 root operator 0, 0x00020024 Nov 22 13:43 wd4s1e brw-r----- 1 root operator 0, 0x00020025 Nov 22 13:43 wd4s1f brw-r----- 1 root operator 0, 0x00020026 Nov 22 13:43 wd4s1g brw-r----- 1 root operator 0, 0x00020027 Nov 22 13:43 wd4s1h wd4s1e is what I need in this case. If it followed the convention, I'd think a "sh MAKEDEV wd4" would make all possible permutations of all drive/partition/slice for wd0,wd1,wd2,& wd3. |I'll investigate this. I'm not sure about the ediff; the leim I |suspect may be a bug in pkg_add. Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 10:53:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01612 for freebsd-current-outgoing; Sun, 22 Nov 1998 10:53:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01598; Sun, 22 Nov 1998 10:53:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id KAA29962; Sun, 22 Nov 1998 10:52:02 -0800 (PST) (envelope-from dillon) Date: Sun, 22 Nov 1998 10:52:02 -0800 (PST) From: Matthew Dillon Message-Id: <199811221852.KAA29962@apollo.backplane.com> To: Donn Miller Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Distortion/RealPlayer 5.0 References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, has anyone solved the problem of distortion and bad video playback on :FreeBSD-current? Video frames won't play back smooth, sound is :distorted/raspy. Maybe some sys/IO calls aren't being made correctly? : :Also, while I'm at it, can anyone tell me if using cvsup with default :release=cvs will be the same as running -current? : :Thanks : :Donn Go into preferences and find the 8 bit audio option. It's somewhere in there. The problem is probably that you have an 8 bit sound card. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 12:05:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07761 for freebsd-current-outgoing; Sun, 22 Nov 1998 12:05:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pc-micha.mc.hp.com (dialin-stg3-180.arcor-ip.de [145.253.74.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07754 for ; Sun, 22 Nov 1998 12:05:24 -0800 (PST) (envelope-from michaelc@bbn.hp.com) Received: from localhost (michaelc@localhost) by pc-micha.mc.hp.com (8.9.1/8.9.1) with ESMTP id UAA00655 for ; Sun, 22 Nov 1998 20:38:30 +0100 (MET) (envelope-from michaelc@bbn.hp.com) X-Authentication-Warning: pc-micha.mc.hp.com: michaelc owned process doing -bs Date: Sun, 22 Nov 1998 20:38:30 +0100 (MET) From: Michael Class X-Sender: michaelc@pc-micha.mc.hp.com Reply-To: michael_class@gmx.net To: current@FreeBSD.ORG Subject: Chip-Recognition in lnc-driver wrong? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, during the process of setting an old HP Vectra XM2 4/66i (66Mhz 486) as a firewall with 3.0-current (as of today) I had a problem with the lance-ethernet driver (lnc). The Vectra has an integrated AMD 79C970 PCI-Chip an the motherboard. I checked that it is really this chip on the MB! The lance-driver seems to recognize this chip as an Am79C965 (VL-Bus) and the further recognition fails. The interface does not show up if I do an 'ifconfig -a'. When I change the code in if_lnc.c / pcnet_probe to force the driver to recognize the chip as 79C970, everything works fine. Question: Is it possible that the recognition-string for the 79C965 in if_lnc.h (0x2430) is in reality the one for the 79C970 chip? Has anyone a working 79C965 that can be checked, or an other 79C970 that delivers 0x0242 back as id? Unfortunately I do not have any documentation. The system works now for me, but I would like to see it working in the future (if possible) without patches in the kernel. Thank you Michael ------------------------------------------------------------------------- michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: michael_class@gmx.net Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 12:07:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07884 for freebsd-current-outgoing; Sun, 22 Nov 1998 12:07:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07879 for ; Sun, 22 Nov 1998 12:07:53 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id MAA00385; Sun, 22 Nov 1998 12:06:29 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811222006.MAA00385@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray cc: Doug Rabson , Jake , current@FreeBSD.ORG Subject: Re: kernel make failure in smbus In-reply-to: Your message of "Sun, 22 Nov 1998 12:55:36 +0200." <199811221055.MAA61606@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Nov 1998 12:06:28 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Doug Rabson wrote: > > This patch or something similar to it should fix it. I haven't tested it. > > It fixes the compile. Something similar needs to be done in iicbus.c. > > I'll yell if it actually works. > > M Well, does the patch work? Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 12:08:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07938 for freebsd-current-outgoing; Sun, 22 Nov 1998 12:08:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07932 for ; Sun, 22 Nov 1998 12:08:24 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id MAA00403; Sun, 22 Nov 1998 12:07:50 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811222007.MAA00403@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Randall Hopper cc: current@FreeBSD.ORG Subject: Re: SANE & 3.0-RELEASE? In-reply-to: Your message of "Sun, 22 Nov 1998 10:15:54 EST." <19981122101554.A8319@pagesz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Nov 1998 12:07:50 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Randall, It is going to take a good days worth of work to sort out sane and related friends :( Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 12:59:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12025 for freebsd-current-outgoing; Sun, 22 Nov 1998 12:59:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.insolwwb.net (ns.insolwwb.net [206.31.149.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12020 for ; Sun, 22 Nov 1998 12:59:10 -0800 (PST) (envelope-from mgrommet@insolwwb.net) Received: from mikeg (work2.insolwwb.net [208.150.248.12]) by ns.insolwwb.net (8.8.8/8.8.5) with SMTP id OAA09209 for ; Sun, 22 Nov 1998 14:42:52 -0600 (CST) Message-ID: <000301be165a$61cac920$0cf896d0@mikeg.insolwwb.net> From: "Mike" To: Subject: Problems with this network card / driver? Date: Sun, 22 Nov 1998 14:55:05 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys... using 3.0 release on 2 servers....3.0 reports this particular card like this on boot lnc1: rev 0x25 int a irq 14 on pci1.5.0 lnc1: PCnet-FAST address 00:60:94:57:4c:f2 And things seem ok, until I start putting somewhat considerable load on the network card when this happens, I get lots of these: omega /kernel: lnc1: Transmit of packet failed after 16 attempts but the machine seems to hum along with no real noticeable speed problems... the data always is intact once its transferred too... These particular machines are IBM rackmounted server 325's... they have an onboard adaptec 7880 and built in ethernet... all in all a pretty dandy little machine as long as you overlook the integrated components... Actually I have 3 of these servers...... 1 of which runs freebsd 3.0, acting as a usenet newsgroup server... which gets these same errors 1 of which is a web server, running 3.0 and apache 1.3.3 (which has this same error) and the 3rd is running bsdi 4.0... it recognizes the card as an AMD ethernet derivative, but I cant remember the exact model. I do _not_ get these errors or anything resembling them from the bsdi machine, which by itself means nothing... It just makes me think that maybe there needs to be some investigation done on the driver for this particular card In any case should I be concerned at all? Like I said the machine hums along perfectly but being the paranoid little guy that I am, I want to know all the details before they reach up and bite me on the ass. Thanks for your input guys. Mike Grommet Unix Systems Adminstrator Internet Solutions, Inc. mgrommet@insolwwb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 13:07:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12590 for freebsd-current-outgoing; Sun, 22 Nov 1998 13:07:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12584 for ; Sun, 22 Nov 1998 13:07:39 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:7hnzLnM4iE0YHga/pjz0LgTeqSYE8H+C@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id XAA29057; Sun, 22 Nov 1998 23:06:59 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:xHmwSOSxUe1iSMPR00O+ENgkmrp69UFa@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id XAA00350; Sun, 22 Nov 1998 23:06:47 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199811222106.XAA00350@greenpeace.grondar.za> X-Mailer: exmh version 2.0.2 2/24/98 To: Amancio Hasty cc: Doug Rabson , Jake , current@FreeBSD.ORG Subject: Re: kernel make failure in smbus In-Reply-To: Your message of " Sun, 22 Nov 1998 12:06:28 PST." <199811222006.MAA00385@rah.star-gate.com> References: <199811222006.MAA00385@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Nov 1998 23:06:46 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, does the patch work? Sort of. I get no sound, and I think it is because my Hauppauge (PAL-I) card is incorrectly probed: bti2c0: iicbb0: on bti2c0 iicbus0: on iicbb0 master-only Probing for devices on iicbus0: <22> <23> smbus0: on bti2c0 Miro TV, Temic NTSC tuner. My card is not a Miro, and it is not NTSC. I believe this is unrelated to Doug's patches, which should go in. Shall I do the honours? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 13:12:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13419 for freebsd-current-outgoing; Sun, 22 Nov 1998 13:12:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles76.castles.com [208.214.165.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13413 for ; Sun, 22 Nov 1998 13:12:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA13433; Sun, 22 Nov 1998 13:10:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811222110.NAA13433@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Mike" cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems with this network card / driver? In-reply-to: Your message of "Sun, 22 Nov 1998 14:55:05 CST." <000301be165a$61cac920$0cf896d0@mikeg.insolwwb.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Nov 1998 13:10:41 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi guys... using 3.0 release on 2 servers....3.0 reports this particular > card like this on boot > > lnc1: rev 0x25 int a irq 14 on pci1.5.0 > lnc1: PCnet-FAST address 00:60:94:57:4c:f2 Yeah. The lnc driver is pretty marginal at the moment. I'd avoid it if at all possilble. I ran some tests at the local IBM evaluation lab and I wasn't too happy with the onboard ethernet. Try an Intel EtherExpress Pro/100B instead if you're really concerned. > In any case should I be concerned at all? Like I said the machine hums > along perfectly but being the paranoid little guy that I am, I want to know > all the details before they > reach up and bite me on the ass. If it's working OK, then it'll probably continue to work just fine. It's quite likely that the BSD/OS driver just doesn't bother to report this error (which seems to indicate a very busy ethernet). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 13:26:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14552 for freebsd-current-outgoing; Sun, 22 Nov 1998 13:26:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14546 for ; Sun, 22 Nov 1998 13:26:12 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id WAA02320; Sun, 22 Nov 1998 22:25:18 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.8.5) id QAA07419; Sun, 22 Nov 1998 16:38:03 GMT Message-ID: <19981122163802.44786@breizh.prism.uvsq.fr> Date: Sun, 22 Nov 1998 16:38:02 +0000 From: Nicolas Souchu To: Doug Rabson Cc: Amancio Hasty , Jake , current@FreeBSD.ORG Subject: Re: kernel make failure in smbus References: <199811220145.RAA03548@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Doug Rabson on Sun, Nov 22, 1998 at 10:09:19AM +0000 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 22, 1998 at 10:09:19AM +0000, Doug Rabson wrote: > >On Sat, 21 Nov 1998, Amancio Hasty wrote: > >> >> Post on the multimedia mailing list and request a patch to disable smb support >> in bktr it should not be difficult to generate since the code >> to talk to the I2C interface is still in the driver. And there will be no way to follow I2C framework with the bktr driver. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 13:43:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15934 for freebsd-current-outgoing; Sun, 22 Nov 1998 13:43:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from werple.mira.net (werple.mira.net [203.9.190.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA15926 for ; Sun, 22 Nov 1998 13:43:32 -0800 (PST) (envelope-from gfm@mira.net) Received: (qmail 446 invoked from network); 22 Nov 1998 21:42:53 -0000 Received: from dp-m-r074.werple.net.au (203.17.46.74) by mira.net with SMTP; 22 Nov 1998 21:42:53 -0000 From: gfm@mira.net (Graham Menhennitt) To: freebsd-current@FreeBSD.ORG Subject: Adaptec 1542B still not detected Date: Sun, 22 Nov 1998 21:45:19 GMT Message-ID: <3659842e.234385067@mira.net> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA15927 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just updated my 3.0-current system via cvsup. A kernel built with the latest still fails to detect my Adaptec 1542B. I reported this a couple of weeks ago and even posted a fix. Could somebody please make a patch and commit it. Thanks, Graham In /usr/src/sys/dev/aha/aha.c at the bottom of the "probe" routine: if (aha->boardid <= 0x42) { + int dummy; + for(dummy = 0; dummy < 1000; dummy++) + ; status = aha_inb(aha, GEOMETRY_REG); if (status != 0xff) return (ENXIO); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 14:00:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17905 for freebsd-current-outgoing; Sun, 22 Nov 1998 14:00:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17868 for ; Sun, 22 Nov 1998 14:00:31 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id WAA12475; Sun, 22 Nov 1998 22:59:00 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.8.5) id XAA08459; Sun, 22 Nov 1998 23:43:16 GMT Message-ID: <19981122234316.06930@breizh.prism.uvsq.fr> Date: Sun, 22 Nov 1998 23:43:16 +0000 From: Nicolas Souchu To: Amancio Hasty Cc: Mark Murray , Doug Rabson , Jake , current@FreeBSD.ORG Subject: Re: kernel make failure in smbus References: <199811221055.MAA61606@greenpeace.grondar.za> <199811222006.MAA00385@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199811222006.MAA00385@rah.star-gate.com>; from Amancio Hasty on Sun, Nov 22, 1998 at 12:06:28PM -0800 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 22, 1998 at 12:06:28PM -0800, Amancio Hasty wrote: > >> Doug Rabson wrote: >> > This patch or something similar to it should fix it. I haven't tested it. >> >> It fixes the compile. Something similar needs to be done in iicbus.c. >> >> I'll yell if it actually works. >> >> M > >Well, does the patch work? It should since this part (2 lines) is dead code :(, this was only there for future use. I'll delete them anyway until we actually need them. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 14:52:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22706 for freebsd-current-outgoing; Sun, 22 Nov 1998 14:52:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from float.dyn.ml.org (cs802463-a.gvcl1.bc.wave.home.com [24.64.194.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22701 for ; Sun, 22 Nov 1998 14:52:49 -0800 (PST) (envelope-from jake@float.dyn.ml.org) Received: from float.dyn.ml.org (jake@localhost [127.0.0.1]) by float.dyn.ml.org (8.9.1/8.9.1) with ESMTP id OAA00575; Sun, 22 Nov 1998 14:52:06 -0800 (PST) (envelope-from jake@float.dyn.ml.org) Message-Id: <199811222252.OAA00575@float.dyn.ml.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: kernel make failure in smbus In-reply-to: Your message of "Sun, 22 Nov 1998 12:06:28 PST." <199811222006.MAA00385@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Nov 1998 14:52:06 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, does the patch work? > > Tnks, > Amancio > > Yes, it works for me. I had to make the same changes in iicbus.c to get it to compile, but after that it worked perfectly. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 15:05:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23443 for freebsd-current-outgoing; Sun, 22 Nov 1998 15:05:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA23434 for ; Sun, 22 Nov 1998 15:05:09 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 24468 invoked from network); 22 Nov 1998 23:07:24 -0000 Received: from d019.paris-8.cybercable.fr (HELO cybercable.fr) (212.198.8.19) by bouvreuil.cybercable.fr with SMTP; 22 Nov 1998 23:07:24 -0000 Message-ID: <36589853.58BA9D8D@cybercable.fr> Date: Mon, 23 Nov 1998 00:03:47 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Mike Smith CC: Mike , freebsd-current@FreeBSD.ORG Subject: Re: Problems with this network card / driver? References: <199811222110.NAA13433@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Hi guys... using 3.0 release on 2 servers....3.0 reports this particular > > card like this on boot > > > > lnc1: rev 0x25 int a irq 14 on pci1.5.0 > > lnc1: PCnet-FAST address 00:60:94:57:4c:f2 > > Yeah. The lnc driver is pretty marginal at the moment. I'd avoid it > if at all possilble. I ran some tests at the local IBM evaluation lab > and I wasn't too happy with the onboard ethernet. Try an Intel > EtherExpress Pro/100B instead if you're really concerned. Hello, Just for the record, I've set up a pretty ancient (but working well) 486DX2 - 66 from HP with an on-board Lnc NIC, and I've got lots of these errors (on a busy net). But the box is running happily. TfH > > > In any case should I be concerned at all? Like I said the machine hums > > along perfectly but being the paranoid little guy that I am, I want to know > > all the details before they > > reach up and bite me on the ass. > > If it's working OK, then it'll probably continue to work just fine. > It's quite likely that the BSD/OS driver just doesn't bother to report > this error (which seems to indicate a very busy ethernet). > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 15:19:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24244 for freebsd-current-outgoing; Sun, 22 Nov 1998 15:19:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24232 for ; Sun, 22 Nov 1998 15:19:42 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA00516; Sun, 22 Nov 1998 16:19:05 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811222319.QAA00516@panzer.plutotech.com> Subject: Re: SANE & 3.0-RELEASE? In-Reply-To: <19981122101554.A8319@pagesz.net> from Randall Hopper at "Nov 22, 98 10:15:54 am" To: aa8vb@pagesz.net (Randall Hopper) Date: Sun, 22 Nov 1998 16:19:05 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Randall Hopper wrote... > Just installed 3.0-RELEASE, and needing my Microtek Scanner back in > operation, I grabbed the SANE port from FreeBSD-current/ports: > > 1) stealth > make install > ===> sane-0.74 is broken for ELF: build. > > No SANE? Ouch! I use it all the time on my 3.0 SNAP system (pre-CAM). > What are my options here? Talk to Corey Kempf . He has ported SANE to CAM, and can probably give you working source code. > Also, on a related note: > > 2) sh MAKEDEV uk0 - doesn't produce a uk0 device file > > This was needed by SANE in 971208-SNAP. > Possibly related to CAM. Yes. There is no 'uk' driver in CAM. > 3) Missing the superscsi devices > > Likely related to CAM. Yep. You've obviously missed all the stuff about the CAM switchover in the lists. > Guess I'll boot over to the 3.0-971208-SNAP side for the current scanner > job I need to take care of. Hopefully someone has a solution so I can > eventually convert to 3.0-RELEASE. See above. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 15:21:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24654 for freebsd-current-outgoing; Sun, 22 Nov 1998 15:21:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24623 for ; Sun, 22 Nov 1998 15:21:03 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA00535; Sun, 22 Nov 1998 16:20:17 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811222320.QAA00535@panzer.plutotech.com> Subject: Re: SANE & 3.0-RELEASE? In-Reply-To: <199811222007.MAA00403@rah.star-gate.com> from Amancio Hasty at "Nov 22, 98 12:07:50 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 22 Nov 1998 16:20:17 -0700 (MST) Cc: aa8vb@pagesz.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Amancio Hasty wrote... > Hi Randall, > > It is going to take a good days worth of work to sort out sane and > related friends :( Really? SANE has already been ported to CAM, as have most applications that use SCSI passthrough. What "related friends" are you talking about? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 15:28:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25541 for freebsd-current-outgoing; Sun, 22 Nov 1998 15:28:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25536 for ; Sun, 22 Nov 1998 15:28:46 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id PAA01557; Sun, 22 Nov 1998 15:28:09 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811222328.PAA01557@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" cc: aa8vb@pagesz.net, current@FreeBSD.ORG Subject: Re: SANE & 3.0-RELEASE? In-reply-to: Your message of "Sun, 22 Nov 1998 16:20:17 MST." <199811222320.QAA00535@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Nov 1998 15:28:09 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was thinking about gimp , gtk and sane . sane provides a gimp plugin so I can scan within gimp. So if the work has been done to port sane to CAM can we have an ftp pointer ? The glue logic for the scsi interface is very small so that leaves elfing sane and gimp (sane and gimp dynamically loads interface modules) Tnks, Amancio > Amancio Hasty wrote... > > Hi Randall, > > > > It is going to take a good days worth of work to sort out sane and > > related friends :( > > Really? SANE has already been ported to CAM, as have most applications > that use SCSI passthrough. > > What "related friends" are you talking about? > > Ken > -- > Kenneth Merry > ken@plutotech.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 Sun Nov 22 15:33:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25921 for freebsd-current-outgoing; Sun, 22 Nov 1998 15:33:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25913 for ; Sun, 22 Nov 1998 15:33:27 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA00658; Sun, 22 Nov 1998 16:32:48 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811222332.QAA00658@panzer.plutotech.com> Subject: Re: SANE & 3.0-RELEASE? In-Reply-To: <199811222328.PAA01557@rah.star-gate.com> from Amancio Hasty at "Nov 22, 98 03:28:09 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 22 Nov 1998 16:32:48 -0700 (MST) Cc: aa8vb@pagesz.net, current@FreeBSD.ORG, ckempf@enigami.com X-Mailer: ELM [version 2.4ME+ PL28s (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 Amancio Hasty wrote... > > Amancio Hasty wrote... > > > Hi Randall, > > > > > > It is going to take a good days worth of work to sort out sane and > > > related friends :( > > > > Really? SANE has already been ported to CAM, as have most applications > > that use SCSI passthrough. > > > > What "related friends" are you talking about? > > I was thinking about gimp , gtk and sane . sane provides a gimp plugin > so I can scan within gimp. > > So if the work has been done to port sane to CAM can we have an ftp > pointer ? The glue logic for the scsi interface is very small so > that leaves elfing sane and gimp (sane and gimp dynamically loads > interface modules) Talk to Corey Kempf . We should probably go ahead and get the SANE patches into the ports tree, if it's ready. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 15:37:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26364 for freebsd-current-outgoing; Sun, 22 Nov 1998 15:37:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (74-sweet.camalott.com [208.239.153.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26347 for ; Sun, 22 Nov 1998 15:36:59 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id RAA57150; Sun, 22 Nov 1998 17:34:45 -0600 (CST) (envelope-from joelh) To: Randall Hopper Cc: current@FreeBSD.ORG Subject: Re: 3.0-RELEASE Feedback References: <19981122100830.A7061@pagesz.net> <861zmvpqd3.fsf@detlev.UUCP> <19981122131714.A632@pagesz.net> <86ww4no9ng.fsf@detlev.UUCP> <19981122134811.A1167@pagesz.net> From: Joel Ray Holveck Date: 22 Nov 1998 17:34:44 -0600 In-Reply-To: Randall Hopper's message of "Sun, 22 Nov 1998 13:48:11 -0500" Message-ID: <8667c75mjv.fsf@detlev.UUCP> Lines: 22 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> stealth : /dev # sh MAKEDEV cd1 >> Sorry, I omitted one minor detail. MAKEDEV syntax means that you use >> the number of devices. If you want to create cd0 and cd1's stuff, you >> must MAKEDEV cd2 (ie, 2 devices). > Ok, that works, but it seems odd. And it appears it isn't applied across > the board. For example, when I needed to make my hard drive slice > partitions, I needed to explicitly specify the hard drive, slice, and > partition to get them. For example: You had best look over the source to MAKEDEV (it's just a shell script). If you want to standardize it some, feel free to send in a pr. I suspect that the devfs will be completely working soon (anybody have a status report on that?), so it may not be worthwhile. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 15:42:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26882 for freebsd-current-outgoing; Sun, 22 Nov 1998 15:42:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rain.futuresouth.com (rain.futuresouth.com [198.79.79.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26876 for ; Sun, 22 Nov 1998 15:42:14 -0800 (PST) (envelope-from stormy@rain.futuresouth.com) Received: (from stormy@localhost) by rain.futuresouth.com (8.9.1/8.9.1) id RAA07539 for current@FreeBSD.ORG; Sun, 22 Nov 1998 17:41:50 -0600 (CST) (envelope-from stormy) Message-ID: <19981122174150.A289@futuresouth.com> Date: Sun, 22 Nov 1998 17:41:50 -0600 From: Stormy Henderson To: current@FreeBSD.ORG Subject: Re: SANE & 3.0-RELEASE? Mail-Followup-To: current@FreeBSD.ORG References: <199811222320.QAA00535@panzer.plutotech.com> <199811222328.PAA01557@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811222328.PAA01557@rah.star-gate.com>; from Amancio Hasty on Sun, Nov 22, 1998 at 03:28:09PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A happy camper (Amancio Hasty, hasty@rah.star-gate.com) once wrote... > I was thinking about gimp [...] that leaves elfing sane and gimp My GIMP from the ports collection is ELF already: # file /usr/X11R6/bin/gimp /usr/X11R6/bin/gimp: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked, stripped Be happy... -- http://www.futuresouth.com/~stormy/signature.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 15:42:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26899 for freebsd-current-outgoing; Sun, 22 Nov 1998 15:42:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26877 for ; Sun, 22 Nov 1998 15:42:16 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id QAA08681; Sun, 22 Nov 1998 16:34:05 -0700 (MST) Date: Sun, 22 Nov 1998 16:34:05 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811222334.QAA08681@narnia.plutotech.com> To: gfm@mira.net (Graham Menhennitt) cc: current@FreeBSD.ORG Subject: Re: Adaptec 1542B still not detected X-Newsgroups: pluto.freebsd.current In-Reply-To: <3659842e.234385067@mira.net> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3659842e.234385067@mira.net> you wrote: > I just updated my 3.0-current system via cvsup. A kernel built with the > latest still fails to detect my Adaptec 1542B. I reported this a couple of > weeks ago and even posted a fix. Could somebody please make a patch and > commit it. The patch is inappropriate as it won't necessarily solve the problem on all machines (loop is CPU speed dependant). I've been meening to re-examine the aha probe code to see if we even need to look at the geometry register. A better approach may be to try an extended command and succeed the probe only if it fails. This requires the ability to recovery from an invalid command in the driver and ensuring that this works on all aha models. Ping me later in the week and I should have something for you to test. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 16:02:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28756 for freebsd-current-outgoing; Sun, 22 Nov 1998 16:02:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28744 for ; Sun, 22 Nov 1998 16:02:07 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id QAA08722; Sun, 22 Nov 1998 16:54:07 -0700 (MST) Date: Sun, 22 Nov 1998 16:54:07 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811222354.QAA08722@narnia.plutotech.com> To: Joel Ray Holveck cc: current@FreeBSD.ORG Subject: Re: 3.0-RELEASE Feedback X-Newsgroups: pluto.freebsd.current In-Reply-To: <19981122100830.A7061@pagesz.net> <861zmvpqd3.fsf@detlev.UUCP> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <861zmvpqd3.fsf@detlev.UUCP> you wrote: >> 3) cd1 probes printed 10 seconds or so after the console comes up >> to the login prompt after booting. >> cd1 at ncr0 bus 0 target 0 lun 0 >> cd1: Removable CD-ROM SCSI2 device >> cd1: 3.300MB/s transfers >> cd1: Attempt to query device size failed: NOT READY, Medium not present >> I don't know if this is a bug or not, but it is a little surprising to >> have this stomp on the login prompt. Are device probes/drivers >> processed in parallel now? > > The CAM stuff is handled in async parallel. > >> Should these be completing before certain system boot-up scripts are >> processed (rc.local, etc.)? > > If you want them to. It'll probably be semi-trivial to make this > happen. CAM probes for all devices prior to proceeding with the boot. What it doesn't wait for is for all peripheral attachments to complete initialization. Peripheral instances that have not completed initialation will block in 'open' until the initialization is complete. With this strategy, the system will only wait for the devices it needs to during the boot process. This is a feature. The easiest way to make the system 'wait' for your cdrom drive is to leave a disc in it and add have the system mount the drive at boot time. > I'm considering making a change so that cd's are not probed for size. Why. It's one of the ways the system ensures it can successfully talk to the device. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 17:06:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05437 for freebsd-current-outgoing; Sun, 22 Nov 1998 17:06:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www0p.netaddress.usa.net (www0p.netaddress.usa.net [204.68.24.45]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA05431 for ; Sun, 22 Nov 1998 17:06:40 -0800 (PST) (envelope-from slpalmer@netscape.net) Received: (qmail 17479 invoked by uid 60001); 23 Nov 1998 01:06:07 -0000 Message-ID: <19981123010607.17478.qmail@www0p.netaddress.usa.net> Received: from 204.68.24.45 by www0p via web-mailer(R2.6) on Mon Nov 23 01:06:07 GMT 1998 Date: 23 Nov 98 01:06:07 America/Fort_Wayne From: Stephen Palmer To: Subject: make world failure at "machine/ansi.sys" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA05433 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I posted this earlier today, and got no response, however, I saw some kernel compile fixes got commited, so I cvsup'd again current as of 4:00pm CST and tried again... I'm still getting the same failure in make world. Output leading up to the error follows... [...snip] ld -N -e start -Ttext 0x100000 -o btxldr.out btxldr.o objcopy -S -O binary btxldr.out btxldr ===> sys/boot/i386/btx/lib as -elf -o btxcsu.o /usr/src/sys/boot/i386/btx/lib/btxcsu.s as -elf -o btxsys.o /usr/src/sys/boot/i386/btx/lib/btxsys.s as -elf -o btxv86.o /usr/src/sys/boot/i386/btx/lib/btxv86.s ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o ===> sys/boot/i386/boot2 (cd /usr/src/sys/boot/i386/boot2; m4 boot1.m4 boot1.s) | as -o boot1.o ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/sys/boot/i386/boot2/boot2.c (cd /usr/src/sys/boot/i386/boot2; m4 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIODIV=0xc sio.s) | as -o sio.o ld -nostdlib -static -N -Ttext 0x1000 -o boot2.out /usr/obj/elf/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x1000 -f bin -b /usr/obj/elf/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=0.87 size=6d0 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=143c text=0 data=0 bss=0 entry=0 output: fmt=bin size=1d0c text=200 data=1b0c org=0 entry=0 244 bytes available dd if=boot2.ld of=boot2 obs=7680 conv=osync 2>/dev/null ===> sys/boot/i386/libi386 make: don't know how to make machine/ansi.h. Stop *** Error code 2 Stop. *** Error code 1 --- | Stephen L. Palmer | Sprint Paranet slpalmer@netscape.net \|/ slpalmer@sprintparanet.com "There are thousands of intelligent species in the Universe, and they all own cats." -Unknown ____________________________________________________________________ More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 17:13:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05930 for freebsd-current-outgoing; Sun, 22 Nov 1998 17:13:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05925 for ; Sun, 22 Nov 1998 17:13:48 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (juana-8.pagesz.net [208.213.126.8]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id UAA31047; Sun, 22 Nov 1998 20:13:13 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id UAA19975; Sun, 22 Nov 1998 20:13:49 -0500 (EST) (envelope-from rhh) Message-ID: <19981122201349.B19160@pagesz.net> Date: Sun, 22 Nov 1998 20:13:49 -0500 From: Randall Hopper To: "Kenneth D. Merry" , Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: SANE & 3.0-RELEASE? Mail-Followup-To: "Kenneth D. Merry" , Amancio Hasty , current@FreeBSD.ORG References: <19981122101554.A8319@pagesz.net> <199811222319.QAA00516@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811222319.QAA00516@panzer.plutotech.com>; from Kenneth D. Merry on Sun, Nov 22, 1998 at 04:19:05PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |Yep. You've obviously missed all the stuff about the CAM switchover in the |lists. I've noticed the threads, but haven't read through them. No time to stay current with -current -- thus my upgrading from 3.0-971208-SNAP. Guess I'm waiting for the "Dummies Guide to CAM" :-) (No joy in the 3.0-RELEASE Handbook or FAQ). Speaking of CAM docs, here's a legacy handbook snippet that needs a tweak: ...The newer model requires CAM support which is not yet a part of FreeBSD - you have to add it, or install from one of the CAM binary snapshot releases (follow the URL). |Amancio Hasty wrote... |> So if the work has been done to port sane to CAM can we have an ftp |> pointer ? The glue logic for the scsi interface is very small so |> that leaves elfing sane and gimp (sane and gimp dynamically loads |> interface modules) | |Talk to Corey Kempf . We should probably go ahead and |get the SANE patches into the ports tree, if it's ready. Sounds good. I've contacted Corey to see about testing his SANE updates. Thanks for the pointers, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 17:57:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09551 for freebsd-current-outgoing; Sun, 22 Nov 1998 17:57:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09544 for ; Sun, 22 Nov 1998 17:56:58 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id UAA26221; Sun, 22 Nov 1998 20:55:34 -0500 (EST) Date: Sun, 22 Nov 1998 20:55:34 -0500 (EST) From: Chuck Robey To: Stephen Palmer cc: freebsd-current@FreeBSD.ORG Subject: Re: make world failure at "machine/ansi.sys" In-Reply-To: <19981123010607.17478.qmail@www0p.netaddress.usa.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23 Nov 1998, Stephen Palmer wrote: > I posted this earlier today, and got no response, however, I > saw some kernel compile fixes got commited, so I cvsup'd again > current as of 4:00pm CST and tried again... I'm still getting > the same failure in make world. Output leading up to the error > follows... > > [...snip] Think it's your sources. Made world here, right after fresh cvsup, just fine. Same yesterday. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 18:00:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10002 for freebsd-current-outgoing; Sun, 22 Nov 1998 18:00:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from drama.navinet.net (drama.navinet.net [206.25.93.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09996 for ; Sun, 22 Nov 1998 18:00:03 -0800 (PST) (envelope-from forrie@drama.navinet.net) Received: (from forrie@localhost) by drama.navinet.net (8.9.1a/8.9.1) id UAA24610 for freebsd-current@freebsd.org; Sun, 22 Nov 1998 20:59:28 -0500 (EST) Message-ID: <19981122205928.A24604@navinet.net> Date: Sun, 22 Nov 1998 20:59:28 -0500 From: Forrest Aldrich To: freebsd-current@FreeBSD.ORG Subject: Netscape Communicator 4.5 core dumps Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Netscape Communicator for FreeBSD (from ftp.netscape.com in the "unsupported" area) will occasionally dump core. It did this upon initial setup, when I went to save my Preference changes. This applies to FreeBSD-3.0-CURRENT (just got done with make world). Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 18:07:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10826 for freebsd-current-outgoing; Sun, 22 Nov 1998 18:07:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rain.futuresouth.com (rain.futuresouth.com [198.79.79.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10817 for ; Sun, 22 Nov 1998 18:07:09 -0800 (PST) (envelope-from stormy@rain.futuresouth.com) Received: (from stormy@localhost) by rain.futuresouth.com (8.9.1/8.9.1) id UAA08035 for freebsd-current@FreeBSD.ORG; Sun, 22 Nov 1998 20:06:57 -0600 (CST) (envelope-from stormy) Message-ID: <19981122200657.D289@futuresouth.com> Date: Sun, 22 Nov 1998 20:06:57 -0600 From: Stormy Henderson To: freebsd-current@FreeBSD.ORG Subject: Re: Netscape Communicator 4.5 core dumps Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <19981122205928.A24604@navinet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981122205928.A24604@navinet.net>; from Forrest Aldrich on Sun, Nov 22, 1998 at 08:59:28PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A happy camper (Forrest Aldrich, forrie@navinet.net) once wrote... > Netscape Communicator for FreeBSD (from ftp.netscape.com in the > "unsupported" area) will occasionally dump core. If you didn't use the port to install it, you might try it to see if things get setup properly. Be happy... -- http://www.futuresouth.com/~stormy/signature.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 18:11:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11348 for freebsd-current-outgoing; Sun, 22 Nov 1998 18:11:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from drama.navinet.net (drama.navinet.net [206.25.93.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11337 for ; Sun, 22 Nov 1998 18:11:24 -0800 (PST) (envelope-from forrie@drama.navinet.net) Received: (from forrie@localhost) by drama.navinet.net (8.9.1a/8.9.1) id VAA24722; Sun, 22 Nov 1998 21:10:47 -0500 (EST) Message-ID: <19981122211047.A24712@navinet.net> Date: Sun, 22 Nov 1998 21:10:47 -0500 From: Forrest Aldrich To: Stormy Henderson Cc: freebsd-current@FreeBSD.ORG Subject: Re: Netscape Communicator 4.5 core dumps References: <19981122205928.A24604@navinet.net> <19981122200657.D289@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981122200657.D289@futuresouth.com>; from Stormy Henderson on Sun, Nov 22, 1998 at 08:06:57PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The port and the file from netscape are the same. Forrest On Sun, Nov 22, 1998 at 08:06:57PM -0600, Stormy Henderson wrote: > A happy camper (Forrest Aldrich, forrie@navinet.net) once wrote... > > Netscape Communicator for FreeBSD (from ftp.netscape.com in the > > "unsupported" area) will occasionally dump core. > > If you didn't use the port to install it, you might try it to see if > things get setup properly. > > Be happy... > -- > http://www.futuresouth.com/~stormy/signature.html > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 18:12:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11686 for freebsd-current-outgoing; Sun, 22 Nov 1998 18:12:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11677 for ; Sun, 22 Nov 1998 18:12:35 -0800 (PST) (envelope-from rock@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.0/1998052000) with ESMTP id DAA10382; Mon, 23 Nov 1998 03:11:41 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (16PR89r4X6fRzpAx8THzGuMDHKhL5FnE@wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id DAA05886; Mon, 23 Nov 1998 03:11:41 +0100 (CET) Received: (from rock@localhost) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) id DAA22019; Mon, 23 Nov 1998 03:11:40 +0100 (CET) Date: Mon, 23 Nov 1998 03:11:40 +0100 (CET) From: "D. Rock" Message-Id: <199811230211.DAA22019@wurzelausix.cs.uni-sb.de> To: freebsd-current@FreeBSD.ORG, gfm@mira.net Subject: Re: Adaptec 1542B still not detected Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just updated my 3.0-current system via cvsup. A kernel built with the > latest still fails to detect my Adaptec 1542B. I reported this a couple of > weeks ago and even posted a fix. Could somebody please make a patch and > commit it. You are not alone! I had the same problems with my 1542B. But I just commented out the offending lines. To be more consistent with the rest of the kernel, you should use the DELAY() function. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 18:15:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11903 for freebsd-current-outgoing; Sun, 22 Nov 1998 18:15:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11898 for ; Sun, 22 Nov 1998 18:15:25 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40343>; Mon, 23 Nov 1998 13:14:13 +1100 Date: Mon, 23 Nov 1998 13:14:36 +1100 From: Peter Jeremy Subject: Re: strings in the kernel (was: snprintf() in the kernel) To: current@FreeBSD.ORG Cc: archie@whistle.com Message-Id: <98Nov23.131413est.40343@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs wrote: >Sounds like a job for mr. linker.. Not really. For the linker to be able to do this, it would each string definition in a separate block (so that it could include or exclude it as it wished). This is not currently supported by the compiler or assembler, and only supported at an object module level within libraries in the linker. There's also the problem that the symbols used to refer to the strings are currently private - and therefore can't be referenced from a different module. Combining substrings across modules really means either pre-processing the source code to generate a common string block and a pile of #defines (or similar) into it [as done by X11], or modifying the compiler, assembler and linker to defer the actual string allocations. Neither approach is quick and easy to implement. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 18:20:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12692 for freebsd-current-outgoing; Sun, 22 Nov 1998 18:20:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rain.futuresouth.com (rain.futuresouth.com [198.79.79.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12687 for ; Sun, 22 Nov 1998 18:20:50 -0800 (PST) (envelope-from stormy@rain.futuresouth.com) Received: (from stormy@localhost) by rain.futuresouth.com (8.9.1/8.9.1) id UAA08087 for freebsd-current@freebsd.org; Sun, 22 Nov 1998 20:20:39 -0600 (CST) (envelope-from stormy) Message-ID: <19981122202039.E289@futuresouth.com> Date: Sun, 22 Nov 1998 20:20:39 -0600 From: Stormy Henderson To: freebsd-current@FreeBSD.ORG Subject: Re: Netscape Communicator 4.5 core dumps Mail-Followup-To: freebsd-current@freebsd.org References: <19981122205928.A24604@navinet.net> <19981122200657.D289@futuresouth.com> <19981122211047.A24712@navinet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981122211047.A24712@navinet.net>; from Forrest Aldrich on Sun, Nov 22, 1998 at 09:10:47PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A happy camper (Forrest Aldrich, forrie@navinet.net) once wrote... > The port and the file from netscape are the same. The port patches the install script, which can change things. I just checked, however, and the changes are trivial in this case, so it won't make any difference. Be happy... -- http://www.futuresouth.com/~stormy/signature.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 18:22:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12797 for freebsd-current-outgoing; Sun, 22 Nov 1998 18:22:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12792 for ; Sun, 22 Nov 1998 18:22:16 -0800 (PST) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id DAA14915; Mon, 23 Nov 1998 03:21:20 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.9.1/8.8.5/pb-19970302) id BAA29264; Mon, 23 Nov 1998 01:16:46 +0100 (CET) Message-ID: <19981123011646.W403@fasterix.frmug.fr.net> Date: Mon, 23 Nov 1998 01:16:46 +0100 From: Pierre Beyssac To: Phil Regnauld , "Roman V. Palagin" Cc: current@FreeBSD.ORG, pb@fasterix.freenix.org Subject: Re: IPv6 and -current References: <19981116224929.52241@stimpy.prosa.dk> <19981121181720.40825@stimpy.prosa.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i In-Reply-To: <19981121181720.40825@stimpy.prosa.dk>; from Phil Regnauld on Sat, Nov 21, 1998 at 06:17:20PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 21, 1998 at 06:17:20PM +0100, Phil Regnauld wrote: [ IPv6 ] > > Yes, it was, but it's outdated now. > Pierre said he would do another port soon, I think. Pierre ? This mainly means getting my home machine back in sync with -current, merging conflicts by hand (I'm not even under ELF yet). I "only" have roughly 10Mbytes of CTM patches to integrate, but I expect to have more free time for FreeBSD than in the last few months, and my new work environment is better suited for this. I can't give a delay yet; currently my top priority is getting a permanent IP link at home :-). Once that's operational, I'll have much more time for IPv6 and FreeBSD hacking. -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 20:00:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20853 for freebsd-current-outgoing; Sun, 22 Nov 1998 20:00:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20783 for ; Sun, 22 Nov 1998 20:00:11 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id TAA20804; Sun, 22 Nov 1998 19:58:39 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma020802; Sun, 22 Nov 98 19:58:37 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id TAA05102; Sun, 22 Nov 1998 19:58:36 -0800 (PST) From: Archie Cobbs Message-Id: <199811230358.TAA05102@bubba.whistle.com> Subject: Re: snprintf() in the kernel In-Reply-To: <199811210655.RAA26988@godzilla.zeta.org.au> from Bruce Evans at "Nov 21, 98 05:55:18 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sun, 22 Nov 1998 19:58:36 -0800 (PST) Cc: archie@whistle.com, dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG, grog@lemis.com, rnordier@nordier.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to those who checked out the snprintf() patches. "Rev 2" is now available in ftp://ftp.whistle.com/pub/archie/misc. I took out a bunch of strncpy() patches and tweaked a couple of other things. Bruce Evans writes: > >i386/isa/mcd.c > > > > (Looks like you fixed a bug here... the strncpy was assuming zero > > termination) > > The bug was subtracting 1 from the size. I took out my patch to this file.. so the "subtracting 1" bug remains. Would someone else like to fix it? (I know nothing about disklabel stuff). Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 22:51:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04525 for freebsd-current-outgoing; Sun, 22 Nov 1998 22:51:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-14-dbn.dial-up.net [196.34.155.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04510 for ; Sun, 22 Nov 1998 22:51:14 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id IAA11366; Mon, 23 Nov 1998 08:49:51 +0200 (SAT) From: Robert Nordier Message-Id: <199811230649.IAA11366@ceia.nordier.com> Subject: Re: make world failure at "machine/ansi.sys" In-Reply-To: <19981123010607.17478.qmail@www0p.netaddress.usa.net> from Stephen Palmer at "Nov 23, 98 01:06:07 am" To: slpalmer@netscape.net (Stephen Palmer) Date: Mon, 23 Nov 1998 08:49:42 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Palmer wrote: > I posted this earlier today, and got no response, however, I > saw some kernel compile fixes got commited, so I cvsup'd again > current as of 4:00pm CST and tried again... I'm still getting > the same failure in make world. Output leading up to the error > follows... > ===> sys/boot/i386/libi386 > make: don't know how to make machine/ansi.h. Stop > *** Error code 2 And Stephen Palmer earlier wrote: > Sources are current as of 2:00 AM CST, Nov 22, 1998 > 'make world' fails with the following on a > AMD K6 233mhz machine / Gigabyte TX-2 motherboard. > I had done a 'make clean' a few days ago to clear disk space > there shouldn't be anything floating around in the src dirs.. > I have not been reading -current lately though. Did I > miss something important? Yes, you did a make clean without doing a make cleandepend, most likely. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 22 23:12:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06929 for freebsd-current-outgoing; Sun, 22 Nov 1998 23:12:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (34-sweet.camalott.com [208.239.153.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06924 for ; Sun, 22 Nov 1998 23:12:05 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id BAA58519; Mon, 23 Nov 1998 01:11:15 -0600 (CST) (envelope-from joelh) To: "Justin T. Gibbs" Cc: current@FreeBSD.ORG Subject: Re: 3.0-RELEASE Feedback References: <199811222354.QAA08722@narnia.plutotech.com> From: Joel Ray Holveck Date: 23 Nov 1998 01:11:12 -0600 In-Reply-To: "Justin T. Gibbs"'s message of "Sun, 22 Nov 1998 16:54:07 -0700 (MST)" Message-ID: <864srq6fzj.fsf@detlev.UUCP> Lines: 43 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The CAM stuff is handled in async parallel. >>> Should these be completing before certain system boot-up scripts are >>> processed (rc.local, etc.)? >> If you want them to. It'll probably be semi-trivial to make this >> happen. > CAM probes for all devices prior to proceeding with the boot. What it > doesn't wait for is for all peripheral attachments to complete > initialization. Peripheral instances that have not completed initialation > will block in 'open' until the initialization is complete. With this > strategy, the system will only wait for the devices it needs to during > the boot process. This is a feature. Agreed. > The easiest way to make the system 'wait' for your cdrom drive is to > leave a disc in it and add have the system mount the drive at boot > time. If I left disks in the drive to begin with, then the probes would complete before bootup. However, I have no desire to do this. >> I'm considering making a change so that cd's are not probed for size. > Why. It's one of the ways the system ensures it can successfully talk > to the device. To keep a slightly more orderly startup. Rather than have a CD-ROM dump a "Not Ready" error code to the login prompt, and miss all mention of said CD drive in dmesg.boot, I for one would rather use a different method. If I'm reading right, we've already sent the CD-ROM a Test Unit Ready, two Inquiries, and a Mode Sense before sending a read capacity command. Are there likely to be CD-ROM failures in which these others all succeed but the Read Capacity fails with a sense code other than Medium Not Present or Logical Unit Not Ready (both of which are considered successful probes by the CD probe code)? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 01:14:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19035 for freebsd-current-outgoing; Mon, 23 Nov 1998 01:14:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from send103.yahoomail.com (send103.yahoomail.com [205.180.60.92]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA19025 for ; Mon, 23 Nov 1998 01:14:44 -0800 (PST) (envelope-from thallgren@yahoo.com) Message-ID: <19981123091527.11403.rocketmail@send103.yahoomail.com> Received: from [131.116.188.2] by send103.yahoomail.com; Mon, 23 Nov 1998 01:15:27 PST Date: Mon, 23 Nov 1998 01:15:27 -0800 (PST) From: Tommy Hallgren Subject: Stable -> Current To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I've now decided to move over to -CURRENT. Yesterday I CVSUp'ed to -CURRENT from a fresh -STABLE, it took 2 hours(V90 modem, P200MMX, IDE drives _only_, I was surprised it took so long). I'll use a.out 3.0 for a while to somewhat lessen the gap between -STABLE and -CURRENT. Is this path relatively safe? 1. As usual: make world and then make my kernel 2. But then how about the bootblocks? Should I update them before I reboot? How do I upgrade them? disklabel -B? 3. And /dev, should/can I update it before I reboot? 4. I have a Fire GL 1000 Pro gfx card. I therefore use the XFCom_3Dlabs X server from SuSE. Are there problems with -CURRENT and this server? Any comments are appreciated. Thanks! Regards, Tommy _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 01:44:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21813 for freebsd-current-outgoing; Mon, 23 Nov 1998 01:44:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21805 for ; Mon, 23 Nov 1998 01:44:16 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA02498; Mon, 23 Nov 1998 09:45:51 GMT Date: Mon, 23 Nov 1998 09:45:51 +0000 (GMT) From: Doug Rabson To: Alfred Perlstein cc: Kazutaka YOKOTA , current@FreeBSD.ORG Subject: Re: Breakage in -current for the ALPHA 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, 22 Nov 1998, Alfred Perlstein wrote: > > On Sun, 22 Nov 1998, Kazutaka YOKOTA wrote: > > > >/usr/src/usr.sbin/moused/moused.c:224: `MOUSE_MODEL_KIDSPAD' undeclared here ( > > >not in a function) > > >/usr/src/usr.sbin/moused/moused.c:224: initializer element for `pnpprod[5].val > > >2' > > >... > > > > Oops, I must have forgot to update /sys/alpha/include/mouse.h when I updated > > moused recently. > > Am i being overly niave in suggesting a common directory for some includes > on all platforms? > > Mice are kinda universal no? > > -Alfred We certainly need a machine independant place to put include files for driver apis. Does anyone have any good suggestions? Perhaps sys/dev/include for the source and /usr/include/dev for the installed version? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 02:47:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28821 for freebsd-current-outgoing; Mon, 23 Nov 1998 02:47:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28814 for ; Mon, 23 Nov 1998 02:47:18 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA16317; Mon, 23 Nov 1998 21:46:34 +1100 Date: Mon, 23 Nov 1998 21:46:34 +1100 From: Bruce Evans Message-Id: <199811231046.VAA16317@godzilla.zeta.org.au> To: bright@hotjobs.com, dfr@nlsystems.com Subject: Re: Breakage in -current for the ALPHA Cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >We certainly need a machine independant place to put include files for >driver apis. Does anyone have any good suggestions? Perhaps >sys/dev/include for the source and /usr/include/dev for the installed >version? They traditionally go in sys (e.g., ttycom.h). Of course, there is no such thing as a machine independant driver API. There isn't even such a thing as a machine independent driver API. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 05:00:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11581 for freebsd-current-outgoing; Mon, 23 Nov 1998 05:00:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from medusa.cs.uoi.gr (medusa.cs.uoi.gr [193.92.5.160]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11499 for ; Mon, 23 Nov 1998 04:59:54 -0800 (PST) (envelope-from stratos@medusa.cs.uoi.gr) Received: (from stratos@localhost) by medusa.cs.uoi.gr (8.9.1/8.9.1) id OAA00441; Mon, 23 Nov 1998 14:59:17 +0200 (EET) (envelope-from stratos) From: Stratos Paschos Message-Id: <199811231259.OAA00441@medusa.cs.uoi.gr> Subject: Random craches under heavy(?) disk activity To: current@FreeBSD.ORG Date: Mon, 23 Nov 1998 14:59:17 +0200 (EET) 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 all, After a `make world' of Saturday Nov 21, I noticed random crashes, especially when there is disk activity (mail delivery + procmail, or/and update of locate DB). The two consequent days I made a complete fresh cvsup and I rebuild everything, but the behavior didn't change. Only once I managed to see for a second the message, that was something like: ffs_blkfree bad size ..... The configuration is : Pentium II (333MHz), 128 MB RAM, 2 SCSI UW disks 4.2GB, Adaptec AHA2940 (UW). OS version 3.0-current Any ideas? --- Stratos Paschos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 05:18:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13234 for freebsd-current-outgoing; Mon, 23 Nov 1998 05:18:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13229 for ; Mon, 23 Nov 1998 05:18:43 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id GAA25029; Mon, 23 Nov 1998 06:18:08 -0700 (MST) Message-Id: <199811231318.GAA25029@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joel Ray Holveck cc: "Justin T. Gibbs" , current@FreeBSD.ORG Subject: Re: 3.0-RELEASE Feedback In-reply-to: Your message of "23 Nov 1998 01:11:12 CST." <864srq6fzj.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 06:10:41 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> I'm considering making a change so that cd's are not probed for size. >> Why. It's one of the ways the system ensures it can successfully talk >> to the device. > >To keep a slightly more orderly startup. Rather than have a CD-ROM >dump a "Not Ready" error code to the login prompt, and miss all >mention of said CD drive in dmesg.boot, I for one would rather use a >different method. You'll get the same behavior for disk drives that the system needed to spin up, or any other type of device that requires more initialization. Again, this is a feature. If you are really concerned about the contents of your dmesg.boot, add a call to 'camcontrol' in /etc/rc that dumps the device list into dmesg.boot. >If I'm reading right, we've already sent the CD-ROM >a Test Unit Ready, two Inquiries, and a Mode Sense before sending a >read capacity command. We won't send a mode sense unless the drive can do tagged queuing. You also miss that the probe code doesn't even know that a cdrom peripheral driver exists at the point that it performs these actions. The peripheral driver can only assume that the probe took the steps necessary to identify the device, nothing more. >Are there likely to be CD-ROM failures in >which these others all succeed but the Read Capacity fails with a >sense code other than Medium Not Present or Logical Unit Not Ready >(both of which are considered successful probes by the CD probe code)? Certainly. A read capacity is the only thing in the initialization sequence that tests the mechanical ability of the device. If there is a problem with the spindle motor or laser mount, it will likely be reported in response to the read capacity. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 06:06:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18162 for freebsd-current-outgoing; Mon, 23 Nov 1998 06:06:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.ziplink.net (kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18156 for ; Mon, 23 Nov 1998 06:06:17 -0800 (PST) (envelope-from mi@localhost.ziplink.net) Received: (from root@localhost) by localhost.ziplink.net (8.9.1a/8.9.1) id OAA07594 for current@freebsd.org; Mon, 23 Nov 1998 14:05:16 GMT From: Mikhail Teterin Message-Id: <199811231405.OAA07594@localhost.ziplink.net> Subject: Re: Netscape Communicator 4.5 core dumps In-Reply-To: <19981122202039.E289@futuresouth.com> from Stormy Henderson at "Nov 22, 1998 08:20:39 pm" To: current@FreeBSD.ORG Date: Mon, 23 Nov 1998 14:05:15 +0000 (GMT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" rtfm communicator-4.5.bin: /etc/pwd.db: Invalid argument Very recenet current. Just my 2 cents. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 06:23:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19694 for freebsd-current-outgoing; Mon, 23 Nov 1998 06:23:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from drama.navinet.net (drama.navinet.net [206.25.93.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19687 for ; Mon, 23 Nov 1998 06:23:20 -0800 (PST) (envelope-from forrie@drama.navinet.net) Received: (from forrie@localhost) by drama.navinet.net (8.9.1a/8.9.1) id JAA29120 for freebsd-current@freebsd.org; Mon, 23 Nov 1998 09:22:46 -0500 (EST) Message-ID: <19981123092246.A29109@navinet.net> Date: Mon, 23 Nov 1998 09:22:46 -0500 From: Forrest Aldrich To: freebsd-current@FreeBSD.ORG Subject: Problems with BusLogic BT-958 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I defined in the kernel: controller bt0 at isa? port "IO_BT0" irq ? But get this error upon boot: bt: unit number (1) too high bt1 not found at 0x300 I didn't see any other info in the LINT file. What's wrong? This applies to FreeBSD-3.0-CURRENT (build world yesterday). Thanks, Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 06:43:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21745 for freebsd-current-outgoing; Mon, 23 Nov 1998 06:43:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA21739 for ; Mon, 23 Nov 1998 06:43:53 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 1696 invoked by uid 1001); 23 Nov 1998 14:43:17 +0000 (GMT) To: forrie@navinet.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems with BusLogic BT-958 In-Reply-To: Your message of "Mon, 23 Nov 1998 09:22:46 -0500" References: <19981123092246.A29109@navinet.net> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 23 Nov 1998 15:43:17 +0100 Message-ID: <1694.911832197@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I defined in the kernel: > > controller bt0 at isa? port "IO_BT0" irq ? > > But get this error upon boot: > > bt: unit number (1) too high > bt1 not found at 0x300 > > I didn't see any other info in the LINT file. > What's wrong? > > This applies to FreeBSD-3.0-CURRENT (build world yesterday). I don't think anything is wrong. I have a similar error message in a 3.0 system with two BT-946C controllers, and two config file entries (bt0 and bt1). On boot I get: bt0: rev 0x00 int a irq 10 on pci0.6.0 bt0: BT-946C FW Rev. 4.28D Narrow SCSI Host Adapter, SCSI ID 7, 100 CCBs bt1: rev 0x00 int a irq 12 on pci0.7.0 bt1: BT-946C FW Rev. 4.28D Narrow SCSI Host Adapter, SCSI ID 7, 100 CCBs while probing the PCI devices, then later bt: unit number (2) too high bt2 not found at 0x230 bt: unit number (2) too high bt2 not found at 0x230 when it's probing the ISA devices. So to me it looks like an artifact of the way these controllers are probed. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 06:59:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23046 for freebsd-current-outgoing; Mon, 23 Nov 1998 06:59:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-184-92.res.iastate.edu (friley-184-92.res.iastate.edu [129.186.184.92]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23041 for ; Mon, 23 Nov 1998 06:59:06 -0800 (PST) (envelope-from mystify@friley-184-92.res.iastate.edu) Received: from friley-184-92.res.iastate.edu (localhost.res.iastate.edu [127.0.0.1]) by friley-184-92.res.iastate.edu (8.9.1/8.9.1) with ESMTP id IAA03461; Mon, 23 Nov 1998 08:58:31 -0600 (CST) (envelope-from mystify@friley-184-92.res.iastate.edu) Message-Id: <199811231458.IAA03461@friley-184-92.res.iastate.edu> To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: Problems with BusLogic BT-958 In-reply-to: Message from Forrest Aldrich of "Mon, 23 Nov 1998 09:22:46 EST." <19981123092246.A29109@navinet.net> Date: Mon, 23 Nov 1998 08:58:31 -0600 From: Patrick Hartling Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forrest Aldrich wrote: } I defined in the kernel: } } controller bt0 at isa? port "IO_BT0" irq ? } } But get this error upon boot: } } bt: unit number (1) too high } bt1 not found at 0x300 } } I didn't see any other info in the LINT file. } What's wrong? The problem is in your kernel config file. You have an entry for an ISA card when yours is actually PCI. I was doing the same thing for a long time. All you need is: controller bt0 Once you change that, that message about bt1 will go away. -Patrick Patrick L. Hartling | Research Assistant, ICEMT mystify@friley-184-92.res.iastate.edu | Carver Lab - 95E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 07:35:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26571 for freebsd-current-outgoing; Mon, 23 Nov 1998 07:35:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26566 for ; Mon, 23 Nov 1998 07:35:34 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id HAA09651; Mon, 23 Nov 1998 07:34:35 -0800 Date: Mon, 23 Nov 1998 07:34:35 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: Breakage in -current for the ALPHA In-Reply-To: <199811231046.VAA16317@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > They traditionally go in sys (e.g., ttycom.h). Of course, there is > no such thing as a machine independant driver API. There isn't even > such a thing as a machine independent driver API. > Eh? The second sentence might have been 'machine *dependent*'? In either case, what do you mean? There most certainly is both a DDI and DKI for *BSD. There are MI functions (even in FreeBSD which is historically less sensitive to MI vs MD issues) such as bcopy (DKI) or devswitch functions. There are MD functions such as isa_configure (DDI). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 07:58:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28111 for freebsd-current-outgoing; Mon, 23 Nov 1998 07:58:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.mishkei.org.il (host3-64.mishkei.org.il [62.0.64.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28106 for ; Mon, 23 Nov 1998 07:58:02 -0800 (PST) (envelope-from rom_glsa@ein-hashofet.co.il) Received: from ein-hashofet.co.il (host45-68.mishkei.org.il [62.0.68.45]) by mail.mishkei.org.il (8.8.5/8.8.5) with ESMTP id SAA29290 for ; Mon, 23 Nov 1998 18:56:37 +0200 Message-ID: <3659A1F2.F95F33E8@ein-hashofet.co.il> Date: Mon, 23 Nov 1998 17:57:06 +0000 From: Gilad Rom X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I too have been experiencing random reboots, with no apparent reason. Since I spend all of my time in X, I cannot see any panic's or messages, and cannot report anything significant. All I know is it started about 5-6 days ago, maybe on the 18/19th, when I remade the world last time. I have cvsupped and remade the kernel each day since, but the problem still persists. My machine is a Pentium 200Mhz overclocked to 233Mhz, with a TXPro chipset, 96MB of ram and an EIDE hard drive. /usr is mounted softupdates, but ive never had any softupdates related problems before. Hope this helps... By the way, Ive noticed that lately, my kernel's -c changes do not get saved... Any /etc files that I need to update? Thanks. -- Gilad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 08:17:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00479 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:17:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00471 for ; Mon, 23 Nov 1998 08:17:34 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA03041; Tue, 24 Nov 1998 03:16:57 +1100 Date: Tue, 24 Nov 1998 03:16:57 +1100 From: Bruce Evans Message-Id: <199811231616.DAA03041@godzilla.zeta.org.au> To: bde@zeta.org.au, mjacob@feral.com Subject: Re: Breakage in -current for the ALPHA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> They traditionally go in sys (e.g., ttycom.h). Of course, there is >> no such thing as a machine independant driver API. There isn't even >> such a thing as a machine independent driver API. > >Eh? The second sentence might have been 'machine *dependent*'? > >In either case, what do you mean? There most certainly is both a DDI and >DKI for *BSD. There are MI functions (even in FreeBSD which is >historically less sensitive to MI vs MD issues) such as bcopy (DKI) or >devswitch functions. There are MD functions such as isa_configure (DDI). 1. Mispelling of `dependent' is annoying. 2. Nothing is really machine independent. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 08:22:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01058 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:22:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01053 for ; Mon, 23 Nov 1998 08:22:50 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id IAA09802; Mon, 23 Nov 1998 08:22:07 -0800 Date: Mon, 23 Nov 1998 08:22:07 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: Breakage in -current for the ALPHA In-Reply-To: <199811231616.DAA03041@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> They traditionally go in sys (e.g., ttycom.h). Of course, there is > >> no such thing as a machine independant driver API. There isn't even > >> such a thing as a machine independent driver API. > > > >Eh? The second sentence might have been 'machine *dependent*'? > > > >In either case, what do you mean? There most certainly is both a DDI and > >DKI for *BSD. There are MI functions (even in FreeBSD which is > >historically less sensitive to MI vs MD issues) such as bcopy (DKI) or > >devswitch functions. There are MD functions such as isa_configure (DDI). > > 1. Mispelling of `dependent' is annoying. Eh? feral-gw.feral.com > grep dependent /usr/dict/words dependent dependently dependents independent independently interdependent > 2. Nothing is really machine independent. So? That's spurious logic. We all die, therefore we shouldn't attempt to live? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 08:36:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02813 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:36:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02794; Mon, 23 Nov 1998 08:36:07 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id LAA22960; Mon, 23 Nov 1998 11:36:36 -0500 (EST) Message-Id: <4.1.19981123111241.00abf390@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 23 Nov 1998 11:14:20 -0500 To: sthaug@nethelp.no From: Forrest Aldrich Subject: Re: Problems with BusLogic BT-958 Cc: freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG In-Reply-To: <2081.911832652@verdi.nethelp.no> References: <19981123094723.A29351@navinet.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Possibly. I don't know the architecture of these controllers well >enough. I always wondered why you had to add *ISA* config entries >for a PCI controller. [ ... ] That's a good point... I wonder why, in this case. The BT-958 is a PCI card. >> Anyhow, despite these errors, are you able to >> run the system without problems? > >Yes, the system runs. Not particularly *fast*, but it runs. [ ... ] Hmmm... this might be a clue. These are Ultra Wide drives, and one would expect this to be very fast. If they're not running well, this might indicate some driver conflict, perhaps? I hope the technical people will speak up on this one (hint hint). Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 08:36:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02905 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:36:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02797 for ; Mon, 23 Nov 1998 08:36:09 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA07035; Mon, 23 Nov 1998 11:35:22 -0500 (EST) Date: Mon, 23 Nov 1998 11:35:22 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Tom Bartol cc: Doug Rabson , freebsd-current@FreeBSD.ORG Subject: Re: NFS problems in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having different problems. For instance, using FreeBSD 3.0-CURRENT (yesterday) as an NFS server, utilizing PLIP as my connection to a FreeBSD 3.0-RELEASE boot disk on an old WinBook. I was backing up the hard drive (cp /dev/rwd0a /mnt) and I tried running top because both systems were getting slow. Top on the desktop showed 8x% interrupt, is that software or hardware interrupts? After this, I wanted to see the traffic, so I did a trafshow -i lp0, and all of a sudden a flood of Fatal trap 12's happened on the desktop system. Basically, I could do nothing at this point, and had to do a hard reset. So, letting you know, something is broken here. Can I disable DDB for fatal traps, not just panic()'s, because I only wanted it enabled so I could drop into it at will to examine kernel state....? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 08:43:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03833 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:43:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03820 for ; Mon, 23 Nov 1998 08:43:27 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id IAA18620; Mon, 23 Nov 1998 08:42:53 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id IAA29035; Mon, 23 Nov 1998 08:42:53 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 23 Nov 1998 08:42:53 -0800 (PST) Message-Id: <199811231642.IAA29035@vashon.polstra.com> To: eischen@vigrid.com Subject: Re: aout-to-elf-build failure in libpam Newsgroups: polstra.freebsd.current In-Reply-To: <199811221336.IAA07410@pcnet1.pcnet.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199811221336.IAA07410@pcnet1.pcnet.com>, Daniel Eischen wrote: > > From sources updated Saturday, a make aout-to-elf-build fails in: > > building shared pam library (version 1) > ===> libpam/modules > ===> libpam/modules/pam_cleartext_pass_ok > cc -O2 -pipe -I/opt/b/src/src/lib/libpam/modules/pam_cleartext_pass_ok/../../../../contrib/libpam/libpam/include -fpic -Wall -I/usr/obj/elf/opt/b/src/src/tmp/usr/include -c /opt/b/src/src/lib/libpam/modules/pam_cleartext_pass_ok/pam_cleartext_pass_ok.c > cc -O2 -pipe -I/opt/b/src/src/lib/libpam/modules/pam_cleartext_pass_ok/../../../../contrib/libpam/libpam/include -fpic -Wall -I/usr/obj/elf/opt/b/src/src/tmp/usr/include -shared -o pam_cleartext_pass_ok.so pam_cleartext_pass_ok.o -lskey -lgcc_pic > /usr/obj/aout/opt/b/src/src/tmp/usr/libexec/elf/ld: cannot open -lskey: No such file or directory > *** Error code 1 This *may* have been fixed by my commit of "src/lib/libskey/Makefile" revision 1.14 on Sunday. Could you please try it and see if that helps? If it still fails ... I'm not in a position where I can test an aout-to-elf build at this time. But if you'll make the transcript of the entire build available to me, I'll try to figure out what's wrong. I can pick it up via ftp, or you can mail it to me (compressed, please, and don't cc the mailing list :-). Sorry for the hassle. With three kinds of builds available in -current at the moment, it's not always easy to avoid these screwups. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 08:48:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04805 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:48:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.insolwwb.net (ns.insolwwb.net [206.31.149.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04800 for ; Mon, 23 Nov 1998 08:48:28 -0800 (PST) (envelope-from mgrommet@insolwwb.net) Received: from mikeg (work2.insolwwb.net [208.150.248.12]) by ns.insolwwb.net (8.8.8/8.8.5) with SMTP id KAA05824 for ; Mon, 23 Nov 1998 10:32:24 -0600 (CST) From: mike grommet Reply-To: To: Subject: hm... what exactly does this mean in my nighty security output? Date: Mon, 23 Nov 1998 10:47:42 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What are these exactly? Folks who tried to use me as a relay? Interesting because the insolwwb.net domain is my own... this is coming from a machine that should only send out mail from itself (no one really should be using it as a relay anyway) This machine is a webserver with lots of scripts to send mail to folks so I am a bit concerned... southerncast.com is also one of the domains I host Checking for rejected mail hosts: 5 inet-direct.com 1 tampabay.rr.com 1 southerncast.com 1 insolwwb.net Mike Grommet Unix Systems Adminstrator Internet Solutions, Inc. mgrommet@insolwwb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 08:49:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04886 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:49:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04871 for ; Mon, 23 Nov 1998 08:49:25 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA04678; Tue, 24 Nov 1998 03:48:49 +1100 Date: Tue, 24 Nov 1998 03:48:49 +1100 From: Bruce Evans Message-Id: <199811231648.DAA04678@godzilla.zeta.org.au> To: bde@zeta.org.au, mjacob@feral.com Subject: Re: Breakage in -current for the ALPHA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> 1. Mispelling of `dependent' is annoying. > >Eh? > >feral-gw.feral.com > grep dependent /usr/dict/words >dependent >dependently >dependents >independent >independently >interdependent That only shows correct spellings. ispell(1) guesses that `dependant' is a misspelling of `0: defendant ... 3: dependent ... 6: de pendant ...'. >> 2. Nothing is really machine independent. > >So? That's spurious logic. We all die, therefore we shouldn't attempt to >live? We shouldn't spend much lifetime on this :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 08:52:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05245 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:52:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05239 for ; Mon, 23 Nov 1998 08:52:48 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id RAA02089; Mon, 23 Nov 1998 17:50:29 +0100 (CET) To: Brian Feldman cc: Tom Bartol , Doug Rabson , freebsd-current@FreeBSD.ORG Subject: Re: NFS problems in -current In-reply-to: Your message of "Mon, 23 Nov 1998 11:35:22 EST." Date: Mon, 23 Nov 1998 17:50:27 +0100 Message-ID: <2087.911839827@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Using bpf (tcpdump/trafshow &c &c) on plip doesn't work. there are numerous patches in the PR database but they have never quite made it into the source it seems :-( -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 08:54:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05390 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:54:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05384 for ; Mon, 23 Nov 1998 08:54:16 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA07274; Mon, 23 Nov 1998 11:53:33 -0500 (EST) Date: Mon, 23 Nov 1998 11:53:33 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Jason Dicioccio cc: Bill Woods , Andrzej Bialecki , FreeBsd-Current , FreeBsd-Current , Doug White Subject: Re: StarOffice 5.0 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 > Actually I htink 4.0 does not work with FreeBSD either, I beleive 3.0 is > only working now although they say they are in the middle of porting it > (since they have iit on every other OS) Really? Thanks for telling me that the copy of StarOFfice 4.0 (no SP level) that I use all the time on FreeBSD 3.0-CURRENT doesn't work! > > On Thu, 19 Nov 1998, Bill Woods wrote: > > > I am going to assume that this version works on FreeBSD in linux emulation > > ok? > > > > On Wed, 18 Nov 1998, Brian Feldman wrote: > > > > > On Wed, 18 Nov 1998, William Woods wrote: > > > > > > > Care to inform me where I can get 4.0 ? > > > > > > ftp://ftp.stardiv.de/pub/so4/linux/sp3/01/so40sp3_lnx_01.tar.gz > > > > > > > ---------------------------------- > > > > E-Mail: William Woods > > > > Date: 18-Nov-98 > > > > Time: 15:53:44 > > > > -->> FreeBSD 3.0 <<-- > > > > AIM bsdman1 > > > > --------------------------------- > > > > > > Brian Feldman _ __ ___ ___ ___ > > > green@unixhelp.org _ __ ___ | _ ) __| \ > > > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > > > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 08:54:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05423 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:54:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05414 for ; Mon, 23 Nov 1998 08:54:31 -0800 (PST) (envelope-from root@eyelab.psy.msu.edu) Received: from devel-eyelab (dhcp109.baker.ssc.msu.edu [35.8.194.109]) by eyelab.psy.msu.edu (8.9.1/8.8.7) with SMTP id LAA05879; Mon, 23 Nov 1998 11:53:52 -0500 (EST) (envelope-from root@eyelab.psy.msu.edu) Message-Id: <4.1.19981123115103.00a360d0@eyelab.msu.edu> X-Sender: root@eyelab.msu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 23 Nov 1998 11:55:15 -0500 To: , From: Gary Schrock Subject: Re: hm... what exactly does this mean in my nighty security output? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:47 AM 11/23/98 -0600, mike grommet wrote: >What are these exactly? Folks who tried to use me as a relay? >Interesting because the insolwwb.net domain is my own... >Checking for rejected mail hosts: > 5 inet-direct.com > 1 tampabay.rr.com > 1 southerncast.com > 1 insolwwb.net >From what I've seen, the addresses that get logged are the addresses the mail was getting sent *to*, which personally I don't find as usefull as if it would log the addresses that it was coming from. Unfortunately, from what I can tell, if sendmail is rejecting the mail for whatever reason, the only address logged is the recipient (well, it also logs a relay, but you don't get a senders address). Only real way to tell what the rejection was for and where it came from is to grep through the mail log for reject. Gary Schrock root@eyelab.msu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 08:59:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05867 for freebsd-current-outgoing; Mon, 23 Nov 1998 08:59:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05860 for ; Mon, 23 Nov 1998 08:59:14 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id IAA09904; Mon, 23 Nov 1998 08:58:30 -0800 Date: Mon, 23 Nov 1998 08:58:30 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: Breakage in -current for the ALPHA In-Reply-To: <199811231648.DAA04678@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Nov 1998, Bruce Evans wrote: > >> 1. Mispelling of `dependent' is annoying. > > > >Eh? > > > >feral-gw.feral.com > grep dependent /usr/dict/words > >dependent > >dependently > >dependents > >independent > >independently > >interdependent > > That only shows correct spellings. ispell(1) guesses that `dependant' is > a misspelling of `0: defendant ... 3: dependent ... 6: de pendant ...'. I misunderstood. I thought you were criticizing my use of 'dependent'. > > >> 2. Nothing is really machine independent. > > > >So? That's spurious logic. We all die, therefore we shouldn't attempt to > >live? > > We shouldn't spend much lifetime on this :-). Rightyo, then! Seriously- attempts to regularize and make as broad as possible kernel APIs and ABIs is a laudable goal and shows whether an OS is ready to be taken seriously for a multiplatform market- I really didn't understand what you meant by "Nothing is really machine independent" except I inferred from the tone that the attempt regularize where machine dependent driver includes would go except "wherever" was a waste of time. Perhaps I didn't understand. But- if you like, we'll just drive on, eh? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 09:34:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10441 for freebsd-current-outgoing; Mon, 23 Nov 1998 09:34:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles354.castles.com [208.214.167.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10380 for ; Mon, 23 Nov 1998 09:34:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA19160; Mon, 23 Nov 1998 09:30:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811231730.JAA19160@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: Tom Bartol , Doug Rabson , freebsd-current@FreeBSD.ORG Subject: Re: NFS problems in -current In-reply-to: Your message of "Mon, 23 Nov 1998 11:35:22 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 09:30:22 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please ask a primary school teacher about "paragraphs". Please also make it clear whether you're using the old 'lpt' driver or the newer ppbus code, so that we can work out what needs attention... > I'm having different problems. For instance, using FreeBSD 3.0-CURRENT > (yesterday) as an NFS server, utilizing PLIP as my connection to > a FreeBSD 3.0-RELEASE boot disk on an old WinBook. I was backing > up the hard drive (cp /dev/rwd0a /mnt) and I tried running top > because both systems were getting slow. Top on the desktop showed > 8x% interrupt, is that software or hardware interrupts? After this, > I wanted to see the traffic, so I did a trafshow -i lp0, and all > of a sudden a flood of Fatal trap 12's happened on the desktop > system. Basically, I could do nothing at this point, and had to do > a hard reset. So, letting you know, something is broken here. Can > I disable DDB for fatal traps, not just panic()'s, because I only > wanted it enabled so I could drop into it at will to examine kernel > state....? > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 09:54:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12150 for freebsd-current-outgoing; Mon, 23 Nov 1998 09:54:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12145 for ; Mon, 23 Nov 1998 09:54:35 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id KAA88191; Mon, 23 Nov 1998 10:01:50 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811231801.KAA88191@troutmask.apl.washington.edu> Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <199811231259.OAA00441@medusa.cs.uoi.gr> from Stratos Paschos at "Nov 23, 1998 2:59:17 pm" To: stratos@medusa.cs.uoi.gr (Stratos Paschos) Date: Mon, 23 Nov 1998 10:01:50 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Stratos Paschos: > > Hi all, > > After a `make world' of Saturday Nov 21, I noticed random crashes, especially > when there is disk activity (mail delivery + procmail, or/and update of > locate DB). The two consequent days I made a complete fresh cvsup > and I rebuild everything, but the behavior didn't change. > Only once I managed to see for a second the message, that was something > like: > ffs_blkfree bad size ..... > > The configuration is : Pentium II (333MHz), 128 MB RAM, > 2 SCSI UW disks 4.2GB, Adaptec AHA2940 (UW). > OS version 3.0-current > > Any ideas? > Just a me too. I filed a PR on 14 Nov 98, but it was closed with an explanation that a commit to vfs_cluster.c fixed the problem. Problem still presists. You might disabling the restored ffs_doreallocblks() stuff. sysctl -w vfs.ffs.doreallocblks=0 -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 10:15:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14842 for freebsd-current-outgoing; Mon, 23 Nov 1998 10:15:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14836 for ; Mon, 23 Nov 1998 10:15:16 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id KAA22533; Mon, 23 Nov 1998 10:13:48 -0800 (PST) Date: Mon, 23 Nov 1998 10:13:49 -0800 (PST) From: Tom Bartol To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Problem with amd (was: NFS problems in -current) 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, 19 Nov 1998, John Polstra wrote: > On 20-Nov-98 Tom Bartol wrote: > > > > Thanks for the info. I'll try it out tomorrow. If I want NFSv3 with UDP > > I suppose I would say: > > > > proto=udp,vers=3 > > > > correct? > > Correct. I had problems using NFSv3 the last time I tried it, but > that was several months ago. Maybe it's better now. > > > BTW, I can't find these options documented in amd(8) amd.conf(5) or > > mount_nfs(8). Any place else I should be looking? > > Not that I know of. The documentation is pretty broken. I had a > very hard time even finding the right options in the sources. > > John > --- With many thanks to your expert advice the proto=udp,vers=3 options to amd gets NFS mounts working reliably with amd for me again. However, I only get ~4MBps throughput to and NFSv3 mounted filesystem when amd makes the mount for me, but I get ~9MBps throughput when I mount the same filesystem by hand (i.e. without amd). The /defaults line in may amd.map file looks like: /defaults type:=nfs;opts:=rw,proto=udp,vers=3 My first guess at the reason would be that amd is mounting with very different default options than those built into mount_nfs but I'm having a lot of trouble narrowing down which of the myriad mount options are to blame here and (more importantly) which options amd is using as its defaults. Does anyone have any help to offer me on this one? Thanks again, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 10:20:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15192 for freebsd-current-outgoing; Mon, 23 Nov 1998 10:20:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15157 for ; Mon, 23 Nov 1998 10:19:58 -0800 (PST) (envelope-from root@zappa.demon.nl) Received: (from root@localhost) by zappa.demon.nl (8.9.1/8.8.8) id TAA00449; Mon, 23 Nov 1998 19:20:34 +0100 (CET) (envelope-from root) Message-ID: <19981123192034.A281@zappa.demon.nl> Date: Mon, 23 Nov 1998 19:20:34 +0100 From: Ron Klinkien To: Mikhail Teterin , current@FreeBSD.ORG Subject: Re: Netscape Communicator 4.5 core dumps References: <19981122202039.E289@futuresouth.com> <199811231405.OAA07594@localhost.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811231405.OAA07594@localhost.ziplink.net>; from Mikhail Teterin on Mon, Nov 23, 1998 at 02:05:15PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 23, 1998 at 02:05:15PM +0000, Mikhail Teterin wrote: > > Sometimes, Netscape hangs on my machine and needs to be killed and > restarted. This is often accompanied by this sort of log entry: > > Nov 21 15:44:59 rtfm communicator-4.5.bin: /etc/pwd.db: Invalid argument > > Very recenet current. Just my 2 cents. > > -mi > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Exactly the same here using the final 4.5 from Netscape site. Ron. -- --- "You could jam in Joe's garage..." -FZ Ron Klinkien System Engineer ron@zappa.demon.nl http://www.zappa.demon.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 10:21:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15433 for freebsd-current-outgoing; Mon, 23 Nov 1998 10:21:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15410 for ; Mon, 23 Nov 1998 10:21:38 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id MAA23100 for ; Mon, 23 Nov 1998 12:50:34 -0500 (EST) Message-Id: <4.1.19981123122653.00abfe40@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 23 Nov 1998 12:28:16 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: CODA on FreeBSD-CURRENT Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wondered about anyone's experience with CODA on FreeBSD-CURRENT. I see that vinum and some other stuff is included in the source tree, but want to find out more about people's experience (good and bad) with these. Are they stable, etc. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 10:51:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01360 for freebsd-current-outgoing; Mon, 23 Nov 1998 10:51:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from plunger.gdeb.com (plunger.gdeb.com [153.11.11.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01343 for ; Mon, 23 Nov 1998 10:51:24 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from clcrtr.clc.gdeb.com ([153.11.109.11]) by plunger.gdeb.com (8.9.1a/8.9.1/CSC-E_2.0) with ESMTP id MAA14304; Mon, 23 Nov 1998 12:20:16 -0500 (EST) Received: from clcrtr.clc.gdeb.com (clcrtr [153.11.109.129]) by clcrtr.clc.gdeb.com (8.8.8/8.8.8) with SMTP id MAA18394; Mon, 23 Nov 1998 12:20:05 -0500 (EST) (envelope-from eischen@vigrid.com) Message-ID: <36599945.41C67EA6@vigrid.com> Date: Mon, 23 Nov 1998 12:20:05 -0500 From: "Daniel M. Eischen" X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: jdp@polstra.com CC: current@FreeBSD.ORG Subject: Re: aout-to-elf-build failure in libpam Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > From sources updated Saturday, a make aout-to-elf-build fails in: > > > > building shared pam library (version 1) > > ===> libpam/modules > > ===> libpam/modules/pam_cleartext_pass_ok > > cc -O2 -pipe -I/opt/b/src/src/lib/libpam/modules/pam_cleartext_pass_ok/../../../../contrib/libpam/libpam/include -fpic -Wall \ > > -I/usr/obj/elf/opt/b/src/src/tmp/usr/include -c /opt/b/src/src/lib/libpam/modules/pam_cleartext_pass_ok/pam_cleartext_pass_ok.c > > cc -O2 -pipe -I/opt/b/src/src/lib/libpam/modules/pam_cleartext_pass_ok/../../../../contrib/libpam/libpam/include -fpic -Wall \ > > -I/usr/obj/elf/opt/b/src/src/tmp/usr/include -shared -o pam_cleartext_pass_ok.so pam_cleartext_pass_ok.o -lskey -lgcc_pic > > /usr/obj/aout/opt/b/src/src/tmp/usr/libexec/elf/ld: cannot open -lskey: No such file or directory > > *** Error code 1 > > This *may* have been fixed by my commit of "src/lib/libskey/Makefile" > revision 1.14 on Sunday. Could you please try it and see if that > helps? I'll try it later tonight - thanks. > If it still fails ... I'm not in a position where I can test an > aout-to-elf build at this time. But if you'll make the transcript of > the entire build available to me, I'll try to figure out what's wrong. > I can pick it up via ftp, or you can mail it to me (compressed, > please, and don't cc the mailing list :-). OK, no problem. > Sorry for the hassle. With three kinds of builds available in > -current at the moment, it's not always easy to avoid these screwups. Yeah, I can imagine ;-) Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 10:54:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01779 for freebsd-current-outgoing; Mon, 23 Nov 1998 10:54:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01765 for ; Mon, 23 Nov 1998 10:54:05 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id KAA10484; Mon, 23 Nov 1998 10:54:30 -0800 (PST) Message-Id: <199811231854.KAA10484@root.com> To: Steve Kargl cc: stratos@medusa.cs.uoi.gr (Stratos Paschos), Gilad Rom , current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Mon, 23 Nov 1998 10:01:50 PST." <199811231801.KAA88191@troutmask.apl.washington.edu> From: David Greenman Reply-To: dg@root.com Date: Mon, 23 Nov 1998 10:54:29 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >According to Stratos Paschos: >> >> Hi all, >> >> After a `make world' of Saturday Nov 21, I noticed random crashes, especially >> when there is disk activity (mail delivery + procmail, or/and update of >> locate DB). The two consequent days I made a complete fresh cvsup >> and I rebuild everything, but the behavior didn't change. >> Only once I managed to see for a second the message, that was something >> like: >> ffs_blkfree bad size ..... >> >> The configuration is : Pentium II (333MHz), 128 MB RAM, >> 2 SCSI UW disks 4.2GB, Adaptec AHA2940 (UW). >> OS version 3.0-current >> >> Any ideas? >> > >Just a me too. I filed a PR on 14 Nov 98, but it was closed >with an explanation that a commit to vfs_cluster.c fixed the problem. >Problem still presists. All of the "me too"'s should contact Kirk McMusick about this, as I'm sure he'll need additional data before fixing the problem....mckusick@mckusick.com. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 11:27:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04947 for freebsd-current-outgoing; Mon, 23 Nov 1998 11:27:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shire.domestic.de (kuebart.stuttgart.netsurf.de [194.233.216.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04923; Mon, 23 Nov 1998 11:26:52 -0800 (PST) (envelope-from joki@kuebart.stuttgart.netsurf.de) Received: from yacht.domestic.de (yacht.domestic.de [192.168.1.4]) by shire.domestic.de (8.8.8/8.8.7) with ESMTP id UAA21187; Mon, 23 Nov 1998 20:27:32 +0100 (CET) (envelope-from joki@shire.domestic.de) From: Joachim Kuebart Received: (from joki@localhost) by yacht.domestic.de (8.9.1/8.8.7) id UAA00933; Mon, 23 Nov 1998 20:27:47 +0100 (CET) (envelope-from joki@shire.domestic.de) Message-Id: <199811231927.UAA00933@yacht.domestic.de> Subject: Re: ES1370 Treiber In-Reply-To: <199811221813.TAA00819@oranje.my.domain> from Marc van Woerkom at "Nov 22, 98 07:13:36 pm" To: van.woerkom@netcologne.de Date: Mon, 23 Nov 1998 18:11:09 +0100 (CET) Cc: luigi@iet.unipi.it, lindgren@informatik.uni-freiburg.de X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc van Woerkom wrote: > marc@oranje$ cat /dev/sndstat > cat: /dev/sndstat: Device not configured > marc@oranje$ The following patch (to be added to my other patches) removes the bug that the cdevsw entry was not added when there was no ISA card attached: --- sound.c.orig Mon Nov 23 18:07:35 1998 +++ sound.c Mon Nov 23 18:06:04 1998 @@ -239,7 +239,6 @@ snddev_info *d = NULL ; struct isa_device *dvp; int stat = 0; - dev_t isadev; dev->id_ointr = pcmintr; @@ -284,9 +283,6 @@ if (FULL_DUPLEX(d)) isa_dma_acquire(d->dbuf_in.chan); - isadev = makedev(CDEV_MAJOR, 0); - cdevsw_add(&isadev, &snd_cdevsw, NULL); - /* * should try and find a suitable value for id_id, otherwise * the interrupt is not registered and dispatched properly. @@ -331,6 +327,10 @@ pcminit(snddev_info *d, int unit) { void *cookie; + dev_t dev; + + dev = makedev(CDEV_MAJOR, 0); + cdevsw_add(&dev, &snd_cdevsw, NULL); /* * initialize standard parameters for the device. This can be cu Jo --------------------------------------------------------------------- Pray that there's intelligent life Joachim Kuebart Somewhere up in space Stuttgart, Germany 'Cause there's bugger all down here on earth. --- Monty Python To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 11:41:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07528 for freebsd-current-outgoing; Mon, 23 Nov 1998 11:41:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07521 for ; Mon, 23 Nov 1998 11:41:08 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id UAA03694 for freebsd-current@FreeBSD.ORG; Mon, 23 Nov 1998 20:41:04 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 80129147E; Mon, 23 Nov 1998 20:40:19 +0100 (CET) Date: Mon, 23 Nov 1998 20:40:19 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? Message-ID: <19981123204019.A11237@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <021f01be136c$244d6440$1f40e6cd@ichiban.ingress.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <021f01be136c$244d6440$1f40e6cd@ichiban.ingress.com>; from Yarema on Wed, Nov 18, 1998 at 10:24:39PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4829 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Yarema: > ${local_startup} in /etc/rc.conf becomes rather misnamed if this patch is > adopted. > --- rc.shutdown.orig Fri Aug 1 20:22:45 1997 > +++ rc.shutdown Wed Nov 18 22:10:04 1998 This one runs the scripts in reverse order. --- /usr/src/etc/rc.shutdown Sat Aug 2 02:22:45 1997 +++ rc.shutdown Mon Nov 23 20:39:57 1998 @@ -17,10 +17,30 @@ PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin export PATH -echo -n Shutting down daemon processes: +echo Shutting down daemon processes: # Insert shutdown procedures here +if [ -f /etc/rc.conf ]; then + . /etc/rc.conf +fi + +echo '' +# for each valid dir in $local_startup, search for init scripts matching +# *.sh +if [ "X${local_startup}" != X"NO" ]; then + echo 'Local package shutdown:' + # reverse the directory list + for dir in ${local_startup}; do + rdir_list="${dir} ${rdir_list}" + done + for dir in ${rdir_list}; do + [ -d ${dir} ] && for script in `/bin/ls -r ${dir}/*.sh`; do + [ -x ${script} ] && \ + (trap 'exit 1' 2 ; ${script} stop ; echo -n) + done + done +fi echo '.' exit 0 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 12:29:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12287 for freebsd-current-outgoing; Mon, 23 Nov 1998 12:29:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12137 for ; Mon, 23 Nov 1998 12:28:55 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Mon, 23 Nov 1998 20:27:59 -0000 Message-ID: From: Paul Richards To: "'Mike Smith'" , Mike Cc: freebsd-current@FreeBSD.ORG Subject: RE: Problems with this network card / driver? Date: Mon, 23 Nov 1998 20:27:58 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mike Smith [mailto:mike@smith.net.au] > Sent: Sunday, November 22, 1998 9:11 PM > To: Mike > Cc: freebsd-current@FreeBSD.ORG > Subject: Re: Problems with this network card / driver? > > > > Hi guys... using 3.0 release on 2 servers....3.0 reports > this particular > > card like this on boot > > > > lnc1: rev 0x25 int a irq 14 on pci1.5.0 > > lnc1: PCnet-FAST address 00:60:94:57:4c:f2 > > Yeah. The lnc driver is pretty marginal at the moment. I'd avoid it > if at all possilble. I ran some tests at the local IBM > evaluation lab > and I wasn't too happy with the onboard ethernet. Try an Intel > EtherExpress Pro/100B instead if you're really concerned. Have you any specific details on why you think it's not working? It seems there's a bug been introduced recently relating to detecting cards that I'll look into but I'm not aware of any other problems with the driver that would make it necessary to avoid using it. In any case, I'm going to give the code an overhaul soon since I haven't looked at it for a few years so if you or anyone else has been having problems with this driver then now's the time to let me know :-) > > In any case should I be concerned at all? Like I said the > machine hums > > along perfectly but being the paranoid little guy that I > am, I want to know > > all the details before they > > reach up and bite me on the ass. > > If it's working OK, then it'll probably continue to work just fine. > It's quite likely that the BSD/OS driver just doesn't bother > to report > this error (which seems to indicate a very busy ethernet). This particular error report is perfectly normal and indicates a saturated network (assuming there aren't any bugs). It's true that one criticism that can be thrown at lnc is that it reports errors where many cards do not. I still claim that this is a good thing :-) Paul Richards Ph.D. Originative Solutions Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 12:46:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14138 for freebsd-current-outgoing; Mon, 23 Nov 1998 12:46:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14129 for ; Mon, 23 Nov 1998 12:46:42 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id MAA43340; Mon, 23 Nov 1998 12:47:29 -0800 (PST) To: Gilad Rom cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Mon, 23 Nov 1998 17:57:06 GMT." <3659A1F2.F95F33E8@ein-hashofet.co.il> Date: Mon, 23 Nov 1998 12:47:28 -0800 Message-ID: <43337.911854048@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I too have been experiencing random > reboots, with no apparent reason. I see an apparent reason. Keep reading. > My machine is a Pentium 200Mhz overclocked to 233Mhz, Stop that. At least until your system is 100% stable and does not exhibit any symptoms which can be clearly traced to software. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 12:51:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14651 for freebsd-current-outgoing; Mon, 23 Nov 1998 12:51:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14646 for ; Mon, 23 Nov 1998 12:51:12 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA29019 for ; Mon, 23 Nov 1998 12:42:02 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdK29003; Mon Nov 23 20:41:52 1998 Date: Mon, 23 Nov 1998 12:41:25 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG Subject: Elf linker question. Message-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 doing some work in a 3.0 system using the elf linker. It seems that the new linker is insisting on me including libraries that I never needed before.. In other words, I thin it's trying to resolve symbols in functions I'm not using. Does anyone have comments on this? The old aout linker didn't need me to specify libraries that were not in my call-graph. THe new one seems to need them. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 13:00:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16167 for freebsd-current-outgoing; Mon, 23 Nov 1998 13:00:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16162 for ; Mon, 23 Nov 1998 13:00:38 -0800 (PST) (envelope-from paulz@trantor.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <4372-13892>; Mon, 23 Nov 1998 22:00:23 +0100 Received: from trantor.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.9.1/8.9.1) with UUCP id VAA00698 for current@FreeBSD.ORG; Mon, 23 Nov 1998 21:24:48 +0100 (MET) (envelope-from paulz@trantor.stuyts.nl) Received: from trantor.stuyts.nl (localhost [127.0.0.1]) by trantor.stuyts.nl (8.9.1/8.8.5) with ESMTP id VAA00480 for ; Mon, 23 Nov 1998 21:22:30 +0100 (MET) Message-Id: <199811232022.VAA00480@trantor.stuyts.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Weird NFS error using Solaris 7 server Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 21:22:30 +0100 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I try to create a file on a FS mounted from my Sparc 5 running Solaris 7 I get the following error: [21:14:42 trantor:paulz:/mnt/var/tmp] $ touch a touch: a: Inappropriate file type or format However if I ktrace the command a ktrace.out gets created. Part of kdump output follows: 428 touch CALL gettimeofday(0xefbfd598,0) 428 touch RET gettimeofday 0 428 touch CALL stat(0xefbfd746,0xefbfd5a8) 428 touch NAMI "a" 428 touch RET stat -1 errno 2 No such file or directory 428 touch CALL open(0xefbfd746,0x201,0x1b6) 428 touch NAMI "a" 428 touch RET open -1 errno 79 Inappropriate file type or format 428 touch CALL write(0x2,0xefbfce04,0x7) Snoop on the Sparc shows the offending(?) request and the response: ________________________________ trantor -> seldon ETHER Type=0800 (IP), size = 238 bytes trantor -> seldon IP D=192.168.200.3 S=192.168.200.2 LEN=224, ID=134 trantor -> seldon TCP D=2049 S=1017 Ack=171713445 Seq=11856676 Len=184 Win=17200 trantor -> seldon RPC C XID=1902072876 PROG=100003 (NFS) VERS=3 PROC=8 trantor -> seldon NFS C CREATE3 FH=B22A (UNCHECKED) a ________________________________ seldon -> trantor ETHER Type=0800 (IP), size = 202 bytes seldon -> trantor IP D=192.168.200.2 S=192.168.200.3 LEN=188, ID=59051 seldon -> trantor TCP D=1017 S=2049 Ack=11856860 Seq=171713445 Len=148 Win=8760 seldon -> trantor RPC R (#137) XID=1902072876 Success seldon -> trantor NFS R CREATE3 (unknown error) ________________________________ Anybody any idea ?? Paul -- Paul van der Zwan paulz @ trantor.stuyts.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 13:03:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16554 for freebsd-current-outgoing; Mon, 23 Nov 1998 13:03:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.insolwwb.net (ns.insolwwb.net [206.31.149.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16549 for ; Mon, 23 Nov 1998 13:03:16 -0800 (PST) (envelope-from mgrommet@insolwwb.net) Received: from mikeg (work2.insolwwb.net [208.150.248.12]) by ns.insolwwb.net (8.8.8/8.8.5) with SMTP id OAA01199; Mon, 23 Nov 1998 14:47:38 -0600 (CST) From: mike grommet Reply-To: To: "'Paul Richards'" , Subject: RE: Problems with this network card / driver? Date: Mon, 23 Nov 1998 15:03:00 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-reply-to: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paul, my concern is I may be loosing data, or at some point that this network card will become a problem... either the card is junk, or the driver needs some looking at. when I transfer fairly large files, or the machines network interface is busy I get lots of dropped packet messages coming from the kernel (in this case the machine acts as my usenet news server and it reguarly misses packets @ around 30k/sec) Of course the problem is much much worse when the traffic is heavier... This A.M. I put in an intel ethernet 10/100 in the machine above and havent had any of the problems mentioned... I have similar problems with an identical machine / NIC running as a webserver... although the load hasnt reached high enough to cause problems regularly as its not a very busy server, i did have the same problems when transerring large files in general to the machine. -----Original Message----- From: owner-freebsd-current@FreeBSD.ORG [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Paul Richards Sent: Monday, November 23, 1998 2:28 PM To: 'Mike Smith'; Mike Cc: freebsd-current@FreeBSD.ORG Subject: RE: Problems with this network card / driver? > -----Original Message----- > From: Mike Smith [mailto:mike@smith.net.au] > Sent: Sunday, November 22, 1998 9:11 PM > To: Mike > Cc: freebsd-current@FreeBSD.ORG > Subject: Re: Problems with this network card / driver? > > > > Hi guys... using 3.0 release on 2 servers....3.0 reports > this particular > > card like this on boot > > > > lnc1: rev 0x25 int a irq 14 on pci1.5.0 > > lnc1: PCnet-FAST address 00:60:94:57:4c:f2 > > Yeah. The lnc driver is pretty marginal at the moment. I'd avoid it > if at all possilble. I ran some tests at the local IBM > evaluation lab > and I wasn't too happy with the onboard ethernet. Try an Intel > EtherExpress Pro/100B instead if you're really concerned. Have you any specific details on why you think it's not working? It seems there's a bug been introduced recently relating to detecting cards that I'll look into but I'm not aware of any other problems with the driver that would make it necessary to avoid using it. In any case, I'm going to give the code an overhaul soon since I haven't looked at it for a few years so if you or anyone else has been having problems with this driver then now's the time to let me know :-) > > In any case should I be concerned at all? Like I said the > machine hums > > along perfectly but being the paranoid little guy that I > am, I want to know > > all the details before they > > reach up and bite me on the ass. > > If it's working OK, then it'll probably continue to work just fine. > It's quite likely that the BSD/OS driver just doesn't bother > to report > this error (which seems to indicate a very busy ethernet). This particular error report is perfectly normal and indicates a saturated network (assuming there aren't any bugs). It's true that one criticism that can be thrown at lnc is that it reports errors where many cards do not. I still claim that this is a good thing :-) Paul Richards Ph.D. Originative Solutions Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 13:05:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16966 for freebsd-current-outgoing; Mon, 23 Nov 1998 13:05:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16957 for ; Mon, 23 Nov 1998 13:05:45 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id IAA05834; Tue, 24 Nov 1998 08:10:35 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199811232110.IAA05834@cimlogic.com.au> Subject: Re: Elf linker question. In-Reply-To: from Julian Elischer at "Nov 23, 98 12:41:25 pm" To: julian@whistle.com (Julian Elischer) Date: Tue, 24 Nov 1998 08:10:35 +1100 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > I'm doing some work in a 3.0 system using the elf linker. > It seems that the new linker is insisting on me including libraries > that I never needed before.. In other words, I thin it's trying to resolve > symbols in functions I'm not using. Does anyone have comments on this? I guess you are linking against shared libraries? A static link should work as previously. > The old aout linker didn't need me to specify libraries that were not in > my call-graph. THe new one seems to need them. We now have standard binutils behaviour, like it or not. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 13:30:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19563 for freebsd-current-outgoing; Mon, 23 Nov 1998 13:30:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19543 for ; Mon, 23 Nov 1998 13:30:44 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.59.35]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA5EF5 for ; Mon, 23 Nov 1998 22:30:26 +0100 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: Mon, 23 Nov 1998 22:35:11 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: make world error dpt.h Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Current as of Monday around 21:00 GMT: ===> usr.bin/kdump cc -O -pipe -I/work/cvs/src/usr.bin/kdump/../ktrace -I/work/cvs/src/usr.bin/kdump/../.. -c /work/cvs/src/usr.bin/kdump/kdump.c cc -O -pipe -I/work/cvs/src/usr.bin/kdump/../ktrace -I/work/cvs/src/usr.bin/kdump/../.. -c /work/cvs/src/usr.bin/kdump/../ktrace/subr.c gzip -cn /work/cvs/src/usr.bin/kdump/kdump.1 > kdump.1.gz /bin/sh /work/cvs/src/usr.bin/kdump/mkioctls > ioctl.c cc -O -pipe -I/work/cvs/src/usr.bin/kdump/../ktrace -I/work/cvs/src/usr.bin/kdump/../.. -c ioctl.c In file included from ioctl.c:73: /usr/include/sys/dpt.h:1123: field `sc_scsi_link' has incomplete type ioctl.c: In function `ioctlname': ioctl.c:1662: `dpt_perf_t' undeclared (first use this function) ioctl.c:1662: (Each undeclared identifier is reported only once ioctl.c:1662: for each function it appears in.) *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 Did a make clean... and then a make... Going to cvsup again to see if I missed a commit... Let you know... --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 14:06:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23916 for freebsd-current-outgoing; Mon, 23 Nov 1998 14:06:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.mishkei.org.il ([62.0.64.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23907 for ; Mon, 23 Nov 1998 14:06:30 -0800 (PST) (envelope-from rom_glsa@ein-hashofet.co.il) Received: from ein-hashofet.co.il (host43-68.mishkei.org.il [62.0.68.43]) by mail.mishkei.org.il (8.8.5/8.8.5) with ESMTP id BAA21387 for ; Tue, 24 Nov 1998 01:05:23 +0200 Message-ID: <3659F860.E8309B47@ein-hashofet.co.il> Date: Tue, 24 Nov 1998 00:05:52 +0000 From: Gilad Rom X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I too have been experiencing random >> reboots, with no apparent reason. >I see an apparent reason. Keep reading. >> My machine is a Pentium 200Mhz overclocked to 233Mhz, >Stop that. At least until your system is 100% stable and does not >exhibit any symptoms which can be clearly traced to software. >- Jordan Well, I would, but I have been running this box overclocked for more than 6 months now, never had a glitch. Reboots only started back when other people reported such behaviour on the list as well. Im going to get a spare box and make a serial console off of it, see if I can get the panic message. -- Gilad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 14:12:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24413 for freebsd-current-outgoing; Mon, 23 Nov 1998 14:12:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24351 for ; Mon, 23 Nov 1998 14:11:55 -0800 (PST) (envelope-from forrie@navinet.net) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1/8.9.1) with SMTP id RAA00313 for ; Mon, 23 Nov 1998 17:11:44 -0500 (EST) Message-Id: <4.1.19981123164943.00a9ae60@206.25.93.69> X-Sender: forrie@206.25.93.8 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 23 Nov 1998 16:50:39 -0500 To: current@FreeBSD.ORG From: Forrest Aldrich Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <3659F860.E8309B47@ein-hashofet.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't had another reboot since the last time I reported it. At the time, I recall seeing a vfs_* file updated in cvs, and I'm wondering if that fixed the problem. I just did a build world, no problems. Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 14:19:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24984 for freebsd-current-outgoing; Mon, 23 Nov 1998 14:19:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24979 for ; Mon, 23 Nov 1998 14:19:08 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id OAA24221; Mon, 23 Nov 1998 14:26:53 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811232226.OAA24221@troutmask.apl.washington.edu> Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <43337.911854048@zippy.cdrom.com> from "Jordan K. Hubbard" at "Nov 23, 1998 12:47:28 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Mon, 23 Nov 1998 14:26:53 -0800 (PST) Cc: rom_glsa@ein-hashofet.co.il, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > > I too have been experiencing random > > reboots, with no apparent reason. > > I see an apparent reason. Keep reading. > > > My machine is a Pentium 200Mhz overclocked to 233Mhz, > > Stop that. At least until your system is 100% stable and does not > exhibit any symptoms which can be clearly traced to software. > Jordan, First, I agree he should stop overclocking. But, there really is a *subtle* bug. I've 4 to 5 crashes, but I haven't been able to get a dump. I've created and deleted 100's of MB of files (e.g., several make worlds). Then, on a seeming idle system, simply reading email can cause the problem. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 14:19:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25025 for freebsd-current-outgoing; Mon, 23 Nov 1998 14:19:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25017 for ; Mon, 23 Nov 1998 14:19:25 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id OAA00459; Mon, 23 Nov 1998 14:19:16 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811232219.OAA00459@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Forrest Aldrich cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Mon, 23 Nov 1998 16:50:39 EST." <4.1.19981123164943.00a9ae60@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 14:19:16 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup yesterday and I have been playing with my test box with no system crashes. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 14:28:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25936 for freebsd-current-outgoing; Mon, 23 Nov 1998 14:28:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25930 for ; Mon, 23 Nov 1998 14:28:51 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA20131; Mon, 23 Nov 1998 14:28:19 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id OAA00715; Mon, 23 Nov 1998 14:28:05 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 23 Nov 1998 14:28:05 -0800 (PST) Message-Id: <199811232228.OAA00715@vashon.polstra.com> To: rom_glsa@ein-hashofet.co.il Subject: Re: Random craches under heavy(?) disk activity Newsgroups: polstra.freebsd.current In-Reply-To: <3659F860.E8309B47@ein-hashofet.co.il> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3659F860.E8309B47@ein-hashofet.co.il>, Gilad Rom wrote: > >> I too have been experiencing random > >> reboots, with no apparent reason. > > >I see an apparent reason. Keep reading. > > >> My machine is a Pentium 200Mhz overclocked to 233Mhz, > > >Stop that. At least until your system is 100% stable and does not > >exhibit any symptoms which can be clearly traced to software. > > >- Jordan > > Well, I would, but I have been running this box > overclocked for more than 6 months now, never had > a glitch. Reboots only started back when other > people reported such behaviour on the list as well. > Im going to get a spare box and make a serial console > off of it, see if I can get the panic message. It doesn't make any difference how long your box has appeared to work. If you're overclocking it at all, we don't want to see your panic messages. They are too likely to mislead. It's just that simple. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 14:37:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27075 for freebsd-current-outgoing; Mon, 23 Nov 1998 14:37:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27070 for ; Mon, 23 Nov 1998 14:37:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id XAA05836; Mon, 23 Nov 1998 23:36:43 +0100 (CET) To: John Polstra cc: rom_glsa@ein-hashofet.co.il, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Mon, 23 Nov 1998 14:28:05 PST." <199811232228.OAA00715@vashon.polstra.com> Date: Mon, 23 Nov 1998 23:36:33 +0100 Message-ID: <5830.911860593@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199811232228.OAA00715@vashon.polstra.com>, John Polstra writes: >> Well, I would, but I have been running this box >> overclocked for more than 6 months now, never had >> a glitch. Reboots only started back when other >> people reported such behaviour on the list as well. >> Im going to get a spare box and make a serial console >> off of it, see if I can get the panic message. > >It doesn't make any difference how long your box has appeared to work. >If you're overclocking it at all, we don't want to see your panic >messages. They are too likely to mislead. It's just that simple. I would actually argue that the longer the box has been overclocked the warmer the cpu runs. Think "dusty fans" to follow the drift. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 14:43:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27720 for freebsd-current-outgoing; Mon, 23 Nov 1998 14:43:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27602 for ; Mon, 23 Nov 1998 14:43:04 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id RAA31187; Mon, 23 Nov 1998 17:41:26 -0500 (EST) Date: Mon, 23 Nov 1998 17:41:26 -0500 (EST) From: Chuck Robey To: Steve Kargl cc: "Jordan K. Hubbard" , rom_glsa@ein-hashofet.co.il, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <199811232226.OAA24221@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Nov 1998, Steve Kargl wrote: > According to Jordan K. Hubbard: > > > I too have been experiencing random > > > reboots, with no apparent reason. > > > > I see an apparent reason. Keep reading. > > > > > My machine is a Pentium 200Mhz overclocked to 233Mhz, > > > > Stop that. At least until your system is 100% stable and does not > > exhibit any symptoms which can be clearly traced to software. > > > > Jordan, > > First, I agree he should stop overclocking. But, there really > is a *subtle* bug. I've 4 to 5 crashes, but I haven't been > able to get a dump. > > I've created and deleted 100's of MB of files (e.g., several > make worlds). Then, on a seeming idle system, simply reading > email can cause the problem. Jordan didn't mean that, but he was completely correct (and should go on being stubborn about it). There's nothing worse, in doing troubleshooting, than making an assumption and going off into a blind alley for weeks, and trying to find a software problem in a system that's being overclocked is simply asking for it. Part of the price you pay for overclocking is needing to dial back the clock for any serious troubleshooting. Overclocking is basically unreliable; if it works, that's just fine, but the guarantee runs 60 seconds, max. The problem's real, but no trouble reports if you're overclocking, no excuses accepted. It's not all that hard to dial the clock back (and no, I don't overclock, myself, even though I do have a system that could do that well). ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 15:18:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00916 for freebsd-current-outgoing; Mon, 23 Nov 1998 15:18:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00906 for ; Mon, 23 Nov 1998 15:18:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00495; Mon, 23 Nov 1998 15:16:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811232316.PAA00495@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Paul Richards cc: Mike , freebsd-current@FreeBSD.ORG Subject: Re: Problems with this network card / driver? In-reply-to: Your message of "Mon, 23 Nov 1998 20:27:58 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 15:16:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Hi guys... using 3.0 release on 2 servers....3.0 reports > > this particular > > > card like this on boot > > > > > > lnc1: rev 0x25 int a irq 14 on pci1.5.0 > > > lnc1: PCnet-FAST address 00:60:94:57:4c:f2 > > > > Yeah. The lnc driver is pretty marginal at the moment. I'd avoid it > > if at all possilble. I ran some tests at the local IBM > > evaluation lab > > and I wasn't too happy with the onboard ethernet. Try an Intel > > EtherExpress Pro/100B instead if you're really concerned. > > Have you any specific details on why you think it's not working? It > seems there's a bug been introduced recently relating to detecting cards > that I'll look into but I'm not aware of any other problems with the > driver that would make it necessary to avoid using it. The key feature of all of the failures I can recall has been that the device is identified, but does not work (usually failing initialisation). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 15:42:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03710 for freebsd-current-outgoing; Mon, 23 Nov 1998 15:42:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from anch01.customcpu.com (anch01.customcpu.com [198.70.210.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03705 for ; Mon, 23 Nov 1998 15:42:37 -0800 (PST) (envelope-from al7oj@customcpu.com) Received: from FreeBSDrulz ([207.14.79.54]) by anch01.customcpu.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-42538U2500L250S0) with SMTP id AAA109 for ; Mon, 23 Nov 1998 14:42:37 -0900 From: "Michael A.Endsley" Reply-To: al7oj@customcpu.com To: freebsd-current@FreeBSD.ORG Subject: Installing 3.0-R from CD Date: Mon, 23 Nov 1998 14:28:57 -0900 X-Mailer: KMail [version 0.7.9] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <98112314415800.00439@FreeBSDrulz> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1). the new 3.0-R is fantastic! Great job to everyone involved 2). I have a Aptiva E-26 that I have FreeBSD 3.0 installed on. With the bios set to boot from cd, I am trying to install 3.0-R onto a new HD. The problem is that for some reason, it can't find the kernel. This is what I have tried: 1:wcd(0,a)kernel, 1:wcd(0,c)kernel, 0:wcd(0,c)kernel, 1:cd(0,c)kernel. Nothing that I type will work so that I can use the cd rather than a boot floppy. I have checked the maillists, the man pages, the FAQ and Handbook. So far, the answer has eluded me. What am I missing? 3). I had to try several times to get /stand/sysinstall to work after the "probing" when I installed FBSD on this HD. For some reason, the probe really messes with input from the keyboard. Whatever key I hit while in /stand/sysinstall, brings up a small window asking if I really want to quit. I checked the errata, but found nothing on this. Is this just my machine? Thanks for your help! Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 15:47:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04295 for freebsd-current-outgoing; Mon, 23 Nov 1998 15:47:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04290 for ; Mon, 23 Nov 1998 15:47:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00744; Mon, 23 Nov 1998 15:46:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811232346.PAA00744@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: al7oj@customcpu.com cc: freebsd-current@FreeBSD.ORG Subject: Re: Installing 3.0-R from CD In-reply-to: Your message of "Mon, 23 Nov 1998 14:28:57 -0900." <98112314415800.00439@FreeBSDrulz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 15:46:10 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1). the new 3.0-R is fantastic! Great job to everyone involved > 2). I have a Aptiva E-26 that I have FreeBSD 3.0 installed on. > With the bios set to boot from cd, I am trying to install 3.0-R onto a new > HD. The problem is that for some reason, it can't find the kernel. This is > what I have tried: 1:wcd(0,a)kernel, 1:wcd(0,c)kernel, 0:wcd(0,c)kernel, > 1:cd(0,c)kernel. Nothing that I type will work so that I can use the cd > rather than a boot floppy. I have checked the maillists, the man pages, > the FAQ and Handbook. So far, the answer has eluded me. > What am I missing? Don't type anything at the boot: prompt to boot from CD. Just stick the CDROM in and wait for it to boot automatically. > 3). I had to try several times to get /stand/sysinstall to work after the > "probing" when I installed FBSD on this HD. For some reason, the probe > really messes with input from the keyboard. Whatever key I hit while in > /stand/sysinstall, brings up a small window asking if I really want to > quit. I checked the errata, but found nothing on this. Is this just my > machine? This is a weird and not-yet-understood bug which sometimes occurs in sysinstall. We don't know what's causing it, sorry. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 15:53:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04860 for freebsd-current-outgoing; Mon, 23 Nov 1998 15:53:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from anch01.customcpu.com (anch01.customcpu.com [198.70.210.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04853 for ; Mon, 23 Nov 1998 15:53:19 -0800 (PST) (envelope-from al7oj@customcpu.com) Received: from FreeBSDrulz ([207.14.79.54]) by anch01.customcpu.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-42538U2500L250S0) with SMTP id AAA50; Mon, 23 Nov 1998 14:53:23 -0900 From: "Michael A.Endsley" Reply-To: al7oj@customcpu.com To: Mike Smith Subject: Re: Installing 3.0-R from CD Date: Mon, 23 Nov 1998 14:50:35 -0900 X-Mailer: KMail [version 0.7.9] Content-Type: text/plain Cc: freebsd-current@FreeBSD.ORG References: <199811232346.PAA00744@dingo.cdrom.com> MIME-Version: 1.0 Message-Id: <98112314524802.00439@FreeBSDrulz> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have sat here for about 2 minutes and just watched the "boot" prompt just keep flashing by. If I type "?" at the prompt, it will access the CD, but comes back saying that it can't find any files. How long should I try waiting? Thanks On Mon, 23 Nov 1998, Mike Smith wrote: >> 1). the new 3.0-R is fantastic! Great job to everyone involved >> 2). I have a Aptiva E-26 that I have FreeBSD 3.0 installed on. >> With the bios set to boot from cd, I am trying to install 3.0-R onto a new >> HD. The problem is that for some reason, it can't find the kernel. This is >> what I have tried: 1:wcd(0,a)kernel, 1:wcd(0,c)kernel, 0:wcd(0,c)kernel, >> 1:cd(0,c)kernel. Nothing that I type will work so that I can use the cd >> rather than a boot floppy. I have checked the maillists, the man pages, >> the FAQ and Handbook. So far, the answer has eluded me. >> What am I missing? > >Don't type anything at the boot: prompt to boot from CD. Just stick >the CDROM in and wait for it to boot automatically. > >> 3). I had to try several times to get /stand/sysinstall to work after the >> "probing" when I installed FBSD on this HD. For some reason, the probe >> really messes with input from the keyboard. Whatever key I hit while in >> /stand/sysinstall, brings up a small window asking if I really want to >> quit. I checked the errata, but found nothing on this. Is this just my >> machine? > >This is a weird and not-yet-understood bug which sometimes occurs in >sysinstall. We don't know what's causing it, sorry. > >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 16:05:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07044 for freebsd-current-outgoing; Mon, 23 Nov 1998 16:05:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07034 for ; Mon, 23 Nov 1998 16:05:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA00863; Mon, 23 Nov 1998 16:03:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811240003.QAA00863@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: al7oj@customcpu.com cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: Installing 3.0-R from CD In-reply-to: Your message of "Mon, 23 Nov 1998 14:50:35 -0900." <98112314524802.00439@FreeBSDrulz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 16:03:12 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have sat here for about 2 minutes and just watched the "boot" prompt just > keep flashing by. If I type "?" at the prompt, it will access the CD, but comes > back saying that it can't find any files. > How long should I try waiting? If it doesn't work first time, then there's something wrong with your BIOS or CDROM drive, and you'll have to boot from floppy. > Thanks > > > On Mon, 23 Nov 1998, Mike Smith wrote: > >> 1). the new 3.0-R is fantastic! Great job to everyone involved > >> 2). I have a Aptiva E-26 that I have FreeBSD 3.0 installed on. > >> With the bios set to boot from cd, I am trying to install 3.0-R onto a new > >> HD. The problem is that for some reason, it can't find the kernel. This is > >> what I have tried: 1:wcd(0,a)kernel, 1:wcd(0,c)kernel, 0:wcd(0,c)kernel, > >> 1:cd(0,c)kernel. Nothing that I type will work so that I can use the cd > >> rather than a boot floppy. I have checked the maillists, the man pages, > >> the FAQ and Handbook. So far, the answer has eluded me. > >> What am I missing? > > > >Don't type anything at the boot: prompt to boot from CD. Just stick > >the CDROM in and wait for it to boot automatically. > > > >> 3). I had to try several times to get /stand/sysinstall to work after the > >> "probing" when I installed FBSD on this HD. For some reason, the probe > >> really messes with input from the keyboard. Whatever key I hit while in > >> /stand/sysinstall, brings up a small window asking if I really want to > >> quit. I checked the errata, but found nothing on this. Is this just my > >> machine? > > > >This is a weird and not-yet-understood bug which sometimes occurs in > >sysinstall. We don't know what's causing it, sorry. > > > >-- > >\\ Sometimes you're ahead, \\ Mike Smith > >\\ sometimes you're behind. \\ mike@smith.net.au > >\\ The race is long, and in the \\ msmith@freebsd.org > >\\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 16:34:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10525 for freebsd-current-outgoing; Mon, 23 Nov 1998 16:34:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chrome.jdl.com (chrome.jdl.com [209.39.144.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10519 for ; Mon, 23 Nov 1998 16:34:50 -0800 (PST) (envelope-from jdl@chrome.jdl.com) Received: from localhost (localhost [127.0.0.1]) by chrome.jdl.com (8.8.4/8.8.4) with SMTP id SAA28165 for ; Mon, 23 Nov 1998 18:33:26 -0600 (CST) Message-Id: <199811240033.SAA28165@chrome.jdl.com> X-Authentication-Warning: chrome.jdl.com: localhost [127.0.0.1] didn't use HELO protocol To: current@FreeBSD.ORG Subject: Swap space? Clarity-Index: null Threat-Level: none Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code. Net-thought: If you meet the Buddha on the net, put him in your Kill file. Date: Mon, 23 Nov 1998 18:33:26 -0600 From: Jon Loeliger Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I'm running: rust 865 % uname -a FreeBSD rust.jdl.com 3.0-RELEASE FreeBSD 3.0-RELEASE #0: Sat Oct 17 17:45:06 GMT 1998 jkh@kickme.freebsd.org:/usr/src/sys/compile/GENERIC i386 With: rust 864 % df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1a 63503 17881 40542 31% / /dev/wd0s1g 2266862 216472 1869042 10% /u00 /dev/wd0s1f 508143 198932 268560 43% /usr /dev/wd0s1e 31743 1763 27441 6% /var /dev/wd1s1e 3075390 268807 2560552 10% /u01 procfs 4 4 0 100% /proc and: rust 866 % swapinfo Device 1K-blocks Used Avail Capacity Type /dev/wd0s1b 131072 46924 84020 36% Interleaved And finally, we have: Oct 19 21:28:55 rust /kernel: real memory = 33554432 (32768K bytes) Oct 19 21:28:55 rust /kernel: avail memory = 30113792 (29408K bytes) They mystery, we produced these two messages earlier today: swap_pager suggest more swap space: 60MB swap_Pager: out of swap space I'm not sure I believe either. Should I? Thanks, jdl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 16:44:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11308 for freebsd-current-outgoing; Mon, 23 Nov 1998 16:44:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rain.futuresouth.com (rain.futuresouth.com [198.79.79.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11297 for ; Mon, 23 Nov 1998 16:44:36 -0800 (PST) (envelope-from stormy@rain.futuresouth.com) Received: (from stormy@localhost) by rain.futuresouth.com (8.9.1/8.9.1) id SAA49461 for current@FreeBSD.ORG; Mon, 23 Nov 1998 18:46:13 -0600 (CST) (envelope-from stormy) Message-ID: <19981123184613.E48655@futuresouth.com> Date: Mon, 23 Nov 1998 18:46:13 -0600 From: Stormy Henderson To: current@FreeBSD.ORG Subject: Re: Swap space? Mail-Followup-To: current@FreeBSD.ORG References: <199811240033.SAA28165@chrome.jdl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811240033.SAA28165@chrome.jdl.com>; from Jon Loeliger on Mon, Nov 23, 1998 at 06:33:26PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A happy camper (Jon Loeliger, jdl@jdl.com) once wrote... > rust 866 % swapinfo > Device 1K-blocks Used Avail Capacity Type > /dev/wd0s1b 131072 46924 84020 36% Interleaved > > Oct 19 21:28:55 rust /kernel: real memory = 33554432 (32768K bytes) > Oct 19 21:28:55 rust /kernel: avail memory = 30113792 (29408K bytes) > swap_pager suggest more swap space: 60MB > swap_Pager: out of swap space > > I'm not sure I believe either. Should I? Why wouldn't you believe it? It isn't lying. (c: I ran out of swap a few times putzing in X, with 64MB of ram and 80MB swap, which totals about the same as yours. What was your machine doing at the time? I have 136MB of ram now, and I allotted 192MB of swap just to be on the safe side. All I do, still, is putz in X11. Be happy... -- http://www.futuresouth.com/~stormy/signature.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 16:49:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11865 for freebsd-current-outgoing; Mon, 23 Nov 1998 16:49:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11860 for ; Mon, 23 Nov 1998 16:48:56 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA14779; Mon, 23 Nov 1998 19:48:35 -0500 (EST) Date: Mon, 23 Nov 1998 19:48:35 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Mike Smith cc: Tom Bartol , Doug Rabson , freebsd-current@FreeBSD.ORG Subject: Re: NFS problems in -current In-Reply-To: <199811231730.JAA19160@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Nov 1998, Mike Smith wrote: > > Please ask a primary school teacher about "paragraphs". Sorry, I'm working on a good solutio, but basically right now I'm piping all my outgoing mail through fmt and losing any special formatting... I'll come up with a real solution soon. > > Please also make it clear whether you're using the old 'lpt' driver or > the newer ppbus code, so that we can work out what needs attention... I'm using the newer ppbus code entirely: controller ppbus0 device nlpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device pps0 at ppbus? controller ppc0 at isa? port ? tty irq 7 vector ppcintr ppc: parallel port found at 0x378 ppc0 at 0x378 irq 7 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 lppps0: on ppbus 0 plip0: on ppbus 0 > > > I'm having different problems. For instance, using FreeBSD 3.0-CURRENT > > (yesterday) as an NFS server, utilizing PLIP as my connection to > > a FreeBSD 3.0-RELEASE boot disk on an old WinBook. I was backing > > up the hard drive (cp /dev/rwd0a /mnt) and I tried running top > > because both systems were getting slow. Top on the desktop showed > > 8x% interrupt, is that software or hardware interrupts? After this, > > I wanted to see the traffic, so I did a trafshow -i lp0, and all > > of a sudden a flood of Fatal trap 12's happened on the desktop > > system. Basically, I could do nothing at this point, and had to do > > a hard reset. So, letting you know, something is broken here. Can > > I disable DDB for fatal traps, not just panic()'s, because I only > > wanted it enabled so I could drop into it at will to examine kernel > > state....? > > > > Brian Feldman _ __ ___ ___ ___ > > green@unixhelp.org _ __ ___ | _ ) __| \ > > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > I'll go check out the PR archives for info on BPF over PLIP, anyway. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 16:49:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11960 for freebsd-current-outgoing; Mon, 23 Nov 1998 16:49:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from anch01.customcpu.com (anch01.customcpu.com [198.70.210.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11950 for ; Mon, 23 Nov 1998 16:49:42 -0800 (PST) (envelope-from al7oj@customcpu.com) Received: from default ([207.14.79.59]) by anch01.customcpu.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-42538U2500L250S0) with SMTP id AAA115; Mon, 23 Nov 1998 15:49:42 -0900 Message-Id: <3.0.5.32.19981123154931.007bd930@customcpu.com> X-Sender: al7oj@customcpu.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 23 Nov 1998 15:49:31 -0900 To: Mike Smith From: "Michael A. Endsley" Subject: Re: Installing 3.0-R from CD Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199811240003.QAA00863@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks! Not what I wanted to read, but.... BTW- could your answer be the reason, that when doing a warm boot from Win95, the probe finds my CDROM drive (E-IDE 24X AKOx), but when doing a cold boot, the probe can't find the CDROM? Again, thanks Mike At 04:03 PM 11/23/98 -0800, Mike Smith wrote: > >If it doesn't work first time, then there's something wrong with your >BIOS or CDROM drive, and you'll have to boot from floppy. > __________________________________________________________ OS of CHOICE? UNIX (FreeBSD), LINUX (Debian), and OS/2Warp al7oj@customcpu.com http://www.customcpu.com/personal/al7oj/ __________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 16:56:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12471 for freebsd-current-outgoing; Mon, 23 Nov 1998 16:56:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from anch01.customcpu.com (anch01.customcpu.com [198.70.210.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12466 for ; Mon, 23 Nov 1998 16:56:56 -0800 (PST) (envelope-from al7oj@customcpu.com) Received: from default ([207.14.79.59]) by anch01.customcpu.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-42538U2500L250S0) with SMTP id AAA96; Mon, 23 Nov 1998 15:56:54 -0900 Message-Id: <3.0.5.32.19981123155643.007c83f0@customcpu.com> X-Sender: al7oj@customcpu.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 23 Nov 1998 15:56:43 -0900 To: Mike Smith From: "Michael A. Endsley" Subject: Re: Installing 3.0-R from CD Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <3.0.5.32.19981123154931.007bd930@customcpu.com> References: <199811240003.QAA00863@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I forgot to mention that the following question has to do with my presently installed 3.0-R. Sorry if it caused confusion. At 03:49 PM 11/23/98 -0900, Michael A. Endsley wrote: >Thanks! Not what I wanted to read, but.... >BTW- could your answer be the reason, that when doing a warm boot from >Win95, the probe finds my CDROM drive (E-IDE 24X AKOx), but when doing a >cold boot, the probe can't find the CDROM? >Again, thanks >Mike > > >At 04:03 PM 11/23/98 -0800, Mike Smith wrote: >> >>If it doesn't work first time, then there's something wrong with your >>BIOS or CDROM drive, and you'll have to boot from floppy. >> > >__________________________________________________________ >OS of CHOICE? UNIX (FreeBSD), LINUX (Debian), and OS/2Warp >al7oj@customcpu.com >http://www.customcpu.com/personal/al7oj/ > >__________________________________________________________ > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > __________________________________________________________ OS of CHOICE? UNIX (FreeBSD), LINUX (Debian), and OS/2Warp al7oj@customcpu.com http://www.customcpu.com/personal/al7oj/ __________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 16:59:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12792 for freebsd-current-outgoing; Mon, 23 Nov 1998 16:59:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12786 for ; Mon, 23 Nov 1998 16:59:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01266; Mon, 23 Nov 1998 16:57:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811240057.QAA01266@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Michael A. Endsley" cc: freebsd-current@FreeBSD.ORG Subject: Re: Installing 3.0-R from CD In-reply-to: Your message of "Mon, 23 Nov 1998 15:49:31 -0900." <3.0.5.32.19981123154931.007bd930@customcpu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 16:57:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks! Not what I wanted to read, but.... > BTW- could your answer be the reason, that when doing a warm boot from > Win95, the probe finds my CDROM drive (E-IDE 24X AKOx), but when doing a > cold boot, the probe can't find the CDROM? It sounds about right; there's something funny about your CDROM that is either "wrong" or just slightly strange that means that until W95 slaps it around we can't work with it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 17:10:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14127 for freebsd-current-outgoing; Mon, 23 Nov 1998 17:10:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14121 for ; Mon, 23 Nov 1998 17:10:28 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id RAA44785; Mon, 23 Nov 1998 17:11:41 -0800 (PST) To: Gilad Rom cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Tue, 24 Nov 1998 00:05:52 GMT." <3659F860.E8309B47@ein-hashofet.co.il> Date: Mon, 23 Nov 1998 17:11:40 -0800 Message-ID: <44781.911869900@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I would, but I have been running this box > overclocked for more than 6 months now, never had > a glitch. Reboots only started back when other I don't care. Just go back to your previous clock rate until things are working again. None of us want to see the panic message from an overclocked box - we've simply been burned far too many times. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 17:20:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15149 for freebsd-current-outgoing; Mon, 23 Nov 1998 17:20:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15144 for ; Mon, 23 Nov 1998 17:20:18 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id RAA44812; Mon, 23 Nov 1998 17:17:10 -0800 (PST) To: Poul-Henning Kamp cc: John Polstra , rom_glsa@ein-hashofet.co.il, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Mon, 23 Nov 1998 23:36:33 +0100." <5830.911860593@critter.freebsd.dk> Date: Mon, 23 Nov 1998 17:17:09 -0800 Message-ID: <44808.911870229@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I would actually argue that the longer the box has been overclocked > the warmer the cpu runs. I've also had OC'd boxes start failing. A trusty PPro 233 of mine ran OC'd for almost 2 years before finally starting to exhibit occasional flakiness. I now run it at 200 and it's happy again. Next to it sits another PPro which has run at 233 all its life without any problems *except* during the summer months, at which point things start doing the sig-11 dance. I keep it around deliberately in that configuration to show people who claim that OC'ing is entirely safe and a boolean go/no-go decision at worst. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 17:40:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16763 for freebsd-current-outgoing; Mon, 23 Nov 1998 17:40:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hsw.generalresources.com ([203.79.17.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16755 for ; Mon, 23 Nov 1998 17:40:33 -0800 (PST) (envelope-from hsw@email.generalresources.com) Received: from hsw.generalresources.com (localhost.generalresources.com [127.0.0.1]) by hsw.generalresources.com (8.9.1/8.9.1) with ESMTP id JAA09783 for ; Tue, 24 Nov 1998 09:39:47 +0800 (CST) (envelope-from hsw@hsw.generalresources.com) Message-Id: <199811240139.JAA09783@hsw.generalresources.com> To: freebsd-current@FreeBSD.ORG From: Christopher Hall Reply-to: Christopher Hall Subject: /boot/loader what to set rootdev to? X-Operating-System: FreeBSD 3.0 X-Mailer: exmh 2.0 Date: Tue, 24 Nov 1998 09:39:46 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From a cvsup and make world at Sat 1998/11/21. I made/installed new boot blocks and /boot/loader. Made an ELF kernel, did not create a boot config file, just hit enter at the timeoout prompt. Booted OK. The system only had da0 and da1. wd0 was disconnected. Problem occured when I reconnected wd0 (Primary IDE master). This has OS/2 boot manager - boot goes to the boot prompt. I can still boot properly with 1:sd(0,a)/kernel However, 1:sd(0,a)/boot/loader at the 'boot:' cannot boot properly. The loader prompts: "disk1s1a>" Which it lists as C: (IDE drive) (SCSI drives are shown as disk2 and disk3) Here are my boot attempts: (commands typed at loader prompt) 1) set currdev=disk2s1a: boot -> Changing root device to da1s1a error 22: panic: cannot mount root (2) 2) set currdev=disk2s1a: set rootdev=disk0s1a: boot -> mount: /dev/da0s1a on /: specified device does not match mounted device Filesystem mount failed, startup aborted Enter full pathname of shell or RETURN for /bin/sh: (press RETURN) which: not found which: not found # mount root_device on / (local, read-only) # mount / mount: /dev/da0s1a on /: specified device does not match mounted device # reboot 3) set currdev=disk2s1a: set rootdev=disk2s1a: boot -> Same result as 1) above. 4) set currdev=disk2s1a: set rootdev=disk3s1a: boot -> Changing root device to da2s1a Changing root device to da2a error 6: panic: cannot mount root (2) 5) tried leaving out ':' from rootdev and using 'da' instead of disk got a register dump followed by system halted. What should rootdev be set to when booting da0s1a with one IDE drive? --- Christopher Hall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 17:45:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17068 for freebsd-current-outgoing; Mon, 23 Nov 1998 17:45:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17063 for ; Mon, 23 Nov 1998 17:45:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id RAA20955; Mon, 23 Nov 1998 17:41:43 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id RAA01311; Mon, 23 Nov 1998 17:41:43 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <44808.911870229@zippy.cdrom.com> Date: Mon, 23 Nov 1998 17:41:43 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: "Jordan K. Hubbard" Subject: Re: Random craches under heavy(?) disk activity Cc: current@FreeBSD.ORG, rom_glsa@ein-hashofet.co.il, Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Nov-98 Jordan K. Hubbard wrote: >> I would actually argue that the longer the box has been overclocked >> the warmer the cpu runs. > > I've also had OC'd boxes start failing. A trusty PPro 233 of mine ran > OC'd for almost 2 years before finally starting to exhibit occasional > flakiness. I now run it at 200 and it's happy again. I wouldn't trust it even back at 200. Overclocking causes overheating, and it's not uniform overheating. Every chip has hot spots which get much hotter than others. Research has clearly shown that such localized overheating damages the chips, makes them less reliable, and shortens their lifetimes. I used to do a lot of consulting work for a company that built equipment for diagnosing problems in digital circuit boards. The goal was to find the bad chip on the board, and the essence of the process was to somehow inject test patterns that would stimulate the inputs of individual chips in controlled ways, and then see whether their outputs matched expectations. We investigated a technique called overdriving. The idea was that you used high-current drivers to just blast the test patterns into the chips' inputs, very briefly overwhelming the outputs of the chips that were driving those inputs. The hope was that we could keep the duration of the overdriving brief enough so that the other chips wouldn't be damaged. We abandoned it eventually. Even the shortest useful periods of overdriving were enough to reduce the lifetimes of the chips being overdriven. I believe that similar damage most likely occurs when you overclock a CPU. It doesn't mean a thing that the package feels cool. There can still be tiny spots on the chip that are badly overheated. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 17:51:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17668 for freebsd-current-outgoing; Mon, 23 Nov 1998 17:51:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17662 for ; Mon, 23 Nov 1998 17:51:57 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id RAA01834; Mon, 23 Nov 1998 17:51:52 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811240151.RAA01834@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Mon, 23 Nov 1998 17:17:09 PST." <44808.911870229@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 17:51:52 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A little while ago "rah" started crashing in the middle of the day after I upgraded the system . It turns out that the problem was that my power supply fan broke after I replaced the fan no crashes . Overclocking can be hazardous to your cpu chipset , I think it can can cause electro thermal migration -- you hose your cpu. I would overclock a cpu if I am ready to buy a new processor for sure I would not overclock a cpu if I am in show-string budget or can't afford to replace the system. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 17:53:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17879 for freebsd-current-outgoing; Mon, 23 Nov 1998 17:53:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17873 for ; Mon, 23 Nov 1998 17:53:43 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id UAA31644; Mon, 23 Nov 1998 20:52:36 -0500 (EST) Date: Mon, 23 Nov 1998 20:52:36 -0500 (EST) From: Chuck Robey To: John Polstra cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, rom_glsa@ein-hashofet.co.il, Poul-Henning Kamp Subject: Re: Random craches under heavy(?) disk activity 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, 23 Nov 1998, John Polstra wrote: > On 24-Nov-98 Jordan K. Hubbard wrote: > >> I would actually argue that the longer the box has been overclocked > >> the warmer the cpu runs. > > > > I've also had OC'd boxes start failing. A trusty PPro 233 of mine ran > > OC'd for almost 2 years before finally starting to exhibit occasional > > flakiness. I now run it at 200 and it's happy again. > > I wouldn't trust it even back at 200. Overclocking causes > overheating, and it's not uniform overheating. Every chip has hot > spots which get much hotter than others. Research has clearly shown > that such localized overheating damages the chips, makes them less > reliable, and shortens their lifetimes. > > I used to do a lot of consulting work for a company that built > equipment for diagnosing problems in digital circuit boards. The > goal was to find the bad chip on the board, and the essence of the > process was to somehow inject test patterns that would stimulate the > inputs of individual chips in controlled ways, and then see whether > their outputs matched expectations. We investigated a technique > called overdriving. The idea was that you used high-current drivers > to just blast the test patterns into the chips' inputs, very briefly > overwhelming the outputs of the chips that were driving those inputs. > The hope was that we could keep the duration of the overdriving brief > enough so that the other chips wouldn't be damaged. We abandoned > it eventually. Even the shortest useful periods of overdriving were > enough to reduce the lifetimes of the chips being overdriven. > > I believe that similar damage most likely occurs when you overclock a > CPU. It doesn't mean a thing that the package feels cool. There can > still be tiny spots on the chip that are badly overheated. An instructor of mine tells me that you can actually use a process that's kinda like silicon sandblasting, to leach away a small part of a chip, and literally look at failure modes. Something like very high energy sputtering ... Intel has used it to uncover bugs that would have taken months to discover using other analytical techniques. I'll have to ask him now about the failure scenario you're painting. > > John > --- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Nobody ever went broke underestimating the taste of the American public." > -- H. L. Mencken > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 18:12:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19436 for freebsd-current-outgoing; Mon, 23 Nov 1998 18:12:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19430 for ; Mon, 23 Nov 1998 18:12:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01652; Mon, 23 Nov 1998 18:10:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811240210.SAA01652@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Hall cc: freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Tue, 24 Nov 1998 09:39:46 +0800." <199811240139.JAA09783@hsw.generalresources.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 18:10:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >From a cvsup and make world at Sat 1998/11/21. > I made/installed new boot blocks and /boot/loader. > Made an ELF kernel, did not create a boot config file, just hit enter > at the timeoout prompt. Booted OK. > The system only had da0 and da1. wd0 was disconnected. > > Problem occured when I reconnected wd0 (Primary IDE master). > This has OS/2 boot manager - boot goes to the boot prompt. > > I can still boot properly with 1:sd(0,a)/kernel > However, 1:sd(0,a)/boot/loader at the 'boot:' cannot boot properly. > > The loader prompts: "disk1s1a>" Which it lists as C: (IDE drive) > (SCSI drives are shown as disk2 and disk3) ... > What should rootdev be set to when booting da0s1a with one IDE drive? Ignore $rootdev and instead set $num_ide_disks to 1. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 18:42:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22210 for freebsd-current-outgoing; Mon, 23 Nov 1998 18:42:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [207.149.232.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22168 for ; Mon, 23 Nov 1998 18:41:58 -0800 (PST) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.8/8.8.8) id SAA12771; Mon, 23 Nov 1998 18:37:15 -0800 (PST) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199811240237.SAA12771@GndRsh.aac.dev.com> Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <5830.911860593@critter.freebsd.dk> from Poul-Henning Kamp at "Nov 23, 98 11:36:33 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Tue, 24 Nov 1998 02:37:15 +0000 (GMT) Cc: jdp@polstra.com, rom_glsa@ein-hashofet.co.il, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199811232228.OAA00715@vashon.polstra.com>, John Polstra writes: > > >> Well, I would, but I have been running this box > >> overclocked for more than 6 months now, never had > >> a glitch. Reboots only started back when other > >> people reported such behaviour on the list as well. > >> Im going to get a spare box and make a serial console > >> off of it, see if I can get the panic message. > > > >It doesn't make any difference how long your box has appeared to work. > >If you're overclocking it at all, we don't want to see your panic > >messages. They are too likely to mislead. It's just that simple. > > I would actually argue that the longer the box has been overclocked > the warmer the cpu runs. > > Think "dusty fans" to follow the drift. And in reality electromigration is something that takes some amount of time to occur. The additional heat created by overclocking the chip doesn't just cause problems instantly, it takes quite some time for the process to occur. It may run fine for a day, a week, a month, or even a year before enough damage occurs to cause a failure mode. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 18:49:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22771 for freebsd-current-outgoing; Mon, 23 Nov 1998 18:49:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from emu.sourcee.com (emu.sourcee.com [199.201.159.173]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22766 for ; Mon, 23 Nov 1998 18:49:33 -0800 (PST) (envelope-from nrice@emu.sourcee.com) Received: (from nrice@localhost) by emu.sourcee.com (8.9.1/8.9.1) id VAA13275; Mon, 23 Nov 1998 21:49:02 -0500 (EST) Message-ID: <19981123214901.A13260@emu.sourcee.com> Date: Mon, 23 Nov 1998 21:49:01 -0500 From: "Norman C. Rice" To: Bruce Evans , mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: Breakage in -current for the ALPHA References: <199811231616.DAA03041@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811231616.DAA03041@godzilla.zeta.org.au>; from Bruce Evans on Tue, Nov 24, 1998 at 03:16:57AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 24, 1998 at 03:16:57AM +1100, Bruce Evans wrote: > >> They traditionally go in sys (e.g., ttycom.h). Of course, there is > >> no such thing as a machine independant driver API. There isn't even > >> such a thing as a machine independent driver API. > > > >Eh? The second sentence might have been 'machine *dependent*'? > > > >In either case, what do you mean? There most certainly is both a DDI and > >DKI for *BSD. There are MI functions (even in FreeBSD which is > >historically less sensitive to MI vs MD issues) such as bcopy (DKI) or > >devswitch functions. There are MD functions such as isa_configure (DDI). > > 1. Mispelling of `dependent' is annoying. ^^^^^^^^^^ The misspelling of `misspelling' when trying to make a point about correct spelling is also annoying. :) -- Regards, Norman C. Rice, Jr. > 2. Nothing is really machine independent. > > Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 18:53:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23256 for freebsd-current-outgoing; Mon, 23 Nov 1998 18:53:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23247 for ; Mon, 23 Nov 1998 18:53:19 -0800 (PST) (envelope-from aw1@stade.co.uk) Received: (from aw1@localhost) by stade.demon.co.uk (8.9.1/8.9.1) id CAA00844 for current@FreeBSD.ORG; Tue, 24 Nov 1998 02:50:11 GMT (envelope-from aw1) Message-ID: <19981124025011.A832@stade.co.uk> Date: Tue, 24 Nov 1998 02:50:11 +0000 From: Adrian Wontroba To: current@FreeBSD.ORG Subject: Re: kernel make failure in smbus Reply-To: aw1@stade.co.uk References: <199811222006.MAA00385@rah.star-gate.com> <199811222106.XAA00350@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811222106.XAA00350@greenpeace.grondar.za>; from Mark Murray on Sun, Nov 22, 1998 at 11:06:46PM +0200 Organization: Stade Computers Ltd, UK X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 22, 1998 at 11:06:46PM +0200, Mark Murray wrote: > My card is not a Miro, and it is not NTSC. I believe this is unrelated > to Doug's patches, which should go in. Shall I do the honours? Card detection has been iffy since the bktr driver was changed to use the iic/smbus stuff - setting the hw.bt848.(card|tuner|reverse_mute) oids on startup is the easy way of dealing with it. Now the honours are done, the kernel compiles and fxtv works. -- Adrian Wontroba, Stade Computers Limited. phone: (+44) 121 681 6677 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 19:06:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24559 for freebsd-current-outgoing; Mon, 23 Nov 1998 19:06:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24552 for ; Mon, 23 Nov 1998 19:06:54 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id EAA26261 for freebsd-current@FreeBSD.ORG; Tue, 24 Nov 1998 04:06:39 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 599DC14FA; Tue, 24 Nov 1998 01:15:12 +0100 (CET) Date: Tue, 24 Nov 1998 01:15:12 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Adaptec SCSI messages Message-ID: <19981124011512.B11237@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <19981114144915.A244@zappa.demon.nl> <19981117112118.A252@zappa.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <19981117112118.A252@zappa.demon.nl>; from Ron Klinkien on Tue, Nov 17, 1998 at 11:21:18AM +0100 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4829 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Ron Klinkien: > Strange though that after doubling the data transfer rate from 40 -> 80Mb/s > iozone 100 doesn't reports any increase of speed. Because you have enlarged the _bus_ by two doesn't mean the drive is able to move bytes faster from the platters. You are now able to put more disks before saturating the SCSI bus but bear in mind that it is very unlikely that you'll be ever eble to saturate a 80 MB/s bus with only one drive. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 20:34:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03114 for freebsd-current-outgoing; Mon, 23 Nov 1998 20:34:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hilly ([203.8.2.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA03100 for ; Mon, 23 Nov 1998 20:34:41 -0800 (PST) (envelope-from tshoumack@rpmsolutions.com.au) Received: from harrier.rpmsolutions.com.au ([150.101.22.224]) by hilly (SMI-8.6/8.6.6) with SMTP id PAA01070 for ; Tue, 24 Nov 1998 15:07:20 +1030 Received: by localhost with Microsoft MAPI; Tue, 24 Nov 1998 14:59:40 +1030 Message-ID: <01BE17BB.0F9B1EE0.tshoumack@rpmsolutions.com.au> From: Tony Shoumack Reply-To: "Tony.Shoumack@rpmsolutions.com.au" To: "'freebsd-current@freebsd.org'" Subject: Idiots guide to PCMCIA Date: Tue, 24 Nov 1998 14:59:34 +1030 Organization: RPM Solutions Australia Pty Ltd X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 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 there, Not sure which forum to post this .. here goes. As a newbie to FreeBSD (and loving it) I am keen to get stuck into perpherial support and am wondering if there is much on PCMCIA - as I see the handbook notes "write documentation" as todo for this area. I think I really need more of an "Idiots Guide to PCMCIA" Any information is welcomed. Cheers, Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 20:35:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03405 for freebsd-current-outgoing; Mon, 23 Nov 1998 20:35:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03400 for ; Mon, 23 Nov 1998 20:35:47 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id XAA02034; Mon, 23 Nov 1998 23:35:35 -0500 (EST) Date: Mon, 23 Nov 1998 23:35:35 -0500 (EST) From: Daniel Eischen Message-Id: <199811240435.XAA02034@pcnet1.pcnet.com> To: eischen@vigrid.com, jdp@polstra.com Subject: Re: aout-to-elf-build failure in libpam Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This *may* have been fixed by my commit of "src/lib/libskey/Makefile" > revision 1.14 on Sunday. Could you please try it and see if that > helps? I just finished a make aout-to-elf-build without problem after the libskey/Makefile change. Thanks! Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 20:52:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05123 for freebsd-current-outgoing; Mon, 23 Nov 1998 20:52:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05118 for ; Mon, 23 Nov 1998 20:52:26 -0800 (PST) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.9.1/8.9.1) id MAA28823; Tue, 24 Nov 1998 12:52:24 +0800 (GMT) Date: Tue, 24 Nov 1998 12:52:24 +0800 (GMT) From: Michael Robinson Message-Id: <199811240452.MAA28823@public.bta.net.cn> To: Tony.Shoumack@rpmsolutions.com.au, freebsd-current@FreeBSD.ORG Subject: Re: Idiots guide to PCMCIA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I think I really need more of an "Idiots Guide to PCMCIA" >Any information is welcomed. http://www.jp.FreeBSD.org/PAO/ -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 20:59:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05913 for freebsd-current-outgoing; Mon, 23 Nov 1998 20:59:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05905 for ; Mon, 23 Nov 1998 20:59:05 -0800 (PST) (envelope-from marc@netcologne.de) Received: from oranje.my.domain (dial10-44.netcologne.de [195.14.235.44]) by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id FAA13021; Tue, 24 Nov 1998 05:58:58 +0100 (MET) X-Ncc-Regid: de.netcologne Received: (from marc@localhost) by oranje.my.domain (8.9.1/8.9.1) id GAA00789; Tue, 24 Nov 1998 06:00:03 +0100 (CET) (envelope-from marc) Date: Tue, 24 Nov 1998 06:00:03 +0100 (CET) Message-Id: <199811240500.GAA00789@oranje.my.domain> From: Marc van Woerkom To: freebsd-current@FreeBSD.ORG CC: joki@kuebart.stuttgart.netsurf.de, hm@kts.org Subject: update visual kernel config Reply-to: van.woerkom@netcologne.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I put this in my local /sys/i386/i386/userconfig.c *** userconfig.c.orig Tue Nov 24 02:54:11 1998 --- userconfig.c Tue Nov 24 05:38:49 1998 *************** *** 355,360 **** --- 355,361 ---- {"lpt", "Parallel printer port", 0, CLS_COMMS}, {"ppc", "Parallel Port chipset", 0, CLS_COMMS}, {"gp", "National Instruments AT-GPIB/TNT driver", 0, CLS_COMMS}, + {"isic", "Siemens chipset based CCITT I.430 ISDN driver", 0, CLS_COMMS}, {"mse", "Microsoft Bus Mouse", 0, CLS_INPUT}, {"psm", "PS/2 Mouse", 0, CLS_INPUT}, *************** *** 377,382 **** --- 378,384 ---- {"mpu", "Roland MPU401 MIDI", 0, CLS_MMEDIA}, {"sscape", "Ensoniq Soundscape MIDI interface", 0, CLS_MMEDIA}, {"sscape_mss", "Ensoniq Soundscape PCM", 0, CLS_MMEDIA}, + {"es", "Ensoniq ES1370 & AK4531 PCM (Audio PCI)", FLG_IMMUTABLE, CLS_MMEDIA}, {"uart", "6850 MIDI UART", 0, CLS_MMEDIA}, {"pca", "PC speaker PCM audio driver", FLG_FIXED, CLS_MMEDIA}, {"ctx", "Coretex-I frame grabber", 0, CLS_MMEDIA}, Regards, Marc (CCed to the authors of these fine drivers) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 21:07:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06775 for freebsd-current-outgoing; Mon, 23 Nov 1998 21:07:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06770 for ; Mon, 23 Nov 1998 21:07:57 -0800 (PST) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with ESMTP id WAA27541; Mon, 23 Nov 1998 22:07:32 -0700 (MST) (envelope-from handy@lambic.physics.montana.edu) Date: Mon, 23 Nov 1998 22:07:32 -0700 (MST) From: Brian Handy To: Tony.Shoumack@rpmsolutions.com.au cc: freebsd-current@FreeBSD.ORG Subject: Re: Idiots guide to PCMCIA In-Reply-To: <199811240452.MAA28823@public.bta.net.cn> Message-ID: X-files: The truth is out there 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, 24 Nov 1998, Michael Robinson wrote: >>I think I really need more of an "Idiots Guide to PCMCIA" >>Any information is welcomed. > >http://www.jp.FreeBSD.org/PAO/ I'll guess this isn't quite what he was looking for, but what the heck... I often wonder where our PCCARD experts get their information. The only doc[s] I've ever seen (aside from stumbling over stuff on web pages from 3Com and friends) is this giant notebook-looking creation I saw at a bookstore in Palo Alto once. Can't remember the name of it now, but looked cool at the time...if I was more of a contributor and less of a bottom feeder, I may have picked up that copy. :-) Good luck, Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 21:10:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07140 for freebsd-current-outgoing; Mon, 23 Nov 1998 21:10:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07094 for ; Mon, 23 Nov 1998 21:09:59 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA04542; Tue, 24 Nov 1998 16:09:38 +1100 Date: Tue, 24 Nov 1998 16:09:38 +1100 From: Bruce Evans Message-Id: <199811240509.QAA04542@godzilla.zeta.org.au> To: green@unixhelp.org, mike@smith.net.au Subject: Re: NFS problems in -current Cc: bartol@salk.edu, dfr@nlsystems.com, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Please also make it clear whether you're using the old 'lpt' driver or >> the newer ppbus code, so that we can work out what needs attention... > >I'm using the newer ppbus code entirely: > >controller ppbus0 >device nlpt0 at ppbus? >device plip0 at ppbus? >device ppi0 at ppbus? >device pps0 at ppbus? > >controller ppc0 at isa? port ? tty irq 7 vector ppcintr ^^^ ppc must be a `net' device for plip to work properly. See the plip man page. ppc must also be a `tty' device for lpt0 and a `cam' device for vp0. These requirements conflict. lpt0 and lp0 have related bugs. lpt0 needs to be a `net' device for lp0 to work. This can be configured by specifying that it is a `tty' device and statically configuring slip. PR: 5699, 6099 The slip LKM has related bugs. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 21:29:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08557 for freebsd-current-outgoing; Mon, 23 Nov 1998 21:29:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08550 for ; Mon, 23 Nov 1998 21:29:14 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA06559; Tue, 24 Nov 1998 16:28:57 +1100 Date: Tue, 24 Nov 1998 16:28:57 +1100 From: Bruce Evans Message-Id: <199811240528.QAA06559@godzilla.zeta.org.au> To: bde@zeta.org.au, green@unixhelp.org, mike@smith.net.au Subject: Re: NFS problems in -current Cc: bartol@salk.edu, dfr@nlsystems.com, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >lpt0 and lp0 have related bugs. lpt0 needs to be a `net' device for >lp0 to work. This can be configured by specifying that it is a `tty' >device and statically configuring slip. >PR: 5699, 6099 ^^^^ oops, should be 5698 Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 21:59:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10993 for freebsd-current-outgoing; Mon, 23 Nov 1998 21:59:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10988 for ; Mon, 23 Nov 1998 21:59:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA02812; Mon, 23 Nov 1998 21:58:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811240558.VAA02812@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Tony.Shoumack@rpmsolutions.com.au" cc: "'freebsd-current@freebsd.org'" Subject: Re: Idiots guide to PCMCIA In-reply-to: Your message of "Tue, 24 Nov 1998 14:59:34 +1030." <01BE17BB.0F9B1EE0.tshoumack@rpmsolutions.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 21:58:12 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi there, > > Not sure which forum to post this .. here goes. > > As a newbie to FreeBSD (and loving it) I am keen to > get stuck into perpherial support and am wondering > if there is much on PCMCIA - as I see the handbook > notes "write documentation" as todo for this area. > > I think I really need more of an "Idiots Guide to PCMCIA" The simple, and unhelpful, answer is that PCMCIA is too complicated for idiots. The handbook section on PCCARD stuff is still empty because anybody that knows anything about our support is either too busy or too embarrassed to write anything about it. If you want to write documentation about peripheral support, that's one thing, and a very worthwhile exercise it is too. In that case, there's lots of stuff to do, and you ought to ask more questions to work out where your efforts might best be spent. If you want to work on writing support *code*, then you should talk to Garrett Wollman (wollman@freebsd.org), who is currently undertaking the not insubstantial task of renovating our ISA support. I'm sure that he has quite a lot of work that he could do with some help with, and if you feel you're able to pick stuff up quickly, there's plenty to do there. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 22:22:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12933 for freebsd-current-outgoing; Mon, 23 Nov 1998 22:22:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12928 for ; Mon, 23 Nov 1998 22:22:26 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id WAA00757 for ; Mon, 23 Nov 1998 22:22:21 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811240622.WAA00757@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: pam can't open module error messages Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Nov 1998 22:22:20 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am getting the following error messages every time I log in to the system with a recent -current.... Amancio Nov 23 22:10:07 cioloco login: [dlerror: Cannot open "/usr/lib/pam_cracklib.so"] Nov 23 22:10:07 cioloco login: adding faulty module: /usr/lib/pam_cracklib.so Nov 23 22:10:07 cioloco login: unable to dlopen(/usr/lib/pam_deny.so) Nov 23 22:10:07 cioloco login: [dlerror: Cannot open "/usr/lib/pam_deny.so"] Nov 23 22:10:07 cioloco login: adding faulty module: /usr/lib/pam_deny.so Nov 23 22:10:07 cioloco login: unable to dlopen(/usr/lib/pam_warn.so) Nov 23 22:10:07 cioloco login: [dlerror: Cannot open "/usr/lib/pam_warn.so"] Nov 23 22:10:07 cioloco login: adding faulty module: /usr/lib/pam_warn.so Nov 23 22:10:07 cioloco login: auth_pam: Module is unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 23 23:34:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17810 for freebsd-current-outgoing; Mon, 23 Nov 1998 23:34:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17803 for ; Mon, 23 Nov 1998 23:34:47 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA02274; Tue, 24 Nov 1998 08:34:19 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199811240734.IAA02274@freebsd.dk> Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <199811232226.OAA24221@troutmask.apl.washington.edu> from Steve Kargl at "Nov 23, 1998 2:26:53 pm" To: sgk@troutmask.apl.washington.edu (Steve Kargl) Date: Tue, 24 Nov 1998 08:34:18 +0100 (CET) Cc: jkh@zippy.cdrom.com, rom_glsa@ein-hashofet.co.il, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Steve Kargl wrote: > According to Jordan K. Hubbard: > > > I too have been experiencing random > > > reboots, with no apparent reason. > > > > I see an apparent reason. Keep reading. > > > > > My machine is a Pentium 200Mhz overclocked to 233Mhz, > > > > Stop that. At least until your system is 100% stable and does not > > exhibit any symptoms which can be clearly traced to software. > > > > Jordan, > > First, I agree he should stop overclocking. But, there really > is a *subtle* bug. I've 4 to 5 crashes, but I haven't been > able to get a dump. > > I've created and deleted 100's of MB of files (e.g., several > make worlds). Then, on a seeming idle system, simply reading > email can cause the problem. Try do a "sysctl -w vfs.ffs.doreallocblks=0" that may fix the problem, at least is has solved a very semilar looking problem for me (and no I dont overclock :) ) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Nov 23 23:42:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18599 for freebsd-current-outgoing; Mon, 23 Nov 1998 23:42:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18577 for ; Mon, 23 Nov 1998 23:41:59 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA17412; Tue, 24 Nov 1998 18:41:35 +1100 Date: Tue, 24 Nov 1998 18:41:35 +1100 From: Bruce Evans Message-Id: <199811240741.SAA17412@godzilla.zeta.org.au> To: archie@whistle.com, bde@zeta.org.au Subject: Re: snprintf() in the kernel Cc: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG, grog@lemis.com, rnordier@nordier.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Thanks to those who checked out the snprintf() patches. "Rev 2" is now >available in ftp://ftp.whistle.com/pub/archie/misc. I took out >a bunch of strncpy() patches and tweaked a couple of other things. It would be better without any strncpy() patches. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 00:43:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23606 for freebsd-current-outgoing; Tue, 24 Nov 1998 00:43:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23601 for ; Tue, 24 Nov 1998 00:43:08 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id AAA10347; Tue, 24 Nov 1998 00:42:02 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma010345; Tue, 24 Nov 98 00:41:56 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id AAA03369; Tue, 24 Nov 1998 00:41:56 -0800 (PST) From: Archie Cobbs Message-Id: <199811240841.AAA03369@bubba.whistle.com> Subject: Re: snprintf() in the kernel In-Reply-To: <199811240741.SAA17412@godzilla.zeta.org.au> from Bruce Evans at "Nov 24, 98 06:41:35 pm" To: bde@zeta.org.au (Bruce Evans) Date: Tue, 24 Nov 1998 00:41:56 -0800 (PST) Cc: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG, grog@lemis.com, rnordier@nordier.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > >Thanks to those who checked out the snprintf() patches. "Rev 2" is now > >available in ftp://ftp.whistle.com/pub/archie/misc. I took out > >a bunch of strncpy() patches and tweaked a couple of other things. > > It would be better without any strncpy() patches. Well, it's certainly easy enough to take them out.. however, some are bug fixes... For example, if a function takes a string argument, when can you assume an upper bound on how long the string is? If you "know" it can't be too long then sure, you don't need to check. But unless that's obvious by looking at it (with someone else's eyes, someone who didn't write the code) then for maintainability's sake why not just be safe...? Especially if someone else wanted to change strings and or buffer sizes later. Eg, on alpha a printed "long" may be longer than 10 characters or whatever. When it comes to maintainability, the less dependent things you have to change (and by implication, know about) in order to make a single change, the better.. Of the strncpy() replacements, there are three categories: - "Possibly unterminated string", where one is required: netatm/spans/spans_print.c netatm/uni/uniarp_cache.c pc98/pc98/diskslice_machdep.c pci/pci_compat.c - "Simplification" (eg, replacing constants like "16" with sizeof()) with otherwise no functional effect (including strncpy()'s zero'ing out of the buffer): i386/ibcs2/ibcs2_stat.c i386/ibcs2/ibcs2_xenix.c i386/linux/linux_misc.c netinet/ip_divert.c - "Gratuitous" (?) alpha/tc/tcds.c dev/dpt/dpt_control.c kern/subr_devstat.c netatm/atm_aal5.c netatm/atm_socket.c Tell me which (or all) of these you don't want and I'll take them out; however my instinct would say to keep the first two sets. If it's performance you're thinking about, my general assumption is that string manipulation in the kernel is uncommon, but that could be wrong. Thanks for reviewing :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 01:00:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25335 for freebsd-current-outgoing; Tue, 24 Nov 1998 01:00:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25330 for ; Tue, 24 Nov 1998 01:00:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id BAA13142; Tue, 24 Nov 1998 01:00:15 -0800 (PST) (envelope-from dillon) Date: Tue, 24 Nov 1998 01:00:15 -0800 (PST) From: Matthew Dillon Message-Id: <199811240900.BAA13142@apollo.backplane.com> To: Archie Cobbs Cc: bde@zeta.org.au (Bruce Evans), freebsd-current@FreeBSD.ORG, grog@lemis.com, rnordier@nordier.com Subject: Re: snprintf() in the kernel References: <199811240841.AAA03369@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Well, it's certainly easy enough to take them out.. however, some :are bug fixes... : :For example, if a function takes a string argument, when can you :assume an upper bound on how long the string is? :... I have a suggestion, why not split the problem up... commit the kernel snprintf() subroutine first, then put up a small subset of the snprintf() changes up for review and commit those on a fast track. i.e. get some of the more obvious sprintf() -> snprintf() fixes in and proven. *then*, after all of that is under our belts, we can start discussing more involved changes. This is much better then trying to throw everything at us in one big gulp. This sort of thing does not have to be an all-or-nothing proposition. Personally, I think we need to move to length-limited copies for all string operations. The code may be correct as is, and it may seem obvious to the people who wrote it, but FreeBSD is a collective effort and the more mistakes we can prevent in the future without compromising code effectiveness the better. -Matt ___________________________________________________________________________ :Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 01:26:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27813 for freebsd-current-outgoing; Tue, 24 Nov 1998 01:26:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27748 for ; Tue, 24 Nov 1998 01:25:58 -0800 (PST) (envelope-from root@zappa.demon.nl) Received: (from root@localhost) by zappa.demon.nl (8.9.1/8.8.8) id KAA00629; Tue, 24 Nov 1998 10:27:06 +0100 (CET) (envelope-from root) Message-ID: <19981124102706.A613@zappa.demon.nl> Date: Tue, 24 Nov 1998 10:27:06 +0100 From: Ron Klinkien To: Steve Kargl , "Jordan K. Hubbard" Cc: rom_glsa@ein-hashofet.co.il, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity References: <43337.911854048@zippy.cdrom.com> <199811232226.OAA24221@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811232226.OAA24221@troutmask.apl.washington.edu>; from Steve Kargl on Mon, Nov 23, 1998 at 02:26:53PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 23, 1998 at 02:26:53PM -0800, Steve Kargl wrote: > According to Jordan K. Hubbard: > > > I too have been experiencing random > > > reboots, with no apparent reason. > > > > I see an apparent reason. Keep reading. > > > > > My machine is a Pentium 200Mhz overclocked to 233Mhz, > > > > Stop that. At least until your system is 100% stable and does not > > exhibit any symptoms which can be clearly traced to software. > > > > Jordan, > > First, I agree he should stop overclocking. But, there really > is a *subtle* bug. I've 4 to 5 crashes, but I haven't been > able to get a dump. > > I've created and deleted 100's of MB of files (e.g., several > make worlds). Then, on a seeming idle system, simply reading > email can cause the problem. > > -- > Steve > > finger kargl@troutmask.apl.washington.edu > http://troutmask.apl.washington.edu/~clesceri/kargl.html > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message My system is: ASUS P2B-S PII 333Mhz 128Mb Mem, U2W SCSI Disk, FreeBSD 3.0-CURRENT I only run the standard full system install with KDE 1.0 and Netscape 4.5 If i don't do a: sysctl -w vfs.ffs.doreallocblks=0 The system won't survive longer than a day, it usally reboots when performing standard cron stuff on 2.00AM Ron. --- "You could jam in Joe's garage..." -FZ Ron Klinkien System Engineer ron@zappa.demon.nl http://www.zappa.demon.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 01:34:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28502 for freebsd-current-outgoing; Tue, 24 Nov 1998 01:34:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28476 for ; Tue, 24 Nov 1998 01:33:58 -0800 (PST) (envelope-from root@zappa.demon.nl) Received: (from root@localhost) by zappa.demon.nl (8.9.1/8.8.8) id KAA01061 for freebsd-current@FreeBSD.ORG; Tue, 24 Nov 1998 10:35:32 +0100 (CET) (envelope-from root) Message-ID: <19981124103532.B613@zappa.demon.nl> Date: Tue, 24 Nov 1998 10:35:32 +0100 From: Ron Klinkien To: freebsd-current@FreeBSD.ORG Subject: Re: Adaptec SCSI messages References: <19981114144915.A244@zappa.demon.nl> <19981117112118.A252@zappa.demon.nl> <19981124011512.B11237@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981124011512.B11237@keltia.freenix.fr>; from Ollivier Robert on Tue, Nov 24, 1998 at 01:15:12AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 24, 1998 at 01:15:12AM +0100, Ollivier Robert wrote: > According to Ron Klinkien: > > Strange though that after doubling the data transfer rate from 40 -> 80Mb/s > > iozone 100 doesn't reports any increase of speed. > > Because you have enlarged the _bus_ by two doesn't mean the drive is able > to move bytes faster from the platters. > > You are now able to put more disks before saturating the SCSI bus but bear > in mind that it is very unlikely that you'll be ever eble to saturate a 80 > MB/s bus with only one drive. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- I guess you are right, but i wonder why they have invented Ultra 2 disks then. Since my disk performed in Single Ended mode exactly the same as in ULTRA2-LVD mode. --- cut --- zappa# iozone 100 IOZONE: Performance Test of Sequential File I/O -- V2.01 (10/21/94) By Bill Norcott Operating System: FreeBSD 2.x -- using fsync() Send comments to: b_norcott@xway.com IOZONE writes a 100 Megabyte sequential file consisting of 204800 records which are each 512 bytes in length. It then reads the file. It prints the bytes-per-second rate at which the computer can read and write files. Writing the 100 Megabyte file, 'iozone.tmp'...9.742188 seconds Reading the file...9.062500 seconds IOZONE performance measurements: 10763250 bytes/second for writing the file 11570493 bytes/second for reading the file zappa# --- cut --- I was hoping it did better than this. Hmm and strange it reports FreeBSD 2.x Ron. --- "You could jam in Joe's garage..." -FZ Ron Klinkien System Engineer ron@zappa.demon.nl http://www.zappa.demon.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 01:39:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29031 for freebsd-current-outgoing; Tue, 24 Nov 1998 01:39:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA29023 for ; Tue, 24 Nov 1998 01:39:30 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 16974 invoked by uid 1001); 24 Nov 1998 09:39:25 +0000 (GMT) To: root@zappa.demon.nl Cc: freebsd-current@FreeBSD.ORG Subject: Re: Adaptec SCSI messages In-Reply-To: Your message of "Tue, 24 Nov 1998 10:35:32 +0100" References: <19981124103532.B613@zappa.demon.nl> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 24 Nov 1998 10:39:25 +0100 Message-ID: <16972.911900365@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I guess you are right, but i wonder why they have invented Ultra 2 disks > then. Since my disk performed in Single Ended mode exactly the same as > in ULTRA2-LVD mode. As Ollivier Robert said, > > Because you have enlarged the _bus_ by two doesn't mean the drive is able > > to move bytes faster from the platters. > > > > You are now able to put more disks before saturating the SCSI bus but bear > > in mind that it is very unlikely that you'll be ever eble to saturate a 80 > > MB/s bus with only one drive. Is this so hard to understand? Making the bus speed faster *will not* magically make the bits come off the platter faster. There is a physical limit here, and *no* amount of bus bandwidth is going to overcome it. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 01:42:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29476 for freebsd-current-outgoing; Tue, 24 Nov 1998 01:42:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29459 for ; Tue, 24 Nov 1998 01:42:06 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id JAA50837 for ; Tue, 24 Nov 1998 09:42:03 GMT Message-ID: <365A7F6A.3ED8A6D6@tdx.co.uk> Date: Tue, 24 Nov 1998 09:42:02 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity References: <43337.911854048@zippy.cdrom.com> <199811232226.OAA24221@troutmask.apl.washington.edu> <19981124102706.A613@zappa.demon.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My system is: ASUS P2B-S PII 333Mhz 128Mb Mem, U2W SCSI Disk, FreeBSD 3.0-CURRENT > I only run the standard full system install with KDE 1.0 and Netscape 4.5 > > If i don't do a: > sysctl -w vfs.ffs.doreallocblks=0 > > The system won't survive longer than a day, it usally reboots when performing > standard cron stuff on 2.00AM I thought this had been fixed a while ago? - my system (current as of Thu/19/11/98) doesn't show any symptoms (it's an SMP P-Pro 200), even when busy (14 drives across 5 controllers) - it certainly makes it past the usual 2am cron-job's, and backups etc. -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 01:45:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29929 for freebsd-current-outgoing; Tue, 24 Nov 1998 01:45:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29919 for ; Tue, 24 Nov 1998 01:45:18 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id KAA07690; Tue, 24 Nov 1998 10:43:25 +0100 (CET) To: Archie Cobbs cc: bde@zeta.org.au (Bruce Evans), dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG, grog@lemis.com, rnordier@nordier.com Subject: Re: snprintf() in the kernel In-reply-to: Your message of "Tue, 24 Nov 1998 00:41:56 PST." <199811240841.AAA03369@bubba.whistle.com> Date: Tue, 24 Nov 1998 10:43:25 +0100 Message-ID: <7688.911900605@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please have all changes to sys/netatm, sys/dev/hea and sys/dev/hfa reviewed by Mike Spengler before committing. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 01:58:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00623 for freebsd-current-outgoing; Tue, 24 Nov 1998 01:58:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00608 for ; Tue, 24 Nov 1998 01:57:38 -0800 (PST) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (peer cross-checked as room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru with ESMTP id MAA02676; Tue, 24 Nov 1998 12:54:35 +0300 (MSK) (envelope-from romanp@wuppy.rcs.ru) Date: Tue, 24 Nov 1998 12:54:35 +0300 (MSK) From: "Roman V. Palagin" To: Karl Pielorz cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <365A7F6A.3ED8A6D6@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Nov 1998, Karl Pielorz wrote: > > I thought this had been fixed a while ago? - my system (current as of > Thu/19/11/98) doesn't show any symptoms (it's an SMP P-Pro 200), even when > busy (14 drives across 5 controllers) - it certainly makes it past the usual > 2am cron-job's, and backups etc. It was fixed by McKusick 17/11/98. But it's very interesting: I've current as of 23/11/98 and kernel crashes without disabling 'realloc' code, maximum uptime about 5-6 hours. Previous kernel was as of about 20/11/98 and works without any problems 8-) It's looks like something changed in src/sys tree. ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE | Just because you're paranoid Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 02:36:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04031 for freebsd-current-outgoing; Tue, 24 Nov 1998 02:36:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04023 for ; Tue, 24 Nov 1998 02:35:49 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA30568; Tue, 24 Nov 1998 21:35:27 +1100 Date: Tue, 24 Nov 1998 21:35:27 +1100 From: Bruce Evans Message-Id: <199811241035.VAA30568@godzilla.zeta.org.au> To: archie@whistle.com, bde@zeta.org.au Subject: Re: snprintf() in the kernel Cc: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG, grog@lemis.com, rnordier@nordier.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> It would be better without any strncpy() patches. > >Well, it's certainly easy enough to take them out.. however, some >are bug fixes... > >For example, if a function takes a string argument, when can you >assume an upper bound on how long the string is? strncpy() already takes a length arg. Changing from strncpy() to snprintf() just wastes space and time unless the value returned by snprintf() is actually checked and cases where the string doesn't fit are actually handled. >Of the strncpy() replacements, there are three categories: > >- "Possibly unterminated string", where one is required: > > netatm/spans/spans_print.c It's interesting that it doesn't just printf everything (using separate printfs because spans-addr_print() returns a pointer to static storage). Most of the strncpy's seem to be to copy the static storage to local storage. All buffers for this seem to have size 80, so there are no truncation problems. > netatm/uni/uniarp_cache.c > pc98/pc98/diskslice_machdep.c > pci/pci_compat.c > >- "Simplification" (eg, replacing constants like "16" with sizeof()) > with otherwise no functional effect (including strncpy()'s zero'ing > out of the buffer): > > i386/ibcs2/ibcs2_stat.c > i386/ibcs2/ibcs2_xenix.c > i386/linux/linux_misc.c These depend on a previous bzero() to zero out the buffer (and any padding in the struct). The strncpy()'s of course should have used sizeof() instead of literal constants. The explicit \0 termiation could have been avoided in ibcs2_stat.c by subtracting 1 from the sizes. This is already done in ibcs2_xenix.c and linux_misc.c, but it is hard to see because sizeof() is not used and the subtraction is done at code-write time. > netinet/ip_divert.c > >- "Gratuitous" (?) > > alpha/tc/tcds.c > dev/dpt/dpt_control.c > kern/subr_devstat.c This is certainly sloppy about null termination. It depends on device name lengths being shorter than 15. Most device names have length 2 (the others are too long :-) so there are no problems in practice. > netatm/atm_aal5.c > netatm/atm_socket.c > >Tell me which (or all) of these you don't want and I'll take them out; >however my instinct would say to keep the first two sets. >If it's performance you're thinking about, my general assumption is >that string manipulation in the kernel is uncommon, but that could >be wrong. strncpy() seems to be only twice as fast as snprintf() in the kernel (when both are in the L1 cache and strncpy() doesn't have to do much padding). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 03:13:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07086 for freebsd-current-outgoing; Tue, 24 Nov 1998 03:13:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA07078 for ; Tue, 24 Nov 1998 03:13:08 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id LAA06622; Tue, 24 Nov 1998 11:14:53 GMT Date: Tue, 24 Nov 1998 11:14:53 +0000 (GMT) From: Doug Rabson To: "Norman C. Rice" cc: Bruce Evans , mjacob@feral.com, current@FreeBSD.ORG Subject: Location for driver includes (was Re: Breakage in -current for theALPHA) In-Reply-To: <19981123214901.A13260@emu.sourcee.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, 23 Nov 1998, Norman C. Rice wrote: > On Tue, Nov 24, 1998 at 03:16:57AM +1100, Bruce Evans wrote: > > >> They traditionally go in sys (e.g., ttycom.h). Of course, there is > > >> no such thing as a machine independant driver API. There isn't even > > >> such a thing as a machine independent driver API. > > > > > >Eh? The second sentence might have been 'machine *dependent*'? > > > > > >In either case, what do you mean? There most certainly is both a DDI and > > >DKI for *BSD. There are MI functions (even in FreeBSD which is > > >historically less sensitive to MI vs MD issues) such as bcopy (DKI) or > > >devswitch functions. There are MD functions such as isa_configure (DDI). > > > > 1. Mispelling of `dependent' is annoying. > ^^^^^^^^^^ > The misspelling of `misspelling' when trying to make a point > about correct spelling is also annoying. :) > -- > Regards, > Norman C. Rice, Jr. > > > 2. Nothing is really machine independent. > > > > Bruce Ok, now that everyone has got their pedantry out of the way, can we please have a discussion about driver include files. The fact is that several architectures (including both of our supported arches) use the same hardware and having driver sources in sys/i386/isa and driver includes in sys/i386/include is just plain wrong. At this point we have two suggestions for locations of driver includes (sys/sys and sys/dev/include) and no suggestions for driver sources. I'm not too keen on dumping all the driver includes in sys/sys since its pretty crowded already. NetBSD appears to have some headers in there and some in the machine's include directory. I don't really have any strong arguments here but I would prefer that only 'generic' apis go here (all the ones currently there are). Is it worth sorting includes based on the type of bus which the hardware is attached to? Something like: sys/dev/include non-bus-specific includes sys/dev/include/isa isa bus includes sys/dev/include/pci pci bus includes ... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 04:40:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA16130 for freebsd-current-outgoing; Tue, 24 Nov 1998 04:40:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA16125 for ; Tue, 24 Nov 1998 04:40:41 -0800 (PST) (envelope-from geoffb@gti.noc.demon.net) Received: by server.noc.demon.net; id MAA11967; Tue, 24 Nov 1998 12:40:38 GMT Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2) id xma011954; Tue, 24 Nov 98 12:40:32 GMT Received: (from geoffb@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id MAA05913 for freebsd-current@freebsd.org; Tue, 24 Nov 1998 12:40:30 GMT From: Geoff Buckingham Message-Id: <199811241240.MAA05913@gti.noc.demon.net> Subject: Intel 82454NX PCI expander bridge To: freebsd-current@FreeBSD.ORG Date: Tue, 24 Nov 1998 12:40:30 +0000 (GMT) Reply-To: geoffb@demon.net X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody have a 450NX based machine working with multiple 82454NX PCI bridge expanders, I can only see my on-board stuff and no PCI slots, hence no ethernet for the install. PS is there a searchable index of CVS commit messages anywhere? -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 04:57:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18124 for freebsd-current-outgoing; Tue, 24 Nov 1998 04:57:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA18119 for ; Tue, 24 Nov 1998 04:57:35 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id HAA22098 for ; Tue, 24 Nov 1998 07:57:33 -0500 (EST) Date: Tue, 24 Nov 1998 07:57:32 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: video mode switching has gone south Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems (nay, it IS so) that video mode switching has gotten extremely strange within the last few days. This is not a problem just with vidcontrol and syscons, this affects XFree86 as well. I've got two kernels, the old one which does not exhibit this problem, and the new one which does. Working: FreeBSD 3.0-CURRENT #3: Sun Nov 22 21:45:52 EST 1998 Broken: FreeBSD 3.0-CURRENT #4: Mon Nov 23 20:11:02 EST 1998 Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #3: Sun Nov 22 21:45:52 EST 1998 green@feldman.dyn.ml.org:/usr/src/sys/compile/FELDMAN Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200455956 Hz CPU: AMD-K6tm w/ multimedia extensions (200.46-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x561 Stepping=1 Features=0x8001bf real memory = 83886080 (81920K bytes) config> quit avail memory = 78667776 (76824K bytes) Preloaded elf kernel "kernel.old" at 0xf0289000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 vga0: rev 0x01 int a irq 10 on pci0.13.0 Probing for PnP devices: Probing for devices on the ISA bus: VESA: v1.2, 4096k memory, flags:0x0, mode table:0xf00c4cc2 (c0004cc2) VESA: S3 Incorporated. 86C375/86C385 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio3 at 0x2e8-0x2ef irq 11 on isa sio3: type 16550A ppc: parallel port found at 0x378 ppc0 at 0x378 irq 7 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 lppps0: on ppbus 0 plip0: on ppbus 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-32 wd0: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , DMA, 32-bit, multi-block-32 wd1: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 1 (atapi): , removable, dma, iordy acd0: drive speed 2067KB/sec, 128KB cache acd0: supported read types: CD-R, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at ? drq 6 on isa snd0: sbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: joy0 at 0x201 on isa joy0: joystick npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging disabled changing root device to wd0s1a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates The kernel configuration is the same in both, except for ppc0 having flags 0x4 in the new one, which changing does not affect [the behavior of video mode switching]. Video mode switching is defined as "any video mode changing, including resolution changing and switching between non- and graphical screen modes," so affects X and syscons. An example of what previously happened: 00:00 I type "xmame wb3bl", for example, which uses Xxf86dga 00:01 xmame initializes, attempts to switch to 320x240 00:02 screen blanks 00:03 320x240 screen pops up, then blanks 00:04 game shows up 15:07 I get bored and press escape 15:08 screen switches back to 1280x1024 In the newer kernel (more or less, my memory might not be great): 00:00 I type "xmame wb3bl", for example, which uses Xxf86dga 00:01 xmame initializes, attempts to switch to 320x240 00:02 screen blanks 00:05 1280x1024 screen pops back up, garbled 00:07 screen blanks 00:09 1280x1024 screen pops back up 00:12 screen blanks 00:17 320x240 screen pops up 00:19 screen blanks 00:23 game shows up 01:40 I press escape because now I'm bored of this game and FreeBSD is being annoying 01:41 screen blanks 01:45 1280x1024 screen pops back up garbled 01:46 screen blanks 01:48 screen is back to normal If anyone has any ideas why any of this is happening now, I'd like to hear any possible explanations. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 05:02:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19007 for freebsd-current-outgoing; Tue, 24 Nov 1998 05:02:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19002 for ; Tue, 24 Nov 1998 05:02:38 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id IAA22150; Tue, 24 Nov 1998 08:02:15 -0500 (EST) Date: Tue, 24 Nov 1998 08:02:15 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Bruce Evans cc: mike@smith.net.au, bartol@salk.edu, dfr@nlsystems.com, freebsd-current@FreeBSD.ORG Subject: Re: NFS problems in -current In-Reply-To: <199811240509.QAA04542@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Nov 1998, Bruce Evans wrote: > >> Please also make it clear whether you're using the old 'lpt' driver or > >> the newer ppbus code, so that we can work out what needs attention... > > > >I'm using the newer ppbus code entirely: > > > >controller ppbus0 > >device nlpt0 at ppbus? > >device plip0 at ppbus? > >device ppi0 at ppbus? > >device pps0 at ppbus? > > > >controller ppc0 at isa? port ? tty irq 7 vector ppcintr > ^^^ > > ppc must be a `net' device for plip to work properly. See the plip > man page. ppc must also be a `tty' device for lpt0 and a `cam' device > for vp0. These requirements conflict. > > lpt0 and lp0 have related bugs. lpt0 needs to be a `net' device for > lp0 to work. This can be configured by specifying that it is a `tty' > device and statically configuring slip. > PR: 5699, 6099 > > The slip LKM has related bugs. > > Bruce Then what's the solution to having both printing and PLIP available? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 05:42:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23861 for freebsd-current-outgoing; Tue, 24 Nov 1998 05:42:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23829 for ; Tue, 24 Nov 1998 05:41:49 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id OAA15139; Tue, 24 Nov 1998 14:40:50 +0100 (CET) Message-ID: <19981124144050.A15122@foobar.franken.de> Date: Tue, 24 Nov 1998 14:40:50 +0100 From: Harold Gutch To: "Kenneth D. Merry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: page fault when rm'ing on ccd-partition References: <19981118113805.A5521@foobar.franken.de> <199811190419.VAA07192@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811190419.VAA07192@panzer.plutotech.com>; from Kenneth D. Merry on Wed, Nov 18, 1998 at 09:19:42PM -0700 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 18, 1998 at 09:19:42PM -0700, Kenneth D. Merry wrote: > Harold Gutch wrote... > > I'm experiencing problems on a (non-local) 3.0-19980916-SNAP > > non-SMP System. When rm'ing certain files from a ccd'd disk the > > machine panics. I can't really localize the problem any further > > as: > > [ ... ] > > > $ nm -aout /kernel | grep f01152 > > f0115288 t _ahc_handle_target_cmd > > I believe this panic was fixed a couple of days after that snapshot was > made: > After upgrading to 3.0-RELEASE the problems disappeared, the machine is running without problems since then, thanks for the hint. > A number of other CAM bugs have been fixed since then. I would recommend > upgrading to a recent -current snapshot. > I'd rather not run the bleeding edge on a machine mostly which is mostly administrated remotely (unless it crashes so that somebody has to drive up to it and reboot it). If some _serious_ CAM bugs (which might crash it) have been fixed since then, upgrading might be an idea, but if these bugs aren't really serious, I'll rather run -RELEASE for now. -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 06:58:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00657 for freebsd-current-outgoing; Tue, 24 Nov 1998 06:58:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cogsci.ed.ac.uk (stevenson144.cogsci.ed.ac.uk [129.215.144.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00651 for ; Tue, 24 Nov 1998 06:58:25 -0800 (PST) (envelope-from richard@cogsci.ed.ac.uk) Received: (from richard@localhost) by cogsci.ed.ac.uk (8.8.7/8.8.7) id OAA14418; Tue, 24 Nov 1998 14:58:08 GMT Date: Tue, 24 Nov 1998 14:58:08 GMT Message-Id: <199811241458.OAA14418@cogsci.ed.ac.uk> From: Richard Tobin Subject: Re: Adaptec SCSI messages To: Ron Klinkien , freebsd-current@FreeBSD.ORG In-Reply-To: Ron Klinkien's message of Tue, 24 Nov 1998 10:35:32 +0100 Organization: just say no Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I guess you are right, but i wonder why they have invented Ultra 2 disks > then. Since my disk performed in Single Ended mode exactly the same as > in ULTRA2-LVD mode. Now try it with 15 disks attached. -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 07:17:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02031 for freebsd-current-outgoing; Tue, 24 Nov 1998 07:17:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sunflower.com (dagda.sunflower.com [24.124.0.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02012 for ; Tue, 24 Nov 1998 07:17:35 -0800 (PST) (envelope-from bsd-curr@artorius.sunflower.com) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by sunflower.com (8.8.8/8.8.5) with ESMTP id JAA03614 for ; Tue, 24 Nov 1998 09:25:51 -0600 (CST) Date: Tue, 24 Nov 1998 09:17:32 -0600 (CST) From: "Stephen D. Spencer" Reply-To: admin@sunflower.com To: freebsd-current@FreeBSD.ORG Subject: Panic using IPFILTER w/ NAT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG System: AMD486dx4-120 clocked down to 100MhZ (the board only goes up to 25MhZ on the Dx4s but I got a good deal on the chip) 32 MB RAM 2 NE2000 ISA cards Adaptec 2840 Quantum 3G Conner 500M FreeBSD 3.0-CURRENT #0: Mon Nov 23 21:08:21 CST 1998 root@madeline.sunflower.com:/usr/src/sys/compile/MADELINE (cvsup'd and compiled on Sunday) Running: sshd 1.2.26 isc-dhcpd server BIND 8.1.2 sendmail 8.9.1 Slow but has been steady for the last 4 years. :) Initial ipnat rules: map ed0 10.15.0.0/16 -> 0/32 proxy port ftp ftp/tcp map ed0 10.15.0.0/16 -> 0/32 portmap tcp/udp 10000:40000 map ed0 10.15.0.0/16 -> 0/32 (I'm still learning NAT config theory. I found the above rules at http://photon.nepean.uws.edu.au/ppp/nat.html so please feel free to send a 'no shit' message if there's something inherently wrong with the above statement(s)) When FTPing from a single 10.15/16 host, the following panic information was made available to me. If more information is needed, please let me know. This is quite reproducable on this particular system. Regards, Stephen --------------------------------------------------------------------- - Stephen Spencer finger gladiatr@artorius.sunflower.com for - - administrator PGP key. - - Sunflower Datavision http://www.sunflower.com/data - --------------------------------------------------------------------- They ask me why I live in the green mountains. I smile and don't reply; my heart's at ease. Peach blossoms flow downstream, leaving no trace - And there are no other earths and skies than these. Li Po (701-761) db> show procvm Fatal trap 12: page fault while in kernel mode fault virtual address = 0x60 fault code = supervisor read, page not present instruction pointer = 0x8:0xf018fa86 stack pointer = 0x10:0xf01e0b88 frame pointer = 0x10:0xf01e0b8c 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 = Idle interrupt mask = kernel: type 12 trap, code=0 Stopped at _fr_addstate+0x244: movl 0x30(%edx),%ecx db> trace _fr_addstate(f032dc30,f01e0f14,500a,f08f0680,f032dc44) at _fr_addstate+0x244 _ippr_ftp_out(f01e0f14,f032dc30,f032dc44,f08f0680,f08f0080) at _ippr_ftp_out+0x242 _ap_check(f032dc30,f032dc44,f01e0f14,f08f0080,202) at _ap_check+0xe0 _ip_natout(f032dc30,14,f01e0f14) at _ip_natout+0x2c3 _fr_check(f032dc30,14,f0207c68,1,f01e0fa0) at _fr_check+0x3ae _ip_output(f032dc00,0,f01fa388,1,0) at _ip_output+0x3e6 _ip_forward(f032dc00,0,f032dc00,f3ffd340,0) at _ip_forward+0x19b _ip_input(f032dc00) at _ip_input+0x3ae _ipintr(f01a0693,80000000,10,10,0) at _ipintr+0x4b swi_net_next() at swi_net_next db> show registers cs 0x3c250008 ds 0x10 es 0xf01e0010 __DYNAMIC+0x1010 ss 0x10 eax 0x3be93a ecx 0 edx 0 ebx 0xf08f1108 esp 0xf01e0d38 __DYNAMIC+0x1d38 ebp 0xf01e0dd0 __DYNAMIC+0x1dd8 esi 0xa8 edi 0xf01e0e24 __DYNAMIC+0x1e24 eip 0xf0172b58 _fr_addstate+0x244 efl 0x10246 _fr_addstate+0x244: movl 0x30(%edx),%ecx db> show page cnt.v_free_count: 1770 cnt.v_cache_count: 0 cnt.v_inactive_count: 1035 cnt.v_active_count: 3782 cnt.v_wire_count: 1039 cnt.v_free_reserved: 123 cnt.v_free_min: 160 cnt.v_free_target: 603 cnt.v_cache_min: 603 cnt.v_inactive_target: 904 ------------------------------ kernel config: machine "i386" cpu "I486_CPU" ident MADELINE maxusers 100 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on da0 controller isa0 controller eisa0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller ahc0 controller scbus0 device da0 device pass0 #CAM passthrough driver device sc0 at isa? port "IO_KBD" flags 0x2 tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr device ed0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector edintr device ed1 at isa? port 0x320 net irq 5 iomem 0xd8000 vector edintr pseudo-device loop pseudo-device ether pseudo-device tun 1 pseudo-device pty 32 pseudo-device gzip # Exec gzipped a.out's options KTRACE #kernel tracing options SYSVSHM options SYSVSEM options SYSVMSG pseudo-device bpfilter 6 #Berkeley packet filter options IPFILTER #kernel ipfilter support options IPFILTER_LOG #ipfilter logging options DDB ------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 08:37:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08842 for freebsd-current-outgoing; Tue, 24 Nov 1998 08:37:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08837 for ; Tue, 24 Nov 1998 08:36:57 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id IAA20102; Tue, 24 Nov 1998 08:37:00 -0800 (PST) Message-ID: <19981124083700.B12951@Alameda.net> Date: Tue, 24 Nov 1998 08:37:00 -0800 From: Ulf Zimmermann To: Ron Klinkien , freebsd-current@FreeBSD.ORG Subject: Re: Adaptec SCSI messages Reply-To: ulf@Alameda.net References: <19981114144915.A244@zappa.demon.nl> <19981117112118.A252@zappa.demon.nl> <19981124011512.B11237@keltia.freenix.fr> <19981124103532.B613@zappa.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981124103532.B613@zappa.demon.nl>; from Ron Klinkien on Tue, Nov 24, 1998 at 10:35:32AM +0100 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 24, 1998 at 10:35:32AM +0100, Ron Klinkien wrote: > > I guess you are right, but i wonder why they have invented Ultra 2 disks > then. Since my disk performed in Single Ended mode exactly the same as > in ULTRA2-LVD mode. > They invented for two reasons: 1.) You can put more drives onto one bus, before running into bus limits (As before said) 2.) LVD = Low Voltage Differential = longer cable lengths possible again. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 09:02:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12572 for freebsd-current-outgoing; Tue, 24 Nov 1998 09:02:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12565 for ; Tue, 24 Nov 1998 09:02:10 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:q5dQnFE/ZczLCBWAaP3ykaFOZtno9KMq@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id CAA29991; Wed, 25 Nov 1998 02:01:39 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id CAA21858; Wed, 25 Nov 1998 02:03:14 +0900 (JST) Message-Id: <199811241703.CAA21858@zodiac.mech.utsunomiya-u.ac.jp> To: Brian Feldman cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: video mode switching has gone south In-reply-to: Your message of "Tue, 24 Nov 1998 07:57:32 EST." References: Date: Wed, 25 Nov 1998 02:03:14 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems (nay, it IS so) that video mode switching has gotten extremely >strange within the last few days. This is not a problem just with vidcontrol >and syscons, this affects XFree86 as well. I've got two kernels, the old one >which does not exhibit this problem, and the new one which does. > >Working: > FreeBSD 3.0-CURRENT #3: Sun Nov 22 21:45:52 EST 1998 >Broken: > FreeBSD 3.0-CURRENT #4: Mon Nov 23 20:11:02 EST 1998 [...] > Video mode switching is defined as "any video mode changing, including >resolution changing and switching between non- and graphical screen modes," so >affects X and syscons. An example of what previously happened: > >00:00 I type "xmame wb3bl", for example, which uses Xxf86dga >00:01 xmame initializes, attempts to switch to 320x240 >00:02 screen blanks >00:03 320x240 screen pops up, then blanks >00:04 game shows up >15:07 I get bored and press escape >15:08 screen switches back to 1280x1024 > > In the newer kernel (more or less, my memory might not be great): > >00:00 I type "xmame wb3bl", for example, which uses Xxf86dga >00:01 xmame initializes, attempts to switch to 320x240 >00:02 screen blanks >00:05 1280x1024 screen pops back up, garbled >00:07 screen blanks >00:09 1280x1024 screen pops back up >00:12 screen blanks >00:17 320x240 screen pops up >00:19 screen blanks >00:23 game shows up >01:40 I press escape because now I'm bored of this game and FreeBSD is being > annoying >01:41 screen blanks >01:45 1280x1024 screen pops back up garbled >01:46 screen blanks >01:48 screen is back to normal > > If anyone has any ideas why any of this is happening now, I'd like to hear >any possible explanations. Video mode switching in the X session is completely managed by the X server. The kernel and syscons are not in any way involved. Which version of XFree86 are you using? Do you see any problems outside the X as well? Do you see garbled or blank screen when you try to change video mode via vidcontrol? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 10:21:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20938 for freebsd-current-outgoing; Tue, 24 Nov 1998 10:21:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20907 for ; Tue, 24 Nov 1998 10:20:52 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id KAA01814 for ; Tue, 24 Nov 1998 10:20:41 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id KAA00461 for current@freebsd.org; Tue, 24 Nov 1998 10:20:27 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 24 Nov 1998 10:20:27 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: current@FreeBSD.ORG Subject: Is fsck broken for autoboot? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We had a nice wind storm up here in sunny Seattle last night, and the power went off. When it came back on, two FreeBSD systems, one running -current and the other running -stable, both failed in the same way to go multi-user. On the "mount -u -o rw /" command in /etc/rc, each system gave me a screen full of: WARNING: R/W mount of / denied. Filesystem is not clean - run fsck. However, in both cases, the automatic fsck had said: /dev/rsd2a: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED) and no other errors. (Yes, my root partition is on sd2 in one of the systems. Don't ask. :-) Soft updates are not used on either system. Any ideas why this happened? John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 10:25:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21382 for freebsd-current-outgoing; Tue, 24 Nov 1998 10:25:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from net.ganymed.org (ws5.cable.vol.at [194.183.130.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21375 for ; Tue, 24 Nov 1998 10:25:04 -0800 (PST) (envelope-from flo@ganymed.org) Received: from stone (stone.ganymed.org [192.168.2.3]) by net.ganymed.org (8.9.1/8.8.5) with SMTP id TAA01031 for ; Tue, 24 Nov 1998 19:24:50 +0100 (CET) Message-Id: <3.0.32.19981124192442.00f334ac@triton> X-Sender: flo@triton X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 24 Nov 1998 19:24:42 +0100 To: freebsd-current@FreeBSD.ORG From: Florian Nigsch Subject: strange /var/log/wtmp logging Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA21378 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all! Recently I noticed that there are strange log entries in my wtmp file. Like this: triton:~$ last | head ¨Õ¿ïttyp0 ÞòZ6 Thu Jan 1 01:00 still logged in ¨Õ¿ïttyp1 <îZ6 Thu Jan 1 01:00 still logged in ÉëZ6ttyp0 Thu Jan 1 01:00 still logged in ÿèZ6ttyv2 Thu Jan 1 01:00 still logged in ÁèZ6ttyv1 Thu Jan 1 01:00 still logged in ¨Õ¿ï~ YäZ6 ot Thu Jan 1 01:00 still logged in 0äZ6ttyp0 Thu Jan 1 01:00 still logged in ÆÝZ6ttyv1 Thu Jan 1 01:00 still logged in ‡ÜZ6ttyv4 Thu Jan 1 01:00 still logged in ÓZ6ttyp0 Thu Jan 1 01:00 still logged in triton:~$ last | more ^h^U^^ottyp0 ^^^rZ6^L Thu Jan 1 01:00 still logged in ^h^U^^ottyp1 <^nZ6^L Thu Jan 1 01:00 still logged in ^I^kZ6ttyp0 Thu Jan 1 01:00 still logged in ^?^hZ6ttyv2 Thu Jan 1 01:00 still logged in ^A^hZ6ttyv1 Thu Jan 1 01:00 still logged in ^h^U^^o~ Y^dZ6^L ot Thu Jan 1 01:00 still logged in 0^dZ6ttyp0 Thu Jan 1 01:00 still logged in ^F^]Z6ttyv1 Thu Jan 1 01:00 still logged in ^G^\Z6ttyv4 Thu Jan 1 01:00 still logged in ^Y^SZ6ttyp0 Thu Jan 1 01:00 still logged in 61.238 195.58.1 320 Thu Jan 1 01:00 still logged in ftp ftp 2.2 Wed Feb 11 21:44 still logged in root ttyp0 2.3 Fri May 12 11:30 still logged in edi ttyp1 2.2 Fri May 12 11:30 - 16:18 (13710+04:48) root ttyp0 2.3 Fri May 12 11:30 - 16:32 (13710+05:02) edi ttyv4 Tue Nov 24 15:57 still logged in root ttyv1 Tue Nov 24 07:58 - 07:58 (00:00) ...? what's that? the ftp entry should be logged with an IP of 192.168.2.2, too. I've already deleted wtmp once, but it always end up with that mess... How can I get rid of this? thanks in advance, Flo ----------------------------------------------------- F. Nigsch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 10:28:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21656 for freebsd-current-outgoing; Tue, 24 Nov 1998 10:28:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA21649 for ; Tue, 24 Nov 1998 10:28:03 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <52043(3)>; Tue, 24 Nov 1998 10:27:53 PST Received: (from fenner@localhost) by mango.parc.xerox.com (8.8.8/8.8.8) id KAA24423; Tue, 24 Nov 1998 10:27:52 -0800 (PST) (envelope-from fenner) Date: Tue, 24 Nov 1998 10:27:52 PST From: Bill Fenner Message-Id: <199811241827.KAA24423@mango.parc.xerox.com> To: current@FreeBSD.ORG, jdp@polstra.com Subject: Re: Is fsck broken for autoboot? In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had this happen a lot when I was still using compatibility slices in fstab; your example of "/dev/rsd2a: CLEAN FLAG NOT SET ..." seems to imply that you're using the compatibility slices too. Switch to /dev/rsd2sNa (where N is the FreeBSD slice on that disk). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 10:36:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22291 for freebsd-current-outgoing; Tue, 24 Nov 1998 10:36:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22283 for ; Tue, 24 Nov 1998 10:36:24 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id KAA01878; Tue, 24 Nov 1998 10:36:18 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id KAA00516; Tue, 24 Nov 1998 10:36:18 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811241827.KAA24423@mango.parc.xerox.com> Date: Tue, 24 Nov 1998 10:36:18 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Bill Fenner Subject: Re: Is fsck broken for autoboot? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Nov-98 Bill Fenner wrote: > I had this happen a lot when I was still using compatibility slices > in fstab; your example of "/dev/rsd2a: CLEAN FLAG NOT SET ..." > seems to imply that you're using the compatibility slices too. > Switch to /dev/rsd2sNa (where N is the FreeBSD slice on that disk). The message I quoted was from the -stable machine. I thought -stable still required the use of the compatibility slice. Am I mistaken about that? You may be on to something, though. The -current machine that failed does still have the compatibility slice in its fstab. A different -current machine which does not use the compatibility slice came back up without a hitch. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 10:40:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22584 for freebsd-current-outgoing; Tue, 24 Nov 1998 10:40:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA22579 for ; Tue, 24 Nov 1998 10:40:45 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <52088(2)>; Tue, 24 Nov 1998 10:40:34 PST Received: (from fenner@localhost) by mango.parc.xerox.com (8.8.8/8.8.8) id KAA24530; Tue, 24 Nov 1998 10:40:32 -0800 (PST) (envelope-from fenner) Date: Tue, 24 Nov 1998 10:40:32 PST From: Bill Fenner Message-Id: <199811241840.KAA24530@mango.parc.xerox.com> To: fenner@parc.xerox.com, jdp@polstra.com Subject: Re: Is fsck broken for autoboot? Cc: current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know when -stable switched to real slices, but I was experiencing this problem when I was booting a mix of 2.2.2 (required compatibility slice) and 2.2.6 (required real slice) kernels on the same machine - if I put the "compatible" device in fstab, the 2.2.6 kernel would fail to mount / if fsck had to fix it. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 10:48:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23058 for freebsd-current-outgoing; Tue, 24 Nov 1998 10:48:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23053 for ; Tue, 24 Nov 1998 10:48:42 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id KAA01925; Tue, 24 Nov 1998 10:48:40 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id KAA00525; Tue, 24 Nov 1998 10:48:27 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811241840.KAA24530@mango.parc.xerox.com> Date: Tue, 24 Nov 1998 10:48:27 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Bill Fenner Subject: Re: Is fsck broken for autoboot? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Nov-98 Bill Fenner wrote: > I don't know when -stable switched to real slices, but I was experiencing > this problem when I was booting a mix of 2.2.2 (required compatibility > slice) and 2.2.6 (required real slice) kernels on the same machine - if I > put the "compatible" device in fstab, the 2.2.6 kernel would fail to mount > / if fsck had to fix it. My -stable machine is fairly recent, so it should be OK to change it. Thanks for the advice. More evidence: a different -stable machine came back up fine. I just checked, and it does not use the compatibility slice. On the failing -current machine, I may be stuck. For work-related reasons, I sometimes have to run an older kernel which requires the compatibility slice on that machine. I guess I could set it up with a separate root partition for the old kernel. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 11:07:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24588 for freebsd-current-outgoing; Tue, 24 Nov 1998 11:07:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24583 for ; Tue, 24 Nov 1998 11:07:39 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA01991; Tue, 24 Nov 1998 11:07:31 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA00624; Tue, 24 Nov 1998 11:07:31 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 24 Nov 1998 11:07:31 -0800 (PST) Message-Id: <199811241907.LAA00624@vashon.polstra.com> To: julian@whistle.com Subject: Re: Elf linker question. Newsgroups: polstra.freebsd.current In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Julian Elischer wrote: > > I'm doing some work in a 3.0 system using the elf linker. > It seems that the new linker is insisting on me including libraries > that I never needed before.. In other words, I thin it's trying to resolve > symbols in functions I'm not using. Does anyone have comments on this? > > The old aout linker didn't need me to specify libraries that were not in > my call-graph. THe new one seems to need them. I really think it was a bug that our old linker didn't complain about those undefined symbols. I tried some tests long ago on some similar systems -- SVR4 and (maybe -- I can't remember) SunOS. They complained like our new linker does. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 11:15:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25111 for freebsd-current-outgoing; Tue, 24 Nov 1998 11:15:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25106 for ; Tue, 24 Nov 1998 11:15:06 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA02009; Tue, 24 Nov 1998 11:15:03 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA00664; Tue, 24 Nov 1998 11:14:57 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 24 Nov 1998 11:14:57 -0800 (PST) Message-Id: <199811241914.LAA00664@vashon.polstra.com> To: green@unixhelp.org Subject: Re: NFS problems in -current Newsgroups: polstra.freebsd.current In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Brian Feldman wrote: > > Sorry, I'm working on a good solutio, but basically right now I'm > piping all my outgoing mail through fmt and losing any special > formatting... I'll come up with a real solution soon. Check out the port "textproc/par". It's really great for stuff like that -- like fmt on steroids. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 11:24:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25852 for freebsd-current-outgoing; Tue, 24 Nov 1998 11:24:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25847 for ; Tue, 24 Nov 1998 11:24:24 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id NAA19240; Tue, 24 Nov 1998 13:24:13 -0600 (CST) From: Kevin Day Message-Id: <199811241924.NAA19240@home.dragondata.com> Subject: Re: MediaGX and calcru: negative time In-Reply-To: <3651D4A1.7566F4CF@whistle.com> from Julian Elischer at "Nov 17, 98 11:55:13 am" To: julian@whistle.com (Julian Elischer) Date: Tue, 24 Nov 1998 13:24:12 -0600 (CST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Kevin Day wrote: > > > > On a possibly related note, after upgrading to -current: > > > > > FreeBSD 2.2.7-RELEASE #0: Wed Oct 21 16:22:35 CDT 1998 > > > devel@kevin1.touchmaster:/usr/src/sys/compile/DEVEL > > > CPU: Cyrix GXm (0.00-MHz 586-class CPU) > > > Origin = "CyrixInstead" Id = 0x540 DIR=0x3346 Stepping=3 Revision=3 > > > real memory = 63963136 (62464K bytes) > > > avail memory = 60252160 (58840K bytes) > > > > FreeBSD 3.0-RELEASE #0: Mon Nov 16 16:10:02 CST 1998 > > root@kevin1.touchmaster:/usr/src/sys/compile/DEVEL > > Timecounter "i8254" frequency 1193182 Hz cost 40336 ns > > Timecounter "TSC" frequency 20172892 Hz cost 180 ns > > CPU: Cyrix GXm (20.17-MHz 586-class CPU) > > Origin = "CyrixInstead" Id = 0x540 Stepping=0 DIR=0x3346 > > Features=0x808131 > > real memory = 63963136 (62464K bytes) > > avail memory = 60243968 (58832K bytes) > > > > The clock now runs super fast. > To follow up..... Patching according to PR/6630 (and probing 4 times, not 2) and modifying i8254_get_timecount still doesn't have the problem completely fixed. I now see: FreeBSD 3.0-RELEASE #4: Tue Nov 24 13:11:34 CST 1998 devel@kevin1.touchmaster:/usr/src/sys/compile/DEVEL Calibrating clock(s) ... TSC clock: 233904016 Hz, i8254 clock: 1217253 Hz 1217253 Hz differs from default of 1193182 Hz by more than 1% Timecounter "i8254" frequency 1193182 Hz cost 4419 ns Timecounter "TSC" frequency 210479132 Hz cost 193 ns interrupt total rate clk0 irq0 34825 89 rtc0 irq8 44567 114 Any further suggestions? This is much closer, but the clock still runs too quickly. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 11:24:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25892 for freebsd-current-outgoing; Tue, 24 Nov 1998 11:24:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25866 for ; Tue, 24 Nov 1998 11:24:30 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA02043; Tue, 24 Nov 1998 11:24:26 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA00714; Tue, 24 Nov 1998 11:24:26 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 24 Nov 1998 11:24:26 -0800 (PST) Message-Id: <199811241924.LAA00714@vashon.polstra.com> To: hasty@rah.star-gate.com Subject: Re: pam can't open module error messages Newsgroups: polstra.freebsd.current In-Reply-To: <199811240622.WAA00757@rah.star-gate.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199811240622.WAA00757@rah.star-gate.com>, Amancio Hasty wrote: > > I am getting the following error messages every time I log in to the system > with a recent -current.... > > Amancio > > > > Nov 23 22:10:07 cioloco login: [dlerror: Cannot open > "/usr/lib/pam_cracklib.so"] > Nov 23 22:10:07 cioloco login: adding faulty module: /usr/lib/pam_cracklib.so > Nov 23 22:10:07 cioloco login: unable to dlopen(/usr/lib/pam_deny.so) > Nov 23 22:10:07 cioloco login: [dlerror: Cannot open "/usr/lib/pam_deny.so"] > Nov 23 22:10:07 cioloco login: adding faulty module: /usr/lib/pam_deny.so > Nov 23 22:10:07 cioloco login: unable to dlopen(/usr/lib/pam_warn.so) > Nov 23 22:10:07 cioloco login: [dlerror: Cannot open "/usr/lib/pam_warn.so"] > Nov 23 22:10:07 cioloco login: adding faulty module: /usr/lib/pam_warn.so > Nov 23 22:10:07 cioloco login: auth_pam: Module is unknown It looks to me like you have a bogus "/etc/pam.conf" file, or else a bogus directory "/etc/pam.d". I bet it's the latter. Delete the directory if you have one. Where did it come from? That's the question. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 11:31:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26812 for freebsd-current-outgoing; Tue, 24 Nov 1998 11:31:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26807 for ; Tue, 24 Nov 1998 11:31:12 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA10461; Tue, 24 Nov 1998 11:24:56 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdw10450; Tue Nov 24 19:24:49 1998 Date: Tue, 24 Nov 1998 11:24:23 -0800 (PST) From: Julian Elischer To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Elf linker question. In-Reply-To: <199811241907.LAA00624@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not sure that it isn't following too many links.. I had to add 100 libraries to our makefiles (usually the same ones) Even if we were only using 1 function in a library, it required all the rest of the libraries in that set, even if they were called from functions other than the one we were calling. I find it hard to believe that all out programs would have worked correctly if they were SO wrong! I will see if I can make a test case.. julian On Tue, 24 Nov 1998, John Polstra wrote: > In article , > Julian Elischer wrote: > > > > I'm doing some work in a 3.0 system using the elf linker. > > It seems that the new linker is insisting on me including libraries > > that I never needed before.. In other words, I thin it's trying to resolve > > symbols in functions I'm not using. Does anyone have comments on this? > > > > The old aout linker didn't need me to specify libraries that were not in > > my call-graph. THe new one seems to need them. > > I really think it was a bug that our old linker didn't complain > about those undefined symbols. I tried some tests long ago on some > similar systems -- SVR4 and (maybe -- I can't remember) SunOS. They > complained like our new linker does. > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Nobody ever went broke underestimating the taste of the American public." > -- H. L. Mencken > > 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 Nov 24 11:32:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27054 for freebsd-current-outgoing; Tue, 24 Nov 1998 11:32:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27049 for ; Tue, 24 Nov 1998 11:32:44 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id LAA87960; Tue, 24 Nov 1998 11:31:56 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811241931.LAA87960@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra cc: current@FreeBSD.ORG Subject: Re: pam can't open module error messages In-reply-to: Your message of "Tue, 24 Nov 1998 11:24:26 PST." <199811241924.LAA00714@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Nov 1998 11:31:56 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got pam.conf from /usr/src/contrib/libpam/conf/pam.conf Where should I fetch pam.conf from ? Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 11:33:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27229 for freebsd-current-outgoing; Tue, 24 Nov 1998 11:33:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27217 for ; Tue, 24 Nov 1998 11:33:53 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA02095; Tue, 24 Nov 1998 11:33:50 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA00749; Tue, 24 Nov 1998 11:33:50 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811241931.LAA87960@rah.star-gate.com> Date: Tue, 24 Nov 1998 11:33:50 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Amancio Hasty Subject: Re: pam can't open module error messages Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Nov-98 Amancio Hasty wrote: > I got pam.conf from /usr/src/contrib/libpam/conf/pam.conf That explains it. > > Where should I fetch pam.conf from ? "/usr/src/etc/pam.conf". --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 11:36:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27518 for freebsd-current-outgoing; Tue, 24 Nov 1998 11:36:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27513 for ; Tue, 24 Nov 1998 11:36:01 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA02110; Tue, 24 Nov 1998 11:35:48 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA00760; Tue, 24 Nov 1998 11:35:48 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 24 Nov 1998 11:35:48 -0800 (PST) Message-Id: <199811241935.LAA00760@vashon.polstra.com> To: flo@ganymed.org Subject: Re: strange /var/log/wtmp logging Newsgroups: polstra.freebsd.current In-Reply-To: <3.0.32.19981124192442.00f334ac@triton> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3.0.32.19981124192442.00f334ac@triton>, Florian Nigsch wrote: > Hi all! > > > Recently I noticed that there are strange log entries in my wtmp file. You probably have an old program predating the changes in the format wtmp file, which is writing old-style records into the file. The usual culprit is xterm. If you are using wu-ftpd from a port, it's another possibility. Likewise for sshd, I believe. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 11:39:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27712 for freebsd-current-outgoing; Tue, 24 Nov 1998 11:39:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27706 for ; Tue, 24 Nov 1998 11:39:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id LAA88093; Tue, 24 Nov 1998 11:38:56 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811241938.LAA88093@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra cc: current@FreeBSD.ORG Subject: Re: pam can't open module error messages In-reply-to: Your message of "Tue, 24 Nov 1998 11:33:50 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Nov 1998 11:38:56 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tnks that did the trick. Cheers, Amancio > > On 24-Nov-98 Amancio Hasty wrote: > > I got pam.conf from /usr/src/contrib/libpam/conf/pam.conf > > That explains it. > > > > > Where should I fetch pam.conf from ? > > "/usr/src/etc/pam.conf". > --- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Nobody ever went broke underestimating the taste of the American public." > -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 11:53:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29362 for freebsd-current-outgoing; Tue, 24 Nov 1998 11:53:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29354 for ; Tue, 24 Nov 1998 11:53:55 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id OAA15837; Tue, 24 Nov 1998 14:57:03 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 24 Nov 1998 14:57:03 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: John Polstra cc: flo@ganymed.org, current@FreeBSD.ORG Subject: Re: strange /var/log/wtmp logging In-Reply-To: <199811241935.LAA00760@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Nov 1998, John Polstra wrote: > > Recently I noticed that there are strange log entries in my wtmp file. > > You probably have an old program predating the changes in the format > wtmp file, which is writing old-style records into the file. The > usual culprit is xterm. If you are using wu-ftpd from a port, it's > another possibility. Likewise for sshd, I believe. urk, why hasn't someone made a UTMP_VERSION #define and int get_utmp_version(), or whatnot that would get bumped when utmp/wtmp change? if(UTMP_VERSION == get_utmp_version()){ login(.....); } else { ... syslog( "warning utmp has changed from under me, " "please recompile "); ... } This error seems to be common enough to warrent something of the sort... Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 11:59:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29950 for freebsd-current-outgoing; Tue, 24 Nov 1998 11:59:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29922 for ; Tue, 24 Nov 1998 11:59:13 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA02191; Tue, 24 Nov 1998 11:57:50 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA00847; Tue, 24 Nov 1998 11:57:50 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 24 Nov 1998 11:57:50 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Alfred Perlstein Subject: Re: strange /var/log/wtmp logging Cc: current@FreeBSD.ORG, flo@ganymed.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Nov-98 Alfred Perlstein wrote: > On Tue, 24 Nov 1998, John Polstra wrote: > >> > Recently I noticed that there are strange log entries in my wtmp file. >> >> You probably have an old program predating the changes in the format >> wtmp file, which is writing old-style records into the file. The >> usual culprit is xterm. If you are using wu-ftpd from a port, it's >> another possibility. Likewise for sshd, I believe. > > urk, why hasn't someone made a UTMP_VERSION #define and > int get_utmp_version(), or whatnot that would > get bumped when utmp/wtmp change? There is a rich mine of past discussion all about this in the mailing list archives. Please, let's not rehash it all over again here. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 12:12:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01413 for freebsd-current-outgoing; Tue, 24 Nov 1998 12:12:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01395 for ; Tue, 24 Nov 1998 12:12:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00609; Tue, 24 Nov 1998 12:10:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811242010.MAA00609@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: geoffb@demon.net cc: freebsd-current@FreeBSD.ORG Subject: Re: Intel 82454NX PCI expander bridge In-reply-to: Your message of "Tue, 24 Nov 1998 12:40:30 GMT." <199811241240.MAA05913@gti.noc.demon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Nov 1998 12:10:48 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Does anybody have a 450NX based machine working with multiple 82454NX > PCI bridge expanders, I can only see my on-board stuff and no PCI > slots, hence no ethernet for the install. Yes, we have one running here. You should pester Kevin VanMaren (IIRC vanmaren@fast.cs.utah.edu) for patches; they may be applicable to 2.2.x, certainly to 3.0. > PS is there a searchable index of CVS commit messages anywhere? $CVSROOT/CVSROOT/commitlogs -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 12:26:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02690 for freebsd-current-outgoing; Tue, 24 Nov 1998 12:26:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02685 for ; Tue, 24 Nov 1998 12:26:22 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id MAA02303; Tue, 24 Nov 1998 12:26:18 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id MAA00962; Tue, 24 Nov 1998 12:26:16 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 24 Nov 1998 12:26:16 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Julian Elischer Subject: Re: Elf linker question. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Nov-98 Julian Elischer wrote: > I'm not sure that it isn't following too many links.. > I had to add 100 libraries to our makefiles > (usually the same ones) > > Even if we were only using 1 function in a library, it required all the > rest of the libraries in that set, even if they were called from functions > other than the one we were calling. A shared library is fundamentally different from an archive library, in that a shared library is a monolithic object rather than a collection of separate object files. You either load the entire shared library or you don't load any of it. With archive libraries, only the component object files that actually satisfy external references are loaded. Also, the linker really doesn't understand the concept of "functions". It only knows about labels. It doesn't have any idea which function a call to another function appears in. > > I find it hard to believe that all out programs would have worked > > correctly if they were SO wrong! It worked just because none of the functions in the missing libraries were actually called. Maybe they can't possibly be called in your program. But the linker doesn't know that (because there are references to some of them even if those references aren't used). So it has to be safe and force you to satisfy all external references. The a.out linker didn't, and I think it was a bug. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 12:40:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03908 for freebsd-current-outgoing; Tue, 24 Nov 1998 12:40:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03896 for ; Tue, 24 Nov 1998 12:40:54 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA13431; Tue, 24 Nov 1998 12:35:59 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdF13429; Tue Nov 24 20:35:54 1998 Date: Tue, 24 Nov 1998 12:35:28 -0800 (PST) From: Julian Elischer To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Elf linker question. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Nov 1998, John Polstra wrote: > It worked just because none of the functions in the missing libraries > were actually called. Maybe they can't possibly be called in your > program. But the linker doesn't know that (because there are > references to some of them even if those references aren't used). So > it has to be safe and force you to satisfy all external references. > The a.out linker didn't, and I think it was a bug. The trouble with that is that ALL libraries end up being loaded into memeory whenever one program requires any of them. they also all get traversed on program startup which keeps them all in memory.. right? not so good for small memory systems. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 13:00:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05540 for freebsd-current-outgoing; Tue, 24 Nov 1998 13:00:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05535 for ; Tue, 24 Nov 1998 13:00:21 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA16650; Tue, 24 Nov 1998 12:59:11 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma016648; Tue, 24 Nov 98 12:59:10 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA05816; Tue, 24 Nov 1998 12:59:09 -0800 (PST) From: Archie Cobbs Message-Id: <199811242059.MAA05816@bubba.whistle.com> Subject: Re: snprintf() in the kernel In-Reply-To: <199811241035.VAA30568@godzilla.zeta.org.au> from Bruce Evans at "Nov 24, 98 09:35:27 pm" To: bde@zeta.org.au (Bruce Evans) Date: Tue, 24 Nov 1998 12:59:09 -0800 (PST) Cc: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG, grog@lemis.com, rnordier@nordier.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > >For example, if a function takes a string argument, when can you > >assume an upper bound on how long the string is? > > strncpy() already takes a length arg. Changing from strncpy() to > snprintf() just wastes space and time unless the value returned by > snprintf() is actually checked and cases where the string doesn't > fit are actually handled. Except when there needs to be a trailing NUL byte and the original code doesn't manually put one in the last buffer byte. For example, devstat_add_entry() and ibcs2_utssys() (just noticed a new bug.. potential crash in index() if your hostname is "longhostname"); > >Of the strncpy() replacements, there are three categories: > > > >- "Possibly unterminated string", where one is required: > > > > netatm/spans/spans_print.c > > It's interesting that it doesn't just printf everything (using separate > printfs because spans-addr_print() returns a pointer to static storage). > Most of the strncpy's seem to be to copy the static storage to local > storage. All buffers for this seem to have size 80, so there are no > truncation problems. Yes, the code is technically correct, but figuring this out requires reverse engineering a bunch of function calls, etc. before you can conclude that there's no actual bug there. Why force a future programmer to have to rediscover that the buffers won't overflow? Why not make it obvious? This is not a bug fix but rather a maintainability fix, as are most of these.. > > netatm/uni/uniarp_cache.c > > pc98/pc98/diskslice_machdep.c > > pci/pci_compat.c > > > >- "Simplification" (eg, replacing constants like "16" with sizeof()) > > with otherwise no functional effect (including strncpy()'s zero'ing > > out of the buffer): > > > > i386/ibcs2/ibcs2_stat.c > > i386/ibcs2/ibcs2_xenix.c > > i386/linux/linux_misc.c > > These depend on a previous bzero() to zero out the buffer (and any padding > in the struct). The strncpy()'s of course should have used sizeof() instead > of literal constants. The explicit \0 termiation could have been avoided > in ibcs2_stat.c by subtracting 1 from the sizes. This is already done in > ibcs2_xenix.c and linux_misc.c, but it is hard to see because sizeof() is > not used and the subtraction is done at code-write time. Again, the code is technically correct but less than pleasant to look at and requires analysis and cross-checking to conclude that there's no actual bug.. yuck. Revision #3 is now ready :-) Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 13:08:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06660 for freebsd-current-outgoing; Tue, 24 Nov 1998 13:08:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06653 for ; Tue, 24 Nov 1998 13:08:13 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA16789; Tue, 24 Nov 1998 13:07:11 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma016787; Tue, 24 Nov 98 13:06:56 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA05958; Tue, 24 Nov 1998 13:06:56 -0800 (PST) From: Archie Cobbs Message-Id: <199811242106.NAA05958@bubba.whistle.com> Subject: Re: snprintf() in the kernel In-Reply-To: <199811240900.BAA13142@apollo.backplane.com> from Matthew Dillon at "Nov 24, 98 01:00:15 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 24 Nov 1998 13:06:56 -0800 (PST) Cc: bde@zeta.org.au, freebsd-current@FreeBSD.ORG, grog@lemis.com, rnordier@nordier.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > I have a suggestion, why not split the problem up... commit the > kernel snprintf() subroutine first, then put up a small subset of the > snprintf() changes up for review and commit those on a fast track. i.e. > get some of the more obvious sprintf() -> snprintf() fixes in and proven. That makes sense.. especially so people can start using snprintf() if they want, instead of waiting for this discussion to finish.. :-) > Personally, I think we need to move to length-limited copies for all > string operations. The code may be correct as is, and it may seem obvious > to the people who wrote it, but FreeBSD is a collective effort and the > more mistakes we can prevent in the future without compromising code > effectiveness the better. Me too. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 13:35:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09714 for freebsd-current-outgoing; Tue, 24 Nov 1998 13:35:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09709 for ; Tue, 24 Nov 1998 13:35:14 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA15703; Tue, 24 Nov 1998 13:30:45 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdw15696; Tue Nov 24 21:30:38 1998 Date: Tue, 24 Nov 1998 13:30:09 -0800 (PST) From: Julian Elischer To: Archie Cobbs cc: Matthew Dillon , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, grog@lemis.com, rnordier@nordier.com Subject: Re: snprintf() in the kernel In-Reply-To: <199811242106.NAA05958@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Nov 1998, Archie Cobbs wrote: > > > Personally, I think we need to move to length-limited copies for all > > string operations. The code may be correct as is, and it may seem obvious > > to the people who wrote it, but FreeBSD is a collective effort and the > > more mistakes we can prevent in the future without compromising code > > effectiveness the better. > code that doesn't obviously do what it does should be either heavily commented or considered a bug.. It will eventually trick someone.. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 13:36:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09939 for freebsd-current-outgoing; Tue, 24 Nov 1998 13:36:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09932 for ; Tue, 24 Nov 1998 13:36:49 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA17201; Tue, 24 Nov 1998 13:35:46 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma017199; Tue, 24 Nov 98 13:35:34 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA06425; Tue, 24 Nov 1998 13:35:34 -0800 (PST) From: Archie Cobbs Message-Id: <199811242135.NAA06425@bubba.whistle.com> Subject: Re: snprintf() in the kernel In-Reply-To: <199811242059.MAA05816@bubba.whistle.com> from Archie Cobbs at "Nov 24, 98 12:59:09 pm" To: archie@whistle.com (Archie Cobbs) Date: Tue, 24 Nov 1998 13:35:34 -0800 (PST) Cc: bde@zeta.org.au, dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG, grog@lemis.com, rnordier@nordier.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs writes: > Revision #3 is now ready :-) Oops, forgot the URL: ftp://ftp.whistle.com/pub/archie/misc/SNPRINTF.patch.3 -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 13:44:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10808 for freebsd-current-outgoing; Tue, 24 Nov 1998 13:44:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from world.virtual-earth.de (world.virtual-earth.de [194.231.209.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10575 for ; Tue, 24 Nov 1998 13:43:21 -0800 (PST) (envelope-from mathiasp@mp.virtual-earth.de) Received: from mp.virtual-earth.de (mp.virtual-earth.de [194.231.209.35]) by world.virtual-earth.de (8.9.1/8.8.5) with ESMTP id WAA00351 for ; Tue, 24 Nov 1998 22:43:01 +0100 (MET) Received: from mp.virtual-earth.de (localhost.virtual-earth.de [127.0.0.1]) by mp.virtual-earth.de (8.9.1/8.8.5) with ESMTP id WAA00285 for ; Tue, 24 Nov 1998 22:42:55 +0100 (MET) Message-Id: <199811242142.WAA00285@mp.virtual-earth.de> Date: Tue, 24 Nov 1998 22:42:48 +0100 (MET) From: Mathias Picker Subject: new da2 no longer recognized To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: MULTIPART/signed; micalg=pgp-md5; protocol="application/pgp-signature"; BOUNDARY="0-1804289383-911943777=:282" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-1804289383-911943777=:282 Content-Type: TEXT/plain; CHARSET=US-ASCII Hmmm, I really don't know if this is a current problem, but: a 4GB UW-SCSI developed problems, so I bought a new one, sticked it in the machine, and copied the recoverable data off the old one. Everything worked fine. Now I unplugged the old drive, closed the case, and: the new drive can't be mounted any more!!! Its still recognised (dmesg output at end of file, its da2), but mount says: device not configured. disklabel, too. Booting off a new boot disk and invoking sysinstall shows me da2, but completely empty, not even a freebsd slice on it. But I allread copied data onto the damn thing!!! Any help??? This is relatively urgent, since all my data usually reside on that disk. Thanks, Mathias -- Mathias Picker Consultant Information Architecture Mathias.Picker@virtual-earth.de ++49 +172 / 89 19 381 --0-1804289383-911943777=:282 Content-Type: APPLICATION/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBNlsoXKzvoSjVwVSdAQGm7wP+MflP8bAu2YMZ+LkmZOf0Z4w0sTlvse1o onLGhbRt9bIqww3xgvf7Yg3mzZp1Nr7LwjEBA0WaY3GEMZeVbdL2l8PtsPSLUAKF +xWUDa/XhUgK4LKzqLjCd3rs2WNhdgRUB/AeBQuuo9xNRQUD1gIPSE2E0GhxevkA fblm9GUOGgc= =dzto -----END PGP MESSAGE----- --0-1804289383-911943777=:282-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 14:00:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12307 for freebsd-current-outgoing; Tue, 24 Nov 1998 14:00:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from world.virtual-earth.de (world.virtual-earth.de [194.231.209.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12210 for ; Tue, 24 Nov 1998 13:59:30 -0800 (PST) (envelope-from mathiasp@mp.virtual-earth.de) Received: from mp.virtual-earth.de (mp.virtual-earth.de [194.231.209.35]) by world.virtual-earth.de (8.9.1/8.8.5) with ESMTP id WAA00399 for ; Tue, 24 Nov 1998 22:59:24 +0100 (MET) Received: from mp.virtual-earth.de (localhost.virtual-earth.de [127.0.0.1]) by mp.virtual-earth.de (8.9.1/8.8.5) with ESMTP id WAA00311 for ; Tue, 24 Nov 1998 22:59:18 +0100 (MET) Message-Id: <199811242159.WAA00311@mp.virtual-earth.de> Date: Tue, 24 Nov 1998 22:59:16 +0100 (MET) From: Mathias Picker Subject: Again: new da2 suddenly gives "device not configured" error To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if I post this twice, my system is not very stable right now (or maybe _I_ am not so stable right now) my 4Gb UW-SCSI drive develped bad sectors, so I bought a new one today, plugged it in with no problems, copied the data from the old disk to the new one, everything went smooth. Then I unplugged the old drive, closed the case and voila: I get a "device not configure" error from mount. sysinstall shows me an empty device, not even an freebsd slice on it. But i _did_ copy data to that disk!!! Just 15 minutes ago! I even tried writing partition data again with sysinstall. Sysinstall seems to do it, but once I reboot I get the same "device not configured" from disklabel. disklabel -r -w da2 auto give no error, too, but a subsequent disklabel -r shows "disklabel: bad pack magic number (label is damaged, or pack is unlabeled)" All other devices on the same bus are working just fine. The system is cvsupped on 1998-11-17, and I can't rebuild it now since my sources are gone...... and I have nowhere enough space for src and obj. Any help?? This is kind of urgent for me since most of my data reside on that disk. Thanks, Mathias dmesg output: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Tue Nov 17 11:59:52 MET 1998 mathiasp@world.virtual-earth.de:/usr/src/sys/compile/WORLD Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 99474219 Hz CPU: Pentium/P54C (99.47-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 33554432 (32768K bytes) config> quit avail memory = 30449664 (29736K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.7.0 de0: rev 0x11 int a irq 10 on pci0.9.0 de0: 21041 [10Mb/s] pass 1.1 de0: address 00:80:48:e8:d7:85 ncr0: rev 0x26 int a irq 11 on pci0.11.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface de0: enabling 10baseT port Intel Pentium F00F detected, installing workaround Waiting 8 seconds for SCSI devices to settle sa0 at ncr0 bus 0 target 3 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 10.0MB/s transfers (10.0MHz, offset 8) changing root device to da0s1a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 1034MB (2118144 512 byte sectors: 255H 63S/T 131C) cd0 at ncr0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 8.64MB/s transfers (8.64MHz, offset 15) cd0: cd present [133289 x 2048 byte records] da1 at ncr0 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da2 at ncr0 bus 0 target 8 lun 0 da2: Fixed Direct Access SCSI2 device da2: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates -- Mathias Picker Consultant Information Architecture Mathias.Picker@virtual-earth.de +49 172 / 89 19 381 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 14:01:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12525 for freebsd-current-outgoing; Tue, 24 Nov 1998 14:01:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12514 for ; Tue, 24 Nov 1998 14:01:49 -0800 (PST) (envelope-from andreasd@ifi.uio.no) Received: from refil.ifi.uio.no (3034@refil.ifi.uio.no [129.240.64.28]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id XAA29428 for ; Tue, 24 Nov 1998 23:01:41 +0100 (MET) Received: (from andreasd@localhost) by refil.ifi.uio.no ; Tue, 24 Nov 1998 23:01:40 +0100 (MET) To: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity References: <43337.911854048@zippy.cdrom.com> From: Andreas Dobloug Date: 24 Nov 1998 23:01:39 +0100 In-Reply-To: <43337.911854048@zippy.cdrom.com> Message-ID: Lines: 15 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jordan K. Hubbard | > I too have been experiencing random | > reboots, with no apparent reason. | I see an apparent reason. Keep reading. | > My machine is a Pentium 200Mhz overclocked to 233Mhz, | Stop that. At least until your system is 100% stable and does not | exhibit any symptoms which can be clearly traced to software. I'm experiencing the same problem, and I'm not overclocking. (My HW: Asus P2B-DS, 2xPII-350, 128MB RAM, 2xQuantum Viking2 (u2w) disks). -- Andreas Dobloug : email: andreasd@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 14:09:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13130 for freebsd-current-outgoing; Tue, 24 Nov 1998 14:09:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rossel.saarnet.de (rossel.saarnet.de [145.253.240.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13065 for ; Tue, 24 Nov 1998 14:09:10 -0800 (PST) (envelope-from doehrm@aubi.de) Received: from igate.aubi.de (root@igate.aubi.de [145.253.242.249]) by rossel.saarnet.de (8.8.8/8.8.8) with ESMTP id XAA28786; Tue, 24 Nov 1998 23:10:25 +0100 (MET) Received: from cisco.aubi.de ([170.56.121.252]) by igate.aubi.de (8.8.7/8.8.7) with ESMTP id AAA11669; Wed, 25 Nov 1998 00:19:19 +0100 Received: from exchange.aubi.de (EXCHANGE.aubi.de [170.56.121.91]) by cisco.aubi.de (8.9.1/8.9.1) with ESMTP id XAA03690; Tue, 24 Nov 1998 23:12:38 +0100 (CET) Received: by EXCHANGE.aubi.de with Internet Mail Service (5.5.2232.9) id ; Tue, 24 Nov 1998 23:03:39 +0100 Message-ID: From: =?iso-8859-1?Q?Markus_D=F6hr?= To: "'Andreas Dobloug'" , current@FreeBSD.ORG Subject: RE: Random craches under heavy(?) disk activity Date: Tue, 24 Nov 1998 23:02:34 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA13070 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > | > I too have been experiencing random > | > reboots, with no apparent reason. just tested with a compile marathon - top load was 13.92 with very heavy disk activiy, but no reboot - just running stable. -- Markus Doehr IT Admin AUBI Baubeschläge GmbH Tel.: +49 6503 917 152 Fax : +49 6503 917 119 e-Mail: doehrm@aubi.de MD1139-RIPE ************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 14:10:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13460 for freebsd-current-outgoing; Tue, 24 Nov 1998 14:10:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.aha.ru (ns1.aha.ru [195.2.80.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13455 for ; Tue, 24 Nov 1998 14:10:01 -0800 (PST) (envelope-from osa@etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by ns1.aha.ru (8.9.1/8.9.1/aha-r/0.04B) with ESMTP id BAA20734 for ; Wed, 25 Nov 1998 01:09:55 +0300 (MSK) Received: by sunny.aha.ru id BAA10256; (8.8.8/vak/1.9) Wed, 25 Nov 1998 01:09:01 +0300 (MSK) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma010189; Wed Nov 25 01:08:42 1998 Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by serv.etrust.ru (8.9.1/8.9.1) with ESMTP id BAA03270 for ; Wed, 25 Nov 1998 01:03:03 +0300 (MSK) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id AAA03868 for ; Wed, 25 Nov 1998 00:57:30 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Wed, 25 Nov 1998 00:57:28 +0300 (MSK) From: oZZ!!! To: current@FreeBSD.ORG Subject: X-server crush... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I use windowmaker-0.20.0 in my FreeBSD-3.0-CURRENT Sun Nov 22 # uname -a time-2-time X server in my machine crush. Caught signal 24. Server aborting Nov 25 00:50:25 ozz /kernel: pid 3663 (XF86_Mach64), uid 0: exited on signal 6 X connection to :0.0 broken (explicit kill or server shutdown). ..... wmaker warning: got signal 1 (Hangup) - restarting What does it mean? Rgdz, Sergey Osokin aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 14:25:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15011 for freebsd-current-outgoing; Tue, 24 Nov 1998 14:25:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (31-sweet.camalott.com [208.239.153.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14942 for ; Tue, 24 Nov 1998 14:25:03 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id QAA23802; Tue, 24 Nov 1998 16:23:15 -0600 (CST) (envelope-from joelh) To: Mathias Picker Cc: current@FreeBSD.ORG Subject: Re: Again: new da2 suddenly gives "device not configured" error References: <199811242159.WAA00311@mp.virtual-earth.de> From: Joel Ray Holveck Date: 24 Nov 1998 16:23:10 -0600 In-Reply-To: Mathias Picker's message of "Tue, 24 Nov 1998 22:59:16 +0100 (MET)" Message-ID: <86k90kybld.fsf@detlev.UUCP> Lines: 14 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > my 4Gb UW-SCSI drive develped bad sectors, so I bought a new one today, > plugged it in with no problems, copied the data from the old disk to > the new one, everything went smooth. How did you prepare the disk and copy the data? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 14:37:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16543 for freebsd-current-outgoing; Tue, 24 Nov 1998 14:37:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16538 for ; Tue, 24 Nov 1998 14:37:50 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA02818; Tue, 24 Nov 1998 14:37:47 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id OAA01307; Tue, 24 Nov 1998 14:37:46 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 24 Nov 1998 14:37:46 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Julian Elischer Subject: Re: Elf linker question. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Nov-98 Julian Elischer wrote: > On Tue, 24 Nov 1998, John Polstra wrote: > >> It worked just because none of the functions in the missing libraries >> were actually called. Maybe they can't possibly be called in your >> program. But the linker doesn't know that (because there are >> references to some of them even if those references aren't used). So >> it has to be safe and force you to satisfy all external references. >> The a.out linker didn't, and I think it was a bug. > > The trouble with that is that ALL libraries end up being loaded into > memeory whenever one program requires any of them. they also all get > traversed on program startup which keeps them all in memory.. right? Right. The whole files don't get "traversed", but their symbol tables, relocation tables, and data segments do get accessed. It's significant. > not so good for small memory systems. I understand, but nevertheless I think the new linker is doing the right thing. We've gotten plenty of complaints about the behavior of the old one, too. People don't like it when the linker fails to report undefined symbols. I think for your case, you need to look at some combination of the following: * Split your top-level libraries into smaller pieces along functional lines, so that each piece depends on fewer other libraries. * Make stub libraries to replace the ones you know aren't really needed. The stubs should define all the needed symbols, but they should all resolve to a function that generates a fatal error if called. * Don't use shared libraries in some cases. The old behavior was a bug. It's unfortunate that you were unwittingly depending on the bug. But that doesn't mean we should reintroduce the bug again. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 14:43:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17100 for freebsd-current-outgoing; Tue, 24 Nov 1998 14:43:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (31-sweet.camalott.com [208.239.153.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17095 for ; Tue, 24 Nov 1998 14:43:26 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id QAA46391; Tue, 24 Nov 1998 16:43:02 -0600 (CST) (envelope-from joelh) To: oZZ!!! Cc: current@FreeBSD.ORG Subject: Re: X-server crush... References: From: Joel Ray Holveck Date: 24 Nov 1998 16:42:56 -0600 In-Reply-To: oZZ!!!'s message of "Wed, 25 Nov 1998 00:57:28 +0300 (MSK)" Message-ID: <86iug4yaoe.fsf@detlev.UUCP> Lines: 35 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello! > I use windowmaker-0.20.0 in my FreeBSD-3.0-CURRENT Sun Nov 22 > # uname -a > time-2-time X server in my machine crush. > Caught signal 24. Server aborting > Nov 25 00:50:25 ozz /kernel: pid 3663 (XF86_Mach64), uid 0: exited on > signal 6 > X connection to :0.0 broken (explicit kill or server shutdown). > ..... > wmaker warning: got signal 1 (Hangup) - restarting Signal 24 is SIGXCPU, the CPU time limit. I'd say to check your /etc/login.conf; it's probably not sync'd to -current. (You probably should also review the rest of /etc while you're at it.) If there is an /etc/login.conf.db, you also need to either delete it or run cap_mkdb on login.conf. It appears you started the server from a non-root command line, since there is a limit. In that case, you can run 'limits' from the same command line to find the current limits; look for "cputime". If xdm started the server, then you may need to kill and restart xdm. Before 16 Sep, the default login.conf has had a 1.5hr CPU time limit. For a social statistic of CPU usage, my XF86_SVGA server has probably gotten light usage on a 486-100 for three days and has used one hour of CPU time. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 14:58:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18944 for freebsd-current-outgoing; Tue, 24 Nov 1998 14:58:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (31-sweet.camalott.com [208.239.153.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18931 for ; Tue, 24 Nov 1998 14:58:03 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id QAA50918; Tue, 24 Nov 1998 16:57:46 -0600 (CST) (envelope-from joelh) To: John Polstra Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: Elf linker question. References: From: Joel Ray Holveck Date: 24 Nov 1998 16:57:40 -0600 In-Reply-To: John Polstra's message of "Tue, 24 Nov 1998 14:37:46 -0800 (PST)" Message-ID: <86emqsy9zu.fsf@detlev.UUCP> Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The trouble with that is that ALL libraries end up being loaded into >> memeory whenever one program requires any of them. they also all get >> traversed on program startup which keeps them all in memory.. right? > Right. The whole files don't get "traversed", but their symbol > tables, relocation tables, and data segments do get accessed. It's > significant. I thought that the current system, did symbol checking at link time, but still had lazy binding at run time. Am I mistaken here? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 14:58:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18990 for freebsd-current-outgoing; Tue, 24 Nov 1998 14:58:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from okeefe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18985 for ; Tue, 24 Nov 1998 14:58:15 -0800 (PST) (envelope-from geniusj@suarez.bestweb.net) Received: from suarez.bestweb.net (suarez.bestweb.net [209.94.100.150]) by okeefe.bestweb.net (8.9.0/8.9.0) with ESMTP id RAA14956; Tue, 24 Nov 1998 17:57:50 -0500 (EST) Date: Tue, 24 Nov 1998 17:57:21 -0500 (EST) From: Jason Dicioccio To: Brian Feldman cc: Bill Woods , Andrzej Bialecki , FreeBsd-Current , FreeBsd-Current , Doug White Subject: Re: StarOffice 5.0 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 My bad, notice the word "think" On Mon, 23 Nov 1998, Brian Feldman wrote: > > Actually I htink 4.0 does not work with FreeBSD either, I beleive 3.0 is > > only working now although they say they are in the middle of porting it > > (since they have iit on every other OS) > > Really? Thanks for telling me that the copy of StarOFfice 4.0 (no SP level) > that I use all the time on FreeBSD 3.0-CURRENT doesn't work! > > > > > On Thu, 19 Nov 1998, Bill Woods wrote: > > > > > I am going to assume that this version works on FreeBSD in linux emulation > > > ok? > > > > > > On Wed, 18 Nov 1998, Brian Feldman wrote: > > > > > > > On Wed, 18 Nov 1998, William Woods wrote: > > > > > > > > > Care to inform me where I can get 4.0 ? > > > > > > > > ftp://ftp.stardiv.de/pub/so4/linux/sp3/01/so40sp3_lnx_01.tar.gz > > > > > > > > > ---------------------------------- > > > > > E-Mail: William Woods > > > > > Date: 18-Nov-98 > > > > > Time: 15:53:44 > > > > > -->> FreeBSD 3.0 <<-- > > > > > AIM bsdman1 > > > > > --------------------------------- > > > > > > > > Brian Feldman _ __ ___ ___ ___ > > > > green@unixhelp.org _ __ ___ | _ ) __| \ > > > > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > > > > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > 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 Nov 24 14:58:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19015 for freebsd-current-outgoing; Tue, 24 Nov 1998 14:58:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18984 for ; Tue, 24 Nov 1998 14:58:15 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (ppp121.dialup.st.keio.ac.jp [131.113.27.121]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id HAA05534; Wed, 25 Nov 1998 07:57:57 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.8.8/3.6W) id HAA01684; Wed, 25 Nov 1998 07:57:55 +0900 (JST) Date: Wed, 25 Nov 1998 07:57:55 +0900 (JST) Message-Id: <199811242257.HAA01684@lavender.yy.cs.keio.ac.jp> To: admin@sunflower.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic using IPFILTER w/ NAT In-Reply-To: Your message of "Wed, 25 Nov 1998 00:17:32 JST". From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> FreeBSD 3.0-CURRENT #0: Mon Nov 23 21:08:21 CST 1998 >> root@madeline.sunflower.com:/usr/src/sys/compile/MADELINE >> (cvsup'd and compiled on Sunday) >> >> Running: sshd 1.2.26 >> isc-dhcpd server >> BIND 8.1.2 >> sendmail 8.9.1 >> >> Slow but has been steady for the last 4 years. :) >> >> Initial ipnat rules: >> >> map ed0 10.15.0.0/16 -> 0/32 proxy port ftp ftp/tcp >> map ed0 10.15.0.0/16 -> 0/32 portmap tcp/udp 10000:40000 >> map ed0 10.15.0.0/16 -> 0/32 I think version number of IP Filter in 3.0-CURRENT is 3.2.7. Version number of latest and released IP Filter is 3.2.10. I'm member of IP Filter mailing list. I tested many time with 3.2.10 with 2.2.6R box, and ftp proxy has many bugs before ver. 3.2.10 :-< If you do not use ftp proxy and use PASSIVE MODE ftp, your machine will be stable, I think. Moreover, currently ftp proxy reboot problem was fixed, but it does not care lost packet and does not recalculate ack number. I think ftp proxy is experimental code, I do not use this. BTW, IP Filter 3.2.10 does not support FreeBSD-3.0, only support 2.2-stable(2.1?). Darren who is author of IP Filter, said that 3.0R code is too many changes from 2.2-stable, he does not have plan to support 3.0-current. Does someone have plan to port latest IP Filter to FreeBSD-current source?? Cheers MIHIRA Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 15:00:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19394 for freebsd-current-outgoing; Tue, 24 Nov 1998 15:00:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19384 for ; Tue, 24 Nov 1998 15:00:12 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id PAA02968; Tue, 24 Nov 1998 15:00:08 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id PAA01350; Tue, 24 Nov 1998 15:00:07 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <86emqsy9zu.fsf@detlev.UUCP> Date: Tue, 24 Nov 1998 15:00:07 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Joel Ray Holveck Subject: Re: Elf linker question. Cc: current@FreeBSD.ORG, Julian Elischer Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I thought that the current system, did symbol checking at link time, > but still had lazy binding at run time. > > Am I mistaken here? No, you're exactly right. But lazy binding applies only to function calls. There are also data references that have to be relocated. Those can't be done lazily. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 15:27:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22149 for freebsd-current-outgoing; Tue, 24 Nov 1998 15:27:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wabakimi.chat.carleton.ca (wabakimi.chat.carleton.ca [134.117.1.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22142 for ; Tue, 24 Nov 1998 15:27:01 -0800 (PST) (envelope-from mcharles@chat.carleton.ca) Received: from sa513-584.carleton.ca (TO79Z9C+lhrVqIEsBGD24vgfHKBJAikw@sa513-584.carleton.ca [134.117.81.109]) by wabakimi.chat.carleton.ca (8.9.1a/8.9.1) with SMTP id SAA01013 for ; Tue, 24 Nov 1998 18:26:55 -0500 (EST) Message-ID: <365B6AE6.3831@wabakimi.carleton.ca> Date: Tue, 24 Nov 1998 18:26:48 -0800 From: moshesh charles Reply-To: mcharles@chat.carleton.ca Organization: Carleton University X-Mailer: Mozilla 3.01Gold (Win16; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: mailing list Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Please send me current information -- ---------------------------------------------------------------------- moshesh charles Carleton University webpage: http://wabakimi.carleton.ca/~mcharles Email address: mcharles@chat.carleton.ca ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 15:30:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22597 for freebsd-current-outgoing; Tue, 24 Nov 1998 15:30:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.aha.ru (ns1.aha.ru [195.2.80.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22585 for ; Tue, 24 Nov 1998 15:30:23 -0800 (PST) (envelope-from osa@etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by ns1.aha.ru (8.9.1/8.9.1/aha-r/0.04B) with ESMTP id CAA23497; Wed, 25 Nov 1998 02:30:01 +0300 (MSK) Received: by sunny.aha.ru id CAA28684; (8.8.8/vak/1.9) Wed, 25 Nov 1998 02:29:07 +0300 (MSK) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma028651; Wed Nov 25 02:28:43 1998 Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by serv.etrust.ru (8.9.1/8.9.1) with ESMTP id CAA03574; Wed, 25 Nov 1998 02:23:02 +0300 (MSK) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id CAA04394; Wed, 25 Nov 1998 02:21:11 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Wed, 25 Nov 1998 02:21:10 +0300 (MSK) From: oZZ!!! To: Joel Ray Holveck cc: current@FreeBSD.ORG Subject: Re: X-server crush... In-Reply-To: <86iug4yaoe.fsf@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hello! > > I use windowmaker-0.20.0 in my FreeBSD-3.0-CURRENT Sun Nov 22 > > # uname -a > > time-2-time X server in my machine crush. > > Caught signal 24. Server aborting > > Nov 25 00:50:25 ozz /kernel: pid 3663 (XF86_Mach64), uid 0: exited on > > signal 6 > > X connection to :0.0 broken (explicit kill or server shutdown). > > ..... > > wmaker warning: got signal 1 (Hangup) - restarting > > Before 16 Sep, the default login.conf has had a 1.5hr CPU time limit. > For a social statistic of CPU usage, my XF86_SVGA server has probably > gotten light usage on a 486-100 for three days and has used one hour > of CPU time. ok tx 4 your help & your social statistic :-)) > > Happy hacking, u2 > joelh > Rgdz, oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 15:37:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23539 for freebsd-current-outgoing; Tue, 24 Nov 1998 15:37:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23531 for ; Tue, 24 Nov 1998 15:37:54 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA00492; Tue, 24 Nov 1998 18:37:41 -0500 (EST) Date: Tue, 24 Nov 1998 18:37:41 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Kazutaka YOKOTA cc: current@FreeBSD.ORG Subject: Re: video mode switching has gone south In-Reply-To: <199811241703.CAA21858@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Nov 1998, Kazutaka YOKOTA wrote: > > > It seems (nay, it IS so) that video mode switching has gotten extremely > >strange within the last few days. This is not a problem just with vidcontrol > >and syscons, this affects XFree86 as well. I've got two kernels, the old one > >which does not exhibit this problem, and the new one which does. > > > >Working: > > FreeBSD 3.0-CURRENT #3: Sun Nov 22 21:45:52 EST 1998 > >Broken: > > FreeBSD 3.0-CURRENT #4: Mon Nov 23 20:11:02 EST 1998 > [...] > > Video mode switching is defined as "any video mode changing, including > >resolution changing and switching between non- and graphical screen modes," so > >affects X and syscons. An example of what previously happened: > > > >00:00 I type "xmame wb3bl", for example, which uses Xxf86dga > >00:01 xmame initializes, attempts to switch to 320x240 > >00:02 screen blanks > >00:03 320x240 screen pops up, then blanks > >00:04 game shows up > >15:07 I get bored and press escape > >15:08 screen switches back to 1280x1024 > > > > In the newer kernel (more or less, my memory might not be great): > > > >00:00 I type "xmame wb3bl", for example, which uses Xxf86dga > >00:01 xmame initializes, attempts to switch to 320x240 > >00:02 screen blanks > >00:05 1280x1024 screen pops back up, garbled > >00:07 screen blanks > >00:09 1280x1024 screen pops back up > >00:12 screen blanks > >00:17 320x240 screen pops up > >00:19 screen blanks > >00:23 game shows up > >01:40 I press escape because now I'm bored of this game and FreeBSD is being > > annoying > >01:41 screen blanks > >01:45 1280x1024 screen pops back up garbled > >01:46 screen blanks > >01:48 screen is back to normal > > > > If anyone has any ideas why any of this is happening now, I'd like to hear > >any possible explanations. > > Video mode switching in the X session is completely managed by the X > server. The kernel and syscons are not in any way involved. > > Which version of XFree86 are you using? > > Do you see any problems outside the X as well? Do you see garbled or > blank screen when you try to change video mode via vidcontrol? > > Kazu > > I thought that the server managed all video access, but what does it say when one kernel works, and one the next day doesn't work right? And this is supposed to be managed by X server, at the hardware- ish level... very strange, isn't it? XFree86 3.3.2.3 plus Xtt is what I'm running. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 15:54:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24710 for freebsd-current-outgoing; Tue, 24 Nov 1998 15:54:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (31-sweet.camalott.com [208.239.153.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24702 for ; Tue, 24 Nov 1998 15:54:47 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id RAA86047; Tue, 24 Nov 1998 17:54:16 -0600 (CST) (envelope-from joelh) To: John Polstra Cc: current@FreeBSD.ORG, Julian Elischer Subject: Re: Elf linker question. References: From: Joel Ray Holveck Date: 24 Nov 1998 17:54:11 -0600 In-Reply-To: John Polstra's message of "Tue, 24 Nov 1998 15:00:07 -0800 (PST)" Message-ID: <86d86cy7do.fsf@detlev.UUCP> Lines: 19 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I thought that the current system, did symbol checking at link time, >> but still had lazy binding at run time. >> Am I mistaken here? > No, you're exactly right. But lazy binding applies only to function > calls. There are also data references that have to be relocated. > Those can't be done lazily. How are things like: sighander_t mysig = libsig; handled? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 16:27:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29945 for freebsd-current-outgoing; Tue, 24 Nov 1998 16:27:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from varmail.net (varmail.net [203.46.50.11] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29508; Tue, 24 Nov 1998 16:24:25 -0800 (PST) (envelope-from offer@varmail.net) Received: from localhost (root@localhost) by varmail.net (8.8.8/8.8.8) with SMTP id KAA08558; Wed, 25 Nov 1998 10:22:43 +1000 (EST) (envelope-from offer@varmail.net) Date: Wed, 25 Nov 1998 10:22:43 +1000 (EST) Received: by varmail.net (bulk_mailer v1.11); Wed, 25 Nov 1998 02:07:25 +1000 From: melanie@varmail.net To: members@wetmelanie.com Subject: A Great Selection of FREE Adult Sites! Message-ID: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have put together a list of 4 Great Adult sites for your viewing pleasure, all FREE and exclusive. Just click on http://www.varmail.net/1011/ to browse the great, FREE content on offer. Click Here ------------------------------------------------ You are receiving this message because you, or someone pretending to be you, added your contact address to our list. To remove yourself from this mailing list please reply to this message with "Remove" in the subject field. ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 16:30:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00925 for freebsd-current-outgoing; Tue, 24 Nov 1998 16:30:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00916 for ; Tue, 24 Nov 1998 16:30:54 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id QAA03405; Tue, 24 Nov 1998 16:30:50 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id QAA01461; Tue, 24 Nov 1998 16:30:49 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <86d86cy7do.fsf@detlev.UUCP> Date: Tue, 24 Nov 1998 16:30:49 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Joel Ray Holveck Subject: Re: Elf linker question. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Nov-98 Joel Ray Holveck wrote: >> No, you're exactly right. But lazy binding applies only to function >> calls. There are also data references that have to be relocated. >> Those can't be done lazily. > > How are things like: > sighander_t mysig = libsig; > handled? Any time you take the address of a function, the linker actually fills in the address of a little stub routine. It's the same stub that gets called when you call an external function. The first time it is executed, the stub jumps to code in the dynamic linker that does the lazy binding to whatever function is being called. Then it rewires itself (an indirect jump is used) so that all future calls will go straight to the target function. I'm glossing over some details. But anyway, you get the address of the stub, not the address of the actual function. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 16:40:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02098 for freebsd-current-outgoing; Tue, 24 Nov 1998 16:40:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02088 for ; Tue, 24 Nov 1998 16:40:36 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA15390; Wed, 25 Nov 1998 11:10:31 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA69501; Wed, 25 Nov 1998 11:10:27 +1030 (CST) Message-ID: <19981125111027.G67961@freebie.lemis.com> Date: Wed, 25 Nov 1998 11:10:27 +1030 From: Greg Lehey To: "Roman V. Palagin" , Karl Pielorz Cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity References: <365A7F6A.3ED8A6D6@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Roman V. Palagin on Tue, Nov 24, 1998 at 12:54:35PM +0300 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 Tuesday, 24 November 1998 at 12:54:35 +0300, Roman V. Palagin wrote: > On Tue, 24 Nov 1998, Karl Pielorz wrote: > >> >> I thought this had been fixed a while ago? - my system (current as of >> Thu/19/11/98) doesn't show any symptoms (it's an SMP P-Pro 200), even when >> busy (14 drives across 5 controllers) - it certainly makes it past the usual >> 2am cron-job's, and backups etc. > > It was fixed by McKusick 17/11/98. But it's very interesting: I've > current as of 23/11/98 and kernel crashes without disabling 'realloc' > code, maximum uptime about 5-6 hours. Previous kernel was as of about > 20/11/98 and works without any problems 8-) It's looks like something > changed in src/sys tree. To be fair, Kirk wasn't 100% sure it would fix the problem. He sent me a fix (I was the first to report the problem), and it hasn't occurred since. It doesn't mean it's completely fixed, nor that your problem is the same. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 17:17:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06526 for freebsd-current-outgoing; Tue, 24 Nov 1998 17:17:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06521 for ; Tue, 24 Nov 1998 17:17:25 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id RAA25566; Tue, 24 Nov 1998 17:18:16 -0800 (PST) Message-Id: <199811250118.RAA25566@root.com> To: Greg Lehey cc: "Roman V. Palagin" , Karl Pielorz , current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Wed, 25 Nov 1998 11:10:27 +1030." <19981125111027.G67961@freebie.lemis.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 24 Nov 1998 17:18:16 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Tuesday, 24 November 1998 at 12:54:35 +0300, Roman V. Palagin wrote: >> On Tue, 24 Nov 1998, Karl Pielorz wrote: >> >>> >>> I thought this had been fixed a while ago? - my system (current as of >>> Thu/19/11/98) doesn't show any symptoms (it's an SMP P-Pro 200), even when >>> busy (14 drives across 5 controllers) - it certainly makes it past the usual >>> 2am cron-job's, and backups etc. >> >> It was fixed by McKusick 17/11/98. But it's very interesting: I've >> current as of 23/11/98 and kernel crashes without disabling 'realloc' >> code, maximum uptime about 5-6 hours. Previous kernel was as of about >> 20/11/98 and works without any problems 8-) It's looks like something >> changed in src/sys tree. > >To be fair, Kirk wasn't 100% sure it would fix the problem. He sent >me a fix (I was the first to report the problem), and it hasn't >occurred since. It doesn't mean it's completely fixed, nor that your >problem is the same. Guys, would you please look at the file sys/kern/vfs_cluster.c and verify that you have rev 1.74? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 18:08:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11668 for freebsd-current-outgoing; Tue, 24 Nov 1998 18:08:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11661 for ; Tue, 24 Nov 1998 18:08:30 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id SAA00353; Tue, 24 Nov 1998 18:15:50 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811250215.SAA00353@troutmask.apl.washington.edu> Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <199811250118.RAA25566@root.com> from David Greenman at "Nov 24, 1998 5:18:16 pm" To: dg@root.com Date: Tue, 24 Nov 1998 18:15:49 -0800 (PST) Cc: grog@lemis.com, romanp@wuppy.rcs.ru, kpielorz@tdx.co.uk, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to David Greenman: > > Guys, would you please look at the file sys/kern/vfs_cluster.c and verify > that you have rev 1.74? > rm -rf /usr/sys cvsup at 981124.1614 pst It crashes. I have an ELF kernel with debugging symbols. I can not get a dump. If I issue 'panic' at the db> prompt the system locks up tight. No keyboard, no disk activity, nothing. All I have is a stack trace: dev=0x20404, bno = 34, bsize = 8192, size = 8192, fs = /var panic: ffs_blkfree: bad size mp_lock = 00000001; cpuid = 0; lapic.id = 01000000 Debugger("panic") Stopped at _Debugger+0x35: movb $0, _in_Debugger.98 db> trace _Debugger() at _Debugger+0x35 _panic() at _panic+0x9f _ffs_blkfree() at _ffs_blkfree+0xc2 _ffs_reallocblks() at _ffs_reallocblks+0x420 _cluster_write() at _cluster_write+0x15f _ffs_write() at _ffs_write+0x56f _vn_write() at _vn_write+0xef _write() at _write+0xba _syscall() at _syscall+0x187 _Xint0x80_syscall() at _Xint0x80_syscall+0x4c If someone can clue me in on getting a crash dump, I'll give Kirk access to my machines to debug this. I have dumpdev=/dev/da1s1b in my rc.conf, and da1s1b is nearly 700MB in size. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 18:09:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11769 for freebsd-current-outgoing; Tue, 24 Nov 1998 18:09:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11759 for ; Tue, 24 Nov 1998 18:09:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02557; Tue, 24 Nov 1998 18:07:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811250207.SAA02557@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson cc: "Norman C. Rice" , Bruce Evans , mjacob@feral.com, current@FreeBSD.ORG Subject: Re: Location for driver includes (was Re: Breakage in -current for theALPHA) In-reply-to: Your message of "Tue, 24 Nov 1998 11:14:53 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Nov 1998 18:07:15 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is it worth sorting includes based on the type of bus which the hardware > is attached to? Something like: > > sys/dev/include non-bus-specific includes > sys/dev/include/isa isa bus includes > sys/dev/include/pci pci bus includes > ... I don't think so; there's always the case where one device with several different bus interfaces but a consistent user-space presentation will spanner the works. IMHO, device-driver headers fall into two categories: - headers consumed only by the driver These should live with the driver source files. - headers consumed by users-space driver users These should be installed in a single location. They might want to live with the driver source files as well, although this may complicate the install process slightly. There should be a clear logical division between the two types of files, even if they're kept together. I don't see any actual virtue in separating the user-consumed headers from the driver source other than to make the install process easier. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 18:31:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13096 for freebsd-current-outgoing; Tue, 24 Nov 1998 18:31:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13091 for ; Tue, 24 Nov 1998 18:30:57 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id SAA26639; Tue, 24 Nov 1998 18:26:57 -0800 (PST) Message-Id: <199811250226.SAA26639@root.com> To: Steve Kargl cc: grog@lemis.com, romanp@wuppy.rcs.ru, kpielorz@tdx.co.uk, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Tue, 24 Nov 1998 18:15:49 PST." <199811250215.SAA00353@troutmask.apl.washington.edu> From: David Greenman Reply-To: dg@root.com Date: Tue, 24 Nov 1998 18:26:57 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >According to David Greenman: >> >> Guys, would you please look at the file sys/kern/vfs_cluster.c and verify >> that you have rev 1.74? >> > >rm -rf /usr/sys >cvsup at 981124.1614 pst That's not what I asked you to do. I asked for you to look at the rev of the vfs_cluster.c file. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 18:32:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13369 for freebsd-current-outgoing; Tue, 24 Nov 1998 18:32:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13318 for ; Tue, 24 Nov 1998 18:31:26 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id SAA00571; Tue, 24 Nov 1998 18:38:33 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811250238.SAA00571@troutmask.apl.washington.edu> Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <19981125111027.G67961@freebie.lemis.com> from Greg Lehey at "Nov 25, 1998 11:10:27 am" To: grog@lemis.com (Greg Lehey) Date: Tue, 24 Nov 1998 18:38:33 -0800 (PST) Cc: romanp@wuppy.rcs.ru, kpielorz@tdx.co.uk, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Greg Lehey: > > To be fair, Kirk wasn't 100% sure it would fix the problem. He sent > me a fix (I was the first to report the problem), and it hasn't > occurred since. It doesn't mean it's completely fixed, nor that your > problem is the same. > Are you running your system with softupdates on the filesystems? If I understand ffs_alloc.c, then ffs_dorealloc() calls ffs_blkfree() at only one location. And, the call to ffs_blkfree() is conditional on not running softupdates. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 19:50:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18542 for freebsd-current-outgoing; Tue, 24 Nov 1998 19:50:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www0p.netaddress.usa.net (www0p.netaddress.usa.net [204.68.24.45]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA18527 for ; Tue, 24 Nov 1998 19:50:03 -0800 (PST) (envelope-from slpalmer@netscape.net) Received: (qmail 7729 invoked by uid 60001); 25 Nov 1998 03:49:56 -0000 Message-ID: <19981125034956.7728.qmail@www0p.netaddress.usa.net> Received: from 204.68.24.45 by www0p via web-mailer(R2.6) on Wed Nov 25 03:49:56 GMT 1998 Date: 25 Nov 98 03:49:56 America/Fort_Wayne From: Stephen Palmer To: Subject: kernel "make depend' fails with "controller ppbus0" in config Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id TAA18537 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With controller ppbus0 activated in /sys/i386/conf/MIDEARTH (my system name).. "make depend" stage of the kernel compile fails as follows... [...snip] ../../dev/ppbus/lpbb.c:53: iicbb_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop. midearth:/sys/compile/MIDEARTH $ [snip] I've done a find on the /usr/src tree for iicbb_if.h with no luck, and if I comment it out of /sys/dev/ppbus/lpbb.c, "make" fails. Was this file overlooked when the Parallel Port Bus stuff was merged into current? --- | Stephen L. Palmer | Sprint Paranet slpalmer@netscape.net \|/ slpalmer@sprintparanet.com "There are thousands of intelligent species in the Universe, and they all own cats." -Unknown ____________________________________________________________________ More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 20:02:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19727 for freebsd-current-outgoing; Tue, 24 Nov 1998 20:02:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19713 for ; Tue, 24 Nov 1998 20:02:08 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA17400; Wed, 25 Nov 1998 15:01:48 +1100 Date: Wed, 25 Nov 1998 15:01:48 +1100 From: Bruce Evans Message-Id: <199811250401.PAA17400@godzilla.zeta.org.au> To: archie@whistle.com, bde@zeta.org.au Subject: Re: snprintf() in the kernel Cc: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG, grog@lemis.com, rnordier@nordier.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> strncpy() already takes a length arg. Changing from strncpy() to >> snprintf() just wastes space and time unless the value returned by >> snprintf() is actually checked and cases where the string doesn't >> fit are actually handled. > >Except when there needs to be a trailing NUL byte and the original >code doesn't manually put one in the last buffer byte. For example, Then the fix should usually be to put one in. >> > netatm/spans/spans_print.c >> >> It's interesting that it doesn't just printf everything (using separate >Yes, the code is technically correct, but figuring this out requires >reverse engineering a bunch of function calls, etc. before you can >conclude that there's no actual bug there. Why force a future >programmer to have to rediscover that the buffers won't overflow? >Why not make it obvious? This is not a bug fix but rather a >maintainability fix, as are most of these.. We don't maintain HARP. Its maintainers presumably have to worry about snprintf() not being available on all supported platforms. >> > i386/ibcs2/ibcs2_stat.c >> > i386/ibcs2/ibcs2_xenix.c >> > i386/linux/linux_misc.c >> >> These depend on a previous bzero() to zero out the buffer (and any padding >> in the struct). The strncpy()'s of course should have used sizeof() instead >> of literal constants. The explicit \0 termiation could have been avoided >> in ibcs2_stat.c by subtracting 1 from the sizes. This is already done in >> ibcs2_xenix.c and linux_misc.c, but it is hard to see because sizeof() is >> not used and the subtraction is done at code-write time. > >Again, the code is technically correct but less than pleasant to look at >and requires analysis and cross-checking to conclude that there's no >actual bug.. yuck. The faults in the code don't include using strncpy(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 20:17:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21236 for freebsd-current-outgoing; Tue, 24 Nov 1998 20:17:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (31-sweet.camalott.com [208.239.153.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21231 for ; Tue, 24 Nov 1998 20:17:20 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA14769; Tue, 24 Nov 1998 22:17:00 -0600 (CST) (envelope-from joelh) To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: Elf linker question. References: From: Joel Ray Holveck Date: 24 Nov 1998 22:16:58 -0600 In-Reply-To: John Polstra's message of "Tue, 24 Nov 1998 16:30:49 -0800 (PST)" Message-ID: <86btlwxv7p.fsf@detlev.UUCP> Lines: 22 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> How are things like: >> sighander_t mysig = libsig; >> handled? > Any time you take the address of a function, the linker actually fills > in the address of a little stub routine. It's the same stub that > gets called when you call an external function. The first time it is > executed, the stub jumps to code in the dynamic linker that does the > lazy binding to whatever function is being called. Then it rewires > itself (an indirect jump is used) so that all future calls will go > straight to the target function. Oh, so it doesn't snap the pointer in the code? It just leaves it pointing to the stub? Thanks, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 21:03:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24731 for freebsd-current-outgoing; Tue, 24 Nov 1998 21:03:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24724 for ; Tue, 24 Nov 1998 21:03:10 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA23511; Wed, 25 Nov 1998 16:02:57 +1100 Date: Wed, 25 Nov 1998 16:02:57 +1100 From: Bruce Evans Message-Id: <199811250502.QAA23511@godzilla.zeta.org.au> To: dfr@nlsystems.com, mike@smith.net.au Subject: Re: Location for driver includes (was Re: Breakage in -current for theALPHA) Cc: bde@zeta.org.au, current@FreeBSD.ORG, mjacob@feral.com, nrice@emu.sourcee.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >IMHO, device-driver headers fall into two categories: > > - headers consumed only by the driver > These should live with the driver source files. These should only exist if there are multiple C source files. Third category: - headers consumed only by the driver, but not driver-specific. These are currently mostly in /sys/i386/isa/ic or combined with headers in the first category. They should be elsewhere. Since I don't believe in /dev, I would attempt to put them in /sys/ic and /sys/{isa,pci,...}. > - headers consumed by users-space driver users > These should be installed in a single location. They might want to > live with the driver source files as well, although this may > complicate the install process slightly. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 21:38:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27778 for freebsd-current-outgoing; Tue, 24 Nov 1998 21:38:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from websmtp1.bellsouth.bigfoot.com (websmtp1.bellsouth.bigfoot.com [208.156.60.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27752 for ; Tue, 24 Nov 1998 21:37:58 -0800 (PST) (envelope-from publish007@webmail.bellsouth.com) From: publish007@webmail.bellsouth.com Received: from default (171-210-58.ipt.aol.com [152.171.210.58]) by websmtp1.bellsouth.bigfoot.com (8.9.1/8.8.5) with SMTP id AAA14721; Wed, 25 Nov 1998 00:35:58 -0500 (EST) Date: Wed, 25 Nov 1998 00:35:58 -0500 (EST) Subject: New Book: "Brothers Beware: Games Black Women Play" Message-Id: Content-Type: TEXT/PLAIN charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; Sisters are saying: "Burn This Book" Brothers are saying: "Free at Last!" You decide . . . Call Today To Order This Book - (800) 830-2047 It will make a great Christmas Gift Brothers Beware: Games Black Women Play by A. Marshall ISBN:0-9658299-3-6 Price: $12.00 $3 Shipping - COD Charges are FREE for a limited time. ____________________________ Brothers Beware: Games Black Women Play is a book that pulls no punches when it details the many tricks and manipulative games for which black women are notorious. This book is an honest, no holds barred, uncensored discussion about dating in the African American community. The number of eligible black men is constantly decreasing. Therefore, black women are doing whatever is necessary to find and keep a good black man. Many of her secrets are exposed in this book. The author interviewed several black women who revealed many of the techniques used by Sisters to get what they want, and who they want, any time they want. These women were especially helpful on the hilarious chapter entitled: "Games Women Play On Each Other." The author had no need whatsoever to embellish - The TRUTH was definitely sensational enough. ____________________________ Chapters "Was She Born This Way?" "What He Has Have To Be With Her" "What Have You Done For Me Lately?" "Lies Women Tell Men" "She's Got The Power" "The Dating Game" "The Sympathy Game" "The Suicide Game" "Honey, I'm Pregnant" "She Loves Me . . . She Loves Me Not" "Games Church Women Play" "Young Women and Old Fools" "Games Women Play on Each Other" "Was It Really Worth It?" _______________________________ Ordering Information Brothers Beware: Games Black Women Play ISBN:0-9658299-3-6 Price: $12.00 $3.00 Shipping - COD Charges are free for a limited time. Wholesale Discounts Available ______________________________ Order by Phone 800-830-2047 - 24 hrs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 21:42:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28536 for freebsd-current-outgoing; Tue, 24 Nov 1998 21:42:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28529 for ; Tue, 24 Nov 1998 21:42:02 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id AAA27421; Wed, 25 Nov 1998 00:41:56 -0500 (EST) Date: Wed, 25 Nov 1998 00:41:56 -0500 (EST) Message-Id: <199811250541.AAA27421@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: accept(2) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quick man page fix for someone: The man page for accept() doesn't say anything about EINTR being a valid error return. However, in libc_r (/usr/src/lib/libc_r/uthread/uthread_accept.c), it can (and does) return EINTR. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 22:31:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02233 for freebsd-current-outgoing; Tue, 24 Nov 1998 22:31:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02217 for ; Tue, 24 Nov 1998 22:31:22 -0800 (PST) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (peer cross-checked as room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru with ESMTP id IAA05194; Wed, 25 Nov 1998 08:38:24 +0300 (MSK) (envelope-from romanp@wuppy.rcs.ru) Date: Wed, 25 Nov 1998 08:38:23 +0300 (MSK) From: "Roman V. Palagin" To: David Greenman cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <199811250118.RAA25566@root.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, 24 Nov 1998, David Greenman wrote: > Guys, would you please look at the file sys/kern/vfs_cluster.c and verify > that you have rev 1.74? $Id: vfs_cluster.c,v 1.74 1998/11/17 00:31:12 mckusick Exp $ And I still experience problem with 'realloc' code enabled :( I've good old AMD 486DX133, so no overclocking. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE | Just because you're paranoid Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 22:32:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02452 for freebsd-current-outgoing; Tue, 24 Nov 1998 22:32:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02249 for ; Tue, 24 Nov 1998 22:31:51 -0800 (PST) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (peer cross-checked as room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru with ESMTP id IAA05204; Wed, 25 Nov 1998 08:44:38 +0300 (MSK) (envelope-from romanp@wuppy.rcs.ru) Date: Wed, 25 Nov 1998 08:44:36 +0300 (MSK) From: "Roman V. Palagin" To: Steve Kargl cc: Greg Lehey , kpielorz@tdx.co.uk, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <199811250238.SAA00571@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Nov 1998, Steve Kargl wrote: > > Are you running your system with softupdates on the filesystems? YES. > > If I understand ffs_alloc.c, then ffs_dorealloc() calls ffs_blkfree() > at only one location. And, the call to ffs_blkfree() is conditional > on not running softupdates. > > -- > Steve > > finger kargl@troutmask.apl.washington.edu > http://troutmask.apl.washington.edu/~clesceri/kargl.html > ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE | Just because you're paranoid Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 22:43:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02958 for freebsd-current-outgoing; Tue, 24 Nov 1998 22:43:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02952 for ; Tue, 24 Nov 1998 22:43:22 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA22844; Tue, 24 Nov 1998 22:42:13 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma022842; Tue, 24 Nov 98 22:41:58 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA11190; Tue, 24 Nov 1998 22:41:58 -0800 (PST) From: Archie Cobbs Message-Id: <199811250641.WAA11190@bubba.whistle.com> Subject: Re: accept(2) In-Reply-To: <199811250541.AAA27421@highwind.com> from HighWind Software Information at "Nov 25, 98 00:41:56 am" To: info@highwind.com (HighWind Software Information) Date: Tue, 24 Nov 1998 22:41:58 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HighWind Software Information writes: > Quick man page fix for someone: > > The man page for accept() doesn't say anything about EINTR being a > valid error return. > > However, in libc_r (/usr/src/lib/libc_r/uthread/uthread_accept.c), it > can (and does) return EINTR. Good catch.. please file a PR to be sure that it gets fixed. Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 22:46:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03267 for freebsd-current-outgoing; Tue, 24 Nov 1998 22:46:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hsw.generalresources.com ([203.79.17.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03259 for ; Tue, 24 Nov 1998 22:46:25 -0800 (PST) (envelope-from hsw@email.generalresources.com) Received: from hsw.generalresources.com (localhost.generalresources.com [127.0.0.1]) by hsw.generalresources.com (8.9.1/8.9.1) with ESMTP id OAA01720; Wed, 25 Nov 1998 14:40:26 +0800 (CST) (envelope-from hsw@hsw.generalresources.com) Message-Id: <199811250640.OAA01720@hsw.generalresources.com> To: Mike Smith cc: freebsd-current@FreeBSD.ORG From: Christopher Hall Reply-to: Christopher Hall Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Message of "Mon, 23 Nov 1998 18:10:40 PST." <199811240210.SAA01652@dingo.cdrom.com> X-Operating-System: FreeBSD 3.0 X-Mailer: exmh 2.0 Date: Wed, 25 Nov 1998 14:40:26 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199811240210.SAA01652@dingo.cdrom.com>, Mike Smith writes: >... >> What should rootdev be set to when booting da0s1a with one IDE drive? > >Ignore $rootdev and instead set $num_ide_disks to 1. > That works, thanks. Another question: Is there any way to boot DOS from /boot/loader? Perhaps using some Forth code? --- Christopher Hall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 23:14:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04684 for freebsd-current-outgoing; Tue, 24 Nov 1998 23:14:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04679 for ; Tue, 24 Nov 1998 23:14:32 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id XAA15979; Tue, 24 Nov 1998 23:13:48 -0800 Date: Tue, 24 Nov 1998 23:13:47 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Bruce Evans cc: dfr@nlsystems.com, mike@smith.net.au, current@FreeBSD.ORG, nrice@emu.sourcee.com Subject: Re: Location for driver includes (was Re: Breakage in -current for theALPHA) In-Reply-To: <199811250502.QAA23511@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Nov 1998, Bruce Evans wrote: > >IMHO, device-driver headers fall into two categories: > > > > - headers consumed only by the driver > > These should live with the driver source files. > > These should only exist if there are multiple C source files. > > Third category: > - headers consumed only by the driver, but not driver-specific. > These are currently mostly in /sys/i386/isa/ic or combined > with headers in the first category. They should be elsewhere. > Since I don't believe in /dev, I would attempt to put them in > /sys/ic and /sys/{isa,pci,...}. > Would I/O Subsystem specific files (e.g., SCSI or FC4/FibreChannel) be in the 3rd category? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 23:25:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05378 for freebsd-current-outgoing; Tue, 24 Nov 1998 23:25:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05372 for ; Tue, 24 Nov 1998 23:25:42 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id CAA27686; Wed, 25 Nov 1998 02:25:34 -0500 (EST) Date: Wed, 25 Nov 1998 02:25:34 -0500 (EST) Message-Id: <199811250725.CAA27686@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: close() can hang! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Follow this: --- A libc_r linked program starts up, binds a TCP port, dup2()'s the socket to STDIN and execv()'s another libc_r linked program. The new libc_r linked program starts a thread that calls "accept()" on STDIN. Once that happens. If the new program calls "close()" STDIN, it hangs! All fd's are blocking fd's at the application level. --- This is bad. Since the new program can't "close()" STDIN, it is in deep trouble if it wants to dup2() something else to STDIN! I have a test case that illustrates this and it is repeatable. I can provide it. However, I suspect this is a logic issue and somebody who understands the STDIN vs exec vs dup2 vs accept issues better than I can probably just pinpoint what is going on. Any ideas here? -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 23:57:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07408 for freebsd-current-outgoing; Tue, 24 Nov 1998 23:57:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07403 for ; Tue, 24 Nov 1998 23:57:34 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id IAA00320; Wed, 25 Nov 1998 08:58:45 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Wed, 25 Nov 1998 08:58:44 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Steve Kargl cc: dg@root.com, grog@lemis.com, romanp@wuppy.rcs.ru, kpielorz@tdx.co.uk, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <199811250215.SAA00353@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Nov 1998, Steve Kargl wrote: > If someone can clue me in on getting a crash dump, I'll > give Kirk access to my machines to debug this. I have > dumpdev=/dev/da1s1b in my rc.conf, and da1s1b is nearly > 700MB in size. In such case you may consider hooking up another machine over a null-modem cable, and establish "remote GDB" session - it's extremely helpful, even better than a crashdump. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 24 23:59:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07825 for freebsd-current-outgoing; Tue, 24 Nov 1998 23:59:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bfc.dk ([194.192.110.140]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA07815 for ; Tue, 24 Nov 1998 23:59:33 -0800 (PST) (envelope-from npe@bfc.dk) From: npe@bfc.dk Received: by bfc.dk(Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) id 412566C7.002B823D ; Wed, 25 Nov 1998 08:55:13 +0100 X-Lotus-FromDomain: BFC-DATA@BFC To: freebsd-current@FreeBSD.ORG Message-ID: <412566C7.002B3390.00@bfc.dk> Date: Wed, 25 Nov 1998 08:56:01 +0100 Subject: Porting driver from 2.2.x to 3.0-x 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 currently trying to port the Compaq SmartRaid driver to 3.0 and is almost done (with a limited version!) but my problem is that the buf->b_un.??? does not exist in 3.0... Is the buf structs totally rewritten or is it just a matter of names ?? Nicolai. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 00:44:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11034 for freebsd-current-outgoing; Wed, 25 Nov 1998 00:44:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11029 for ; Wed, 25 Nov 1998 00:44:47 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id DAA27850; Wed, 25 Nov 1998 03:44:33 -0500 (EST) Date: Wed, 25 Nov 1998 03:44:33 -0500 (EST) Message-Id: <199811250844.DAA27850@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: Resend Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to track a problem where a "write()" to a socket sends the beginning of the data over and over. I'm looking at "sosend()" in uipc_socket.c, a comment says: > * Returns nonzero on error, timeout or signal; callers > * must check for short counts if EINTR/ERESTART are returned. > * Data and control buffers are freed on return. However, I don't see anywhere in the code where it returns EINTR/ERESTART. That is, if this code mistakenly loops when it gets interrupted or does a partial write(), it would result in the behavior I am seeing. That is: When asked to write a big buffer "1234", we are sometimes seeing on the network connection: "1121231234" Any ideas? -Rob ps. Sorry for all the questions and issues. I'm trying to help the best I can given my new-ness to the FreeBSD internals. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 00:46:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11341 for freebsd-current-outgoing; Wed, 25 Nov 1998 00:46:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freesbee.t.dk (freesbee.t.dk [193.163.159.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA11334 for ; Wed, 25 Nov 1998 00:46:57 -0800 (PST) (envelope-from jesper@freesbee.t.dk) Received: (qmail 28112 invoked by uid 1001); 25 Nov 1998 08:46:41 -0000 Date: Wed, 25 Nov 1998 09:46:41 +0100 From: Jesper Skriver To: David Greenman Cc: Greg Lehey , "Roman V. Palagin" , Karl Pielorz , current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity Message-ID: <19981125094641.A28029@skriver.dk> References: <19981125111027.G67961@freebie.lemis.com> <199811250118.RAA25566@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: <199811250118.RAA25566@root.com>; from David Greenman on Tue, Nov 24, 1998 at 05:18:16PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 24, 1998 at 05:18:16PM -0800, David Greenman wrote: > Guys, would you please look at the file sys/kern/vfs_cluster.c and verify > that you have rev 1.74? I have rev 1.74. I installed a 3.0-RELEASE monday (11/23), and ran cvsup to get it updated, I upgraded the kernel, and made a "make buildworld && make installworld", after that the box crashes when running X and starting a few programs, or when running a make buildworld .... I happend before I enabled softupdates, and it has happend afterwards. On one time I got the output from the panic. fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read page not present instruction pointer = 0x8 : 0xf01d6583 stack pointer = 0x10 : 0xf4345afc frame pointer = 0x10 : 0xf4345b04 code segment = base 0x0 limit 0xfffff type 0x1b = DPL0 pres1 def 321 gran 1 processor eflags = interrupt enabled, resume IOPL = 0 current process = 290 (as) interrrupt mask = net tty bio cam trap number = 12 panic: page fault Output from dmesg: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #2: Tue Nov 24 11:14:01 CET 1998 root@pagedaemon.tde.tdb.dk:/usr/src/sys/compile/PAGEDAEMON Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 132954284 Hz CPU: Pentium/P54C (132.95-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 67108864 (65536K bytes) config> quit avail memory = 62824448 (61352K bytes) Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 chip2: rev 0x02 on pci0.9.0 ahc0: rev 0x00 int a irq 10 on pci0.10.0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs vga0: rev 0x03 on pci0.11.0 lnc1: rev 0x16 int a irq 11 on pci0.12.0 lnc1: PCnet-PCI II address 02:07:01:20:0e:18 Probing for devices on PCI bus 1: ahc1: rev 0x03 int a irq 12 on pci1.4.0 ahc1: aic7870 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc2: rev 0x00 int a irq 11 on pci1.5.0 RAID functionality unsupported ahc3: rev 0x03 int a irq 12 on pci1.8.0 ahc3: aic7870 Wide Channel B, SCSI Id=7, 16/255 SCBs ahc4: rev 0x03 int a irq 12 on pci1.12.0 ahc4: aic7870 Wide Channel C, SCSI Id=7, 16/255 SCBs Probing for devices on the ISA bus: VESA: v1.2, 2048k memory, flags:0x0, mode table:0xf00c4886 (c0004886) VESA: ATI MACH64 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <12 virtual consoles, flags=0x0> psm0 not found at 0x60 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in lnc0 not found at 0x280 npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround Waiting 2 seconds for SCSI devices to settle changing root device to da0s1a cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 5.0MB/s transfers (5.0MHz, offset 15) cd0: cd present [97654 x 2048 byte records] da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) WARNING: / was not properly dismounted ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates lnc1: Receive CRC error lnc1: Receive CRC error Kernel configuration: machine "i386" cpu "I586_CPU" ident PAGEDAEMON maxusers 16 options INET options FFS options NFS #options NFS_NOSERVER options "CD9660" options FFS_ROOT options PROCFS #options MSDOSFS options "COMPAT_43" options SCSI_DELAY=2000 #options SCSI_CAM #We're using CAM in this kernel #options BOUNCE_BUFFERS options UCONSOLE options USERCONFIG options "MAXCONS=12" options VISUAL_USERCONFIG options SOFTUPDATES #options "AUTO_EOI_1" #options "AUTO_EOI_2" #options "CLK_USE_I8254_CALIBRATION" options CLK_USE_TSC_CALIBRATION options COMPAT_LINUX config kernel root on da0 controller isa0 #controller pnp0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 controller ahc0 controller scbus0 device da0 #device sa0 device cd0 device pass0 device psm0 at isa? port IO_KBD conflicts tty irq 12 #device pcm0 #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 #device sbxvi0 at isa? drq 5 #device sbmidi0 at isa? port 0x330 #device opl0 at isa? port 0x388 device sc0 at isa? port IO_KBD conflicts tty irq 1 options SC_HISTORY_SIZE=1024 options XSERVER device npx0 at isa? port IO_NPX irq 13 #device apm0 at isa? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device lnc0 at isa? port 0x280 net irq 10 drq 0 device lpt0 at isa? port? tty irq 7 #device fxp0 device xl0 pseudo-device loop pseudo-device ether pseudo-device pty 16 pseudo-device gzip pseudo-device vn pseudo-device bpfilter 4 options KTRACE options SYSVSHM options SYSVSEM options SYSVMSG options "VM86" options VESA /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 01:16:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13252 for freebsd-current-outgoing; Wed, 25 Nov 1998 01:16:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freesbee.t.dk (freesbee.t.dk [193.163.159.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA13214 for ; Wed, 25 Nov 1998 01:16:28 -0800 (PST) (envelope-from jesper@freesbee.t.dk) Received: (qmail 28387 invoked by uid 1001); 25 Nov 1998 09:16:06 -0000 Date: Wed, 25 Nov 1998 10:16:06 +0100 From: Jesper Skriver To: David Greenman Cc: Greg Lehey , "Roman V. Palagin" , Karl Pielorz , current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity Message-ID: <19981125101606.A28378@skriver.dk> References: <19981125111027.G67961@freebie.lemis.com> <199811250118.RAA25566@root.com> <19981125094641.A28029@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: <19981125094641.A28029@skriver.dk>; from Jesper Skriver on Wed, Nov 25, 1998 at 09:46:41AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 25, 1998 at 09:46:41AM +0100, Jesper Skriver wrote: I just spoke to Poul Henning Kamp, he wanted me to give this ... > instruction pointer = 0x8 : 0xf01d6583 Snip from /usr/libexec/aout/nm -n /kernel f01d6320 T _zinitna f01d645c T _zinit f01d64b4 T _zbootinit f01d655c T _zalloci f01d65a0 T _zfreei f01d65dc T __zget f01d6798 t _sysctl_vm_zone f01d6910 t ___set_sysctl__vm_sym_sysctl___vm_zone /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 01:20:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13719 for freebsd-current-outgoing; Wed, 25 Nov 1998 01:20:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13714 for ; Wed, 25 Nov 1998 01:20:48 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id TAA17152; Wed, 25 Nov 1998 19:50:31 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id TAA10894; Wed, 25 Nov 1998 19:50:31 +1030 (CST) Message-ID: <19981125195031.R67961@freebie.lemis.com> Date: Wed, 25 Nov 1998 19:50:31 +1030 From: Greg Lehey To: npe@bfc.dk, freebsd-current@FreeBSD.ORG Subject: Re: Porting driver from 2.2.x to 3.0-x References: <412566C7.002B3390.00@bfc.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <412566C7.002B3390.00@bfc.dk>; from npe@bfc.dk on Wed, Nov 25, 1998 at 08:56:01AM +0100 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 Wednesday, 25 November 1998 at 8:56:01 +0100, npe@bfc.dk wrote: > I'm currently trying to port the Compaq SmartRaid driver to 3.0 and is > almost done (with a limited version!) but my problem is that the > buf->b_un.??? does not exist in 3.0... Is the buf structs totally rewritten > or is it just a matter of names ?? Do a diff: it shows - struct { - caddr_t b_addr; /* Memory, superblocks, indirect etc. */ - } b_un; + caddr_t b_data; /* Memory, superblocks, indirect etc. */ In other words, b_data is your friend. Previously it was defined like this: -/* Device driver compatibility definitions. */ -#define b_data b_un.b_addr /* b_un.b_addr is not changeable. */ Can you send me more details of the driver (offline if necessary)? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 01:24:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14052 for freebsd-current-outgoing; Wed, 25 Nov 1998 01:24:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14044 for ; Wed, 25 Nov 1998 01:24:53 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id KAA28816; Wed, 25 Nov 1998 10:28:25 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Wed, 25 Nov 1998 10:28:24 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Christopher Hall cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <199811250640.OAA01720@hsw.generalresources.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Nov 1998, Christopher Hall wrote: > > In message <199811240210.SAA01652@dingo.cdrom.com>, Mike Smith writes: > >... > >> What should rootdev be set to when booting da0s1a with one IDE drive? > > > >Ignore $rootdev and instead set $num_ide_disks to 1. > > > > That works, thanks. > > Another question: Is there any way to boot DOS from /boot/loader? > Perhaps using some Forth code? Let me add yet another question to this: is there any way to boot FreeBSD from DOS partition, using /boot/loader? (I suspect it's not possible in both cases, though...) Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 01:42:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15252 for freebsd-current-outgoing; Wed, 25 Nov 1998 01:42:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15247 for ; Wed, 25 Nov 1998 01:42:46 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA09736; Wed, 25 Nov 1998 09:23:09 GMT Date: Wed, 25 Nov 1998 09:23:08 +0000 (GMT) From: Doug Rabson To: Mike Smith cc: "Norman C. Rice" , Bruce Evans , mjacob@feral.com, current@FreeBSD.ORG Subject: Re: Location for driver includes (was Re: Breakage in -current for theALPHA) In-Reply-To: <199811250207.SAA02557@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Nov 1998, Mike Smith wrote: > > Is it worth sorting includes based on the type of bus which the hardware > > is attached to? Something like: > > > > sys/dev/include non-bus-specific includes > > sys/dev/include/isa isa bus includes > > sys/dev/include/pci pci bus includes > > ... > > I don't think so; there's always the case where one device with several > different bus interfaces but a consistent user-space presentation will > spanner the works. > > IMHO, device-driver headers fall into two categories: > > - headers consumed only by the driver > These should live with the driver source files. > > - headers consumed by users-space driver users > These should be installed in a single location. They might want to > live with the driver source files as well, although this may > complicate the install process slightly. > > There should be a clear logical division between the two types of > files, even if they're kept together. > > I don't see any actual virtue in separating the user-consumed headers > from the driver source other than to make the install process easier. Apart from the install issues, I'm not too worried about where the external interface headers live in the source tree. The place where they are installed to needs to be agreed though. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 01:52:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16052 for freebsd-current-outgoing; Wed, 25 Nov 1998 01:52:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16046 for ; Wed, 25 Nov 1998 01:52:40 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id UAA11512; Wed, 25 Nov 1998 20:57:01 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199811250957.UAA11512@cimlogic.com.au> Subject: Re: Location for driver includes (was Re: Breakage in -current for theALPHA) In-Reply-To: from Doug Rabson at "Nov 25, 98 09:23:08 am" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 25 Nov 1998 20:57:00 +1100 (EST) Cc: mike@smith.net.au, nrice@emu.sourcee.com, bde@zeta.org.au, mjacob@feral.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > Apart from the install issues, I'm not too worried about where the > external interface headers live in the source tree. The place where they > are installed to needs to be agreed though. Does the installed location below /usr/include need to match the source location below /sys, though? This seems to be assumed by a lot of existing code. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 02:08:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17148 for freebsd-current-outgoing; Wed, 25 Nov 1998 02:08:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hsw.generalresources.com ([203.79.17.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17133 for ; Wed, 25 Nov 1998 02:08:07 -0800 (PST) (envelope-from hsw@email.generalresources.com) Received: from hsw.generalresources.com (localhost.generalresources.com [127.0.0.1]) by hsw.generalresources.com (8.9.1/8.9.1) with ESMTP id SAA03218; Wed, 25 Nov 1998 18:01:48 +0800 (CST) (envelope-from hsw@hsw.generalresources.com) Message-Id: <199811251001.SAA03218@hsw.generalresources.com> To: Andrzej Bialecki cc: Christopher Hall , freebsd-current@FreeBSD.ORG From: Christopher Hall Reply-to: Christopher Hall From: Christopher Hall Reply-to: Christopher Hall Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Message of "Wed, 25 Nov 1998 10:28:24 +0100." X-Operating-System: FreeBSD 3.0 X-Mailer: exmh 2.0 Date: Wed, 25 Nov 1998 18:01:48 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , And rzej Bialecki writes: >On Wed, 25 Nov 1998, Christopher Hall wrote: > >> >> In message <199811240210.SAA01652@dingo.cdrom.com>, Mike Smith writes: >> >... >> >> What should rootdev be set to when booting da0s1a with one IDE drive? >> > >> >Ignore $rootdev and instead set $num_ide_disks to 1. >> > >> >> That works, thanks. >> >> Another question: Is there any way to boot DOS from /boot/loader? >> Perhaps using some Forth code? > >Let me add yet another question to this: is there any way to boot FreeBSD >from DOS partition, using /boot/loader? > >(I suspect it's not possible in both cases, though...) > >Andrzej Bialecki on the 1998/Nov 3.0 CDROM there is an install.bat that says fbsdboot.exe -D kernel I wonder if this can be used? I will try it and see. > >-------------------- ++-------++ ------------------------------------- > ||PicoBSD|| FreeBSD in your pocket? Go and see: > Research & Academic |+-------+| "Small & Embedded FreeBSD" > Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ >-------------------- ~-+==---+-+ ------------------------------------- > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > --- Christopher Hall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 02:49:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20704 for freebsd-current-outgoing; Wed, 25 Nov 1998 02:49:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-12-dbn.dial-up.net [196.34.155.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20695 for ; Wed, 25 Nov 1998 02:49:43 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id MAA15178; Wed, 25 Nov 1998 12:47:07 +0200 (SAT) From: Robert Nordier Message-Id: <199811251047.MAA15178@ceia.nordier.com> Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <199811250640.OAA01720@hsw.generalresources.com> from Christopher Hall at "Nov 25, 98 02:40:26 pm" To: hsw@acm.org Date: Wed, 25 Nov 1998 12:47:02 +0200 (SAT) Cc: mike@smith.net.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Hall wrote: > Another question: Is there any way to boot DOS from /boot/loader? > Perhaps using some Forth code? I'm curious why you should want to do this (ie. rather than use a partition manager such as boot0/booteasy or some free or commercial alternative). There's currently no way, though. The boot/loader, with Forth itself, runs in userland (i386 protected mode ring 3). So you'd have to add a BTX syscall, at least, in addition to the Forth code. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 02:50:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20839 for freebsd-current-outgoing; Wed, 25 Nov 1998 02:50:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20815 for ; Wed, 25 Nov 1998 02:50:03 -0800 (PST) (envelope-from root@zappa.demon.nl) Received: (from root@localhost) by zappa.demon.nl (8.9.1/8.8.8) id LAA03259; Wed, 25 Nov 1998 11:51:03 +0100 (CET) (envelope-from root) Message-ID: <19981125115103.A3247@zappa.demon.nl> Date: Wed, 25 Nov 1998 11:51:03 +0100 From: Ron Klinkien To: ulf@Alameda.net, freebsd-current@FreeBSD.ORG Subject: Re: Adaptec SCSI messages References: <19981114144915.A244@zappa.demon.nl> <19981117112118.A252@zappa.demon.nl> <19981124011512.B11237@keltia.freenix.fr> <19981124103532.B613@zappa.demon.nl> <19981124083700.B12951@Alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981124083700.B12951@Alameda.net>; from Ulf Zimmermann on Tue, Nov 24, 1998 at 08:37:00AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 24, 1998 at 08:37:00AM -0800, Ulf Zimmermann wrote: > On Tue, Nov 24, 1998 at 10:35:32AM +0100, Ron Klinkien wrote: > > > > I guess you are right, but i wonder why they have invented Ultra 2 disks > > then. Since my disk performed in Single Ended mode exactly the same as > > in ULTRA2-LVD mode. > > > > They invented for two reasons: > > 1.) You can put more drives onto one bus, before running into bus limits > (As before said) > 2.) LVD = Low Voltage Differential = longer cable lengths possible again. Aha, ok, so its not only a faster bus. That make sense. Thanks. > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- --- "You could jam in Joe's garage..." -FZ Ron Klinkien System Engineer ron@zappa.demon.nl http://www.zappa.demon.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 03:09:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22454 for freebsd-current-outgoing; Wed, 25 Nov 1998 03:09:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-22-dbn.dial-up.net [196.34.155.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22449 for ; Wed, 25 Nov 1998 03:09:11 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA15237; Wed, 25 Nov 1998 13:02:55 +0200 (SAT) From: Robert Nordier Message-Id: <199811251102.NAA15237@ceia.nordier.com> Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <199811251001.SAA03218@hsw.generalresources.com> from Christopher Hall at "Nov 25, 98 06:01:48 pm" To: hsw@email.generalresources.com, hsw@acm.org Date: Wed, 25 Nov 1998 13:02:48 +0200 (SAT) Cc: abial@nask.pl, hsw@acm.org, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Hall wrote: > > In message , And > rzej Bialecki writes: > >Let me add yet another question to this: is there any way to boot FreeBSD > >from DOS partition, using /boot/loader? > > > >(I suspect it's not possible in both cases, though...) > > > >Andrzej Bialecki > > on the 1998/Nov 3.0 CDROM there is an install.bat that says > fbsdboot.exe -D kernel > I wonder if this can be used? I will try it and see. The fbsdboot.exe program runs in a DOS environment. You can use it to boot FreeBSD from DOS itself (though it works best when DOS is not running in V86 mode; and often doesn't work at all). You certainly can boot a FreeBSD kernel off a FAT/VFAT/FAT32 file system from /boot/loader. Currently, however, the kernel tends to get confused because it thinks it was booted from a UFS partition. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 03:23:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23708 for freebsd-current-outgoing; Wed, 25 Nov 1998 03:23:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA23703 for ; Wed, 25 Nov 1998 03:23:18 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id GAA29928; Wed, 25 Nov 1998 06:23:12 -0500 (EST) Date: Wed, 25 Nov 1998 06:23:12 -0500 (EST) Message-Id: <199811251123.GAA29928@highwind.com> From: HighWind Software Information To: info@highwind.com CC: current@FreeBSD.ORG In-reply-to: <199811250725.CAA27686@highwind.com> (message from HighWind Software Information on Wed, 25 Nov 1998 02:25:34 -0500 (EST)) Subject: Re: close() can hang! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Responding to myself... --- A libc_r linked program starts up, binds a TCP port, dup2()'s the socket to STDIN and execv()'s another libc_r linked program. The new libc_r linked program starts a thread that calls "accept()" on STDIN. Once that happens. If the new program calls "close()" STDIN, it hangs! All fd's are blocking fd's at the application level. --- It actually simply has to do with calling "close()" on an fd that another thread is "accept()"'ing on. It appears that FreeBSD doesn't like it when you to do that. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 03:56:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25326 for freebsd-current-outgoing; Wed, 25 Nov 1998 03:56:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA25321 for ; Wed, 25 Nov 1998 03:56:13 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id DAA50494; Wed, 25 Nov 1998 03:56:21 -0800 (PST) To: Robert Nordier cc: hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Sat, 25 Nov 1998 13:02:48 +0200." <199811251102.NAA15237@ceia.nordier.com> Date: Wed, 25 Nov 1998 03:56:20 -0800 Message-ID: <50490.911994980@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The fbsdboot.exe program runs in a DOS environment. You can use it > to boot FreeBSD from DOS itself (though it works best when DOS is > not running in V86 mode; and often doesn't work at all). Indeed. These days, most people just want an icon on their Win98 desktops they can click to boot into FreeBSD and Windows just doesn't make provisions for that kinda thing. :-) I think it's probably a bit of functionality which is on its way out and people are going to start having to rely increasingly on boot managers. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 04:11:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28761 for freebsd-current-outgoing; Wed, 25 Nov 1998 04:11:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA28753 for ; Wed, 25 Nov 1998 04:11:15 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KGMBRAQJ; Wed, 25 Nov 98 12:11:10 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981125131056.00973c10@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 25 Nov 1998 13:10:56 +0100 To: "Jordan K. Hubbard" , Robert Nordier From: Marius Bendiksen Subject: Re: /boot/loader what to set rootdev to? Cc: hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG In-Reply-To: <50490.911994980@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Indeed. These days, most people just want an icon on their Win98 >desktops they can click to boot into FreeBSD and Windows just doesn't >make provisions for that kinda thing. :-) I think it's probably a bit I think that should be fairly simple to do. After all, IIRC, it has support for boot-out to DOS to run various games. One could probably use that feature. >of functionality which is on its way out and people are going to start >having to rely increasingly on boot managers. Actually, speaking of win98 icons, the idea of using the umsdosfs idea from linux, or using OS/2 Extended Attribute files, to extend FAT to support the various freebsd-isms, and implementing this as a root filesystem might be a good thing. That would make it easier for a lot of people to "check it out" and such. Is this purely catering to the lusers which need win98 to autostart their CDs, or ...? --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 04:23:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29469 for freebsd-current-outgoing; Wed, 25 Nov 1998 04:23:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29461 for ; Wed, 25 Nov 1998 04:23:01 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id OAA26393; Wed, 25 Nov 1998 14:22:49 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id OAA39153; Wed, 25 Nov 1998 14:22:50 +0200 (EET) (envelope-from vallo) Message-ID: <19981125142249.B38959@matti.ee> Date: Wed, 25 Nov 1998 14:22:49 +0200 From: Vallo Kallaste To: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: CODA on FreeBSD-CURRENT Reply-To: vallo@matti.ee References: <4.1.19981123122653.00abfe40@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <4.1.19981123122653.00abfe40@206.25.93.69>; from Forrest Aldrich on Mon, Nov 23, 1998 at 12:28:16PM -0500 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forrest Aldrich wrote: > Wondered about anyone's experience with CODA on FreeBSD-CURRENT. > I see that vinum and some other stuff is included in the source tree, but want > to find out more about people's experience (good and bad) with these. Are > they stable, etc. I have tried CODA on current-elf machines. One acts as server and one as a client :-) , but my client machine crash everytime I run cvsup on /coda mounted /usr/src. As the cvsup crashes client machine everytime, I mark coda as unstable for me and don't spend any more time, althought it seems very interesting and suitable for our needs. Maybe I should try an aout version instead, because it's better supported and tested ? Anyone knowledgeable ? 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 Nov 25 04:29:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29947 for freebsd-current-outgoing; Wed, 25 Nov 1998 04:29:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29942 for ; Wed, 25 Nov 1998 04:29:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id EAA50637; Wed, 25 Nov 1998 04:29:26 -0800 (PST) To: Marius Bendiksen cc: Robert Nordier , hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Wed, 25 Nov 1998 13:10:56 +0100." <3.0.5.32.19981125131056.00973c10@mail.scancall.no> Date: Wed, 25 Nov 1998 04:29:26 -0800 Message-ID: <50633.911996966@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think that should be fairly simple to do. After all, IIRC, it has support > for boot-out to DOS to run various games. One could probably use that feature Oh yeah? How about telling us how. :-) > Actually, speaking of win98 icons, the idea of using the umsdosfs idea from > linux, or using OS/2 Extended Attribute files, to extend FAT to support the I'm still waiting for a umsdos implementation of some sort. After 3 years, I'm not waiting too hard. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 04:44:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01149 for freebsd-current-outgoing; Wed, 25 Nov 1998 04:44:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA01143 for ; Wed, 25 Nov 1998 04:44:30 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KGMJJZWJ; Wed, 25 Nov 98 12:44:21 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981125134406.0092f440@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 25 Nov 1998 13:44:06 +0100 To: "Jordan K. Hubbard" From: Marius Bendiksen Subject: Re: /boot/loader what to set rootdev to? Cc: Robert Nordier , hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG In-Reply-To: <50633.911996966@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Oh yeah? How about telling us how. :-) Ever heard of .pif files? Go check out how Full Throttle works, for example. >I'm still waiting for a umsdos implementation of some sort. After 3 >years, I'm not waiting too hard. :) Actually, the OS/2 Extended Attributes would probably be better... --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 04:57:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01829 for freebsd-current-outgoing; Wed, 25 Nov 1998 04:57:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01824 for ; Wed, 25 Nov 1998 04:57:49 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id EAA50757; Wed, 25 Nov 1998 04:57:39 -0800 (PST) To: Marius Bendiksen cc: Robert Nordier , hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Wed, 25 Nov 1998 13:44:06 +0100." <3.0.5.32.19981125134406.0092f440@mail.scancall.no> Date: Wed, 25 Nov 1998 04:57:35 -0800 Message-ID: <50753.911998655@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Oh yeah? How about telling us how. :-) > > Ever heard of .pif files? Go check out how Full Throttle works, for example. Ummm. Rebooting into DOS is *not* the same problem as booting into FreeBSD, though you seem to be under the mistaken impression that it is. If you don't believe me, just try constructing a PIF file for fbsdboot.exe and launch the procedure from your desktop. You will not shut down gracefully to DOS and be presented with a freebsd login prompt a few minutes later, as you would hope and expect. The kinds of things you need to do in order to properly shut down Windows and launch the FreeBSD kernel are simply different. > Actually, the OS/2 Extended Attributes would probably be better... Seeing as how nobody's doing the work in either case, it seems a rather moot point, don't you think? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 05:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02237 for freebsd-current-outgoing; Wed, 25 Nov 1998 05:01:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-59-dbn.dial-up.net [196.34.155.123]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02217 for ; Wed, 25 Nov 1998 05:00:53 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id OAA16516; Wed, 25 Nov 1998 14:55:32 +0200 (SAT) From: Robert Nordier Message-Id: <199811251255.OAA16516@ceia.nordier.com> Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <50633.911996966@zippy.cdrom.com> from "Jordan K. Hubbard" at "Nov 25, 98 04:29:26 am" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Wed, 25 Nov 1998 14:55:27 +0200 (SAT) Cc: Marius.Bendiksen@scancall.no, rnordier@nordier.com, hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > I think that should be fairly simple to do. After all, IIRC, it has support > > for boot-out to DOS to run various games. One could probably use that feature > > Oh yeah? How about telling us how. :-) > > > Actually, speaking of win98 icons, the idea of using the umsdosfs idea from > > linux, or using OS/2 Extended Attribute files, to extend FAT to support the > > I'm still waiting for a umsdos implementation of some sort. After 3 > years, I'm not waiting too hard. :) Mike and I actually discussed both these topics at some length off the lists some months back, and decided on workable solutions. The preferred boot-from-windows solution entails doing a cold boot out of Windows and a partition manager modification (one reason for bringing boot0 into the tree) to allow the FreeBSD slice to be selected transparently. The umsdos solution was generalized to a file system layer approach which could accommodate a FreeBSD slice on any (not necessarily MS-DOS) file system which supports 255 character filenames. As with most things, the issues aren't really technical: the people doing the boot work just don't want this stuff badly enough to spend time making it happen (eg. I don't even have MS-DOS or Windows installed these days.) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 05:07:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02561 for freebsd-current-outgoing; Wed, 25 Nov 1998 05:07:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02555 for ; Wed, 25 Nov 1998 05:07:08 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id FAA50840; Wed, 25 Nov 1998 05:06:58 -0800 (PST) To: Robert Nordier cc: Marius.Bendiksen@scancall.no, hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Sat, 25 Nov 1998 14:55:27 +0200." <199811251255.OAA16516@ceia.nordier.com> Date: Wed, 25 Nov 1998 05:06:57 -0800 Message-ID: <50832.911999217@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The umsdos solution was generalized to a file system layer approach > which could accommodate a FreeBSD slice on any (not necessarily > MS-DOS) file system which supports 255 character filenames. > > As with most things, the issues aren't really technical: the people > doing the boot work just don't want this stuff badly enough to > spend time making it happen (eg. I don't even have MS-DOS or Windows > installed these days.) Well, the only residual interest I have in the problem is for FreeBSD demo systems, where you want to hand someone an 80MB zip file (ala Slackware's "zipslack") which they unpack into C:\FREEBSD and then run something which creates a suitable boot disk for it (unless the boot-from-Windows issues can be fully worked out) and lets them try it out without sacrificing more space. If they can mount /usr/X11R6 from CD or something after that, all the better for your typical kiosk demo. Yes, it would be sort of useful. Useful enough to pay for, I think. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 05:08:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02707 for freebsd-current-outgoing; Wed, 25 Nov 1998 05:08:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02696 for ; Wed, 25 Nov 1998 05:08:14 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.1/8.9.1) with ESMTP id IAA15349; Wed, 25 Nov 1998 08:00:22 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 25 Nov 1998 08:00:22 -0500 (EST) From: "Alok K. Dhir" To: David Greenman cc: Steve Kargl , grog@lemis.com, romanp@wuppy.rcs.ru, kpielorz@tdx.co.uk, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <1BB089A92E313CAF852566C7000E1164.000C3319852566C7@worldbank.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 Mine is 1.74... On Tue, 24 Nov 1998, David Greenman wrote: > > > >According to David Greenman: > >> > >> Guys, would you please look at the file sys/kern/vfs_cluster.c and > verify > >> that you have rev 1.74? > >> > > > >rm -rf /usr/sys > >cvsup at 981124.1614 pst > > That's not what I asked you to do. I asked for you to look at the rev of > the vfs_cluster.c file. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S11-151, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 05:13:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03046 for freebsd-current-outgoing; Wed, 25 Nov 1998 05:13:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA03040 for ; Wed, 25 Nov 1998 05:13:05 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.1/8.9.1) with ESMTP id HAA15328; Wed, 25 Nov 1998 07:59:41 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 25 Nov 1998 07:59:41 -0500 (EST) From: "Alok K. Dhir" To: Steve Kargl cc: dg@root.com, grog@lemis.com, romanp@wuppy.rcs.ru, kpielorz@tdx.co.uk, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <74A981D02E8D95E0852566C7000C14BE.000A4B1E852566C7@worldbank.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 I'm seeing the same thing also on a kernel as of 11/24. I set "sysctl -w vfs.ffs.doreallocblks=0" and so far its stable. On Tue, 24 Nov 1998, Steve Kargl wrote: > > According to David Greenman: > > > > Guys, would you please look at the file sys/kern/vfs_cluster.c and > verify > > that you have rev 1.74? > > > > rm -rf /usr/sys > cvsup at 981124.1614 pst > > It crashes. I have an ELF kernel with debugging symbols. > I can not get a dump. If I issue 'panic' at the db> prompt > the system locks up tight. No keyboard, no disk activity, > nothing. All I have is a stack trace: > > dev=0x20404, bno = 34, bsize = 8192, size = 8192, fs = /var > panic: ffs_blkfree: bad size > mp_lock = 00000001; cpuid = 0; lapic.id = 01000000 > Debugger("panic") > Stopped at _Debugger+0x35: movb $0, _in_Debugger.98 > db> trace > _Debugger() at _Debugger+0x35 > _panic() at _panic+0x9f > _ffs_blkfree() at _ffs_blkfree+0xc2 > _ffs_reallocblks() at _ffs_reallocblks+0x420 > _cluster_write() at _cluster_write+0x15f > _ffs_write() at _ffs_write+0x56f > _vn_write() at _vn_write+0xef > _write() at _write+0xba > _syscall() at _syscall+0x187 > _Xint0x80_syscall() at _Xint0x80_syscall+0x4c > > If someone can clue me in on getting a crash dump, I'll > give Kirk access to my machines to debug this. I have > dumpdev=/dev/da1s1b in my rc.conf, and da1s1b is nearly > 700MB in size. > > -- > Steve > > finger kargl@troutmask.apl.washington.edu > http://troutmask.apl.washington.edu/~clesceri/kargl.html > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S11-151, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 05:24:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03643 for freebsd-current-outgoing; Wed, 25 Nov 1998 05:24:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freesbee.t.dk (freesbee.t.dk [193.163.159.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA03638 for ; Wed, 25 Nov 1998 05:24:57 -0800 (PST) (envelope-from jesper@freesbee.t.dk) Received: (qmail 1402 invoked by uid 1001); 25 Nov 1998 13:24:48 -0000 Date: Wed, 25 Nov 1998 14:24:48 +0100 From: Jesper Skriver To: "Alok K. Dhir" Cc: Steve Kargl , dg@root.com, grog@lemis.com, romanp@wuppy.rcs.ru, kpielorz@tdx.co.uk, current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity Message-ID: <19981125142448.A1397@skriver.dk> References: <74A981D02E8D95E0852566C7000C14BE.000A4B1E852566C7@worldbank.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: ; from Alok K. Dhir on Wed, Nov 25, 1998 at 07:59:41AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Didn't help here ... crashed after running X for 20 seconds (ran ssh in a xterm) ... Kernel as of 11/25 10:26:50 CET /Jesper On Wed, Nov 25, 1998 at 07:59:41AM -0500, Alok K. Dhir wrote: > > I'm seeing the same thing also on a kernel as of 11/24. I set "sysctl -w > vfs.ffs.doreallocblks=0" and so far its stable. > > -------------------------------------------------------------------- \||/_ > Alok K. Dhir Phone: +1.202.473.2446 oo \ > S11-151, ISGMC Email: adhir@worldbank.org L_ > The World Bank Group Washington, DC \/ > ------------------------------------------------------------------------| > "Unix _is_ user friendly - it just chooses friends selectively..." /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 05:35:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04170 for freebsd-current-outgoing; Wed, 25 Nov 1998 05:35:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04162 for ; Wed, 25 Nov 1998 05:35:09 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id FAA04515; Wed, 25 Nov 1998 05:36:16 -0800 (PST) Message-Id: <199811251336.FAA04515@root.com> To: Jesper Skriver cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Wed, 25 Nov 1998 14:24:48 +0100." <19981125142448.A1397@skriver.dk> From: David Greenman Reply-To: dg@root.com Date: Wed, 25 Nov 1998 05:36:16 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Didn't help here ... crashed after running X for 20 seconds (ran ssh in >a xterm) ... I think the problem you are seeing is entirely different than the one we are working on resolving at the moment. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 05:37:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04338 for freebsd-current-outgoing; Wed, 25 Nov 1998 05:37:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04329 for ; Wed, 25 Nov 1998 05:37:27 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id FAA04533; Wed, 25 Nov 1998 05:38:43 -0800 (PST) Message-Id: <199811251338.FAA04533@root.com> To: Jesper Skriver cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Wed, 25 Nov 1998 09:46:41 +0100." <19981125094641.A28029@skriver.dk> From: David Greenman Reply-To: dg@root.com Date: Wed, 25 Nov 1998 05:38:43 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Tue, Nov 24, 1998 at 05:18:16PM -0800, David Greenman wrote: > >> Guys, would you please look at the file sys/kern/vfs_cluster.c and verify >> that you have rev 1.74? > >I have rev 1.74. > >I installed a 3.0-RELEASE monday (11/23), and ran cvsup to get it >updated, I upgraded the kernel, and made a "make buildworld && make >installworld", after that the box crashes when running X and starting a >few programs, or when running a make buildworld .... > >I happend before I enabled softupdates, and it has happend afterwards. > >On one time I got the output from the panic. > >fatal trap 12: page fault while in kernel mode >fault virtual address = 0x0 >fault code = supervisor read page not present >instruction pointer = 0x8 : 0xf01d6583 >stack pointer = 0x10 : 0xf4345afc >frame pointer = 0x10 : 0xf4345b04 >code segment = base 0x0 limit 0xfffff type 0x1b > = DPL0 pres1 def 321 gran 1 >processor eflags = interrupt enabled, resume IOPL = 0 >current process = 290 (as) >interrrupt mask = net tty bio cam >trap number = 12 >panic: page fault This is unrelated to the filesystem panic that we've been talking about. I saw your followup about the fault occuring in zalloci(). A traceback would be helpfull in isolating this problem. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 05:39:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04468 for freebsd-current-outgoing; Wed, 25 Nov 1998 05:39:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tabor.abirnet.co.il (tabor.abirnet.co.il [212.25.82.176]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA04325 for ; Wed, 25 Nov 1998 05:37:06 -0800 (PST) (envelope-from cigan@abirnet.co.il) Received: (qmail 1846 invoked by uid 0); 25 Nov 1998 13:43:52 -0000 Received: from unknown (HELO wizard.abirnet.co.il) (unknown) by unknown with SMTP; 25 Nov 1998 13:43:52 -0000 X-BlackMail: cigan@wizard.abirnet.co.il, wizard.abirnet.co.il, , 212.25.82.10 X-Authenticated-Timestamp: 15:43:52(IST) on November 25, 1998 Date: Wed, 25 Nov 1998 15:36:53 +0200 (IST) From: CIGAN To: FreeBSD-current@FreeBSD.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 help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 06:14:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07662 for freebsd-current-outgoing; Wed, 25 Nov 1998 06:14:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-14-dbn.dial-up.net [196.34.155.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07655 for ; Wed, 25 Nov 1998 06:14:39 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id QAA17263; Wed, 25 Nov 1998 16:13:31 +0200 (SAT) From: Robert Nordier Message-Id: <199811251413.QAA17263@ceia.nordier.com> Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <50832.911999217@zippy.cdrom.com> from "Jordan K. Hubbard" at "Nov 25, 98 05:06:57 am" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Wed, 25 Nov 1998 16:13:27 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > The umsdos solution was generalized to a file system layer approach > > which could accommodate a FreeBSD slice on any (not necessarily > > MS-DOS) file system which supports 255 character filenames. > > > > As with most things, the issues aren't really technical: the people > > doing the boot work just don't want this stuff badly enough to > > spend time making it happen (eg. I don't even have MS-DOS or Windows > > installed these days.) > > Well, the only residual interest I have in the problem is for FreeBSD > demo systems, where you want to hand someone an 80MB zip file (ala > Slackware's "zipslack") which they unpack into C:\FREEBSD and then run > something which creates a suitable boot disk for it (unless the > boot-from-Windows issues can be fully worked out) and lets them try it > out without sacrificing more space. If they can mount /usr/X11R6 from > CD or something after that, all the better for your typical kiosk > demo. > > Yes, it would be sort of useful. Useful enough to pay for, I > think. :-) Well, it may be worth discussing that. I particularly like the generalized approach as it adds a fundamental capability that could equally apply to any other file system (NT, SYSV, ... ) that we might acquire code for at some stage. I think a cold boot from within Windows could be fairly painless. The cold boot is needed if we're going to expect the kernel vm86 stuff to be reliable. It's reasonably easy to even boot straight out of Windows, but it completely destroys the BIOS interrupt chain when the page tables change and the Windows interrupt handlers are vaporized. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 06:15:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07875 for freebsd-current-outgoing; Wed, 25 Nov 1998 06:15:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shire.domestic.de (kuebart.stuttgart.netsurf.de [194.233.216.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07859; Wed, 25 Nov 1998 06:15:33 -0800 (PST) (envelope-from joki@kuebart.stuttgart.netsurf.de) Received: from yacht.domestic.de (yacht.domestic.de [192.168.1.4]) by shire.domestic.de (8.8.8/8.8.7) with ESMTP id PAA25819; Wed, 25 Nov 1998 15:15:49 +0100 (CET) (envelope-from joki@shire.domestic.de) From: Joachim Kuebart Received: (from joki@localhost) by yacht.domestic.de (8.9.1/8.8.7) id PAA00634; Wed, 25 Nov 1998 15:16:24 +0100 (CET) (envelope-from joki@shire.domestic.de) Message-Id: <199811251416.PAA00634@yacht.domestic.de> Subject: Re: ES1370 driver for FreeBSD In-Reply-To: from "Andrew A. Bely" at "Nov 24, 98 10:17:59 pm" To: taurus@cave.garant.ru (Andrew A. Bely) Date: Wed, 25 Nov 1998 15:16:24 +0100 (CET) Cc: freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, my ENSONIQ AudioPCI (Es1370, AK4531) driver is now available at: ftp://ftp.lf.net/pub/users/Joachim.Kuebart/es1370/ The directory contains the .c and .h files that go into /sys/i386/isa/snd and a .diff file that also must be applied in that directory. The directory also contains the documentation of the card's two chips in PostScript and PDF format. Yesterday I tested xanim and found the sound to be crackling. I haven't discovered the reasons yet but I'm at it. cu Jo --------------------------------------------------------------------- Pray that there's intelligent life Joachim Kuebart Somewhere up in space Stuttgart, Germany 'Cause there's bugger all down here on earth. --- Monty Python To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 07:00:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12384 for freebsd-current-outgoing; Wed, 25 Nov 1998 07:00:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freesbee.t.dk (freesbee.t.dk [193.163.159.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA12259 for ; Wed, 25 Nov 1998 07:00:00 -0800 (PST) (envelope-from jesper@freesbee.t.dk) Received: (qmail 2612 invoked by uid 1001); 25 Nov 1998 14:59:53 -0000 Date: Wed, 25 Nov 1998 15:59:53 +0100 From: Jesper Skriver To: David Greenman Cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity Message-ID: <19981125155953.A2593@skriver.dk> References: <19981125094641.A28029@skriver.dk> <199811251338.FAA04533@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: <199811251338.FAA04533@root.com>; from David Greenman on Wed, Nov 25, 1998 at 05:38:43AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 25, 1998 at 05:38:43AM -0800, David Greenman wrote: > This is unrelated to the filesystem panic that we've been talking about. I > saw your followup about the fault occuring in zalloci(). A traceback would > be helpfull in isolating this problem. This is with a diffenrent kernel with support for DDB Fatal trap 12: page fault while in kernel mode fault virtual address = 0x67566f7c fault code = supervisor read, page not present instruction pointer = 0x8 :0xf0153798 stack pointer = 0x10 : 0xf42c2d34 frame pointer = 0x10 : 0xf42c2d34 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 = 264 (cpp) interrupt mask = bio kernel: type 12 trap, code=0 Stopped at _gbincore+0x20: cmpl %ecx,0x64(%eax) db> trace _gbincore(f42b3740,0,288e,11,f42c2eb8) at _gbincore+0x20 _getblk(f42b3740,0,2000,0,0) at _getblk+0x6d _cluster_read(f42b3740,288e,0,0,2000) at _cluster_read+0x8b _ffs_read(f42c2eec,f4205300,288e,f42c2f84,f42c2eec) at _ffs_read+0x3e9 _vn_read(f0a6ab80,f42c2f30,f09f9c80,f4205300,f0234de4) at _vn_read+0x121 _read(f4205300,f42c2f84,0,288e,8093000) at _read+0xb9 _syscall(27,27,8093000,288e,efbfd388) at _syscall+0x187 _Xint0x80_syscall() at _Xint0x80_syscall+0x2c db> /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 07:04:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12815 for freebsd-current-outgoing; Wed, 25 Nov 1998 07:04:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley-185-114.res.iastate.edu (friley-185-114.res.iastate.edu [129.186.185.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12810 for ; Wed, 25 Nov 1998 07:04:21 -0800 (PST) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Received: from friley-185-114.res.iastate.edu (loopback [127.0.0.1]) by friley-185-114.res.iastate.edu (8.9.1/8.9.1) with ESMTP id JAA10521; Wed, 25 Nov 1998 09:03:58 -0600 (CST) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Message-Id: <199811251503.JAA10521@friley-185-114.res.iastate.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier cc: hsw@acm.org, mike@smith.net.au, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Sat, 25 Nov 1998 12:47:02 +0200." <199811251047.MAA15178@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 09:03:57 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Christopher Hall wrote: > >> Another question: Is there any way to boot DOS from /boot/loader? >> Perhaps using some Forth code? > >I'm curious why you should want to do this (ie. rather than use a >partition manager such as boot0/booteasy or some free or commercial >alternative). Perhaps if you want to dual boot off of a serial console. Right now, I have to use lilo to boot my FreeBSD partition. It would be nice if it were possible to boot random partitions from FreeBSD as well. Chris >There's currently no way, though. The boot/loader, with Forth >itself, runs in userland (i386 protected mode ring 3). So you'd >have to add a BTX syscall, at least, in addition to the Forth code. > >-- >Robert Nordier > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 07:55:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16439 for freebsd-current-outgoing; Wed, 25 Nov 1998 07:55:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16434 for ; Wed, 25 Nov 1998 07:55:22 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1/8.9.1) with SMTP id KAA07070; Wed, 25 Nov 1998 10:52:17 -0500 (EST) Message-Id: <4.1.19981125102903.00ad3b10@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 25 Nov 1998 10:29:33 -0500 To: vallo@matti.ee, freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Re: CODA on FreeBSD-CURRENT In-Reply-To: <19981125142249.B38959@matti.ee> References: <4.1.19981123122653.00abfe40@206.25.93.69> <4.1.19981123122653.00abfe40@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Your crashing problem may very well not be related to CODA, but related to the "random crashing/rebooting" thread that's been going on. Forrest At 02:22 PM 11/25/98 +0200, Vallo Kallaste wrote: >Forrest Aldrich wrote: > >> Wondered about anyone's experience with CODA on FreeBSD-CURRENT. >> I see that vinum and some other stuff is included in the source tree, but >want >> to find out more about people's experience (good and bad) with these. Are >> they stable, etc. > >I have tried CODA on current-elf machines. One acts as server and >one as a client :-) , but my client machine crash everytime I run >cvsup on /coda mounted /usr/src. As the cvsup crashes client >machine everytime, I mark coda as unstable for me and don't spend >any more time, althought it seems very interesting and suitable for >our needs. Maybe I should try an aout version instead, because it's >better supported and tested ? Anyone knowledgeable ? > > >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 Nov 25 08:06:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17154 for freebsd-current-outgoing; Wed, 25 Nov 1998 08:06:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-29-dbn.dial-up.net [196.34.155.93]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17136 for ; Wed, 25 Nov 1998 08:06:31 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id SAA18008; Wed, 25 Nov 1998 18:04:03 +0200 (SAT) From: Robert Nordier Message-Id: <199811251604.SAA18008@ceia.nordier.com> Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <199811251503.JAA10521@friley-185-114.res.iastate.edu> from Chris Csanady at "Nov 25, 98 09:03:57 am" To: ccsanady@friley-185-114.res.iastate.edu (Chris Csanady) Date: Wed, 25 Nov 1998 18:04:00 +0200 (SAT) Cc: rnordier@nordier.com, hsw@acm.org, mike@smith.net.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Csanady wrote: > > >Christopher Hall wrote: > > > >> Another question: Is there any way to boot DOS from /boot/loader? > >> Perhaps using some Forth code? > > > >I'm curious why you should want to do this (ie. rather than use a > >partition manager such as boot0/booteasy or some free or commercial > >alternative). > > Perhaps if you want to dual boot off of a serial console. Right now, > I have to use lilo to boot my FreeBSD partition. It would be nice > if it were possible to boot random partitions from FreeBSD as well. Yes, that's true. Bear in mind that boot/loader just looks like a FreeBSD kernel to the boot blocks. So one solution might be a "boot/manager". This could be loaded by the boot blocks or by boot/loader, and could itself load either boot/loader or other boot blocks. With BTX and the current libstand, ficl, and other boot library code, the necessary tools now exist for producing various mutant boot applications on demand. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 08:13:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17555 for freebsd-current-outgoing; Wed, 25 Nov 1998 08:13:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17549 for ; Wed, 25 Nov 1998 08:13:29 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id IAA07245; Wed, 25 Nov 1998 08:13:20 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id IAA02426; Wed, 25 Nov 1998 08:13:20 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <86btlwxv7p.fsf@detlev.UUCP> Date: Wed, 25 Nov 1998 08:13:20 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Joel Ray Holveck Subject: Re: Elf linker question. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you follow up to this, let's drop it off the mailing list. It's getting pretty far off topic. On 25-Nov-98 Joel Ray Holveck wrote: >>> How are things like: >>> sighander_t mysig = libsig; >>> handled? >> Any time you take the address of a function, the linker actually fills >> in the address of a little stub routine. It's the same stub that >> gets called when you call an external function. The first time it is >> executed, the stub jumps to code in the dynamic linker that does the >> lazy binding to whatever function is being called. Then it rewires >> itself (an indirect jump is used) so that all future calls will go >> straight to the target function. > > Oh, so it doesn't snap the pointer in the code? It just leaves it > pointing to the stub? That's right. The whole point of PIC is that you don't relocate anything in the text (code) segment. That way, all the processes using a given shared library can share the exact same copy of the code. Once the lazy binding has already been done for a given function, the "stub" hardly deserves the name. It's nothing more than an indirect jump through a location that contains a pointer to the real function's entry point. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 08:23:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18347 for freebsd-current-outgoing; Wed, 25 Nov 1998 08:23:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (38-sweet.camalott.com [208.239.153.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18331 for ; Wed, 25 Nov 1998 08:23:32 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id KAA98404; Wed, 25 Nov 1998 10:21:51 -0600 (CST) (envelope-from joelh) To: "Jordan K. Hubbard" Cc: Marius Bendiksen , Robert Nordier , hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? References: <50753.911998655@zippy.cdrom.com> From: Joel Ray Holveck Date: 25 Nov 1998 10:21:49 -0600 In-Reply-To: "Jordan K. Hubbard"'s message of "Wed, 25 Nov 1998 04:57:35 -0800" Message-ID: <864srnyc82.fsf@detlev.UUCP> Lines: 22 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>Oh yeah? How about telling us how. :-) >> Ever heard of .pif files? Go check out how Full Throttle works, for example. > Ummm. Rebooting into DOS is *not* the same problem as booting into > FreeBSD, though you seem to be under the mistaken impression that it > is. If you don't believe me, just try constructing a PIF file for > fbsdboot.exe and launch the procedure from your desktop. You will not > shut down gracefully to DOS and be presented with a freebsd login > prompt a few minutes later, as you would hope and expect. The kinds > of things you need to do in order to properly shut down Windows and > launch the FreeBSD kernel are simply different. Jordan, we've been over this before. Did you ever actually *try* what the rest of the list said? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 08:24:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18444 for freebsd-current-outgoing; Wed, 25 Nov 1998 08:24:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from world.virtual-earth.de (world.virtual-earth.de [194.231.209.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18360; Wed, 25 Nov 1998 08:23:47 -0800 (PST) (envelope-from mathiasp@world.virtual-earth.de) Received: from world.virtual-earth.de (localhost.virtual-earth.de [127.0.0.1]) by world.virtual-earth.de (8.9.1/8.8.5) with ESMTP id RAA02710; Wed, 25 Nov 1998 17:20:18 +0100 (MET) Message-Id: <199811251620.RAA02710@world.virtual-earth.de> Date: Wed, 25 Nov 1998 17:20:16 +0100 (MET) From: Mathias Picker Subject: da2s1e device not configured error To: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a new UW-SCSI-disk I get Error mounting /dev/da2s1e on /disk1 : Device not configured after partinioning with the newest sysinstall. This is on fbsd current from the Nov 17 with sysinstall from today. The system sees the disk, it responds to camcontrol start/stop/inquiry, I can write to it with dd. disklabel da2 gives me "disklabel: ioctl DIOCGDINFO: Invalid argument" I really need HELP here, I need this disk. What exactly does "not configured" mean in the cam sense? Where can I look, what can I do? Thanks for any help, Mathias -- Mathias Picker Consultant Information Architecture Mathias.Picker@virtual-earth.de +49 172 / 89 19 381 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 08:37:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19787 for freebsd-current-outgoing; Wed, 25 Nov 1998 08:37:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19781 for ; Wed, 25 Nov 1998 08:37:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00611; Wed, 25 Nov 1998 08:34:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811251634.IAA00611@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Hall cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Wed, 25 Nov 1998 14:40:26 +0800." <199811250640.OAA01720@hsw.generalresources.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 08:34:47 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In message <199811240210.SAA01652@dingo.cdrom.com>, Mike Smith writes: > >... > >> What should rootdev be set to when booting da0s1a with one IDE drive? > > > >Ignore $rootdev and instead set $num_ide_disks to 1. > > > > That works, thanks. > > Another question: Is there any way to boot DOS from /boot/loader? > Perhaps using some Forth code? Not trivially. Install the boot0 module or booteasy, and use that. By the time the bootloader has been invoked, you're well down the road towards running FreeBSD. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 08:43:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20296 for freebsd-current-outgoing; Wed, 25 Nov 1998 08:43:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20290 for ; Wed, 25 Nov 1998 08:43:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00674; Wed, 25 Nov 1998 08:40:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811251640.IAA00674@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Christopher Hall , Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Wed, 25 Nov 1998 10:28:24 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 08:40:52 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Let me add yet another question to this: is there any way to boot FreeBSD > from DOS partition, using /boot/loader? It's not generally possible to boot FreeBSD once DOS has started; modern DOS versions corrupt the BIOS vectors in a fashion that makes it impossible to obtain system information. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 09:21:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22683 for freebsd-current-outgoing; Wed, 25 Nov 1998 09:21:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22678 for ; Wed, 25 Nov 1998 09:21:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA00911; Wed, 25 Nov 1998 09:17:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811251717.JAA00911@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joel Ray Holveck cc: "Jordan K. Hubbard" , Marius Bendiksen , Robert Nordier , hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "25 Nov 1998 10:21:49 CST." <864srnyc82.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 09:17:08 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>>Oh yeah? How about telling us how. :-) > >> Ever heard of .pif files? Go check out how Full Throttle works, for example. > > Ummm. Rebooting into DOS is *not* the same problem as booting into > > FreeBSD, though you seem to be under the mistaken impression that it > > is. If you don't believe me, just try constructing a PIF file for > > fbsdboot.exe and launch the procedure from your desktop. You will not > > shut down gracefully to DOS and be presented with a freebsd login > > prompt a few minutes later, as you would hope and expect. The kinds > > of things you need to do in order to properly shut down Windows and > > launch the FreeBSD kernel are simply different. > > Jordan, we've been over this before. Did you ever actually *try* what > the rest of the list said? Yes, we have been over this before. Would you care to explain how you plan to reinstate the vectors that the DOS7 kernel replaces so that vm86 BIOS calls from the FreeBSD kernel will work? Please understand that there are some really fundamental issues which absolutely preclude starting FreeBSD once DOS has been started. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 09:36:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23655 for freebsd-current-outgoing; Wed, 25 Nov 1998 09:36:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23649 for ; Wed, 25 Nov 1998 09:36:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA01096; Wed, 25 Nov 1998 09:34:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811251734.JAA01096@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: HighWind Software Information cc: current@FreeBSD.ORG Subject: Re: Resend In-reply-to: Your message of "Wed, 25 Nov 1998 03:44:33 EST." <199811250844.DAA27850@highwind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 09:34:33 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm trying to track a problem where a "write()" to a socket > sends the beginning of the data over and over. > > I'm looking at "sosend()" in uipc_socket.c, a comment says: > > > * Returns nonzero on error, timeout or signal; callers > > * must check for short counts if EINTR/ERESTART are returned. > > * Data and control buffers are freed on return. > > However, I don't see anywhere in the code where it returns > EINTR/ERESTART. That is, if this code mistakenly loops when it gets > interrupted or does a partial write(), it would result in the behavior > I am seeing. The sblock() macro can return this. > That is: > When asked to write a big buffer "1234", we are sometimes seeing > on the network connection: > "1121231234" > > > Any ideas? You'll also get this behaviour if the socket is nonblocking and you only make a partial write, but forget to update your buffer pointer/ count before calling write() again. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 09:41:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24009 for freebsd-current-outgoing; Wed, 25 Nov 1998 09:41:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rain.futuresouth.com (rain.futuresouth.com [198.79.79.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24000; Wed, 25 Nov 1998 09:41:46 -0800 (PST) (envelope-from stormy@rain.futuresouth.com) Received: (from stormy@localhost) by rain.futuresouth.com (8.9.1/8.9.1) id LAA04683; Wed, 25 Nov 1998 11:43:02 -0600 (CST) (envelope-from stormy) Message-ID: <19981125114301.A4677@futuresouth.com> Date: Wed, 25 Nov 1998 11:43:01 -0600 From: Stormy Henderson To: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: da2s1e device not configured error Mail-Followup-To: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG References: <199811251620.RAA02710@world.virtual-earth.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811251620.RAA02710@world.virtual-earth.de>; from Mathias Picker on Wed, Nov 25, 1998 at 05:20:16PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A happy camper (Mathias Picker, mathiasp@virtual-earth.de) once wrote... > Error mounting /dev/da2s1e on /disk1 : Device not configured > > after partinioning with the newest sysinstall. This is on fbsd current > from the Nov 17 with sysinstall from today. I assume you labeled it, too? Be happy... -- Stormy Henderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 09:55:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24980 for freebsd-current-outgoing; Wed, 25 Nov 1998 09:55:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24975 for ; Wed, 25 Nov 1998 09:55:44 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.7) with SMTP id RAA09213; Wed, 25 Nov 1998 17:54:22 GMT (envelope-from arg@arg1.demon.co.uk) Date: Wed, 25 Nov 1998 17:54:21 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: "Jordan K. Hubbard" cc: Robert Nordier , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <50753.911998655@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Nov 1998, Jordan K. Hubbard wrote: > > >Oh yeah? How about telling us how. :-) > > > > Ever heard of .pif files? Go check out how Full Throttle works, for example. > > Ummm. Rebooting into DOS is *not* the same problem as booting into > FreeBSD, though you seem to be under the mistaken impression that it > is. If you don't believe me, just try constructing a PIF file for > fbsdboot.exe and launch the procedure from your desktop. You will not > shut down gracefully to DOS and be presented with a freebsd login > prompt a few minutes later, as you would hope and expect. The kinds > of things you need to do in order to properly shut down Windows and > launch the FreeBSD kernel are simply different. Works fine for me - indeed it's the only way I had at the time of booting my laptop into FreeBSD as I put the root partition beyond cyl 1024. System is Win95-OSR2 / FreeBSD-2.2.various on a Libretto 50 with 1.6Gb harddrive. FBSDBOOT.EXE is configured to start in MS-DOS mode by clicking the appropriate box in the 'advanced program settings' dialog from the program tab of the alias properties. It isn't clear to me to what extent I am 'lucky' - but certainly in this particular configuration it is 100% reliable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 10:04:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25623 for freebsd-current-outgoing; Wed, 25 Nov 1998 10:04:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25617 for ; Wed, 25 Nov 1998 10:04:26 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id NAA02326; Wed, 25 Nov 1998 13:03:36 -0500 (EST) Date: Wed, 25 Nov 1998 13:03:36 -0500 (EST) Message-Id: <199811251803.NAA02326@highwind.com> From: HighWind Software Information To: mike@smith.net.au CC: current@FreeBSD.ORG In-reply-to: <199811251734.JAA01096@dingo.cdrom.com> (message from Mike Smith on Wed, 25 Nov 1998 09:34:33 -0800) Subject: Re: Resend Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike, > > I'm trying to track a problem where a "write()" to a socket > > sends the beginning of the data over and over. > > > > I'm looking at "sosend()" in uipc_socket.c, a comment says: > > > > > * Returns nonzero on error, timeout or signal; callers > > > * must check for short counts if EINTR/ERESTART are returned. > > > * Data and control buffers are freed on return. > > > > However, I don't see anywhere in the code where it returns > > EINTR/ERESTART. That is, if this code mistakenly loops when it gets > > interrupted or does a partial write(), it would result in the behavior > > I am seeing. > The sblock() macro can return this. Really??? #define sblock(sb, wf) ((sb)->sb_flags & SB_LOCK ? \ (((wf) == M_WAITOK) ? sb_lock(sb) : EWOULDBLOCK) : \ ((sb)->sb_flags |= SB_LOCK), 0) That doesn't look like it. Did I miss something? > You'll also get this behaviour if the socket is nonblocking and you > only make a partial write, but forget to update your buffer pointer/ > count before calling write() again. True. But, my reading of the libc_r write() code looks like it handles this perfectly. Maybe I missed something. On the outside, the descriptors are blocking, John Birrell's libc_r code loops and handles this correctly. I haven't been able to find any problems with that code. Maybe I missed something. It is in "lib/libc_r/uthread/uthread_write.c" -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 10:09:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25924 for freebsd-current-outgoing; Wed, 25 Nov 1998 10:09:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25919 for ; Wed, 25 Nov 1998 10:09:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA01262; Wed, 25 Nov 1998 10:06:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811251806.KAA01262@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gordon cc: "Jordan K. Hubbard" , Robert Nordier , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Wed, 25 Nov 1998 17:54:21 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 10:06:12 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It isn't clear to me to what extent I am 'lucky' - but certainly in this > particular configuration it is 100% reliable. Try booting a 3.0 kernel with 'options "VM86"' in the config. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 10:13:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26184 for freebsd-current-outgoing; Wed, 25 Nov 1998 10:13:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26178 for ; Wed, 25 Nov 1998 10:12:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA01308; Wed, 25 Nov 1998 10:10:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811251810.KAA01308@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: HighWind Software Information cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: Resend In-reply-to: Your message of "Wed, 25 Nov 1998 13:03:36 EST." <199811251803.NAA02326@highwind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 10:10:29 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike, > > > > I'm trying to track a problem where a "write()" to a socket > > > sends the beginning of the data over and over. > > > > > > I'm looking at "sosend()" in uipc_socket.c, a comment says: > > > > > > > * Returns nonzero on error, timeout or signal; callers > > > > * must check for short counts if EINTR/ERESTART are returned. > > > > * Data and control buffers are freed on return. > > > > > > However, I don't see anywhere in the code where it returns > > > EINTR/ERESTART. That is, if this code mistakenly loops when it gets > > > interrupted or does a partial write(), it would result in the behavior > > > I am seeing. > > > The sblock() macro can return this. > > Really??? > > #define sblock(sb, wf) ((sb)->sb_flags & SB_LOCK ? \ > (((wf) == M_WAITOK) ? sb_lock(sb) : EWOULDBLOCK) : \ > ((sb)->sb_flags |= SB_LOCK), 0) > > That doesn't look like it. Did I miss something? The implementation of sb_lock(): sb_lock(sb) register struct sockbuf *sb; { int error; while (sb->sb_flags & SB_LOCK) { sb->sb_flags |= SB_WANT; error = tsleep((caddr_t)&sb->sb_flags, (sb->sb_flags & SB_NOINTR) ? PSOCK : PSOCK|PCATCH, "sblock", 0); if (error) return (error); } sb->sb_flags |= SB_LOCK; return (0); } see tsleep(9) > > You'll also get this behaviour if the socket is nonblocking and you > > only make a partial write, but forget to update your buffer pointer/ > > count before calling write() again. > > True. But, my reading of the libc_r write() code looks like it handles > this perfectly. Maybe I missed something. On the outside, the descriptors > are blocking, John Birrell's libc_r code loops and handles this correctly. > > I haven't been able to find any problems with that code. Maybe I missed > something. It is in "lib/libc_r/uthread/uthread_write.c" It appears to do the correct thing in the nonblocking case; this points the finger at your application. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 10:18:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26583 for freebsd-current-outgoing; Wed, 25 Nov 1998 10:18:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.insolwwb.net (ns.insolwwb.net [206.31.149.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26572 for ; Wed, 25 Nov 1998 10:18:42 -0800 (PST) (envelope-from mgrommet@insolwwb.net) Received: from mikeg (work2.insolwwb.net [208.150.248.12]) by ns.insolwwb.net (8.8.8/8.8.5) with SMTP id MAA03818 for ; Wed, 25 Nov 1998 12:02:43 -0600 (CST) From: mike grommet Reply-To: To: Subject: So, how long until 3.0-Stable? Date: Wed, 25 Nov 1998 12:18:35 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wondering how long until the 3.0-stable path begins? Mike Grommet Unix Systems Adminstrator Internet Solutions, Inc. mgrommet@insolwwb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 10:27:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27088 for freebsd-current-outgoing; Wed, 25 Nov 1998 10:27:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ares.cs.Virginia.EDU (ares.cs.Virginia.EDU [128.143.137.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27079 for ; Wed, 25 Nov 1998 10:27:14 -0800 (PST) (envelope-from christin@cs.virginia.edu) Received: from cs.virginia.edu (koala.cs.Virginia.EDU [128.143.136.57]) by ares.cs.Virginia.EDU (8.8.5/8.8.5) with ESMTP id NAA18951 for ; Wed, 25 Nov 1998 13:26:46 -0500 (EST) Message-ID: <365C4BF1.1318F833@cs.virginia.edu> Date: Wed, 25 Nov 1998 13:26:57 -0500 From: Nicolas Christin Organization: University of Virginia X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: files.newconf in 3.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 trying to install a packet scheduler on 3.0. Initially, this stuff has been developed for 2.2.6, and to install it I would need to modify /usr/src/sys/conf/files.newconf. The problem is that this file is not present on 3.0. I'd like to know what is its equivalent. Thank you, -- Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 10:35:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27509 for freebsd-current-outgoing; Wed, 25 Nov 1998 10:35:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA27503 for ; Wed, 25 Nov 1998 10:35:49 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KGPSWHIJ; Wed, 25 Nov 98 18:35:43 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981125193527.00992e70@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 25 Nov 1998 19:35:27 +0100 To: "Jordan K. Hubbard" From: Marius Bendiksen Subject: Re: /boot/loader what to set rootdev to? Cc: Robert Nordier , hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG In-Reply-To: <50753.911998655@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Seeing as how nobody's doing the work in either case, it seems >a rather moot point, don't you think? :-) Of course. However, if this item is on a 'todo' list somewhere, the use of OS/2 EA's, rather than creating a new method and adding to the confusion, should probably be commented upon under that same heading. =) --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 10:39:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27667 for freebsd-current-outgoing; Wed, 25 Nov 1998 10:39:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27661 for ; Wed, 25 Nov 1998 10:39:55 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA17268; Wed, 25 Nov 1998 13:43:32 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 25 Nov 1998 13:43:32 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: mike grommet cc: freebsd-current@FreeBSD.ORG Subject: Re: So, how long until 3.0-Stable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Nov 1998, mike grommet wrote: > Just wondering how long until the 3.0-stable path begins? > # uptime 1:37PM up 10 days, 19:08, 6 users, load averages: 0.30, 0.09, 0.04 # ls -l /kernel -r-xr-xr-x 1 root wheel 1739868 Nov 14 17:44 /kernel (rebooted to swap drives, using as a workstation, large compiles) A snap from a few hours before that date would be a nice bet. No garantees though. :) My box at home blew up a few days ago, but it's running a kernel from a few days later which i'm guessing was when the ffs_realloc problem popped up. -Alfred > Mike Grommet > Unix Systems Adminstrator > Internet Solutions, Inc. > mgrommet@insolwwb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 10:40:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27796 for freebsd-current-outgoing; Wed, 25 Nov 1998 10:40:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA27770 for ; Wed, 25 Nov 1998 10:40:07 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KGPTVYZJ; Wed, 25 Nov 98 18:39:58 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981125193943.00992af0@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 25 Nov 1998 19:39:43 +0100 To: Mike Smith , Andrew Gordon From: Marius Bendiksen Subject: Re: /boot/loader what to set rootdev to? Cc: "Jordan K. Hubbard" , Robert Nordier , freebsd-current@FreeBSD.ORG In-Reply-To: <199811251806.KAA01262@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Try booting a 3.0 kernel with 'options "VM86"' in the config. I am sure having the ability to do everything -except- VM86 in this fashion would be infinitely preferrable to not being able to do -anything- at all :) --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 10:42:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27879 for freebsd-current-outgoing; Wed, 25 Nov 1998 10:42:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA27872 for ; Wed, 25 Nov 1998 10:42:04 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KGPUIPQJ; Wed, 25 Nov 98 18:42:00 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981125194144.009a08e0@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 25 Nov 1998 19:41:44 +0100 To: Robert Nordier , jkh@zippy.cdrom.com (Jordan K. Hubbard) From: Marius Bendiksen Subject: Re: /boot/loader what to set rootdev to? Cc: rnordier@nordier.com, hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG In-Reply-To: <199811251255.OAA16516@ceia.nordier.com> References: <50633.911996966@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The umsdos solution was generalized to a file system layer approach >which could accommodate a FreeBSD slice on any (not necessarily >MS-DOS) file system which supports 255 character filenames. This is a good point, which I forgot in my posting. While the OS/2 EA's have the advantage of utilising an existing standard, this approach would offer us the ability to transparently use any filesystem. Though the 255 character filename requirement should go. We can stick the long filenames in a seperate file or EA. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 10:43:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27932 for freebsd-current-outgoing; Wed, 25 Nov 1998 10:43:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27926 for ; Wed, 25 Nov 1998 10:42:58 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA17276 for ; Wed, 25 Nov 1998 13:46:51 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 25 Nov 1998 13:46:51 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: 3.0 FS code is really nifty. Message-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 pretty much common knowledge that Softupdates are REALLY fast. But many operations are 2.5 to 5 times faster with FreeBSD-UFS+softupd than Solaris-UFS for file creation/deletion. Quite amazing. The just for kicks benches I did were not multiuser tests though, I'm going to look at that when I have a chance. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 10:48:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28371 for freebsd-current-outgoing; Wed, 25 Nov 1998 10:48:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28361 for ; Wed, 25 Nov 1998 10:48:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA01537; Wed, 25 Nov 1998 10:45:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811251845.KAA01537@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Marius Bendiksen cc: Mike Smith , Andrew Gordon , "Jordan K. Hubbard" , Robert Nordier , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Wed, 25 Nov 1998 19:39:43 +0100." <3.0.5.32.19981125193943.00992af0@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 10:45:39 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Try booting a 3.0 kernel with 'options "VM86"' in the config. > > I am sure having the ability to do everything -except- VM86 in this fashion > would be infinitely preferrable to not being able to do -anything- at all :) vm86 (and other similar functions) are going to be mandatory soon if we have any hope of keeping up with PC evolution. So let me put it more simply; DOS scrambles the state of the system to a point where it's not possible to run FreeBSD properly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 10:57:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29117 for freebsd-current-outgoing; Wed, 25 Nov 1998 10:57:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29111 for ; Wed, 25 Nov 1998 10:57:28 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id KAA00369; Wed, 25 Nov 1998 10:57:02 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811251857.KAA00369@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: mike grommet , freebsd-current@FreeBSD.ORG Subject: Re: So, how long until 3.0-Stable? In-reply-to: Your message of "Wed, 25 Nov 1998 13:43:32 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 10:57:02 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't had any crashes over here in a while and I am running with softupdates enabled. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 11:14:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00640 for freebsd-current-outgoing; Wed, 25 Nov 1998 11:14:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00633 for ; Wed, 25 Nov 1998 11:14:16 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id UAA07267; Wed, 25 Nov 1998 20:18:13 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Wed, 25 Nov 1998 20:18:13 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: Christopher Hall , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <199811251640.IAA00674@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Nov 1998, Mike Smith wrote: > > > > Let me add yet another question to this: is there any way to boot FreeBSD > > from DOS partition, using /boot/loader? > > It's not generally possible to boot FreeBSD once DOS has started; > modern DOS versions corrupt the BIOS vectors in a fashion that makes it > impossible to obtain system information. I said: "is it possible to start from _DOS_ _partition_". Not "from under running DOS"... see the difference? Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 11:15:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00712 for freebsd-current-outgoing; Wed, 25 Nov 1998 11:15:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA00703 for ; Wed, 25 Nov 1998 11:15:38 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zikPS-0000s9-00; Wed, 25 Nov 1998 12:15:30 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id MAA26254; Wed, 25 Nov 1998 12:15:59 -0700 (MST) Message-Id: <199811251915.MAA26254@harmony.village.org> To: "Justin T. Gibbs" Subject: Re: Adaptec 1542B still not detected Cc: gfm@mira.net (Graham Menhennitt), current@FreeBSD.ORG In-reply-to: Your message of "Sun, 22 Nov 1998 16:34:05 MST." <199811222334.QAA08681@narnia.plutotech.com> References: <199811222334.QAA08681@narnia.plutotech.com> Date: Wed, 25 Nov 1998 12:15:58 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199811222334.QAA08681@narnia.plutotech.com> "Justin T. Gibbs" writes: : The patch is inappropriate as it won't necessarily solve the problem : on all machines (loop is CPU speed dependant). I've fixed this by using DELAY. : I've been meening : to re-examine the aha probe code to see if we even need to look at : the geometry register. A better approach may be to try an extended : command and succeed the probe only if it fails. This requires the : ability to recovery from an invalid command in the driver and : ensuring that this works on all aha models. Ping me later in the : week and I should have something for you to test. I've tried that in the aha probe, but it locks up some cards (none of the ones that I have, but others that people have reported to me). I originally did do the extended setup command, and failed like this, but I ran into many problems with this. Touching the geometry register (which isn't present on older adaptech cards) seems to be fairly reliable, even if there needs to be some delay before touching it to make sure that we get ff from the read. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 11:44:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03267 for freebsd-current-outgoing; Wed, 25 Nov 1998 11:44:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03257 for ; Wed, 25 Nov 1998 11:44:37 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id MAA06556; Wed, 25 Nov 1998 12:43:57 -0700 (MST) (envelope-from gibbs@narnia.plutotech.com) Message-Id: <199811251943.MAA06556@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: gfm@mira.net (Graham Menhennitt), current@FreeBSD.ORG Subject: Re: Adaptec 1542B still not detected In-reply-to: Your message of "Wed, 25 Nov 1998 12:15:58 MST." <199811251915.MAA26254@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 12:36:31 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In message <199811222334.QAA08681@narnia.plutotech.com> "Justin T. Gibbs" writ >es: >: The patch is inappropriate as it won't necessarily solve the problem >: on all machines (loop is CPU speed dependant). > >I've fixed this by using DELAY. But we have no way of knowing how long of a wait is enough. >: I've been meening >: to re-examine the aha probe code to see if we even need to look at >: the geometry register. A better approach may be to try an extended >: command and succeed the probe only if it fails. This requires the >: ability to recovery from an invalid command in the driver and >: ensuring that this works on all aha models. Ping me later in the >: week and I should have something for you to test. > >I've tried that in the aha probe, but it locks up some cards (none of >the ones that I have, but others that people have reported to me). This makes no sense considering that in the GENERIC kernel the bt probe occurs before the aha probe and the bt probe will cause an extended setup command to go to the aha (assuming it shows up as having a geometry register). I would suspect that we aren't clearing the invalid command status properly if sending an extended setup command doesn't work. Which cards had problems with the extended setup command? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 11:45:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03308 for freebsd-current-outgoing; Wed, 25 Nov 1998 11:45:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03298 for ; Wed, 25 Nov 1998 11:45:07 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id NAA11425 for ; Wed, 25 Nov 1998 13:44:56 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <365C5E38.44FAC6A7@webwizard.org.mx> Date: Wed, 25 Nov 1998 13:44:56 -0600 From: Edwin Culp Reply-To: eculp@MexComUSA.net X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Current@FreeBSD.ORG Subject: IBM Netfinity 3500 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to install current on an IBM Netfinity 3500 PII-266 with everything on the motherboard. Adaptec SCSI, sound and an fxp 10/100 ethernet. Sounds good and everything works until I try to do an ifconfig to set up the fxp0 interface. I can list it , change the media, change mediaopt but when I put # ifconfig fxp0 inet myip netmask mymask and hit return, it dies. I don't even get to see my carriage return :-) I'm stumped. I even disabled it with BIOS and put a physical card in and it did the same. Thanks for any suggestions. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 11:52:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04005 for freebsd-current-outgoing; Wed, 25 Nov 1998 11:52:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03992 for ; Wed, 25 Nov 1998 11:52:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA01848; Wed, 25 Nov 1998 11:50:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811251950.LAA01848@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: eculp@MexComUSA.net cc: FreeBSD-Current@FreeBSD.ORG Subject: Re: IBM Netfinity 3500 In-reply-to: Your message of "Wed, 25 Nov 1998 13:44:56 CST." <365C5E38.44FAC6A7@webwizard.org.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 11:50:07 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am trying to install current on an IBM Netfinity 3500 PII-266 with > everything on the motherboard. Adaptec SCSI, sound and an fxp 10/100 > ethernet. Sounds good and everything works until I try to do an > ifconfig to set up the fxp0 interface. I can list it , change the > media, change mediaopt but when I put > > # ifconfig fxp0 inet myip netmask mymask > > and hit return, it dies. I don't even get to see my carriage return > :-) I'm stumped. I even disabled it with BIOS and put a physical card > in and it did the same. > > Thanks for any suggestions. This is noted in the release notes for 3.0-RELEASE; I experienced it at the IBM test centre here. I don't know what causes it; it looks like an interrupt lock or something similar. The short answer is - don't try to use the onboard ethernet. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 11:56:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04257 for freebsd-current-outgoing; Wed, 25 Nov 1998 11:56:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04249 for ; Wed, 25 Nov 1998 11:56:10 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id NAA11547; Wed, 25 Nov 1998 13:55:43 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <365C60BF.C46E19C2@webwizard.org.mx> Date: Wed, 25 Nov 1998 13:55:43 -0600 From: Edwin Culp Reply-To: eculp@MexComUSA.net X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith CC: jabc@webwizard.org.mx, FreeBSD-Current@FreeBSD.ORG Subject: Re: IBM Netfinity 3500 References: <199811251950.LAA01848@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > I am trying to install current on an IBM Netfinity 3500 PII-266 with > > everything on the motherboard. Adaptec SCSI, sound and an fxp 10/100 > > ethernet. Sounds good and everything works until I try to do an > > ifconfig to set up the fxp0 interface. I can list it , change the > > media, change mediaopt but when I put > > > > # ifconfig fxp0 inet myip netmask mymask > > > > and hit return, it dies. I don't even get to see my carriage return > > :-) I'm stumped. I even disabled it with BIOS and put a physical card > > in and it did the same. > > > > Thanks for any suggestions. > > This is noted in the release notes for 3.0-RELEASE; I experienced it at > the IBM test centre here. I don't know what causes it; it looks like an > interrupt lock or something similar. > > The short answer is - don't try to use the onboard ethernet. > Thank you. I disabled (BIOS) the onboard and installed a seperate card and had the same problem. Maybe I should look for a jumper? Thanks again, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 12:02:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04737 for freebsd-current-outgoing; Wed, 25 Nov 1998 12:02:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04662 for ; Wed, 25 Nov 1998 12:01:56 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA21943 for ; Wed, 25 Nov 1998 11:52:40 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdb21940; Wed Nov 25 19:52:37 1998 Date: Wed, 25 Nov 1998 11:52:10 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG Subject: reallocblks panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG message was: panic: ffs_reallocblks: non-physical cluster 1 syncing disks... 6 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving up no other info available at this time.. just a datapoint To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 12:04:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04957 for freebsd-current-outgoing; Wed, 25 Nov 1998 12:04:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04950 for ; Wed, 25 Nov 1998 12:04:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA01916; Wed, 25 Nov 1998 12:00:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811252000.MAA01916@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: eculp@MexComUSA.net cc: Mike Smith , jabc@webwizard.org.mx, FreeBSD-Current@FreeBSD.ORG Subject: Re: IBM Netfinity 3500 In-reply-to: Your message of "Wed, 25 Nov 1998 13:55:43 CST." <365C60BF.C46E19C2@webwizard.org.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 12:00:44 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > I am trying to install current on an IBM Netfinity 3500 PII-266 with > > > everything on the motherboard. Adaptec SCSI, sound and an fxp 10/100 > > > ethernet. Sounds good and everything works until I try to do an > > > ifconfig to set up the fxp0 interface. I can list it , change the > > > media, change mediaopt but when I put > > > > > > # ifconfig fxp0 inet myip netmask mymask > > > > > > and hit return, it dies. I don't even get to see my carriage return > > > :-) I'm stumped. I even disabled it with BIOS and put a physical card > > > in and it did the same. > > > > > > Thanks for any suggestions. > > > > This is noted in the release notes for 3.0-RELEASE; I experienced it at > > the IBM test centre here. I don't know what causes it; it looks like an > > interrupt lock or something similar. > > > > The short answer is - don't try to use the onboard ethernet. > > > > Thank you. I disabled (BIOS) the onboard and installed a seperate card and > had the same problem. Maybe I should look for a jumper? I don't know. You might want to talk to David Greenman about this one; he might have some ideas. You might also want to send the 'mptable' output to the SMP folks; they may have some ideas about interrupt routing that might shed some light on the situation. If you have time to tinker with the machine at all, it'd be very educational to add some debugging to the PCI interrupt handling code to see what's actually going on. A good start would be the interrupt handler for the 'fxp' device. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 12:21:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06678 for freebsd-current-outgoing; Wed, 25 Nov 1998 12:21:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06665 for ; Wed, 25 Nov 1998 12:21:14 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id OAA11782; Wed, 25 Nov 1998 14:21:03 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <365C66AF.7E9A42AB@webwizard.org.mx> Date: Wed, 25 Nov 1998 14:21:03 -0600 From: Edwin Culp Reply-To: eculp@MexComUSA.net X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith CC: eculp@MexComUSA.net, jabc@webwizard.org.mx, FreeBSD-Current@FreeBSD.ORG Subject: Re: IBM Netfinity 3500 References: <199811252000.MAA01916@dingo.cdrom.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > I don't know. You might want to talk to David Greenman about this one; > he might have some ideas. You might also want to send the 'mptable' > output to the SMP folks; they may have some ideas about interrupt > routing that might shed some light on the situation. > > If you have time to tinker with the machine at all, it'd be very > educational to add some debugging to the PCI interrupt handling code to > see what's actually going on. A good start would be the interrupt > handler for the 'fxp' device. > I don't have a better idea. I´ll give it a try. Thanks again. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 12:38:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08333 for freebsd-current-outgoing; Wed, 25 Nov 1998 12:38:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08157 for ; Wed, 25 Nov 1998 12:38:19 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA09604 for ; Wed, 25 Nov 1998 13:38:11 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA10234; Wed, 25 Nov 1998 13:38:11 -0700 Date: Wed, 25 Nov 1998 13:38:11 -0700 Message-Id: <199811252038.NAA10234@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: current@FreeBSD.ORG Subject: FWD: src/lib/libc/quad/moddi3.c broken! X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Keith White just fixed a bug in the JDK that turned out to be a bug in the libc source code. It's not normally seen because the version in libgcc.a works, and is used before the libc version. ------- start of forwarded message ------- From: Keith White Date: Wed, 25 Nov 1998 15:05:50 -0500 (EST) > You're a God! How did you figure this out? I kept writing trivial > programs and couldn't figure out what was going on, since all of my > trivial programs behaved correctly. For the curious: I first did 'nm -op /usr/lib/*.a | egrep moddi3'. This gave libc.a and libgcc.a. I then compared the source for the two versions. The version in /usr/src/lib/libc/quad/moddi3.c looked a little suspicious. To verify the problem, I built the following test program: --- main() { long long a, b, c, d; a = -12L; b = -5L; c = a % b; d = a - (a / b) * b; printf("long long '%%' %s\n", (c == d) ? "passed" : "failed"); } --- like this: cc -o remtest remtest.c ./remtest long long '%' passed cc -c remtest.c ld -r -o x.o remtest.o -lc cc -o remtest x.o ./remtest long long '%' failed Then I was convinced there was a problem with libc. Then a find javasrc/build -name '*.o' | xargs nm -op | egrep moddi3 gave me the likely candidates in the jdk build tree. The most critical one being in java/java. Quick check of the GNUmakefile showed '-lc'... I suppose this might actually be a true bug with libc. ...keith -- Keith White, EITI/SITE, University of Ottawa kwhite@site.uottawa.ca [+1 613 562 5800 x6681] FAX [+1 613 562 5187] ------- end of forwarded message ------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 12:44:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08803 for freebsd-current-outgoing; Wed, 25 Nov 1998 12:44:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08789 for ; Wed, 25 Nov 1998 12:44:40 -0800 (PST) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t1o29p82.telia.com [194.236.214.82]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id VAA00421 for ; Wed, 25 Nov 1998 21:44:32 +0100 Received: from pegasys (pegasys.granlund.nu [192.168.0.2]) by phoenix.granlund.nu (8.9.1/8.9.1) with SMTP id VAA00375 for ; Wed, 25 Nov 1998 21:34:48 +0100 (CET) (envelope-from johan@phoenix.granlund.nu) Message-Id: <199811252034.VAA00375@phoenix.granlund.nu> From: "Johan Granlund" To: freebsd-current@FreeBSD.ORG Date: Wed, 25 Nov 1998 20:36:57 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: sio breakage X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Have someone commited something that i missed that breaks sio? I have a HylaFAX that says that the modem appears to be wedget. The faxgetty process appears to talk to the modem but it seems that it dont get the right answers. This is a kernel cvsuped around 20:00 CET today. A kernel from NOV 19 works. /Johan ___________________________________________________________ Internet: johan@granlund.nu I don't even speak for myself To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 13:06:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11115 for freebsd-current-outgoing; Wed, 25 Nov 1998 13:06:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11002 for ; Wed, 25 Nov 1998 13:05:46 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA09783 for ; Wed, 25 Nov 1998 14:05:42 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA10347; Wed, 25 Nov 1998 14:05:41 -0700 Date: Wed, 25 Nov 1998 14:05:41 -0700 Message-Id: <199811252105.OAA10347@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nate Williams Cc: current@FreeBSD.ORG Subject: Re: FWD: src/lib/libc/quad/moddi3.c broken! In-Reply-To: <199811252038.NAA10234@mt.sri.com> References: <199811252038.NAA10234@mt.sri.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Keith White just fixed a bug in the JDK that turned out to be a bug in > the libc source code. It's not normally seen because the version in > libgcc.a works, and is used before the libc version. ...... > The version in /usr/src/lib/libc/quad/moddi3.c looked a > little suspicious. To verify the problem, I built the following test > program: > > --- > main() { > long long a, b, c, d; > a = -12L; b = -5L; > c = a % b; > d = a - (a / b) * b; > > printf("long long '%%' %s\n", (c == d) ? "passed" : "failed"); > } > --- > like this: > cc -o remtest remtest.c > ./remtest > long long '%' passed > > cc -c remtest.c > ld -r -o x.o remtest.o -lc > cc -o remtest x.o > ./remtest > long long '%' failed > > Then I was convinced there was a problem with libc. Here is my fix for it which appears to work. I'm not math whiz, but we're using the same sort of logic that exists in the gcc sources, and there is only a slight difference. Note, this 'fix' is also in the NetBSD sources in a slightly different form. They essentially copy the same algorithm as exists in the libgcc2 sources, while I minimized the changes and kept the original format for my fix. If no-one objects, I'll commit this when I get back next week. Nate ---------------- [ Warning, cut-n-paste done here so white-space is hosed ] Index: moddi3.c =================================================================== RCS file: /data/FreeBSD/CVS/src/lib/libc/quad/moddi3.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 moddi3.c --- moddi3.c 1994/05/27 04:57:21 1.1.1.1 +++ moddi3.c 1998/11/25 21:02:23 @@ -59,7 +59,7 @@ else ua = a, neg = 0; if (b < 0) - ub = -(u_quad_t)b, neg ^= 1; + ub = -(u_quad_t)b; else ub = b; (void)__qdivrem(ua, ub, &ur); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 13:45:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14284 for freebsd-current-outgoing; Wed, 25 Nov 1998 13:45:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14279 for ; Wed, 25 Nov 1998 13:45:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id NAA01135; Wed, 25 Nov 1998 13:45:50 -0800 (PST) To: Joel Ray Holveck cc: Marius Bendiksen , Robert Nordier , hsw@email.generalresources.com, hsw@acm.org, abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "25 Nov 1998 10:21:49 CST." <864srnyc82.fsf@detlev.UUCP> Date: Wed, 25 Nov 1998 13:45:50 -0800 Message-ID: <1131.912030350@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jordan, we've been over this before. Did you ever actually *try* what > the rest of the list said? Yes. It doesn't work. Have YOU? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 14:08:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16497 for freebsd-current-outgoing; Wed, 25 Nov 1998 14:08:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16484 for ; Wed, 25 Nov 1998 14:08:03 -0800 (PST) (envelope-from adrian@lorax.ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id RAA24924; Wed, 25 Nov 1998 17:07:49 -0500 (EST) (envelope-from adrian@lorax.ubergeeks.com) Date: Wed, 25 Nov 1998 17:07:49 -0500 (EST) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: mike grommet cc: freebsd-current@FreeBSD.ORG Subject: Re: So, how long until 3.0-Stable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Nov 1998, mike grommet wrote: > Just wondering how long until the 3.0-stable path begins? > I believe -current will branch into 3.x-stable and 3.x-current when 3.1 is released (1/15/99). In any event, there are not supposed to be any 2.x releases after 2.2.8, which I belive is scheduled for 11/30. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 14:47:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21657 for freebsd-current-outgoing; Wed, 25 Nov 1998 14:47:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21652 for ; Wed, 25 Nov 1998 14:47:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id OAA01542; Wed, 25 Nov 1998 14:48:26 -0800 (PST) To: Alfred Perlstein cc: mike grommet , freebsd-current@FreeBSD.ORG Subject: Re: So, how long until 3.0-Stable? In-reply-to: Your message of "Wed, 25 Nov 1998 13:43:32 EST." Date: Wed, 25 Nov 1998 14:48:26 -0800 Message-ID: <1537.912034106@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > # uptime > 1:37PM up 10 days, 19:08, 6 users, load averages: 0.30, 0.09, 0.04 > # ls -l /kernel > -r-xr-xr-x 1 root wheel 1739868 Nov 14 17:44 /kernel > > (rebooted to swap drives, using as a workstation, large compiles) Alfred, if you don't know how to answer a question, please don't bother trying - that's where list noise comes from. Your personal uptime has nothing to do with the planned date for forking 3.1, which is the question that was asked. We'll fork the tree again sometime in January, as previously announced on this list. As always, the list archives are Your Friend. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 15:06:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24471 for freebsd-current-outgoing; Wed, 25 Nov 1998 15:06:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24464 for ; Wed, 25 Nov 1998 15:06:23 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (isabella-39.pagesz.net [208.194.157.39]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id SAA01500 for ; Wed, 25 Nov 1998 18:06:23 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id SAA03957; Wed, 25 Nov 1998 18:06:56 -0500 (EST) (envelope-from rhh) Message-ID: <19981125180656.A2751@pagesz.net> Date: Wed, 25 Nov 1998 18:06:56 -0500 From: Randall Hopper To: current@FreeBSD.ORG Subject: Re: SANE & 3.0-RELEASE? - YES! Mail-Followup-To: current@FreeBSD.ORG References: <19981122101554.A8319@pagesz.net> <199811222319.QAA00516@panzer.plutotech.com> <19981122201349.B19160@pagesz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981122201349.B19160@pagesz.net>; from Randall Hopper on Sun, Nov 22, 1998 at 08:13:49PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to a SANE patch for CAM from Corey Kempf , and advice from Corey and Amancio Hasty , SANE is now up-n-running ELF/CAM on my box controlling my SCSI Microtek E6 Scanner (under GIMP no less, without a GIMP recompile). Thaks for the help guys! For the archives, here's what was needed beyond applying Cory's patch, and building/installing SANE: 1) First, for convenience, wire the scanner down to a specific CAM pass-through device. Example kernel config line: device pass0 at scbus0 target 6 unit 0 # CAM passthrough = Scanner 2) Make sure the relevent CAM passthrough and TLI devices exist. In my case they did (/dev/pass0 and /dev/xpt0, respectively). 3) Open up permissions to those devices so the relevent scanner users/groups can access them. E.g.: crw-rw---- 1 root scanner 31, 0 Nov 24 18:32 /dev/pass0 crw-rw---- 1 root scanner 104, 0 Nov 17 17:32 /dev/xpt0 works for me since the scanner grp is all that need xpt0 access. 4) Insert the appropriate /dev/pass? device name into your scanner's SANE config file in /usr/local/etc/sane.d/ (mine: microtek.conf). E.g.: #Uncomment following line to disable "clever precalibration" routines... #noprecal scsi * * Scanner /dev/pass0 NOTE: Unlike pre-CAM SANEs, you cannot create a symlink or hardlink (e.g. /dev/scanner) pointing to the real pass-through device, and then add the symlink path to this file. The config file has to literally contain the /dev/pass? device name. 5) Then fire up the scanner, rescan the bus (camcontrol rescan 0), make sure the scanner is there (camcontrol devlist), and scan away! Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 15:20:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26400 for freebsd-current-outgoing; Wed, 25 Nov 1998 15:20:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26324 for ; Wed, 25 Nov 1998 15:20:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA03368; Wed, 25 Nov 1998 15:20:55 -0800 (PST) To: Adrian Filipi-Martin cc: mike grommet , freebsd-current@FreeBSD.ORG Subject: Re: So, how long until 3.0-Stable? In-reply-to: Your message of "Wed, 25 Nov 1998 17:07:49 EST." Date: Wed, 25 Nov 1998 15:20:54 -0800 Message-ID: <3364.912036054@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I believe -current will branch into 3.x-stable and 3.x-current > when 3.1 is released (1/15/99). In any event, there are not supposed to 3.0.1 you mean. 3.1 isn't due until at least July of 1999. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 15:26:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27185 for freebsd-current-outgoing; Wed, 25 Nov 1998 15:26:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27173 for ; Wed, 25 Nov 1998 15:26:21 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA07149 for freebsd-current@FreeBSD.ORG; Thu, 26 Nov 1998 00:26:08 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id B916D15D1; Thu, 26 Nov 1998 00:23:04 +0100 (CET) Date: Thu, 26 Nov 1998 00:23:04 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: So, how long until 3.0-Stable? Message-ID: <19981126002304.A11137@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199811251857.KAA00369@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <199811251857.KAA00369@rah.star-gate.com>; from Amancio Hasty on Wed, Nov 25, 1998 at 10:57:02AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4835 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Amancio Hasty: > I haven't had any crashes over here in a while and I am running with > softupdates enabled. To add to this, I'm using SMP + softupdates on my 2x PPro/200 and it survived a "make world" w/o a hitch. 4635.42 real 4505.99 user 2548.80 sys 3.0-CURRENT, Intel Providence mb, 64 MB RAM. FreeBSD 3.0-CURRENT #4: Tue Nov 24 01:20:38 CET 1998 roberto@tara.freenix.org:/src/src/sys/compile/TARA_SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 15:48:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28591 for freebsd-current-outgoing; Wed, 25 Nov 1998 15:48:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28584 for ; Wed, 25 Nov 1998 15:48:30 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id XAA93484; Wed, 25 Nov 1998 23:48:16 GMT Message-ID: <365C9740.30D04971@tdx.co.uk> Date: Wed, 25 Nov 1998 23:48:16 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Nicolas Christin CC: freebsd-current@FreeBSD.ORG Subject: Re: files.newconf in 3.0 References: <365C4BF1.1318F833@cs.virginia.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicolas Christin wrote: > > Hi, > > I'm trying to install a packet scheduler on 3.0. Initially, this stuff > has been developed for 2.2.6, and to install it I would need to modify > /usr/src/sys/conf/files.newconf. The problem is that this file is not > present on 3.0. I'd like to know what is its equivalent. > > Thank you, If this is a driver, theres going to be quite a bit more changed than just that file AFAIK... :-( - I've recently ported my 2.2.7 driver to 3.0, quite a few things needed changing... What type/packet scheduler is it? Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 16:24:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03540 for freebsd-current-outgoing; Wed, 25 Nov 1998 16:24:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03532 for ; Wed, 25 Nov 1998 16:24:10 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with ESMTP id TAA74994 for ; Wed, 25 Nov 1998 19:23:59 -0500 (EST) Date: Wed, 25 Nov 1998 19:23:59 -0500 (EST) From: jack To: freebsd-current@FreeBSD.ORG Subject: 3.0 crashes/reboots Message-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 3 boxes that have each run 3.0-RELEASE and 3.0-CURRENT (approx 11/18 and 11/24 versions of current). All have completed at least one make world. Two of them, a dual P133 and a single PPro 200 both with SCSI only, have not crashed. The third, a dual P166 with IDE only, has crashed three times, twice running RELEASE and once running CURRENT as of 11/24. Two of the three crashes were with a NFS mounted /usr/ports, at the time the first there were no NFS mounts. This leads me to ask, are the people seeing crashes using IDE? Are any SCSI folks experiencing them? Just to shoot down my own theory, I also have a single P166 with IDE only running 3.0-19981009-BETA that has not crashed. `Light' doesn't begin to describe the usage that box gets. -------------------------------------------------------------------------- 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 Wed Nov 25 16:42:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04906 for freebsd-current-outgoing; Wed, 25 Nov 1998 16:42:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04873 for ; Wed, 25 Nov 1998 16:42:26 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA20043; Thu, 26 Nov 1998 11:12:08 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA12496; Thu, 26 Nov 1998 11:12:07 +1030 (CST) Message-ID: <19981126111206.E67961@freebie.lemis.com> Date: Thu, 26 Nov 1998 11:12:06 +1030 From: Greg Lehey To: jack , freebsd-current@FreeBSD.ORG Subject: Re: 3.0 crashes/reboots References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from jack on Wed, Nov 25, 1998 at 07:23:59PM -0500 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 Wednesday, 25 November 1998 at 19:23:59 -0500, jack wrote: > I have 3 boxes that have each run 3.0-RELEASE and 3.0-CURRENT > (approx 11/18 and 11/24 versions of current). All have completed > at least one make world. Two of them, a dual P133 and a single > PPro 200 both with SCSI only, have not crashed. > > The third, a dual P166 with IDE only, has crashed three times, > twice running RELEASE and once running CURRENT as of 11/24. Two > of the three crashes were with a NFS mounted /usr/ports, at the > time the first there were no NFS mounts. > > This leads me to ask, are the people seeing crashes using IDE? > Are any SCSI folks experiencing them? I'm sure the answer is ``yes'' in each case. And until you describe the crashes, the answer is also meaningless. What kind of problems have you been having? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 17:02:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06556 for freebsd-current-outgoing; Wed, 25 Nov 1998 17:02:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06548 for ; Wed, 25 Nov 1998 17:02:09 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with ESMTP id UAA93075; Wed, 25 Nov 1998 20:01:53 -0500 (EST) Date: Wed, 25 Nov 1998 20:01:52 -0500 (EST) From: jack To: Greg Lehey cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 crashes/reboots In-Reply-To: <19981126111206.E67961@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 26 Nov 1998, Greg Lehey wrote: > > This leads me to ask, are the people seeing crashes using IDE? > > Are any SCSI folks experiencing them? > > I'm sure the answer is ``yes'' in each case. And until you describe > the crashes, the answer is also meaningless. What kind of problems > have you been having? I'd like nothing more than to be able to provide more information but that's the tough part. :( I wasn't there for the first crash but the other two, the screen went blank and the next thing I saw was the video's bios sign on message. /var/log/messages provides no help either. Nov 25 16:05:01 diamond ntpdate[78074]: step time server ,,, Nov 25 18:04:59 diamond ntpdate[93775]: step time server ,,, Nov 25 18:26:54 diamond /kernel: Copyright (c) 1992-1998 FreeBSD Nov 25 18:26:54 diamond /kernel: Copyright (c) 1982, 1986, ... Nov 25 18:26:54 diamond /kernel: The Regents of the University... Nov 25 18:26:54 diamond /kernel: FreeBSD 3.0-CURRENT #0: Wed Nov 25 09:45:15 EST 1998 I plan to add DDB to the kernel when I go back to work on Monday. Any other ideas on how to get it to spit out useful information? -------------------------------------------------------------------------- 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 Wed Nov 25 17:22:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07869 for freebsd-current-outgoing; Wed, 25 Nov 1998 17:22:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07862 for ; Wed, 25 Nov 1998 17:22:03 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id RAA04766; Wed, 25 Nov 1998 17:29:30 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811260129.RAA04766@troutmask.apl.washington.edu> Subject: Re: 3.0 crashes/reboots In-Reply-To: <19981126111206.E67961@freebie.lemis.com> from Greg Lehey at "Nov 26, 1998 11:12: 6 am" To: grog@lemis.com (Greg Lehey) Date: Wed, 25 Nov 1998 17:29:30 -0800 (PST) Cc: jack@germanium.xtalwind.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Greg Lehey: > On Wednesday, 25 November 1998 at 19:23:59 -0500, jack wrote: > > I have 3 boxes that have each run 3.0-RELEASE and 3.0-CURRENT > > (approx 11/18 and 11/24 versions of current). All have completed > > at least one make world. Two of them, a dual P133 and a single > > PPro 200 both with SCSI only, have not crashed. > > > > The third, a dual P166 with IDE only, has crashed three times, > > twice running RELEASE and once running CURRENT as of 11/24. Two > > of the three crashes were with a NFS mounted /usr/ports, at the > > time the first there were no NFS mounts. > > > > This leads me to ask, are the people seeing crashes using IDE? > > Are any SCSI folks experiencing them? > > I'm sure the answer is ``yes'' in each case. And until you describe > the crashes, the answer is also meaningless. What kind of problems > have you been having? > I've never owned IDE hardware. I can crash my scsi system by firing off a "make -j 32 world", a "make" in /usr/ports/devel/ddd, and then in a kernel build tree continously run "make depend; make -j 8 ; make clean;" In essense, you need quite a bit of disk activity. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 17:39:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09426 for freebsd-current-outgoing; Wed, 25 Nov 1998 17:39:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09421 for ; Wed, 25 Nov 1998 17:39:14 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id RAA09852; Wed, 25 Nov 1998 17:40:10 -0800 (PST) Message-Id: <199811260140.RAA09852@root.com> To: Jesper Skriver cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Wed, 25 Nov 1998 15:59:53 +0100." <19981125155953.A2593@skriver.dk> From: David Greenman Reply-To: dg@root.com Date: Wed, 25 Nov 1998 17:40:10 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Wed, Nov 25, 1998 at 05:38:43AM -0800, David Greenman wrote: > >> This is unrelated to the filesystem panic that we've been talking about. I >> saw your followup about the fault occuring in zalloci(). A traceback would >> be helpfull in isolating this problem. > >This is with a diffenrent kernel with support for DDB > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x67566f7c >fault code = supervisor read, page not present >instruction pointer = 0x8 :0xf0153798 >stack pointer = 0x10 : 0xf42c2d34 >frame pointer = 0x10 : 0xf42c2d34 >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 = 264 (cpp) >interrupt mask = bio >kernel: type 12 trap, code=0 >Stopped at _gbincore+0x20: cmpl %ecx,0x64(%eax) >db> trace >_gbincore(f42b3740,0,288e,11,f42c2eb8) at _gbincore+0x20 >_getblk(f42b3740,0,2000,0,0) at _getblk+0x6d >_cluster_read(f42b3740,288e,0,0,2000) at _cluster_read+0x8b >_ffs_read(f42c2eec,f4205300,288e,f42c2f84,f42c2eec) at _ffs_read+0x3e9 >_vn_read(f0a6ab80,f42c2f30,f09f9c80,f4205300,f0234de4) at _vn_read+0x121 >_read(f4205300,f42c2f84,0,288e,8093000) at _read+0xb9 >_syscall(27,27,8093000,288e,efbfd388) at _syscall+0x187 >_Xint0x80_syscall() at _Xint0x80_syscall+0x2c >db> This appears to be different and unrelated as well and probably indicates a hardware problem. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 17:57:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11020 for freebsd-current-outgoing; Wed, 25 Nov 1998 17:57:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11012 for ; Wed, 25 Nov 1998 17:57:12 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id VAA00478 for ; Wed, 25 Nov 1998 21:00:06 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 25 Nov 1998 21:00:06 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: weird anomaly Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone noticed this recently: Ok this is odd, i just upgraded to a ELF kernel, from an aout kernel ~nov 12th. Everything is fine so far except one oddity I noticed. x11amp is REALLY weird. I have the FreeBSD ELF version downloaded from www.opensound.com and i'm using Luigi's drivers, MSS audio. (aout version also misbehaves the same way) Sound plays fine, however the app itself lags terribly. Meaning i click on it and drag it and it pauses for a second or two then zips over to where I dragged it. It's quite an amusing effect. Dialog boxes appear about 3 seconds after i try to bring one up. Ktrace doesn't show anything really odd from what I can see. Maybe something earlier was masking a bug in x11amp? or perhaps something else needs to be looked at. (i noticed some changes to the ipc code recently *nudge* *nudge*) mp3's are mounted via NFS but i'm not having problems with NFS speed at all... vfs.nfs.async: 1 vfs.nfs.gatherdelay: 10000 vfs.nfs.gatherdelay_v3: 10000 vfs.nfs.access_cache_timeout: 6 vfs.nfs.access_cache_hits: 627 vfs.nfs.access_cache_fills: 96 thanks for taking a look, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current Probing for PnP devices: CSN 1 Vendor ID: YMH0030 [0x3000a865] Serial 0x80860001 Comp ID: PNPb02f [0x2fb0 d041] mss_attach 1 at 0x530 irq 5 dma 0:1 flags 0x11 setting up yamaha registers set yamaha master volume to max pcm1 (CS423x/Yamaha sn 0x80860001) at 0x530-0x537 irq 5 drq 0 flags 0x11 on isa --config file-- # bright machine "i386" cpu "I686_CPU" ident bright maxusers 80 options INCLUDE_CONFIG_FILE # Include this file in kernel options SOFTUPDATES #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root device options FFS_ROOT #FFS usable as root device [keep this!] #options NFS_ROOT #NFS usable as root device options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console #options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor #options DEVFS options MFS options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" config kernel root on wd0 controller isa0 controller eisa0 controller pci0 controller pnp0 device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 vector pcmintr controller ppbus0 controller ppc0 at isa? port ? tty irq 7 vector ppcintr controller vpo0 at ppbus? device nlpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # Unless you know very well what you're doing, leave ft0 at drive 2, or # remove the line entirely if you don't need it. Trying to configure # it on another unit might cause surprises, see PR kern/7176. tape ft0 at fdc0 drive 2 options "CMD640" # work around CMD640 chip deficiency #controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x7fff7fff vector wdintr controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xe0ffe0ff vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xe0ffe0ff vector wdintr #controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0x7fff7fff vector wdintr #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) controller scbus0 device da0 device sa0 device pass0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device mse0 at isa? port 0x23c tty irq 5 vector mseintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device de0 device xl0 pseudo-device loop pseudo-device ether pseudo-device snp 4 pseudo-device bpfilter 4 pseudo-device vn 4 pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 256 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM options SYSVSEM options SYSVMSG options MSGBUF_SIZE=32768 options USER_LDT options "VM86" options VESA options DDB options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 18:29:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14013 for freebsd-current-outgoing; Wed, 25 Nov 1998 18:29:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hsw.generalresources.com ([203.79.17.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13990 for ; Wed, 25 Nov 1998 18:29:15 -0800 (PST) (envelope-from hsw@email.generalresources.com) Received: from hsw.generalresources.com (localhost.generalresources.com [127.0.0.1]) by hsw.generalresources.com (8.9.1/8.9.1) with ESMTP id KAA21774; Thu, 26 Nov 1998 10:25:33 +0800 (CST) (envelope-from hsw@hsw.generalresources.com) Message-Id: <199811260225.KAA21774@hsw.generalresources.com> To: Robert Nordier cc: mike@smith.net.au, freebsd-current@FreeBSD.ORG From: Christopher Hall Reply-to: Christopher Hall Subject: boot0, was /boot/loader what to set rootdev to? In-reply-to: Message of "Sat, 25 Nov 1998 12:47:02 +0200." <199811251047.MAA15178@ceia.nordier.com> X-Operating-System: FreeBSD 3.0 X-Mailer: exmh 2.0 Date: Thu, 26 Nov 1998 10:25:33 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199811251047.MAA15178@ceia.nordier.com>, Robert Nordier writes: >Christopher Hall wrote: > >> Another question: Is there any way to boot DOS from /boot/loader? >> Perhaps using some Forth code? > >I'm curious why you should want to do this (ie. rather than use a >partition manager such as boot0/booteasy or some free or commercial >alternative). I simply wanted to take an already installed/working FreeBSD system on a single IDE disk. (only has has one FreeBSD partition, no space left to install bootmanager partitions). Take it to a clients site - they have one pc with Win95 installed (disk is almost full). I would move the Win95 to slave, put the FreeBSD as master and still allow booting back into Win95. I will see if boot0 works, I did not see any reference to it in man boot. However, a quick look at the code suggests that it does not show the partitions on the second drive until F5 is pressed. This may be confusing for the user. >There's currently no way, though. The boot/loader, with Forth >itself, runs in userland (i386 protected mode ring 3). So you'd >have to add a BTX syscall, at least, in addition to the Forth code. I looked at BTX code and found system call, so it would have to invoke the 'exit' switch back to real mode code. Then instead of INT 0x19 would use BIOS disk services to load the selected boot block. The the drive/partition to load would be passed in a register to system call. Finally jump to the loaded boot block. For this to work after switching back to real mode, the machine state must the same as the just booted condition. i.e. Are all the bios vectors set back to normal? > >-- >Robert Nordier > --- Christopher Hall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 18:32:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14523 for freebsd-current-outgoing; Wed, 25 Nov 1998 18:32:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from drama.navinet.net (drama.navinet.net [206.25.93.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14517 for ; Wed, 25 Nov 1998 18:32:09 -0800 (PST) (envelope-from forrie@drama.navinet.net) Received: (from forrie@localhost) by drama.navinet.net (8.9.1a/8.9.1) id VAA25481 for freebsd-current@freebsd.org; Wed, 25 Nov 1998 21:31:52 -0500 (EST) Message-ID: <19981125213152.B25418@navinet.net> Date: Wed, 25 Nov 1998 21:31:52 -0500 From: Forrest Aldrich To: freebsd-current@FreeBSD.ORG Subject: XFree86-3.3.3 missing libtiff Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've checked the ports install for libtiff34... the X server is looking for libtiff34.so.1, but the package only installs libtiff.a and libtiff.so.4. Where is the bug? This applies to FreeBSD-3.0-CURRENT (build world 1.5 days ago, with current kernel from today). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 18:32:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14550 for freebsd-current-outgoing; Wed, 25 Nov 1998 18:32:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hsw.generalresources.com ([203.79.17.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14380 for ; Wed, 25 Nov 1998 18:31:20 -0800 (PST) (envelope-from hsw@email.generalresources.com) Received: from hsw.generalresources.com (localhost.generalresources.com [127.0.0.1]) by hsw.generalresources.com (8.9.1/8.9.1) with ESMTP id KAA21785; Thu, 26 Nov 1998 10:28:07 +0800 (CST) (envelope-from hsw@hsw.generalresources.com) Message-Id: <199811260228.KAA21785@hsw.generalresources.com> To: Andrzej Bialecki cc: Mike Smith , Christopher Hall , freebsd-current@FreeBSD.ORG From: Christopher Hall Reply-to: Christopher Hall Subject: Using Dos Partition, was Re: /boot/loader what to set rootdev to? In-reply-to: Message of "Wed, 25 Nov 1998 20:18:13 +0100." X-Operating-System: FreeBSD 3.0 X-Mailer: exmh 2.0 Date: Thu, 26 Nov 1998 10:28:07 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Andr zej Bialecki writes: >On Wed, 25 Nov 1998, Mike Smith wrote: > >> > >> > Let me add yet another question to this: is there any way to boot FreeBSD >> > from DOS partition, using /boot/loader? >> >> It's not generally possible to boot FreeBSD once DOS has started; >> modern DOS versions corrupt the BIOS vectors in a fashion that makes it >> impossible to obtain system information. > >I said: "is it possible to start from _DOS_ _partition_". Not "from under >running DOS"... see the difference? I have a client who want to make a PC function as an X terminal, there is little space on the hard disk (single Win95 C:). Maybe I could make an absolute minimum FreeBSD system, make an image of this save as dos file, put this and a kernel in c:\freebsd and boot. Could the vn device be used to implement this? >Andrzej Bialecki > >-------------------- ++-------++ ------------------------------------- > ||PicoBSD|| FreeBSD in your pocket? Go and see: > Research & Academic |+-------+| "Small & Embedded FreeBSD" > Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ >-------------------- ~-+==---+-+ ------------------------------------- > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > --- Christopher Hall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 18:54:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16309 for freebsd-current-outgoing; Wed, 25 Nov 1998 18:54:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16299 for ; Wed, 25 Nov 1998 18:54:41 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id DAA15362; Thu, 26 Nov 1998 03:51:34 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199811260251.DAA15362@ocean.campus.luth.se> Subject: Re: boot0, was /boot/loader what to set rootdev to? In-Reply-To: <199811260225.KAA21774@hsw.generalresources.com> from Christopher Hall at "Nov 26, 98 10:25:33 am" To: hsw@acm.org Date: Thu, 26 Nov 1998 03:51:33 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Christopher Hall: > I simply wanted to take an already installed/working FreeBSD system on > a single IDE disk. (only has has one FreeBSD partition, no space left > to install bootmanager partitions). Take it to a clients site - they > have one pc with Win95 installed (disk is almost full). I would move > the Win95 to slave, put the FreeBSD as master and still allow booting > back into Win95. Excuse me? Win 95 needs to be on "C:", ie the first disk. No can do. Instead take your drive, and a DOS boot floppy with bootinst.exe and boot.bin and go to your customer. Hang your drive as slave, and boot from the floppy, and install booteasy using bootinst.exe, and you can boot either of the disks. /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 20:19:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22030 for freebsd-current-outgoing; Wed, 25 Nov 1998 20:19:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hsw.generalresources.com ([203.79.17.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22017 for ; Wed, 25 Nov 1998 20:18:34 -0800 (PST) (envelope-from hsw@email.generalresources.com) Received: from hsw.generalresources.com (localhost.generalresources.com [127.0.0.1]) by hsw.generalresources.com (8.9.1/8.9.1) with ESMTP id MAA22180; Thu, 26 Nov 1998 12:15:39 +0800 (CST) (envelope-from hsw@hsw.generalresources.com) Message-Id: <199811260415.MAA22180@hsw.generalresources.com> To: Mikael Karpberg cc: hsw@acm.org, freebsd-current@FreeBSD.ORG From: Christopher Hall Reply-to: Christopher Hall Subject: Re: boot0, was /boot/loader what to set rootdev to? In-reply-to: Message of "Thu, 26 Nov 1998 03:51:33 +0100." <199811260251.DAA15362@ocean.campus.luth.se> X-Operating-System: FreeBSD 3.0 X-Mailer: exmh 2.0 Date: Thu, 26 Nov 1998 12:15:38 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199811260251.DAA15362@ocean.campus.luth.se>, Mikael Karpberg writes : >According to Christopher Hall: >> I simply wanted to take an already installed/working FreeBSD system on >> a single IDE disk. (only has has one FreeBSD partition, no space left >> to install bootmanager partitions). Take it to a clients site - they >> have one pc with Win95 installed (disk is almost full). I would move >> the Win95 to slave, put the FreeBSD as master and still allow booting >> back into Win95. > >Excuse me? Win 95 needs to be on "C:", ie the first disk. No can do. >Instead take your drive, and a DOS boot floppy with bootinst.exe and >boot.bin and go to your customer. Hang your drive as slave, and boot >from the floppy, and install booteasy using bootinst.exe, and you can >boot either of the disks. > > /Mikael > Thanks for the info. --- Christopher Hall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 20:36:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23057 for freebsd-current-outgoing; Wed, 25 Nov 1998 20:36:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oitunix.oit.umass.edu (nscs22p16.remote.umass.edu [128.119.179.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23020 for ; Wed, 25 Nov 1998 20:35:48 -0800 (PST) (envelope-from gp@oitunix.oit.umass.edu) Received: (from gp@localhost) by oitunix.oit.umass.edu (8.9.1/8.9.1) id XAA01101 for current@freebsd.org; Wed, 25 Nov 1998 23:35:42 -0500 (EST) (envelope-from gp) Message-ID: <19981125233541.A1094@oit.umass.edu> Date: Wed, 25 Nov 1998 23:35:41 -0500 From: Greg Pavelcak To: current@FreeBSD.ORG Subject: Xlib: unexpected async reply Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm posting here because I run -current, but I'm not quite sure what information is relevant to my problem. I installed 3.0 plus X from the Walnut Creek CD-Rom; then immediately cvsup-ed and built world and elf-kernel (sources from 11/21). All this seemed to go well. I also installed fvwm2 as window manager. My problem is when I quit certain programs running in X --tkdesk, tkcvs, tkinfo for example--just about everything stops working. Specifically, although the mouse pointer still moves, neither keyboard shortcuts nor mouse clicks have any affect. Furthermore, focus does not follow the mouse. So, I quit X with ctl/alt/backspace and see the message: Xlib: unexpected async reply (sequence 0xe08) on the console (though the number changes). I seem to be able to open and close xterms without a problem. Any insight on this would be appreciated. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 20:44:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23458 for freebsd-current-outgoing; Wed, 25 Nov 1998 20:44:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles143.castles.com [208.214.165.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23451 for ; Wed, 25 Nov 1998 20:44:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA00358; Wed, 25 Nov 1998 20:43:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811260443.UAA00358@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Hall cc: Robert Nordier , mike@smith.net.au, freebsd-current@FreeBSD.ORG Subject: Re: boot0, was /boot/loader what to set rootdev to? In-reply-to: Your message of "Thu, 26 Nov 1998 10:25:33 +0800." <199811260225.KAA21774@hsw.generalresources.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 20:43:05 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In message <199811251047.MAA15178@ceia.nordier.com>, Robert Nordier writes: > >Christopher Hall wrote: > > > >> Another question: Is there any way to boot DOS from /boot/loader? > >> Perhaps using some Forth code? > > > >I'm curious why you should want to do this (ie. rather than use a > >partition manager such as boot0/booteasy or some free or commercial > >alternative). > > I simply wanted to take an already installed/working FreeBSD system on > a single IDE disk. (only has has one FreeBSD partition, no space left > to install bootmanager partitions). Take it to a clients site - they > have one pc with Win95 installed (disk is almost full). I would move > the Win95 to slave, put the FreeBSD as master and still allow booting > back into Win95. Some bootmanagers don't require extra partitions (boot0, booteasy, OS-BS, etc.) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 20:48:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23950 for freebsd-current-outgoing; Wed, 25 Nov 1998 20:48:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles143.castles.com [208.214.165.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23943 for ; Wed, 25 Nov 1998 20:48:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA00402; Wed, 25 Nov 1998 20:47:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811260447.UAA00402@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Hall cc: Andrzej Bialecki , Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: Using Dos Partition, was Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Thu, 26 Nov 1998 10:28:07 +0800." <199811260228.KAA21785@hsw.generalresources.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 20:46:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a client who want to make a PC function as an X terminal, there > is little space on the hard disk (single Win95 C:). Maybe I could > make an absolute minimum FreeBSD system, make an image of this save as > dos file, put this and a kernel in c:\freebsd and boot. Could the vn > device be used to implement this? Get an X server for Windows. This will stop them whining about not being able to run Word at the same time. Alternatively, if they don't want PC functionality, nuke the Windows stuff. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 20:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24176 for freebsd-current-outgoing; Wed, 25 Nov 1998 20:54:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24171 for ; Wed, 25 Nov 1998 20:54:28 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with ESMTP id XAA75280; Wed, 25 Nov 1998 23:54:16 -0500 (EST) Date: Wed, 25 Nov 1998 23:54:15 -0500 (EST) From: jack To: Steve Kargl cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 crashes/reboots In-Reply-To: <199811260129.RAA04766@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Nov 1998, Steve Kargl wrote: > I've never owned IDE hardware. Wish I could say that. > I can crash my scsi system by > firing off a "make -j 32 world", a "make" in /usr/ports/devel/ddd, > and then in a kernel build tree continously run > "make depend; make -j 8 ; make clean;" Glad I can't say that. ddd just finished building, make world and the endless loop of kernel builds are still running, and so is the build of the new X in /usr/ports/x11/XFree86 that I started before the rest of them. > In essense, you need quite a bit of disk activity. Had that. -------------------------------------------------------------------------- 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 Wed Nov 25 21:14:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25669 for freebsd-current-outgoing; Wed, 25 Nov 1998 21:14:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles143.castles.com [208.214.165.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25661 for ; Wed, 25 Nov 1998 21:14:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00592; Wed, 25 Nov 1998 21:13:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811260513.VAA00592@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Mike Smith , Christopher Hall , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Wed, 25 Nov 1998 20:18:13 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 21:13:05 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 25 Nov 1998, Mike Smith wrote: > > > > > > > Let me add yet another question to this: is there any way to boot FreeBSD > > > from DOS partition, using /boot/loader? > > > > It's not generally possible to boot FreeBSD once DOS has started; > > modern DOS versions corrupt the BIOS vectors in a fashion that makes it > > impossible to obtain system information. > > I said: "is it possible to start from _DOS_ _partition_". Not "from under > running DOS"... see the difference? I didn't, no. Yes, it's possible; you can load the kernel and then either change $currdev or set $rootdev to the 'real' root filesystem. ($rootdev was being bogusly ignored until recently, so you will want to be up to date) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 21:28:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26598 for freebsd-current-outgoing; Wed, 25 Nov 1998 21:28:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26591 for ; Wed, 25 Nov 1998 21:28:23 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forresta (forrie.ne.mediaone.net [24.128.73.118]) by spook.navinet.net (8.9.1/8.9.1) with SMTP id AAA63608 for ; Thu, 26 Nov 1998 00:29:04 -0500 (EST) Message-Id: <4.1.19981126001953.0091d140@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 26 Nov 1998 00:28:07 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Page fault crash 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 installed a new TEAC scsi-2 CDROM and SoundBlaster AWE32 card... when using the OSS drivers to configure the card, the system crashed with the following error. I'm not sure whether this is the driver's fault or if I've hit upon a buglet in FreeBSD-3.0-CURRENT. I just rebuilt the kernel... cvsup'd this evening. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10 fault code = supervisor write, page not present instruction pointer = 0x8:0xf8234710 stack pointer = 0x10:0xf8233c9c frame pointer = 0x10:0xf8233cc0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor flags = resume, IOPL = 0 current process = 345 (sndconf) interrupt mask = trap number = 12 panic: page fault syncing disks... 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 giving up To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 21:31:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26835 for freebsd-current-outgoing; Wed, 25 Nov 1998 21:31:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles143.castles.com [208.214.165.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26819 for ; Wed, 25 Nov 1998 21:31:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00764; Wed, 25 Nov 1998 21:30:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811260530.VAA00764@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: Page fault crash In-reply-to: Your message of "Thu, 26 Nov 1998 00:28:07 EST." <4.1.19981126001953.0091d140@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 21:30:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've installed a new TEAC scsi-2 CDROM and SoundBlaster AWE32 card... > when using the OSS drivers to configure the card, the system crashed > with the following error. I'm not sure whether this is the driver's fault > or if I've hit upon a buglet in FreeBSD-3.0-CURRENT. I just rebuilt > the kernel... cvsup'd this evening. OSS almost certainly won't work with 3.0; it's too much of a moving target for a commercial product to support. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 21:35:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27055 for freebsd-current-outgoing; Wed, 25 Nov 1998 21:35:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27001 for ; Wed, 25 Nov 1998 21:34:59 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id PAA04868; Thu, 26 Nov 1998 15:59:02 +1030 (CST) Received: from fuzz.dsto.defence.gov.au ([131.185.75.229]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id XTZMWN31; Thu, 26 Nov 1998 16:04:36 +1030 Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by fuzz.dsto.defence.gov.au (8.9.1/8.8.8) with ESMTP id QAA00758; Thu, 26 Nov 1998 16:04:31 +1030 (CST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Message-ID: <365CE867.62F68C8A@dsto.defence.gov.au> Date: Thu, 26 Nov 1998 16:04:31 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-BETA i386) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: Graham Menhennitt , CURRENT@FreeBSD.ORG Subject: aha delaying patch works for genuine 1542B Content-Type: multipart/mixed; boundary="------------FD0CFC316C29D9F6C098DBFA" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------FD0CFC316C29D9F6C098DBFA Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The card wasn't detected at all before and now it works fine! The card in question is a genuine Adaptec 1542B and I really need it to work as it contains my /usr/src !! As Graham Menhennitt said: "Could somebody please commit this change" The source I patched was CTM src-cur.3631 where /sys/dev/aha/aha.c is version 1.12 The patch I used is: fuzz: {1} diff /sys/dev/aha/aha.c.orig /sys/dev/aha/aha.c 356a357,359 > printf("aha: Before Matts DELAY\n"); > DELAY(100000); > printf("aha: After Matts DELAY\n"); 357a361 > printf("aha: After aha_inb(aha, GEOMETRY_REG)\n"); -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 --------------FD0CFC316C29D9F6C098DBFA Content-Type: message/rfc822; name="nsmail365B38EB0105803" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="nsmail365B38EB0105803" Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by itd3.dsto.defence.gov.au (8.8.8/sendmail.ITD.EDB+userdb.960305) with ESMTP id IAA10950 for ; Wed, 11 Nov 1998 08:38:29 +1030 (CST) Received: by exchsa1.dsto.defence.gov.au with Internet Mail Service (5.5.2232.9) id ; Wed, 11 Nov 1998 08:38:38 +1030 Received: from dsto-ms1.dsto.defence.gov.au (mimesweeper.dsto.defence.gov.au [131.185.2.51]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id WTQFV9HF; Wed, 11 Nov 1998 08:38:33 +1030 Received: from digger1.defence.gov.au (unverified [203.5.217.4]) by dsto-ms1.dsto.defence.gov.au (Integralis SMTPRS 2.04) with SMTP id ; Wed, 11 Nov 1998 08:41:49 +1030 Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id IAA00765 for ; Wed, 11 Nov 1998 08:32:39 +1030 (CST) Received: by hub.freebsd.org (VMailer, from userid 1) id 8C540A0B6; Tue, 10 Nov 1998 14:07:27 -0800 (PST) Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23792 for freebsd-current-outgoing; Tue, 10 Nov 1998 14:07:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from werple.mira.net (werple.mira.net [203.9.190.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA23780 for ; Tue, 10 Nov 1998 14:07:24 -0800 (PST) (envelope-from gfm@mira.net) Received: (qmail 27050 invoked from network); 10 Nov 1998 22:07:04 -0000 Received: from dp-m-r051.werple.net.au (203.17.46.51) by mira.net with SMTP; 10 Nov 1998 22:07:04 -0000 Delivered-To: vmailer-current@freebsd.org From: gfm@mira.net (Graham Menhennitt) To: "Justin T. Gibbs" , freebsd-current@FreeBSD.ORG Subject: Re: 3.0-CURRENT: Adaptec 1540 not detected (with workaround) Date: Tue, 10 Nov 1998 22:09:37 GMT Message-Id: <3648b287.87315503@mira.net> References: <199811100058.RAA22604@narnia.plutotech.com> In-Reply-To: <199811100058.RAA22604@narnia.plutotech.com> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA23785 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=us-ascii X-Mozilla-Status2: 00000000 Ok, I did a bit more investigating. Firstly, I pulled the card out of the machine. It's an AHA 1542B. Then I added a printf to output the board id and the status value read from the geometry register. The values were 0x41 and 0xFF respectively. Hang on... with those values, the test should pass!!! I did a bit more fiddling and found that putting in the printf makes it work! It must be a timing problem. Sure enough, I added a delay loop before reading the geometry register and it fixed it. I forgot to generate a patch file but it now looks like: if (aha->boardid <= 0x42) { int dummy; for(dummy = 0; dummy < 1000; dummy++) ; status = aha_inb(aha, GEOMETRY_REG); if (status != 0xff) return (ENXIO); } I tried 100 for the loop count but it still failed. I don't know if there is a more elegant way of doing this. But anyway, the above seems to work 100% reliably. Could somebody please commit this change. Graham On Mon, 9 Nov 1998 17:58:30 -0700 (MST), you wrote: >In article <36484fb6.262608561@mira.net> you wrote: >> Eventually I found the problem. In /usr/src/sys/dev/aha/aha.c there is some >> code that attempts to distinguish between Adaptec and Buslogic adaptors. >> This was failing. I'm not sure what model my adaptor is (I think it's an >> 'A') but it is a genuine Adaptec. Hence the comment in the code about >> cloned cards may apply to some genuine ones also. > > >Can you print out the value of aha->boardid and send it to me? It >would also be useful for you to look in your machine and determine >exactly which version of this card you have. > >Thanks, >Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message --------------FD0CFC316C29D9F6C098DBFA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 21:41:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27372 for freebsd-current-outgoing; Wed, 25 Nov 1998 21:41:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27366 for ; Wed, 25 Nov 1998 21:41:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA00926; Wed, 25 Nov 1998 21:42:07 -0800 (PST) To: Mike Smith cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Page fault crash In-reply-to: Your message of "Wed, 25 Nov 1998 21:30:14 PST." <199811260530.VAA00764@dingo.cdrom.com> Date: Wed, 25 Nov 1998 21:42:06 -0800 Message-ID: <921.912058926@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OSS almost certainly won't work with 3.0; it's too much of a moving > target for a commercial product to support. Actually, according to their web site oss was very recently (like last week) patched up to 3.0-current level. With some apparent help from Bruce Evans (way to go bde!), they worked out the contiguous DMA buffer allocation issues. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 21:55:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27948 for freebsd-current-outgoing; Wed, 25 Nov 1998 21:55:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles143.castles.com [208.214.165.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27943 for ; Wed, 25 Nov 1998 21:55:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00916; Wed, 25 Nov 1998 21:53:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811260553.VAA00916@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Mike Smith , Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Page fault crash In-reply-to: Your message of "Wed, 25 Nov 1998 21:42:06 PST." <921.912058926@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 21:53:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > OSS almost certainly won't work with 3.0; it's too much of a moving > > target for a commercial product to support. > > Actually, according to their web site oss was very recently (like last > week) patched up to 3.0-current level. With some apparent help from > Bruce Evans (way to go bde!), they worked out the contiguous DMA > buffer allocation issues. Way to go! We should talk them through the conversion to a KLD module as soon as we're sure what they need to look like. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 22:15:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29351 for freebsd-current-outgoing; Wed, 25 Nov 1998 22:15:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29346 for ; Wed, 25 Nov 1998 22:15:34 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca3-185.ix.netcom.com [209.109.233.185]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id WAA21418; Wed, 25 Nov 1998 22:15:19 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id WAA26413; Wed, 25 Nov 1998 22:15:09 -0800 (PST) Date: Wed, 25 Nov 1998 22:15:09 -0800 (PST) Message-Id: <199811260615.WAA26413@silvia.hip.berkeley.edu> To: forrie@navinet.net CC: freebsd-current@FreeBSD.ORG In-reply-to: <19981125213152.B25418@navinet.net> (message from Forrest Aldrich on Wed, 25 Nov 1998 21:31:52 -0500) Subject: Re: XFree86-3.3.3 missing libtiff From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * I've checked the ports install for libtiff34... the * X server is looking for libtiff34.so.1, but the package * only installs libtiff.a and libtiff.so.4. Which "X server" are you talking about? The X server doesn't require the tiff library here: === ## ldd /usr/X11R6/bin/XF86_SVGA /usr/X11R6/bin/XF86_SVGA: -lxpg4.2 => /usr/lib/libxpg4.so.2.0 (0x20288000) -lz.2 => /usr/lib/libz.so.2.0 (0x2028b000) -lm.2 => /usr/lib/libm.so.2.0 (0x20297000) -lc.3 => /usr/lib/libc.so.3.1 (0x202b1000) === Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 25 22:27:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00403 for freebsd-current-outgoing; Wed, 25 Nov 1998 22:27:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00398 for ; Wed, 25 Nov 1998 22:27:34 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forresta (forrie.ne.mediaone.net [24.128.73.118]) by spook.navinet.net (8.9.1/8.9.1) with SMTP id BAA63729 for ; Thu, 26 Nov 1998 01:28:02 -0500 (EST) Message-Id: <4.1.19981126012554.009266c0@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 26 Nov 1998 01:26:59 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Page fault response from OSS Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's the follow-up to the problem I reported earlier. Apparently it is a FreeBSD kernel buglet. Forrest >There are still problems with FreeBSD 3.0 inspite of the patch. > >There is nothing we can do until the kernel people really fix the bug. >This patch is a temporary workaround. > >Best regards >tech support > >-- >--------------------------------------------------------------------- >4Front Technologies > >4035 Lafayette Place, Unit F, Culver City, CA 90232, USA. > >Tel: (310) 202 8530 URL: www.opensound.com >Fax: (310) 202 0496 Email: info@opensound.com >--------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 00:13:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07946 for freebsd-current-outgoing; Thu, 26 Nov 1998 00:13:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freesbee.t.dk (freesbee.t.dk [193.163.159.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA07941 for ; Thu, 26 Nov 1998 00:13:35 -0800 (PST) (envelope-from jesper@freesbee.t.dk) Received: (qmail 14331 invoked by uid 1001); 26 Nov 1998 08:13:30 -0000 Date: Thu, 26 Nov 1998 09:13:30 +0100 From: Jesper Skriver To: David Greenman Cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity Message-ID: <19981126091330.C14233@skriver.dk> References: <19981125155953.A2593@skriver.dk> <199811260140.RAA09852@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: <199811260140.RAA09852@root.com>; from David Greenman on Wed, Nov 25, 1998 at 05:40:10PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 25, 1998 at 05:40:10PM -0800, David Greenman wrote: > >This is with a diffenrent kernel with support for DDB > > > >Fatal trap 12: page fault while in kernel mode > >fault virtual address = 0x67566f7c > >fault code = supervisor read, page not present > >instruction pointer = 0x8 :0xf0153798 > >stack pointer = 0x10 : 0xf42c2d34 > >frame pointer = 0x10 : 0xf42c2d34 > >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 = 264 (cpp) > >interrupt mask = bio > >kernel: type 12 trap, code=0 > >Stopped at _gbincore+0x20: cmpl %ecx,0x64(%eax) > >db> trace > >_gbincore(f42b3740,0,288e,11,f42c2eb8) at _gbincore+0x20 > >_getblk(f42b3740,0,2000,0,0) at _getblk+0x6d > >_cluster_read(f42b3740,288e,0,0,2000) at _cluster_read+0x8b > >_ffs_read(f42c2eec,f4205300,288e,f42c2f84,f42c2eec) at _ffs_read+0x3e9 > >_vn_read(f0a6ab80,f42c2f30,f09f9c80,f4205300,f0234de4) at _vn_read+0x121 > >_read(f4205300,f42c2f84,0,288e,8093000) at _read+0xb9 > >_syscall(27,27,8093000,288e,efbfd388) at _syscall+0x187 > >_Xint0x80_syscall() at _Xint0x80_syscall+0x2c > >db> > > This appears to be different and unrelated as well and probably indicates > a hardware problem. Have you got any idea which HW, I've got a ethernet card that logs "Recieve CRC error" all the time, I'm working on getting it replaced, but as the security people here require static MAC addresses in the routers, it's a but of a hassle to swap it ... sigh ... /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 00:56:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10462 for freebsd-current-outgoing; Thu, 26 Nov 1998 00:56:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-1-dbn.dial-up.net [196.34.155.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10456 for ; Thu, 26 Nov 1998 00:56:23 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id KAA22086; Thu, 26 Nov 1998 10:53:38 +0200 (SAT) From: Robert Nordier Message-Id: <199811260853.KAA22086@ceia.nordier.com> Subject: Re: boot0, was /boot/loader what to set rootdev to? In-Reply-To: <199811260225.KAA21774@hsw.generalresources.com> from Christopher Hall at "Nov 26, 98 10:25:33 am" To: hsw@acm.org Date: Thu, 26 Nov 1998 10:53:30 +0200 (SAT) Cc: rnordier@nordier.com, mike@smith.net.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Hall wrote: > > In message <199811251047.MAA15178@ceia.nordier.com>, Robert Nordier writes: > > >There's currently no way, though. The boot/loader, with Forth > >itself, runs in userland (i386 protected mode ring 3). So you'd > >have to add a BTX syscall, at least, in addition to the Forth code. > > I looked at BTX code and found system call, so it would have to invoke > the 'exit' switch back to real mode code. Then instead of INT 0x19 > would use BIOS disk services to load the selected boot block. > The the drive/partition to load would be passed in a register to system > call. Finally jump to the loaded boot block. > > For this to work after switching back to real mode, the machine state > must the same as the just booted condition. i.e. Are all the bios > vectors set back to normal? The bios vectors themselves are not currently altered. The interrupt vector offsets (of the PICs) are changed for protected mode, but are reprogrammed on re-entry into real address mode. BTX doesn't itself mess with the A20 line, but this is usually done in the boot blocks, so you may have to undo this, by way of the keyboard controller. I think it may just be easier to handle all of this by modifying the booteasy or boot0 sources, though, if neither of them meet your needs "as is". The first PC partition almost invariable begins on cylinder 0, head 1, so (as others have already mentioned) a number of boot managers exist which require no otherwise-usable space. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 01:06:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11312 for freebsd-current-outgoing; Thu, 26 Nov 1998 01:06:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freesbee.t.dk (freesbee.t.dk [193.163.159.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA11306 for ; Thu, 26 Nov 1998 01:06:34 -0800 (PST) (envelope-from ncbp@freesbee.t.dk) Received: (qmail 14721 invoked by uid 1002); 26 Nov 1998 09:06:27 -0000 Date: Thu, 26 Nov 1998 10:06:27 +0100 From: "Niels Chr. Bank-Pedersen" To: Jesper Skriver Cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity Message-ID: <19981126100627.B14622@bank-pedersen.dk> References: <19981125155953.A2593@skriver.dk> <199811260140.RAA09852@root.com> <19981126091330.C14233@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: <19981126091330.C14233@skriver.dk>; from Jesper Skriver on Thu, Nov 26, 1998 at 09:13:30AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 26, 1998 at 09:13:30AM +0100, Jesper Skriver wrote: > > > > This appears to be different and unrelated as well and probably indicates > > a hardware problem. > > Have you got any idea which HW, I've got a ethernet card that logs > "Recieve CRC error" all the time, I'm working on getting it replaced, > but as the security people here require static MAC addresses in the > routers, it's a but of a hassle to swap it ... sigh ... My guess would be RAM - I've seen often enough, that what works in one OS doesn't necessarily work in another - that goes for upgrading from 2.2.x to 3.x as well I guess. You have checked your CPU-fan, right? :-) > /Jesper /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark DataNET, IP-section. # rsh -l God universe.all find / -name '*windows*' -exec rm -rf {} \; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 01:06:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11335 for freebsd-current-outgoing; Thu, 26 Nov 1998 01:06:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11301 for ; Thu, 26 Nov 1998 01:06:20 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id BAA14375; Thu, 26 Nov 1998 01:07:10 -0800 (PST) Message-Id: <199811260907.BAA14375@root.com> To: Jesper Skriver cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-reply-to: Your message of "Thu, 26 Nov 1998 09:13:30 +0100." <19981126091330.C14233@skriver.dk> From: David Greenman Reply-To: dg@root.com Date: Thu, 26 Nov 1998 01:07:10 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> This appears to be different and unrelated as well and probably indicates >> a hardware problem. > >Have you got any idea which HW, I've got a ethernet card that logs >"Recieve CRC error" all the time, I'm working on getting it replaced, >but as the security people here require static MAC addresses in the >routers, it's a but of a hassle to swap it ... sigh ... Memory, cache, CPU, or motherboard. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 02:09:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15136 for freebsd-current-outgoing; Thu, 26 Nov 1998 02:09:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freesbee.t.dk (freesbee.t.dk [193.163.159.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA15129 for ; Thu, 26 Nov 1998 02:09:08 -0800 (PST) (envelope-from jesper@freesbee.t.dk) Received: (qmail 15396 invoked by uid 1001); 26 Nov 1998 10:09:03 -0000 Date: Thu, 26 Nov 1998 11:09:02 +0100 From: Jesper Skriver To: David Greenman Cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity Message-ID: <19981126110902.C15228@skriver.dk> References: <19981126091330.C14233@skriver.dk> <199811260907.BAA14375@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: <199811260907.BAA14375@root.com>; from David Greenman on Thu, Nov 26, 1998 at 01:07:10AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 26, 1998 at 01:07:10AM -0800, David Greenman wrote: > >> This appears to be different and unrelated as well and probably indicates > >> a hardware problem. > > > >Have you got any idea which HW, I've got a ethernet card that logs > >"Recieve CRC error" all the time, I'm working on getting it replaced, > >but as the security people here require static MAC addresses in the > >routers, it's a but of a hassle to swap it ... sigh ... > > Memory, cache, CPU, or motherboard. I finally got the old lance ethernet replaced with a 3c905B card, and now it hasn't crashed yet, even a "make buildworld" and running X at the same time hasn't crashed the box ... /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 07:50:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09507 for freebsd-current-outgoing; Thu, 26 Nov 1998 07:50:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ida.net (mail.ida.net [204.228.203.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09494 for ; Thu, 26 Nov 1998 07:50:10 -0800 (PST) (envelope-from muck@ida.net) Received: from falcon.hinterlands.com (tc-pt1-26.ida.net [208.141.181.35]) by mail.ida.net (8.8.7/8.8.7) with SMTP id IAA20120; Thu, 26 Nov 1998 08:50:52 -0700 (MST) Date: Thu, 26 Nov 1998 08:49:02 -0700 (MST) From: Mike X-Sender: muck@falcon.hinterlands.com To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: Page fault response from OSS In-Reply-To: <4.1.19981126012554.009266c0@206.25.93.69> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 26 Nov 1998, Forrest Aldrich wrote: > Here's the follow-up to the problem I reported earlier. Apparently it > is a FreeBSD kernel buglet. > > > Forrest > > >There are still problems with FreeBSD 3.0 inspite of the patch. > > > >There is nothing we can do until the kernel people really fix the bug. > >This patch is a temporary workaround. > > > >Best regards > >tech support > > Apologies if this got sent to the list twice. The first time I sent it, I used sendmail instead of my ISP's mail server, but since my domain does not resolve... How current are you? With a kernel cvsup'd on 25 Nov, I can use the oss drivers just fine. # cd /usr/local/lib/oss # ./soundon OSS/FreeBSD loading, address = f410b020 Open Sound System is licensed for evaluation purposes only. I'm listening to a Def Leppard cd while typing this email. I typed soundon immediately after booting up and logging on. FreeBSD falcon.hinterlands.com 3.0-CURRENT FreeBSD 3.0-CURRENT #4: Thu Nov 26 08:17:27 MST 1998 muck@falcon.hinterlands.com:/usr/src/sys/compile/POOR_TWISTED_ME i386 Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 08:58:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14347 for freebsd-current-outgoing; Thu, 26 Nov 1998 08:58:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oitunix.oit.umass.edu (nscs24p3.remote.umass.edu [128.119.179.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14342 for ; Thu, 26 Nov 1998 08:58:31 -0800 (PST) (envelope-from gp@oitunix.oit.umass.edu) Received: (from gp@localhost) by oitunix.oit.umass.edu (8.9.1/8.9.1) id LAA55021; Thu, 26 Nov 1998 11:58:35 -0500 (EST) (envelope-from gp) Message-ID: <19981126115834.A55000@oit.umass.edu> Date: Thu, 26 Nov 1998 11:58:34 -0500 From: Greg Pavelcak To: current@FreeBSD.ORG Cc: Alfred Perlstein Subject: Re: Xlib: unexpected async reply References: <19981125233541.A1094@oit.umass.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Alfred Perlstein on Wed, Nov 25, 1998 at 11:44:34PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 25, 1998 at 11:44:34PM -0500, Alfred Perlstein wrote: > You may want to download the ports collection and compile XFree86 from the > ports tree. > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's FreeBSD. > -- http://www.freebsd.org/ 3.0-current > Did that this morning, but the problem described below persists, except I no longer get any Xlib messsage. Maybe I have a Tcl/Tk problem, since other "fancy" windows, like gv work OK, and you can add cbb, which depends on wish4.2, to the list of programs that give me trouble. Greg > On Wed, 25 Nov 1998, Greg Pavelcak wrote: > > > I'm posting here because I run -current, but I'm not quite sure > > what information is relevant to my problem. > > > > I installed 3.0 plus X from the Walnut Creek CD-Rom; then > > immediately cvsup-ed and built world and elf-kernel (sources from > > 11/21). All this seemed to go well. I also installed fvwm2 as > > window manager. > > > > My problem is when I quit certain programs running in X --tkdesk, > > tkcvs, tkinfo for example--just about everything stops working. > > Specifically, although the mouse pointer still moves, neither > > keyboard shortcuts nor mouse clicks have any affect. Furthermore, > > focus does not follow the mouse. So, I quit X with > > ctl/alt/backspace and see the message: > > > > Xlib: unexpected async reply (sequence 0xe08) > > > > on the console (though the number changes). > > > > I seem to be able to open and close xterms without a problem. > > > > Any insight on this would be appreciated. > > > > Greg > > > > 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 Nov 26 09:23:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16223 for freebsd-current-outgoing; Thu, 26 Nov 1998 09:23:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16218 for ; Thu, 26 Nov 1998 09:23:51 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA03476; Fri, 27 Nov 1998 04:23:45 +1100 Date: Fri, 27 Nov 1998 04:23:45 +1100 From: Bruce Evans Message-Id: <199811261723.EAA03476@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, johan@granlund.nu Subject: Re: sio breakage Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Have someone commited something that i missed that breaks sio? >I have a HylaFAX that says that the modem appears to be wedget. sio is now missing a workaround for certain (16C450?) incompatible UARTs, and now honours TCSANOW. Previously it waited for output to drain out of the UART before changing the parameters, but tcsetattr(... TCSANOW) is supposed to change the parameters immediately. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 09:25:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16513 for freebsd-current-outgoing; Thu, 26 Nov 1998 09:25:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16508 for ; Thu, 26 Nov 1998 09:25:04 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Thu, 26 Nov 1998 17:23:26 -0000 Message-ID: From: Paul Richards To: "'Jesper Skriver'" , David Greenman Cc: current@FreeBSD.ORG Subject: RE: Random craches under heavy(?) disk activity Date: Thu, 26 Nov 1998 17:23:26 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Jesper Skriver [mailto:jesper@skriver.dk] > Sent: Thursday, November 26, 1998 10:09 AM > To: David Greenman > Cc: current@FreeBSD.ORG > Subject: Re: Random craches under heavy(?) disk activity > > > On Thu, Nov 26, 1998 at 01:07:10AM -0800, David Greenman wrote: > > >> This appears to be different and unrelated as well > and probably indicates > > >> a hardware problem. > > > > > >Have you got any idea which HW, I've got a ethernet card that logs > > >"Recieve CRC error" all the time, I'm working on getting > it replaced, > > >but as the security people here require static MAC addresses in the > > >routers, it's a but of a hassle to swap it ... sigh ... > > > > Memory, cache, CPU, or motherboard. > > I finally got the old lance ethernet replaced with a 3c905B card, and > now it hasn't crashed yet, even a "make buildworld" and > running X at the > same time hasn't crashed the box ... I always said logging those errors was a good idea :-) Paul Richards Ph.D. Originative Solutions Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 10:31:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21954 for freebsd-current-outgoing; Thu, 26 Nov 1998 10:31:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21949 for ; Thu, 26 Nov 1998 10:31:37 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forresta (forrie.ne.mediaone.net [24.128.73.118]) by spook.navinet.net (8.9.1/8.9.1) with SMTP id NAA64586 for ; Thu, 26 Nov 1998 13:32:29 -0500 (EST) Message-Id: <4.1.19981126132839.00926100@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 26 Nov 1998 13:31:22 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: ELF Kernels Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /etc/make.conf should be changed to specify that boot.conf should be in /boot, not / ... at least the loader complains about it. Also, it complained "boot bad format", which I presume was the boot.conf file, which stated "/boot/loader". Is the ELF Kernel still in an experimental stage? If not, why doesn't the system default to using an ELF kernel? Just curious... Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 10:32:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22110 for freebsd-current-outgoing; Thu, 26 Nov 1998 10:32:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22104 for ; Thu, 26 Nov 1998 10:32:53 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forresta (forrie.ne.mediaone.net [24.128.73.118]) by spook.navinet.net (8.9.1/8.9.1) with SMTP id NAA64590 for ; Thu, 26 Nov 1998 13:33:48 -0500 (EST) Message-Id: <4.1.19981126133134.00925100@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 26 Nov 1998 13:32:41 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Netscape45-communicator port broken Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This should probably be changed to BROKEN. It dumps core (and the makefile seems botched). This applies to FreeBSD-3.0-CURRENT build world as of last night. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 11:01:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24547 for freebsd-current-outgoing; Thu, 26 Nov 1998 11:01:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24537 for ; Thu, 26 Nov 1998 11:01:27 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id OAA02168; Thu, 26 Nov 1998 14:04:25 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 26 Nov 1998 14:04:25 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Greg Pavelcak cc: current@FreeBSD.ORG Subject: Re: Xlib: unexpected async reply In-Reply-To: <19981126115834.A55000@oit.umass.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 Try to recompile your programs against tcl/tk 8.1x it's much faster and has bugfixes. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Thu, 26 Nov 1998, Greg Pavelcak wrote: > On Wed, Nov 25, 1998 at 11:44:34PM -0500, Alfred Perlstein wrote: > > You may want to download the ports collection and compile XFree86 from the > > ports tree. > > > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > > -- There are operating systems, and then there's FreeBSD. > > -- http://www.freebsd.org/ 3.0-current > > > Did that this morning, but the problem described below persists, > except I no longer get any Xlib messsage. Maybe I have a Tcl/Tk > problem, since other "fancy" windows, like gv work OK, and you > can add cbb, which depends on wish4.2, to the list of programs > that give me trouble. > > Greg > > > > On Wed, 25 Nov 1998, Greg Pavelcak wrote: > > > > > I'm posting here because I run -current, but I'm not quite sure > > > what information is relevant to my problem. > > > > > > I installed 3.0 plus X from the Walnut Creek CD-Rom; then > > > immediately cvsup-ed and built world and elf-kernel (sources from > > > 11/21). All this seemed to go well. I also installed fvwm2 as > > > window manager. > > > > > > My problem is when I quit certain programs running in X --tkdesk, > > > tkcvs, tkinfo for example--just about everything stops working. > > > Specifically, although the mouse pointer still moves, neither > > > keyboard shortcuts nor mouse clicks have any affect. Furthermore, > > > focus does not follow the mouse. So, I quit X with > > > ctl/alt/backspace and see the message: > > > > > > Xlib: unexpected async reply (sequence 0xe08) > > > > > > on the console (though the number changes). > > > > > > I seem to be able to open and close xterms without a problem. > > > > > > Any insight on this would be appreciated. > > > > > > Greg > > > > > > 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 Nov 26 11:13:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25529 for freebsd-current-outgoing; Thu, 26 Nov 1998 11:13:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25522 for ; Thu, 26 Nov 1998 11:13:05 -0800 (PST) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t2o29p77.telia.com [194.236.214.197]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id UAA00667; Thu, 26 Nov 1998 20:12:53 +0100 Received: from pegasys (pegasys.granlund.nu [192.168.0.2]) by phoenix.granlund.nu (8.9.1/8.9.1) with SMTP id UAA00347; Thu, 26 Nov 1998 20:06:39 +0100 (CET) (envelope-from johan@phoenix.granlund.nu) Message-Id: <199811261906.UAA00347@phoenix.granlund.nu> From: "Johan Granlund" To: Bruce Evans , freebsd-current@FreeBSD.ORG Date: Thu, 26 Nov 1998 19:08:47 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: sio breakage In-reply-to: <199811261723.EAA03476@godzilla.zeta.org.au> X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Have someone commited something that i missed that breaks sio? > >I have a HylaFAX that says that the modem appears to be wedget. > l> sio is now missing a workaround for certain (16C450?) incompatible > UARTs, and now honours TCSANOW. Previously it waited for output > to drain out of the UART before changing the parameters, but > tcsetattr(... TCSANOW) is supposed to change the parameters > immediately. > Hmm The ports is reported as 16550A:s sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A This is the onboard serialports on a Intel Advanced/EV motherboard. The I/O controller is a NS PC87306 chip and is supposed to be 16C550 compatible. Is this controller broken? HylaFAX is compiled from ports OCT 19 and the system is all ELF including the kernel. The port used is cuaa1. /Johan > Bruce > ___________________________________________________________ Internet: johan@granlund.nu I don't even speak for myself To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 11:42:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27717 for freebsd-current-outgoing; Thu, 26 Nov 1998 11:42:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lionking.org (blacker-99.caltech.edu [131.215.86.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27710 for ; Thu, 26 Nov 1998 11:42:20 -0800 (PST) (envelope-from btman@ugcs.caltech.edu) Received: from localhost (btman@localhost) by lionking.org (8.9.1a/8.9.1) with ESMTP id LAA07390; Thu, 26 Nov 1998 11:42:08 -0800 (PST) X-Authentication-Warning: lionking.org: btman owned process doing -bs Date: Thu, 26 Nov 1998 11:42:08 -0800 (PST) From: Brian Tiemann X-Sender: btman@lionking.org To: Mike cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Page fault response from OSS 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, 26 Nov 1998, Mike wrote: > How current are you? With a kernel cvsup'd on 25 Nov, I can use the oss > drivers just fine. For what it's worth, I've been able to use OSS successfully ever since kern/8632 was closed (with the patch by Bruce Evans). Another bug, i386/8673, relates to the remaining crashes, though I haven't run across them yet. But as people have been saying, this has only been addressed with patches so far; this all seems to mask a more serious general problem with the vm architecture, according to the OSS developers. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 11:56:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28827 for freebsd-current-outgoing; Thu, 26 Nov 1998 11:56:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.aha.ru (ns1.aha.ru [195.2.80.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28822 for ; Thu, 26 Nov 1998 11:56:07 -0800 (PST) (envelope-from osa@etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by ns1.aha.ru (8.9.1/8.9.1/aha-r/0.04B) with ESMTP id WAA19491 for ; Thu, 26 Nov 1998 22:55:59 +0300 (MSK) Received: by sunny.aha.ru id WAA04047; (8.8.8/vak/1.9) Thu, 26 Nov 1998 22:55:18 +0300 (MSK) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma003975; Thu Nov 26 22:54:58 1998 Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by serv.etrust.ru (8.9.1/8.9.1) with ESMTP id WAA08167 for ; Thu, 26 Nov 1998 22:46:48 +0300 (MSK) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id WAA16444 for ; Thu, 26 Nov 1998 22:44:42 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Thu, 26 Nov 1998 22:44:42 +0300 (MSK) From: oZZ!!! To: current@FreeBSD.ORG Subject: SCOs Informix online on FreeBSD? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Does some1 use SCOs Informix online on FreeBSD? Rgdz, ïÓÏËÉÎ óÅÒÇÅÊ aka oZZ, osa@etrust.ru FreeBSD - äÁ ÐÒÅÂÕÄÅÔ Ó ÎÁÍÉ ÓÉÌÁ! http://www.freebsd.org.ru áÓÓÏÃÉÁÃÉÑ ÒÕÓÓËÏÑÚÙÞÎÙÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 13:36:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07197 for freebsd-current-outgoing; Thu, 26 Nov 1998 13:36:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA07192 for ; Thu, 26 Nov 1998 13:36:11 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zj94x-0001ac-00; Thu, 26 Nov 1998 14:35:59 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id OAA88116; Thu, 26 Nov 1998 14:35:02 -0700 (MST) Message-Id: <199811262135.OAA88116@harmony.village.org> To: Matthew Thyer Subject: Re: aha delaying patch works for genuine 1542B Cc: CURRENT@FreeBSD.ORG In-reply-to: Your message of "Thu, 26 Nov 1998 16:04:31 +1030." <365CE867.62F68C8A@dsto.defence.gov.au> References: <365CE867.62F68C8A@dsto.defence.gov.au> Date: Thu, 26 Nov 1998 14:35:01 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <365CE867.62F68C8A@dsto.defence.gov.au> Matthew Thyer writes: : The card in question is a genuine Adaptec 1542B and I really : need it to work as it contains my /usr/src !! Which revision? The 1542B that I have doesn't need this delay. The probe string will tell you the revision. : As Graham Menhennitt said: "Could somebody please commit this change" Been there, done that. Justin and I have been talking about a better way to deal with this problem than putting in a magic delay. There may be another round of patches for the folks with the problem 1542B cards to test. : fuzz: {1} diff /sys/dev/aha/aha.c.orig /sys/dev/aha/aha.c diff -u generally produces better results. Also, I have a better comment stating that a delay to 1000 works, but 10mS is very long in card time, but very short in probe time. There was a similar delay in the old driver in places, but I've not looked closely enough to know if this was one of the places or not. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 14:05:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09348 for freebsd-current-outgoing; Thu, 26 Nov 1998 14:05:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09330; Thu, 26 Nov 1998 14:05:20 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id XAA04180; Thu, 26 Nov 1998 23:05:00 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.8.5) id AAA01196; Fri, 27 Nov 1998 00:05:41 GMT Message-ID: <19981127000541.21781@breizh.prism.uvsq.fr> Date: Fri, 27 Nov 1998 00:05:41 +0000 From: Nicolas Souchu To: aw1@stade.co.uk Cc: current@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG Subject: Re: kernel make failure in smbus References: <199811222006.MAA00385@rah.star-gate.com> <199811222106.XAA00350@greenpeace.grondar.za> <19981124025011.A832@stade.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19981124025011.A832@stade.co.uk>; from Adrian Wontroba on Tue, Nov 24, 1998 at 02:50:11AM +0000 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 24, 1998 at 02:50:11AM +0000, Adrian Wontroba wrote: > >On Sun, Nov 22, 1998 at 11:06:46PM +0200, Mark Murray wrote: >> My card is not a Miro, and it is not NTSC. I believe this is unrelated >> to Doug's patches, which should go in. Shall I do the honours? > >Card detection has been iffy since the bktr driver was changed to use the >iic/smbus stuff - setting the hw.bt848.(card|tuner|reverse_mute) oids on >startup is the easy way of dealing with it. I thought it was solved when we returned to the previous check_for_i2c_devices() behaviour. What about trying the following patch which disables iic/smb support? Index: brooktree848.c =================================================================== RCS file: /home/ncvs/src/sys/pci/brooktree848.c,v retrieving revision 1.59 diff -u -r1.59 brooktree848.c --- brooktree848.c 1998/11/08 12:39:06 1.59 +++ brooktree848.c 1998/11/27 00:00:47 @@ -355,11 +355,15 @@ #include /* extensions to ioctl_meteor.h */ #include #include + +#ifdef IIC_SUPPORT #include #include #include #include "smbus_if.h" #include "iicbus_if.h" +#endif /* IIC_SUPPORT */ + #include static int bt848_card = -1; static int bt848_tuner = -1; @@ -1178,9 +1182,11 @@ fun = pci_conf_read(tag, 0x40); pci_conf_write(tag, 0x40, fun | 1); +#ifdef IIC_SUPPORT /* XXX call bt848_i2c dependent attach() routine */ if (bt848_i2c_attach(unit, bktr->base, &bktr->i2c_sc)) printf("bktr%d: i2c_attach: can't attach\n", unit); +#endif #ifdef BROOKTREE_IRQ /* from the configuration file */ old_irq = pci_conf_read(tag, PCI_INTERRUPT_REG); @@ -4169,7 +4175,7 @@ BT848_DATA_CTL_I2CSCL | \ BT848_DATA_CTL_I2CSDA) -#if defined(__FreeBSD__) +#if defined(__FreeBSD__) && defined(IIC_SUPPORT) /* * The hardware interface is actually SMB commands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 15:06:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13951 for freebsd-current-outgoing; Thu, 26 Nov 1998 15:06:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13938; Thu, 26 Nov 1998 15:06:04 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id BAA16030; Fri, 27 Nov 1998 01:04:25 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Fri, 27 Nov 1998 01:04:25 +0200 (EET) From: Adrian Penisoara To: Forrest Aldrich cc: FreeBSD ports Subject: Re: Netscape45-communicator port broken In-Reply-To: <4.1.19981126133134.00925100@206.25.93.69> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Thu, 26 Nov 1998, Forrest Aldrich wrote: > This should probably be changed to BROKEN. It dumps core > (and the makefile seems botched). This applies to FreeBSD-3.0-CURRENT > build world as of last night. Could you please give some more details ? I've proposed the patches but it seems that the committer changed a bit the Makefile. I'll be testing the CVS version of the port as soon as I can. > > PS: Let's move it to freebsd-ports... Thanks, Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 15:29:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16008 for freebsd-current-outgoing; Thu, 26 Nov 1998 15:29:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piston.ecp.fr (piston.ecp.fr [138.195.33.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16003 for ; Thu, 26 Nov 1998 15:29:31 -0800 (PST) (envelope-from dae@via.ecp.fr) Received: from caracal.cti.ecp.fr (root@caracal.cti.ecp.fr [138.195.33.4]) by piston.ecp.fr (8.8.7/jtpda-5.3) with ESMTP id AAA02027 for ; Fri, 27 Nov 1998 00:29:24 +0100 (MET) Received: from via.ecp.fr (dae.via.ecp.fr [138.195.136.50]) by caracal.cti.ecp.fr (8.8.8/jtpda-5.2) with ESMTP id AAA02467 for ; Fri, 27 Nov 1998 00:29:23 +0100 (MET) Message-ID: <365DE74E.3711874C@via.ecp.fr> Date: Fri, 27 Nov 1998 00:42:06 +0100 From: Andres Krapf X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: top weirdness Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG a fresh cvsup as of 25/11/98 gave me a few weird things: the first thing i noticed is that snes9x didn't work well, the sound was comming out the same way it does when i try to play mp3s under heavy load. it had been working fine for a month with a 24/10 cvsup. then here is a top output: [snip] CPU states: 78.2% user, 0.0% nice, 20.6% system, 1.2% interrupt, 0.0% idle Mem: 55M Active, 16M Inact, 17M Wired, 5416K Cache, 8339K Buf, 572K Free Swap: 128M Total, 320K Used, 128M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 625 dae 94 0 9432K 7412K RUN 7:00 113.04% 113.04% snes9x [snip] ^^^^^^^^^^^^^^^ 27/11 0:28 ~% uname -a FreeBSD dae.via.ecp.fr 3.0-CURRENT FreeBSD 3.0-CURRENT #4: Thu Nov 26 16:31:52 CET 1998 root@dae.via.ecp.fr:/usr/home/ftp/pub/src/sys/compile/KERNEL i386 I probably missed something during my last cvsup/make world, but i can't find what it is ... by the way, i'm using voxware drivers, could it be related ? (haven't had time to try with luigi's drivers yet) -- Krapf Andres, Engineering student at the Ecole Centrale Paris IRCnet: X-dae -- dae@via.ecp.fr -=- FreeBSD:The Power To Serve -=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 15:53:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18186 for freebsd-current-outgoing; Thu, 26 Nov 1998 15:53:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18178 for ; Thu, 26 Nov 1998 15:53:04 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA23823; Fri, 27 Nov 1998 10:22:45 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA31504; Fri, 27 Nov 1998 10:22:45 +1030 (CST) Message-ID: <19981127102245.Y67961@freebie.lemis.com> Date: Fri, 27 Nov 1998 10:22:45 +1030 From: Greg Lehey To: Andres Krapf , "current@FreeBSD.ORG" Subject: Re: top weirdness References: <365DE74E.3711874C@via.ecp.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <365DE74E.3711874C@via.ecp.fr>; from Andres Krapf on Fri, Nov 27, 1998 at 12:42:06AM +0100 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 Friday, 27 November 1998 at 0:42:06 +0100, Andres Krapf wrote: > a fresh cvsup as of 25/11/98 gave me a few weird things: > the first thing i noticed is that snes9x didn't work well, the sound was > comming out the same way it does when i try to play mp3s under heavy > load. it had been working fine for a month with a 24/10 cvsup. > then here is a top output: > > [snip] > CPU states: 78.2% user, 0.0% nice, 20.6% system, 1.2% interrupt, 0.0% > idle > Mem: 55M Active, 16M Inact, 17M Wired, 5416K Cache, 8339K Buf, 572K Free > Swap: 128M Total, 320K Used, 128M Free > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 625 dae 94 0 9432K 7412K RUN 7:00 113.04% 113.04% > snes9x > [snip] ^^^^^^^^^^^^^^^ Bruce has just committed some fixes which appear to address this problem. It seems that some kernel counters scaled incorrectly. Try resupping and rebuilding, then see if the problem recurs. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 16:31:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23490 for freebsd-current-outgoing; Thu, 26 Nov 1998 16:31:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23485 for ; Thu, 26 Nov 1998 16:31:09 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (andyf@localhost) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id LAA23147; Fri, 27 Nov 1998 11:30:38 +1100 (EST) X-Authentication-Warning: backup.zippynet.iol.net.au: andyf owned process doing -bs Date: Fri, 27 Nov 1998 11:30:38 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: Bruce Evans cc: freebsd-current@FreeBSD.ORG, johan@granlund.nu Subject: Re: sio breakage In-Reply-To: <199811261723.EAA03476@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >Have someone commited something that i missed that breaks sio? > >I have a HylaFAX that says that the modem appears to be wedget. > > sio is now missing a workaround for certain (16C450?) incompatible > UARTs, and now honours TCSANOW. Previously it waited for output > to drain out of the UART before changing the parameters, but > tcsetattr(... TCSANOW) is supposed to change the parameters > immediately. > > Bruce > I have one serial port with a mouse attached. sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16450 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 I see these types of messages (when running XF86 3.3.2): Nov 25 23:10:11 zippy /kernel: sio0: 9 more tty-level buffer overflows (total 1260) Nov 25 23:10:12 zippy /kernel: sio0: 4 more tty-level buffer overflows (total 1264) Nov 25 23:10:15 zippy /kernel: sio0: 20 more tty-level buffer overflows (total 1284) Nov 26 13:36:55 zippy /kernel: sio0: 1 more silo overflow (total 4) Nov 26 13:39:18 zippy /kernel: sio0: 1 more silo overflow (total 5) Nov 26 13:39:19 zippy /kernel: sio0: 1 more silo overflow (total 6) Nov 26 13:39:20 zippy /kernel: sio0: 1 more silo overflow (total 7) Never had them before. # uname -a FreeBSD zippy.zippynet.iol.net.au 3.0-CURRENT FreeBSD 3.0-CURRENT #4: Sat Nov 14 23:54:15 EST 1998 root@zippy.zippynet.iol.net.au:/usr/src-3.0-RELEASE/sys/compile/ZIPPY-SMP i386 -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 17:39:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28630 for freebsd-current-outgoing; Thu, 26 Nov 1998 17:39:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28625 for ; Thu, 26 Nov 1998 17:39:53 -0800 (PST) (envelope-from leifn@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id CAA00901 for ; Fri, 27 Nov 1998 02:39:41 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Fri, 27 Nov 1998 02:39:40 +0100 (CET) From: Leif Neland To: freebsd-current@FreeBSD.ORG Subject: user-ppp broken since a few days ago? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I usually run cvsup and make world every night (don't want the poor machine to get bored...) A few mornings ago I couldn't connect anymore with ppp. Luckily I got the idea of using /stand/ppp, and it works. -r-xr-xr-x 19 root bin 1171456 24 Jul 06:59 /stand/ppp -r-sr-xr-- 1 root network 193212 26 Nov 04:54 /usr/sbin/ppp Logfile of current ppp: Nov 27 02:24:00 gina ppp[222]: tun0: Phase: deflink: dial -> login Nov 27 02:24:00 gina ppp[222]: tun0: Phase: deflink: login -> lcp Nov 27 02:24:00 gina ppp[222]: tun0: LCP: FSM: Using "deflink" as a transport Nov 27 02:24:00 gina ppp[222]: tun0: LCP: deflink: State change Initial --> Closed Nov 27 02:24:00 gina ppp[222]: tun0: LCP: deflink: State change Closed --> Stopped Nov 27 02:24:02 gina ppp[222]: tun0: Phase: Unknown protocol 0x0801 (unrecognised protocol) Nov 27 02:24:02 gina ppp[222]: tun0: LCP: deflink: SendProtocolRej(1) state = Stopped Nov 27 02:24:03 gina ppp[222]: tun0: LCP: deflink: LayerStart Nov 27 02:24:03 gina ppp[222]: tun0: LCP: deflink: SendConfigReq(1) state = Stopped Nov 27 02:24:03 gina ppp[222]: tun0: LCP: ACFCOMP[2] Nov 27 02:24:03 gina ppp[222]: tun0: LCP: PROTOCOMP[2] Nov 27 02:24:03 gina ppp[222]: tun0: LCP: ACCMAP[6] 0x00000000 Nov 27 02:24:03 gina ppp[222]: tun0: LCP: MRU[4] 1500 Nov 27 02:24:03 gina ppp[222]: tun0: LCP: MAGICNUM[6] 0x71f4a124 Nov 27 02:24:03 gina ppp[222]: tun0: LCP: deflink: State change Stopped --> Req-Sent Nov 27 02:24:05 gina ppp[222]: tun0: Phase: deflink: Carrier lost Nov 27 02:24:05 gina ppp[222]: tun0: LCP: deflink: State change Req-Sent --> Starting Nov 27 02:24:05 gina ppp[222]: tun0: LCP: deflink: LayerFinish Nov 27 02:24:05 gina ppp[222]: tun0: LCP: deflink: State change Starting --> Initial Nov 27 02:24:05 gina ppp[222]: tun0: Phase: deflink: Disconnected! Nov 27 02:24:05 gina ppp[222]: tun0: Phase: deflink: lcp -> hangup Nov 27 02:24:05 gina ppp[222]: tun0: Phase: deflink: Connect time: 9 secs: 23 octets in, 74 octets out Nov 27 02:24:05 gina ppp[222]: tun0: Phase: total 10 bytes/sec, peak 19 bytes/sec on Fri Nov 27 02:24:05 1998 Nov 27 02:24:05 gina ppp[222]: tun0: Phase: deflink: hangup -> closed Nov 27 02:24:05 gina ppp[222]: tun0: Phase: bundle: Dead /stand/ppp: Nov 27 02:26:07 gina ppp[560]: tun0: Connect: CONNECT Nov 27 02:26:07 gina ppp[560]: tun0: IPCP: Using trigger address 0.0.0.0 Nov 27 02:26:07 gina ppp[560]: tun0: LCP: State change Initial --> Closed Nov 27 02:26:07 gina ppp[560]: tun0: LCP: State change Closed --> Stopped Nov 27 02:26:09 gina ppp[560]: tun0: LCP: LcpSendConfigReq Nov 27 02:26:09 gina ppp[560]: tun0: LCP: ACFCOMP[2] Nov 27 02:26:09 gina ppp[560]: tun0: LCP: PROTOCOMP[2] Nov 27 02:26:09 gina ppp[560]: tun0: LCP: ACCMAP[6] 0x00000000 Nov 27 02:26:09 gina ppp[560]: tun0: LCP: MRU[4] 1500 Nov 27 02:26:09 gina ppp[560]: tun0: LCP: MAGICNUM[6] 0x1ddb61c0 Nov 27 02:26:09 gina ppp[560]: tun0: LCP: State change Stopped --> Req-Sent Nov 27 02:26:09 gina ppp[560]: tun0: LCP: Received Configure Reject (1) state = Req-Sent (6) Nov 27 02:26:09 gina ppp[560]: tun0: LCP: RecvConfigRej. Nov 27 02:26:09 gina ppp[560]: tun0: LCP: PROTOCOMP[2] Nov 27 02:26:09 gina ppp[560]: tun0: LCP: ACFCOMP[2] Nov 27 02:26:09 gina ppp[560]: tun0: LCP: LcpSendConfigReq Nov 27 02:26:09 gina ppp[560]: tun0: LCP: ACCMAP[6] 0x00000000 Nov 27 02:26:09 gina ppp[560]: tun0: LCP: MRU[4] 1500 Nov 27 02:26:09 gina ppp[560]: tun0: LCP: MAGICNUM[6] 0x1ddb61c0 Nov 27 02:26:10 gina ppp[560]: tun0: LCP: Received Configure Ack (2) state = Req-Sent (6) Nov 27 02:26:10 gina ppp[560]: tun0: LCP: State change Req-Sent --> Ack-Rcvd Nov 27 02:26:10 gina ppp[560]: tun0: LCP: Received Configure Request (1) state = Ack-Rcvd (7) Nov 27 02:26:10 gina ppp[560]: tun0: LCP: ACCMAP[6] 0x00000000 Nov 27 02:26:10 gina ppp[560]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Nov 27 02:26:10 gina ppp[560]: tun0: LCP: MAGICNUM[6] 0x0267d36b Nov 27 02:26:10 gina ppp[560]: tun0: LCP: SendConfigAck(Ack-Rcvd) Nov 27 02:26:10 gina ppp[560]: tun0: LCP: ACCMAP[6] 0x00000000 Nov 27 02:26:10 gina ppp[560]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Nov 27 02:26:10 gina ppp[560]: tun0: LCP: MAGICNUM[6] 0x0267d36b Nov 27 02:26:10 gina ppp[560]: tun0: LCP: State change Ack-Rcvd --> Opened Nov 27 02:26:10 gina ppp[560]: tun0: LCP: LcpLayerUp Nov 27 02:26:10 gina ppp[560]: tun0: Phase: NewPhase: Authenticate Nov 27 02:26:10 gina ppp[560]: tun0: Phase: his = PAP, mine = none Nov 27 02:26:10 gina ppp[560]: tun0: Phase: PAP: idk70486 Nov 27 02:26:10 gina ppp[560]: tun0: Phase: PapInput: ACK Nov 27 02:26:10 gina ppp[560]: tun0: Phase: Received PAP_ACK (Login Succeeded) Nov 27 02:26:10 gina ppp[560]: tun0: Phase: NewPhase: Network Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: State change Initial --> Closed Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPCP Up event!! Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IpcpSendConfigReq Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPADDR[6] 0.0.0.0 Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: COMPPROTO[6] 16 VJ slots with slot compres Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: State change Closed --> Req-Sent Nov 27 02:26:10 gina ppp[560]: tun0: CCP: State change Initial --> Closed Nov 27 02:26:10 gina ppp[560]: tun0: CCP: CCP Up event!! Nov 27 02:26:10 gina ppp[560]: tun0: CCP: CcpSendConfigReq Nov 27 02:26:10 gina ppp[560]: tun0: CCP: DEFLATE[4] win 15 Nov 27 02:26:10 gina ppp[560]: tun0: CCP: PRED1[2] Nov 27 02:26:10 gina ppp[560]: tun0: CCP: State change Closed --> Req-Sent Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: Received Configure Request (1) state = Req-Sent (6) Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: COMPPROTO[6] 16 VJ slots without slot compression Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPADDR[6] 194.19.140.21 Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: SendConfigAck(Req-Sent) Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: COMPPROTO[6] 16 VJ slots without slot compression Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPADDR[6] 194.19.140.21 Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: State change Req-Sent --> Ack-Sent Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: Received Configure Nak (1) state = Ack-Sent (8) Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPADDR[6] 194.255.12.232 Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPADDR[6] changing address: 0.0.0.0 --> 194.255.12.232 Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IpcpSendConfigReq Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IPADDR[6] 194.255.12.232 Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: COMPPROTO[6] 16 VJ slots with slot compres Nov 27 02:26:10 gina ppp[560]: tun0: LCP: Received Protocol Reject (2) state = Opened (9) Nov 27 02:26:10 gina ppp[560]: tun0: LCP: -- Protocol (80fd) was rejected. Nov 27 02:26:10 gina ppp[560]: tun0: CCP: CcpLayerFinish. Nov 27 02:26:10 gina ppp[560]: tun0: CCP: State change Req-Sent --> Stopped Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: Received Configure Ack (2) state = Ack-Sent (8) Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: State change Ack-Sent --> Opened Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: IpcpLayerUp(9). Nov 27 02:26:10 gina ppp[560]: tun0: IPCP: myaddr = 194.255.12.232 hisaddr = 194.19.140.21 Nov 27 02:26:10 gina ppp[560]: tun0: LCP: OsLinkup: 194.19.140.21 What's up? Why only me? Or are the others who are hit by this unable to get connected at all and tell us? :-) Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 19:09:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04561 for freebsd-current-outgoing; Thu, 26 Nov 1998 19:09:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04554 for ; Thu, 26 Nov 1998 19:09:29 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA13097; Fri, 27 Nov 1998 14:09:20 +1100 Date: Fri, 27 Nov 1998 14:09:20 +1100 From: Bruce Evans Message-Id: <199811270309.OAA13097@godzilla.zeta.org.au> To: bde@zeta.org.au, freebsd-current@FreeBSD.ORG, johan@granlund.nu Subject: Re: sio breakage Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >This is the onboard serialports on a Intel Advanced/EV motherboard. The >I/O controller is a NS PC87306 chip and is supposed to be 16C550 >compatible. >Is this controller broken? Don't know. >HylaFAX is compiled from ports OCT 19 and the system is all ELF >including the kernel. The port used is cuaa1. Is HylaFAX broken? Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 19:27:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05930 for freebsd-current-outgoing; Thu, 26 Nov 1998 19:27:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05925 for ; Thu, 26 Nov 1998 19:27:54 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA14836; Fri, 27 Nov 1998 14:27:43 +1100 Date: Fri, 27 Nov 1998 14:27:43 +1100 From: Bruce Evans Message-Id: <199811270327.OAA14836@godzilla.zeta.org.au> To: andyf@speednet.com.au, bde@zeta.org.au Subject: Re: sio breakage Cc: freebsd-current@FreeBSD.ORG, johan@granlund.nu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have one serial port with a mouse attached. > >sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa >sio0: type 16450 >sio1: configured irq 3 not in bitmap of probed irqs 0 >sio1 not found at 0x2f8 > >I see these types of messages (when running XF86 3.3.2): > >Nov 25 23:10:11 zippy /kernel: sio0: 9 more tty-level buffer overflows (total 1260) >Nov 25 23:10:12 zippy /kernel: sio0: 4 more tty-level buffer overflows (total 1264) >Nov 25 23:10:15 zippy /kernel: sio0: 20 more tty-level buffer overflows (total 1284) >Nov 26 13:36:55 zippy /kernel: sio0: 1 more silo overflow (total 4) >Nov 26 13:39:18 zippy /kernel: sio0: 1 more silo overflow (total 5) >Nov 26 13:39:19 zippy /kernel: sio0: 1 more silo overflow (total 6) >Nov 26 13:39:20 zippy /kernel: sio0: 1 more silo overflow (total 7) > >Never had them before. Fix the misconfiguration of sio1 and try again. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 26 23:14:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19144 for freebsd-current-outgoing; Thu, 26 Nov 1998 23:14:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19126 for ; Thu, 26 Nov 1998 23:14:33 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (woof.lan.Awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id HAA28011; Fri, 27 Nov 1998 07:13:40 GMT (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id HAA41019; Fri, 27 Nov 1998 07:13:40 GMT (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199811270713.HAA41019@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Leif Neland cc: freebsd-current@FreeBSD.ORG Subject: Re: user-ppp broken since a few days ago? In-reply-to: Your message of "Fri, 27 Nov 1998 02:39:40 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 1998 07:13:39 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, What happens if you ``set openmode active 2'' ? Also, you may want to enable async logging to see what that initial data is - 0801 doesn't make much sense (is this consistent?). > I usually run cvsup and make world every night (don't want the poor > machine to get bored...) > > A few mornings ago I couldn't connect anymore with ppp. > Luckily I got the idea of using /stand/ppp, and it works. > > -r-xr-xr-x 19 root bin 1171456 24 Jul 06:59 /stand/ppp > -r-sr-xr-- 1 root network 193212 26 Nov 04:54 /usr/sbin/ppp > > Logfile of current ppp: > Nov 27 02:24:00 gina ppp[222]: tun0: Phase: deflink: dial -> login > Nov 27 02:24:00 gina ppp[222]: tun0: Phase: deflink: login -> lcp > Nov 27 02:24:00 gina ppp[222]: tun0: LCP: FSM: Using "deflink" as a transport > Nov 27 02:24:00 gina ppp[222]: tun0: LCP: deflink: State change Initial --> Closed > Nov 27 02:24:00 gina ppp[222]: tun0: LCP: deflink: State change Closed --> Stopped > Nov 27 02:24:02 gina ppp[222]: tun0: Phase: Unknown protocol 0x0801 (unrecognised protocol) > Nov 27 02:24:02 gina ppp[222]: tun0: LCP: deflink: SendProtocolRej(1) state = Stopped > Nov 27 02:24:03 gina ppp[222]: tun0: LCP: deflink: LayerStart > Nov 27 02:24:03 gina ppp[222]: tun0: LCP: deflink: SendConfigReq(1) state = Stopped > Nov 27 02:24:03 gina ppp[222]: tun0: LCP: ACFCOMP[2] > Nov 27 02:24:03 gina ppp[222]: tun0: LCP: PROTOCOMP[2] > Nov 27 02:24:03 gina ppp[222]: tun0: LCP: ACCMAP[6] 0x00000000 > Nov 27 02:24:03 gina ppp[222]: tun0: LCP: MRU[4] 1500 > Nov 27 02:24:03 gina ppp[222]: tun0: LCP: MAGICNUM[6] 0x71f4a124 > Nov 27 02:24:03 gina ppp[222]: tun0: LCP: deflink: State change Stopped --> Req-Sent > Nov 27 02:24:05 gina ppp[222]: tun0: Phase: deflink: Carrier lost [.....] > What's up? Why only me? Or are the others who are hit by this unable to > get connected at all and tell us? :-) > > Leif -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 00:28:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25098 for freebsd-current-outgoing; Fri, 27 Nov 1998 00:28:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25080; Fri, 27 Nov 1998 00:28:33 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id JAA13976; Fri, 27 Nov 1998 09:28:32 +0100 (MET) Date: Fri, 27 Nov 1998 09:28:18 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: freebsd-current@FreeBSD.ORG cc: FreeBSD hackers mailing list Subject: USB support Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG USB support has been committed to FreeBSD Current. Feel free to switch it on (by uncommenting the last block in GENERIC) and report success or failure. Supported are mice, keyboards, generic devices (have not seen any company selling those, but we support them already!). Mice actually do something, keyboards and generic devices only give you silly output. BEWARE: This is preliminary. Do _not_ leave a USB device attached while running anything operational leaving the USB stack compiled in is already dangerous, although I have not seen big problems on my laptop yet. With Easter coming up, I've left a number of bugs in there. So let me know if you find one! The debugging output is bad, and we are going to solve that, to make it more selective, but for now, 'a lot' is the only setting for it. Keep me informed: n_hibma@www.etla.net Cheers, Nick P.S.: Mouse support, the road to success: (make kernel with ums in there and reboot) (start the usbd daemon, reprobing the bus once in while) usbd (or cd /usr/src/usr.sbin/usbd; make; ./usbd) (plug in mouse) mknod /dev/ums0 c 138 0 moused -p /dev/ums0 The major number might change in the future. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 00:38:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25730 for freebsd-current-outgoing; Fri, 27 Nov 1998 00:38:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles305.castles.com [208.214.167.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25725 for ; Fri, 27 Nov 1998 00:38:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA00739; Fri, 27 Nov 1998 00:36:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811270836.AAA00739@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: ELF Kernels In-reply-to: Your message of "Thu, 26 Nov 1998 13:31:22 EST." <4.1.19981126132839.00926100@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 1998 00:36:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /etc/make.conf should be changed to specify that boot.conf > should be in /boot, not / ... at least the loader complains about it. The only error in make.conf is that it says that the bootloader startup script is 'loader.conf' when in fact it's still called 'boot.conf'. > Also, it complained "boot bad format", which I presume was the > boot.conf file, which stated "/boot/loader". There is no such error string in any of the boot components that I'm able to find. Could you please indicate at which stage in the boot phase the message was emitted, and the exact message including punctuation, etc.? > Is the ELF Kernel still in an experimental stage? If not, why doesn't > the system default to using an ELF kernel? Just curious... ELF kernels are reliable but not the default yet. We're staying with a.out until the issues related to migration from LKMs are resolved and the KLD design is stable. There's probably one more iteration of this to go. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 02:09:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04308 for freebsd-current-outgoing; Fri, 27 Nov 1998 02:09:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04303 for ; Fri, 27 Nov 1998 02:09:49 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id LAA19904; Fri, 27 Nov 1998 11:13:53 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 27 Nov 1998 11:13:53 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: Christopher Hall , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <199811260513.VAA00592@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 25 Nov 1998, Mike Smith wrote: > > On Wed, 25 Nov 1998, Mike Smith wrote: > > > > > > > > > > Let me add yet another question to this: is there any way to boot FreeBSD > > > > from DOS partition, using /boot/loader? > > > > > > It's not generally possible to boot FreeBSD once DOS has started; > > > modern DOS versions corrupt the BIOS vectors in a fashion that makes it > > > impossible to obtain system information. > > > > I said: "is it possible to start from _DOS_ _partition_". Not "from under > > running DOS"... see the difference? > > I didn't, no. Yes, it's possible; you can load the kernel and then You mean: it's possible with current boot1/boot2 to load kernel from DOS partition? How? Or, are you saying that /boot/loader is able to do that? Then again, how? Thus far all my attempts at using something other than FreeBSD partition for $currdev result in nice System halted message. BTW. Issuing 'set' with no args should behave as 'show' IMHO, instead of 'System halted'... > either change $currdev or set $rootdev to the 'real' root filesystem. > > ($rootdev was being bogusly ignored until recently, so you will want to > be up to date) I am (sources as of yesterday). While I'm at it: I think the built-in commands of /boot/loader should leave their result on Forth stack. Otherwise it's really hard to test if they were successfull. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | 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 Fri Nov 27 02:41:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07183 for freebsd-current-outgoing; Fri, 27 Nov 1998 02:41:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA07173 for ; Fri, 27 Nov 1998 02:41:18 -0800 (PST) (envelope-from nordwick@scam.XCF.Berkeley.EDU) Message-Id: <199811271041.CAA07173@hub.freebsd.org> Received: (qmail 6049 invoked by uid 27268); 27 Nov 1998 10:42:44 -0000 Received: from localhost (HELO scam.XCF.Berkeley.EDU) (sendmail-bs@127.0.0.1) by localhost with SMTP; 27 Nov 1998 10:42:44 -0000 To: freebsd-current@FreeBSD.ORG Subject: Strange tagged openings error msg MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6046.912163363.1@scam.XCF.Berkeley.EDU> Date: Fri, 27 Nov 1998 02:42:44 -0800 From: "Jay Nordwick" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just installed a snapshot dated around November 20 and I just saw this message pop up duing some heavy disk operation: Nov 27 01:36:25 beastie /kernel: (da0:ahc0:0:0:0): tagged openings now 64 Nov 27 01:36:25 beastie /kernel: (da0:ahc0:0:0:0): tagged openings now 64 (yes, repeated) I have an AIC7880 onboard SCSI chip and a pair of IBM Barracuda drives. Softupdates were not running at the time. I was rm'ing /usr/ports so it was some heavy disk spinning it sounded like. There didn't appear to be any system instabilites. What does this error message mean? Is there a problem? thanks, jay -- 4.4 > 98 http://www.xcf.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 03:18:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09346 for freebsd-current-outgoing; Fri, 27 Nov 1998 03:18:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09341 for ; Fri, 27 Nov 1998 03:18:48 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id NAA03397 for ; Fri, 27 Nov 1998 13:18:39 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id NAA04955 for freebsd-current@FreeBSD.ORG; Fri, 27 Nov 1998 13:18:41 +0200 (EET) (envelope-from vallo) Message-ID: <19981127131841.A4601@matti.ee> Date: Fri, 27 Nov 1998 13:18:41 +0200 From: Vallo Kallaste To: freebsd-current@FreeBSD.ORG Subject: Re: So, how long until 3.0-Stable? Reply-To: vallo@matti.ee References: <199811251857.KAA00369@rah.star-gate.com> <19981126002304.A11137@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981126002304.A11137@keltia.freenix.fr>; from Ollivier Robert on Thu, Nov 26, 1998 at 12:23:04AM +0100 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert wrote: > According to Amancio Hasty: > > I haven't had any crashes over here in a while and I am running with > > softupdates enabled. > > To add to this, I'm using SMP + softupdates on my 2x PPro/200 and it > survived a "make world" w/o a hitch. > > 4635.42 real 4505.99 user 2548.80 sys > > 3.0-CURRENT, Intel Providence mb, 64 MB RAM. I have survived 6 buildworlds recently with -j8 on softupdates enabled filesystems. Also I have vfs.ffs.doreallocblks turned on. sysctl -a | grep ffs vfs.ffs.doreallocblks: 1 vfs.ffs.doasyncfree: 1 FreeBSD 3.0-CURRENT #0: Sun Nov 22 22:44:48 EET 1998 root@myhakas.matti.ee:/usr/src/sys/compile/Myhakas_SMP Timecounter "i8254" frequency 1193057 Hz CPU: Pentium II (quarter-micron) (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 134217728 (131072K bytes) avail memory = 127627264 (124636K bytes) Programming 24 pins in IOAPIC #0 Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 03:39:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA10669 for freebsd-current-outgoing; Fri, 27 Nov 1998 03:39:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA10659 for ; Fri, 27 Nov 1998 03:39:43 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id LAA05320; Fri, 27 Nov 1998 11:39:33 GMT Message-ID: <365E8F74.55E1A115@tdx.co.uk> Date: Fri, 27 Nov 1998 11:39:32 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Jay Nordwick CC: freebsd-current@FreeBSD.ORG Subject: Re: Strange tagged openings error msg References: <199811271041.CAA07173@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jay Nordwick wrote: > I just installed a snapshot dated around November 20 and I just saw this > message pop up duing some heavy disk operation: > > Nov 27 01:36:25 beastie /kernel: (da0:ahc0:0:0:0): tagged openings now 64 > Nov 27 01:36:25 beastie /kernel: (da0:ahc0:0:0:0): tagged openings now 64 > > (yes, repeated) I have an AIC7880 onboard SCSI chip and a pair of IBM > Barracuda drives. Softupdates were not running at the time. I was rm'ing > /usr/ports so it was some heavy disk spinning it sounded like. There > didn't appear to be any system instabilites. > > What does this error message mean? Is there a problem? > thanks, Hmmm... Barracuda = Seagate no? - Anyway, it's not an error - it's informational, it tells you how many commands the hard drive can have queued at any one time... e.g. on my system I get: caladan /kernel: (da7:ahc1:0:0:0): tagged openings now 15 When my rather ageing Quantum ProDrive gets hammered... It's harmless, but informative... Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 04:40:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA16879 for freebsd-current-outgoing; Fri, 27 Nov 1998 04:40:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.mishkei.org.il ([62.0.64.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA16874 for ; Fri, 27 Nov 1998 04:40:49 -0800 (PST) (envelope-from rom_glsa@ein-hashofet.co.il) Received: from ein-hashofet.co.il (host51-68.mishkei.org.il [62.0.68.51]) by mail.mishkei.org.il (8.8.5/8.8.5) with ESMTP id PAA14428 for ; Fri, 27 Nov 1998 15:39:46 +0200 Message-ID: <365EB9DD.56FEF540@ein-hashofet.co.il> Date: Fri, 27 Nov 1998 14:40:29 +0000 From: Gilad Rom X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: RE: Random craches under heavy(?) disk activity Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, First of all, Sorry, Forgot about the "dont complain if you overclock" rule. Guess I shouldnt be complaining. Second of all, The Rebooting problem seems to be gone, finally: FreeBSD 3.0-CURRENT #0: Mon Nov 23 18:52:37 GMT 1998 uptime: 2:36PM up 3 days, 19:43 -- Gilad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 04:49:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17635 for freebsd-current-outgoing; Fri, 27 Nov 1998 04:49:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17619; Fri, 27 Nov 1998 04:49:20 -0800 (PST) (envelope-from aw1@stade.co.uk) Received: (from aw1@localhost) by stade.demon.co.uk (8.9.1/8.9.1) id HAA05694; Fri, 27 Nov 1998 07:32:13 GMT (envelope-from aw1) Message-ID: <19981127073212.B99436@stade.co.uk> Date: Fri, 27 Nov 1998 07:32:12 +0000 From: Adrian Wontroba To: Nicolas Souchu Cc: current@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG Subject: Re: kernel make failure in smbus Reply-To: aw1@stade.co.uk References: <199811222006.MAA00385@rah.star-gate.com> <199811222106.XAA00350@greenpeace.grondar.za> <19981124025011.A832@stade.co.uk> <19981127000541.21781@breizh.prism.uvsq.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981127000541.21781@breizh.prism.uvsq.fr>; from Nicolas Souchu on Fri, Nov 27, 1998 at 12:05:41AM +0000 Organization: Stade Computers Ltd, UK X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 27, 1998 at 12:05:41AM +0000, Nicolas Souchu wrote: > I thought it was solved when we returned to the previous > check_for_i2c_devices() behaviour. What about trying the following patch > which disables iic/smb support? I'll try out the patch over the weekend. Thanks. -- Adrian Wontroba, Stade Computers Limited. phone: (+44) 121 681 6677 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 06:08:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22825 for freebsd-current-outgoing; Fri, 27 Nov 1998 06:08:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22820 for ; Fri, 27 Nov 1998 06:08:15 -0800 (PST) (envelope-from werner@btp1da.phy.uni-bayreuth.de) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id PAA06437; Fri, 27 Nov 1998 15:07:11 +0100 (MET) 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: <365C66AF.7E9A42AB@webwizard.org.mx> Date: Fri, 27 Nov 1998 15:07:11 +0100 (MET) Organization: University of bayreuth From: Werner Griessl To: Edwin Culp Subject: Re: IBM Netfinity 3500 Cc: FreeBSD-Current@FreeBSD.ORG, jabc@webwizard.org.mx, eculp@MexComUSA.net, Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Nov-98 Edwin Culp wrote: > Mike Smith wrote: > >> I don't know. You might want to talk to David Greenman about this one; >> he might have some ideas. You might also want to send the 'mptable' >> output to the SMP folks; they may have some ideas about interrupt >> routing that might shed some light on the situation. >> >> If you have time to tinker with the machine at all, it'd be very >> educational to add some debugging to the PCI interrupt handling code to >> see what's actually going on. A good start would be the interrupt >> handler for the 'fxp' device. >> > > I don't have a better idea. I´ll give it a try. Thanks again. > > ed > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- Have the same problem here with a Compaq-AP200 with any fxp-card. The AP400 is working even with the buildin fxp. But 2.2.7-Stable is working on both, so there must be a difference between Stable and Current in the fxp-driver. Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 07:54:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02561 for freebsd-current-outgoing; Fri, 27 Nov 1998 07:54:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from easeway.com (ns1.easeway.com [209.69.71.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02555 for ; Fri, 27 Nov 1998 07:54:07 -0800 (PST) (envelope-from mwlucas@easeway.com) Received: (from mwlucas@localhost) by easeway.com (8.8.8/8.8.5) id KAA09525; Fri, 27 Nov 1998 10:37:10 -0500 (EST) Message-Id: <199811271537.KAA09525@easeway.com> Subject: Re: SCOs Informix online on FreeBSD? In-Reply-To: from ! at "Nov 26, 98 10:44:42 pm" To: osa@etrust.ru Date: Fri, 27 Nov 1998 10:37:10 -0500 (EST) Cc: current@FreeBSD.ORG From: mwlucas@exceptionet.com X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Haven't used the SCO Informix, but the Linux port works perfectly under Linux emulation, so I suspect this would work fine. I'd be *very* interested in your results with SCO emulation. ==ml [Charset KOI8-R unsupported, filtering to ASCII...] > > Hello! > Does some1 use SCOs Informix online on FreeBSD? > > Rgdz, > ______ ______ aka oZZ, > osa@etrust.ru > FreeBSD - __ ________ _ ____ ____! > http://www.freebsd.org.ru > __________ _____________ _____________ FreeBSD > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Michael Lucas | Exceptionet, Inc. | www.exceptionet.com "Exceptional Networking" | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 08:25:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04871 for freebsd-current-outgoing; Fri, 27 Nov 1998 08:25:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04866 for ; Fri, 27 Nov 1998 08:25:03 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id CAA24778 for ; Sat, 28 Nov 1998 02:54:55 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA26748; Sat, 28 Nov 1998 02:54:55 +1030 Date: Sat, 28 Nov 1998 02:54:55 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: current@FreeBSD.ORG Subject: Updated gperf? Message-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 playing around with the egcs snapshots, and newer ones rely on a modified version of gperf 2.7 (gperf 2.1 is the version currently in 3.0). Can someone who actually understands what gperf does: 1) pronounce whether 2.7 is suitable for inclusion in the base tree (i.e. backwards-compatible for our needs, or whatever), and 2) take a look at ftp://egcs.cygnus.com/pub/egcs/infrastructure/gperf-2.7-19981006.pat and see whether this is a worthwhile patch to include? If not, what would be the best way to make the patched 2.7 available for use in building egcs (a gperf27 port?) I haven't checked with obrien, but from my own investigations this is probably one reason the ports snapshot hasn't been updated in the past month and a half. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 08:31:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05492 for freebsd-current-outgoing; Fri, 27 Nov 1998 08:31:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05483 for ; Fri, 27 Nov 1998 08:31:29 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id LAA39446; Fri, 27 Nov 1998 11:34:27 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 27 Nov 1998 11:34:27 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Gilad Rom cc: current@FreeBSD.ORG Subject: RE: Random craches under heavy(?) disk activity In-Reply-To: <365EB9DD.56FEF540@ein-hashofet.co.il> Message-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, 27 Nov 1998, Gilad Rom wrote: > Hello, > > First of all, Sorry, Forgot about > the "dont complain if you overclock" > rule. Guess I shouldnt be complaining. > > Second of all, The Rebooting problem > seems to be gone, finally: > > FreeBSD 3.0-CURRENT #0: Mon Nov 23 18:52:37 GMT 1998 > > uptime: 2:36PM up 3 days, 19:43 Did it stop after a recent build, or because you stopped overclocking? or both? -Alfred > > -- Gilad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 09:33:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10058 for freebsd-current-outgoing; Fri, 27 Nov 1998 09:33:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles130.castles.com [208.214.165.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10053 for ; Fri, 27 Nov 1998 09:33:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA03165; Fri, 27 Nov 1998 09:29:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811271729.JAA03165@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Werner Griessl cc: Edwin Culp , FreeBSD-Current@FreeBSD.ORG, jabc@webwizard.org.mx, eculp@MexComUSA.net, Mike Smith Subject: Re: IBM Netfinity 3500 In-reply-to: Your message of "Fri, 27 Nov 1998 15:07:11 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 27 Nov 1998 09:29:51 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA10054 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 25-Nov-98 Edwin Culp wrote: > > Mike Smith wrote: > > > >> I don't know. You might want to talk to David Greenman about this one; > >> he might have some ideas. You might also want to send the 'mptable' > >> output to the SMP folks; they may have some ideas about interrupt > >> routing that might shed some light on the situation. > >> > >> If you have time to tinker with the machine at all, it'd be very > >> educational to add some debugging to the PCI interrupt handling code to > >> see what's actually going on. A good start would be the interrupt > >> handler for the 'fxp' device. > >> > > > > I don't have a better idea. I´ll give it a try. Thanks again. > > > > ed > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > ---------------------------------- > > Have the same problem here with a Compaq-AP200 with any fxp-card. > The AP400 is working even with the buildin fxp. > But 2.2.7-Stable is working on both, so there must be a difference between > Stable and Current in the fxp-driver. Sounds about right. Both of you should be talking to David Greenman about this; make sure you get all the low-level information (PCI chipset, revision of FXP devices, etc.) to him as well. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 09:39:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10640 for freebsd-current-outgoing; Fri, 27 Nov 1998 09:39:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nts006.visionsys.com.br (nts006.visionsys.com.br [200.224.232.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10635 for ; Fri, 27 Nov 1998 09:39:00 -0800 (PST) (envelope-from mjabbur@microtecvision.com.br) Received: from microtecvision.com.br (acme.visionsys.com.br [200.224.232.54]) by nts006.visionsys.com.br with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id XNRNC81Y; Fri, 27 Nov 1998 16:38:49 -0200 Message-ID: <365EE3C3.5DD8B2D4@microtecvision.com.br> Date: Fri, 27 Nov 1998 15:39:15 -0200 From: Marlon Jabbur X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-19981117-SNAP i386) MIME-Version: 1.0 To: "FreeBSD-Current@FreeBSD.ORG" Subject: 3c905B - PLEASE HELP 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 using a 30.19981117-SNAP and i have a 3c905B Nic, when i s3et this nic in promiscuous mode , i lose my net, i can't send and receive anything , any idea ??????? I need desperately to put this working. PLEASE HELP !!!!!!!!! Marlon Jabbur To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 10:16:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13628 for freebsd-current-outgoing; Fri, 27 Nov 1998 10:16:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles130.castles.com [208.214.165.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13619 for ; Fri, 27 Nov 1998 10:16:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA03531; Fri, 27 Nov 1998 10:14:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811271814.KAA03531@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Mike Smith , Christopher Hall , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-reply-to: Your message of "Fri, 27 Nov 1998 11:13:53 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 1998 10:14:05 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I said: "is it possible to start from _DOS_ _partition_". Not "from under > > > running DOS"... see the difference? > > > > I didn't, no. Yes, it's possible; you can load the kernel and then > > You mean: it's possible with current boot1/boot2 to load kernel from > DOS partition? How? Or, are you saying that /boot/loader is able to do > that? Then again, how? The bootloader can read DOS filesystems. You'll have to work out how to get it into memory without starting DOS; either boot a floppy or rework boot1/boot2 to read DOS filesystems instead of UFS. > Thus far all my attempts at using something other than FreeBSD partition > for $currdev result in nice System halted message. > > BTW. Issuing 'set' with no args should behave as 'show' IMHO, instead of > 'System halted'... It's *very* easy to track this sort of bug down; look at sys/boot/i386/loader/Makefile, and uncomment the "debug me" lines. Also uncomment the '-g' in CFLAGS in src/lib/libstand/Makefile. Rebuild and reinstall libstand and then rebuild and reinstall the bootstrap. In the loader object directory you'll have a file called 'loader.sym'. This contains full debugging information. When you get the register dump and 'System halted' message, look at the value for %eip. Then use objdump --debug --dissassemble-all --line-numbers loader.sym to work out where the problem is. This will print a full dissasembly, but it will also match addresses with source line numbers, which will get you sorted pretty quickly. (Yes, a serial GDB stub would be nice.) > While I'm at it: I think the built-in commands of /boot/loader should > leave their result on Forth stack. Otherwise it's really hard to test if > they were successfull. Many of the builtins should be frontended by Forth code; some can probably be reimplemented largely in Forth (eg. autoboot). Since you're the Forth hacker, not me, I'm happy to take submissions. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 10:22:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13921 for freebsd-current-outgoing; Fri, 27 Nov 1998 10:22:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piston.ecp.fr (piston.ecp.fr [138.195.33.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13915 for ; Fri, 27 Nov 1998 10:22:10 -0800 (PST) (envelope-from dae@via.ecp.fr) Received: from caracal.cti.ecp.fr (root@caracal.cti.ecp.fr [138.195.33.4]) by piston.ecp.fr (8.8.7/jtpda-5.3) with ESMTP id TAA18268 ; Fri, 27 Nov 1998 19:22:00 +0100 (MET) Received: from via.ecp.fr (dae.via.ecp.fr [138.195.136.50]) by caracal.cti.ecp.fr (8.8.8/jtpda-5.2) with ESMTP id TAA23601 ; Fri, 27 Nov 1998 19:21:59 +0100 (MET) Message-ID: <365EF0C1.143E9756@via.ecp.fr> Date: Fri, 27 Nov 1998 19:34:41 +0100 From: Andres Krapf X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey , "current@FreeBSD.ORG" Subject: Re: top weirdness References: <365DE74E.3711874C@via.ecp.fr> <19981127102245.Y67961@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG my snes9x sound problem didn't go away, but now the top display is correct. thanks, Andres -- Krapf Andres, Engineering student at the Ecole Centrale Paris IRCnet: X-dae -- dae@via.ecp.fr -=- FreeBSD:The Power To Serve -=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 10:26:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14364 for freebsd-current-outgoing; Fri, 27 Nov 1998 10:26:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA14359 for ; Fri, 27 Nov 1998 10:26:42 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA28671; Fri, 27 Nov 1998 13:31:40 -0500 From: Bill Paul Message-Id: <199811271831.NAA28671@skynet.ctr.columbia.edu> Subject: Re: 3c905B - PLEASE HELP To: mjabbur@microtecvision.com.br (Marlon Jabbur) Date: Fri, 27 Nov 1998 13:31:39 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <365EE3C3.5DD8B2D4@microtecvision.com.br> from "Marlon Jabbur" at Nov 27, 98 03:39:15 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text 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, Marlon Jabbur had to walk into mine and say: > Hi, > > I'm using a 30.19981117-SNAP and i have a 3c905B Nic, when i s3et this > nic in promiscuous mode , i lose my net, i can't send and receive > anything , any idea ??????? > > > I need desperately to put this working. PLEASE HELP !!!!!!!!! First of all, calm the hell down. Second, you need to provide more information. Like, for example, how are you putting the interface into promiscuous mode? With tcpdump? With your own program? If so, can you show us the code? Some other utility? If so, which one? If you're not using tcpdump, then what happens if you do try tcpdump? Does it work? Why are you trying to run the interface in promiscuous mode? How did you come to the conclusion that the interface stopped working when you set it to promiscuous mode? What happens when you change it back? Are you using 10Mbps or 100Mbps? Full or half duplex? Show us the dmesg output from where the kernel probes the card. Do you see any error messages when the card stops working? If so, show them to us. Does netstat -in show any errors? What does ifconfig xl0 say? Go back and gather all this imformation. Don't leave anything out. Don't say "I forgot." Don't say "I'll have to try again later when I have time." Don't paraphrase error messages: quote them exactly. Breathe. -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 Nov 27 10:45:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15576 for freebsd-current-outgoing; Fri, 27 Nov 1998 10:45:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from snark.wizard.com (snark.wizard.com [199.171.28.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15403 for ; Fri, 27 Nov 1998 10:45:13 -0800 (PST) (envelope-from ernst@snark.wizard.com) Received: (from ernst@localhost) by snark.wizard.com (8.9.0/8.9.0) id KAA14957; Fri, 27 Nov 1998 10:45:07 -0800 (PST) Date: Fri, 27 Nov 1998 10:45:06 -0800 (PST) From: "Richard B. Ernst" To: current@FreeBSD.ORG Subject: 2.2.7-->current shortcut *boom* Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a production ("toy") machine that mostly provides shell accounts, serves two web sites, and runs a MUD. Since the MUD players are a fickle lot, I decided to try to upgrade from 2.2.7 to 3.0 without going into single-user mode. I really can't remember the exact steps I took now, other than trying to run the upgrade from sysinstall, and also manually backing up /etc and installing the /bin distribution. When I try to buildworld it fails at various places with .tmp files missing. When I try to recompile the kernel, it makes it all the way to the end with "symorder kernel: no such file or directory". I've also cvsup'ed the current sources with the same result. I'm vague on the exact errors, since the last time I tried compiling was last night. I can re-compile and get more detailed information if needed, though. Any suggestions for getting a clean compile? If I have to shutdown to single-user, my users will just have to live with it, but I'd rather be fairly certain that whatever steps I take will actually solve the problem rather then leaving the system in its current state. Thanks! P.S. (Yup, trying to save a few minutes has added many hours {so far} to getting this working :). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 12:34:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23027 for freebsd-current-outgoing; Fri, 27 Nov 1998 12:34:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23022 for ; Fri, 27 Nov 1998 12:34:06 -0800 (PST) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t1o29p5.telia.com [194.236.214.5]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id VAA00052; Fri, 27 Nov 1998 21:33:51 +0100 Received: from localhost (johan@localhost) by phoenix.granlund.nu (8.9.1/8.9.1) with ESMTP id VAA00373; Fri, 27 Nov 1998 21:17:29 +0100 (CET) (envelope-from johan@granlund.nu) Date: Fri, 27 Nov 1998 21:17:28 +0100 (CET) From: Johan Granlund To: Bruce Evans cc: freebsd-current@FreeBSD.ORG Subject: Re: sio breakage In-Reply-To: <199811270309.OAA13097@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Nov 1998, Bruce Evans wrote: > > >HylaFAX is compiled from ports OCT 19 and the system is all ELF > >including the kernel. The port used is cuaa1. > > Is HylaFAX broken? > It's working fine with a NOV 19 kernel and i have used it for a long time and is also using it on a 2.2-STABLE system. But who knows:) For whatever it's worth, if i talk to the modem directly with cu it seems ok. At least i don't get scrambled replys. /Johan > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 12:57:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24111 for freebsd-current-outgoing; Fri, 27 Nov 1998 12:57:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24096 for ; Fri, 27 Nov 1998 12:57:38 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forresta (forrie.ne.mediaone.net [24.128.73.118]) by spook.navinet.net (8.9.1/8.9.1) with SMTP id PAA66492 for ; Fri, 27 Nov 1998 15:58:58 -0500 (EST) Message-Id: <4.1.19981127155100.00928cb0@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 27 Nov 1998 15:57:26 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Crash (3.0) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whilst doing the following tasks: - X11 - 8hz-mp3 - x11amp (when this was started) the system locked up and rebooted. This is a build world from ~Wednesday, but the kernel is current. The machine is an HP Vectra PentiumPro 200mhz with ~92meg RAM. The crash started shortly after running x11amp... and I'm again suspicious of an on-going issue which OSS mentioned (they weren't specific about -what-, but presumably the kernel people know). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 13:29:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26075 for freebsd-current-outgoing; Fri, 27 Nov 1998 13:29:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.imc-to.com (mail.imc-to.com [209.82.43.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26070 for ; Fri, 27 Nov 1998 13:29:24 -0800 (PST) (envelope-from tim@imc.ca) Received: from valkyrie.imc-to.com (209.82.43.200) by mail.imc-to.com with SMTP (Eudora Internet Mail Server 2.1); Fri, 27 Nov 1998 17:51:27 -0400 Message-ID: <365F1914.41C67EA6@imc.ca> Date: Fri, 27 Nov 1998 16:26:44 -0500 From: Tim Gibson Organization: IMC Inc. X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: 3.0 install Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't know if I've got a problem here or if it's supposed to be like this. I've got a few old HP Vectras with an AMD ether on board. The generic install kernel sees the ether, but doesn't seem to poll it for the MAC and then doesn't finish setting up the lnc0 device for use with install. 2.2.7 did do this with no probs. I've popped a realtek 8029 into the PCI bus, didn't bother turning off the onboard ether and 3.0 setup the ed1 fine. I'm hoping that a kernel recompile (downloading the install now) will fix this up. Anyone else out there have/had this problem? Did it fixup ok with a kernel recompile? Tim Gibson IMC Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 13:40:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26836 for freebsd-current-outgoing; Fri, 27 Nov 1998 13:40:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26831 for ; Fri, 27 Nov 1998 13:40:05 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id NAA16454; Fri, 27 Nov 1998 13:39:51 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id NAA07693; Fri, 27 Nov 1998 13:39:38 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 27 Nov 1998 13:39:38 -0800 (PST) Message-Id: <199811272139.NAA07693@vashon.polstra.com> To: kkennawa@physics.adelaide.edu.au Subject: Re: Updated gperf? Newsgroups: polstra.freebsd.current In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Kris Kennaway wrote: > I've been playing around with the egcs snapshots, and newer ones rely on a > modified version of gperf 2.7 (gperf 2.1 is the version currently in 3.0). > Can someone who actually understands what gperf does: > > 1) pronounce whether 2.7 is suitable for inclusion in the base tree (i.e. > backwards-compatible for our needs, or whatever), and I don't know. I'd suggest trying a make world with the new gperf in the tree, and seeing what happens. > 2) take a look at > ftp://egcs.cygnus.com/pub/egcs/infrastructure/gperf-2.7-19981006.pat > and see whether this is a worthwhile patch to include? The patch appears to be incomplete, since it doesn't change any of the documentation files. That makes it kind of hard to guess what the patch does. It apparently adds a new command line option. But what does the new option do? It scratches somebody's secret itch, apparently. ;-) If the new gperf passes the make world test, and if you can find out what the patch does and update the man page and texinfo file appropriately, then I don't have a problem with its being brought into the source tree. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 13:52:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27791 for freebsd-current-outgoing; Fri, 27 Nov 1998 13:52:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA27786 for ; Fri, 27 Nov 1998 13:52:36 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 760 invoked from network); 27 Nov 1998 21:52:44 -0000 Received: from d007.paris-8.cybercable.fr (HELO cybercable.fr) (212.198.8.7) by bouvreuil.cybercable.fr with SMTP; 27 Nov 1998 21:52:44 -0000 Message-ID: <365F1EF6.C1ABA139@cybercable.fr> Date: Fri, 27 Nov 1998 22:51:50 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Tim Gibson CC: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 install References: <365F1914.41C67EA6@imc.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tim Gibson wrote: > > Don't know if I've got a problem here or if it's supposed to be > like this. I've got a few old HP Vectras with an AMD ether on > board. The generic install kernel sees the ether, but doesn't > seem to poll it for the MAC and then doesn't finish setting up > the lnc0 device for use with install. 2.2.7 did do this with > no probs. > > I've popped a realtek 8029 into the PCI bus, didn't bother > turning off the onboard ether and 3.0 setup the ed1 fine. > I'm hoping that a kernel recompile (downloading the install > now) will fix this up. > > Anyone else out there have/had this problem? Did it fixup ok > with a kernel recompile? > > Tim Gibson > IMC Inc. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Hello, The lance/Ethernet seems to be broken these times (see in the archives if the messages on the subject already went in) HTH TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 14:47:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03236 for freebsd-current-outgoing; Fri, 27 Nov 1998 14:47:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03228 for ; Fri, 27 Nov 1998 14:47:31 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (juana-22.pagesz.net [208.213.126.22]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id RAA12700; Fri, 27 Nov 1998 17:47:36 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id RAA01533; Fri, 27 Nov 1998 17:48:08 -0500 (EST) (envelope-from rhh) Message-ID: <19981127174808.A1208@pagesz.net> Date: Fri, 27 Nov 1998 17:48:08 -0500 From: Randall Hopper To: Thierry Herbelot , Tim Gibson Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 install Mail-Followup-To: Thierry Herbelot , Tim Gibson , freebsd-current@FreeBSD.ORG References: <365F1914.41C67EA6@imc.ca> <365F1EF6.C1ABA139@cybercable.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <365F1EF6.C1ABA139@cybercable.fr>; from Thierry Herbelot on Fri, Nov 27, 1998 at 10:51:50PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thierry Herbelot: |Tim Gibson wrote: |> Don't know if I've got a problem here or if it's supposed to be |> like this. I've got a few old HP Vectras with an AMD ether on |> board. The generic install kernel sees the ether, but doesn't |> seem to poll it for the MAC and then doesn't finish setting up |> the lnc0 device for use with install. 2.2.7 did do this with |> no probs. ... |The lance/Ethernet seems to be broken these times (see in the archives |if the messages on the subject already went in) What about it is broken? I've got a Lance board (Allied Telesyn AT-1500BT) I've been using for a long while. Great performance and works fine with FreeBSD. Currently running 3.0-RELEASE. Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 15:09:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05467 for freebsd-current-outgoing; Fri, 27 Nov 1998 15:09:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05456 for ; Fri, 27 Nov 1998 15:09:30 -0800 (PST) (envelope-from rock@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.0/1998052000) with ESMTP id AAA12715 for ; Sat, 28 Nov 1998 00:08:37 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (YC0U2YbXq3lDA5sNYxuafk/FQDN+7mOj@wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id AAA00662 for ; Sat, 28 Nov 1998 00:08:38 +0100 (CET) Received: (from rock@localhost) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) id AAA02889 for current@freebsd.org; Sat, 28 Nov 1998 00:08:34 +0100 (CET) Date: Sat, 28 Nov 1998 00:08:34 +0100 (CET) From: "D. Rock" Message-Id: <199811272308.AAA02889@wurzelausix.cs.uni-sb.de> To: current@FreeBSD.ORG Subject: ALI Aladdin V and 2nd IDE channel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I recall someone else had discussed this a while ago, but with no answers from the developers. I have an Aladdin V chipset and the 2nd IDE channel is only detected if I insert options DISABLE_PCI_IDE in my kernel config file. This option is nowhere documented but only with this option enabled my secondary IDE channel and its CDROM drive is detected properly. I didn't notice any performance degradation on the 1st IDE channel. (I get 11 MB/s with only 5% CPU usage) What does this option do exactly? Could it be somewhere documented (at least in options.i386, so I don't get the warning message from config?) Or is there a better workaround on the way form Aladdin V chips? Perhaps the problem arises because only the 1st IDE channel is DMA capable? Daniel Here is my dmesg output, if it helps (with DISABLE_PCI_IDE) Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #119: Thu Nov 26 23:59:30 CET 1998 rock@doom:/usr/src/sys/compile/ROCK Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf real memory = 67108864 (65536K bytes) config> quit avail memory = 62074880 (60620K bytes) Preloaded elf kernel "kernel" at 0xf0308000. Probing for devices on PCI bus 0: chip0: rev 0x04 on pci0.0.0 chip1: rev 0x04 on pci0.1.0 chip2: rev 0xc3 on pci0.7.0 ide_pci0: rev 0xc1 int a irq 0 on pci0.15.0 ide_pci: controller is simplex, no DMA on secondary channel Probing for devices on PCI bus 1: vga0: rev 0x5c int a irq 255 on pci1.0.0 Probing for PnP devices: Probing for devices on the ISA bus: VESA: v2.0, 8192k memory, flags:0x0, mode table:0xf02bc402 (1000022) VESA: ATI MACH64 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pca0 on motherboard pca0: PC speaker audio driver ppc: parallel port found at 0x378 ppc0 at 0x378 irq 7 flags 0x30 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode nlpt0: on ppbus 0 ppi0: on ppbus 0 wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa ide_pci: generic_dmainit 01f0:1: warning, IDE controller timing not set wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-32 wd0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa [no, other flags for wdc1 don't make any difference] wdc1: unit 0 (atapi): , removable, intr, dma, iordis wcd0: 5511KB/sec, 120KB cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in isic0 at 0x240 irq 10 flags 0x8 on isa isic0: AVM A1 or AVM Fritz!Card isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x1620) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x620, AddrB=0xe20) aha0 at 0x330-0x333 irq 11 drq 6 on isa aha0: AHA-1540/1542 64 head BIOS FW Rev. 0.5 (ID=41) SCSI Host Adapter, SCSI ID 7, 16 CCBs npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at ? drq 5 on isa snd0: awe0 at 0x620 on isa awe0: opl0 at 0x388 on isa snd0: apm0 on isa apm: found APM BIOS version 1.2 joy0 at 0x201 on isa joy0: joystick IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, unlimited logging i4b: ISDN call control device attached i4bisppp: 1 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4btrc: 1 ISDN trace device(s) attached da0 at aha0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 5.0MB/s transfers (5.0MHz, offset 7) da0: 1003MB (2056008 512 byte sectors: 64H 32S/T 1003C) da1 at aha0 bus 0 target 5 lun 0 da1: Removable Direct Access SCSI2 device da1: 3.300MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present changing root device to wd0s2a ffs_mountfs: superblock updated for soft updates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 15:25:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07125 for freebsd-current-outgoing; Fri, 27 Nov 1998 15:25:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07118 for ; Fri, 27 Nov 1998 15:25:57 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id AAA24122; Sat, 28 Nov 1998 00:31:34 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sat, 28 Nov 1998 00:31:34 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader what to set rootdev to? In-Reply-To: <199811271814.KAA03531@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Nov 1998, Mike Smith wrote: > It's *very* easy to track this sort of bug down; look at Thanks for explainig this. I'll try it (once I'm moved to my new flat.. :-/ ) > > While I'm at it: I think the built-in commands of /boot/loader should > > leave their result on Forth stack. Otherwise it's really hard to test if > > they were successfull. > > Many of the builtins should be frontended by Forth code; some can > probably be reimplemented largely in Forth (eg. autoboot). Since > you're the Forth hacker, not me, I'm happy to take submissions. 8) Heh.. The word "apprentice" would be more appropriate here. But I'll look at it. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | 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 Fri Nov 27 16:56:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16593 for freebsd-current-outgoing; Fri, 27 Nov 1998 16:56:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA16586 for ; Fri, 27 Nov 1998 16:56:51 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 6008 invoked from network); 28 Nov 1998 00:56:33 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 28 Nov 1998 00:56:33 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id TAA03374 for current@freebsd.org; Fri, 27 Nov 1998 19:56:32 -0500 (EST) Message-Id: <199811280056.TAA03374@y.dyson.net> Subject: Fix for incorrect clobbers in asm's To: current@FreeBSD.ORG Date: Fri, 27 Nov 1998 19:56:32 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM912214592-3366-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM912214592-3366-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Note that the specification for clobbers in inline asm's on GCC hasn't always been clear. The attached patches correct the clobbers in the inline asms for current. Specifically, it is totally incorrect to clobber any of the input or output operands. The workaround is to indicate that the clobbered registers are output operands, with no subsequent usage. It might be counter-intuitive, but is the suggested solution to the problem. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. --ELM912214592-3366-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=clobbers.diff Content-Description: clobbers.diff Content-Transfer-Encoding: 7bit Index: i386/i386/identcpu.c =================================================================== RCS file: /local/home/ncvs/src/sys/i386/i386/identcpu.c,v retrieving revision 1.52 diff -C1 -r1.52 identcpu.c *** identcpu.c 1998/10/06 13:16:23 1.52 --- identcpu.c 1998/11/28 00:49:10 *************** *** 106,107 **** --- 106,108 ---- { + int nax; __asm __volatile( *************** *** 112,116 **** "movl %%edx, (12)(%%esi);" ! : : "a" (ax), "S" (p) ! : "ax", "bx", "cx", "dx" ); --- 113,117 ---- "movl %%edx, (12)(%%esi);" ! : "=a"(nax) : "a" (ax), "S" (p) ! : "bx", "cx", "dx" ); Index: i386/include/cpufunc.h =================================================================== RCS file: /local/home/ncvs/src/sys/i386/include/cpufunc.h,v retrieving revision 1.81 diff -C1 -r1.81 cpufunc.h *** cpufunc.h 1998/08/17 08:57:05 1.81 --- cpufunc.h 1998/11/28 00:46:45 *************** *** 192,196 **** { __asm __volatile("cld; rep; insb" ! : : "d" (port), "D" (addr), "c" (cnt) ! : "di", "cx", "memory"); } --- 192,198 ---- { + int ndi, ncx; __asm __volatile("cld; rep; insb" ! : "=D"(ndi), "=c"(ncx) ! : "d" (port), "D" (addr), "c" (cnt) ! : "memory"); } *************** *** 200,204 **** { __asm __volatile("cld; rep; insw" ! : : "d" (port), "D" (addr), "c" (cnt) ! : "di", "cx", "memory"); } --- 202,208 ---- { + int ndi, ncx; __asm __volatile("cld; rep; insw" ! : "=D"(ndi), "=c"(ncx) ! : "d" (port), "D" (addr), "c" (cnt) ! : "memory"); } *************** *** 208,212 **** { __asm __volatile("cld; rep; insl" ! : : "d" (port), "D" (addr), "c" (cnt) ! : "di", "cx", "memory"); } --- 212,218 ---- { + int ndi, ncx; __asm __volatile("cld; rep; insl" ! : "=D"(ndi), "=c"(ncx) ! : "d" (port), "D" (addr), "c" (cnt) ! : "memory"); } *************** *** 323,327 **** { __asm __volatile("cld; rep; outsb" ! : : "d" (port), "S" (addr), "c" (cnt) ! : "si", "cx"); } --- 329,334 ---- { + int nsi, ncx; __asm __volatile("cld; rep; outsb" ! : "=S"(nsi), "=c"(ncx) ! : "d" (port), "S" (addr), "c" (cnt)); } *************** *** 331,335 **** { __asm __volatile("cld; rep; outsw" ! : : "d" (port), "S" (addr), "c" (cnt) ! : "si", "cx"); } --- 338,343 ---- { + int nsi, ncx; __asm __volatile("cld; rep; outsw" ! : "=S"(nsi), "=c"(ncx) ! : "d" (port), "S" (addr), "c" (cnt)); } *************** *** 339,343 **** { __asm __volatile("cld; rep; outsl" ! : : "d" (port), "S" (addr), "c" (cnt) ! : "si", "cx"); } --- 347,352 ---- { + int nsi, ncx; __asm __volatile("cld; rep; outsl" ! : "=S"(nsi), "=c"(ncx) ! : "d" (port), "S" (addr), "c" (cnt)); } Index: i386/isa/sound/audio.c =================================================================== RCS file: /local/home/ncvs/src/sys/i386/isa/sound/audio.c,v retrieving revision 1.19 diff -C1 -r1.19 audio.c *** audio.c 1998/07/15 11:47:58 1.19 --- audio.c 1998/11/28 00:50:36 *************** *** 167,168 **** --- 167,169 ---- { + int nbx, ncx, ndi, nsi; if (n > 0) { *************** *** 172,176 **** "stosb\n\t" ! "loop 1b\n\t": :"b"(table), "c"(n), "D"(buff), "S"(buff) ! :"bx", "cx", "di", "si", "ax"); } --- 173,178 ---- "stosb\n\t" ! "loop 1b\n\t" ! :"=b"(nbx), "=c"(ncx), "=D" (ndi), "=S" (nsi) :"b"(table), "c"(n), "D"(buff), "S"(buff) ! :"ax"); } --ELM912214592-3366-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 19:20:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26748 for freebsd-current-outgoing; Fri, 27 Nov 1998 19:20:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from citycom.com (mail.citycom.com [207.171.207.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26740 for ; Fri, 27 Nov 1998 19:20:25 -0800 (PST) (envelope-from nordwick@citycom.com) Received: from yasmeen (38.28.61.229) by citycom.com with SMTP (Eudora Internet Mail Server 2.2); Fri, 27 Nov 1998 19:19:31 -0800 Message-ID: <000301be1a7d$29cf7ad0$e53d1c26@yasmeen.citycom.com> From: "Jason Nordwick" To: Subject: System hangs when I start X-3.3.3 Date: Fri, 27 Nov 1998 19:14:07 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I really have two questions: I just downloaded a 3.0-SNAP and then when I saw X-3.3.3 come out, I immediately downloaded a new ports tree. It builds and installs fine, but when I type 'startx' the monitor changes video modes and then just remains black. I can't switch to any other consoles or hit C-A-BS or C-A-DEL. The system appears to totally freeze. I tried with different mouse protocols and a different video can setting (I have a 4M-Trident 3Dimage985 AGP, so I tried the 985 in the card database, but it didn't say AGP, so then I tried 975 AGP, and then 975 PCI). Anybody know of any problems? My second question is about cvsup. I installed it, but last time I used FreeBSD (6-8 months ago maybe?) it seems that the supfile was in a different format. If I want to track /usr/src and /usr/ports what would my cvsup file look like? I tried what I thought was correct, with by dasedir being /usr, but it starts to unpack all these RCS files in /usr/src... I wind up with /usr/CVSROOT and then all the ",v" files in /usr/src... uck. This isn't the way this is supposed to work, is it? uname -a reveils: FreeBSD beastie.citycom.com 3.0-19981122-SNAP FreeBSD 3.0-19981122-SNAP #0: Fri Nov 27 01:28:36 PST 1998 root@beastie.citycom.com:/usr/src/sys/compile/BEASTIE i386 Any suggesions? I really need to get this system up and useable soon, before I run out of time. Thanks, jay -- 4.4 > 98 http://www.xcf.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 19:44:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28647 for freebsd-current-outgoing; Fri, 27 Nov 1998 19:44:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28640 for ; Fri, 27 Nov 1998 19:44:47 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id TAA00804; Fri, 27 Nov 1998 19:44:12 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id TAA08140; Fri, 27 Nov 1998 19:43:59 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 27 Nov 1998 19:43:59 -0800 (PST) Message-Id: <199811280343.TAA08140@vashon.polstra.com> To: nordwick@citycom.com Subject: Re: System hangs when I start X-3.3.3 Newsgroups: polstra.freebsd.current In-Reply-To: <000301be1a7d$29cf7ad0$e53d1c26@yasmeen.citycom.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <000301be1a7d$29cf7ad0$e53d1c26@yasmeen.citycom.com>, Jason Nordwick wrote: > > My second question is about cvsup. I installed it, but last time I used > FreeBSD (6-8 months ago maybe?) it seems that the supfile was in a different > format. Nope, it hasn't changed recently. > If I want to track /usr/src and /usr/ports what would my cvsup file > look like? I tried what I thought was correct, with by dasedir being /usr, > but it starts to unpack all these RCS files in /usr/src... I wind up with > /usr/CVSROOT and then all the ",v" files in /usr/src... uck. It sounds like you omitted the "tag=" clause from your supfile. Study the tutorial in the FreeBSD Handbook. It was section 18.3.3 the last time I looked. Also look at the sample supfiles in "/usr/share/examples/cvsup", and the FAQ at . Then if you're still having problems with it, drop me a line and I'll help you get it straightened out. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 19:50:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29179 for freebsd-current-outgoing; Fri, 27 Nov 1998 19:50:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29172 for ; Fri, 27 Nov 1998 19:50:39 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA17888; Sat, 28 Nov 1998 14:50:29 +1100 Date: Sat, 28 Nov 1998 14:50:29 +1100 From: Bruce Evans Message-Id: <199811280350.OAA17888@godzilla.zeta.org.au> To: current@FreeBSD.ORG, rock@wurzelausix.CS.Uni-SB.DE Subject: Re: ALI Aladdin V and 2nd IDE channel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have an Aladdin V chipset and the 2nd IDE channel is only detected if >I insert >options DISABLE_PCI_IDE >in my kernel config file. This option is nowhere documented but only with >this option enabled my secondary IDE channel and its CDROM drive is detected >properly. I didn't notice any performance degradation on the 1st IDE channel. >(I get 11 MB/s with only 5% CPU usage) > >What does this option do exactly? I think it just bypasses broken unit number handling. See a recent PR. Patches for this have been floating around for more than a year, but are said to be broken in different ways. 11 MB/s takes at least 11/16.6*100% CPU in PIO mode. Reports of 5% mean that the CPU meter is broken. The CPU meter in `systat -vmstat' should work. >Could it be somewhere documented (at least >in options.i386, so I don't get the warning message from config?) Or is there No. The warning should be as annoying. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 20:13:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01021 for freebsd-current-outgoing; Fri, 27 Nov 1998 20:13:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01003; Fri, 27 Nov 1998 20:13:01 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from william.cybcon.com (william@pm3a-42.cybcon.com [205.147.75.171]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id UAA19324; Fri, 27 Nov 1998 20:12:53 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 27 Nov 1998 20:11:11 -0800 (PST) From: William Woods To: current@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Weird CPU useage Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey guys, I have a dual PP200 with 128 megs mem. Running 3.0 -current, compiled cvsup from yesterday and..... When I do a top I get this.....look the pecentages...does this make sence? PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 19262 william 105 10 692K 284K CPU1 1 25:11 123.14% 123.14% rc5des 17515 william 105 10 692K 268K RUN 0 45:04 122.22% 122.22% rc5des 3495 william 2 0 20120K 18428K select 0 3:29 1.46% 1.46% XF86_SVGA 162 root 2 0 1268K 760K select 0 3:08 1.07% 1.07% ppp 3516 william 10 0 1844K 1092K nanslp 0 0:34 0.83% 0.83% xosview 16723 william 2 0 4216K 3200K select 1 0:19 0.24% 0.24% xfmail 3509 william 2 0 4768K 3296K select 0 0:22 0.20% 0.20% kpanel 3510 william 2 0 4696K 3292K select 0 0:35 0.10% 0.10% kwm 141 root 2 0 764K 340K select 0 0:20 0.10% 0.10% moused Look at th 1st two readings, rc5...those are a little high arent they for a dual cpu system arent they? How can I be getting >200% CPU useage??? ---------------------------------- E-Mail: William Woods Date: 27-Nov-98 Time: 14:56:51 This message was sent by XFMail ---------------------------------- --------------End of forwarded message------------------------- ---------------------------------- E-Mail: William Woods Date: 27-Nov-98 Time: 20:09:53 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 21:26:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05157 for freebsd-current-outgoing; Fri, 27 Nov 1998 21:26:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05152 for ; Fri, 27 Nov 1998 21:26:46 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA22443; Sat, 28 Nov 1998 16:26:35 +1100 Date: Sat, 28 Nov 1998 16:26:35 +1100 From: Bruce Evans Message-Id: <199811280526.QAA22443@godzilla.zeta.org.au> To: current@FreeBSD.ORG, dyson@iquest.net Subject: Re: Fix for incorrect clobbers in asm's Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Specifically, it is totally incorrect to clobber any of the input >or output operands. The workaround is to indicate that the clobbered >registers are output operands, with no subsequent usage. It might >be counter-intuitive, but is the suggested solution to the problem. This is best written using constraints that say that some output operands are the same as input operands. There is no other way if the input operands aren't in fixed registers. >Index: i386/include/cpufunc.h >=================================================================== >RCS file: /local/home/ncvs/src/sys/i386/include/cpufunc.h,v >retrieving revision 1.81 >diff -C1 -r1.81 cpufunc.h >*** cpufunc.h 1998/08/17 08:57:05 1.81 >--- cpufunc.h 1998/11/28 00:46:45 >*************** >*** 192,196 **** > { > __asm __volatile("cld; rep; insb" >! : : "d" (port), "D" (addr), "c" (cnt) >! : "di", "cx", "memory"); > } >--- 192,198 ---- > { >+ int ndi, ncx; > __asm __volatile("cld; rep; insb" >! : "=D"(ndi), "=c"(ncx) >! : "d" (port), "D" (addr), "c" (cnt) >! : "memory"); > } Rewritten using constraints: __asm __volatile("cld; rep; insb" : "=D" (addr), "=c" (cnt) : "0" (addr), "1" (cnt), "d" (port) : "memory"); This discards the output operands in the input variables to avoid extra local variables. This is harmless because the input variables are dead, and more natural because it is normal for pointers to be incremented and counts to be decremented. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 21:53:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06925 for freebsd-current-outgoing; Fri, 27 Nov 1998 21:53:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from float.dyn.ml.org (cs802463-a.gvcl1.bc.wave.home.com [24.64.194.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06918 for ; Fri, 27 Nov 1998 21:53:46 -0800 (PST) (envelope-from jake@float.dyn.ml.org) Received: from float.dyn.ml.org (jake@localhost [127.0.0.1]) by float.dyn.ml.org (8.9.1/8.9.1) with ESMTP id VAA92785 for ; Fri, 27 Nov 1998 21:53:35 -0800 (PST) (envelope-from jake@float.dyn.ml.org) Message-Id: <199811280553.VAA92785@float.dyn.ml.org> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: install: strip: No such file or directory Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 1998 21:53:34 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG anyone else seeing the following just before a make -j4 world should finish? ===> netboot install -c strip -aout -o root -g wheel -m 555 nb8390.com nb3c509.com nb8390.r om nb3c509.rom /usr/mdec install: strip: No such file or directory *** Error code 71 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error fresh sources as of about 7:30 PM (PST) today. Happened yesterday too, everything was fine the day before. Would the -j4 have anything to do with it? I'll try again without it. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 21:59:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07139 for freebsd-current-outgoing; Fri, 27 Nov 1998 21:59:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA07133 for ; Fri, 27 Nov 1998 21:59:10 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 26272 invoked from network); 28 Nov 1998 05:59:02 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 28 Nov 1998 05:59:02 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id AAA04288; Sat, 28 Nov 1998 00:59:01 -0500 (EST) Message-Id: <199811280559.AAA04288@y.dyson.net> Subject: Re: Fix for incorrect clobbers in asm's In-Reply-To: <199811280526.QAA22443@godzilla.zeta.org.au> from Bruce Evans at "Nov 28, 98 04:26:35 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sat, 28 Nov 1998 00:59:01 -0500 (EST) Cc: current@FreeBSD.ORG, dyson@iquest.net From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans said: > > Rewritten using constraints: > > __asm __volatile("cld; rep; insb" > : "=D" (addr), "=c" (cnt) > : "0" (addr), "1" (cnt), "d" (port) > : "memory"); > > This discards the output operands in the input variables to avoid extra > local variables. This is harmless because the input variables are dead, > and more natural because it is normal for pointers to be incremented and > counts to be decremented. > Yes, your specific approach is better. However, the incorrect clobbers do need to be fixed, or compiling kernels with egcs will be forever a pain... -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 22:10:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08118 for freebsd-current-outgoing; Fri, 27 Nov 1998 22:10:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08112 for ; Fri, 27 Nov 1998 22:10:07 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with ESMTP id BAA60100; Sat, 28 Nov 1998 01:08:33 -0500 (EST) Date: Sat, 28 Nov 1998 01:08:33 -0500 (EST) From: jack To: Jake cc: current@FreeBSD.ORG Subject: Re: install: strip: No such file or directory In-Reply-To: <199811280553.VAA92785@float.dyn.ml.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 Fri, 27 Nov 1998, Jake wrote: > anyone else seeing the following just before a make -j4 world should finish? Yup, and I submitted a PR a little while ago. Adding beforeinstall: STRIP= to /sys/i386/boot/netboot between 3c509.o makerom ns8390.o start2.ro: machine and .include solved it for me. > ===> netboot > install -c strip -aout -o root -g wheel -m 555 nb8390.com nb3c509.com > nb8390.r > om nb3c509.rom /usr/mdec > install: strip: No such file or directory > *** Error code 71 > 1 error > fresh sources as of about 7:30 PM (PST) today. Happened yesterday too, > everything was fine the day before. > > Would the -j4 have anything to do with it? I'll try again without it. Nope. I got it without -j, and with -j{anything} -------------------------------------------------------------------------- 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 Fri Nov 27 22:21:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08760 for freebsd-current-outgoing; Fri, 27 Nov 1998 22:21:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from morgan.angis.su.OZ.AU (morgan.angis.su.OZ.AU [129.78.25.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08755 for ; Fri, 27 Nov 1998 22:21:17 -0800 (PST) (envelope-from tonym@angis.org.au) Received: (from tonym@localhost) by morgan.angis.su.OZ.AU (8.9.1a/8.9.1) id RAA02020; Sat, 28 Nov 1998 17:19:47 +1100 (EST) Date: Sat, 28 Nov 1998 17:19:47 +1100 (EST) From: Tony Maher Message-Id: <199811280619.RAA02020@morgan.angis.su.OZ.AU> To: jake@checker.org Subject: Re: install: strip: No such file or directory Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > anyone else seeing the following just before a make -j4 world should finish? > > ===> netboot > install -c strip -aout -o root -g wheel -m 555 nb8390.com nb3c509.com > nb8390.r > om nb3c509.rom /usr/mdec > install: strip: No such file or directory > Would the -j4 have anything to do with it? I'll try again without it. Happens without it too. /usr/src/sys/i386/boot/netboot/Makefile defines STRIP= strip -aout and includes /usr/src/share/mk/bsd.prog.mk which has ${INSTALL} ${COPY} ${STRIP} -o ${BINOWN} -g ${BINGRP} -m ${BINMODE} \ ${INSTALLFLAGS} ${PROG} ${DESTDIR}${BINDIR} but dont really want the strip bit here. Setting STRIP= Would solve the install bit (or just run the install by hand which is what I did) but I dont know if this has unwanted side effects. tonym To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 22:49:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10732 for freebsd-current-outgoing; Fri, 27 Nov 1998 22:49:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10726 for ; Fri, 27 Nov 1998 22:49:04 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with ESMTP id BAA23700; Sat, 28 Nov 1998 01:48:46 -0500 (EST) Date: Sat, 28 Nov 1998 01:48:45 -0500 (EST) From: jack To: Tony Maher cc: jake@checker.org, current@FreeBSD.ORG Subject: Re: install: strip: No such file or directory In-Reply-To: <199811280619.RAA02020@morgan.angis.su.OZ.AU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 28 Nov 1998, Tony Maher wrote: > /usr/src/sys/i386/boot/netboot/Makefile defines > STRIP= strip -aout > > and includes > /usr/src/share/mk/bsd.prog.mk which has > > ${INSTALL} ${COPY} ${STRIP} -o ${BINOWN} -g ${BINGRP} -m ${BINMODE} \ > ${INSTALLFLAGS} ${PROG} ${DESTDIR}${BINDIR} > > > but dont really want the strip bit here. Setting > STRIP= > > Would solve the install bit (or just run the install by hand which is what I > did) but I dont know if this has unwanted side effects. STRIP is used during the build in the nb8390.rom, nb3c509.rom, nb8390.com, and nb3c509.com targets. Setting it to the strip(1) at that point works fine, and `strip -aout' is executed during the build. During the install, where "strip -aout" is passed as a switch to install(1) in bsd.prog.mk, install(1) wants to install a program named strip. The problem is that STRIP used `locally' for the build conflicts with its use in bsd.prog.mk. Clearing it with beforeinstall allows it to be used during the build but gets it out of the way for install. Granted this is a bit of a dirty way to do it, but it was the first thing that came to mind and I need to roll a release tonight. Something other than STRIP probably should have been used to pass `strip -aout' during the build since anything other than a valid switch for install(1) will knock the install over. -------------------------------------------------------------------------- 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 Fri Nov 27 22:55:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11382 for freebsd-current-outgoing; Fri, 27 Nov 1998 22:55:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11377 for ; Fri, 27 Nov 1998 22:55:32 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA01037; Sat, 28 Nov 1998 17:55:22 +1100 Date: Sat, 28 Nov 1998 17:55:22 +1100 From: Bruce Evans Message-Id: <199811280655.RAA01037@godzilla.zeta.org.au> To: jack@germanium.xtalwind.net, jake@checker.org Subject: Re: install: strip: No such file or directory Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> anyone else seeing the following just before a make -j4 world should finish? > >Yup, and I submitted a PR a little while ago. >Adding > >beforeinstall: >STRIP= Make macros have global scope in make, so this breaks all non-install uses of STRIP. There shouldn't be any such uses, but this was broken in rev.1.20 of netboot/Makefile. All changes those changes are wrong anyway, because netboot is part of a whole tree with similarly deficient aout support. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 23:32:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14373 for freebsd-current-outgoing; Fri, 27 Nov 1998 23:32:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles303.castles.com [208.214.167.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14364 for ; Fri, 27 Nov 1998 23:32:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA00387; Fri, 27 Nov 1998 23:30:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811280730.XAA00387@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: jack@germanium.xtalwind.net, jake@checker.org, current@FreeBSD.ORG Subject: Re: install: strip: No such file or directory In-reply-to: Your message of "Sat, 28 Nov 1998 17:55:22 +1100." <199811280655.RAA01037@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Nov 1998 23:30:36 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> anyone else seeing the following just before a make -j4 world should finish? > > > >Yup, and I submitted a PR a little while ago. > >Adding > > > >beforeinstall: > >STRIP= > > Make macros have global scope in make, so this breaks all non-install > uses of STRIP. There shouldn't be any such uses, but this was broken > in rev.1.20 of netboot/Makefile. All changes those changes are wrong > anyway, because netboot is part of a whole tree with similarly deficient > aout support. The correct fix is probably to remove netboot from the world build; it is not generally useful without recompilation anyway. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 27 23:40:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15162 for freebsd-current-outgoing; Fri, 27 Nov 1998 23:40:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15157 for ; Fri, 27 Nov 1998 23:40:56 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA22969; Fri, 27 Nov 1998 23:35:51 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdd22967; Sat Nov 28 07:35:41 1998 Date: Fri, 27 Nov 1998 23:35:15 -0800 (PST) From: Julian Elischer To: "John S. Dyson" cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: Fix for incorrect clobbers in asm's In-Reply-To: <199811280559.AAA04288@y.dyson.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 I guess bruce has volunteered to check in his fixes..... On Sat, 28 Nov 1998, John S. Dyson wrote: > Bruce Evans said: > > > > Rewritten using constraints: > > > > __asm __volatile("cld; rep; insb" > > : "=D" (addr), "=c" (cnt) > > : "0" (addr), "1" (cnt), "d" (port) > > : "memory"); > > > > This discards the output operands in the input variables to avoid extra > > local variables. This is harmless because the input variables are dead, > > and more natural because it is normal for pointers to be incremented and > > counts to be decremented. > > > Yes, your specific approach is better. However, the incorrect clobbers > do need to be fixed, or compiling kernels with egcs will be forever a pain... > > -- > John | Never try to teach a pig to sing, > dyson@iquest.net | it makes one look stupid > jdyson@nc.com | and it irritates the pig. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-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 Nov 28 01:55:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25539 for freebsd-current-outgoing; Sat, 28 Nov 1998 01:55:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA25534 for ; Sat, 28 Nov 1998 01:55:22 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 14858 invoked from network); 28 Nov 1998 09:48:54 -0000 Received: from d007.paris-8.cybercable.fr (HELO cybercable.fr) (212.198.8.7) by bouvreuil.cybercable.fr with SMTP; 28 Nov 1998 09:48:54 -0000 Message-ID: <365FC6CD.D73BF0C2@cybercable.fr> Date: Sat, 28 Nov 1998 10:47:57 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Mike Smith CC: Bruce Evans , jack@germanium.xtalwind.net, jake@checker.org, current@FreeBSD.ORG Subject: Re: install: strip: No such file or directory References: <199811280730.XAA00387@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > >> anyone else seeing the following just before a make -j4 world should finish? > > > > > >Yup, and I submitted a PR a little while ago. > > >Adding > > > > > >beforeinstall: > > >STRIP= > > > > Make macros have global scope in make, so this breaks all non-install > > uses of STRIP. There shouldn't be any such uses, but this was broken > > in rev.1.20 of netboot/Makefile. All changes those changes are wrong > > anyway, because netboot is part of a whole tree with similarly deficient > > aout support. > > The correct fix is probably to remove netboot from the world build; it > is not generally useful without recompilation anyway. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Hello, What is the resulting state of a machine after such an "Installworld" ? I've done this yesterday, and I wonder what to do next (re-make world after cvsupping the last mod by Joerg Wunsch on src/sys/i386/boot/netboot/Makefile ?) TIA TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 04:40:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10508 for freebsd-current-outgoing; Sat, 28 Nov 1998 04:40:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10502 for ; Sat, 28 Nov 1998 04:40:26 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id XAA29355; Sat, 28 Nov 1998 23:10:17 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA31719; Sat, 28 Nov 1998 23:10:16 +1030 Date: Sat, 28 Nov 1998 23:10:15 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: Updated gperf? In-Reply-To: <199811272139.NAA07693@vashon.polstra.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Nov 1998, John Polstra wrote: > In article , > Kris Kennaway wrote: > > I've been playing around with the egcs snapshots, and newer ones rely on a > > modified version of gperf 2.7 (gperf 2.1 is the version currently in 3.0). > > Can someone who actually understands what gperf does: > > > > 1) pronounce whether 2.7 is suitable for inclusion in the base tree (i.e. > > backwards-compatible for our needs, or whatever), and > > I don't know. I'd suggest trying a make world with the new gperf in > the tree, and seeing what happens. Works fine, as far as I can tell.. > > 2) take a look at > > ftp://egcs.cygnus.com/pub/egcs/infrastructure/gperf-2.7-19981006.pat > > and see whether this is a worthwhile patch to include? > > The patch appears to be incomplete, since it doesn't change any of > the documentation files. That makes it kind of hard to guess what > the patch does. It apparently adds a new command line option. But > what does the new option do? It scratches somebody's secret itch, > apparently. ;-) I've forwarded on the request to the egcs people..hopefully someone will either volunteer to make the doc changes, or explain enough about what the patch does so I can. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 04:58:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11444 for freebsd-current-outgoing; Sat, 28 Nov 1998 04:58:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11438; Sat, 28 Nov 1998 04:58:33 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from cybcon.com (wwoods@cybcon.com [205.147.64.49]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id EAA04946; Sat, 28 Nov 1998 04:58:26 -0800 (PST) Date: Sat, 28 Nov 1998 04:58:25 -0800 (PST) From: Bill Woods To: questions@FreeBSD.ORG cc: current@FreeBSD.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 I am running 3.0 -current, 2 day old code, on a dual PP200 with 128meg Ram. The system is NOT overclocked. (This is inmportant) The problem is this, when I run rc5 clients and do a top, I see them both running at >120% cpu useage each...that is too weird. I run two sessions of the client, on for each cpu. Now, just to test this, I wrote a small infinite loop progra (a cpu sucker) just to see how much CPU useage was done, again, a top produced the same thing >120% per cpu. Now this would be all fine and dandy, (faster is better right?), except for ythe heat produced. This weird situation produces a nice ammount of heat. I have a fan in front, one in the back of the case, and each cpu has a fan and heat sink on it. Any ideas would be appreciated. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 05:00:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11729 for freebsd-current-outgoing; Sat, 28 Nov 1998 05:00:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11723; Sat, 28 Nov 1998 05:00:16 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from cybcon.com (wwoods@cybcon.com [205.147.64.49]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id FAA04996; Sat, 28 Nov 1998 05:00:09 -0800 (PST) Date: Sat, 28 Nov 1998 05:00:09 -0800 (PST) From: Bill Woods To: questions@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: Weird CPU useage Message-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 am running 3.0 -current, 2 day old code, on a dual PP200 with 128meg Ram. The system is NOT overclocked. (This is inmportant) The problem is this, when I run rc5 clients and do a top, I see them both running at >120% cpu useage each...that is too weird. I run two sessions of the client, on for each cpu. Now, just to test this, I wrote a small infinite loop progra (a cpu sucker) just to see how much CPU useage was done, again, a top produced the same thing >120% per cpu. Now this would be all fine and dandy, (faster is better right?), except for ythe heat produced. This weird situation produces a nice ammount of heat. I have a fan in front, one in the back of the case, and each cpu has a fan and heat sink on it. Any ideas would be appreciated. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 06:04:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14940 for freebsd-current-outgoing; Sat, 28 Nov 1998 06:04:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA14935 for ; Sat, 28 Nov 1998 06:04:33 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id PAA13038; Sat, 28 Nov 1998 15:04:09 +0100 Message-ID: <366002D7.7B736AF0@we.lc.ehu.es> Date: Sat, 28 Nov 1998 15:04:07 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: Jason Nordwick CC: freebsd-current@FreeBSD.ORG Subject: Re: System hangs when I start X-3.3.3 References: <000301be1a7d$29cf7ad0$e53d1c26@yasmeen.citycom.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Nordwick wrote: > I just downloaded a 3.0-SNAP and then when I saw X-3.3.3 come out, I > immediately downloaded a new ports tree. It builds and installs fine, but > when I type 'startx' the monitor changes video modes and then just remains > black. I can't switch to any other consoles or hit C-A-BS or C-A-DEL. The > system appears to totally freeze. I tried with different mouse protocols > and a different video can setting (I have a 4M-Trident 3Dimage985 AGP, so > I tried the 985 in the card database, but it didn't say AGP, so then I tried > 975 AGP, and then 975 PCI). Anybody know of any problems? Mmmm... sometimes, the probe for the amount of VideoRam can lock the machine with certain hardware combinations. Try to put a "VideoRam 4096" in the "Device" section in your /etc/XF86Config file. Also, check the appropriate READMEs for your Xserver/card. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-944647700 x2624 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 08:07:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22089 for freebsd-current-outgoing; Sat, 28 Nov 1998 08:07:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles233.castles.com [208.214.165.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22084 for ; Sat, 28 Nov 1998 08:07:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00888; Sat, 28 Nov 1998 08:06:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811281606.IAA00888@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Paul van der Zwan cc: current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server In-reply-to: Your message of "Mon, 23 Nov 1998 21:22:30 +0100." <199811232022.VAA00480@trantor.stuyts.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Nov 1998 08:06:10 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > When I try to create a file on a FS mounted from my Sparc 5 running Solaris 7 > I get the following error: > [21:14:42 trantor:paulz:/mnt/var/tmp] > $ touch a > touch: a: Inappropriate file type or format Interesting. > However if I ktrace the command a ktrace.out gets created. > > Part of kdump output follows: > 428 touch CALL gettimeofday(0xefbfd598,0) > 428 touch RET gettimeofday 0 > 428 touch CALL stat(0xefbfd746,0xefbfd5a8) > 428 touch NAMI "a" > 428 touch RET stat -1 errno 2 No such file or directory > 428 touch CALL open(0xefbfd746,0x201,0x1b6) > 428 touch NAMI "a" > 428 touch RET open -1 errno 79 Inappropriate file type or format > 428 touch CALL write(0x2,0xefbfce04,0x7) > > Snoop on the Sparc shows the offending(?) request and the response: > > ________________________________ > trantor -> seldon ETHER Type=0800 (IP), size = 238 bytes > trantor -> seldon IP D=192.168.200.3 S=192.168.200.2 LEN=224, ID=134 > trantor -> seldon TCP D=2049 S=1017 Ack=171713445 Seq=11856676 Len=184 Win=17200 > trantor -> seldon RPC C XID=1902072876 PROG=100003 (NFS) VERS=3 PROC=8 > trantor -> seldon NFS C CREATE3 FH=B22A (UNCHECKED) a > ________________________________ > seldon -> trantor ETHER Type=0800 (IP), size = 202 bytes > seldon -> trantor IP D=192.168.200.2 S=192.168.200.3 LEN=188, ID=59051 > seldon -> trantor TCP D=1017 S=2049 Ack=11856860 Seq=171713445 Len=148 Win=8760 > seldon -> trantor RPC R (#137) XID=1902072876 Success > seldon -> trantor NFS R CREATE3 (unknown error) > ________________________________ > > Anybody any idea ?? Looks like a problem on the Solaris box; 'unknown error' is pretty useless. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 08:14:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22700 for freebsd-current-outgoing; Sat, 28 Nov 1998 08:14:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22692 for ; Sat, 28 Nov 1998 08:14:49 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id QAA89994; Sat, 28 Nov 1998 16:14:37 GMT Message-ID: <3660216C.89446EB2@tdx.co.uk> Date: Sat, 28 Nov 1998 16:14:36 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Bill Woods CC: current@FreeBSD.ORG Subject: Re: Weird CPU useage References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Woods wrote: > > I am running 3.0 -current, 2 day old code, on a dual PP200 with 128meg > Ram. The system is NOT overclocked. (This is inmportant) > > The problem is this, when I run rc5 clients and do a top, I see them > both running at >120% cpu useage each...that is too weird. I run two > sessions of the client, on for each cpu. Now, just to test this, I wrote > a small infinite loop progra (a cpu sucker) just to see how much CPU > useage was done, again, a top produced the same thing >120% per cpu. Hmmm... I have a dual PP200 system here, I'll see if I get a similar result (not obviously noticed this to be honest... ;-) > Now this would be all fine and dandy, (faster is better right?), except > for ythe heat produced. This weird situation produces a nice ammount of > heat. I have a fan in front, one in the back of the case, and each cpu has > a fan and heat sink on it. > > Any ideas would be appreciated. I'm sorry? - Are you saying that the CPU running RC5 or a 'tight-loop' shouldn't produce that much heat? RC5 runs as 'nice' - i.e. it will get the CPU if nothing else wants/needs it - and as such, on an idle system it will use all the CPU available for it's nasty DES/RC5 code cracking routines - this should generate the same amount of heat as a system running a deliberate 'tight' / CPU sucker (in fact it might generate more heat for the RC5 client - as it pushes the CPU more than a simple tight loop)... FreeBSD only _ever_ runs 'cooler' when it's doing _nothing_ as the HALT instruction get's called a lot by the idle loop AFAIK, this is why an idle FreeBSD box will not heat your cpu as much as an Idle 'other os' box (unless the 'other' OS does a similar thing)... It's also the reason why going into MS DOS edit and dropping down the 'File' menu causes the CPU to get nice and warm... Apparenlty dropping down the File menu involves some nice stressfull MS code ;-) -Kp ps. Please don't cross post - it almost always annoys people ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 08:17:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23018 for freebsd-current-outgoing; Sat, 28 Nov 1998 08:17:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23001; Sat, 28 Nov 1998 08:17:36 -0800 (PST) (envelope-from a0074@netcologne.de) Received: from bsd3.scs-koeln.de (dial5-83.netcologne.de [194.8.195.83]) by mail2.netcologne.de (8.9.1/8.9.1) with SMTP id RAA27775; Sat, 28 Nov 1998 17:17:14 +0100 (MET) X-Ncc-Regid: de.netcologne Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 28 Nov 1998 17:13:32 +0100 (CET) From: "R. Luettgen" To: freebsd-current@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Correction of nfsstat in 3.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I've a 3.0 RELEASE on my box and it works well. Today I want use nfsstat but I g ot an error message. Here is the patch I make in nfsstat.c . 172c172 < name[1] = vfc.vfc_typenum; --- > name[1] = VFS_GENERIC; I hope I can help also others. By Ralf ---------------------------------- E-Mail: R. Luettgen Date: 28-Nov-98 Time: 17:13:32 This message was sent by XF-Mail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 08:34:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24500 for freebsd-current-outgoing; Sat, 28 Nov 1998 08:34:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ww181.netaddress.usa.net (ww181.netaddress.usa.net [204.68.24.81]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA24493 for ; Sat, 28 Nov 1998 08:34:52 -0800 (PST) (envelope-from WillliamW@netscape.net) Received: (qmail 9361 invoked by uid 60001); 28 Nov 1998 09:37:38 -0000 Message-ID: <19981128093738.9360.qmail@ww181.netaddress.usa.net> Received: from 204.68.24.81 by ww181 via web-mailer(R2.6) on Sat Nov 28 09:37:38 GMT 1998 Date: 28 Nov 98 03:37:38 CST From: Willliam Woods To: majordom@FreeBSD.ORG, Bill Woods Subject: Re: [Re: Weird CPU useage] CC: current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA24494 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hmmm... I have a dual PP200 system here, I'll see if I get a similar result > (not obviously noticed this to be honest... ;-) OK, thanks. Everything ran just fine untill I compiled the new cvsup. > > Now this would be all fine and dandy, (faster is better right?), except > I'm sorry? - Are you saying that the CPU running RC5 or a 'tight-loop' > shouldn't produce that much heat? Not really, what I said about the loop was just to point out that it did not seem like rc5 was the culpret in this case. > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message William Woods: Please reply to --->>> wwoods@cybcon.com <<<--- AOL IM: bsdman1 ____________________________________________________________________ More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 08:42:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25231 for freebsd-current-outgoing; Sat, 28 Nov 1998 08:42:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25226 for ; Sat, 28 Nov 1998 08:42:11 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id IAA24441; Sat, 28 Nov 1998 08:41:29 -0800 (PST) Date: Sat, 28 Nov 1998 08:41:29 -0800 (PST) From: "Steven P. Donegan" To: Mike Smith cc: Bruce Evans , jack@germanium.xtalwind.net, jake@checker.org, current@FreeBSD.ORG Subject: Re: install: strip: No such file or directory In-Reply-To: <199811280730.XAA00387@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 Well, whoever is working on this has succeeded in making the failure happen after 5 minutes instead of 3+ hours :-) ===> usr.bin/strip rm -f maybe_stripped strip strip.o strip.1aout.gz strip.1aout.cat.gz rm -f .depend /usr/src/usr.bin/strip/GRTAGS /usr/src/usr.bin/strip/GSYMS /usr/src/usr.bin/strip/GTAGS 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error 179.7u 209.9s 5:17.22 122.8% 327+428k 2199+16724io 24pf+0w I think that's progress :-) The errors here are from a make world: cd /usr/obj chflags -R noschg * rm -r * cd /usr/src time make -j 18 world To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 08:45:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25636 for freebsd-current-outgoing; Sat, 28 Nov 1998 08:45:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25630; Sat, 28 Nov 1998 08:45:11 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA25934; Sun, 29 Nov 1998 03:44:07 +1100 Date: Sun, 29 Nov 1998 03:44:07 +1100 From: Bruce Evans Message-Id: <199811281644.DAA25934@godzilla.zeta.org.au> To: a0074@netcologne.de, freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Correction of nfsstat in 3.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I've a 3.0 RELEASE on my box and it works well. Today I want use nfsstat but I g >ot an error message. Here is the patch I make in nfsstat.c . > > >172c172 >< name[1] = vfc.vfc_typenum; >--- >> name[1] = VFS_GENERIC; vfc_typenum was broken in some (old, almost as old as 3.0) versions of the kernel. VFS_GENERIC isn't correct here. It only works if nfs's vfc_typenum happens to be VFS_GENERIC (= 0). This should never happen for current kernels, because the type numbers start at 1. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 08:46:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25586 for freebsd-current-outgoing; Sat, 28 Nov 1998 08:44:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25569; Sat, 28 Nov 1998 08:44:01 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id QAA90168; Sat, 28 Nov 1998 16:43:47 GMT Message-ID: <36602843.DFD3E0A1@tdx.co.uk> Date: Sat, 28 Nov 1998 16:43:47 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Willliam Woods CC: majordom@FreeBSD.ORG, Bill Woods , current@FreeBSD.ORG Subject: Re: [Re: Weird CPU useage] References: <19981128093738.9360.qmail@ww181.netaddress.usa.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Willliam Woods wrote: > > Hmmm... I have a dual PP200 system here, I'll see if I get a similar result > > (not obviously noticed this to be honest... ;-) > OK, thanks. Everything ran just fine untill I compiled the new cvsup. I'm now running -current as of about 4 hours ago, and so far (fingers crossed ;-) - it looks OK... > > > Now this would be all fine and dandy, (faster is better right?), except > > I'm sorry? - Are you saying that the CPU running RC5 or a 'tight-loop' > > shouldn't produce that much heat? > > Not really, what I said about the loop was just to point out that it did not > seem like rc5 was the culpret in this case. OK - I thought you were complaining about the heat produced when just running RC5 ;-) - I was trying to make the point, just because it runs 'nice' (and only in otherwise Idle time) - it's still doing work, therefore still generates more heat (then the HALT / idle states it's replacing ;-) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 10:14:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02554 for freebsd-current-outgoing; Sat, 28 Nov 1998 10:14:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from head.lvl.ru (head.lvl.ru [195.210.164.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02531; Sat, 28 Nov 1998 10:13:58 -0800 (PST) (envelope-from elias@head.lvl.ru) Received: (from elias@localhost) by head.lvl.ru (8.8.8/8.8.8) id VAA17409; Sat, 28 Nov 1998 21:13:07 +0300 (MSK) (envelope-from elias) Message-ID: <19981128211307.A16994@cnetworks.net> Date: Sat, 28 Nov 1998 21:13:07 +0300 From: Ilya Orehov To: Brian Feldman Cc: phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: kern_clock.c (was: video mode switching has gone south) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from Brian Feldman on Tue, Nov 24, 1998 at 07:57:32AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm another one who can report somewhat new behaviour : 1. X now starts up more slowly, with flicker. 2. usleep(s), where s=1, 10, 100, 10000 sleeps for about 1 second, regardless of argument. I think it is hardware-dependent, since on another machine (with Intel CPU) usleep() works ok. It shows up after recent commit in kern_clock.c: Edit src/sys/kern/kern_clock.c Add delta 1.85 98.11.23.09.58.53 phk Commenting out 2 lines in tco_forward() solved both problems for me. *** /sys/kern/kern_clock.c Sat Nov 28 18:13:02 1998 --- kern_clock.c.1.85 Mon Nov 23 12:58:53 1998 *************** *** 792,801 **** tco_setscales(tc); force++; } ! /* if (!force) return; ! */ tc->tc_offset_micro = (tc->tc_offset_nano / 1000) >> 32; /* Figure out the wall-clock time */ --- 792,801 ---- tco_setscales(tc); force++; } ! if (!force) return; ! tc->tc_offset_micro = (tc->tc_offset_nano / 1000) >> 32; /* Figure out the wall-clock time */ Half of my dmesg ( gee! we're both use CPUs by AMD and ViRGE): Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #33: Sat Nov 28 18:15:51 MSK 1998 elias@cactus.unicon.msk.su:/make/src/sys/compile/Cactus Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 99952410 Hz CPU: AMD-K5(tm) Processor (99.95-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x512 Stepping=2 Features=0x21bf real memory = 33554432 (32768K bytes) config> quit avail memory = 30216192 (29508K bytes) DEVFS: ready for devices Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 vga0: rev 0x01 int a irq 11 on pci0.13.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> [...] On Tue, Nov 24, 1998 at 07:57:32AM -0500, Brian Feldman wrote: | It seems (nay, it IS so) that video mode switching has gotten extremely | strange within the last few days. This is not a problem just with vidcontrol | and syscons, this affects XFree86 as well. I've got two kernels, the old one | which does not exhibit this problem, and the new one which does. | | Working: | FreeBSD 3.0-CURRENT #3: Sun Nov 22 21:45:52 EST 1998 | Broken: | FreeBSD 3.0-CURRENT #4: Mon Nov 23 20:11:02 EST 1998 | | | Copyright (c) 1992-1998 FreeBSD Inc. | Copyright (c) 1982, 1986, 1989, 1991, 1993 | The Regents of the University of California. All rights reserved. | FreeBSD 3.0-CURRENT #3: Sun Nov 22 21:45:52 EST 1998 | green@feldman.dyn.ml.org:/usr/src/sys/compile/FELDMAN | Timecounter "i8254" frequency 1193182 Hz | Timecounter "TSC" frequency 200455956 Hz | CPU: AMD-K6tm w/ multimedia extensions (200.46-MHz 586-class CPU) | Origin = "AuthenticAMD" Id = 0x561 Stepping=1 | Features=0x8001bf | real memory = 83886080 (81920K bytes) | config> quit | avail memory = 78667776 (76824K bytes) | Preloaded elf kernel "kernel.old" at 0xf0289000. | Probing for devices on PCI bus 0: | chip0: rev 0x02 on pci0.0.0 | chip1: rev 0x01 on pci0.7.0 | ide_pci0: rev 0x00 on pci0.7.1 | vga0: rev 0x01 int a irq 10 on pci0.13.0 | Probing for PnP devices: | Probing for devices on the ISA bus: | VESA: v1.2, 4096k memory, flags:0x0, mode table:0xf00c4cc2 (c0004cc2) | VESA: S3 Incorporated. 86C375/86C385 | sc0 at 0x60-0x6f irq 1 on motherboard | sc0: VGA color <16 virtual consoles, flags=0x0> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 11:03:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05239 for freebsd-current-outgoing; Sat, 28 Nov 1998 11:03:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05234 for ; Sat, 28 Nov 1998 11:03:44 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA05561; Sat, 28 Nov 1998 11:03:37 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA12139; Sat, 28 Nov 1998 11:03:36 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 28 Nov 1998 11:03:36 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Kris Kennaway Subject: Re: Updated gperf? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Nov-98 Kris Kennaway wrote: > On Fri, 27 Nov 1998, John Polstra wrote: > >> I don't know. I'd suggest trying a make world with the new gperf in >> the tree, and seeing what happens. > > Works fine, as far as I can tell.. Then it's almost certainly OK. The utility is used mainly (only?) for building the compiler. And it's not used for some subtle code generation thing; it's used for recognizing the language's keywords. If it were broken, it surely would have shown up in a make world. > I've forwarded on the request to the egcs people..hopefully someone > will either volunteer to make the doc changes, or explain enough > about what the patch does so I can. Great. Thanks! John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 11:08:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05635 for freebsd-current-outgoing; Sat, 28 Nov 1998 11:08:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mcfs.whowhere.com (mcfs.whowhere.com [209.1.236.44]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA05628 for ; Sat, 28 Nov 1998 11:08:14 -0800 (PST) (envelope-from erkaf@my-dejanews.com) Received: from Unknown/Local ([?.?.?.?]) by my-dejanews.com; Sat Nov 28 11:07:57 1998 To: current@FreeBSD.ORG Date: Sat, 28 Nov 1998 11:07:57 -0700 From: "Kelvin Farmer" Message-ID: Mime-Version: 1.0 Cc: green@unixhelp.org, phk@FreeBSD.ORG X-Sent-Mail: off X-Mailer: MailCity Service Subject: Re: kern_clock.c (me too) X-Sender-Ip: 192.75.12.156 Organization: Deja News Mail (http://www.my-dejanews.com:80) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ilya Orehov's fix also works for me. I have an AMD K6 and a Virge VX. -----== Sent via Deja News, The Discussion Network ==----- http://www.dejanews.com/ Easy access to 50,000+ discussion forums To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 12:59:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13596 for freebsd-current-outgoing; Sat, 28 Nov 1998 12:59:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13580 for ; Sat, 28 Nov 1998 12:59:40 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id PAA07956; Sat, 28 Nov 1998 15:53:44 -0500 (EST) Message-ID: <19981128155344.A4298@ns1.adsu.bellsouth.com> Date: Sat, 28 Nov 1998 15:53:44 -0500 From: Christian Kuhtz To: "Steven P. Donegan" , Mike Smith Cc: Bruce Evans , jack@germanium.xtalwind.net, jake@checker.org, current@FreeBSD.ORG Subject: Re: install: strip: No such file or directory References: <199811280730.XAA00387@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Steven P. Donegan on Sat, Nov 28, 1998 at 08:41:29AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I manually cvsup'ed late this morning (EST) and everything appears to be fine now.. my make world ran through all the way just fine. Cheers, Chris On Sat, Nov 28, 1998 at 08:41:29AM -0800, Steven P. Donegan wrote: > Well, whoever is working on this has succeeded in making the failure > happen after 5 minutes instead of 3+ hours :-) > > ===> usr.bin/strip > rm -f maybe_stripped strip strip.o strip.1aout.gz strip.1aout.cat.gz > rm -f .depend /usr/src/usr.bin/strip/GRTAGS /usr/src/usr.bin/strip/GSYMS > /usr/src/usr.bin/strip/GTAGS > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > 179.7u 209.9s 5:17.22 122.8% 327+428k 2199+16724io 24pf+0w > > I think that's progress :-) > > The errors here are from a make world: > > cd /usr/obj > chflags -R noschg * > rm -r * > cd /usr/src > time make -j 18 world > > > 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 Nov 28 13:24:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15668 for freebsd-current-outgoing; Sat, 28 Nov 1998 13:24:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15662 for ; Sat, 28 Nov 1998 13:24:34 -0800 (PST) (envelope-from leifn@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id WAA12154; Sat, 28 Nov 1998 22:23:34 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Sat, 28 Nov 1998 22:23:34 +0100 (CET) From: Leif Neland To: Brian Somers cc: freebsd-current@FreeBSD.ORG Subject: Re: user-ppp broken since a few days ago? In-Reply-To: <199811270713.HAA41019@woof.lan.awfulhak.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 Fri, 27 Nov 1998, Brian Somers wrote: > Hi, > > What happens if you ``set openmode active 2'' ? > > Also, you may want to enable async logging to see what that initial > data is - 0801 doesn't make much sense (is this consistent?). > Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: deflink: Dial attempt 1 of 1 Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Send: AT^M Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Expect(5): OK Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Received: AT^M^M Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Received: OK^M Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Send: ATE1Q0^M Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Expect(5): OK Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Received: ATE1Q0^M^M Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Received: OK^M Nov 28 22:14:42 gina ppp[11867]: tun0: Chat: Send: ATDI1001-xxxxxxxx^M Nov 28 22:14:47 gina ppp[11867]: tun0: Chat: Expect(40): CONNECT Nov 28 22:14:47 gina ppp[11867]: tun0: Chat: Received: ATDI1001-xxxxxxxx^M^M Nov 28 22:14:47 gina ppp[11867]: tun0: Chat: Received: CONNECT 115200/PPP 64000/NONE^M Nov 28 22:14:47 gina ppp[11867]: tun0: Phase: deflink: dial -> login Nov 28 22:14:47 gina ppp[11867]: tun0: Phase: deflink: login -> lcp Nov 28 22:14:47 gina ppp[11867]: tun0: LCP: FSM: Using "deflink" as a transport Nov 28 22:14:47 gina ppp[11867]: tun0: LCP: deflink: State change Initial --> Closed Nov 28 22:14:47 gina ppp[11867]: tun0: Phase: deflink: Entering STOPPED state for 2 seconds Nov 28 22:14:47 gina ppp[11867]: tun0: LCP: deflink: State change Closed --> Stopped Nov 28 22:14:48 gina ppp[11867]: tun0: Async: ReadFromModem Nov 28 22:14:48 gina ppp[11867]: tun0: Async: 7e 7d 28 7d 21 7f a6 92 7e Nov 28 22:14:48 gina ppp[11867]: tun0: Phase: Unknown protocol 0x0801 (unrecognised protocol) Nov 28 22:14:48 gina ppp[11867]: tun0: LCP: deflink: SendProtocolRej(1) state = Stopped Nov 28 22:14:48 gina ppp[11867]: tun0: Async: WriteModem Nov 28 22:14:48 gina ppp[11867]: tun0: Async: 7e ff 7d 23 c0 21 7d 28 7d 21 7d 20 7d 27 7d 28 Nov 28 22:14:48 gina ppp[11867]: tun0: Async: 7d 21 7f 57 67 7e Nov 28 22:14:49 gina ppp[11867]: tun0: Async: ReadFromModem Nov 28 22:14:49 gina ppp[11867]: tun0: Async: 0d 0a 4e 4f 20 43 41 52 52 49 45 52 0d 0a Nov 28 22:14:49 gina ppp[11867]: tun0: Phase: deflink: Carrier lost Nov 28 22:14:49 gina ppp[11867]: tun0: LCP: deflink: State change Stopped --> Closed Unknown protocol? Is that the same as the windows message "Dialup network couldn't find a supported protocol. Check the servertype settings and the settings in control panel" ? Sometimes I and clients get this message when calling by isdn to the portmaster 2e. Leif Neland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 13:57:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18386 for freebsd-current-outgoing; Sat, 28 Nov 1998 13:57:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18380 for ; Sat, 28 Nov 1998 13:57:42 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id NAA24809; Sat, 28 Nov 1998 13:57:29 -0800 (PST) Date: Sat, 28 Nov 1998 13:57:29 -0800 (PST) From: "Steven P. Donegan" To: Christian Kuhtz cc: Mike Smith , Bruce Evans , jack@germanium.xtalwind.net, jake@checker.org, current@FreeBSD.ORG Subject: Re: install: strip: No such file or directory In-Reply-To: <19981128155344.A4298@ns1.adsu.bellsouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 28 Nov 1998, Christian Kuhtz wrote: > > > I manually cvsup'ed late this morning (EST) and everything appears to be fine > now.. my make world ran through all the way just fine. > > Cheers, > Chris > I'm trying again - this time with make world - not make -j 18 world. Things are running along fine so far. A few months ago a make -j anything was a guaranteed SMP/softupdates killer. I'm glad to see that things have hardened a bit. Does anyone run SMP/softupdates without problems? Happy Holiday's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 14:00:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18817 for freebsd-current-outgoing; Sat, 28 Nov 1998 14:00:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18809; Sat, 28 Nov 1998 14:00:45 -0800 (PST) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA04723; Sat, 28 Nov 1998 22:55:44 +0100 (MET) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id WAA00974; Sat, 28 Nov 1998 22:54:21 +0100 (CET) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199811282154.WAA00974@semyam.dinoco.de> To: Ilya Orehov cc: Brian Feldman , phk@FreeBSD.ORG, current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: kern_clock.c (was: video mode switching has gone south) In-reply-to: Your message of "Sat, 28 Nov 1998 21:13:07 +0300." <19981128211307.A16994@cnetworks.net> Date: Sat, 28 Nov 1998 22:54:20 +0100 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm another one who can report somewhat new behaviour : > > 1. X now starts up more slowly, with flicker. I think for me that's the case, too but is hard to judge. > 2. usleep(s), where s=1, 10, 100, 10000 sleeps for about 1 second, > regardless of argument. That probably explains the strange behavior of olvwm I saw. When I tried to deiconify xconsole it shows the usual animation but with the new kernel it did it in slow motion. Removing 1.85 from kern_clock.c and installing another kernel cured that. I didn't try you attached patch, though. The shortened down dmesg for a kernel with 1.84 is this: (BTW: Where the hell does the "config> quit" come from???) Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #28: Sat Nov 28 22:41:03 CET 1998 seggers@semyam.dinoco.de:/usr2/FreeBSD/src/sys/compile/SEMYAM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 99474053 Hz CPU: Pentium/P54C (99.47-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 50331648 (49152K bytes) config> quit avail memory = 46751744 (45656K bytes) Preloaded elf kernel "kernel" at 0xf023a000. [...] Preloaded elf module "ipfw.ko" at 0xf023a27c. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.7.0 ide_pci0: rev 0x02 on pci0.7.1 vga0: rev 0x00 int a irq 10 on pci0.10.0 ncr0: rev 0x03 int a irq 11 on pci0.12.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> [sio0/sio1/sio2] [ppc/ppc0/nlpt0/plip0] [ppc/ppc1/nlpt1/plip1] [fdc0/fd0] [wdc0/wd0/wdc1/wd2] npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging limited to 100 packets/entry ccd0-3: Concatenated disk drivers Waiting 5 seconds for SCSI devices to settle changing root device to wd0s1a [cd0] [da0] Start pid=2 Start pid=3 Start pid=4 Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 14:24:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20942 for freebsd-current-outgoing; Sat, 28 Nov 1998 14:24:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20921 for ; Sat, 28 Nov 1998 14:24:31 -0800 (PST) (envelope-from rock@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.0/1998052000) with ESMTP id XAA19088; Sat, 28 Nov 1998 23:24:08 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (Sz40inlzoevDIllAfey9tkMz/jOonfTQ@wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id XAA09442; Sat, 28 Nov 1998 23:24:08 +0100 (CET) Received: (from rock@localhost) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) id XAA07155; Sat, 28 Nov 1998 23:23:59 +0100 (CET) Date: Sat, 28 Nov 1998 23:23:59 +0100 (CET) From: "D. Rock" Message-Id: <199811282223.XAA07155@wurzelausix.cs.uni-sb.de> To: bde@zeta.org.au, current@FreeBSD.ORG Subject: Re: ALI Aladdin V and 2nd IDE channel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>I have an Aladdin V chipset and the 2nd IDE channel is only detected if >>I insert >>options DISABLE_PCI_IDE >>in my kernel config file. This option is nowhere documented but only with >>this option enabled my secondary IDE channel and its CDROM drive is detected >>properly. I didn't notice any performance degradation on the 1st IDE channel. >>(I get 11 MB/s with only 5% CPU usage) >> >>What does this option do exactly? > >I think it just bypasses broken unit number handling. See a recent PR. >Patches for this have been floating around for more than a year, but are >said to be broken in different ways. > >11 MB/s takes at least 11/16.6*100% CPU in PIO mode. Reports of 5% >mean that the CPU meter is broken. The CPU meter in `systat -vmstat' >should work. This was the output from systat -v! The CPU meter showed up 95% idle time, so I think, it is still using DMA. The system was also too responsive for PIO modes. To be sure I will do another test with an CPU intensive job running at the same time, so the real idle time (if it is measured incorrectly) should be scheduled to this process. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 15:03:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23071 for freebsd-current-outgoing; Sat, 28 Nov 1998 15:03:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23066 for ; Sat, 28 Nov 1998 15:03:24 -0800 (PST) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.1/8.9.1) id PAA01738 for current@freebsd.org; Sat, 28 Nov 1998 15:46:51 -0600 (CST) (envelope-from conrads) 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: Sat, 28 Nov 1998 15:46:50 -0600 (CST) Reply-To: conrads@neosoft.com Organization: NeoSoft, Inc. From: Conrad Sabatier To: current@FreeBSD.ORG Subject: What happened to "options USERCONFIG_BOOT"? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The latest -current seems to have deprecated "options USERCONFIG_BOOT", but I've been unable to find out what the new substitute for this is. I certainly hope we won't have to manually configure PnP devices on each new kernel boot! Sorry if I somehow missed the mention of this earlier. Any info greatly appreciated. Thanks. -- Conrad Sabatier No man is an island, but some of us are long peninsulas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 15:32:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24962 for freebsd-current-outgoing; Sat, 28 Nov 1998 15:32:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA24952 for ; Sat, 28 Nov 1998 15:32:25 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 21177 invoked by uid 1001); 28 Nov 1998 23:32:13 +0000 (GMT) To: freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Patches and mptable for Supermicro P6DGU with 440GX chipset X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 29 Nov 1998 00:32:13 +0100 Message-ID: <21175.912295933@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I now have FreeBSD-current up and running on a Supermicro P6DGU mother- board with 440GX chipset, 2 x PII-400 and onboard Adaptec 7890 U2W SCSI. Getting FreeBSD up and running was relatively painless, and it seems to be working great so far. The only SMP options I'm currently using are SMP and APIC_IO. Included below are a patch for pci/pcisupport.c to identify the 440GX, and the mptable output for this system. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- --- pcisupport.c.orig Sat Oct 31 11:35:24 1998 +++ pcisupport.c Sun Nov 29 00:05:19 1998 @@ -226,6 +226,12 @@ return ("Intel 82443BX host to AGP bridge"); case 0x71928086: return ("Intel 82443BX host to PCI bridge (AGP disabled)"); + case 0x71a08086: + return ("Intel 82443GX host to PCI bridge"); + case 0x71a18086: + return ("Intel 82443GX host to AGP bridge"); + case 0x71a28086: + return ("Intel 82443GX host to PCI bridge (AGP disabled)"); case 0x12378086: fixwsc_natoma(tag); return ("Intel 82440FX (Natoma) PCI and memory controller"); =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000fb4f0 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0xbd mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f24b0 signature: 'PCMP' base table length: 268 version: 1.4 checksum: 0xc3 OEM ID: 'INTEL ' Product ID: '440BX ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 25 local APIC address: 0xfee00000 extended table length: 16 extended table checksum: 234 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 6 5 2 0x183fbff 1 0x11 AP, usable 6 5 2 0x183fbff -- Bus: Bus ID Type 0 PCI 1 PCI 2 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 2 0 2 0 INT conforms conforms 2 1 2 1 INT conforms conforms 2 0 2 2 INT conforms conforms 2 3 2 3 INT conforms conforms 2 4 2 4 INT conforms conforms 2 5 2 5 INT conforms conforms 2 6 2 6 INT conforms conforms 2 7 2 7 INT active-hi edge 2 8 2 8 INT conforms conforms 2 9 2 9 INT conforms conforms 2 12 2 12 INT conforms conforms 2 13 2 13 INT conforms conforms 2 14 2 14 INT conforms conforms 2 15 2 15 INT active-lo level 2 10 2 16 INT active-lo level 2 11 2 17 SMI conforms conforms 2 0 2 23 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0:A 255 0 NMI conforms conforms 0 0:A 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: Extended Table HOSED! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 15:34:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25322 for freebsd-current-outgoing; Sat, 28 Nov 1998 15:34:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bursa.asel.net.tr ([195.174.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25293 for ; Sat, 28 Nov 1998 15:34:32 -0800 (PST) (envelope-from vlad@bursa.asel.net.tr) Received: from localhost (vlad@localhost) by bursa.asel.net.tr (8.8.8/8.8.8) with ESMTP id BAA19195; Sun, 29 Nov 1998 01:32:45 +0200 (EET) (envelope-from vlad@bursa.asel.net.tr) Date: Sun, 29 Nov 1998 01:32:45 +0200 (EET) From: Vlad Cambur To: "Steven P. Donegan" cc: current@FreeBSD.ORG Subject: Re: install: strip: No such file or directory In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 28 Nov 1998, Steven P. Donegan wrote: [snip] > > I'm trying again - this time with make world - not make -j 18 world. > Things are running along fine so far. A few months ago a make -j anything > was a guaranteed SMP/softupdates killer. I'm glad to see that things have > hardened a bit. > > Does anyone run SMP/softupdates without problems? > > Happy Holiday's. I'm running 3.0-CURRENT SMP (aout kernel everything else is elf) with softupdates enabled more than a month and it works just fine, survived even a make -j48 world. FreeBSD 3.0-CURRENT #0: Wed Nov 25 11:10:09 EET 1998 root@oxid.asel.net.tr:/usr/src/sys/compile/OXID Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II (quarter-micron) (686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183fbff> real memory = 268435456 (262144K bytes) config> quit avail memory = 258416640 (252360K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 -- vlad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 15:49:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26280 for freebsd-current-outgoing; Sat, 28 Nov 1998 15:49:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26274 for ; Sat, 28 Nov 1998 15:49:48 -0800 (PST) (envelope-from wolman@cs.washington.edu) Received: from miles.cs.washington.edu (miles.cs.washington.edu [128.95.4.177]) by june.cs.washington.edu (8.8.7+CS/7.2ju) with ESMTP id PAA11175 for ; Sat, 28 Nov 1998 15:49:41 -0800 Received: from miles.cs.washington.edu (localhost [127.0.0.1]) by miles.cs.washington.edu (8.9.1/8.9.1) with ESMTP id PAA16757 for ; Sat, 28 Nov 1998 15:49:40 -0800 (PST) (envelope-from wolman@miles.cs.washington.edu) Message-Id: <199811282349.PAA16757@miles.cs.washington.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: MAXDSIZ limit Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Nov 1998 15:49:40 -0800 From: "Alec Wolman" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm running FreeBSD 3.0-19981103 SNAP, and I'm running into a problem or two. I first tried changing MAXDSIZE in my kernel config file to MAXDSIZ 2048*1024*1024 This causes numerous compilation warnings, presumably because the calculations being done with the number are signed rather than unsigned. Setting it to 2000*1024*1024 eliminates all of those warnings except for one, in imgact_elf.c. I tried booting this kernel, but it dies. I don't have the exact error message, but the kernel boots up and manages to go through the device configuration, but when it gets to execing an elf process things go haywire. I think the error message had to do with being unable to start getty. When I fixed the compiler warning with the following change, and I changed MAXDSIZ to 1500*1024*1024, and rebooted, then things seemed to work ok. However, I suspect that lowering MAXDSIZ rather than fixing the code is what made things better. Does anyone here understand why the elf code needs to multiply MAXDSIZ by 2 and then use that as a base address for something else? Is anyone with a bit more expertise interested in looking into this problem? Thanks, Alec *** imgact_elf.c~ Sun Oct 25 09:44:50 1998 --- imgact_elf.c Sat Nov 28 15:22:28 1998 *************** *** 498,504 **** vmspace->vm_dsize = data_size >> PAGE_SHIFT; vmspace->vm_daddr = (caddr_t)(uintptr_t)data_addr; ! addr = 2L*MAXDSIZ; /* May depend on OS type XXX */ imgp->entry_addr = entry; --- 498,504 ---- vmspace->vm_dsize = data_size >> PAGE_SHIFT; vmspace->vm_daddr = (caddr_t)(uintptr_t)data_addr; ! addr = 2UL*(unsigned)MAXDSIZ; /* May depend on OS type XXX */ imgp->entry_addr = entry; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 16:14:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29669 for freebsd-current-outgoing; Sat, 28 Nov 1998 16:14:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from stade.demon.co.uk (stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29647; Sat, 28 Nov 1998 16:14:11 -0800 (PST) (envelope-from aw1@stade.co.uk) Received: (from aw1@localhost) by stade.demon.co.uk (8.9.1/8.9.1) id UAA01136; Sat, 28 Nov 1998 20:50:32 GMT (envelope-from aw1) Message-ID: <19981128205032.A788@stade.co.uk> Date: Sat, 28 Nov 1998 20:50:32 +0000 From: Adrian Wontroba To: Nicolas Souchu Cc: current@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG Subject: Re: kernel make failure in smbus Reply-To: aw1@stade.co.uk References: <199811222006.MAA00385@rah.star-gate.com> <199811222106.XAA00350@greenpeace.grondar.za> <19981124025011.A832@stade.co.uk> <19981127000541.21781@breizh.prism.uvsq.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981127000541.21781@breizh.prism.uvsq.fr>; from Nicolas Souchu on Fri, Nov 27, 1998 at 12:05:41AM +0000 Organization: Stade Computers Ltd, UK X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 27, 1998 at 12:05:41AM +0000, Nicolas Souchu wrote: > I thought it was solved when we returned to the previous > check_for_i2c_devices() behaviour. What about trying the following patch > which disables iic/smb support? With a 3.0-CURRENT system cvsupped at 0600 GMT today and and freshly installed without the patch, my tv card is mis-identified. With a kernel containing your patch, the card is identified correctly. I'm writing this listening to the radio with xmradio (8-) Significant part of a diff on dmesg output: bktr0: rev 0x12 int a irq 15 on pci0.15.0 -bti2c0: -iicbb0: on bti2c0 -iicbus0: on iicbb0 master-only -Probing for devices on iicbus0: <80> <81> -smbus0: on bti2c0 -IMS TV Turbo, Philips FR1236 NTSC FM tuner. +Hauppauge WinCast/TV, Philips FR1216 PAL tuner, msp3400c stereo. -- Adrian Wontroba, Stade Computers Limited. phone: (+44) 121 681 6677 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 16:18:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00360 for freebsd-current-outgoing; Sat, 28 Nov 1998 16:18:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from float.dyn.ml.org (cs802463-a.gvcl1.bc.wave.home.com [24.64.194.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00354 for ; Sat, 28 Nov 1998 16:18:11 -0800 (PST) (envelope-from jake@float.dyn.ml.org) Received: from float.dyn.ml.org (jake@localhost [127.0.0.1]) by float.dyn.ml.org (8.9.1/8.9.1) with ESMTP id QAA00318 for ; Sat, 28 Nov 1998 16:18:03 -0800 (PST) (envelope-from jake@float.dyn.ml.org) Message-Id: <199811290018.QAA00318@float.dyn.ml.org> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: install: strip: No such file or directory In-reply-to: Your message of "Sat, 28 Nov 1998 15:53:44 EST." <19981128155344.A4298@ns1.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Nov 1998 16:18:03 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I manually cvsup'ed late this morning (EST) and everything appears to be fine > now.. my make world ran through all the way just fine. > Agreed, works fine for me now. -------------------------------------------------------------- >>> elf make world completed on Sat Nov 28 16:13:08 PST 1998 -------------------------------------------------------------- :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 16:51:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03200 for freebsd-current-outgoing; Sat, 28 Nov 1998 16:51:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03172; Sat, 28 Nov 1998 16:51:21 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id TAA44645; Sat, 28 Nov 1998 19:54:21 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sat, 28 Nov 1998 19:54:21 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Ilya Orehov cc: Brian Feldman , phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: fix: Re: kern_clock.c In-Reply-To: <19981128211307.A16994@cnetworks.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 28 Nov 1998, Ilya Orehov wrote: > > Hi! > > I'm another one who can report somewhat new behaviour : > > 1. X now starts up more slowly, with flicker. > 2. usleep(s), where s=1, 10, 100, 10000 sleeps for about 1 second, > regardless of argument. > > I think it is hardware-dependent, since on another machine > (with Intel CPU) usleep() works ok. > > It shows up after recent commit in kern_clock.c: > Edit src/sys/kern/kern_clock.c > Add delta 1.85 98.11.23.09.58.53 phk Thank you, your patch fixed my problems with x11amp at home (AMD-k6-233) and i will test it at work (PII-300) monday. could you file a PR so someone in core takes notice? thank you, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 16:53:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03477 for freebsd-current-outgoing; Sat, 28 Nov 1998 16:53:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from float.dyn.ml.org (cs802463-a.gvcl1.bc.wave.home.com [24.64.194.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03472 for ; Sat, 28 Nov 1998 16:53:10 -0800 (PST) (envelope-from jake@float.dyn.ml.org) Received: from float.dyn.ml.org (jake@localhost [127.0.0.1]) by float.dyn.ml.org (8.9.1/8.9.1) with ESMTP id QAA02513 for ; Sat, 28 Nov 1998 16:52:58 -0800 (PST) (envelope-from jake@float.dyn.ml.org) Message-Id: <199811290052.QAA02513@float.dyn.ml.org> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: USB support In-reply-to: Your message of "Fri, 27 Nov 1998 09:28:18 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Nov 1998 16:52:58 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > USB support has been committed to FreeBSD Current. Feel free to switch > it on (by uncommenting the last block in GENERIC) and report success or > failure. Shouldn't this have gone into LINT instead of GENERIC? LINT is where I would have expected to find it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 17:33:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06955 for freebsd-current-outgoing; Sat, 28 Nov 1998 17:33:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06950 for ; Sat, 28 Nov 1998 17:33:45 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id RAA06624; Sat, 28 Nov 1998 17:33:37 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id RAA27144; Sat, 28 Nov 1998 17:33:36 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 28 Nov 1998 17:33:36 -0800 (PST) Message-Id: <199811290133.RAA27144@vashon.polstra.com> To: wolman@cs.washington.edu Subject: Re: MAXDSIZ limit Newsgroups: polstra.freebsd.current In-Reply-To: <199811282349.PAA16757@miles.cs.washington.edu> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199811282349.PAA16757@miles.cs.washington.edu>, Alec Wolman wrote: > > Hello, > > I'm running FreeBSD 3.0-19981103 SNAP, and I'm running into a problem > or two. I first tried changing MAXDSIZE in my kernel config file to > > MAXDSIZ 2048*1024*1024 > > This causes numerous compilation warnings, presumably because the > calculations being done with the number are signed rather than unsigned. You should have defined MAXDSIZ as something like "2048UL*1024*1024" ^^ to make it explicitly an unsigned long. That's the form that is used in . > Setting it to 2000*1024*1024 eliminates all of those warnings except > for one, in imgact_elf.c. I tried booting this kernel, but it dies. > I don't have the exact error message, but the kernel boots up and > manages to go through the device configuration, but when it gets to > execing an elf process things go haywire. I think the error message > had to do with being unable to start getty. > > When I fixed the compiler warning with the following change, > and I changed MAXDSIZ to 1500*1024*1024, and rebooted, then things > seemed to work ok. However, I suspect that lowering MAXDSIZ rather > than fixing the code is what made things better. Does anyone here > understand why the elf code needs to multiply MAXDSIZ by 2 and then > use that as a base address for something else? Is anyone with a > bit more expertise interested in looking into this problem? The code is loading the dynamic linker at the address 2*MAXDSIZ, which by default works out to 0x40000000. I don't know why it's being loaded there. The traditional place for ELF dynamic linkers (in SVR4) is at 0x08000000, which is "far enough" below the load address for executables, 0x08048000. Would you mind trying it with that statement in imgact_elf.c changed to "addr = 0x08000000"? I'd be interested to know whether it works OK. If it does, we should probably change it. It would have the nice advantage that we could count on the dynamic linker being at a fixed address. We wouldn't have to build it PIC any more, so it would be faster. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 28 20:14:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19644 for freebsd-current-outgoing; Sat, 28 Nov 1998 20:14:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19637 for ; Sat, 28 Nov 1998 20:14:33 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forresta (forrie.ne.mediaone.net [24.128.73.118]) by spook.navinet.net (8.9.1/8.9.1) with SMTP id XAA00346 for ; Sat, 28 Nov 1998 23:14:05 -0500 (EST) Message-Id: <4.1.19981128231200.0092d2e0@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 28 Nov 1998 23:14:20 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Netscape 4.5 core dumps Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This still isn't working correctly, and I'd like to fix it. I'm using XFree86-3.3.3 on FreeBSD-3.0-CURRENT (build world this morning), with WindowMaker (built today also). Whenever I go to run Netscape, I get this in the log: ... /kernel: pid xxxx (netscape), uid xxx: exited on signal 11 It happens regardless of whether I'm root or not, and also happens under other window managers like blackbox. I've updated the libs (giflib) and such that WindowMaker is dependent upon. I'm using tk/tcl 8.1... what is wrong? Thanks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message