From owner-freebsd-current Sun Dec 5 0:43:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id B56DB150F2 for ; Sun, 5 Dec 1999 00:43:30 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id CAA77924; Sun, 5 Dec 1999 02:40:34 -0600 (CST) (envelope-from dan) Date: Sun, 5 Dec 1999 02:40:34 -0600 From: Dan Nelson To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: NFS client zeroing out blocks on write? Message-ID: <19991205024034.A77822@dan.emsphone.com> References: <19991203112518.A43843@dan.emsphone.com> <199912042051.MAA56920@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912042051.MAA56920@apollo.backplane.com>; from "Matthew Dillon" on Sat Dec 4 12:51:59 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Dec 04), Matthew Dillon said: > Hmm. I thought we had fixed all the zeroing problems. Are you sure > you compiled your current up from the latest source? Yep. The machine was a snapshot install from Nov 15 that I rebuilt world on the 23rd, and rebuilt the kernel on Dec 2nd. > I am presuming there are no other clients accessing the output files > while the split is running? Correct. "split" isn't even strictly necessary, but it makes it easier to generate multiple gigs worth of data across an nfsv2 mount point. Depending on my mount options, the glitch is sometimes infrequent enough to only occur once every 5-10 gig of generated data.. > Interesting. It looks very similar to a problem we fixed months ago. > That problem was related only to NFSv3 and mmap(), and you aren't > using mmap() here. It's disturbing to see this problem occur with > both NFSv2 and NFSv3. > > I wonder if the problem occurs between a FreeBSD client and server. Most of my tests have been done on NFSv3 mounts since they are so much faster. I'll try another test run, NFSv2 mounting another FreeBSD box and see what happens. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 1:40:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 67D2415147; Sun, 5 Dec 1999 01:38:05 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id KAA26933; Sun, 5 Dec 1999 10:24:06 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA30805; Sun, 5 Dec 1999 00:45:12 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912042345.AAA30805@yedi.iaf.nl> Subject: Re: Mounting one FS on more than one system In-Reply-To: <199912042044.MAA05073@flamingo.McKusick.COM> from Kirk McKusick at "Dec 4, 1999 12:44:43 pm" To: mckusick@flamingo.McKusick.COM (Kirk McKusick) Date: Sun, 5 Dec 1999 00:45:12 +0100 (CET) Cc: msmith@FreeBSD.ORG, match@elen.utah.edu, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Kirk McKusick wrote ... > Mounting on more than one system is generally problematical unless > you are willing to have all systems read-only. The problem is cache > coherence between the machines. If one changes a block, the other > machines will not see it. Basically, this is why we have the NFS > filesystem. That lets a disk be mounted on one machine, but shared > out to others. If you wanted to write a protocol that would allow > for multiple machines, then you would need to have some central > coordinator running some sort of coherency protocol with a complexity > akin to that of NFS. I wonder how Tru64 is doing it. IIRC V5.0 Tru64 can do a cluster filesystem. A CFS must have solved the coherency issue in some way. Older revs had distributed raw devices (for Oracle and the like) but that had all I/O go through one cluster member that did all the I/O for that DRD. The I/O from the other cluster members was done via the Memory Channel to the DRD-serving machine. Interesting.. Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 2: 3: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id AB93D15280 for ; Sun, 5 Dec 1999 02:02:54 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 5B3622CE4E; Sun, 5 Dec 1999 12:02:23 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 2FE34106; Sun, 5 Dec 1999 12:02:27 +0200 (EET) Date: Sun, 5 Dec 1999 12:02:27 +0200 From: Vallo Kallaste To: "Brian W. Buchanan" Cc: current@freebsd.org Subject: Re: mount(2) broken? Message-ID: <19991205120227.A14872@myhakas.matti.ee> Reply-To: vallo@matti.ee References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Brian W. Buchanan on Sat, Dec 04, 1999 at 08:01:43PM -0800 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 04, 1999 at 08:01:43PM -0800, "Brian W. Buchanan" wrote: > After an unfortunate hard reboot today, the system fscked everything and > then barfed attempting to mount /, claiming it to be unclean. I dropped > to single-user mode and proceeded to re-fsck / and then tried to mount it > again to no avail. Rebooting didn't help things either. Same here, except I'm able to mount after fscking an rebooting. ATA disk and new ata drivers. -- 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 Sun Dec 5 2:14: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 8E6291529D for ; Sun, 5 Dec 1999 02:14:02 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id LAA16758; Sun, 5 Dec 1999 11:12:29 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: vallo@matti.ee Cc: "Brian W. Buchanan" , current@FreeBSD.ORG Subject: Re: mount(2) broken? In-reply-to: Your message of "Sun, 05 Dec 1999 12:02:27 +0200." <19991205120227.A14872@myhakas.matti.ee> Date: Sun, 05 Dec 1999 11:12:29 +0100 Message-ID: <16756.944388749@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991205120227.A14872@myhakas.matti.ee>, Vallo Kallaste writes: >On Sat, Dec 04, 1999 at 08:01:43PM -0800, "Brian W. Buchanan" wrote: > >> After an unfortunate hard reboot today, the system fscked everything and >> then barfed attempting to mount /, claiming it to be unclean. I dropped >> to single-user mode and proceeded to re-fsck / and then tried to mount it >> again to no avail. Rebooting didn't help things either. > >Same here, except I'm able to mount after fscking an rebooting. ATA disk >and new ata drivers. Please update your /dev entries. You need to copy MAKEDEV from the source area (it isn't installed by default) and run it with the right arguments to recreate the device nodes you need. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 2:36:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 5844414EF4 for ; Sun, 5 Dec 1999 02:36:34 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 865B72CE4E; Sun, 5 Dec 1999 12:34:29 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id C24DD106; Sun, 5 Dec 1999 12:34:38 +0200 (EET) Date: Sun, 5 Dec 1999 12:34:38 +0200 From: Vallo Kallaste To: Poul-Henning Kamp Cc: vallo@matti.ee, "Brian W. Buchanan" , current@FreeBSD.ORG Subject: Re: mount(2) broken? Message-ID: <19991205123438.B14872@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <19991205120227.A14872@myhakas.matti.ee> <16756.944388749@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <16756.944388749@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Dec 05, 1999 at 11:12:29AM +0100 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 05, 1999 at 11:12:29AM +0100, Poul-Henning Kamp wrote: > Please update your /dev entries. You need to copy MAKEDEV from the > source area (it isn't installed by default) and run it with the right > arguments to recreate the device nodes you need. Thanks, that was it. Mergemaster was done, but MAKEDEV not. -- 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 Sun Dec 5 6:48: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 45B1C14DC1 for ; Sun, 5 Dec 1999 06:47:56 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.154]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA3570 for ; Sun, 5 Dec 1999 15:47:53 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id PAA41244 for current@freebsd.org; Sun, 5 Dec 1999 15:39:30 +0100 (CET) (envelope-from asmodai) Date: Sun, 5 Dec 1999 15:39:30 +0100 From: Jeroen Ruigrok/Asmodai To: current@freebsd.org Subject: question regarding info Message-ID: <19991205153930.A41237@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG info, you know that GUN program, is supposed to display documentation installed. Well, we place relevant make world info into /use/share/info and I can see those docs a-ok. gcc, bison, gawk, etc. The problem comes when I install ports, they place info documents into /usr/local/info. And when I try to info for example libtool which is present in there it doesn't `know' about the .info file. Now. I know info can accept a longoption to specify the directories to look for, but given that the average user nowadays doesn't seem to bother to man info before looking further and that I am fairly positive that this used to work before and I wonder if something is b0rked. Suggestions and all that are welcome. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project Man is the Dream of the dolphin... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 7: 9:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id DC7D414BF6; Sun, 5 Dec 1999 07:09:55 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id HAA96621; Sun, 5 Dec 1999 07:09:55 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id HAA52158; Sun, 5 Dec 1999 07:09:54 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <199912051509.HAA52158@realtime.exit.com> Subject: Re: Mounting one FS on more than one system In-Reply-To: <199912042345.AAA30805@yedi.iaf.nl> from Wilko Bulte at "Dec 5, 1999 00:45:12 am" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sun, 5 Dec 1999 07:09:54 -0800 (PST) Cc: mckusick@flamingo.McKusick.COM (Kirk McKusick), msmith@FreeBSD.ORG, match@elen.utah.edu, current@FreeBSD.ORG Reply-To: frank@exit.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > I wonder how Tru64 is doing it. IIRC V5.0 Tru64 can do a cluster filesystem. > A CFS must have solved the coherency issue in some way. The CFS filesystem in Tru64 is the same one (more or less, it has been modified for Tru64) that's in the SCO/Compaq NonStop Clusters product and is the same one that was written at Locus (and is the same one in the product I work on). It solves coherency using tokens; in fact, an earlier version of this filesystem is where the OSF got the token mechanism used in DFS. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 7:22:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id EB8841508F for ; Sun, 5 Dec 1999 07:22:50 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.154]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2750 for ; Sun, 5 Dec 1999 16:22:49 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id QAA41618 for current@freebsd.org; Sun, 5 Dec 1999 16:22:45 +0100 (CET) (envelope-from asmodai) Date: Sun, 5 Dec 1999 16:22:44 +0100 From: Jeroen Ruigrok/Asmodai To: current@freebsd.org Subject: Re: question regarding info Message-ID: <19991205162244.E41237@daemon.ninth-circle.org> References: <19991205153930.A41237@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991205153930.A41237@daemon.ninth-circle.org>; from asmodai@wxs.nl on Sun, Dec 05, 1999 at 03:39:30PM +0100 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991205 16:00], Jeroen Ruigrok/Asmodai (asmodai@wxs.nl) wrote: >The problem comes when I install ports, they place info documents into >/usr/local/info. And when I try to info for example libtool which is >present in there it doesn't `know' about the .info file. Now. I know >info can accept a longoption to specify the directories to look for, but >given that the average user nowadays doesn't seem to bother to man info >before looking further and that I am fairly positive that this used to >work before and I wonder if something is b0rked. OK, nothing seems to be borked except that: if you decide to cleanse /usr/local and accidently rm all in info you should be well after your next make world, since the makefile targets in src/share/info/Makefile will make sure that if the file doesn't exist it will get copied (dir-tmpl to dir that is) so that it is ready to register info files. naturally if dir exists and we make world we don't want to overwrite our present dir with a copied over dir-tmpl. The `problem' (as found in mailinglist archives under install targets fail to register info files) is that if the file in question (dir) is zero-length or otherwise does not contain dir-tmpl stuff, the info files cannot register. Mayhaps this info/dir `problem' might be suitable for a FAQ entry? It will surely answer the archived questions about info files failing to install. with thanks to Peter Wemm for pointing some things out. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project A pilgrim must follow in search of a shrine, as he enters inside a cathedral... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 7:51: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 7B3A114BD0 for ; Sun, 5 Dec 1999 07:51:01 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id CAA05610; Mon, 6 Dec 1999 02:56:04 +1100 Date: Mon, 6 Dec 1999 02:50:43 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: disklabel -W now seems to not work(?) 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, 4 Dec 1999, Matthew Jacob wrote: > It seems that in the latest running around with things, disklabel -W > doesn't seem to quite work, at least on the alpha- it seems to set the > label writable, but the next attempt to open the disk sets the label area > non-writable again. It hasn't quite worked for 5 years now (except for additional not workage on alphas). There are layers and layers of bugs and features which combine to make it very difficult to write the label sector except in the normal way: (1) All labels on the disk go away and are reconstructed from scratch on first (re)open ("first open" here means "first on the disk to go from the state with no minors on the disk open to the state with >= 1 minors open"). In particular, the settings of all label write protection flags go away and then com back as "set". Things are done this way in an attempt to make removable media work right even if the driver doesn't support it. Drivers that support removable media also make all the labels go away when the media goes away. Workaround: keep some minor on the disk open while using disklabel -W. (2) The label i/o snooping code checks the validity of labels written to the label sector. You can't write an invalid label to the label sector even if the sector is not write protected. Things are done this way because it's the normal mode of operation for disklabel -r to write and read slightly invalid labels (with relative offsets instead of absolute). The label i/o snooping code watches for these accesses and fixes up the labels. Workaround: duplicate the existing label in the output. (3) The label snooping code is not smart enough to fix up the labels properly for copying slices on the same disk, even if the partition tables are apparently identical. Similarly for copying any partition which contains the label. Workaround: copy everything up to the label sector and everything after the label sector separately. Then use disklabel(8) to adjust the label sector. (4) Write protection and i/o snooping of labels is half-intentionally broken for i/o to the whole disk slice (e.g., /dev/da0). It can be used to work around bugs and features in the write protection and snooping. E.g., the only way to clear a label is to write garbage over it using the whole disk slice. Writing garbage over it using an ordinary slice is prevented by the i/o snooping code. (5) The whole disk slice was broken for alphas in rev.1.63 of subr_diskslice.c, by putting a label on it if the underlying disk contains a label. The underlying disk contains a label in the "dangerously dedicated case". If there is a label, then it is initially write protected, and always snooped on. This closes the back door in (4). > Secondly, how do people feel about having dd(1) use the DIOCWLABEL > argument to enable writing the label area of the disk if the output is a > disk and there is no offset from zero? Unwell. The whole disk device (e.g., /dev/da0) is already entirely write-enabled and unsnooped. except as in (5). Write protection of labels should continue to apply to partitions (e.g., /dev/da0a and /dev/da0c) even if the partitions start at offset 0. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 8: 0:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (Postfix) with ESMTP id 2959A14BD0 for ; Sun, 5 Dec 1999 07:58:56 -0800 (PST) (envelope-from ron@zappa.demon.nl) Received: from win98 (win98.demon.nl [192.168.1.3]) by zappa.demon.nl (Postfix) with SMTP id CD5795C85 for ; Sun, 5 Dec 1999 17:01:46 +0100 (CET) Message-ID: <000801bf3f39$b10d7c40$0301a8c0@demon.nl> From: "Ron Klinkien" To: Subject: Current in loop while compiling MySQL Server 3.22.27 Date: Sun, 5 Dec 1999 16:59:20 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01BF3F42.12C11B60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BF3F42.12C11B60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, After cvsupping and a make kernel/world I decided to update my pkg's, = all goes well until a make in /usr/ports/database/mysql322-server. It hangs half way the compile on... --- cut --- I./../regex -I. -I../include -I.. -I. = -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=3D64 -DDBUG_OFF -O -pipe = -fno-implic it-templates -c sql_parse.cc c++ -DMYSQL_SERVER = -DDEFAULT_MYSQL_HOME=3D"\"/usr/local\"" - DDATADIR=3D"\"/var/db/mysql\"" = -DSHAREDIR=3D"\"/usr/local/share/m ysql\"" -DHAVE_CONFIG_H -I./../include = - I./../regex -I. -I../include -I.. -I. = -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=3D64 -DDBUG_OFF -O -pipe = -fno-implic it-templates -c sql_yacc.cc --- cut --- top showed: --- cut --- last pid: 29984; load averages: 0.93, 0.88, 0.65 up 6+19:45:29 = 16:55:03 59 processes: 2 running, 57 sleeping CPU states: 95.7% user, 0.0% nice, 2.4% system, 0.0% interrupt, 1.9% = idle Mem: 85M Active, 5384K Inact, 29M Wired, 3880K Cache, 11M Buf, 680K Free Swap: 256M Total, 105M Used, 151M Free, 40% Inuse, 80K In =20 PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 29974 root 59 0 156M 84064K RUN 4:21 92.63% 92.63% cc1plus 29976 root 29 0 1928K 964K RUN 0:02 2.76% 2.59% top 189 root 2 0 2824K 576K select 0:18 0.00% 0.00% apache 223 root 2 0 1608K 436K select 0:07 0.00% 0.00% nmbd 180 root 2 0 904K 308K select 0:06 0.00% 0.00% master 183 postfix 2 0 936K 424K select 0:04 0.00% 0.00% qmgr 77 root 2 0 848K 324K select 0:03 0.00% 0.00% syslogd 102 root 10 0 888K 284K nanslp 0:03 0.00% 0.00% cron 74322 root 2 0 1384K 284K select 0:01 0.00% 0.00% telnetd 100 root 2 0 928K 284K select 0:01 0.00% 0.00% inetd 215 mysql 2 0 11888K 124K select 0:00 0.00% 0.00% mysqld 82 daemon 2 0 868K 196K select 0:00 0.00% 0.00% portmap 105 root 2 0 860K 200K select 0:00 0.00% 0.00% lpd 221 root 2 0 2000K 196K select 0:00 0.00% 0.00% smbd 29837 root 10 0 1264K 324K wait 0:00 0.00% 0.00% make 26273 root 10 0 1104K 324K wait 0:00 0.00% 0.00% make 20572 root 10 0 1100K 324K wait 0:00 0.00% 0.00% make --- cut --- any idea what is wrong? Btw after the screencapture's above cc1plus kept eating memory and cpu = cycles ... but i didn't let it finish... zappa# uname -a FreeBSD zappa.demon.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #56: Sun Nov 28 = 16:50:176 Regards, Ron. ------=_NextPart_000_0005_01BF3F42.12C11B60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
After cvsupping and a make kernel/world = I decided=20 to update my pkg's, all goes well until a make in=20 /usr/ports/database/mysql322-server.
 
It hangs half way the compile = on...
--- cut ---
I./../regex         = ;           =20 -I. -I../include -I.. -I.   =20 -D_LARGEFILE_SOURCE
 -D_LARGEFILE64_SOURCE = -D_FILE_OFFSET_BITS=3D64 =20 -DDBUG_OFF  -O -pipe  -fno-implic
it-templates -c=20 sql_parse.cc
c++=20 -DMYSQL_SERVER          = ;           =20 -DDEFAULT_MYSQL_HOME=3D"\"/usr/local\"" =20 -
DDATADIR=3D"\"/var/db/mysql\""      &n= bsp;           &nb= sp;=20 -DSHAREDIR=3D"\"/usr/local/share/m
ysql\""    &nbs= p;            = ;       =20 -DHAVE_CONFIG_H=20 -I./../include          = ;      =20 -
I./../regex         &nb= sp;          =20 -I. -I../include -I.. -I.   =20 -D_LARGEFILE_SOURCE
 -D_LARGEFILE64_SOURCE = -D_FILE_OFFSET_BITS=3D64 =20 -DDBUG_OFF  -O -pipe  -fno-implic
it-templates  -c=20 sql_yacc.cc
--- cut ---
 
top showed:
--- cut ---
last pid: 29984;  load = averages: =20 0.93,  0.88,  0.65    up 6+19:45:29 =20 16:55:03
59 processes:  2 running, 57 sleeping
CPU states: = 95.7%=20 user,  0.0% nice,  2.4% system,  0.0% interrupt,  = 1.9%=20 idle
Mem: 85M Active, 5384K Inact, 29M Wired, 3880K Cache, 11M Buf, = 680K=20 Free
Swap: 256M Total, 105M Used, 151M Free, 40% Inuse, 80K=20 In
 
  PID USERNAME PRI NICE  = SIZE    RES=20 STATE    TIME   WCPU    CPU=20 COMMAND
29974 root      59   = 0  =20 156M 84064K RUN      4:21 92.63% 92.63%=20 cc1plus
29976 root      29   = 0 =20 1928K   964K RUN      0:02  = 2.76% =20 2.59% top
  189 root       = 2  =20 0  2824K   576K select   0:18  0.00%  = 0.00%=20 apache
  223 root       = 2  =20 0  1608K   436K select   0:07  0.00%  = 0.00%=20 nmbd
  180 root       = 2  =20 0   904K   308K select   0:06  = 0.00% =20 0.00% master
  183 postfix    2   = 0  =20 936K   424K select   0:04  0.00%  0.00%=20 qmgr
   77 root       = 2  =20 0   848K   324K select   0:03  = 0.00% =20 0.00% syslogd
  102 root      = 10  =20 0   888K   284K nanslp   0:03  = 0.00% =20 0.00% cron
74322 root       = 2  =20 0  1384K   284K select   0:01  0.00%  = 0.00%=20 telnetd
  100 root       = 2  =20 0   928K   284K select   0:01  = 0.00% =20 0.00% inetd
  215 mysql      = 2   0=20 11888K   124K select   0:00  0.00%  0.00%=20 mysqld
   82 daemon     2  =20 0   868K   196K select   0:00  = 0.00% =20 0.00% portmap
  105 root      =20 2   0   860K   200K select   = 0:00 =20 0.00%  0.00% lpd
  221 = root      =20 2   0  2000K   196K select   = 0:00 =20 0.00%  0.00% smbd
29837 root     =20 10   0  1264K   324K = wait    =20 0:00  0.00%  0.00% make
26273 = root     =20 10   0  1104K   324K = wait    =20 0:00  0.00%  0.00% make
20572 = root     =20 10   0  1100K   324K = wait    =20 0:00  0.00%  0.00% make
--- cut ---
 
any idea what is wrong?
 
Btw after the screencapture's above = cc1plus kept=20 eating memory and cpu cycles ... but i didn't let it = finish...
 
zappa# uname -a
FreeBSD = zappa.demon.nl=20 4.0-CURRENT FreeBSD 4.0-CURRENT #56: Sun Nov 28 16:50:176
 
Regards,
Ron.
 
 
------=_NextPart_000_0005_01BF3F42.12C11B60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 9: 7:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgw.cablecom.ne.jp (mailgw.cablecom.ne.jp [202.248.199.37]) by hub.freebsd.org (Postfix) with ESMTP id 405F414CF7 for ; Sun, 5 Dec 1999 09:07:38 -0800 (PST) (envelope-from motoyuki@snipe.rim.or.jp) Received: from srv2.cablecom.ne.jp by mailgw.cablecom.ne.jp (8.9.3/3.7W) id CAA24938; Mon, 6 Dec 1999 02:07:37 +0900 (JST) Received: from mail.snipe.rim.or.jp by srv2.cablecom.ne.jp (8.9.3/3.7W) id BAA26520; Mon, 6 Dec 1999 01:31:38 +0900 (JST) Received: from sakura.snipe.rim.or.jp (sakura.snipe.rim.or.jp [192.168.11.4]) by mail.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id BAA92830 for ; Mon, 6 Dec 1999 01:31:37 +0900 (JST) Received: from sakura.snipe.rim.or.jp (localhost [127.0.0.1]) by sakura.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id BAA56201 for ; Mon, 6 Dec 1999 01:31:37 +0900 (JST) Message-Id: <199912051631.BAA56201@sakura.snipe.rim.or.jp> To: current@freebsd.org X-Mailer: mh-e on Mule 2.3 / Emacs 19.34.1 Subject: make -DWANT_AOUT world is broken on -current Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Mon, 06 Dec 1999 01:31:37 +0900 From: Motoyuki Konno Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, For a week or so, AOUT library of -current is broken. "make -DWANT_AOUT world" fails at the following point: -------- log starts here -------- -------------------------------------------------------------- >>> Building legacy libraries -------------------------------------------------------------- [snip] cd /usr/src/lib/libncurses; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD \ -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; \ /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC \ -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD \ -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj [snip] cc -o make_keys -O2 -m486 -pipe -I. -I/usr/src/lib/libncurses \ -I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses \ -I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall \ -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS \ -I/usr/obj/aout/usr/src/tmp/usr/include \ /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/make_keys.c __main.o: Undefined symbol `___do_global_ctors' referenced from text segment *** Error code 1 -------- log ends here --------- This error occurs because ___do_global_ctors does not exists in libgcc.a. So, I think the following patch will be needed for -current. -------- patch begins here -------- --- contrib/gcc/libgcc2.c.old Wed Oct 27 18:45:47 1999 +++ contrib/gcc/libgcc2.c Mon Dec 6 00:50:25 1999 @@ -2853,7 +2853,7 @@ } #endif -#ifndef HAS_INIT_SECTION +#if !defined (HAS_INIT_SECTION) || !defined (OBJECT_FORMAT_ELF) /* Run all the global constructors on entry to the program. */ #ifndef ON_EXIT @@ -2917,7 +2917,7 @@ must be in the bss/common section. Long term no port should use those extensions. But many still do. */ -#if !defined(INIT_SECTION_ASM_OP) && !defined(CTOR_LISTS_DEFINED_EXTERNALLY) +#if (!defined(INIT_SECTION_ASM_OP) || !defined(OBJECT_FORMAT_ELF)) && !defined(CTOR_LISTS_DEFINED_EXTERNALLY) #if defined (ASM_OUTPUT_CONSTRUCTOR) || defined (USE_COLLECT2) func_ptr __CTOR_LIST__[2] = {0, 0}; func_ptr __DTOR_LIST__[2] = {0, 0}; --- contrib/gcc/config/i386/freebsd.h.old Sat Oct 16 05:56:19 1999 +++ contrib/gcc/config/i386/freebsd.h Mon Dec 6 00:38:30 1999 @@ -557,3 +557,8 @@ the EGCS crtstuff.c is overcome, we will switch to the non-sjlj-exceptions type exception machanism. */ #define DWARF2_UNWIND_INFO 0 + +/* to assist building libgcc2.c */ +#ifndef __ELF__ +#undef OBJECT_FORMAT_ELF +#endif -------- patch ends here -------- Since -mno-486 option of gcc is deleted, the following patch also needed for "make -DWANT_AOUT world". -------- patch begins here -------- --- sys/i386/boot/biosboot/Makefile.old Mon Dec 6 01:27:59 1999 +++ sys/i386/boot/biosboot/Makefile Sat Aug 28 09:43:09 1999 @@ -8,7 +8,7 @@ BINMODE= 444 CFLAGS= -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 \ - -m386 \ + -mno-486 \ -DBOOTWAIT=${BOOTWAIT} -DTIMEOUT=${TIMEOUT} CFLAGS+= -DBOOTSEG=${BOOTSEG} -DBOOTSTACK=${BOOTSTACK} CFLAGS+= -DDO_BAD144 --- sys/i386/boot/cdboot/Makefile.old Sat Aug 28 09:43:16 1999 +++ sys/i386/boot/cdboot/Makefile Mon Dec 6 01:28:17 1999 @@ -10,7 +10,7 @@ BINMODE= 444 CFLAGS= -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 \ - -mno-486 \ + -m386 \ -DDO_BAD144 -DBOOTWAIT=${BOOTWAIT} -DTIMEOUT=${TIMEOUT} CFLAGS+= -DBOOTSEG=${BOOTSEG} -DBOOTSTACK=${BOOTSTACK} CFLAGS+= -I${.CURDIR}/../biosboot -------- patch ends here -------- -- ------------------------------------------------------------------------ Motoyuki Konno mkonno@res.yamanashi-med.ac.jp (Univ) motoyuki@snipe.rim.or.jp (Home) motoyuki@FreeBSD.ORG (FreeBSD Project) Yamanashi Medical University http://www.freebsd.org/~motoyuki/ (WWW) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 9:26:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgw.cablecom.ne.jp (mailgw.cablecom.ne.jp [202.248.199.37]) by hub.freebsd.org (Postfix) with ESMTP id 32C13153D3 for ; Sun, 5 Dec 1999 09:26:33 -0800 (PST) (envelope-from motoyuki@snipe.rim.or.jp) Received: from srv2.cablecom.ne.jp by mailgw.cablecom.ne.jp (8.9.3/3.7W) id CAA25484; Mon, 6 Dec 1999 02:26:32 +0900 (JST) Received: from mail.snipe.rim.or.jp by srv2.cablecom.ne.jp (8.9.3/3.7W) id CAA00824; Mon, 6 Dec 1999 02:26:31 +0900 (JST) Received: from sakura.snipe.rim.or.jp (sakura.snipe.rim.or.jp [192.168.11.4]) by mail.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id CAA94808 for ; Mon, 6 Dec 1999 02:26:30 +0900 (JST) Received: from sakura.snipe.rim.or.jp (localhost [127.0.0.1]) by sakura.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id CAA00322 for ; Mon, 6 Dec 1999 02:26:30 +0900 (JST) Message-Id: <199912051726.CAA00322@sakura.snipe.rim.or.jp> To: current@freebsd.org X-Mailer: mh-e on Mule 2.3 / Emacs 19.34.1 Subject: patch for Makefile.inc1 Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Mon, 06 Dec 1999 02:26:30 +0900 From: Motoyuki Konno Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have found that lib/aout/libgcc.a is needed to build lib/aout/libncurses, but libgcc.a is not listed in bootstrap-libraries in the Makefile.inc1. So, I think the following patch is needed to build the a.out libraries. -------- patch begins here -------- --- Makefile.inc1.old Fri Nov 26 05:05:07 1999 +++ Makefile.inc1 Mon Dec 6 02:25:16 1999 @@ -662,6 +662,7 @@ # libm must be built before libstdc++. # libmd must be built before libatm, libcrypt, libopie, libradius, libskey, # and libtacplus. +# libgcc must be built before libncurses. # libncurses must be built before libdialog, libedit and libreadline. # libradius must be built before libpam. # libskey must be built before libpam. @@ -713,7 +714,7 @@ # host. # bootstrap-libraries: -.for _lib in ${_csu} lib/libc lib/libncurses \ +.for _lib in ${_csu} lib/libc gnu/lib/libgcc lib/libncurses \ gnu/lib/libregex gnu/lib/libreadline \ lib/libedit ${_libm} \ lib/libmd lib/libcrypt lib/libutil lib/libz usr.bin/lex/lib \ -------- patch ends here -------- -- ------------------------------------------------------------------------ Motoyuki Konno mkonno@res.yamanashi-med.ac.jp (Univ) motoyuki@snipe.rim.or.jp (Home) motoyuki@FreeBSD.ORG (FreeBSD Project) Yamanashi Medical University http://www.freebsd.org/~motoyuki/ (WWW) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 10:10:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 3559A153E0 for ; Sun, 5 Dec 1999 10:10:23 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (cc.publicdata.com.ai [209.88.68.29]) by cypherpunks.ai (Postfix) with ESMTP id A9E253B for ; Sun, 5 Dec 1999 14:10:22 -0400 (AST) Message-ID: <384AAA57.CF98083F@vangelderen.org> Date: Sun, 05 Dec 1999 14:09:27 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Mount problems after lockup 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 having some problems with my -CURRENT box. The problem as described has happened twice already but I cannot reproduce it reliably yet (have to wait for X to lock up). My system locked up solidly (no ping response) while in X so I had to reboot the box. Upon fsck I got the following messages: WARNING: / was not properly dismounted WARNING: R/W mount of / denied. Filesystem is not clean - run fsck I then drop into single user mode to run fsck manually and it simply succeeds, without any errors shown. If I subsequently try to mount R/W I again get the the complaint about the filesystem not being clean as seen above. I then tried fsck -b32 /, a couple of syncs and a reboot and the machine is happy now, apart from some filesystem corruption. (I had to boot an older kernel as /kernel was corrupt.) I ran a disk checker (the one provided in the Adaptec BIOS) and it doesn't find any problems on the the disk. Also, all cables are terminated properly and this configuration has worked for months without problems. I've never seen any SCSI related errors in my logs. Is this likely to be a hardware problem? If so, how come there is no messages in syslog? Could it be that one of the IDE drives has gone bad and this confuses the kernel?? I'd appreciate any clues as to how to approach this correctly. Cheers, Jeroen FreeBSD grolsch.ai 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed Dec 1 08:27:42 GMT 1999 gelderen@grolsch.ai:/usr/src/sys/compile/DESKTOP i386 Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Wed Dec 1 08:27:42 GMT 1999 gelderen@mises.ai:/usr/src/sys/compile/DESKTOP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (450.46-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbff real memory = 268423168 (262132K bytes) avail memory = 257310720 (251280K bytes) Preloaded elf kernel "kernel" at 0xc02fc000. ccd0-3: Concatenated disk drivers Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 11 at device 0.0 on pci1 isab0: at device 4.0 on pci0 isa0: on isab0 ata-pci0: at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 4.2 irq 10 chip1: at device 4.3 on pci0 ahc0: irq 10 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: irq 10 at device 9.0 on pci0 fxp0: Ethernet address 00:90:27:88:b2:dc fxp0: supplying EUI64: 00:90:27:ff:fe:88:b2:dc atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ad0: ATA-4 disk at ata0 as master ad0: 6204MB (12706470 sectors), 13446 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: ATA-4 disk at ata0 as slave ad1: 6204MB (12706470 sectors), 13446 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad2: ATA-3 disk at ata1 as master ad2: 8693MB (17803296 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA33 ad3: ATA-3 disk at ata1 as slave ad3: 8693MB (17803440 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S ad3: 16 secs/int, 1 depth queue, UDMA33 Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) fxp0: starting DAD for fe80:0001::0290:27ff:fe88:b2dc fxp0: DAD complete for fe80:0001::0290:27ff:fe88:b2dc - no duplicates found # Device Mountpoint FStype Options Dump Pass# /dev/da0s1b none swap sw 0 0 /dev/da0s1a / ufs rw 1 1 ^^^^^^ not running soft updates. the others do. /dev/da0s1f /tmp ufs rw 2 2 /dev/da0s1g /usr ufs rw 2 2 /dev/da0s1e /var ufs rw 2 2 /dev/wcd0c /cdrom cd9660 ro,noauto 0 0 /dev/ccd0c /mnt/ccd0 ufs rw 0 2 /dev/wd2s1e /mnt/wd2 ufs rw 0 2 /dev/wd3s1e /mnt/wd3 ufs rw,sync 0 2 proc /proc procfs rw 0 0 -- Jeroen C. van Gelderen - jeroen@vangelderen.org Interesting read: http://www.vcnet.com/bms/ JLF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 10:13:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A7281153F3 for ; Sun, 5 Dec 1999 10:13:53 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA13944; Sun, 5 Dec 1999 10:15:08 -0800 Date: Sun, 5 Dec 1999 10:15:07 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: disklabel -W now seems to not work(?) 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 Wow. Okay. On Mon, 6 Dec 1999, Bruce Evans wrote: > On Sat, 4 Dec 1999, Matthew Jacob wrote: > > > It seems that in the latest running around with things, disklabel -W > > doesn't seem to quite work, at least on the alpha- it seems to set the > > label writable, but the next attempt to open the disk sets the label area > > non-writable again. > > It hasn't quite worked for 5 years now (except for additional not workage I was being polite... :-) > on alphas). There are layers and layers of bugs and features which > combine to make it very difficult to write the label sector except in the > normal way: > ... > > (4) Write protection and i/o snooping of labels is half-intentionally > broken for i/o to the whole disk slice (e.g., /dev/da0). It can be > used to work around bugs and features in the write protection and > snooping. E.g., the only way to clear a label is to write garbage > over it using the whole disk slice. Writing garbage over it using > an ordinary slice is prevented by the i/o snooping code. > > (5) The whole disk slice was broken for alphas in rev.1.63 of > subr_diskslice.c, by putting a label on it if the underlying disk > contains a label. The underlying disk contains a label in the > "dangerously dedicated case". If there is a label, then it is > initially write protected, and always snooped on. This closes > the back door in (4). > > > Secondly, how do people feel about having dd(1) use the DIOCWLABEL > > argument to enable writing the label area of the disk if the output is a > > disk and there is no offset from zero? > > Unwell. The whole disk device (e.g., /dev/da0) is already entirely > write-enabled and unsnooped. except as in (5). Write protection of > labels should continue to apply to partitions (e.g., /dev/da0a and > /dev/da0c) even if the partitions start at offset 0. The reason I brought this all up is that XX0 access would not work for me. The disk had a dangerously dedicated label, but I wanted to overwrite the front of the disk. Impossible. I've noticed this also in the case where you have slices but want to go to a dangerously dedicated label- no can do. Hence a "Well, gee, let's see if disklabel -W will help". Nope. So, what's the answer about what to do? I sure wouldn't want to leap in and 'fix' it because I don't have a good feel for the ins and outs of this stuff here (odd- I usually have a strong sense of knowing what's right, but this house of cards gives me the creeps). I have a hacked dd that works for me, but this can't be the right general solution. Probably if I added my disk tester into the test suites, that would allow one to force this (although by default the tester I use always skips label areas). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 10:14: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id C0AB21544F; Sun, 5 Dec 1999 10:13:55 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 5 Dec 1999 18:13:55 +0000 (GMT) To: current@freebsd.org Cc: imp@village.org, phk@freebsd.org Subject: Should UPDATING tell you to rerun MAKEDEV now? X-Request-Do: Date: Sun, 05 Dec 1999 18:13:54 +0000 From: David Malone Message-ID: <199912051813.aa78561@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recompiled -current today and had to rerun MAKEDEV - I think I've seen phk recommending this to people. Should there be an entry in UPDATING for this? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 10:16:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 62543153E0; Sun, 5 Dec 1999 10:16:38 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id NAA45189; Sun, 5 Dec 1999 13:04:10 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Sun, 5 Dec 1999 13:04:09 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Mark Murray Cc: Kris Kennaway , current@FreeBSD.org Subject: Re: Importing OpenSSL In-Reply-To: <199912040735.JAA11750@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 4 Dec 1999, Mark Murray wrote: > > I think it's high time we expanded our cryptographic support beyond the > > bare minimum of DES - anyone violently disagree? > > On the contrary; I violently agree! > > We need to make OpenSSH work with K5 as a matter of priority. I'm accepting "{,cvs }diff -u"-format patches for the OpenSSH port :) > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Dec 5 10:23:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A242814DFB for ; Sun, 5 Dec 1999 10:23:25 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA18354; Sun, 5 Dec 1999 19:23:13 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Jeroen C. van Gelderen" Cc: current@FreeBSD.ORG Subject: Re: Mount problems after lockup In-reply-to: Your message of "Sun, 05 Dec 1999 14:09:27 -0400." <384AAA57.CF98083F@vangelderen.org> Date: Sun, 05 Dec 1999 19:23:12 +0100 Message-ID: <18352.944418192@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is really a good idea to read the current mailing list if you run current on your machine. copy MAKEDEV from src/etc/MAKEDEV to /dev, and run it to recreate your disk devices. Poul-Henning In message <384AAA57.CF98083F@vangelderen.org>, "Jeroen C. van Gelderen" writes : >Hi, > >I'm having some problems with my -CURRENT box. The problem as >described has happened twice already but I cannot reproduce >it reliably yet (have to wait for X to lock up). > >My system locked up solidly (no ping response) while in X so I >had to reboot the box. Upon fsck I got the following messages: > > WARNING: / was not properly dismounted > > WARNING: R/W mount of / denied. Filesystem is not clean - run fsck > >I then drop into single user mode to run fsck manually and it >simply succeeds, without any errors shown. If I subsequently >try to mount R/W I again get the the complaint about the >filesystem not being clean as seen above. > >I then tried fsck -b32 /, a couple of syncs and a reboot and the >machine is happy now, apart from some filesystem corruption. (I >had to boot an older kernel as /kernel was corrupt.) > >I ran a disk checker (the one provided in the Adaptec BIOS) and >it doesn't find any problems on the the disk. Also, all cables >are terminated properly and this configuration has worked for >months without problems. I've never seen any SCSI related errors >in my logs. > >Is this likely to be a hardware problem? If so, how come there is >no messages in syslog? Could it be that one of the IDE drives has >gone bad and this confuses the kernel?? I'd appreciate any clues >as to how to approach this correctly. > >Cheers, >Jeroen > >FreeBSD grolsch.ai 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed Dec 1 >08:27:42 GMT 1999 > >gelderen@grolsch.ai:/usr/src/sys/compile/DESKTOP i386 >Copyright (c) 1992-1999 The FreeBSD Project. >Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights >reserved. >FreeBSD 4.0-CURRENT #0: Wed Dec 1 08:27:42 GMT 1999 > gelderen@mises.ai:/usr/src/sys/compile/DESKTOP >Timecounter "i8254" frequency 1193182 Hz >CPU: Pentium II/Xeon/Celeron (450.46-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x651 Stepping = 1 > >Features=0x183fbff >real memory = 268423168 (262132K bytes) >avail memory = 257310720 (251280K bytes) >Preloaded elf kernel "kernel" at 0xc02fc000. >ccd0-3: Concatenated disk drivers >Pentium Pro MTRR support enabled >npx0: on motherboard >npx0: INT 16 interface >pcib0: on motherboard >pci0: on pcib0 >pcib1: at device 1.0 on >pci0 >pci1: on pcib1 >vga-pci0: irq 11 at device 0.0 on >pci1 >isab0: at device 4.0 on pci0 >isa0: on isab0 >ata-pci0: at device 4.1 on pci0 >ata-pci0: Busmastering DMA supported >ata0 at 0x01f0 irq 14 on ata-pci0 >ata1 at 0x0170 irq 15 on ata-pci0 >pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 4.2 irq 10 >chip1: at device 4.3 on pci0 >ahc0: irq 10 at device 6.0 on >pci0 >ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs >fxp0: irq 10 at device 9.0 on >pci0 >fxp0: Ethernet address 00:90:27:88:b2:dc >fxp0: supplying EUI64: 00:90:27:ff:fe:88:b2:dc >atkbdc0: at port 0x60-0x6f on isa0 >atkbd0: irq 1 on atkbdc0 >psm0: irq 12 on atkbdc0 >psm0: model Generic PS/2 mouse, device ID 0 >vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on >isa0 >sc0: on isa0 >sc0: VGA <16 virtual consoles, flags=0x200> >sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 >sio0: type 16550A >sio1 at port 0x2f8-0x2ff irq 3 on isa0 >sio1: type 16550A >sio2: not probed (disabled) >sio3: not probed (disabled) >ad0: ATA-4 disk at ata0 as master >ad0: 6204MB (12706470 sectors), 13446 cyls, 15 heads, 63 S/T, 512 B/S >ad0: 16 secs/int, 1 depth queue, UDMA33 >ad1: ATA-4 disk at ata0 as slave >ad1: 6204MB (12706470 sectors), 13446 cyls, 15 heads, 63 S/T, 512 B/S >ad1: 16 secs/int, 1 depth queue, UDMA33 >ad2: ATA-3 disk at ata1 as master >ad2: 8693MB (17803296 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S >ad2: 16 secs/int, 1 depth queue, UDMA33 >ad3: ATA-3 disk at ata1 as slave >ad3: 8693MB (17803440 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S >ad3: 16 secs/int, 1 depth queue, UDMA33 >Mounting root from ufs:/dev/da0s1a >da0 at ahc0 bus 0 target 0 lun 0 >da0: Fixed Direct Access SCSI-2 device >da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing >Enabled >da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) >fxp0: starting DAD for fe80:0001::0290:27ff:fe88:b2dc >fxp0: DAD complete for fe80:0001::0290:27ff:fe88:b2dc - no duplicates >found > ># Device Mountpoint FStype Options Dump >Pass# >/dev/da0s1b none swap sw 0 >0 >/dev/da0s1a / ufs rw 1 >1 > ^^^^^^ > not running soft updates. the others do. >/dev/da0s1f /tmp ufs rw 2 >2 >/dev/da0s1g /usr ufs rw 2 >2 >/dev/da0s1e /var ufs rw 2 >2 >/dev/wcd0c /cdrom cd9660 ro,noauto 0 >0 >/dev/ccd0c /mnt/ccd0 ufs rw 0 >2 >/dev/wd2s1e /mnt/wd2 ufs rw 0 >2 >/dev/wd3s1e /mnt/wd3 ufs rw,sync 0 >2 >proc /proc procfs rw 0 >0 >-- >Jeroen C. van Gelderen - jeroen@vangelderen.org >Interesting read: http://www.vcnet.com/bms/ JLF > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 10:52: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 8D398153FF; Sun, 5 Dec 1999 10:51:57 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-160.skylink.it [194.185.55.160]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id TAA09960; Sun, 5 Dec 1999 19:51:48 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id TAA00828; Sun, 5 Dec 1999 19:52:30 +0100 (CET) (envelope-from hibma@skylink.it) Date: Sun, 5 Dec 1999 19:52:30 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List , bde@FreeBSD.ORG, Warner Losh Subject: bug in sio.c sioattach? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In sioattach the returned values kind of look odd to me. I think it should be different, like below, ENXIO on error, 0 on success. Nick Index: sys/isa/sio.c =================================================================== RCS file: /home/ncvs/src/sys/isa/sio.c,v retrieving revision 1.276 diff -u -w -r1.276 sio.c --- sio.c 1999/12/01 07:38:52 1.276 +++ sio.c 1999/12/05 18:51:10 @@ -991,7 +991,7 @@ if (siosetwater(com, com->it_in.c_ispeed) != 0) { enable_intr(); free(com, M_DEVBUF); - return (0); + return (ENXIO); } enable_intr(); termioschars(&com->it_in); Index: sys/pc98/pc98/sio.c =================================================================== RCS file: /home/ncvs/src/sys/pc98/pc98/sio.c,v retrieving revision 1.113 diff -u -w -r1.113 sio.c --- sio.c 1999/12/01 13:40:03 1.113 +++ sio.c 1999/12/05 18:51:11 @@ -1577,7 +1577,7 @@ obufsize = 2048; } if ((obuf = malloc(obufsize * 2, M_DEVBUF, M_NOWAIT)) == NULL) - return (0); + return ENXIO; bzero(obuf, obufsize * 2); #endif @@ -1660,7 +1660,7 @@ if (siosetwater(com, com->it_in.c_ispeed) != 0) { enable_intr(); free(com, M_DEVBUF); - return (0); + return ENXIO; } enable_intr(); termioschars(&com->it_in); -- hibma@skylink.it n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 11: 5: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 88CBC14CC3 for ; Sun, 5 Dec 1999 11:05:06 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (cc.publicdata.com.ai [209.88.68.29]) by cypherpunks.ai (Postfix) with ESMTP id 60CF73B for ; Sun, 5 Dec 1999 15:05:05 -0400 (AST) Message-ID: <384AB72A.FC02F3D@vangelderen.org> Date: Sun, 05 Dec 1999 15:04:10 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: current@FreeBSD.ORG Subject: Re: Mount problems after lockup References: <18352.944418192@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Jeroen C. van Gelderen" 14:33 Subject: Re: Mount problems after lockup To: Poul-Henning Kamp Poul-Henning Kamp wrote: > It is really a good idea to read the current mailing list > if you run current on your machine. I do. > copy MAKEDEV from src/etc/MAKEDEV to /dev, and run it to recreate > your disk devices. I did just this. The entries in /dev are supposed to be of type char right? They are. Cheers, Jeroen -- Jeroen C. van Gelderen - jeroen@vangelderen.org Interesting read: http://www.vcnet.com/bms/ JLF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 11:42:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 680D8153C8; Sun, 5 Dec 1999 11:42:30 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id GAA11261; Mon, 6 Dec 1999 06:47:24 +1100 Date: Mon, 6 Dec 1999 06:42:09 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Nick Hibma Cc: FreeBSD CURRENT Mailing List , bde@FreeBSD.ORG, Warner Losh Subject: Re: bug in sio.c sioattach? 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, 5 Dec 1999, Nick Hibma wrote: > In sioattach the returned values kind of look odd to me. I think it > should be different, like below, ENXIO on error, 0 on success. sioattach() was once an old-isa attach routine. Old-isa attach routines return 1 on success and 0 on failure. Some probably don't, because the return value is always ignored :-(. sioattach is still too much like an old-isa attach routine :-). Someone changed the main return (1) to return (0), but not the internal one. > Index: sys/isa/sio.c > =================================================================== > RCS file: /home/ncvs/src/sys/isa/sio.c,v > retrieving revision 1.276 > diff -u -w -r1.276 sio.c > --- sio.c 1999/12/01 07:38:52 1.276 > +++ sio.c 1999/12/05 18:51:10 > @@ -991,7 +991,7 @@ > if (siosetwater(com, com->it_in.c_ispeed) != 0) { > enable_intr(); > free(com, M_DEVBUF); > - return (0); > + return (ENXIO); > } > enable_intr(); > termioschars(&com->it_in); Resource deallocation is also missing here. I doubt that this return has ever been executed; it only occurs if malloc() fails. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 12:11:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id E757115415 for ; Sun, 5 Dec 1999 12:11:45 -0800 (PST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id VAA17110 for ; Sun, 5 Dec 1999 21:11:43 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <003001bf3f5d$1ff01780$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: References: <16756.944388749@critter.freebsd.dk> Subject: Sv: mount(2) broken? Date: Sun, 5 Dec 1999 21:12:16 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why isn't MAKEDEV installed by make (install)world? Leif ----- Original Message -----=20 From: Poul-Henning Kamp =20 > Please update your /dev entries. You need to copy MAKEDEV from the > source area (it isn't installed by default) and run it with the right > arguments to recreate the device nodes you need. >=20 > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their = laptop." > FreeBSD -- It will take a long time before progress goes too far! >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 12:14:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 62F4D15415 for ; Sun, 5 Dec 1999 12:14:50 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA18866; Sun, 5 Dec 1999 21:14:12 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Leif Neland" Cc: current@FreeBSD.ORG Subject: Re: Sv: mount(2) broken? In-reply-to: Your message of "Sun, 05 Dec 1999 21:12:16 +0100." <003001bf3f5d$1ff01780$0e00a8c0@neland.dk> Date: Sun, 05 Dec 1999 21:14:12 +0100 Message-ID: <18864.944424852@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <003001bf3f5d$1ff01780$0e00a8c0@neland.dk>, "Leif Neland" writes: >Why isn't MAKEDEV installed by make (install)world? I'm actually starting to wonder about that too... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 12:51: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 5C26315452 for ; Sun, 5 Dec 1999 12:50:58 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id A84221CC7; Mon, 6 Dec 1999 04:50:57 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Richard S. Straka" Cc: current@FreeBSD.ORG Subject: Re: ide dma support not enabled In-Reply-To: Message from "Richard S. Straka" of "Sat, 04 Dec 1999 10:27:28 MST." <38494F00.84C5E0D@home.com> Date: Mon, 06 Dec 1999 04:50:57 +0800 From: Peter Wemm Message-Id: <19991205205057.A84221CC7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Richard S. Straka" wrote: > Bruce Evans wrote: > > > On Fri, 3 Dec 1999, Richard S. Straka wrote: > > > > > A kernel built from current source which was cvsup'ed today at > > > approximately 10:00 pm MST no longer enables DMA support on my > > > IDE drives. A previous kernel from 27 Nov had no problems > > > recognizing and enabling IDE DMA support. > > > > This was broken in rev.1.132 of sys/pci.pci.c. > > > > Quick fix (ifdef away rev.1.132): > > > > diff -c2 pci.c~ pci.c > > *** pci.c~ Sat Dec 4 20:08:44 1999 > > --- pci.c Sat Dec 4 22:28:37 1999 > > *************** > > *** 879,884 **** > > --- 879,888 ---- > > if (name) { > > device_set_desc_copy(dev, name); > > + #ifdef WANT_BROKEN_IDE_PCI > > /* Allow newbus drivers to match "better" */ > > error = -1000; > > + #else > > + error = 0; > > + #endif > > } > > } > > > > Bruce > > > Bruce, > > Works like a champ. IDE DMA is back. > > Thanks, When you next cvsup, please try it again without this patch. It should work now. The problem was that the 'chip*' driver was probing with a higher priority than the ide driver. I'd also suggest that you look into trying out the ata driver. Something like this.. (comment out the wdc and wd devices) controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives #device atapifd0 # ATAPI floppy drives #device atapist0 # ATAPI tape drives options ATA_STATIC_ID #Static dev number like old `wd' driver #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices The new driver is expected to become the default soon and the old one will probably go away. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 13:18:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C609514E09; Sun, 5 Dec 1999 13:18:10 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA34354; Sun, 5 Dec 1999 14:18:08 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA29838; Sun, 5 Dec 1999 14:18:07 -0700 (MST) Message-Id: <199912052118.OAA29838@harmony.village.org> To: David Malone Subject: Re: Should UPDATING tell you to rerun MAKEDEV now? Cc: current@freebsd.org, phk@freebsd.org In-reply-to: Your message of "Sun, 05 Dec 1999 18:13:54 GMT." <199912051813.aa78561@salmon.maths.tcd.ie> References: <199912051813.aa78561@salmon.maths.tcd.ie> Date: Sun, 05 Dec 1999 14:18:07 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912051813.aa78561@salmon.maths.tcd.ie> David Malone writes: : I recompiled -current today and had to rerun MAKEDEV - I think I've : seen phk recommending this to people. Should there be an entry in : UPDATING for this? phk didn't recommend this. Alpha was the platform that needed it, iirc. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 13:40:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id BBBA314E10; Sun, 5 Dec 1999 13:40:42 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id QAA13526; Sun, 5 Dec 1999 16:40:27 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Sun, 5 Dec 1999 16:40:24 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Kris Kennaway Cc: "Jordan K. Hubbard" , current@FreeBSD.org Subject: Re: Importing OpenSSL 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, 4 Dec 1999, Kris Kennaway wrote: > Unfortunately, that will probably mean no openssh out of the box, since it > depends on RSA :-( When the RSA patent runs out, there will be pretty much no problem with having OpenSSL without RSAREF in the tree. In that case, I wouldn't mind being the FreeBSD maintainer for OpenSSH in the tree ;) > > Kris > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Dec 5 13:43:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C09F814E10 for ; Sun, 5 Dec 1999 13:43:23 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id QAA16023; Sun, 5 Dec 1999 16:42:59 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Sun, 5 Dec 1999 16:42:57 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Poul-Henning Kamp Cc: Leif Neland , current@FreeBSD.org Subject: Re: Sv: mount(2) broken? In-Reply-To: <18864.944424852@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Dec 1999, Poul-Henning Kamp wrote: > In message <003001bf3f5d$1ff01780$0e00a8c0@neland.dk>, "Leif Neland" writes: > >Why isn't MAKEDEV installed by make (install)world? > > I'm actually starting to wonder about that too... Just like with the base KLDs, I really think this should be installed at the same time as the kernel (i.e. MAKEDEV part of the kernel install target and modules as part of the kernel build). Then again, if MAKEDEV were to somehow become deprecated, this wouldn't be a problem... :) > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Dec 5 13:46: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 13E7F15428 for ; Sun, 5 Dec 1999 13:45:56 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA26864; Sun, 5 Dec 1999 16:45:45 -0500 (EST) (envelope-from wollman) Date: Sun, 5 Dec 1999 16:45:45 -0500 (EST) From: Garrett Wollman Message-Id: <199912052145.QAA26864@khavrinen.lcs.mit.edu> To: Poul-Henning Kamp Cc: "Leif Neland" , current@FreeBSD.ORG Subject: Re: Sv: mount(2) broken? In-Reply-To: <18864.944424852@critter.freebsd.dk> References: <003001bf3f5d$1ff01780$0e00a8c0@neland.dk> <18864.944424852@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > In message <003001bf3f5d$1ff01780$0e00a8c0@neland.dk>, "Leif Neland" writes: >> Why isn't MAKEDEV installed by make (install)world? > I'm actually starting to wonder about that too... Um, the correct question would have been: * Why isn't MAKEDEV installed by `make install' in a kernel compilation directory? -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 13:54:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id C152615472 for ; Sun, 5 Dec 1999 13:54:11 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA26911; Sun, 5 Dec 1999 16:54:03 -0500 (EST) (envelope-from wollman) Date: Sun, 5 Dec 1999 16:54:03 -0500 (EST) From: Garrett Wollman Message-Id: <199912052154.QAA26911@khavrinen.lcs.mit.edu> To: mjacob@feral.com Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: disklabel -W now seems to not work(?) In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > So, what's the answer about what to do? exec 3; Sun, 5 Dec 1999 14:13:42 -0800 (PST) (envelope-from khetan@link.freebsd.os.org.za) Received: by kg.ops.uunet.co.za (Postfix, from userid 1000) id 8B93116E06; Mon, 6 Dec 1999 00:13:40 +0200 (SAST) Received: from localhost (localhost [127.0.0.1]) by kg.ops.uunet.co.za (Postfix) with ESMTP id 6A8A3112DB for ; Mon, 6 Dec 1999 00:13:40 +0200 (SAST) Date: Mon, 6 Dec 1999 00:13:39 +0200 (SAST) From: Khetan Gajjar X-Sender: khetan@kg.ops.uunet.co.za Reply-To: Khetan Gajjar To: current@FreeBSD.ORG Subject: Re: Sv: mount(2) broken? In-Reply-To: <199912052145.QAA26864@khavrinen.lcs.mit.edu> Message-ID: X-Mobile: +27 82 9907663 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Dec 1999, Garrett Wollman wrote: >Um, the correct question would have been: > >* Why isn't MAKEDEV installed by `make install' in a kernel >compilation directory? Afaik, anyone tracking -current either knows to do this or uses a tool (like mergemaster) that does it for you (I know I do ;-) Installing MAKEDEV also won't solve these problems from what I understand unless the disk devices are re-made. Is it acceptable for MAKEDEV to be installed into /dev (at some stage of the make world, rebuild kernel and install process) and have it re-make at least the disk devices contained in /etc/fstab and /etc/amd.conf ? --- Khetan Gajjar (!kg1779) * khetan@iafrica.com ; khetan@os.org.za http://www.os.org.za/~khetan * Talk/Finger khetan@chain.freebsd.os.org.za FreeBSD enthusiast * http://www2.za.freebsd.org/ Stupidest quote heard : Who is this BSD, and why should we free him ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 14:19:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 8785F14E65; Sun, 5 Dec 1999 14:19:42 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 5 Dec 1999 22:19:41 +0000 (GMT) Date: Sun, 5 Dec 1999 22:19:41 +0000 From: David Malone To: Warner Losh Cc: current@freebsd.org, phk@freebsd.org Subject: Re: Should UPDATING tell you to rerun MAKEDEV now? Message-ID: <19991205221941.A27611@walton.maths.tcd.ie> References: <199912051813.aa78561@salmon.maths.tcd.ie> <199912052118.OAA29838@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912052118.OAA29838@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 05, 1999 at 02:18:07PM -0700, Warner Losh wrote: > In message <199912051813.aa78561@salmon.maths.tcd.ie> David Malone writes: > : I recompiled -current today and had to rerun MAKEDEV - I think I've > : seen phk recommending this to people. Should there be an entry in > : UPDATING for this? > > phk didn't recommend this. Alpha was the platform that needed it, iirc. I just had the same problem as someone else on the list where I booted after a make world and new kernel, and then fsck reported the filesystems clean but mount said they were dirty. I booted from the old kernel, installed and ran the new MAKEDEV and the new kernel ran fine. This is on a 386. Phk just recommended running MAKEDEV to the othe person with this problem. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 14:22: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5309D14E65; Sun, 5 Dec 1999 14:21:54 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA34747; Sun, 5 Dec 1999 15:21:53 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA30632; Sun, 5 Dec 1999 15:21:53 -0700 (MST) Message-Id: <199912052221.PAA30632@harmony.village.org> To: David Malone Subject: Re: Should UPDATING tell you to rerun MAKEDEV now? Cc: current@freebsd.org, phk@freebsd.org In-reply-to: Your message of "Sun, 05 Dec 1999 22:19:41 GMT." <19991205221941.A27611@walton.maths.tcd.ie> References: <19991205221941.A27611@walton.maths.tcd.ie> <199912051813.aa78561@salmon.maths.tcd.ie> <199912052118.OAA29838@harmony.village.org> Date: Sun, 05 Dec 1999 15:21:53 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991205221941.A27611@walton.maths.tcd.ie> David Malone writes: : Phk just recommended running MAKEDEV to the othe person with this problem. Yes. phk has helped me produce a better MAKEDEV need statement for UPDATING. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 14:22: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 07FF615480 for ; Sun, 5 Dec 1999 14:21:56 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id XAA19475 for ; Sun, 5 Dec 1999 23:21:51 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: a couple of patches for review From: Poul-Henning Kamp Date: Sun, 05 Dec 1999 23:21:51 +0100 Message-ID: <19473.944432511@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://phk.freebsd.dk/misc: The bad144.patch removes BAD144 support from the kernel. The adjtime.patch fixes (?) a adjtime(2) related cause of time-travel. 19991205/phk -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 14:42:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0262314A0A for ; Sun, 5 Dec 1999 14:42:13 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA14923; Sun, 5 Dec 1999 14:43:26 -0800 Date: Sun, 5 Dec 1999 14:43:25 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Garrett Wollman Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: disklabel -W now seems to not work(?) In-Reply-To: <199912052154.QAA26911@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good, but like just having popcorn for dinner, somehow unsatisfying... On Sun, 5 Dec 1999, Garrett Wollman wrote: > < said: > > > So, what's the answer about what to do? > > exec 3 dislabel -W xx0 > spam /dev/xx0 > exec 3<&- > > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 14:57: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 99F7F14A0A for ; Sun, 5 Dec 1999 14:57:06 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA28161; Sun, 5 Dec 1999 14:57:06 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA74120; Sun, 5 Dec 1999 14:57:06 -0800 (PST) (envelope-from obrien) Date: Sun, 5 Dec 1999 14:57:05 -0800 From: "David O'Brien" To: Matthew Jacob Cc: current@freebsd.org Subject: Re: disklabel -W now seems to not work(?) Message-ID: <19991205145705.A74087@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjacob@feral.com on Sat, Dec 04, 1999 at 06:48:13PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems that in the latest running around with things, disklabel -W > doesn't seem to quite work, at least on the alpha- it seems to set the This was the topic of my "Fscking disklabel crap" mail to freebsd-alpha on Fri, 26 Nov 1999 11:56:59 -0800, which nobody responded to. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 15: 3:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 733ED14C2F for ; Sun, 5 Dec 1999 15:03:22 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA28194; Sun, 5 Dec 1999 15:03:22 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA74147; Sun, 5 Dec 1999 15:03:21 -0800 (PST) (envelope-from obrien) Date: Sun, 5 Dec 1999 15:03:21 -0800 From: "David O'Brien" To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: disklabel -W now seems to not work(?) Message-ID: <19991205150321.B74087@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bde@zeta.org.au on Mon, Dec 06, 1999 at 02:50:43AM +1100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 06, 1999 at 02:50:43AM +1100, Bruce Evans wrote: > (5) The whole disk slice was broken for alphas in rev.1.63 of > subr_diskslice.c, by putting a label on it if the underlying disk > contains a label. The underlying disk contains a label in the > "dangerously dedicated case". If there is a label, then it is > initially write protected, and always snooped on. This closes > the back door in (4). How do we fix this problem? I keeps from from ``dd if=/dev/da1 of=/dev/da2'' ?? I was very peeved at having to put the disks on a Solaris box to do such a normal Unix task. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 15: 6:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id A79FD14C2F for ; Sun, 5 Dec 1999 15:06:17 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id RAA01754; Sun, 5 Dec 1999 17:06:14 -0600 (CST) (envelope-from dan) Date: Sun, 5 Dec 1999 17:06:14 -0600 From: Dan Nelson To: Ron Klinkien Cc: freebsd-current@FreeBSD.ORG Subject: Re: Current in loop while compiling MySQL Server 3.22.27 Message-ID: <19991205170614.A1496@dan.emsphone.com> References: <000801bf3f39$b10d7c40$0301a8c0@demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <000801bf3f39$b10d7c40$0301a8c0@demon.nl>; from "Ron Klinkien" on Sun Dec 5 16:59:20 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Dec 05), Ron Klinkien said: > Hi, > > After cvsupping and a make kernel/world I decided to update my pkg's, > all goes well until a make in /usr/ports/database/mysql322-server. > > It hangs half way the compile on... > --- cut --- > c++ -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME="\"/usr/local\"" - > DDATADIR="\"/var/db/mysql\"" -DSHAREDIR="\"/usr/local/share/m > ysql\"" -DHAVE_CONFIG_H -I./../include - > I./../regex -I. -I../include -I.. -I. -D_LARGEFILE_SOURCE > -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DDBUG_OFF -O -pipe -fno-implic > it-templates -c sql_yacc.cc > --- cut --- sql_yacc.cc is the parser for all of mysqld, and is a 400K c++ file. It just takes a LONG time to compile. > top showed: > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 29974 root 59 0 156M 84064K RUN 4:21 92.63% 92.63% cc1plus > > any idea what is wrong? nothing's wrong; you just need to let it finish :) Add "--with-low-memory" to the CONFIGURE_ARGS line in the port Makefile if you run out of swap during the compile. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 15:11:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 4425F14CA4 for ; Sun, 5 Dec 1999 15:11:07 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id PAA88129; Sun, 5 Dec 1999 15:10:29 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912052310.PAA88129@gndrsh.dnsmgr.net> Subject: Re: Sv: mount(2) broken? In-Reply-To: <18864.944424852@critter.freebsd.dk> from Poul-Henning Kamp at "Dec 5, 1999 09:14:12 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sun, 5 Dec 1999 15:10:29 -0800 (PST) Cc: leif@neland.dk (Leif Neland), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <003001bf3f5d$1ff01780$0e00a8c0@neland.dk>, "Leif Neland" writes: > >Why isn't MAKEDEV installed by make (install)world? > > I'm actually starting to wonder about that too... Because the source is buried in src/etc, and src/etc is not run as a SUBDIR target. It had always been my intent when I originally wrote world: to add src/etc once src/etc/Makefile was up to snuff as far as a reasonably correct set of install: targets that wouldn't do any more than update non user modified files, like this one. This issue should be looked at, it's was currently sluft off into mergemaster, which is now part of the base system, which means it may now be possible to do a much better job in etc/Makefile of updateing more of the system. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 15:15:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8883E14CAD; Sun, 5 Dec 1999 15:15:18 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA15064; Sun, 5 Dec 1999 15:16:37 -0800 Date: Sun, 5 Dec 1999 15:16:37 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: current@freebsd.org Subject: Re: disklabel -W now seems to not work(?) In-Reply-To: <19991205145705.A74087@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry- I missed it. I was in Kaui. On Sun, 5 Dec 1999, David O'Brien wrote: > > It seems that in the latest running around with things, disklabel -W > > doesn't seem to quite work, at least on the alpha- it seems to set the > > This was the topic of my "Fscking disklabel crap" mail to freebsd-alpha > on Fri, 26 Nov 1999 11:56:59 -0800, which nobody responded to. > > -- > -- David (obrien@NUXI.com) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 15:16:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5EEBD14CA4; Sun, 5 Dec 1999 15:16:42 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA15076; Sun, 5 Dec 1999 15:17:58 -0800 Date: Sun, 5 Dec 1999 15:17:58 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: disklabel -W now seems to not work(?) In-Reply-To: <19991205150321.B74087@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, there *are* workarounds, but I agree that this is broken. I think we had better fix disklabel somehow. I'm just wary of leaping in to 'do it', because I'm sure I'll break more than I fix. On Sun, 5 Dec 1999, David O'Brien wrote: > On Mon, Dec 06, 1999 at 02:50:43AM +1100, Bruce Evans wrote: > > (5) The whole disk slice was broken for alphas in rev.1.63 of > > subr_diskslice.c, by putting a label on it if the underlying disk > > contains a label. The underlying disk contains a label in the > > "dangerously dedicated case". If there is a label, then it is > > initially write protected, and always snooped on. This closes > > the back door in (4). > > How do we fix this problem? I keeps from from > ``dd if=/dev/da1 of=/dev/da2'' ?? I was very peeved at having to put the > disks on a Solaris box to do such a normal Unix task. > > -- > -- David (obrien@NUXI.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 Dec 5 15:18: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EC0D914CA4; Sun, 5 Dec 1999 15:17:59 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA15084; Sun, 5 Dec 1999 15:19:18 -0800 Date: Sun, 5 Dec 1999 15:19:18 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: Bruce Evans , current@FreeBSD.ORG Subject: oh, btw... In-Reply-To: <19991205150321.B74087@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > How do we fix this problem? I keeps from from > ``dd if=/dev/da1 of=/dev/da2'' ?? I was very peeved at having to put the > disks on a Solaris box to do such a normal Unix task. this will fix your dd Index: dd.c =================================================================== RCS file: /home/ncvs/src/bin/dd/dd.c,v retrieving revision 1.27 diff -u -r1.27 dd.c --- dd.c 1999/10/03 18:49:51 1.27 +++ dd.c 1999/12/05 23:17:16 @@ -216,6 +216,16 @@ if (ioctl(io->fd, FIODTYPE, &type) == -1) { err(1, "%s", io->name); } else { +if (type & D_DISK) { +static int one = 1; +#ifndef DIOCWLABEL +#define DIOCWLABEL _IOW('d', 109, int) +#endif +fprintf(stderr, "is a disk\n"); +if (ioctl(io->fd, DIOCWLABEL, &one) < 0) { +perror("DIOCWLABEL"); +} +} if (type & D_TAPE) io->flags |= ISTAPE; else if (type & (D_DISK | D_MEM)) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 16:18: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 8179914D4F for ; Sun, 5 Dec 1999 16:18:00 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id LAA29906; Mon, 6 Dec 1999 11:22:51 +1100 Date: Mon, 6 Dec 1999 11:17:42 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: disklabel -W now seems to not work(?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The reason I brought this all up is that XX0 access would not work for me. > > The disk had a dangerously dedicated label, but I wanted to overwrite the > front of the disk. Impossible. I've noticed this also in the case where > you have slices but want to go to a dangerously dedicated label- no can > do. The second case should work even on alphas unless the first slice already begins at offset 0. The labels and their write protection will go away when the slice table for the dangerously dedicated disk is written (and synced by closing all minors on the disk or by calling the ioctl for this as in sysinstall). At worst you resurrect an old label if you didn't clear it before changing the slice table. > So, what's the answer about what to do? I sure wouldn't want to leap > in and 'fix' it because I don't have a good feel for the ins and outs > of this stuff here (odd- I usually have a strong sense of knowing > what's right, but this house of cards gives me the creeps). The correct fix for the immediate problem of write protection on XX0 is to remove the alpha ifdefs in subr_diskslice.c and then properly fix the bug in the alpha sysinstall which caused them to be hacked in. sysinstall and libdisk have an alarming number of __alpha__ ifdefs. The dangerously dedicated case seems to be required, so it should be possible to use XX0c instad of XX0 for almost everything. The problem is probably that XX0c doesn't exist until you write suitable magic to XX0 (XX0c is the 'c' partition on the first BSD slice, so it doesn't exist if there are no BSD slices). For the i386 the boot sector contains suitable magic. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 16:43:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 6122D14E52; Sun, 5 Dec 1999 16:43:45 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id LAA32057; Mon, 6 Dec 1999 11:48:40 +1100 Date: Mon, 6 Dec 1999 11:43:32 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: disklabel -W now seems to not work(?) In-Reply-To: <19991205150321.B74087@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Dec 1999, David O'Brien wrote: > On Mon, Dec 06, 1999 at 02:50:43AM +1100, Bruce Evans wrote: > > (5) The whole disk slice was broken for alphas in rev.1.63 of > > subr_diskslice.c, by putting a label on it if the underlying disk > How do we fix this problem? I keeps from from > ``dd if=/dev/da1 of=/dev/da2'' ?? I was very peeved at having to put the > disks on a Solaris box to do such a normal Unix task. See other replies. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 17:58:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail3.mia.bellsouth.net (mail3.mia.bellsouth.net [205.152.16.15]) by hub.freebsd.org (Postfix) with ESMTP id 8DBB714E1E; Sun, 5 Dec 1999 17:58:40 -0800 (PST) (envelope-from otterr@bellsouth.net) Received: from bellsouth.net (adsl-77-246-121.mia.bellsouth.net [216.77.246.121]) by mail3.mia.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id UAA04517; Sun, 5 Dec 1999 20:57:35 -0500 (EST) Message-ID: <384AD0E9.735D88C6@bellsouth.net> Date: Sun, 05 Dec 1999 20:54:01 +0000 From: blah X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 18: 6:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 96C8214E16; Sun, 5 Dec 1999 18:06:12 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (cc.publicdata.com.ai [209.88.68.29]) by cypherpunks.ai (Postfix) with ESMTP id 00D353B; Sun, 5 Dec 1999 22:06:10 -0400 (AST) Message-ID: <384B19D9.E77F7E21@vangelderen.org> Date: Sun, 05 Dec 1999 22:05:13 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David Malone Cc: Warner Losh , current@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: Should UPDATING tell you to rerun MAKEDEV now? References: <199912051813.aa78561@salmon.maths.tcd.ie> <199912052118.OAA29838@harmony.village.org> <19991205221941.A27611@walton.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone wrote: > I just had the same problem as someone else on the list where I > booted after a make world and new kernel, and then fsck reported > the filesystems clean but mount said they were dirty. I booted > from the old kernel, installed and ran the new MAKEDEV and the > new kernel ran fine. This is on a 386. Being the other person, I basically had the same problem. I had run MAKEDEV but an IDE disk did go bad which caused a crash which caused /dev corruption which caused the problem I posted... > Phk just recommended running MAKEDEV to the othe person with this > problem. I had to boot a kernel and /dev off a floppy to fix the /dev. Cheers, Jeroen -- Jeroen C. van Gelderen - jeroen@vangelderen.org Interesting read: http://www.vcnet.com/bms/ JLF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 19:13:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta2.snfc21.pbi.net (mta2.snfc21.pbi.net [206.13.28.123]) by hub.freebsd.org (Postfix) with ESMTP id EF48914E08 for ; Sun, 5 Dec 1999 19:13:21 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.116.115]) by mta2.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMA00CAKTV27U@mta2.snfc21.pbi.net> for current@FreeBSD.ORG; Sun, 5 Dec 1999 19:04:17 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 6E3889155D; Sun, 05 Dec 1999 19:04:14 -0800 (PST) Date: Sun, 05 Dec 1999 19:04:14 -0800 (PST) From: Alex Zepeda Subject: Re: mount(2) broken? In-reply-to: <16756.944388749@critter.freebsd.dk> To: Poul-Henning Kamp Cc: vallo@matti.ee, "Brian W. Buchanan" , 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 On Sun, 5 Dec 1999, Poul-Henning Kamp wrote: > >Same here, except I'm able to mount after fscking an rebooting. ATA disk > >and new ata drivers. > > Please update your /dev entries. You need to copy MAKEDEV from the > source area (it isn't installed by default) and run it with the right > arguments to recreate the device nodes you need. I've seen this exact same thing before too. In fact it was two rather annoying things, one being a single solitary last buffer that wouldn't sync and thus left the whole fs marked dirty, and then fsck would check it, see it was fine, but mount wouldn't recognize that it was clean. 'Course I saw this this morning too. Yes, with a new kernel, new devices, ata driver, and new world. 'Twas very odd. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 19:33: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id C5C9A14E1E; Sun, 5 Dec 1999 19:32:59 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id WAA15957; Sun, 5 Dec 1999 22:33:19 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199912060333.WAA15957@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jeroen C. van Gelderen" Cc: David Malone , Warner Losh , current@FreeBSD.ORG, phk@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Should UPDATING tell you to rerun MAKEDEV now? References: <199912051813.aa78561@salmon.maths.tcd.ie> <199912052118.OAA29838@harmony.village.org> <19991205221941.A27611@walton.maths.tcd.ie> <384B19D9.E77F7E21@vangelderen.org> In-reply-to: Your message of "Sun, 05 Dec 1999 22:05:13 -0400." <384B19D9.E77F7E21@vangelderen.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Dec 1999 22:33:19 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > David Malone wrote: > > I just had the same problem as someone else on the list where I > > booted after a make world and new kernel, and then fsck reported > > the filesystems clean but mount said they were dirty. I booted > > from the old kernel, installed and ran the new MAKEDEV and the > > new kernel ran fine. This is on a 386. > > Being the other person, I basically had the same problem. I had run > MAKEDEV but an IDE disk did go bad which caused a crash which caused > /dev corruption which caused the problem I posted... > > > Phk just recommended running MAKEDEV to the othe person with this > > problem. > > I had to boot a kernel and /dev off a floppy to fix the /dev. > I've been in a similar situation, even when not in "crisis" mode, but just when installing new disk drives or moving stuff around. It's sort of annoying that you can't run MAKEDEV with just a root file system mounted. It wants to chown(8) the device nodes as they're created, but it fails since chown is in /usr/sbin, which isn't mounted. If we've got chio(1) in the root file system, couldn't we have chown there too? louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 19:36:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6078514E1E; Sun, 5 Dec 1999 19:36:40 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA29171; Sun, 5 Dec 1999 19:36:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA74713; Sun, 5 Dec 1999 19:36:38 -0800 (PST) (envelope-from obrien) Date: Sun, 5 Dec 1999 19:36:38 -0800 From: "David O'Brien" To: sos@freebsd.org Cc: current@freebsd.org Subject: ATA driver as the default Message-ID: <19991205193638.B74670@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since the ATA driver is destined to be the default in 4.0-R, and we hare hitting the feature freeze date; can we make the switch now? I think it is very important to get ATA into more hands to see where it breaks. It certainly has problems on my Vaio 505 laptop; and I wonder where else it will have problems. Better to find them now than right before release. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 19:38:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx2.asiaonline.net (mx2.asiaonline.net [202.85.0.14]) by hub.freebsd.org (Postfix) with ESMTP id 834FD14F31 for ; Sun, 5 Dec 1999 19:38:42 -0800 (PST) (envelope-from cckok00@stlinux.ouhk.edu.hk) Received: from stlinux.ouhk.edu.hk (ip94-227.asiaonline.net [202.85.94.227]) by mx2.asiaonline.net (8.9.3/8.9.3) with ESMTP id LAA00815 for ; Mon, 6 Dec 1999 11:39:09 +0800 (HKT) Message-ID: <384B305E.6B8443E7@stlinux.ouhk.edu.hk> Date: Mon, 06 Dec 1999 11:41:18 +0800 From: Peter Kok X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 21:55:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.5]) by hub.freebsd.org (Postfix) with ESMTP id 25C8C15055 for ; Sun, 5 Dec 1999 21:55:38 -0800 (PST) (envelope-from blaz@amis.net) Received: from gold.amis.net (gold.amis.net [212.18.37.254]) by server.amis.net (Postfix) with ESMTP id 83371D5C08 for ; Mon, 6 Dec 1999 06:55:21 +0100 (CET) Received: by gold.amis.net (Postfix, from userid 1000) id 8B2D71D87; Sun, 5 Dec 1999 22:35:29 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id 3295F5820 for ; Sun, 5 Dec 1999 22:35:29 +0100 (CET) Date: Sun, 5 Dec 1999 22:35:28 +0100 (CET) From: Blaz Zupan X-Sender: blaz@localhost To: freebsd-current@freebsd.org Subject: No more DMA with ata driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After cvsuping today and making a new kernel, DMA is no longer working on my IDE disk with Soren's ata driver. As far as I can see, the only relevant change between my last working kernel and the new one is a fix for DMA with the pcm driver (RealPlayer now finally works, thanks Grant). Here is what I get: ad0: HARD READ ERROR blk# 46887ad0: DMA problem encountered, fallback to PIO mode ad0: DMA problem encountered, fallback to PIO mode ad0: DMA problem encountered, fallback to PIO mode ad0: DMA problem encountered, fallback to PIO mode ad0: DMA problem encountered, fallback to PIO mode ad0: DMA problem encountered, fallback to PIO mode ad0: DMA problem encountered, fallback to PIO mode ad0: HARD READ ERROR blk# 46999 status=59 error=01 ad0: DMA problem encountered, fallback to PIO mode DMA was working fine on this motherboard (Intel AN430TX) and disk (IBM DTTA-371440) before the recent kernel upgrade (which was done two days ago). Any ideas? Following is my kernel configuration and complete dmesg. machine i386 cpu I586_CPU ident GOLD maxusers 32 options INET options FFS options FFS_ROOT options MFS options MSDOSFS options CD9660 options PROCFS options COMPAT_43 options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options AHC_ALLOW_MEMIO options SOFTUPDATES options COMPAT_LINUX options USER_LDT options TEL_S0_16_3 options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options DDB options INCLUDE_CONFIG_FILE controller isa0 controller pnp0 controller pci0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 controller ahc0 controller scbus0 device da0 device cd0 device pass0 controller ata0 device atadisk0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? device pcm0 device joy0 device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? controller card0 controller pcic0 at isa? port 0x3e0 irq 10 iomem 0xd0000 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 controller smbus0 controller intpm0 device smb0 at smbus? device isic0 at isa? port 0xd80 irq 15 flags 3 device ed0 device wi0 #controller ppc0 at isa? port? flags 0x40 irq 7 #controller ppbus0 #device lpt0 #device plip0 #device ppi0 #controller vpo0 controller uhci0 controller usb0 device ugen0 device uhid0 device ukbd0 device ulpt0 controller umass0 device ums0 pseudo-device loop pseudo-device ether pseudo-device tun pseudo-device ppp 2 pseudo-device sppp 4 pseudo-device pty pseudo-device gzip pseudo-device bpf pseudo-device streams pseudo-device "i4bq921" pseudo-device "i4bq931" pseudo-device "i4b" pseudo-device "i4btrc" 4 pseudo-device "i4bctl" pseudo-device "i4brbch" 4 pseudo-device "i4btel" 2 pseudo-device "i4bipr" 4 pseudo-device "i4bisppp" 4 pseudo-device vinum options VINUMDEBUG Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #2: Sun Dec 5 21:59:47 CET 1999 blaz@gold.amis.net:/delo/src/sys/compile/GOLD Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (232.88-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 61136896 (59704K bytes) Preloaded elf kernel "kernel" at 0xc03cf000. Intel Pentium detected, installing workaround for F00F bug vinum: loaded npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 uhci0: irq 9 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: at device 7.3 on pci0 intpm0: I/O mapped 7000 intpm0: intr SMI disabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 8000 ed0: irq 9 at device 13.0 on pci0 ed0: address 00:80:48:ca:93:de, type NE2000 (16 bit) ahc0: irq 9 at device 14.0 on pci0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs vga-pci0: irq 11 at device 15.0 on pci0 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3d0-0x3db iomem 0xb8000-0xbffff on isa0 sc0: on isa0 sc0: CGA <16 virtual consoles, flags=0x200> pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A isic0 at port 0xd80 irq 15 flags 0x3 on isa0 isic0: Teles S0/16.3 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x960) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x160, AddrB=0x560) pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38f,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 joy0: at port 0x201 on isa0 i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached ad0: ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 pccard: card inserted, slot 0 Mounting root from ufs:/dev/wd0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15) da1: 1547MB (3170160 512 byte sectors: 255H 63S/T 197C) cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) ad0: HARD READ ERROR blk# 46887ad0: DMA problem encountered, fallback to PIO mode ad0: DMA problem encountered, fallback to PIO mode ad0: DMA problem encountered, fallback to PIO mode ad0: DMA problem encountered, fallback to PIO mode ad0: DMA problem encountered, fallback to PIO mode ad0: DMA problem encountered, fallback to PIO mode ad0: DMA problem encountered, fallback to PIO mode ad0: HARD READ ERROR blk# 46999 status=59 error=01 ad0: DMA problem encountered, fallback to PIO mode vinum: reading configuration from /dev/da1s1e vinum: updating configuration from /dev/da0s1e wi0: at port 0x240-0x27f irq 7 slot 0 on pccard0 wi0: Ethernet address: 00:60:1d:04:af:db Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 22: 4:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 251F214DDA for ; Sun, 5 Dec 1999 22:04:04 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id HAA21671 for freebsd-current@FreeBSD.ORG; Mon, 6 Dec 1999 07:04:03 +0100 (CET) (envelope-from olli) Date: Mon, 6 Dec 1999 07:04:03 +0100 (CET) From: Oliver Fromme Message-Id: <199912060604.HAA21671@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: pcm: Soundcard not recognized anymore Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have today upgraded a machine from some 3.1-stable to the latest -current snapshot (19991204). Now the ISA PnP soundcard doesn't work anymore (it worked fine before, using the pcm driver). It is an Avance Logic ALS100+ card. This is from dmesg: unknown0: at port 0x220-0x22f irq 5 drq 5,1 on isa0 unknown1: at port 0x388-0x38f on isa0 unknown2: at port 0x200-0x201 on isa0 unknown3: at port 0x330-0x331 irq 9 on isa0 `pnpinfo` output is attached below. Please let me know if any further information is required to get this thing working again. I hope this is only a matter of a missing vendor ID or something like that... Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID ALS0001 (0x01009305), Serial Number 0x01000000 PnP Version 1.0, Vendor Version 0 Device Description: ALS100 Media Audio Controller Logical Device ID: @@@0001 0x01000000 #0 Device supports I/O Range Check TAG Start DF Good Configuration FIXED I/O base address 0x220 length 0x10 IRQ: 5 - only one type (true/edge) DMA: channel(s) 5 16-bit, not a bus master, , count by word, Type F DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Type F TAG Start DF Acceptable Configuration I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [not 16-bit addr] IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Type F DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type F TAG Start DF Sub-optimal Configuration I/O Range 0x100 .. 0x3f0, alignment 0x10, len 0x10 [not 16-bit addr] IRQ: 5 7 9 10 11 12 15 IRQ: High true edge sensitive IRQ: Low true edge sensitive IRQ: High true level sensitive IRQ: Low true level sensitive DMA: channel(s) 0 1 3 5 6 7 8/16-bit, not a bus master, count by byte, count by word, Type F TAG End DF Logical Device ID: @H@0001 0x01000001 #1 Device supports I/O Range Check FIXED I/O base address 0x388 length 0x8 Logical Device ID: @P@0001 0x01000002 #2 Device supports I/O Range Check FIXED I/O base address 0x200 length 0x2 Logical Device ID: @X@0001 0x01000003 #3 Device supports I/O Range Check TAG Start DF Good Configuration FIXED I/O base address 0x330 length 0x2 IRQ: 9 - only one type (true/edge) TAG Start DF Acceptable Configuration I/O Range 0x100 .. 0x3f0, alignment 0x10, len 0x2 [not 16-bit addr] IRQ: 5 7 9 10 11 12 15 IRQ: High true edge sensitive IRQ: Low true edge sensitive IRQ: High true level sensitive IRQ: Low true level sensitive TAG End DF End Tag Successfully got 30 resources, 4 logical fdevs -- card select # 0x0001 CSN ALS0001 (0x01009305), Serial Number 0x01000000 Logical device #0 IO: 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 IRQ 5 0 DMA 5 1 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #2 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #3 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 9 0 DMA 4 4 IO range check 0x00 activate 0x01 -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 22:36:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 234CA14CB1 for ; Sun, 5 Dec 1999 22:36:44 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id BAA13606; Mon, 6 Dec 1999 01:36:03 -0500 (EST) (envelope-from chuckr@mat.net) Date: Mon, 6 Dec 1999 01:36:03 -0500 (EST) From: Chuck Robey To: Poul-Henning Kamp Cc: "Jeroen C. van Gelderen" , current@FreeBSD.ORG Subject: Re: Mount problems after lockup In-Reply-To: <18352.944418192@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Dec 1999, Poul-Henning Kamp wrote: > > It is really a good idea to read the current mailing list > if you run current on your machine. > > copy MAKEDEV from src/etc/MAKEDEV to /dev, and run it to recreate > your disk devices. > > Poul-Henning Excuse me, Poul, I have to switch back and forth for a day on one machine, can I run MAKEDEV to prepare for the new devs without ruining the system for a kernel that's about 4 months old? [No, it's not my machine, I run current -- real current]. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 22:48:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 963B514CB1 for ; Sun, 5 Dec 1999 22:48:37 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id HAA21217; Mon, 6 Dec 1999 07:47:47 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Chuck Robey Cc: "Jeroen C. van Gelderen" , current@FreeBSD.ORG Subject: Re: Mount problems after lockup In-reply-to: Your message of "Mon, 06 Dec 1999 01:36:03 EST." Date: Mon, 06 Dec 1999 07:47:47 +0100 Message-ID: <21215.944462867@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Chuck Rob ey writes: >On Sun, 5 Dec 1999, Poul-Henning Kamp wrote: > >> >> It is really a good idea to read the current mailing list >> if you run current on your machine. >> >> copy MAKEDEV from src/etc/MAKEDEV to /dev, and run it to recreate >> your disk devices. >> >> Poul-Henning > >Excuse me, Poul, I have to switch back and forth for a day on one machine, >can I run MAKEDEV to prepare for the new devs without ruining the system >for a kernel that's about 4 months old? No, 4 months is too old. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 5 23:11:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 4D7FA14C0C for ; Sun, 5 Dec 1999 23:11:37 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id CAA13762; Mon, 6 Dec 1999 02:10:57 -0500 (EST) (envelope-from chuckr@mat.net) Date: Mon, 6 Dec 1999 02:10:57 -0500 (EST) From: Chuck Robey To: Poul-Henning Kamp Cc: "Jeroen C. van Gelderen" , current@FreeBSD.ORG Subject: Re: Mount problems after lockup In-Reply-To: <21215.944462867@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Dec 1999, Poul-Henning Kamp wrote: > In message , Chuck Rob > ey writes: > >On Sun, 5 Dec 1999, Poul-Henning Kamp wrote: > > > >> > >> It is really a good idea to read the current mailing list > >> if you run current on your machine. > >> > >> copy MAKEDEV from src/etc/MAKEDEV to /dev, and run it to recreate > >> your disk devices. > >> > >> Poul-Henning > > > >Excuse me, Poul, I have to switch back and forth for a day on one machine, > >can I run MAKEDEV to prepare for the new devs without ruining the system > >for a kernel that's about 4 months old? > > No, 4 months is too old. Then if I have to do this in multiple steps, can I upgrade to current as it was before you changed out the bdevs-cdevs (I'll hunt down the commit) and do that in one step, get it working, then MAKEDEV and do another step taking it the rest of the way to current? I don't want to move it with no ability to fall back on an old kernel, as I step it towards current. > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 0:12:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3AEE515129 for ; Mon, 6 Dec 1999 00:12:17 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA21370; Mon, 6 Dec 1999 09:11:38 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Chuck Robey Cc: "Jeroen C. van Gelderen" , current@FreeBSD.ORG Subject: Re: Mount problems after lockup In-reply-to: Your message of "Mon, 06 Dec 1999 02:10:57 EST." Date: Mon, 06 Dec 1999 09:11:37 +0100 Message-ID: <21368.944467897@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Chuck Rob ey writes: >> >Excuse me, Poul, I have to switch back and forth for a day on one machine, >> >can I run MAKEDEV to prepare for the new devs without ruining the system >> >for a kernel that's about 4 months old? >> >> No, 4 months is too old. > >Then if I have to do this in multiple steps, can I upgrade to current as >it was before you changed out the bdevs-cdevs (I'll hunt down the commit) >and do that in one step, get it working, then MAKEDEV and do another step >taking it the rest of the way to current? Make a backup. Upgrade your kernel first. Then make world Then MAKEDEV. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 1:34:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 250AF151A3 for ; Mon, 6 Dec 1999 01:34:34 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup6-49.iptelecom.net.ua [212.9.227.113]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA10065 for ; Mon, 6 Dec 1999 11:38:23 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id LAA23950 for ; Mon, 6 Dec 1999 11:34:00 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <384B8305.8BF239C7@altavista.net> Date: Mon, 06 Dec 1999 11:33:57 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Removal of egcs 1.12 from the base tree Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody could clarify why egcs is still in the base tree after several months of gcc2.95.2 as base compiler? Users with disk space constrains (including me) would definitely love to see those 34 MB being freed... -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 1:51:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 56FC214A2D; Mon, 6 Dec 1999 01:51:22 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA18467; Mon, 6 Dec 1999 09:59:05 GMT (envelope-from dfr@nlsystems.com) Date: Mon, 6 Dec 1999 09:59:05 +0000 (GMT) From: Doug Rabson To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: a couple of patches for review In-Reply-To: <19473.944432511@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Dec 1999, Poul-Henning Kamp wrote: > > http://phk.freebsd.dk/misc: > > The bad144.patch removes BAD144 support from the kernel. > > The adjtime.patch fixes (?) a adjtime(2) related cause of time-travel. > > 19991205/phk The bad144 stuff looks straightforward for the most part. The change in vfs_conf.c seems unrelated - perhaps this should be committed separately? I don't understand the adjtime change enough to give you a worthwhile review, sorry. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 1:53:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 90BC114EFC for ; Mon, 6 Dec 1999 01:53:05 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA21803; Mon, 6 Dec 1999 10:52:58 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Doug Rabson Cc: current@freebsd.org Subject: Re: a couple of patches for review In-reply-to: Your message of "Mon, 06 Dec 1999 09:59:05 GMT." Date: Mon, 06 Dec 1999 10:52:58 +0100 Message-ID: <21801.944473978@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dou g Rabson writes: >On Sun, 5 Dec 1999, Poul-Henning Kamp wrote: > >> >> http://phk.freebsd.dk/misc: >> >> The bad144.patch removes BAD144 support from the kernel. >> >> The adjtime.patch fixes (?) a adjtime(2) related cause of time-travel. >> >> 19991205/phk > >The bad144 stuff looks straightforward for the most part. The change in >vfs_conf.c seems unrelated - perhaps this should be committed separately? Yup, that one is a leak from another one of my source trees. Sorry. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 2:19:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 026DF15477; Mon, 6 Dec 1999 02:19:22 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id BF4A32CE58; Mon, 6 Dec 1999 12:19:18 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 96839106; Mon, 6 Dec 1999 12:19:16 +0200 (EET) Date: Mon, 6 Dec 1999 12:19:16 +0200 From: Vallo Kallaste To: David O'Brien Cc: sos@freebsd.org, current@freebsd.org Subject: Re: ATA driver as the default Message-ID: <19991206121916.A17569@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <19991205193638.B74670@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19991205193638.B74670@dragon.nuxi.com>; from David O'Brien on Sun, Dec 05, 1999 at 07:36:38PM -0800 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 05, 1999 at 07:36:38PM -0800, David O'Brien wrote: > Since the ATA driver is destined to be the default in 4.0-R, and we hare > hitting the feature freeze date; can we make the switch now? > > I think it is very important to get ATA into more hands to see where it > breaks. It certainly has problems on my Vaio 505 laptop; and I wonder > where else it will have problems. Better to find them now than right > before release. It doesn't know about SiS 5591 PCI IDE controller, the wdc controller knows. I'm speaking about boot messages, nothing else. Furthermore the wdc driver sets up UDMA mode on my UDMA capable disks, ata driver doesn't. It claims that busmastering DMA is supported and sets up WDMA2 mode instead, I think it's normal as it currently doesn't know about 5591. The WDMA2 isn't really that bad and otherwise I'm using ata driver quite happily. Just FYI. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 3:22:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatesrv.rz.unibw-muenchen.de (gatesrv.RZ.UniBw-Muenchen.de [137.193.10.21]) by hub.freebsd.org (Postfix) with ESMTP id 6E14D150FF for ; Mon, 6 Dec 1999 03:22:38 -0800 (PST) (envelope-from didi@Xterminator.STUDFB.UniBw-Muenchen.de) Received: from XTerminator.StudFb.UniBw-Muenchen.De (Xterminator.STUDFB.UniBw-Muenchen.de [137.193.211.64]) by gatesrv.rz.unibw-muenchen.de (8.9.1b+Sun/8.9.3) with ESMTP id MAA06382 for ; Mon, 6 Dec 1999 12:22:37 +0100 (MET) Received: from didi.STUDFB.UniBw-Muenchen.de (didi.STUDFB.UniBw-Muenchen.de [137.193.211.220]) by XTerminator.StudFb.UniBw-Muenchen.De (8.8.7/8.8.6) with SMTP id MAA32162 for ; Mon, 6 Dec 1999 12:21:51 +0100 From: Dieter Rothacker To: current@FreeBSD.ORG Subject: Old Libs...? Date: Mon, 06 Dec 1999 12:22:35 +0100 Organization: Organized ? No way... Message-ID: X-Mailer: Forte Agent 1.6/32.661 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have just installed 4.0-SNAP-19991203. I noticed that some packages (e.g. samba, bash2) complain about missing shared libs (e.g. libreadline.so.3 needed and .4 is installed). Reading similar things in the mailing list archive, I assume that I have to install the old libs from a 3.3-stable BIN. Correct? How do I find out which bin-archives I really need to download? I looked at the mtree-file, but did not find the exact arc files mentioned. I do not want to download all bin.* files. Please forgive me if the solution should be obvious, it is my first try at FreeBSD. -- Dieter Rothacker To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 3:29:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatesrv.rz.unibw-muenchen.de (gatesrv.RZ.UniBw-Muenchen.de [137.193.10.21]) by hub.freebsd.org (Postfix) with ESMTP id 3AB6E151E8; Mon, 6 Dec 1999 03:29:21 -0800 (PST) (envelope-from didi@Xterminator.STUDFB.UniBw-Muenchen.de) Received: from XTerminator.StudFb.UniBw-Muenchen.De (Xterminator.STUDFB.UniBw-Muenchen.de [137.193.211.64]) by gatesrv.rz.unibw-muenchen.de (8.9.1b+Sun/8.9.3) with ESMTP id MAA08427; Mon, 6 Dec 1999 12:29:20 +0100 (MET) Received: from didi.STUDFB.UniBw-Muenchen.de (didi.STUDFB.UniBw-Muenchen.de [137.193.211.220]) by XTerminator.StudFb.UniBw-Muenchen.De (8.8.7/8.8.6) with SMTP id MAA32495; Mon, 6 Dec 1999 12:28:34 +0100 From: Dieter Rothacker To: current@FreeBSD.ORG Cc: obrien@FreeBSD.ORG Subject: Re: ATA driver as the default Date: Mon, 06 Dec 1999 12:29:18 +0100 Organization: Organized ? No way... Message-ID: References: <19991205193638.B74670@dragon.nuxi.com> In-Reply-To: <19991205193638.B74670@dragon.nuxi.com> X-Mailer: Forte Agent 1.6/32.661 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Dec 1999 19:36:38 -0800, David O'Brien wrote: >Since the ATA driver is destined to be the default in 4.0-R, and we hare >hitting the feature freeze date; can we make the switch now? > >I think it is very important to get ATA into more hands to see where it >breaks. It certainly has problems on my Vaio 505 laptop; and I wonder >where else it will have problems. Better to find them now than right >before release. So far, the ATA driver works flawlessly with my PIIX3 and my Abit Hotrod66 PCI card (HPT366 chip). When I have my system set up completely, I will do some stress tests. The linux driver for the HPT366 is seriously broken, it never got the IRQ handling right when both channels on the chip were used and actually transferred data in parallel (I have one IBM UDMA66 drive on each channel) - I hope FreeBSD's driver is better :-) -- Dieter Rothacker To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 4:35:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id BD19F14FB0 for ; Mon, 6 Dec 1999 04:35:47 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 6 Dec 1999 12:35:43 +0000 (GMT) Date: Mon, 6 Dec 1999 12:35:43 +0000 From: David Malone To: Maxim Sobolev Cc: current@freebsd.org Subject: Re: Removal of egcs 1.12 from the base tree Message-ID: <19991206123543.A36163@walton.maths.tcd.ie> References: <384B8305.8BF239C7@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <384B8305.8BF239C7@altavista.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 06, 1999 at 11:33:57AM +0200, Maxim Sobolev wrote: > Does anybody could clarify why egcs is still in the base tree after several > months of gcc2.95.2 as base compiler? Users with disk space constrains > (including me) would definitely love to see those 34 MB being freed... I wonder if there is any interest in getting gcov turned on in gcc-2.95.2. The stuff about it is in the info pages, and it seems to work OK. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 4:46:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 3F6E614FB0; Mon, 6 Dec 1999 04:46:45 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id GAA01569; Mon, 6 Dec 1999 06:46:28 -0600 (CST) (envelope-from dick) Date: Mon, 6 Dec 1999 06:46:28 -0600 From: "Richard Seaman, Jr." To: Vallo Kallaste Cc: "David O'Brien" , sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: ATA driver as the default Message-ID: <19991206064628.G44207@tar.com> References: <19991205193638.B74670@dragon.nuxi.com> <19991206121916.A17569@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991206121916.A17569@myhakas.matti.ee> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 06, 1999 at 12:19:16PM +0200, Vallo Kallaste wrote: > It doesn't know about SiS 5591 PCI IDE controller, the wdc controller > knows. I'm speaking about boot messages, nothing else. Furthermore the > wdc driver sets up UDMA mode on my UDMA capable disks, ata driver > doesn't. It claims that busmastering DMA is supported and sets up WDMA2 > mode instead, I think it's normal as it currently doesn't know about > 5591. The WDMA2 isn't really that bad and otherwise I'm using ata driver > quite happily. Just FYI. The one time I tried ata with my SiS 5591 board I got PIO, no DMA at all. With wd I get UDMA. This was about 2-3 weeks ago. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 5:41:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 809D8152ED for ; Mon, 6 Dec 1999 05:41:19 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11uyO3-0007vB-00; Mon, 06 Dec 1999 15:41:07 +0200 From: Sheldon Hearn To: Dieter Rothacker Cc: current@FreeBSD.ORG Subject: Re: Old Libs...? In-reply-to: Your message of "Mon, 06 Dec 1999 12:22:35 +0100." Date: Mon, 06 Dec 1999 15:41:07 +0200 Message-ID: <30452.944487667@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 06 Dec 1999 12:22:35 +0100, Dieter Rothacker wrote: > I have just installed 4.0-SNAP-19991203. I noticed that some packages (e.g. > samba, bash2) complain about missing shared libs (e.g. libreadline.so.3 > needed and .4 is installed). [...] > I assume that I have to install the old libs from a 3.3-stable BIN. Yes. Apparently, the appropriate libraries will be added to compat3x at the last moment. :-) > How do I find out which bin-archives I really need to download? I looked at > the mtree-file, but did not find the exact arc files mentioned. I do not > want to download all bin.* files. Don't you have a trusted 3.3-STABLE/3.3-RELEASE machine you can grab them from? I ask because I don't think there's an easy way to avoid sucking down the whole of bin. :-( > Please forgive me if the solution should be obvious, it is my first > try at FreeBSD. Ah, then that's where you've gone wrong. For your first try at FreeBSD, you should probably be trying 3.3-RELEASe or a 3.3 snapshot. The 4.0 branch is still considered the bleeding edge. And as you've discovered, it tends to make you bleed. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 6:18:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from cloudbase.sixforty.co.uk (cloudbase.sixforty.co.uk [194.207.180.10]) by hub.freebsd.org (Postfix) with ESMTP id 3A4AE14A05; Mon, 6 Dec 1999 06:18:37 -0800 (PST) (envelope-from l.farr@epcdirect.co.uk) Received: from monkey (pepe.sixforty.co.uk [194.207.180.202]) by cloudbase.sixforty.co.uk (8.9.3/8.8.7) with SMTP id OAA29576; Mon, 6 Dec 1999 14:02:11 GMT Reply-To: From: "Lawrence Farr" To: Cc: Subject: Samba Performance Date: Mon, 6 Dec 1999 14:17:33 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have installed a couple of FreeBSD machines using 3.3-Release, which have Appletalk over IP and samba access to them. On a write to a shared disk, the Macs can write at about 9000kb/sec (Measured with Helios LAN test). From a P3-500 via samba over switched fast ethernet I get about 100Kb/sec. to the same disk. I have added the usual socket options, and upped the recieve buffer size. On a read from the same machine, it is comparable to the Mac. The same machine running Linux was about equal on both. I have also made samba from source, which made no difference. Any bright ideas? Lawrence Farr EPC Direct T:01179666123 F:01179666111 M:07970780901 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 7:21:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A6E314DA6; Mon, 6 Dec 1999 07:21:25 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup7-8.iptelecom.net.ua [212.9.227.136]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id QAA26623; Mon, 6 Dec 1999 16:59:03 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id QAA55100; Mon, 6 Dec 1999 16:52:38 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <384BCDB1.BD599C68@altavista.net> Date: Mon, 06 Dec 1999 16:52:33 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: l.farr@epcdirect.co.uk Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Samba Performance References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lawrence Farr wrote: > I have installed a couple of FreeBSD machines using 3.3-Release, which have > Appletalk over IP and samba access to them. On a write to a shared disk, the > Macs can write at about 9000kb/sec (Measured with Helios LAN test). From a > P3-500 via samba over switched fast ethernet I get about 100Kb/sec. to the > same disk. > > I have added the usual socket options, and upped the recieve buffer size. On > a read from the same machine, it is comparable to the Mac. > > The same machine running Linux was about equal on both. I have also made > samba from source, which made no difference. > > Any bright ideas? Try to look into the ports/samba/patches for the patch-ah file (which provided to resolve such misbehaviour). If that file doesn't exist than either try to cvsup your ports, or manually add following patch and recompile/reinstall samba: -----patch.ah. Cut Here------------ --- lib/util_sock.c.orig Wed Sep 22 10:52:50 1999 +++ lib/util_sock.c Wed Sep 22 11:30:18 1999 @@ -28,6 +28,9 @@ extern int sslFd; #endif /* WITH_SSL */ +#undef MSG_WAITALL +#define MSG_WAITALL 0 + extern int DEBUGLEVEL; BOOL passive = False; -----patch.ah. Cut Here------------ -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 11: 9:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 3556E154EC for ; Mon, 6 Dec 1999 11:08:41 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from skylink.it (va-143.skylink.it [194.185.55.143]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id UAA18307; Mon, 6 Dec 1999 20:00:40 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id RAA02816; Mon, 6 Dec 1999 17:36:20 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Mon, 6 Dec 1999 17:36:20 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Alex Zepeda Cc: Poul-Henning Kamp , vallo@matti.ee, "Brian W. Buchanan" , FreeBSD CURRENT Mailing List Subject: Re: mount(2) broken? 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 > > Please update your /dev entries. You need to copy MAKEDEV from the > > source area (it isn't installed by default) and run it with the right > > arguments to recreate the device nodes you need. > > I've seen this exact same thing before too. In fact it was two rather > annoying things, one being a single solitary last buffer that wouldn't > sync and thus left the whole fs marked dirty, and then fsck would check > it, see it was fine, but mount wouldn't recognize that it was clean. > > 'Course I saw this this morning too. Yes, with a new kernel, new devices, > ata driver, and new world. 'Twas very odd. Most probably this is exactly the problem I was describing to you a couple of days ago on IRC, phk. The solution is to boot single user, fsck / and reboot. After that things are back to normal. Even crashing the machine does not make this problem reoccur. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 11: 9:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id B623F154BB; Mon, 6 Dec 1999 11:08:41 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from skylink.it (va-143.skylink.it [194.185.55.143]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id UAA18301; Mon, 6 Dec 1999 20:00:33 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id RAA02828; Mon, 6 Dec 1999 17:43:20 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Mon, 6 Dec 1999 17:43:20 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: "David O'Brien" Cc: sos@freebsd.org, current@freebsd.org Subject: Re: ATA driver as the default In-Reply-To: <19991205193638.B74670@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good idea. I'm using it on two machines here. One has a (known) broken hard disk, but I don't care whether it drops a few sectors each day. ATA is keeping it more or less alive. The other one is my laptop, and that one seems to be a lot faster and the system load is down (PIIX4 chipset). Except that it always gives me a timeout at boot. This started about 3 weeks ago I think, but as the drive works fine for the rest, I didn't bother to check into it more deeply. ata-pci0: at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ad0: ATA-4 disk at ata0 as master ad0: 4126MB (8452080 sectors), 8944 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata1 as master acd0: read 2416KB/s (2416KB/s), 128KB buffer, PIO acd0: supported read types: CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked pccard: card inserted, slot 0 ata_command: timeout waiting for interrupt Mounting root from ufs:/dev/ad0s2a On Sun, 5 Dec 1999, David O'Brien wrote: > Since the ATA driver is destined to be the default in 4.0-R, and we hare > hitting the feature freeze date; can we make the switch now? > > I think it is very important to get ATA into more hands to see where it > breaks. It certainly has problems on my Vaio 505 laptop; and I wonder > where else it will have problems. Better to find them now than right > before release. > > -- > -- David (obrien@NUXI.com) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 11:10:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 60FC01564C for ; Mon, 6 Dec 1999 11:09:48 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 403F71CC7 for ; Tue, 7 Dec 1999 02:34:11 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: HEADS UP - i4b broken on -current Date: Tue, 07 Dec 1999 02:34:11 +0800 From: Peter Wemm Message-Id: <19991206183411.403F71CC7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apply http://www.freebsd.org/~peter/i4b.patch to get up and running or wait until a fix has been committed. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 11:10:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 81E031564E for ; Mon, 6 Dec 1999 11:09:48 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 85BCC1CCB for ; Tue, 7 Dec 1999 02:37:22 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: HEADS UP - pnp Date: Tue, 07 Dec 1999 02:37:22 +0800 From: Peter Wemm Message-Id: <19991206183722.85BCC1CCB@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG .. things will pretty much work as before, except you'll see unknown pnp devices being claimed by the "unknown" driver. You will need to remove "controller pnp0" from your config file if you have it. The latest config(8) has been fixed to warn about all unknown devices/controllers/etc. It's not a fatal error though and a kernel with the line will build and work just the same. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 11:12:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id 61E5015319 for ; Mon, 6 Dec 1999 11:12:22 -0800 (PST) (envelope-from dakuntz@home.com) Received: from windows ([24.2.16.41]) by mail.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19991206175618.DRZU7535.mail.rdc1.tn.home.com@windows>; Mon, 6 Dec 1999 09:56:18 -0800 Message-ID: <001d01bf4013$94cbbe40$29100218@micronetinfo.com> From: "Douglas Kuntz" To: "Dieter Rothacker" , References: Subject: Re: Old Libs...? Date: Mon, 6 Dec 1999 12:59:02 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The way I worked around the libs problem was: instead of installing through /stand/sysinstall, I installed through /usr/ports, as that rebuilds the binary using the libs that 4.0 comes with. So far, everything's worked semi-perfectly (well, bash and samba work fine..as do the rest of the ports I've installed) Douglas Kuntz Editor PC Tech Reports ----- Original Message ----- From: "Dieter Rothacker" To: Sent: Monday, December 06, 1999 6:22 AM Subject: Old Libs...? > Hi, > > I have just installed 4.0-SNAP-19991203. I noticed that some packages (e.g. > samba, bash2) complain about missing shared libs (e.g. libreadline.so.3 > needed and .4 is installed). Reading similar things in the mailing list > archive, I assume that I have to install the old libs from a 3.3-stable BIN. > Correct? > > How do I find out which bin-archives I really need to download? I looked at > the mtree-file, but did not find the exact arc files mentioned. I do not > want to download all bin.* files. > > Please forgive me if the solution should be obvious, it is my first try at > FreeBSD. > -- > Dieter Rothacker > > > 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 Dec 6 11:12:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4154615156 for ; Mon, 6 Dec 1999 11:12:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA71576; Mon, 6 Dec 1999 11:12:21 -0800 (PST) (envelope-from dillon) Date: Mon, 6 Dec 1999 11:12:21 -0800 (PST) From: Matthew Dillon Message-Id: <199912061912.LAA71576@apollo.backplane.com> To: Dan Nelson Cc: current@FreeBSD.ORG Subject: Re: NFS client zeroing out blocks on write? References: <19991203112518.A43843@dan.emsphone.com> <199912042051.MAA56920@apollo.backplane.com> <19991205024034.A77822@dan.emsphone.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :In the last episode (Dec 04), Matthew Dillon said: :> Hmm. I thought we had fixed all the zeroing problems. Are you sure :> you compiled your current up from the latest source? : :Yep. The machine was a snapshot install from Nov 15 that I rebuilt :world on the 23rd, and rebuilt the kernel on Dec 2nd. : :> I am presuming there are no other clients accessing the output files :> while the split is running? : :Correct. "split" isn't even strictly necessary, but it makes it easier :to generate multiple gigs worth of data across an nfsv2 mount point. :Depending on my mount options, the glitch is sometimes infrequent :enough to only occur once every 5-10 gig of generated data.. : :> Interesting. It looks very similar to a problem we fixed months ago. :> That problem was related only to NFSv3 and mmap(), and you aren't :> using mmap() here. It's disturbing to see this problem occur with :> both NFSv2 and NFSv3. :> :> I wonder if the problem occurs between a FreeBSD client and server. : :Most of my tests have been done on NFSv3 mounts since they are so much :faster. I'll try another test run, NFSv2 mounting another FreeBSD box :and see what happens. : :-- : Dan Nelson : dnelson@emsphone.com Dan, I know this may be placing an undue burden on you, but can you try installing a 3.x snapshot to see if the bug exists there? If the bug exists in 3.x then I'll know that it isn't due to changes I've made in 4.x (or at least not likely due to those changes). If the bug does not exist then it gives me a place to start looking. The weird thing is that we are talking about a single process here, and I would expect this type of bug to occur with multiple contending processes. If it had just been an NFSv3 mount I would have suspected the commit rpc code, but if it is occuring on NFSv2 as well it kinda sounds like a preexisting bug that has just been brought out into the light due to changes in the way NFS works (major NFS performance improvements have been made in -current, for example, that allow NFS to saturate the network more easily). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 11:13: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id CC97715568; Mon, 6 Dec 1999 11:12:39 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA70858; Mon, 6 Dec 1999 10:00:51 -0800 (PST) (envelope-from dillon) Date: Mon, 6 Dec 1999 10:00:51 -0800 (PST) From: Matthew Dillon Message-Id: <199912061800.KAA70858@apollo.backplane.com> To: Matthew Jacob Cc: "David O'Brien" , Bruce Evans , current@FreeBSD.ORG Subject: Re: oh, btw... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> How do we fix this problem? I keeps from from :> ``dd if=/dev/da1 of=/dev/da2'' ?? I was very peeved at having to put the :> disks on a Solaris box to do such a normal Unix task. : : :this will fix your dd : :Index: dd.c :=================================================================== :RCS file: /home/ncvs/src/bin/dd/dd.c,v :retrieving revision 1.27 :diff -u -r1.27 dd.c :--- dd.c 1999/10/03 18:49:51 1.27 :+++ dd.c 1999/12/05 23:17:16 :@@ -216,6 +216,16 @@ : if (ioctl(io->fd, FIODTYPE, &type) == -1) { : err(1, "%s", io->name); : } else { :+if (type & D_DISK) { :+static int one = 1; :+#ifndef DIOCWLABEL :+#define DIOCWLABEL _IOW('d', 109, int) :+#endif :+fprintf(stderr, "is a disk\n"); :+if (ioctl(io->fd, DIOCWLABEL, &one) < 0) { :+perror("DIOCWLABEL"); :+} :+} : if (type & D_TAPE) : io->flags |= ISTAPE; : else if (type & (D_DISK | D_MEM)) : Woa, timeout! dd if=/dev/da1 of=/dev/da2 had better work - the label area should not be in any way write protected when you use the non-partition device. If you were to use /dev/da2c, *then* it would be reasonable to write-protect the label area. But if you use /dev/da2 it is not. We should not go around hacking dd when the problem is in the kernel. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 11:17:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B7E7214FA0; Mon, 6 Dec 1999 11:17:25 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA13093; Mon, 6 Dec 1999 20:17:06 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912061917.UAA13093@freebsd.dk> Subject: Re: ATA driver as the default In-Reply-To: <19991206064628.G44207@tar.com> from "Richard Seaman, Jr." at "Dec 6, 1999 06:46:28 am" To: dick@tar.com (Richard Seaman, Jr.) Date: Mon, 6 Dec 1999 20:17:06 +0100 (CET) Cc: vallo@matti.ee (Vallo Kallaste), obrien@FreeBSD.ORG (David O'Brien), sos@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Richard Seaman, Jr. wrote: > On Mon, Dec 06, 1999 at 12:19:16PM +0200, Vallo Kallaste wrote: > > > It doesn't know about SiS 5591 PCI IDE controller, the wdc controller > > knows. I'm speaking about boot messages, nothing else. Furthermore the > > wdc driver sets up UDMA mode on my UDMA capable disks, ata driver > > doesn't. It claims that busmastering DMA is supported and sets up WDMA2 > > mode instead, I think it's normal as it currently doesn't know about > > 5591. The WDMA2 isn't really that bad and otherwise I'm using ata driver > > quite happily. Just FYI. > > The one time I tried ata with my SiS 5591 board I got PIO, no > DMA at all. With wd I get UDMA. This was about 2-3 weeks ago. The SiS is supported, depending on how the BIOS sets up the chip the ata driver will do at max wdma2 transfers. I hope to have support before 4.0, are you guys willing to test some patches, they might hose your disks, you have been warned :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 11:21:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id AD933156B6 for ; Mon, 6 Dec 1999 11:21:02 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (boomer.navinet.net [216.67.12.90]) by forrie.net (8.9.3/8.9.3) with ESMTP id NAA00565 for ; Mon, 6 Dec 1999 13:16:53 -0500 (EST) Message-Id: <4.2.2.19991206131555.014d92d0@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 06 Dec 1999 13:17:06 -0500 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Compiler looping Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Someone recently posted a note about a compiler error (loop?) when compiling mysql. I just did buildworld/installworld from today's cvsup and still get the same problem when it goes to: c++ -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME="\"/usr/local\"" -DDATADIR="\"/var/db/mysql\"" -DSHAREDIR="\"/usr/local/share/mysql\"" -DHAVE_CONFIG_H -I./../include -I./../regex -I. -I../include -I.. -I. -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DDBUG_OFF -O -pipe -fno-implicit-templates -c sql_yacc.cc This is compiled directly out of the ports collection. Has anyone identified (and fixed) the bug? _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 11:23:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 04713154DB; Mon, 6 Dec 1999 11:23:25 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA32956; Mon, 6 Dec 1999 14:23:24 -0500 (EST) (envelope-from wollman) Date: Mon, 6 Dec 1999 14:23:24 -0500 (EST) From: Garrett Wollman Message-Id: <199912061923.OAA32956@khavrinen.lcs.mit.edu> To: current@freebsd.org, hw@freebsd.org Group-Reply-To: hw@freebsd.org Subject: Intel 810? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently got a quote from a hardware vendor which made the following claim: > All Socket 370PGA Motherboards use either the 810 or [the] 810c chip > set which does not support FreeBSD because 16MB of the motherboard > memory is used for the display controller. There is no way to tell > the FreeBSD kernel not to use this memory so it will corrupt data. I find this statement rather dubious. Can anyone out there say with more certainty? -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 12: 1: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4D3C815510 for ; Mon, 6 Dec 1999 11:59:34 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA33328; Mon, 6 Dec 1999 11:59:33 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA17026; Mon, 6 Dec 1999 11:59:33 -0800 (PST) (envelope-from obrien) Date: Mon, 6 Dec 1999 11:59:33 -0800 From: "David O'Brien" To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: oh, btw... Message-ID: <19991206115933.E69411@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <199912061800.KAA70858@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912061800.KAA70858@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Dec 06, 1999 at 10:00:51AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 06, 1999 at 10:00:51AM -0800, Matthew Dillon wrote: > dd if=/dev/da1 of=/dev/da2 had better work - the label area should not > be in any way write protected when you use the non-partition device. It doesn't on my Alpha. I certainly would not mind a confermation on this. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 12: 3:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 6505514EE2; Mon, 6 Dec 1999 12:03:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00608; Mon, 6 Dec 1999 12:04:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912062004.MAA00608@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Garrett Wollman Cc: current@freebsd.org, hw@freebsd.org Subject: Re: Intel 810? In-reply-to: Your message of "Mon, 06 Dec 1999 14:23:24 EST." <199912061923.OAA32956@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Dec 1999 12:04:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I recently got a quote from a hardware vendor which made the following > claim: > > > All Socket 370PGA Motherboards use either the 810 or [the] 810c chip > > set which does not support FreeBSD because 16MB of the motherboard > > memory is used for the display controller. There is no way to tell > > the FreeBSD kernel not to use this memory so it will corrupt data. > > I find this statement rather dubious. Can anyone out there say with > more certainty? I can say with certainty that there are S370PGA boards that don't use the 810; we have a number inhouse here that use the 440BX for example. I'd be quite surprised if the 16MB shared video aperture wasn't correctly described by the PnP data; this may require 4.x or 3.x with VM86 defined to deal with it "right". If nobody else has any commentary on this, we'll get one into the lab. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 12: 8:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 1C14D155EE for ; Mon, 6 Dec 1999 12:07:50 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (boomer.navinet.net [216.67.12.90]) by forrie.net (8.9.3/8.9.3) with ESMTP id PAA01477; Mon, 6 Dec 1999 15:07:50 -0500 (EST) Message-Id: <4.2.2.19991206150157.014a4760@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 06 Dec 1999 15:07:21 -0500 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: PAM problems Cc: cyrus-sasl@lists.andrew.cmu.edu 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 trying, in vain, to get pam_mysql.so working on FreeBSD-4.0-CURRENT. This is in use with Cyrus 1.6.x. I'm running into these errors: Dec 6 19:59:34 inbound pop3d[36251]: unable to dlopen /usr/lib/sasl/libdigestmd5.so: /usr/lib/sasl/libdigestmd5.so: Undefined symbol "RC4_set_key" Dec 6 19:59:38 inbound pop3d[36251]: unable to resolve symbol: pam_sm_authenticate Dec 6 19:59:38 inbound pop3d[36251]: unable to resolve symbol: pam_sm_setcred I'm using the CMU RC4 library, and ./configure locates it. The other symbols are unknown to me. Has anyone else gotten this lot/combo to work? _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 13: 1:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 759FB1561E for ; Mon, 6 Dec 1999 13:01:15 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id QAA00369 for ; Mon, 6 Dec 1999 16:01:12 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Mon, 6 Dec 1999 16:01:12 -0500 (EST) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: Sound Blaster ViBRA16X and pcm driver Message-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 these two lines in my kernel: device pcm0 device sbc0 and this is the relative part of a dmesg output: unknown0: at port 0x2f8-0x2ff irq 3 on isa0 unknown1: at port 0x220-0x22f,0x300-0x301,0x388-0x38b ir q 9 drq 0,1 on isa0 unknown2: at port 0x201 on isa0 So what exactly do I need to do to get this working? ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 13:20:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id A4C9D14D78; Mon, 6 Dec 1999 13:20:23 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id PAA98177; Mon, 6 Dec 1999 15:22:45 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <199912062122.PAA98177@celery.dragondata.com> Subject: Re: Intel 810? To: msmith@FreeBSD.ORG (Mike Smith) Date: Mon, 6 Dec 1999 15:22:45 -0600 (CST) Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG, hw@FreeBSD.ORG In-Reply-To: <199912062004.MAA00608@mass.cdrom.com> from "Mike Smith" at Dec 06, 1999 12:04:46 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I recently got a quote from a hardware vendor which made the following > > claim: > > > > > All Socket 370PGA Motherboards use either the 810 or [the] 810c chip > > > set which does not support FreeBSD because 16MB of the motherboard > > > memory is used for the display controller. There is no way to tell > > > the FreeBSD kernel not to use this memory so it will corrupt data. > > > > I find this statement rather dubious. Can anyone out there say with > > more certainty? > > I can say with certainty that there are S370PGA boards that don't use the > 810; we have a number inhouse here that use the 440BX for example. > > I'd be quite surprised if the 16MB shared video aperture wasn't correctly > described by the PnP data; this may require 4.x or 3.x with VM86 defined > to deal with it "right". If nobody else has any commentary on this, > we'll get one into the lab. > I'm using a Socket 370 board with a 440ZX and one with a 440BX, they both work fine... I've got an 810c and an 810e that I'll try later today. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 13:46:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id CC7E9150CF; Mon, 6 Dec 1999 13:46:38 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id NAA90659; Mon, 6 Dec 1999 13:46:29 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912062146.NAA90659@gndrsh.dnsmgr.net> Subject: Re: Intel 810? In-Reply-To: <199912061923.OAA32956@khavrinen.lcs.mit.edu> from Garrett Wollman at "Dec 6, 1999 02:23:24 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Mon, 6 Dec 1999 13:46:28 -0800 (PST) Cc: current@FreeBSD.ORG, hw@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I recently got a quote from a hardware vendor which made the following > claim: > > > All Socket 370PGA Motherboards use either the 810 or [the] 810c chip ^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^ I can say with certain that statement is false, you can run a Socket 370 chip with any PII chipset, including the BX (which is what I have) and the VIA chipsets. > > set which does not support FreeBSD because 16MB of the motherboard > > memory is used for the display controller. There is no way to tell > > the FreeBSD kernel not to use this memory so it will corrupt data. > > I find this statement rather dubious. Can anyone out there say with > more certainty? -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 15:20: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (Postfix) with ESMTP id 06F8515049 for ; Mon, 6 Dec 1999 15:19:43 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from atelier.acadiau.ca (atelier.acadiau.ca [131.162.138.223]) by garlic.acadiau.ca (8.8.5/8.8.5) with ESMTP id TAA09555; Mon, 6 Dec 1999 19:19:01 -0400 (AST) Date: Mon, 6 Dec 1999 19:19:34 -0400 (AST) From: "Marc G. Fournier" To: Forrest Aldrich Cc: freebsd-current@freebsd.org, cyrus-sasl@lists.andrew.cmu.edu Subject: Re: PAM problems In-Reply-To: <4.2.2.19991206150157.014a4760@216.67.12.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 Mon, 6 Dec 1999, Forrest Aldrich wrote: > I'm trying, in vain, to get pam_mysql.so working on FreeBSD-4.0-CURRENT. This is in use with Cyrus 1.6.x. > > I'm running into these errors: > > Dec 6 19:59:34 inbound pop3d[36251]: unable to dlopen /usr/lib/sasl/libdigestmd5.so: /usr/lib/sasl/libdigestmd5.so: Undefined symbol "RC4_set_key" > Dec 6 19:59:38 inbound pop3d[36251]: unable to resolve symbol: pam_sm_authenticate > Dec 6 19:59:38 inbound pop3d[36251]: unable to resolve symbol: pam_sm_setcred > > I'm using the CMU RC4 library, and ./configure locates it. > > The other symbols are unknown to me. > > Has anyone else gotten this lot/combo to work? When you compile the pam module, try using the -R option to set the paths to the libraries implicitly...that might help... Marc G. Fournier marc.fournier@acadiau.ca Senior Systems Administrator Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 16:38:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id 10D8B14CC7; Mon, 6 Dec 1999 16:38:33 -0800 (PST) (envelope-from dakuntz@home.com) Received: from windows ([24.2.16.41]) by mail.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19991207003832.KJJX7535.mail.rdc1.tn.home.com@windows>; Mon, 6 Dec 1999 16:38:32 -0800 Message-ID: <001101bf404b$c5049540$29100218@micronetinfo.com> From: "Douglas Kuntz" To: "Garrett Wollman" , , References: <199912061923.OAA32956@khavrinen.lcs.mit.edu> Subject: Re: Intel 810? Date: Mon, 6 Dec 1999 19:41:15 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current machine was, until last week, a Celeron 366 Socket370 on a Shuttle 440LX board. Though, as far as I can tell, if you're going to use a Celeron PPGA chip, save money and go with the LX or Via chipset based boards, and use the saved money on ram or a larger harddrive. Celerons are all 66mhz bus speed...though, Intel has said they plan on releasing Socket370 Pentium IIIs in 2000. Though, on a sidenote, I really see no reason on getting a 100mhz Socket370 board to run a Pentium III on later, when, except for the clock speed increase, a P3 is the same as a P2 with just the addition of SIMD extensions, which I dont think FreeBSD uses yet. Douglas Kuntz Editor PC Tech Reports http://www.pctechreports.com ----- Original Message ----- From: "Garrett Wollman" To: ; Sent: Monday, December 06, 1999 2:23 PM Subject: Intel 810? > I recently got a quote from a hardware vendor which made the following > claim: > > > All Socket 370PGA Motherboards use either the 810 or [the] 810c chip > > set which does not support FreeBSD because 16MB of the motherboard > > memory is used for the display controller. There is no way to tell > > the FreeBSD kernel not to use this memory so it will corrupt data. > > I find this statement rather dubious. Can anyone out there say with > more certainty? > > -GAWollman > > > > 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 Dec 6 16:46:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from grace.speakeasy.org (grace.speakeasy.net [216.254.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 97BC11504B; Mon, 6 Dec 1999 16:46:45 -0800 (PST) (envelope-from seanj@speakeasy.org) Received: from localhost (seanj@localhost) by grace.speakeasy.org (8.9.1/8.9.1) with ESMTP id QAA30338; Mon, 6 Dec 1999 16:46:30 -0800 Date: Mon, 6 Dec 1999 16:46:30 -0800 (PST) From: Sean Jensen-Grey To: Douglas Kuntz Cc: Garrett Wollman , current@FreeBSD.ORG, hw@FreeBSD.ORG Subject: Re: Intel 810? In-Reply-To: <001101bf404b$c5049540$29100218@micronetinfo.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 whoa. Celerons are whatever bus speed you set them to (not 66). I see no reason to buy a PIII when I can very reliably over clock a celeron processor. I have 5 Celeron SMP machines all running FreeBSD. They are celeron 300a OCd to 450 running on the Abit BP6 MB. Never a problem. I even have a pair of 366 Mhz chips overclocked to 550. My 4.0 Current machine is a dual celeron 450. please reference http://www.sharkyextreme.com http://www.arstechnica.com for info on overclocking. Abit boards are the defacto standard for over clocking. Sean. On Mon, 6 Dec 1999, Douglas Kuntz wrote: > As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current > machine was, until last week, a Celeron 366 Socket370 on a Shuttle 440LX > board. Though, as far as I can tell, if you're going to use a Celeron PPGA > chip, save money and go with the LX or Via chipset based boards, and use the > saved money on ram or a larger harddrive. Celerons are all 66mhz bus > speed...though, Intel has said they plan on releasing Socket370 Pentium IIIs > in 2000. > > Though, on a sidenote, I really see no reason on getting a 100mhz Socket370 > board to run a Pentium III on later, when, except for the clock speed > increase, a P3 is the same as a P2 with just the addition of SIMD > extensions, which I dont think FreeBSD uses yet. > > Douglas Kuntz > Editor > PC Tech Reports > http://www.pctechreports.com > > ----- Original Message ----- > From: "Garrett Wollman" > To: ; > Sent: Monday, December 06, 1999 2:23 PM > Subject: Intel 810? > > > > I recently got a quote from a hardware vendor which made the following > > claim: > > > > > All Socket 370PGA Motherboards use either the 810 or [the] 810c chip > > > set which does not support FreeBSD because 16MB of the motherboard > > > memory is used for the display controller. There is no way to tell > > > the FreeBSD kernel not to use this memory so it will corrupt data. > > > > I find this statement rather dubious. Can anyone out there say with > > more certainty? > > > > -GAWollman > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 16:52:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 1A6A215075 for ; Mon, 6 Dec 1999 16:52:28 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id TAA34764; Mon, 6 Dec 1999 19:52:20 -0500 (EST) (envelope-from wollman) Date: Mon, 6 Dec 1999 19:52:20 -0500 (EST) From: Garrett Wollman Message-Id: <199912070052.TAA34764@khavrinen.lcs.mit.edu> To: "Douglas Kuntz" Cc: Subject: Re: Intel 810? In-Reply-To: <001101bf404b$c5049540$29100218@micronetinfo.com> References: <199912061923.OAA32956@khavrinen.lcs.mit.edu> <001101bf404b$c5049540$29100218@micronetinfo.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current The important issue to me is: will FreeBSD work on an 810 motherboard? The reason I care is because I need the form-factor (a 1U-high server); if I am to use some alternate motherboard, I'll need to be certain in advance that it will fit in a MicroATX opening. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 16:57:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id E22C915075 for ; Mon, 6 Dec 1999 16:57:40 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id SAA25976; Mon, 6 Dec 1999 18:59:10 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <199912070059.SAA25976@celery.dragondata.com> Subject: Re: Intel 810? To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Mon, 6 Dec 1999 18:59:10 -0600 (CST) Cc: dakuntz@home.com (Douglas Kuntz), current@FreeBSD.ORG In-Reply-To: <199912070052.TAA34764@khavrinen.lcs.mit.edu> from "Garrett Wollman" at Dec 06, 1999 07:52:20 PM X-Mailer: ELM [version 2.5 PL1] 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 > > < said: > > > As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current > > The important issue to me is: will FreeBSD work on an 810 motherboard? > The reason I care is because I need the form-factor (a 1U-high > server); if I am to use some alternate motherboard, I'll need to be > certain in advance that it will fit in a MicroATX opening. > Have you considered NLX or LPX form factors? I can dig up the specs if you want, Intel makes motherboards in both form factors. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 16:57:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 138F915156 for ; Mon, 6 Dec 1999 16:57:57 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03791; Mon, 6 Dec 1999 16:59:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912070059.QAA03791@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: Intel 810? In-reply-to: Your message of "Mon, 06 Dec 1999 19:52:20 EST." <199912070052.TAA34764@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Dec 1999 16:59:28 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current > > The important issue to me is: will FreeBSD work on an 810 motherboard? > The reason I care is because I need the form-factor (a 1U-high > server); if I am to use some alternate motherboard, I'll need to be > certain in advance that it will fit in a MicroATX opening. The 1U servers we're using are S370 SBCs in a single-slot PCI passive backplane. These are 440BX boards, and overclock quite nicely. Onboard fxp, available with SCSI as well. Note that IBM have a dual P-III based 1U system as well. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 17: 1:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id F1B8D15075 for ; Mon, 6 Dec 1999 17:01:30 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id LAA00744; Tue, 7 Dec 1999 11:30:45 +1030 (CST) (envelope-from newton) Date: Tue, 7 Dec 1999 11:30:45 +1030 From: Mark Newton To: Garrett Wollman Cc: Douglas Kuntz , current@FreeBSD.ORG Subject: Re: Intel 810? Message-ID: <19991207113045.A697@internode.com.au> References: <199912061923.OAA32956@khavrinen.lcs.mit.edu> <001101bf404b$c5049540$29100218@micronetinfo.com> <199912070052.TAA34764@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912070052.TAA34764@khavrinen.lcs.mit.edu> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 06, 1999 at 07:52:20PM -0500, Garrett Wollman wrote: > < said: > > > As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current > > The important issue to me is: will FreeBSD work on an 810 motherboard? > The reason I care is because I need the form-factor (a 1U-high > server); if I am to use some alternate motherboard, I'll need to be > certain in advance that it will fit in a MicroATX opening. For what it's worth, we've been buying 1U servers pre-configured (and pre-installed with FreeBSD) from Telenet Systems, http://www.tesys.com. US$1199 for the entry-level model. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 17:13:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id E174115129 for ; Mon, 6 Dec 1999 17:13:45 -0800 (PST) (envelope-from dakuntz@home.com) Received: from windows ([24.2.16.41]) by mail.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19991207011320.LAPW7535.mail.rdc1.tn.home.com@windows>; Mon, 6 Dec 1999 17:13:20 -0800 Message-ID: <000d01bf4050$a15c3800$29100218@micronetinfo.com> From: "Douglas Kuntz" To: "Sean Jensen-Grey" Cc: "Garrett Wollman" , References: Subject: Re: Intel 810? Date: Mon, 6 Dec 1999 20:15:57 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG By 66mhz, thats what Intel rates them at...I'm runnin my 366 at 75mhz (412.5mhz)...but they're only designed for 66mhz. Plus, you cant OC the Socket370 chips the same as with the older 300/300a and most of the Slot1 chips. The Socket370 CPUs dont have clock multiplier options, only bus speed options. But as for Micro-ATX, Shuttle makes several Socket370 440BX boards in Micro-ATX, and FIC sells a LX based Micro-ATX board (never used a FIC board w/ a Pentium, however, only AMD). But, I'm willing to guess most board manufacturers sell MicroATX boards for the Socket370...and if not, and you really like the board, and it's a P2/P3 board, you can always get a Socket370 to Slot1 converter card ("slocket") Douglas Kuntz Editor PC Tech Reports http://www.pctechreports.com ----- Original Message ----- From: "Sean Jensen-Grey" To: "Douglas Kuntz" Cc: "Garrett Wollman" ; ; Sent: Monday, December 06, 1999 7:46 PM Subject: Re: Intel 810? > whoa. Celerons are whatever bus speed you set them to (not 66). I see no reason > to buy a PIII when I can very reliably over clock a celeron processor. I have 5 > Celeron SMP machines all running FreeBSD. They are celeron 300a OCd to 450 > running on the Abit BP6 MB. Never a problem. I even have a pair of 366 Mhz chips > overclocked to 550. My 4.0 Current machine is a dual celeron 450. > > please reference > > http://www.sharkyextreme.com > > http://www.arstechnica.com > > for info on overclocking. Abit boards are the defacto standard for over > clocking. > > Sean. > > On Mon, 6 Dec 1999, Douglas Kuntz wrote: > > > As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current > > machine was, until last week, a Celeron 366 Socket370 on a Shuttle 440LX > > board. Though, as far as I can tell, if you're going to use a Celeron PPGA > > chip, save money and go with the LX or Via chipset based boards, and use the > > saved money on ram or a larger harddrive. Celerons are all 66mhz bus > > speed...though, Intel has said they plan on releasing Socket370 Pentium IIIs > > in 2000. > > > > Though, on a sidenote, I really see no reason on getting a 100mhz Socket370 > > board to run a Pentium III on later, when, except for the clock speed > > increase, a P3 is the same as a P2 with just the addition of SIMD > > extensions, which I dont think FreeBSD uses yet. > > > > Douglas Kuntz > > Editor > > PC Tech Reports > > http://www.pctechreports.com > > > > ----- Original Message ----- > > From: "Garrett Wollman" > > To: ; > > Sent: Monday, December 06, 1999 2:23 PM > > Subject: Intel 810? > > > > > > > I recently got a quote from a hardware vendor which made the following > > > claim: > > > > > > > All Socket 370PGA Motherboards use either the 810 or [the] 810c chip > > > > set which does not support FreeBSD because 16MB of the motherboard > > > > memory is used for the display controller. There is no way to tell > > > > the FreeBSD kernel not to use this memory so it will corrupt data. > > > > > > I find this statement rather dubious. Can anyone out there say with > > > more certainty? > > > > > > -GAWollman > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 17:41:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id C4CB714DED for ; Mon, 6 Dec 1999 17:41:51 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id CAA24259 for freebsd-current@FreeBSD.ORG; Tue, 7 Dec 1999 02:41:50 +0100 (CET) (envelope-from olli) Date: Tue, 7 Dec 1999 02:41:50 +0100 (CET) From: Oliver Fromme Message-Id: <199912070141.CAA24259@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: pcm: Soundcard not recognized anymore Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Replying to myself...) Oliver Fromme wrote in list.freebsd-current: > I have today upgraded a machine from some 3.1-stable to the > latest -current snapshot (19991204). Now the ISA PnP soundcard > doesn't work anymore (it worked fine before, using the pcm > driver). It is an Avance Logic ALS100+ card. The following patch makes the card work again in -current: --- dev/sound/isa/sb.c.orig Tue Dec 7 02:30:19 1999 +++ dev/sound/isa/sb.c Tue Dec 7 02:30:19 1999 @@ -1261,6 +1261,10 @@ u_int32_t logical_id = isa_get_logicalid(dev); switch(logical_id) { + case 0x01000000: /* @@@0001 */ + s = "Avance Asound 100"; + break; + case 0x01100000: /* @@@1001 */ s = "Avance Asound 110"; break; Can someone please just commit this trivial fix, or shall I submit a PR? Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 17:54:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 4FEA114E3B for ; Mon, 6 Dec 1999 17:54:12 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 36F931C4F; Mon, 6 Dec 1999 19:55:00 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 3369A381B for ; Mon, 6 Dec 1999 19:55:00 -0500 (EST) Date: Mon, 6 Dec 1999 19:55:00 -0500 (EST) From: Bill Fumerola To: freebsd-current@FreeBSD.ORG Subject: Re: pcm: Soundcard not recognized anymore In-Reply-To: <199912070141.CAA24259@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Dec 1999, Oliver Fromme wrote: > --- dev/sound/isa/sb.c.orig Tue Dec 7 02:30:19 1999 > +++ dev/sound/isa/sb.c Tue Dec 7 02:30:19 1999 > @@ -1261,6 +1261,10 @@ > u_int32_t logical_id = isa_get_logicalid(dev); > > switch(logical_id) { > + case 0x01000000: /* @@@0001 */ > + s = "Avance Asound 100"; > + break; > + > case 0x01100000: /* @@@1001 */ > s = "Avance Asound 110"; > break; > > Can someone please just commit this trivial fix, or shall I > submit a PR? Done ( * $FreeBSD: src/sys/dev/sound/isa/sb.c,v 1.36 1999/12/07 01:53:24 billf Exp $) thanks. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 18:19:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from assurance.rstcorp.com (assurance.rstcorp.com [216.112.242.2]) by hub.freebsd.org (Postfix) with ESMTP id 6408115156 for ; Mon, 6 Dec 1999 18:19:52 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id VAA11127 for ; Mon, 6 Dec 1999 21:21:24 -0500 Received: from proxy.rstcorp.com(216.112.242.5) by assurance.rstcorp.com via smap (V2.0) id xma011121; Tue, 7 Dec 99 02:21:14 GMT Received: from jabberwock.rstcorp.com (jabberwock.rstcorp.com [192.168.2.98]) by sandbox.rstcorp.com (8.8.8+Sun/8.8.8) with ESMTP id VAA23322 for ; Mon, 6 Dec 1999 21:17:09 -0500 (EST) Received: by jabberwock.rstcorp.com (Postfix, from userid 93) id 1AF485AF1; Mon, 6 Dec 1999 21:19:41 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14412.28348.832717.776543@jabberwock.rstcorp.com> Date: Mon, 6 Dec 1999 21:19:40 -0500 (EST) From: "Viren R.Shah" To: freebsd-current@freebsd.org Subject: Using USB modules with an USB keyboard... X-Mailer: VM 6.72 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R.Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way to use only the USB KLDs (i.e. remove all the USB options from the kernel config file) on a machine that has an USB keyboard? I tried doing this (removed all the USB options from my config file, but left KBD_INSTALL_CDEV). However, this caused the kernel build to fail with undefined symbols when compiling the syscons stuff. So, I tried it with putting the normal keyboard line back in (atkbdc and atkbd), but this just caused the system to look for a normal keyboard. What's the correct way to do this? Seems like there should be a way, but I can't find it in the man pages or LINT. Thanks, Viren -- Viren R. Shah, viren @ rstcorp . com, http://www.rstcorp.com/~vshah/ If you understand what you're doing, you are not learning anything To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 18:31: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id BD03215173 for ; Mon, 6 Dec 1999 18:31:06 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id SAA19483; Mon, 6 Dec 1999 18:31:00 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 6 Dec 1999 18:30:59 -0800 (PST) From: Doug White To: Kenneth Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: Sound Blaster ViBRA16X and pcm driver 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, 6 Dec 1999, Kenneth Culver wrote: > I have these two lines in my kernel: > > device pcm0 > device sbc0 > > and this is the relative part of a dmesg output: > > unknown0: at port 0x2f8-0x2ff irq 3 on isa0 > unknown1: at port > 0x220-0x22f,0x300-0x301,0x388-0x38b ir > q 9 drq 0,1 on isa0 > unknown2: at port 0x201 on isa0 > > So what exactly do I need to do to get this working? Can you report the entire dmesg? I suspect this is only one of the logical devices. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 19:36:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id DD89A14F3D for ; Mon, 6 Dec 1999 19:36:49 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id WAA01382; Mon, 6 Dec 1999 22:36:46 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Mon, 6 Dec 1999 22:36:46 -0500 (EST) From: Kenneth Culver To: Doug White Cc: freebsd-current@FreeBSD.ORG Subject: Re: Sound Blaster ViBRA16X and pcm driver 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 Sure. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Dec 6 17:18:47 EST 1999 culverk@culverk.student.umd.edu:/usr/src/sys/compile/MYKERNEL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134152192 (131008K bytes) avail memory = 127414272 (124428K bytes) Preloaded elf kernel "kernel" at 0xc029c000. Preloaded elf module "bktr.ko" at 0xc029c09c. Pentium Pro MTRR support enabled apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 11 chip1: at device 7.3 on pci0 pci0: unknown card (vendor=0x121a, dev=0x0002) at 13.0 pci0: unknown card (vendor=0x121a, dev=0x0002) at 15.0 bktr0: irq 5 at device 17.0 on pci0 bktr0: Hauppauge Model 61291 D110 Warning - Unknown Hauppauge Tuner 0xa Hauppauge WinCast/TV, Philips NTSC tuner, remote control. pci0: unknown card (vendor=0x109e, dev=0x0878) at 17.1 irq 5 de0: irq 10 at device 19.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:1f:21:02 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 vpo0: on ppbus 0 vpo0: EPP 1.9 mode unknown0: at port 0x2f8-0x2ff irq 3 on isa0 unknown1: at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 9 drq 0,1 on isa0 unknown2: at port 0x201 on isa0 ad0: ATA-4 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: ATA-3 disk at ata0 as slave ad1: 4120MB (8438850 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad2: ATA-3 disk at ata1 as master ad2: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata1 as slave , 128KB buffer, PIO acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data/audio disc loaded, unlocked da0 at vpo0 bus 0 target 6 lun 0 da0: Removable Direct Access SCSI-2 device da0: Attempt to query device size failed: NOT READY, Medium not present Mounting root from ufs:/dev/wd1s1a WARNING: / was not properly dismounted de0: enabling 10baseT port ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Mon, 6 Dec 1999, Doug White wrote: > On Mon, 6 Dec 1999, Kenneth Culver wrote: > > > I have these two lines in my kernel: > > > > device pcm0 > > device sbc0 > > > > and this is the relative part of a dmesg output: > > > > unknown0: at port 0x2f8-0x2ff irq 3 on isa0 > > unknown1: at port > > 0x220-0x22f,0x300-0x301,0x388-0x38b ir > > q 9 drq 0,1 on isa0 > > unknown2: at port 0x201 on isa0 > > > > So what exactly do I need to do to get this working? > > Can you report the entire dmesg? I suspect this is only one of the > logical devices. > > Doug White | FreeBSD: The Power to Serve > dwhite@resnet.uoregon.edu | www.FreeBSD.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 21:11:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id DE1DC14EE9 for ; Mon, 6 Dec 1999 21:11:21 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:8XgyY83CwdyULlhPwKGvticD0PTh1HEu@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id OAA32511; Tue, 7 Dec 1999 14:10:37 +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 OAA22642; Tue, 7 Dec 1999 14:15:28 +0900 (JST) Message-Id: <199912070515.OAA22642@zodiac.mech.utsunomiya-u.ac.jp> To: "Viren R.Shah" Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Using USB modules with an USB keyboard... In-reply-to: Your message of "Mon, 06 Dec 1999 21:19:40 EST." <14412.28348.832717.776543@jabberwock.rstcorp.com> References: <14412.28348.832717.776543@jabberwock.rstcorp.com> Date: Tue, 07 Dec 1999 14:15:28 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is there any way to use only the USB KLDs (i.e. remove all the USB >options from the kernel config file) on a machine that has an USB >keyboard? Add "flags 0x100" to syscons. Note this is still an experimental flag. device sc0 at isa? flags 0x100 >I tried doing this (removed all the USB options from my config file, >but left KBD_INSTALL_CDEV). However, this caused the kernel build to >fail with undefined symbols when compiling the syscons stuff. So, I Would you provide your kernel configuration file and exact error messages when you compiled a kernel with this configuration? >tried it with putting the normal keyboard line back in (atkbdc and >atkbd), but this just caused the system to look for a normal >keyboard. And the atkbd driver fails to find an AT keyboard, right? That should not cause any problem to you. Or, did you find any trouble? But, if it still bothers you, you may "disable" the atkbd driver included in the kernel, by specifying device atkbd0 at atkbdc? disable irq 1 Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 21:57:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta3.snfc21.pbi.net (mta3.snfc21.pbi.net [206.13.28.141]) by hub.freebsd.org (Postfix) with ESMTP id D564E14D7D for ; Mon, 6 Dec 1999 21:57:46 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.187]) by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMC00G80W809B@mta3.snfc21.pbi.net> for current@freebsd.org; Mon, 6 Dec 1999 21:50:31 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 2B5BC91846; Mon, 06 Dec 1999 21:50:24 -0800 (PST) Date: Mon, 06 Dec 1999 21:50:24 -0800 (PST) From: Alex Zepeda Subject: Re: mount(2) broken? In-reply-to: To: Nick Hibma Cc: Poul-Henning Kamp , vallo@matti.ee, "Brian W. Buchanan" , FreeBSD CURRENT Mailing List Message-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, 6 Dec 1999, Nick Hibma wrote: > Most probably this is exactly the problem I was describing to you a > couple of days ago on IRC, phk. > > The solution is to boot single user, fsck / and reboot. After that > things are back to normal. Even crashing the machine does not make this > problem reoccur. Nah. This is about the third time I've seen this. I hadn't really gathered any useful information (and no data was lost) so I didn't bother to report it. I suspect it has something to do with soft-updates however. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 22: 2:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles552.castles.com [208.214.165.116]) by hub.freebsd.org (Postfix) with ESMTP id 3E19514D7D for ; Mon, 6 Dec 1999 22:02:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00482; Mon, 6 Dec 1999 22:04:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912070604.WAA00482@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alex Zepeda Cc: FreeBSD CURRENT Mailing List Subject: Re: mount(2) broken? In-reply-to: Your message of "Mon, 06 Dec 1999 21:50:24 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Dec 1999 22:04:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 6 Dec 1999, Nick Hibma wrote: > > > Most probably this is exactly the problem I was describing to you a > > couple of days ago on IRC, phk. > > > > The solution is to boot single user, fsck / and reboot. After that > > things are back to normal. Even crashing the machine does not make this > > problem reoccur. > > Nah. This is about the third time I've seen this. I hadn't really > gathered any useful information (and no data was lost) so I didn't bother > to report it. I suspect it has something to do with soft-updates however. Me too. I just manifested this after a particularly nasty crash this evening (about 500 outstanding buffers), but softupdates weren't active. (It's too easy to kill the system with them enabled; there's a whole realm of exploration still untouched there.) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 23:12:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id EDF4214D6A for ; Mon, 6 Dec 1999 23:12:52 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.199.153]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB8C2; Tue, 7 Dec 1999 08:12:51 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id HAA16398; Tue, 7 Dec 1999 07:48:24 +0100 (CET) (envelope-from asmodai) Date: Tue, 7 Dec 1999 07:48:24 +0100 From: Jeroen Ruigrok/Asmodai To: Khetan Gajjar Cc: current@FreeBSD.ORG Subject: Re: mount(2) broken? Message-ID: <19991207074824.B16352@daemon.ninth-circle.org> References: <199912052145.QAA26864@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from khetan@link.freebsd.os.org.za on Mon, Dec 06, 1999 at 12:13:39AM +0200 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991206 00:00], Khetan Gajjar (khetan@link.freebsd.os.org.za) wrote: >On Sun, 5 Dec 1999, Garrett Wollman wrote: >>* Why isn't MAKEDEV installed by `make install' in a kernel >>compilation directory? > >Afaik, anyone tracking -current either knows to do this or >uses a tool (like mergemaster) that does it for you (I know >I do ;-) Not exactly a relevant answer to the question. There is no reason that after a new kernel or make world MAKEDEV shouldn't be upgraded/replaced by the new one. >Installing MAKEDEV also won't solve these problems from what >I understand unless the disk devices are re-made. Is it >acceptable for MAKEDEV to be installed into /dev >(at some stage of the make world, rebuild kernel and install >process) and have it re-make at least the disk devices contained >in /etc/fstab and /etc/amd.conf ? I don't think you want to force mknod's automatically for the same reason you don't want /etc to be overwritten by new files. Effectively: you want to have the framwork ready yet let the administrator decide when to remake the devices. Just my 0.02 Euro. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project Atone me to my throes curtail... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 23:13: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id E4F4614CA2 for ; Mon, 6 Dec 1999 23:12:51 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.199.153]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA8C2; Tue, 7 Dec 1999 08:12:50 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id HAA16391; Tue, 7 Dec 1999 07:44:38 +0100 (CET) (envelope-from asmodai) Date: Tue, 7 Dec 1999 07:44:37 +0100 From: Jeroen Ruigrok/Asmodai To: Forrest Aldrich Cc: freebsd-current@freebsd.org Subject: Re: Compiler looping Message-ID: <19991207074437.A16352@daemon.ninth-circle.org> References: <4.2.2.19991206131555.014d92d0@216.67.12.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <4.2.2.19991206131555.014d92d0@216.67.12.69>; from forrie@forrie.com on Mon, Dec 06, 1999 at 01:17:06PM -0500 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991206 21:57], Forrest Aldrich (forrie@forrie.com) wrote: >Someone recently posted a note about a compiler error (loop?) when compiling mysql. I just did buildworld/installworld from today's cvsup and still get the same problem when it goes to: > >c++ -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME="\"/usr/local\"" -DDATADIR="\"/var/db/mysql\"" -DSHAREDIR="\"/usr/local/share/mysql\"" -DHAVE_CONFIG_H -I./../include -I./../regex -I. -I../include -I.. -I. -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DDBUG_OFF -O -pipe -fno-implicit-templates -c sql_yacc.cc As what said in the other mail. This is not a `loop'. The C++ compilation takes ages before it is done compiling. Just let it finish, if you are worried about resources, you can limit those per instructions in the other mail. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project Atone me to my throes curtail... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 6 23:16:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id B8FD514CA2 for ; Mon, 6 Dec 1999 23:16:32 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id CAA16646; Tue, 7 Dec 1999 02:16:29 -0500 (EST) (envelope-from luoqi) Date: Tue, 7 Dec 1999 02:16:29 -0500 (EST) From: Luoqi Chen Message-Id: <199912070716.CAA16646@lor.watermarkgroup.com> To: jazepeda@pacbell.net, phk@critter.freebsd.dk Subject: Re: mount(2) broken? Cc: brian@CSUA.Berkeley.EDU, current@FreeBSD.ORG, vallo@matti.ee Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've seen this exact same thing before too. In fact it was two rather > annoying things, one being a single solitary last buffer that wouldn't > sync and thus left the whole fs marked dirty, and then fsck would check > it, see it was fine, but mount wouldn't recognize that it was clean. > > 'Course I saw this this morning too. Yes, with a new kernel, new devices, > ata driver, and new world. 'Twas very odd. > > - alex > I'd like to add something about the last buffer wouldn't sync. This occurs when a shutdown syscall is issued when the syncer process is asleep waiting for a buffer write to complete. The write will never complete, because the syncer won't be given a chance to run again, and the buffer will stay marked as busy and become the buffer that wouldn't sync. I haven't thought about a clean way of handling this situation, maybe some of you out there have better ideas... -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 0:32: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 0A20C14E1C for ; Tue, 7 Dec 1999 00:31:59 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA26463; Tue, 7 Dec 1999 09:31:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Luoqi Chen Cc: jazepeda@pacbell.net, brian@CSUA.Berkeley.EDU, current@FreeBSD.ORG, vallo@matti.ee Subject: Re: mount(2) broken? In-reply-to: Your message of "Tue, 07 Dec 1999 02:16:29 EST." <199912070716.CAA16646@lor.watermarkgroup.com> Date: Tue, 07 Dec 1999 09:31:09 +0100 Message-ID: <26461.944555469@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912070716.CAA16646@lor.watermarkgroup.com>, Luoqi Chen writes: >I'd like to add something about the last buffer wouldn't sync. This occurs >when a shutdown syscall is issued when the syncer process is asleep waiting >for a buffer write to complete. The write will never complete, because the >syncer won't be given a chance to run again, and the buffer will stay marked >as busy and become the buffer that wouldn't sync. I haven't thought about >a clean way of handling this situation, maybe some of you out there have >better ideas... I always thought it would make sense to have the syncer perform the shutdown and cleanup since it had code to write buffers with anyway... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 0:41:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from crucian.comset.net (crucian.comset.com [194.190.242.2]) by hub.freebsd.org (Postfix) with ESMTP id E8F1214C49 for ; Tue, 7 Dec 1999 00:41:45 -0800 (PST) (envelope-from kong@comset.net) Received: from localhost (kong@localhost) by crucian.comset.net (8.9.3/8.8.7) with ESMTP id LAA39308 for ; Tue, 7 Dec 1999 11:41:44 +0300 (MSK) X-Authentication-Warning: crucian.comset.net: kong owned process doing -bs Date: Tue, 7 Dec 1999 11:41:43 +0300 (MSK) From: Hostas Red To: current@freebsd.org Subject: 3.3-stable -> 4.0-current problem... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I've cvsup'ed my 3.3-stable source tree to 4.0-current source tree, and when i'm trying to make buildworld, i'm getting following: ======================================================================== echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h rm -f .depend mkdep -f .depend -a -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c Bad system call - core dumped mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 ======================================================================== And when i'm trying to run buildworld again, following happens: ======================================================================== cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/make/arch.c *** Signal 12 Stop in /usr/src/usr.bin/make. *** Error code 1 ======================================================================== Anybody knows where can be a problem? On my another 4.0 box make world goes just fine... Adios, /KONG ======================================================================== Hostas Red (KVK10, KVK10-RIPN) || UNiX Systems Administrator, ComSet ISP ======================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 0:50: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mgw-i2.ntc.nokia.com (mgw-i2.ntc.nokia.com [131.228.118.61]) by hub.freebsd.org (Postfix) with ESMTP id 9A7A014F0A for ; Tue, 7 Dec 1999 00:49:56 -0800 (PST) (envelope-from marc.solsona@nokia.com) Received: from loki.research.nokia.com (loki.research.nokia.com [172.21.33.76]) by mgw-i2.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id KAA28521; Tue, 7 Dec 1999 10:49:48 +0200 (EET) Received: from pupu.research.nokia.com (pupu.research.nokia.com [172.21.33.84]) by loki.research.nokia.com (8.9.3/8.9.3) with ESMTP id KAA03804; Tue, 7 Dec 1999 10:49:48 +0200 (EET) Received: from nokia.com (playa.research.nokia.com [172.21.41.32]) by pupu.research.nokia.com (8.9.1a/8.9.1) with ESMTP id KAA03737; Tue, 7 Dec 1999 10:49:47 +0200 (EET) Message-ID: <384CCC8C.E8A7E6BB@nokia.com> Date: Tue, 07 Dec 1999 10:59:57 +0200 From: Marc Solsona X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: EXT Hostas Red Cc: current@FreeBSD.ORG Subject: Re: 3.3-stable -> 4.0-current problem... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've tried to do the same and it seems that there have been some changes of the signal achitecture. A solution I found was to build a kernel 4.0 before building world. I haven't tried though. Tell me if it works!! EXT Hostas Red wrote: > Hi! > > I've cvsup'ed my 3.3-stable source tree to 4.0-current source tree, and > when i'm trying to make buildworld, i'm getting following: > > ======================================================================== > echo '#include "i386/freebsd.h"' >> tm.h > echo '#include "i386/perform.h"' >> tm.h > rm -f .depend > mkdep -f .depend -a > -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config > -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -DIN_GCC > -I/usr/obj/usr/src/tmp/usr/include > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c > Bad system call - core dumped > mkdep: compile failed > *** Error code 1 > > Stop in /usr/src/gnu/lib/libgcc. > *** Error code 1 > ======================================================================== > > And when i'm trying to run buildworld again, following happens: > > ======================================================================== > cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/usr/include > -c /usr/src/usr.bin/make/arch.c > *** Signal 12 > > Stop in /usr/src/usr.bin/make. > *** Error code 1 > ======================================================================== > > Anybody knows where can be a problem? On my another 4.0 box make world > goes just fine... > > Adios, > /KONG > > ======================================================================== > Hostas Red (KVK10, KVK10-RIPN) || UNiX Systems Administrator, ComSet ISP > ======================================================================== > > 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 Dec 7 0:54:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from grace.speakeasy.org (grace.speakeasy.net [216.254.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 401FC14F0A for ; Tue, 7 Dec 1999 00:54:13 -0800 (PST) (envelope-from seanj@speakeasy.org) Received: from localhost (seanj@localhost) by grace.speakeasy.org (8.9.1/8.9.1) with ESMTP id AAA15962; Tue, 7 Dec 1999 00:53:54 -0800 Date: Tue, 7 Dec 1999 00:53:53 -0800 (PST) From: Sean Jensen-Grey To: Marc Solsona Cc: EXT Hostas Red , current@FreeBSD.ORG Subject: Re: 3.3-stable -> 4.0-current problem... In-Reply-To: <384CCC8C.E8A7E6BB@nokia.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 Building the kernel first works. also you will need to run the /usr/sbin/config from the /usr/src/usr.sbin tree as the installed one is for the older kernel format. Sean. On Tue, 7 Dec 1999, Marc Solsona wrote: > I've tried to do the same and it seems that there have been some changes of > the signal achitecture. A solution I found was to build a kernel 4.0 before > building world. > I haven't tried though. > > Tell me if it works!! > > EXT Hostas Red wrote: > > > Hi! > > > > I've cvsup'ed my 3.3-stable source tree to 4.0-current source tree, and > > when i'm trying to make buildworld, i'm getting following: > > > > ======================================================================== > > echo '#include "i386/freebsd.h"' >> tm.h > > echo '#include "i386/perform.h"' >> tm.h > > rm -f .depend > > mkdep -f .depend -a > > -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config > > -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -DIN_GCC > > -I/usr/obj/usr/src/tmp/usr/include > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c > > Bad system call - core dumped > > mkdep: compile failed > > *** Error code 1 > > > > Stop in /usr/src/gnu/lib/libgcc. > > *** Error code 1 > > ======================================================================== > > > > And when i'm trying to run buildworld again, following happens: > > > > ======================================================================== > > cc -O -pipe -I/usr/src/usr.bin/make -I/usr/obj/usr/src/tmp/usr/include > > -c /usr/src/usr.bin/make/arch.c > > *** Signal 12 > > > > Stop in /usr/src/usr.bin/make. > > *** Error code 1 > > ======================================================================== > > > > Anybody knows where can be a problem? On my another 4.0 box make world > > goes just fine... > > > > Adios, > > /KONG > > > > ======================================================================== > > Hostas Red (KVK10, KVK10-RIPN) || UNiX Systems Administrator, ComSet ISP > > ======================================================================== > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 1:12:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay5.smtp.psi.net (relay5.smtp.psi.net [38.9.28.2]) by hub.freebsd.org (Postfix) with ESMTP id A3BFF14D79 for ; Tue, 7 Dec 1999 01:12:55 -0800 (PST) (envelope-from keichii@mail.utexas.edu) Received: from [38.192.209.90] (helo=mail.utexas.edu) by relay5.smtp.psi.net with esmtp (Exim 1.90 #1) id 11vGg2-0002gm-00; Tue, 7 Dec 1999 04:12:55 -0500 Message-ID: <384CCF96.C9288D6B@mail.utexas.edu> Date: Tue, 07 Dec 1999 09:12:54 +0000 From: Michael Chin-Yuan Wu Organization: Keichii, Univ of Texas at Austin-ECE X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: zh-TW, en MIME-Version: 1.0 To: Sean Jensen-Grey Cc: Marc Solsona , current@FreeBSD.ORG Subject: Re: 3.3-stable -> 4.0-current problem... References: Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Jensen-Grey wrote: > > Building the kernel first works. also you will need to run the /usr/sbin/config > from the /usr/src/usr.sbin tree as the installed one is for the older kernel > format. > > Sean. This will work: src/usr.sbin/config # make all install use this new config to compile a newly edited current kernel reboot with new kernel make buildworld and so on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 1:34:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay2.smtp.psi.net (relay2.smtp.psi.net [38.8.188.2]) by hub.freebsd.org (Postfix) with ESMTP id 59A4114A29 for ; Tue, 7 Dec 1999 01:34:13 -0800 (PST) (envelope-from keichii@mail.utexas.edu) Received: from [38.192.209.90] (helo=mail.utexas.edu) by relay2.smtp.psi.net with esmtp (Exim 1.90 #1) for freebsd-current@freebsd.org id 11vH0e-0001Yy-00; Tue, 7 Dec 1999 04:34:12 -0500 Message-ID: <384CD494.CB736864@mail.utexas.edu> Date: Tue, 07 Dec 1999 09:34:12 +0000 From: Michael Chin-Yuan Wu Organization: Keichii, Univ of Texas at Austin-ECE X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: zh-TW, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: ps: proc size mismatch for root Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everyone, I have just compiled the newest current as of yesterday. The following only happens when the root user does it. [Other users see the normal results for 'ps'] keichii[root]:~# ps -ax ps: proc size mismatch (60320 total, 712 chunks) keichii[root]:~# ps ps: proc size mismatch (36400 total, 712 chunks) keichii[root]:~# This baffles me because it only happens for the root user. However, I used to have a larger procfs when I ran -stable. Here is my df currently, and it used to be bigger. [Another user admined the box, so I do not know what he did.] keichii[root]:~# df Filesystem 1K-blocks Used Avail Capacity Mounted on [deleted] /dev/wd0s3g 230191 216594 -4818 102% /usr/obj /dev/wd0s3d 109837 40143 60908 40% /var procfs 4 4 0 100% /proc [deleted] keichii[root]:~# Did I misconfigure procfs? Or what should I do? Thank you, Michael Wu keichii@mail.utexas.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 2:36:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 279CD14E32 for ; Tue, 7 Dec 1999 02:36:40 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id FAA00306 for ; Tue, 7 Dec 1999 05:36:38 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Tue, 7 Dec 1999 05:36:38 -0500 (EST) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: sbc and ViBRA16X Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alright, I was under the impression that in order for the ViBRA16X soundcard (sound blaster) to work, these lines were needed in the kernel: device pcm0 device sbc0 Am I right, because it doesn't attach a driver to the soundcard. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 3:18:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from crucian.comset.net (crucian.comset.com [194.190.242.2]) by hub.freebsd.org (Postfix) with ESMTP id DDC4B14E49 for ; Tue, 7 Dec 1999 03:18:17 -0800 (PST) (envelope-from kong@comset.net) Received: from localhost (kong@localhost) by crucian.comset.net (8.9.3/8.8.7) with ESMTP id OAA46782; Tue, 7 Dec 1999 14:17:38 +0300 (MSK) X-Authentication-Warning: crucian.comset.net: kong owned process doing -bs Date: Tue, 7 Dec 1999 14:17:38 +0300 (MSK) From: Hostas Red To: Sean Jensen-Grey Cc: Marc Solsona , current@FreeBSD.ORG Subject: Re: 3.3-stable -> 4.0-current problem... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Tue, 7 Dec 1999, Sean Jensen-Grey wrote: > Building the kernel first works. also you will need to run the /usr/sbin/config > from the /usr/src/usr.sbin tree as the installed one is for the older kernel > format. Yes, worked fine, thanks. I've tried to compile new kernel before, but forgot that new config(8) can be made from new source tree ;) Adios, /KONG ======================================================================== Hostas Red (KVK10, KVK10-RIPN) || UNiX Systems Administrator, ComSet ISP ======================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 3:39:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay6.smtp.psi.net (relay6.smtp.psi.net [38.9.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 42D0914E49 for ; Tue, 7 Dec 1999 03:39:35 -0800 (PST) (envelope-from keichii@mail.utexas.edu) Received: from [38.192.209.90] (helo=mail.utexas.edu) by relay6.smtp.psi.net with esmtp (Exim 1.90 #1) for freebsd-current@freebsd.org id 11vIxz-0002zn-00; Tue, 7 Dec 1999 06:39:35 -0500 Message-ID: <384CF1F7.CB04786E@mail.utexas.edu> Date: Tue, 07 Dec 1999 11:39:35 +0000 From: Michael Chin-Yuan Wu Organization: Keichii, Univ of Texas at Austin-ECE X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: zh-TW, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: ps: proc size mismatch for root References: <384CD494.CB736864@mail.utexas.edu> Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Chin-Yuan Wu wrote: > > Hello everyone, > > I have just compiled the newest current as of yesterday. > The following only happens when the root user does it. > [Other users see the normal results for 'ps'] By the way, just to clarify this, I am running -current updated kernels. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 3:43:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id ED6AD14EDF for ; Tue, 7 Dec 1999 03:43:11 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id MAA27441; Tue, 7 Dec 1999 12:43:03 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Michael Chin-Yuan Wu Cc: freebsd-current@FreeBSD.ORG Subject: Re: ps: proc size mismatch for root In-reply-to: Your message of "Tue, 07 Dec 1999 11:39:35 GMT." <384CF1F7.CB04786E@mail.utexas.edu> Date: Tue, 07 Dec 1999 12:43:03 +0100 Message-ID: <27439.944566983@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <384CF1F7.CB04786E@mail.utexas.edu>, Michael Chin-Yuan Wu writes: >Michael Chin-Yuan Wu wrote: >> >> Hello everyone, >> >> I have just compiled the newest current as of yesterday. >> The following only happens when the root user does it. >> [Other users see the normal results for 'ps'] > >By the way, just to clarify this, I am running -current updated > >kernels. :) what is roots ps aliased to ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 3:49:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay6.smtp.psi.net (relay6.smtp.psi.net [38.9.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 75C0D14E49 for ; Tue, 7 Dec 1999 03:49:42 -0800 (PST) (envelope-from keichii@mail.utexas.edu) Received: from [38.192.209.90] (helo=mail.utexas.edu) by relay6.smtp.psi.net with esmtp (Exim 1.90 #1) id 11vJ7j-0003A6-00; Tue, 7 Dec 1999 06:49:39 -0500 Message-ID: <384CF453.263A0614@mail.utexas.edu> Date: Tue, 07 Dec 1999 11:49:39 +0000 From: Michael Chin-Yuan Wu Organization: Keichii, Univ of Texas at Austin-ECE X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: zh-TW, en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: ps: proc size mismatch for root References: <27439.944566983@critter.freebsd.dk> Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > >Michael Chin-Yuan Wu wrote: > >> I have just compiled the newest current as of yesterday. > >> The following only happens when the root user does it. > >> [Other users see the normal results for 'ps'] > > > >By the way, just to clarify this, I am running -current updated > > > >kernels. :) > > what is roots ps aliased to ? > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG ps is not aliased to anything. all the other users have exactly the same .profile .bashrc etc. as root. Only root has this problem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 3:54:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D05FF14CEE for ; Tue, 7 Dec 1999 03:54:08 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id MAA27484; Tue, 7 Dec 1999 12:54:01 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Michael Chin-Yuan Wu Cc: freebsd-current@FreeBSD.ORG Subject: Re: ps: proc size mismatch for root In-reply-to: Your message of "Tue, 07 Dec 1999 11:49:39 GMT." <384CF453.263A0614@mail.utexas.edu> Date: Tue, 07 Dec 1999 12:54:00 +0100 Message-ID: <27482.944567640@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <384CF453.263A0614@mail.utexas.edu>, Michael Chin-Yuan Wu writes: >Poul-Henning Kamp wrote: >> >Michael Chin-Yuan Wu wrote: >> >> I have just compiled the newest current as of yesterday. >> >> The following only happens when the root user does it. >> >> [Other users see the normal results for 'ps'] >> > >> >By the way, just to clarify this, I am running -current updated >> > >> >kernels. :) >> >> what is roots ps aliased to ? >> >> -- >> Poul-Henning Kamp FreeBSD coreteam member >> phk@FreeBSD.ORG > >ps is not aliased to anything. >all the other users have exactly the same .profile .bashrc etc. as root. Only root has this problem what happens if you type /bin/ps as root ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 4: 2: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id A9AEC14CA3 for ; Tue, 7 Dec 1999 04:02:02 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from cvzoom.net (lcl225.cvzoom.net [208.226.155.225]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id GAA21726; Tue, 7 Dec 1999 06:42:36 -0500 (EST) Message-ID: <384CF700.3B0B444A@cvzoom.net> Date: Tue, 07 Dec 1999 07:01:04 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kenneth Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: sbc and ViBRA16X References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Culver wrote: > > Alright, I was under the impression that in order for the ViBRA16X > soundcard (sound blaster) to work, these lines were needed in the kernel: > > device pcm0 > device sbc0 > > Am I right, because it doesn't attach a driver to the soundcard. In my kernel config, I've got the order of the two switched around. Don't know if that makes a difference or not. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 4:14: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.5]) by hub.freebsd.org (Postfix) with ESMTP id 689BD14F95 for ; Tue, 7 Dec 1999 04:13:56 -0800 (PST) (envelope-from blaz@amis.net) Received: from gold.amis.net (gold.amis.net [212.18.37.254]) by server.amis.net (Postfix) with ESMTP id F0734D5C07 for ; Tue, 7 Dec 1999 13:13:54 +0100 (CET) Received: by gold.amis.net (Postfix, from userid 1000) id BE2871D5F; Tue, 7 Dec 1999 13:13:54 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id B708A5805 for ; Tue, 7 Dec 1999 13:13:54 +0100 (CET) Date: Tue, 7 Dec 1999 13:13:54 +0100 (CET) From: Blaz Zupan X-Sender: blaz@localhost To: freebsd-current@freebsd.org Subject: Initio SCSI driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any particular reason why the Initio SCSI driver (available at http://www.initio.com/drivers/BSD3sourc91xx.zip) is not part of the FreeBSD source tree? I was contemplating buying this SCSI host adapter instead of an Adaptec 2940UW, but I fear that there will be problems in the future (for example late or no support for FBSD 4.0+). The license seems ok and the driver seems to be cam-ified. Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 4:43:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id C104E14E2D for ; Tue, 7 Dec 1999 04:43:00 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id SAA72225 for ; Tue, 7 Dec 1999 18:42:56 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 7 Dec 1999 18:42:56 +0600 (NS) From: Max Khon To: current@freebsd.org Subject: grep -a (-stable) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! it is not possible to make short equivalent for old grep -a option (as in grep 2.3 -a is used for other purposes). it is possible to make a long option (--skip-binary) but long options are quite unusable. GREP_OPTIONS cannot help much (I want an equiv. for old 'grep -aRl pattern .') any thoughts? /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 4:47:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-096.rp-plus.de [149.221.237.96]) by hub.freebsd.org (Postfix) with ESMTP id ED5FE14F4E for ; Tue, 7 Dec 1999 04:47:22 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 0D440AB7F; Tue, 7 Dec 1999 13:47:41 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id NAA09195; Tue, 7 Dec 1999 13:47:50 +0100 (CET) (envelope-from alex) Date: Tue, 7 Dec 1999 13:47:50 +0100 From: Alexander Langer To: Blaz Zupan Cc: freebsd-current@FreeBSD.ORG Subject: Re: Initio SCSI driver Message-ID: <19991207134750.A9129@cichlids.cichlids.com> Mail-Followup-To: Blaz Zupan , freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blaz@amis.net on Tue, Dec 07, 1999 at 01:13:54PM +0100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Blaz Zupan (blaz@amis.net): > http://www.initio.com/drivers/BSD3sourc91xx.zip) is not part of the > FreeBSD source tree? good question. A Friend of mine has already asked me if the initio-controllers are supported. It's the only stone in his way to FreeBSD (yet) Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 5: 7: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from satsuma.mail.easynet.net (satsuma.mail.easynet.net [195.40.1.44]) by hub.freebsd.org (Postfix) with ESMTP id 98B8314F4E; Tue, 7 Dec 1999 05:06:52 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (alister.w.easynet.co.uk [212.212.251.86]) by satsuma.mail.easynet.net with ESMTP id C36BE7B100; Tue, 7 Dec 1999 13:06:50 +0000 (GMT) Message-ID: <384D076F.4E2F437@freenet.co.uk> Date: Tue, 07 Dec 1999 13:11:11 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Nick Hibma Cc: David O'Brien , sos@freebsd.org, freebsd-current@freebsd.org Subject: Re: ATA driver as the default References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote: > > The other one is my laptop, and that one seems to be a lot faster and > the system load is down (PIIX4 chipset). Except that it always gives me > a timeout at boot. > > acd0: CDROM drive at ata1 as master > acd0: read 2416KB/s (2416KB/s), 128KB buffer, PIO > acd0: supported read types: CD-DA > acd0: Audio: play, 16 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked > pccard: card inserted, slot 0 > ata_command: timeout waiting for interrupt Same here (similar hardware): acd0: CDROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked ata_command: timeout waiting for interrupt The command it's failing on is 0xa1 (ATA_C_ATAPI_IDENTIFY). Perhaps the driver should keep a list of misbehaving devices and not try to identify them? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 5:13:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id EFC45151E4 for ; Tue, 7 Dec 1999 05:13:48 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from skylink.it (va-138.skylink.it [194.185.55.138]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id OAA06215; Tue, 7 Dec 1999 14:13:50 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id KAA00845; Tue, 7 Dec 1999 10:41:35 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Tue, 7 Dec 1999 10:41:35 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Alex Zepeda Cc: Poul-Henning Kamp , vallo@matti.ee, "Brian W. Buchanan" , FreeBSD CURRENT Mailing List Subject: Re: mount(2) broken? 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 > > Most probably this is exactly the problem I was describing to you a > > couple of days ago on IRC, phk. > > > > The solution is to boot single user, fsck / and reboot. After that > > things are back to normal. Even crashing the machine does not make this > > problem reoccur. > > Nah. This is about the third time I've seen this. I hadn't really > gathered any useful information (and no data was lost) so I didn't bother > to report it. I suspect it has something to do with soft-updates however. No softupdates in my case. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 5:22:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 48D3514C45 for ; Tue, 7 Dec 1999 05:22:13 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 01D321CC6; Tue, 7 Dec 1999 21:22:10 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Donn Miller Cc: Kenneth Culver , freebsd-current@FreeBSD.ORG Subject: Re: sbc and ViBRA16X In-Reply-To: Message from Donn Miller of "Tue, 07 Dec 1999 07:01:04 EST." <384CF700.3B0B444A@cvzoom.net> Date: Tue, 07 Dec 1999 21:22:09 +0800 From: Peter Wemm Message-Id: <19991207132210.01D321CC6@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller wrote: > Kenneth Culver wrote: > > > > Alright, I was under the impression that in order for the ViBRA16X > > soundcard (sound blaster) to work, these lines were needed in the kernel: > > > > device pcm0 > > device sbc0 > > > > Am I right, because it doesn't attach a driver to the soundcard. > > In my kernel config, I've got the order of the two switched > around. Don't know if that makes a difference or not. Under -current, the kernel config file order is totally irrelevant. You can order it however you like. The only ordering is imposed on old drivers in the sys/i386/isa/isa_compat.* files. New-style drivers are supposed to set the 'sensitive' flag so they get probed first but I don't recall this being quite implemented properly. > - Donn Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 5:25:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from cip12.melaten.rwth-aachen.de (cip12.melaten.RWTH-Aachen.DE [134.130.92.12]) by hub.freebsd.org (Postfix) with ESMTP id 9DFB514C45 for ; Tue, 7 Dec 1999 05:25:41 -0800 (PST) (envelope-from tg@melaten.rwth-aachen.de) Received: (from tg@localhost) by cip12.melaten.rwth-aachen.de (8.9.3/8.9.3) id OAA00545; Tue, 7 Dec 1999 14:25:59 +0100 (CET) (envelope-from tg@melaten.rwth-aachen.de) X-Authentication-Warning: cip12.melaten.rwth-aachen.de: tg set sender to tg@melaten.rwth-aachen.de using -f To: Alexander Langer Cc: Blaz Zupan , freebsd-current@FreeBSD.ORG Subject: Re: Initio SCSI driver References: <19991207134750.A9129@cichlids.cichlids.com> From: Thomas Gellekum In-Reply-To: Alexander Langer's message of "Tue, 7 Dec 1999 13:47:50 +0100" Date: 07 Dec 1999 14:25:59 +0100 Message-ID: Lines: 16 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Langer writes: > Thus spake Blaz Zupan (blaz@amis.net): > > > http://www.initio.com/drivers/BSD3sourc91xx.zip) is not part of the > > FreeBSD source tree? Maybe no one else knew about those drivers? > good question. A Friend of mine has already asked me if the > initio-controllers are supported. > > It's the only stone in his way to FreeBSD (yet) Get him to try the driver. tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 5:37:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from umd5.umd.edu (umd5.umd.edu [128.8.10.5]) by hub.freebsd.org (Postfix) with ESMTP id 2987014E13 for ; Tue, 7 Dec 1999 05:37:07 -0800 (PST) (envelope-from howardjp@wam.umd.edu) Received: from poirot.umd.edu (poirot.umd.edu [128.8.10.129]) by umd5.umd.edu (8.9.1/8.9.1) with ESMTP id IAA28268; Tue, 7 Dec 1999 08:37:06 -0500 (EST) Received: from localhost (howardjp@localhost) by poirot.umd.edu (8.9.1/8.9.1) with SMTP id IAA10303; Tue, 7 Dec 1999 08:37:06 -0500 (EST) X-Authentication-Warning: poirot.umd.edu: howardjp owned process doing -bs Date: Tue, 7 Dec 1999 08:37:06 -0500 (EST) From: James Howard X-Sender: howardjp@poirot.umd.edu To: Max Khon Cc: current@freebsd.org Subject: Re: grep -a (-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 Tue, 7 Dec 1999, Max Khon wrote: > hi, there! > > it is not possible to make short equivalent for old grep -a option > (as in grep 2.3 -a is used for other purposes). > it is possible to make a long option (--skip-binary) but long options > are quite unusable. GREP_OPTIONS cannot help much > (I want an equiv. for old 'grep -aRl pattern .') > any thoughts? Get textproc/freegrep out of the ports collection. :) Let me know if you see any bugs. Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 5:39:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id DB09E14C87 for ; Tue, 7 Dec 1999 05:39:16 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11vKnX-000IfG-00; Tue, 07 Dec 1999 15:36:55 +0200 From: Sheldon Hearn To: Max Khon Cc: current@FreeBSD.ORG Subject: Re: grep -a (-stable) In-reply-to: Your message of "Tue, 07 Dec 1999 18:42:56 +0600." Date: Tue, 07 Dec 1999 15:36:55 +0200 Message-ID: <71749.944573815@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 07 Dec 1999 18:42:56 +0600, Max Khon wrote: > it is not possible to make short equivalent for old grep -a option > (as in grep 2.3 -a is used for other purposes). Que? I've used grep -a since the update to grep 2.3 and haven't noticed any strange behaviour from the -a option. You wanna explain what's going on? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 5:40: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with SMTP id 64AD514A11 for ; Tue, 7 Dec 1999 05:40:00 -0800 (PST) (envelope-from matt@camtech.net.au) Received: from dialup-ad-15-72.camtech.net.au ([203.55.243.72]) by camtech.net.au ; Wed, 08 Dec 1999 00:09:58 +1030 Date: Wed, 8 Dec 1999 00:10:27 +1030 (CST) From: Matthew Thyer X-Sender: matt@localhost Reply-To: thyerm@camtech.net.au To: Jeroen Ruigrok/Asmodai Cc: Forrest Aldrich , freebsd-current@freebsd.org Subject: Re: Compiler looping In-Reply-To: <19991207074437.A16352@daemon.ninth-circle.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 can also vouch that there is nothing wrong with mysql-server-3.22.27. When my machine was compiling sql_yacc.cc the compiler was using 200 MB of memory (this is on a machine with 64 MB RAM!). The solution is to minimize other memory use (stop the X server and setiathome if you run it) and go to bed. In the morning it was all finished without problems. On Tue, 7 Dec 1999, Jeroen Ruigrok/Asmodai wrote: > -On [19991206 21:57], Forrest Aldrich (forrie@forrie.com) wrote: > >Someone recently posted a note about a compiler error (loop?) when compiling mysql. I just did buildworld/installworld from today's cvsup and still get the same problem when it goes to: > > > >c++ -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME="\"/usr/local\"" -DDATADIR="\"/var/db/mysql\"" -DSHAREDIR="\"/usr/local/share/mysql\"" -DHAVE_CONFIG_H -I./../include -I./../regex -I. -I../include -I.. -I. -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DDBUG_OFF -O -pipe -fno-implicit-templates -c sql_yacc.cc > > As what said in the other mail. > > This is not a `loop'. The C++ compilation takes ages before it is done > compiling. Just let it finish, if you are worried about resources, you > can limit those per instructions in the other mail. > > -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 5:49:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 419E914D61 for ; Tue, 7 Dec 1999 05:48:45 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id TAA77173; Tue, 7 Dec 1999 19:48:08 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 7 Dec 1999 19:48:08 +0600 (NS) From: Max Khon To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: grep -a (-stable) In-Reply-To: <71749.944573815@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 7 Dec 1999, Sheldon Hearn wrote: > > it is not possible to make short equivalent for old grep -a option > > (as in grep 2.3 -a is used for other purposes). > > Que? I've used grep -a since the update to grep 2.3 and haven't > noticed any strange behaviour from the -a option. > > You wanna explain what's going on? -stable grep (2.0 + FreeBSD-specific features) uses -a to skip binary files at all. Very useful in such context as: vi `grep -aRl foo .` in -current both 'grep -al' and 'grep -l' print names of binary files and there is no way to tell grep to skip them /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 5:52:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id B4BAC14E13 for ; Tue, 7 Dec 1999 05:51:45 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id TAA77359; Tue, 7 Dec 1999 19:50:26 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 7 Dec 1999 19:50:25 +0600 (NS) From: Max Khon To: James Howard Cc: current@freebsd.org Subject: Re: grep -a (-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 hi, there! On Tue, 7 Dec 1999, James Howard wrote: > > it is not possible to make short equivalent for old grep -a option > > (as in grep 2.3 -a is used for other purposes). > > it is possible to make a long option (--skip-binary) but long options > > are quite unusable. GREP_OPTIONS cannot help much > > (I want an equiv. for old 'grep -aRl pattern .') > > any thoughts? > > Get textproc/freegrep out of the ports collection. :) I know about this beast. It would be nice if our out-of-box grep had this option. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 5:57: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id BC9E814C86; Tue, 7 Dec 1999 05:55:09 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id TAA76479; Tue, 7 Dec 1999 19:37:58 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 7 Dec 1999 19:37:57 +0600 (NS) From: Max Khon To: Alex Cc: Nick Hibma , "David O'Brien" , sos@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: ATA driver as the default In-Reply-To: <384D076F.4E2F437@freenet.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 hi, there! On Tue, 7 Dec 1999, Alex wrote: > > The other one is my laptop, and that one seems to be a lot faster and > > the system load is down (PIIX4 chipset). Except that it always gives me > > a timeout at boot. > > > > acd0: CDROM drive at ata1 as master > > acd0: read 2416KB/s (2416KB/s), 128KB buffer, PIO > > acd0: supported read types: CD-DA > > acd0: Audio: play, 16 volume levels > > acd0: Mechanism: ejectable tray > > acd0: Medium: no/blank disc inside, unlocked > > pccard: card inserted, slot 0 > > ata_command: timeout waiting for interrupt > > Same here (similar hardware): > > acd0: CDROM drive at ata1 as master > acd0: read 4134KB/s (4134KB/s), 128KB buffer, PIO > acd0: supported read types: CD-R, CD-RW, CD-DA > acd0: Audio: play, 256 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked > ata_command: timeout waiting for interrupt > > The command it's failing on is 0xa1 (ATA_C_ATAPI_IDENTIFY). Perhaps > the driver should keep a list of misbehaving devices and not try to > identify them? Same here (kernel & world built from sources cvsupped 29 Nov 1999): acd0: CDROM drive at ata1 as master acd0: read 5512KB/s (5512KB/s), 256KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked ata_command: timeout waiting for interrupt /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 5:58: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 3592514C86 for ; Tue, 7 Dec 1999 05:58:04 -0800 (PST) (envelope-from howardjp@wam.umd.edu) Received: from rac7.wam.umd.edu (root@rac7.wam.umd.edu [128.8.10.147]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id IAA03312; Tue, 7 Dec 1999 08:56:51 -0500 (EST) Received: from rac7.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.3/8.9.3) with SMTP id IAA09147; Tue, 7 Dec 1999 08:56:54 -0500 (EST) Received: from localhost (howardjp@localhost) by rac7.wam.umd.edu (8.9.3/8.9.3) with ESMTP id IAA09143; Tue, 7 Dec 1999 08:56:53 -0500 (EST) X-Authentication-Warning: rac7.wam.umd.edu: howardjp owned process doing -bs Date: Tue, 7 Dec 1999 08:56:53 -0500 (EST) From: James Howard To: Max Khon Cc: current@freebsd.org Subject: Re: grep -a (-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 Tue, 7 Dec 1999, Max Khon wrote: > I know about this beast. It would be nice if our out-of-box grep had > this option. Hah, it used to. I modeled it exactly on it (option-wise). BTW, if you do choose to use it, get it soon. I submitted a PR yesterday for my newest version. It is a faster, but most of the options are broken. Unfortunetly with exams and all, I will not be able to fix it until Christmas or so. Patches are more than welcome ;) Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 6:10:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 32FBD14C9B for ; Tue, 7 Dec 1999 06:10:33 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11vLIT-000Iol-00; Tue, 07 Dec 1999 16:08:53 +0200 From: Sheldon Hearn To: James Howard Cc: Max Khon , current@FreeBSD.ORG Subject: Re: grep -a (-stable) In-reply-to: Your message of "Tue, 07 Dec 1999 08:56:53 EST." Date: Tue, 07 Dec 1999 16:08:53 +0200 Message-ID: <72338.944575733@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 07 Dec 1999 08:56:53 EST, James Howard wrote: > I submitted a PR yesterday for my newest version. It is a faster, but > most of the options are broken. Unfortunetly with exams and all, I > will not be able to fix it until Christmas or so. Then I suggest sending PR follow-up requesting that the update be postponed until _after_ 3.4-RELEASE. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 6:11:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id D702714C9B for ; Tue, 7 Dec 1999 06:11:31 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11vLER-000Imp-00; Tue, 07 Dec 1999 16:04:43 +0200 From: Sheldon Hearn To: Max Khon Cc: current@FreeBSD.ORG Subject: Re: grep -a (-stable) In-reply-to: Your message of "Tue, 07 Dec 1999 19:48:08 +0600." Date: Tue, 07 Dec 1999 16:04:43 +0200 Message-ID: <72218.944575483@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 07 Dec 1999 19:48:08 +0600, Max Khon wrote: > in -current both 'grep -al' and 'grep -l' print names of binary files > and there is no way to tell grep to skip them Ah, so this isn't about -a, it's about -a in conjunction with -l. Thanks for the clarification. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 6:12:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id EDE4F14F18 for ; Tue, 7 Dec 1999 06:12:00 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id UAA78513; Tue, 7 Dec 1999 20:08:55 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 7 Dec 1999 20:08:54 +0600 (NS) From: Max Khon To: James Howard Cc: current@freebsd.org Subject: Re: grep -a (-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 hi, there! On Tue, 7 Dec 1999, James Howard wrote: > > I know about this beast. It would be nice if our out-of-box grep had > > this option. > > Hah, it used to. -stable grep used -a to skip binary files. -current does not. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 6:45:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay2.smtp.psi.net (relay2.smtp.psi.net [38.8.188.2]) by hub.freebsd.org (Postfix) with ESMTP id 0199814C83 for ; Tue, 7 Dec 1999 06:45:29 -0800 (PST) (envelope-from keichii@mail.utexas.edu) Received: from [38.192.209.90] (helo=mail.utexas.edu) by relay2.smtp.psi.net with esmtp (Exim 1.90 #1) for freebsd-current@freebsd.org id 11vLrs-0005Qv-00; Tue, 7 Dec 1999 09:45:28 -0500 Message-ID: <384D1D88.B2F7F062@mail.utexas.edu> Date: Tue, 07 Dec 1999 14:45:28 +0000 From: Michael Chin-Yuan Wu Organization: Keichii, Univ of Texas at Austin-ECE X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: zh-TW, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Cannot mount cd9660 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Chin-Yuan Wu wrote: > > Hi all, > > I have just made -current last night. > I decided to use the new ata0 driver for the first time. > All the devices detect fine. > But this happens when I try to mount my acd0 and acd1 > acd0 is a 40x sony cdrom and acd1 is a sony 6/4/4 cd-r > > keichii[root]:/usr/home/keichii# mount -t iso9660 /dev/acd0 /cdrom1 > mount: exec mount_iso9660 not found in /sbin, /usr/sbin: No such file or directory > keichii[root]:/usr/home/keichii# > > Same with mount_cd9660. I tried with acd1 and all other *cd* devices > and still same error. > > Then I went to src/sbin and did make all install. > Tested and still same error. No result > > went to each of the mount directories and did make all install > Tested and still same error message. No result. > > Dos partitions and floppy drives mount fine > > What should I do? > > P.S. I did a patch for cd9660 and patch for reading Chinese filenames > [patch is in attachment] > =========uname -a============ > FreeBSD keichii.internal.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0 > 8:09 CST 1999 keichii@keichii.internal.org:/usr/current/src > .ATA i386 > ===============dmesg========= > as attachment > =============kernel========= > as attachment > ============patches for chinese filesystems====== > as attachment > ============================== > > Thank you, > > Michael Wu > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #0: Mon Dec 6 04:48:09 CST 1999 > keichii@keichii.internal.org:/usr/current/src/sys/compile/RHEA.ATA > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 598624067 Hz > CPU: Pentium III/Xeon (598.62-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > Features=0x383f9ff > real memory = 402653184 (393216K bytes) > config> di zp0 > No such device: zp0 > Invalid command or syntax. Type `?' for help. > config> di ze0 > No such device: ze0 > Invalid command or syntax. Type `?' for help. > config> di lnc0 > No such device: lnc0 > Invalid command or syntax. Type `?' for help. > config> di le0 > No such device: le0 > Invalid command or syntax. Type `?' for help. > config> di ie0 > No such device: ie0 > Invalid command or syntax. Type `?' for help. > config> di fe0 > No such device: fe0 > Invalid command or syntax. Type `?' for help. > config> di ex0 > No such device: ex0 > Invalid command or syntax. Type `?' for help. > config> di ep0 > No such device: ep0 > Invalid command or syntax. Type `?' for help. > config> di ed0 > No such device: ed0 > Invalid command or syntax. Type `?' for help. > config> di cs0 > No such device: cs0 > Invalid command or syntax. Type `?' for help. > config> di wt0 > No such device: wt0 > Invalid command or syntax. Type `?' for help. > config> di scd0 > No such device: scd0 > Invalid command or syntax. Type `?' for help. > config> di mcd0 > No such device: mcd0 > Invalid command or syntax. Type `?' for help. > config> di matcdc0 > No such device: matcdc0 > Invalid command or syntax. Type `?' for help. > config> di bt0 > No such device: bt0 > Invalid command or syntax. Type `?' for help. > config> di aha0 > No such device: aha0 > Invalid command or syntax. Type `?' for help. > config> di adv0 > No such device: adv0 > Invalid command or syntax. Type `?' for help. > config> q > avail memory = 386830336 (377764K bytes) > Preloaded elf kernel "kernel" at 0xc0327000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc032709c. > Pentium Pro MTRR support enabled > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vga-pci0: irq 11 at device 0.0 on pci1 > isab0: at device 7.0 on pci0 > isa0: on isab0 > ata-pci0: at device 7.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > uhci0: irq 9 at device 7.2 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > ums0: Logitech product 0xc001, rev 1.00/11.00, addr 2, iclass 3/1 > ums0: 3 buttons and Z dir. > chip1: at device 7.3 on pci0 > xl0: <3Com 3c905C-TX Fast Etherlink XL> irq 11 at device 13.0 on pci0 > xl0: Ethernet address: 00:50:da:1b:fb:1c > miibus0: on xl0 > xlphy0: <3c905C 10/100 internal PHY> on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > pci0: unknown card (vendor=0x1102, dev=0x0002) at 14.0 irq 10 > pci0: unknown card (vendor=0x1102, dev=0x7002) at 14.1 > pci0: unknown card (vendor=0x14f1, dev=0x1033) at 16.0 irq 9 > pci0: unknown card (vendor=0x109e, dev=0x036e) at 17.0 irq 3 > pci0: unknown card (vendor=0x109e, dev=0x0878) at 17.1 irq 3 > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio2: not probed (disabled) > sio3: not probed (disabled) > ad0: ATA-4 disk at ata0 as master > ad0: 13042MB (26712000 sectors), 26500 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 32 depth queue, UDMA33 > WARNING: WAIT_INTR active=UNKNOWN > ad1: ATA-? disk at ata0 as slave > ad1: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 1 depth queue, PIO > acd0: CDROM drive at ata1 as master > acd0: read 6875KB/s (6875KB/s), 128KB buffer, UDMA33 > acd0: supported read types: CD-R, CD-RW, CD-DA, packet > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked, lock protected > acd1: CDROM drive at ata1 as slave > acd1: read 4134KB/s (4134KB/s) write 689KB/s (689KB/s), 1024KB buffer, DMA > acd1: supported read types: CD-R, CD-RW, CD-DA, packet > acd1: supported write types: CD-R, CD-RW, test write > acd1: Audio: play, 256 volume levels > acd1: Mechanism: ejectable tray > acd1: Medium: no/blank disc inside, unlocked > Mounting root from ufs:/dev/wd0s3a > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > Name: chinese_joliet.patch.for_3.2-19990615.gz > chinese_joliet.patch.for_3.2-19990615.gz Type: application/x-gzip > Encoding: base64 > > Name: chinese_vfat-3.0.patch.gz > chinese_vfat-3.0.patch.gz Type: application/x-gzip > Encoding: base64 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 7: 7: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 9050D14BE7 for ; Tue, 7 Dec 1999 07:06:59 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-162.skylink.it [194.185.55.162]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id QAA10197; Tue, 7 Dec 1999 16:06:49 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id OAA00467; Tue, 7 Dec 1999 14:20:16 +0100 (CET) (envelope-from hibma@skylink.it) Date: Tue, 7 Dec 1999 14:20:16 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Warner Losh Cc: FreeBSD CURRENT Mailing List Subject: ed driver, resources not released (was: Re: PCCARD eject freeze) In-Reply-To: <199912010755.AAA00462@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've cleaned this up, worked it around, and managed to insert and > eject my ep card 5 times in a row on my desktop kludge environment. > It even appeared to be working. Don't know if this will work on a Hm, The machine is not crashing at the moment when unplugging the device. But plugging it back in gives me a 'No free configuration for card Ethernet' ('Ethernet' being the quite splendid name of the card in the CIS). A quick browse reveals the following difference between ep and ed. It doesn't have any effect however. Let me know if I can test anything. I'd like to get that working, but don't have the time to dig into this (utun driver is more important :) Nick Index: if_ed_pccard.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ed/if_ed_pccard.c,v retrieving revision 1.6 diff -u -w -r1.6 if_ed_pccard.c --- if_ed_pccard.c 1999/11/20 05:16:13 1.6 +++ if_ed_pccard.c 1999/12/03 22:04:06 @@ -91,6 +91,7 @@ ifp->if_flags &= ~IFF_RUNNING; if_down(ifp); bus_teardown_intr(dev, sc->irq_res, &sc->irq_handle); + ed_release_resources(dev); sc->gone = 1; device_printf(dev, "unload\n"); } Nick -- hibma@skylink.it n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 7:13:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 97A1214CAE for ; Tue, 7 Dec 1999 07:13:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id HAA38328; Tue, 7 Dec 1999 07:13:23 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id HAA59099; Tue, 7 Dec 1999 07:13:23 -0800 (PST) (envelope-from obrien) Date: Tue, 7 Dec 1999 07:13:23 -0800 From: "David O'Brien" To: Max Khon Cc: current@freebsd.org Subject: Re: grep -a (-stable) Message-ID: <19991207071323.A59056@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from fjoe@iclub.nsu.ru on Tue, Dec 07, 1999 at 06:42:56PM +0600 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 07, 1999 at 06:42:56PM +0600, Max Khon wrote: > it is not possible to make short equivalent for old grep -a option > (as in grep 2.3 -a is used for other purposes). > it is possible to make a long option (--skip-binary) but long options > are quite unusable. GREP_OPTIONS cannot help much > (I want an equiv. for old 'grep -aRl pattern .') > any thoughts? Talk to the GNU Grep maintainers. I told them such an option was needed in GNU Grep and they said people *liked* the behavior of printing out a match in binary files. I was especially saying with "-l" this behavior us useless. Email them at Paul Eggert and Alain Magloire . See the archives of this list from 11/11/1999 - 11/12/1999 where this was discussed. Are you new to -CURRENT, or were you just not reading this list as you are suppose to? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 7:14:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8946C14BE7 for ; Tue, 7 Dec 1999 07:14:42 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id HAA38333; Tue, 7 Dec 1999 07:14:42 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id HAA59131; Tue, 7 Dec 1999 07:14:41 -0800 (PST) (envelope-from obrien) Date: Tue, 7 Dec 1999 07:14:41 -0800 From: "David O'Brien" To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: grep -a (-stable) Message-ID: <19991207071441.B59056@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <71749.944573815@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <71749.944573815@axl.noc.iafrica.com>; from sheldonh@uunet.co.za on Tue, Dec 07, 1999 at 03:36:55PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 07, 1999 at 03:36:55PM +0200, Sheldon Hearn wrote: > Que? I've used grep -a since the update to grep 2.3 and haven't > noticed any strange behavior from the -a option. You are in for a *BIG* surprise next time you hit a binary file. You really should read what "-a" is now about in the man page. Lets just say "-a" now does the opposite of what you think it does. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 7:16:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 796EC14EC2; Tue, 7 Dec 1999 07:16:39 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11vMM2-0000QR-00; Tue, 07 Dec 1999 17:16:38 +0200 From: Sheldon Hearn To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: grep -a (-stable) In-reply-to: Your message of "Tue, 07 Dec 1999 07:14:41 PST." <19991207071441.B59056@dragon.nuxi.com> Date: Tue, 07 Dec 1999 17:16:38 +0200 Message-ID: <1638.944579798@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 07 Dec 1999 07:14:41 PST, "David O'Brien" wrote: > You are in for a *BIG* surprise next time you hit a binary file. You > really should read what "-a" is now about in the man page. Lets just say > "-a" now does the opposite of what you think it does. Ah wunnerful. So this is why we always argue for days on end about the inclusion of new options in existing utilities. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 7:18:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id EF79B152CC for ; Tue, 7 Dec 1999 07:18:36 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id HAA38350; Tue, 7 Dec 1999 07:18:36 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id HAA59147; Tue, 7 Dec 1999 07:18:34 -0800 (PST) (envelope-from obrien) Date: Tue, 7 Dec 1999 07:18:34 -0800 From: "David O'Brien" To: Blaz Zupan Cc: freebsd-current@freebsd.org Subject: Re: Initio SCSI driver Message-ID: <19991207071834.C59056@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blaz@amis.net on Tue, Dec 07, 1999 at 01:13:54PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 07, 1999 at 01:13:54PM +0100, Blaz Zupan wrote: > Is there any particular reason why the Initio SCSI driver (available at > http://www.initio.com/drivers/BSD3sourc91xx.zip) is not part of the > FreeBSD source tree? Ask on freebsd-scsi@freebsd.org. The people there would have a much better knowledge about it. I've seen this driver, and when I asked, I think Justin Gibbs said he didn't have time to review it and clean it up, or something. Well ask on the SCSI list. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 7:27: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id DA6D214BE7 for ; Tue, 7 Dec 1999 07:26:59 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id HAA38374; Tue, 7 Dec 1999 07:26:59 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id HAA59220; Tue, 7 Dec 1999 07:26:58 -0800 (PST) (envelope-from obrien) Date: Tue, 7 Dec 1999 07:26:58 -0800 From: "David O'Brien" To: Hostas Red Cc: current@freebsd.org Subject: Re: 3.3-stable -> 4.0-current problem... Message-ID: <19991207072658.D59056@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kong@comset.net on Tue, Dec 07, 1999 at 11:41:43AM +0300 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 07, 1999 at 11:41:43AM +0300, Hostas Red wrote: > I've cvsup'ed my 3.3-stable source tree to 4.0-current source tree, and ... > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c > Bad system call - core dumped > mkdep: compile failed > *** Error code 1 ..snip.. > > Anybody knows where can be a problem? On my another 4.0 box make world > goes just fine... (*sigh, this comes up again....*) Yes, you are both running -CURRENT when you have *NO* business doing so. You obviously didn't *_READ_* /usr/src/UPDATING. You obviously haven't been *_READING_* this mailing list. You obviously haven't *_READ_* the past 1-2 months of archives looking for "HEADS UP" messages. I would suggest staying at 3-STABLE. 4-CURRENT is for developers that have the time and ability to follow this list, and read the documentation provided. Please go read http://www.freebsd.org/handbook/cutting-edge.html. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 8:15:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0C02C14D05; Tue, 7 Dec 1999 08:15:25 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id IAA21815; Tue, 7 Dec 1999 08:16:47 -0800 Date: Tue, 7 Dec 1999 08:16:47 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: Alex Zepeda , FreeBSD CURRENT Mailing List Subject: Re: mount(2) broken? In-Reply-To: <199912070604.WAA00482@mass.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 Happens to me every boot. And I'm up to date with all binaries and kernel. I don't have softupdates on the root filesystem. On Mon, 6 Dec 1999, Mike Smith wrote: > > On Mon, 6 Dec 1999, Nick Hibma wrote: > > > > > Most probably this is exactly the problem I was describing to you a > > > couple of days ago on IRC, phk. > > > > > > The solution is to boot single user, fsck / and reboot. After that > > > things are back to normal. Even crashing the machine does not make this > > > problem reoccur. > > > > Nah. This is about the third time I've seen this. I hadn't really > > gathered any useful information (and no data was lost) so I didn't bother > > to report it. I suspect it has something to do with soft-updates however. > > > Me too. > > > I just manifested this after a particularly nasty crash this evening > (about 500 outstanding buffers), but softupdates weren't active. > > (It's too easy to kill the system with them enabled; there's a whole > realm of exploration still untouched there.) > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 8:19: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2D17D14D31 for ; Tue, 7 Dec 1999 08:19:02 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id IAA21823; Tue, 7 Dec 1999 08:20:15 -0800 Date: Tue, 7 Dec 1999 08:20:15 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Luoqi Chen Cc: jazepeda@pacbell.net, phk@critter.freebsd.dk, brian@CSUA.Berkeley.EDU, current@FreeBSD.ORG, vallo@matti.ee Subject: Re: mount(2) broken? In-Reply-To: <199912070716.CAA16646@lor.watermarkgroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Dec 1999, Luoqi Chen wrote: > > I've seen this exact same thing before too. In fact it was two rather > > annoying things, one being a single solitary last buffer that wouldn't > > sync and thus left the whole fs marked dirty, and then fsck would check > > it, see it was fine, but mount wouldn't recognize that it was clean. > > > > 'Course I saw this this morning too. Yes, with a new kernel, new devices, > > ata driver, and new world. 'Twas very odd. > > > > - alex > > > I'd like to add something about the last buffer wouldn't sync. This occurs > when a shutdown syscall is issued when the syncer process is asleep waiting > for a buffer write to complete. The write will never complete, because the > syncer won't be given a chance to run again, and the buffer will stay marked > as busy and become the buffer that wouldn't sync. I haven't thought about > a clean way of handling this situation, maybe some of you out there have > better ideas... Ah. That *could* be happening to me, but this happens even with a quiescent system (I mean, several times with nothing happening). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 8:22:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3ADEF14C80 for ; Tue, 7 Dec 1999 08:22:32 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA42216; Tue, 7 Dec 1999 09:22:31 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA41964; Tue, 7 Dec 1999 09:22:31 -0700 (MST) Message-Id: <199912071622.JAA41964@harmony.village.org> To: Nick Hibma Subject: Re: ed driver, resources not released (was: Re: PCCARD eject freeze) Cc: FreeBSD CURRENT Mailing List In-reply-to: Your message of "Tue, 07 Dec 1999 14:20:16 +0100." References: Date: Tue, 07 Dec 1999 09:22:31 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Nick Hibma writes: : Hm, The machine is not crashing at the moment when unplugging the : device. But plugging it back in gives me a 'No free configuration for : card Ethernet' ('Ethernet' being the quite splendid name of the card in : the CIS). : : A quick browse reveals the following difference between ep and ed. It : doesn't have any effect however. : : Let me know if I can test anything. I'd like to get that working, but : don't have the time to dig into this (utun driver is more important :) Quick question. If you kill and restart pccardd does the problem go away? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 8:39:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id EC35614BE0 for ; Tue, 7 Dec 1999 08:39:09 -0800 (PST) (envelope-from lynch@bsdunix.net) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id LAA10539; Tue, 7 Dec 1999 11:38:52 -0500 (EST) Date: Tue, 7 Dec 1999 11:38:51 -0500 (EST) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: Doug White Cc: Kenneth Culver , freebsd-current@FreeBSD.ORG Subject: Re: Sound Blaster ViBRA16X and pcm driver 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, 6 Dec 1999, Doug White wrote: > > > > unknown0: at port 0x2f8-0x2ff irq 3 on isa0 > > unknown1: at port > > 0x220-0x22f,0x300-0x301,0x388-0x38b ir > > q 9 drq 0,1 on isa0 > > unknown2: at port 0x201 on isa0 > > > > So what exactly do I need to do to get this working? > > Can you report the entire dmesg? I suspect this is only one of the > logical devices. > the nice thing about the old PnP code (in -STABLE and earlier) is that it showed the Vendor ID and Serials so that it would be trivial to check whether this is the issue or not. (the driver may simply not know thats its a card thats supported? incomplete ID list in the driver?) having not looked at newpcm for a few months and not having a -current box here currently to look at source, I couldn't say whther this is the case or not. the question I have is, is there an easy way for a "user" to probe for these ID's and get this kind of information? -Pat ___________________________________________________________________________ Pat Lynch lynch@rush.net lynch@bsdunix.net Systems Administrator Rush Networking ___________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 9: 2:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 5CC2214DEA for ; Tue, 7 Dec 1999 09:02:50 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id MAA00662; Tue, 7 Dec 1999 12:02:49 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Tue, 7 Dec 1999 12:02:49 -0500 (EST) From: Kenneth Culver To: Pat Lynch Cc: freebsd-current@freebsd.org Subject: Re: Sound Blaster ViBRA16X and pcm driver 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 Just use pnpinfo to find out device vender id's and logical id's. It appears that the ViBRA16X is supported (with the correct logical id) in /usr/src/sys/dev/sound/isa/sbc.c but for some reason a driver is still not being attached for it. Any suggestions? ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 7 Dec 1999, Pat Lynch wrote: > On Mon, 6 Dec 1999, Doug White wrote: > > > > > > > unknown0: at port 0x2f8-0x2ff irq 3 on isa0 > > > unknown1: at port > > > 0x220-0x22f,0x300-0x301,0x388-0x38b ir > > > q 9 drq 0,1 on isa0 > > > unknown2: at port 0x201 on isa0 > > > > > > So what exactly do I need to do to get this working? > > > > Can you report the entire dmesg? I suspect this is only one of the > > logical devices. > > > > the nice thing about the old PnP code (in -STABLE and earlier) is that it > showed the Vendor ID and Serials so that it would be trivial to check > whether this is the issue or not. (the driver may simply not know thats > its a card thats supported? incomplete ID list in the driver?) > > having not looked at newpcm for a few months and not having a -current box > here currently to look at source, I couldn't say whther this is the case > or not. > > the question I have is, is there an easy way for a "user" to probe for > these ID's and get this kind of information? > > -Pat > > ___________________________________________________________________________ > > Pat Lynch lynch@rush.net > lynch@bsdunix.net > Systems Administrator Rush Networking > ___________________________________________________________________________ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 9:24:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 52AB915413 for ; Tue, 7 Dec 1999 09:24:29 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id MAA13029; Tue, 7 Dec 1999 12:24:10 -0500 (EST) Message-ID: <19991207122410.A12753@netmonger.net> Date: Tue, 7 Dec 1999 12:24:10 -0500 From: Christopher Masto To: Warner Losh , Nick Hibma Cc: FreeBSD CURRENT Mailing List Subject: Re: ed driver, resources not released (was: Re: PCCARD eject freeze) References: <199912071622.JAA41964@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199912071622.JAA41964@harmony.village.org>; from Warner Losh on Tue, Dec 07, 1999 at 09:22:31AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 07, 1999 at 09:22:31AM -0700, Warner Losh wrote: > In message Nick Hibma writes: > : Hm, The machine is not crashing at the moment when unplugging the > : device. But plugging it back in gives me a 'No free configuration for > : card Ethernet' ('Ethernet' being the quite splendid name of the card in > : the CIS). > : > : A quick browse reveals the following difference between ep and ed. It > : doesn't have any effect however. > : > : Let me know if I can test anything. I'd like to get that working, but > : don't have the time to dig into this (utun driver is more important :) > > Quick question. If you kill and restart pccardd does the problem go > away? It doesn't for me (I have the same problem). This last commit was unfortunate, as it didn't really help the eject situation and now I can't use my sio card at all. :-( -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 9:31: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 8154214D54 for ; Tue, 7 Dec 1999 09:31:03 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (ibmpc.whistle.com [207.76.205.196]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA19598 for ; Tue, 7 Dec 1999 09:31:02 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id JAA00514 for current@FreeBSD.ORG; Tue, 7 Dec 1999 09:26:55 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199912071726.JAA00514@whistle.com> Subject: Re: Intel 810? In-Reply-To: <19991207113045.A697@internode.com.au> from Mark Newton at "Dec 7, 1999 11:30:45 am" To: current@FreeBSD.ORG Date: Tue, 7 Dec 1999 09:26:54 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Newton writes: | On Mon, Dec 06, 1999 at 07:52:20PM -0500, Garrett Wollman wrote: | | > < said: | > | > > As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current | > | > The important issue to me is: will FreeBSD work on an 810 motherboard? | > The reason I care is because I need the form-factor (a 1U-high | > server); if I am to use some alternate motherboard, I'll need to be | > certain in advance that it will fit in a MicroATX opening. | | For what it's worth, we've been buying 1U servers pre-configured | (and pre-installed with FreeBSD) from Telenet Systems, http://www.tesys.com. | US$1199 for the entry-level model. To add to the 1U & 810 thread. - 810 does not support ECC memory from what I've read. - Several cases are available that use ATX or PICMG SBC boards. There are some others but not as interesting or standard. - ATX boards that can fit in a 1U case need a socket and not a slot. I think it is a risk to depend on generic ATX motherboard venders to make them in the future since the ATX spec does not meet the needs of 1U. 2U is fine, no issues. Boomrack has lots of solutions. Also you need to get everything on board since you only have one precious expansion slot (a right angle adapter). - NLX has same problem as ATX (besides I have a grip against NLX since you can't use off the shelf AGP cards in them ... there is a special spec for AGP/NLX) Try to buy one I dare you I eventually dug one up at 2X suggested retail). - PICMG SBC guys need to make thin boards for multi-slot machines so there are lots of Socket boards out their with "real" chipset (ie BX that support ECC memory). Also you can get onbard SCSI, VGA, Ethernet, USB etc. SBC's usually have watchdogs, DiskOnChip (in which you can easily stick a netboot rom) etc. - Lots of 1U cases a little "lame", meaning the SBC cases don't have mounts for all of the SBC boards options. You can only get so many things out a single slot. Mitac is the only company I've seen so far that has more then enough knock outs in their case (www.mitacinds.com). Also the Mitac case can fit a - CDROM - 3.5" hard drive - 3.5" floppy - 2.5" laptop drive All at the same time. I haven't found any other cases that can do that. Most require a laptop drive if you use a CDROM. Now most FreeBSD machines can get away with not having a CDROM so it isn't critical. - Expansion is usually one PCI/ISA slot. We use a D-Link 4 port ethernet card. This card is short enough to fit in the slot since it is not quite a full lenght slot with a CDROM. - Mitac does not use the Intel ethernet chip :-( We have a Mitac case in house and it is very nice. BTW the IBM 1U system is OEM'ed. There is also another company doing dual PII in 1U. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 9:44:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id C42F814E3E for ; Tue, 7 Dec 1999 09:43:58 -0800 (PST) (envelope-from schuerge@wjpserver.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999070600) with ESMTP id SAA07248 for ; Tue, 7 Dec 1999 18:43:56 +0100 (CET) Received: from wjpserver.cs.uni-sb.de (wjpserver.cs.uni-sb.de [134.96.247.42]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id SAA05949 for ; Tue, 7 Dec 1999 18:43:56 +0100 (CET) Received: (from schuerge@localhost) by wjpserver.cs.uni-sb.de (8.9.3/8.9.3/wjp-SVR4/1999052600) id SAA12567 for freebsd-current@freebsd.org; Tue, 7 Dec 1999 18:43:55 +0100 (MET) From: Thomas Schuerger Message-Id: <199912071743.SAA12567@wjpserver.cs.uni-sb.de> Subject: AWE64 problems To: freebsd-current@freebsd.org Date: Tue, 7 Dec 1999 18:43:55 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL57 (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 Hi! I am still having problems getting my AWE64 soundcard to work with the newpcm driver (the "old" pcm driver worked fine). I have updated the world last week and am using the kernel as of today. I'm using the "pcm0" and "sbc0" devices in my kernel options. My card is recognized correctly, but not attached to the pcm0 driver (it is listed as unknown0:), so all audio devices don't work. Any ideas what I am doing wrong? Are there more people having problems with their AWE64? Any help is appreciated! I have included my dmesg and pnpinfo outputs: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Dec 7 18:26:28 CET 1999 schuerge@starfire.heim-d.uni-sb.de:/usr/src/sys/compile/STARFIRE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (412.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183fbff real memory = 268423168 (262132K bytes) avail memory = 256204800 (250200K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc03e6000. Preloaded userconfig_script "/kernel.config" at 0xc03e609c. Preloaded splash_image_data "/boot/starfire.bmp" at 0xc03e60e8. Preloaded elf module "splash_bmp.ko" at 0xc03e6138. Pentium Pro MTRR support enabled splash_bmp: No appropriate video mode found module_register_init: MOD_LOAD (splash_bmp, c03e1654, 0) error 19 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 16 at device 0.0 on pci1 isab0: at device 4.0 on pci0 isa0: on isab0 ata-pci0: at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 4.2 irq 19 Timecounter "PIIX" frequency 3579545 Hz chip1: at device 4.3 on pci0 ahc0: irq 19 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs pci0: unknown card (vendor=0x121a, dev=0x0002) at 9.0 ed0: irq 18 at device 10.0 on pci0 ed0: address 00:80:48:c4:b7:99, type NE2000 (16 bit) devclass_alloc_unit: npx0 already exists, using next available unit number isa0: unexpected tag 14 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A joy0 at port 0x201 on isa0 ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pps0: on ppbus 0 unknown0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 joy1: at port 0x208-0x20f on isa0 unknown1: at port 0x620-0x623 on isa0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default IP Filter: initialized. Default = pass all, Logging = enabled IP Filter: v3.3.3 SMP: AP CPU #1 Launched! ad0: ATA-4 disk at ata0 as master ad0: 26105MB (53464320 sectors), 53040 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 ad1: ATA-4 disk at ata1 as master ad1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 32 depth queue, UDMA33 ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers Mounting root from ufs:/dev/da0s2a cd0 at ahc0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 8 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) pnpinfo: Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CTL00c5 (0xc5008c0e), Serial Number 0x1ea37970 PnP Version 1.0, Vendor Version 16 Device Description: Creative SB AWE64 PnP *** Small Vendor Tag Detected Logical Device ID: CTL0045 0x45008c0e #0 Device Description: Audio TAG Start DF Good Configuration IRQ: 5 - only one type (true/edge) DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 [16-bit addr] I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x10, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x394, alignment 0x4, len 0x4 [16-bit addr] TAG End DF Logical Device ID: CTL7002 0x02708c0e #1 Compatible Device ID: PNPb02f (2fb0d041) Device Description: Game TAG Start DF Good Configuration I/O Range 0x200 .. 0x200, alignment 0x1, len 0x8 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x200 .. 0x208, alignment 0x8, len 0x8 [16-bit addr] TAG End DF Logical Device ID: CTL0022 0x22008c0e #2 Device Description: WaveTable TAG Start DF Good Configuration I/O Range 0x620 .. 0x620, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x620 .. 0x680, alignment 0x20, len 0x4 [16-bit addr] TAG End DF *** Small Vendor Tag Detected End Tag Successfully got 69 resources, 3 logical fdevs -- card select # 0x0001 CSN CTL00c5 (0xc5008c0e), Serial Number 0x1ea37970 Logical device #0 IO: 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 IRQ 5 0 DMA 1 5 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #2 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Ciao, Thomas Schürger. http://www.menden.augustin.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 9:50:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 0446614E19; Tue, 7 Dec 1999 09:50:32 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id EAA19048; Wed, 8 Dec 1999 04:54:26 +1100 Date: Wed, 8 Dec 1999 04:50:13 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Mike Smith Cc: Alex Zepeda , FreeBSD CURRENT Mailing List Subject: Re: mount(2) broken? In-Reply-To: <199912070604.WAA00482@mass.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, 6 Dec 1999, Mike Smith wrote: > > On Mon, 6 Dec 1999, Nick Hibma wrote: > > > > > Most probably this is exactly the problem I was describing to you a > > > couple of days ago on IRC, phk. > > > > > > The solution is to boot single user, fsck / and reboot. After that > > > things are back to normal. Even crashing the machine does not make this > > > problem reoccur. > > > > Nah. This is about the third time I've seen this. I hadn't really > > gathered any useful information (and no data was lost) so I didn't bother > > to report it. I suspect it has something to do with soft-updates however. > > > Me too. > "mount -f /" on a dirty root file system causes the clean flag to stay off forever. (I forgot to change the unclean flag for mount -u.) diff -c2 ffs_vfsops.c~ ffs_vfsops.c *** ffs_vfsops.c~ Thu Nov 25 23:27:44 1999 --- ffs_vfsops.c Sun Dec 5 05:12:51 1999 *************** *** 218,222 **** --- 220,226 ---- } + fs->fs_flags &= ~FS_UNCLEAN; if (fs->fs_clean == 0) { + fs->fs_flags |= FS_UNCLEAN; if (mp->mnt_flag & MNT_FORCE) { printf( Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 9:54:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id C2F0114C99; Tue, 7 Dec 1999 09:54:48 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id MAA215194; Tue, 7 Dec 1999 12:54:46 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Tue, 7 Dec 1999 13:00:33 -0500 To: current@FreeBSD.ORG, stable@FreeBSD.ORG From: Garance A Drosihn Subject: [PATCHES] Two fixes for lpd/lpc for review and test Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, here's my third attempt to get someone to at least acknowledge some minor patches for lpd. The patches are also covered in PR's, as noted in the previous attempts. My theory is that my previous attempts had a subject which made it sound like I was looking for someone to *make* some fixes, as opposed to the fact that I already have fixes for these known bugs and I thought someone with commit privs might want to apply them to the official distribution. In my next installment, I'm going to try a subject of "Make Money Fast via Sex With Green Card Lawyers" Although with this crowd I'd probably have better luck with something like: "I have vmware running native on FreeBSD 3.2-release"... While I'm at it, I'd like to note another patch for lpd which looked interesting. This one might be a bit too risky to get into 3.4-release, but it would be nice to at least add it to current. To quote from another message: - - - Date: Mon, 22 Nov 1999 20:08:13 +0100 From: Andre Albsmeier Subject: Enhancement for lpr (maybe for STABLE-3.4) A while ago I sent a PR containing an enhancement for lpr -r for the case that the file to be printed is on the same filesystem as lpd's spooling directory. The PR is bin/11997 and can be found at: http://www.freebsd.org/cgi/query-pr.cgi?pr=11997 Maybe someone can look at it, review it and eventually commit it to -STABLE (and current, of course). The patch now runs nearly 2 years without problems and saves quite a lot of time when printing large temporay files. - - - Note that the above patch not only saves time, but reduces the amount of disk space needed in a print-spooling partition. That may not seem like much of an issue when you're printing 10-Kbyte files, but when you're throwing around 200-Meg files (for color plotters, for instance), then it can be very nice. The text from my previous attempts follow. - - - - - - - - - - - - - - - - - - - - - - - - - At 5:04 PM -0500 11/20/99, Garance A Drosihn wrote: >Back when we were closing in on the release date for 3.3, I sent >the following message. As we now close in on the release date >for 3.4, I thought I'd send it again, seeing that both of the >problem reports are still marked "open", and neither of the two >patches have been applied yet. (not even to current) > >These are both pretty tiny minor lovable cuddly changes... Any >chance of getting them in for 3.4? > >Note that problem report bin/12912 probably depends on what >umask is set when lpd starts up. The pr says "the problem >doesn't seem to be reproducible", but reproducing the problem >may depend on someone making a change elsewhere. Given that >lpd uses the actual access-bit settings to govern it's behavior, >then it should make sure the exactly-correct bit settings are >set up when it creates the file. > >Also note that the fix for bin/9362, sent in as bin/13549, >is also confirmed in bin/14975. > >>Date: Mon, 6 Sep 1999 18:14:55 -0500 >>To: current@FreeBSD.org >>From: Garance A Drosihn >>Subject: Two fixes for lpd/lpc (printing) >>Cc: kheuer@gwdu60.gwdg.de >> >>I noticed problem-report bin/9362, which reported that the >>'lpc start' command no longer works. (it claims to start >>the queue, but it doesn't actually start it). >> >>I came up with a two or three line fix for that bug, and >>sent it in as problem-report bin/13549. This patch should >>work on both freebsd-current and freebsd-stable. >> >>I also noticed problem report bin/12912. This PR includes >>a patch to make sure that if a lockfile does not already >>exist, then it will be created such that the queue is both >>"enabled" and "started". I have not tried this exact patch >>yet, but here at RPI we've had a similar patch to lpd for a >>long time. We add printer queues to a master printcap file, >>which is then copied to a few hundred workstations. We really >>don't want to have to run around all those workstations to >>'enable' and 'start' a queue that we have just added. Perhaps >>we have a different 'umask' setting when lpd starts up than >>most freebsd sites do... >> >>Could some other people try these simple patches, and see >>how well they work? I am hoping these could make it into >>the next official release, although I realize that time is >>rapidly running out for that! :-) > >--- >Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu >Senior Systems Programmer or drosih@rpi.edu >Rensselaer Polytechnic Institute --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 10: 0:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 238B314D87 for ; Tue, 7 Dec 1999 10:00:29 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA28254; Tue, 7 Dec 1999 13:00:25 -0500 (EST) Received: from rac5.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id NAA13958; Tue, 7 Dec 1999 13:00:23 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA13932; Tue, 7 Dec 1999 13:00:19 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Tue, 7 Dec 1999 13:00:17 -0500 (EST) From: Kenneth Wayne Culver To: Thomas Schuerger Cc: freebsd-current@FreeBSD.ORG Subject: Re: AWE64 problems In-Reply-To: <199912071743.SAA12567@wjpserver.cs.uni-sb.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, I'm having the same problem with my Soundblaster ViBRA16X. It seems that for some reason the sbc driver is not working right. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D | Kenneth Culver=09 | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq=09 | | The University of Maryland, | Website: (Under Construction) | | College Park.=09=09 | http://www.wam.umd.edu/~culverk/| =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D On Tue, 7 Dec 1999, Thomas Schuerger wrote: > Hi! >=20 > I am still having problems getting my AWE64 soundcard to > work with the newpcm driver (the "old" pcm driver worked > fine). I have updated the world last week and am using > the kernel as of today. I'm using the "pcm0" and "sbc0" > devices in my kernel options. My card is recognized > correctly, but not attached to the pcm0 driver (it is > listed as unknown0:), so all audio devices don't work. >=20 > Any ideas what I am doing wrong? Are there more people > having problems with their AWE64? >=20 > Any help is appreciated! >=20 >=20 >=20 > I have included my dmesg and pnpinfo outputs: >=20 >=20 > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #0: Tue Dec 7 18:26:28 CET 1999 > schuerge@starfire.heim-d.uni-sb.de:/usr/src/sys/compile/STARFIRE > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium II/Xeon/Celeron (412.05-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0x652 Stepping =3D 2 > Features=3D0x183fbff > real memory =3D 268423168 (262132K bytes) > avail memory =3D 256204800 (250200K bytes) > Programming 24 pins in IOAPIC #0 > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > Preloaded elf kernel "kernel" at 0xc03e6000. > Preloaded userconfig_script "/kernel.config" at 0xc03e609c. > Preloaded splash_image_data "/boot/starfire.bmp" at 0xc03e60e8. > Preloaded elf module "splash_bmp.ko" at 0xc03e6138. > Pentium Pro MTRR support enabled > splash_bmp: No appropriate video mode found > module_register_init: MOD_LOAD (splash_bmp, c03e1654, 0) error 19 > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 on pci= 0 > pci1: on pcib1 > vga-pci0: irq 16 at device 0.0 o= n pci1 > isab0: at device 4.0 on pci0 > isa0: on isab0 > ata-pci0: at device 4.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > pci0: UHCI USB controller (vendor=3D0x8086, dev=3D0x7112) at 4.2 irq 19 > Timecounter "PIIX" frequency 3579545 Hz > chip1: at device 4.3 on pci0 > ahc0: irq 19 at device 6.0 on pc= i0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=3D7, 16/255 SCBs > pci0: unknown card (vendor=3D0x121a, dev=3D0x0002) at 9.0 > ed0: irq 18 at device 10.0 on pci0 > ed0: address 00:80:48:c4:b7:99, type NE2000 (16 bit)=20 > devclass_alloc_unit: npx0 already exists, using next available unit numbe= r > isa0: unexpected tag 14 > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > joy0 at port 0x201 on isa0 > ppc0 at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > plip0: on ppbus 0 > lpt0: on ppbus 0 > lpt0: Interrupt-driven port > ppi0: on ppbus 0 > pps0: on ppbus 0 > unknown0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b= irq 5 drq 1,5 on isa0 > joy1: at port 0x208-0x20f on isa0 > unknown1: at port 0x620-0x623 on isa0 > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: routing 8254 via pin 2 > IP packet filtering initialized, divert enabled, rule-based forwarding di= sabled, default to accept, logging limited to 100 packets/entry by default > IP Filter: initialized. Default =3D pass all, Logging =3D enabled > IP Filter: v3.3.3 > SMP: AP CPU #1 Launched! > ad0: ATA-4 disk at ata0 as master > ad0: 26105MB (53464320 sectors), 53040 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 32 depth queue, UDMA33 > ad1: ATA-4 disk at ata1 as master > ad1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 32 depth queue, UDMA33 > ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers > ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers > ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers > ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers > ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers > ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers > ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers > ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers > Mounting root from ufs:/dev/da0s2a > cd0 at ahc0 bus 0 target 2 lun 0 > cd0: Removable CD-ROM SCSI-2 device=20 > cd0: 20.000MB/s transfers (20.000MHz, offset 16) > cd0: Attempt to query device size failed: NOT READY, Medium not present > da0 at ahc0 bus 0 target 8 lun 0 > da0: Fixed Direct Access SCSI-2 device=20 > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing = Enabled > da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) >=20 >=20 >=20 > pnpinfo: >=20 > Checking for Plug-n-Play devices... >=20 > Card assigned CSN #1 > Vendor ID CTL00c5 (0xc5008c0e), Serial Number 0x1ea37970 > PnP Version 1.0, Vendor Version 16 > Device Description: Creative SB AWE64 PnP > *** Small Vendor Tag Detected >=20 > Logical Device ID: CTL0045 0x45008c0e #0 > Device Description: Audio > TAG Start DF > Good Configuration > IRQ: 5 - only one type (true/edge) > DMA: channel(s) 1=20 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 5=20 > 16-bit, not a bus master, , count by word, Compatibility mode > I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 > [16-bit addr] > I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 > [16-bit addr] > I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3=20 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 5 6 7=20 > 16-bit, not a bus master, , count by word, Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 > [16-bit addr] > I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3=20 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 5 6 7=20 > 16-bit, not a bus master, , count by word, Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3=20 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 5 6 7=20 > 16-bit, not a bus master, , count by word, Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3=20 > 8-bit, not a bus master, count by byte, , Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 > [16-bit addr] > I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3=20 > 8-bit, not a bus master, count by byte, , Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 > [16-bit addr] > TAG Start DF > Acceptable Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3=20 > 8-bit, not a bus master, count by byte, , Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > TAG Start DF > Sub-optimal Configuration > IRQ: 5 7 9 10 - only one type (true/edge) > DMA: channel(s) 0 1 3=20 > 8-bit, not a bus master, count by byte, , Compatibility mode > DMA: channel(s) 5 6 7=20 > 16-bit, not a bus master, , count by word, Compatibility mode > I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 > [16-bit addr] > I/O Range 0x300 .. 0x330, alignment 0x10, len 0x2 > [16-bit addr] > I/O Range 0x388 .. 0x394, alignment 0x4, len 0x4 > [16-bit addr] > TAG End DF >=20 > Logical Device ID: CTL7002 0x02708c0e #1 > Compatible Device ID: PNPb02f (2fb0d041) > Device Description: Game > TAG Start DF > Good Configuration > I/O Range 0x200 .. 0x200, alignment 0x1, len 0x8 > [16-bit addr] > TAG Start DF > Acceptable Configuration > I/O Range 0x200 .. 0x208, alignment 0x8, len 0x8 > [16-bit addr] > TAG End DF >=20 > Logical Device ID: CTL0022 0x22008c0e #2 > Device Description: WaveTable > TAG Start DF > Good Configuration > I/O Range 0x620 .. 0x620, alignment 0x1, len 0x4 > [16-bit addr] > TAG Start DF > Acceptable Configuration > I/O Range 0x620 .. 0x680, alignment 0x20, len 0x4 > [16-bit addr] > TAG End DF > *** Small Vendor Tag Detected > End Tag >=20 > Successfully got 69 resources, 3 logical fdevs > -- card select # 0x0001 >=20 > CSN CTL00c5 (0xc5008c0e), Serial Number 0x1ea37970 >=20 > Logical device #0 > IO: 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 > IRQ 5 0 > DMA 1 5 > IO range check 0x00 activate 0x01 >=20 > Logical device #1 > IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 > IRQ 0 0 > DMA 4 4 > IO range check 0x00 activate 0x01 >=20 > Logical device #2 > IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 > IRQ 0 0 > DMA 4 4 > IO range check 0x00 activate 0x01 >=20 >=20 >=20 > Ciao, > Thomas Sch=FCrger. http://www.menden.augustin.de >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 10:11:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 9009514CBB for ; Tue, 7 Dec 1999 10:11:31 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA23389; Tue, 7 Dec 1999 11:11:19 -0700 (MST) (envelope-from ken) Message-Id: <199912071811.LAA23389@panzer.kdm.org> Subject: Re: Initio SCSI driver In-Reply-To: from Blaz Zupan at "Dec 7, 1999 01:13:54 pm" To: blaz@amis.net (Blaz Zupan) Date: Tue, 7 Dec 1999 11:11:19 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Blaz Zupan wrote... > Is there any particular reason why the Initio SCSI driver (available at > http://www.initio.com/drivers/BSD3sourc91xx.zip) is not part of the > FreeBSD source tree? > > I was contemplating buying this SCSI host adapter instead of an Adaptec > 2940UW, but I fear that there will be problems in the future (for example > late or no support for FBSD 4.0+). > > The license seems ok and the driver seems to be cam-ified. As David O'Brien mentioned, it's best to ask on the SCSI list about SCSI stuff. In any case, the license on the driver for their Ultra-Wide controllers has not always been a BSD-style license. It used to have one file with a BSD-style license, one file with a proprietary license, and one file with no license. Thomas Graichen has been working on getting both of Initio's drivers into FreeBSD. This may explain why Initio has fixed the copyright on their Ultra-Wide driver. (Their Ultra2 driver never had a copyright problem.) You may want to contact Thomas and see how things are going. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 10:12:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 1D12E14CBB for ; Tue, 7 Dec 1999 10:12:24 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id TAA06870; Tue, 7 Dec 1999 19:11:39 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <199912071811.TAA06870@info.iet.unipi.it> Subject: is there any heap functions in the kernel ? To: current@freebsd.org Date: Tue, 7 Dec 1999 19:11:39 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, i was wondering if there is any place in the kernel with functions to implement a "heap" data structure. I would expect so, as typically this structure is used wherever we need to do some kind of scheduling, but i am not sure on where to look... Ideas ? (for those who wonder why I ask -- i redesigning dummynet so it handles more efficiently large numbers of pipes, and while i have rewritten the heap management code, i was wondering if i am not duplicating existing funcionality.) cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) http://www.iet.unipi.it/~luigi/ngc99/ ==== First International Workshop on Networked Group Communication ==== -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 10:24:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id E390715328 for ; Tue, 7 Dec 1999 10:24:09 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id NAA25202; Tue, 7 Dec 1999 13:24:06 -0500 (EST) (envelope-from luoqi) Date: Tue, 7 Dec 1999 13:24:06 -0500 (EST) From: Luoqi Chen Message-Id: <199912071824.NAA25202@lor.watermarkgroup.com> To: phk@critter.freebsd.dk Subject: Re: mount(2) broken? Cc: brian@CSUA.Berkeley.EDU, current@FreeBSD.ORG, jazepeda@pacbell.net, vallo@matti.ee Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I'd like to add something about the last buffer wouldn't sync. This occurs > >when a shutdown syscall is issued when the syncer process is asleep waiting > >for a buffer write to complete. The write will never complete, because the > >syncer won't be given a chance to run again, and the buffer will stay marked > >as busy and become the buffer that wouldn't sync. I haven't thought about > >a clean way of handling this situation, maybe some of you out there have > >better ideas... > > I always thought it would make sense to have the syncer perform the shutdown > and cleanup since it had code to write buffers with anyway... > This sounds like a good idea, and should be easy to implement. I'll work on it tonight. > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 11:21:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (columbus.rr.com [204.210.252.19]) by hub.freebsd.org (Postfix) with ESMTP id C524314EBB for ; Tue, 7 Dec 1999 11:20:59 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([24.95.60.151]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com for ; Tue, 7 Dec 1999 14:20:43 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id OAA00518 for freebsd-current@FreeBSD.ORG; Tue, 7 Dec 1999 14:20:46 -0500 (EST) (envelope-from caa) Date: Tue, 7 Dec 1999 14:20:46 -0500 From: "Charles Anderson" To: FreeBSD Current Subject: Re: AWE64 problems Message-ID: <19991207142046.A465@midgard.dhs.org> References: <199912071743.SAA12567@wjpserver.cs.uni-sb.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=8t9RHnE3ZwKMSgU+ X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Kenneth Wayne Culver on Tue, Dec 07, 1999 at 01:00:17PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii I hate me too messages, but I'm having problems too. Exact same symptoms. I looked at sbc.c and it has the correct logical id, I spent some time looking at this last night, but was stymied by my lack of understanding of how the pnp system works. I even tried it with PNPBIOS defined, but that didn't help any either. I have attached dmesg output and pnpinfo output. -Charlie -- Charles Anderson caa@columbus.rr.com No quote, no nothin' --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.out" Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Dec 7 12:19:46 EST 1999 caa@midgard.dhs.org:/usr/src/sys/compile/MIDGARD Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 451024486 Hz CPU: Pentium II/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping = 0 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 126877696 (123904K bytes) Preloaded elf kernel "kernel" at 0xc030c000. Preloaded elf module "splash_bmp.ko" at 0xc030c09c. Preloaded elf module "vesa.ko" at 0xc030c140. Preloaded splash_image_data "/root/daemon_640.bmp" at 0xc030c1dc. VESA: v1.2, 4096k memory, flags:0x0, mode table:0xc00c5e02 (c0005e02) VESA: Alliance Semiconductor PMAT3D Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 chip1: at device 7.1 on pci0 pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 15 intpm0: at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 fxp0: irq 14 at device 11.0 on pci0 fxp0: Ethernet address 00:a0:c9:78:ae:3a vga-pci0: at device 13.0 on pci0 ncr0: irq 11 at device 15.0 on pci0 ncr1: irq 15 at device 17.0 on pci0 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> joy0 at port 0x201 on isa0 ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 unknown0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 unknown1: at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 unknown2: at port 0x620-0x623 on isa0 unknown: can't assign resources (sa0:ncr0:0:4:0): found quirk entry 2 sa0 at ncr0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-CCS device sa0: 3.300MB/s transfers Mounting root from ufs:/dev/da0s1a cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 19.230MB/s transfers (19.230MHz, offset 16) cd0: cd present [306474 x 2048 byte records] da3 at ncr0 bus 0 target 15 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da2 at ncr0 bus 0 target 10 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) da2: 2150MB (4404489 512 byte sectors: 255H 63S/T 274C) da1 at ncr0 bus 0 target 9 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) da1: 2150MB (4404489 512 byte sectors: 255H 63S/T 274C) da0 at ncr0 bus 0 target 8 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) da0: 2150MB (4404489 512 byte sectors: 255H 63S/T 274C) (cd1:ncr0:0:6:0): got CAM status 0x4c (cd1:ncr0:0:6:0): fatal error, failed to attach to device (cd1:ncr0:0:6:0): lost device (cd1:ncr0:0:6:0): removing device entry --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg-pnpbios.out" Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Dec 7 14:04:42 EST 1999 caa@midgard.dhs.org:/usr/src/sys/compile/MIDGARD Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 451024606 Hz CPU: Pentium II/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping = 0 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 126873600 (123900K bytes) Preloaded elf kernel "kernel" at 0xc030d000. Preloaded elf module "splash_bmp.ko" at 0xc030d09c. Preloaded elf module "vesa.ko" at 0xc030d140. Preloaded splash_image_data "/root/daemon_640.bmp" at 0xc030d1dc. VESA: v1.2, 4096k memory, flags:0x0, mode table:0xc00c5e02 (c0005e02) VESA: Alliance Semiconductor PMAT3D Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 chip1: at device 7.1 on pci0 pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 15 intpm0: at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 fxp0: irq 14 at device 11.0 on pci0 fxp0: Ethernet address 00:a0:c9:78:ae:3a vga-pci0: at device 13.0 on pci0 ncr0: irq 11 at device 15.0 on pci0 ncr1: irq 15 at device 17.0 on pci0 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> joy0 at port 0x201 on isa0 ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 unknown0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 unknown1: at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 unknown2: at port 0x620-0x623 on isa0 unknown: can't assign resources unknown: can't assign resources unknown3: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 unknown4: at port 0x40-0x43 irq 0 on isa0 unknown5: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown: can't assign resources unknown6: at port 0xf0-0xff irq 13 on isa0 unknown7: at iomem 0-0x9ffff,0xfffe0000-0xffffffff,0x100000-0x7ffffff on isa0 unknown8: at iomem 0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfffff,0xcc200-0xcffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown9: at port 0x208-0x20f on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources (sa0:ncr0:0:4:0): found quirk entry 2 sa0 at ncr0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-CCS device sa0: 3.300MB/s transfers Mounting root from ufs:/dev/da0s1a cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 19.230MB/s transfers (19.230MHz, offset 16) cd0: cd present [306474 x 2048 byte records] da3 at ncr0 bus 0 target 15 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1 at ncr0 bus 0 target 9 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) da1: 2150MB (4404489 512 byte sectors: 255H 63S/T 274C) da0 at ncr0 bus 0 target 8 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) da0: 2150MB (4404489 512 byte sectors: 255H 63S/T 274C) da2 at ncr0 bus 0 target 10 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) da2: 2150MB (4404489 512 byte sectors: 255H 63S/T 274C) (cd1:ncr0:0:6:0): got CAM status 0x4c (cd1:ncr0:0:6:0): fatal error, failed to attach to device (cd1:ncr0:0:6:0): lost device (cd1:ncr0:0:6:0): removing device entry --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="pnp.out" Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CTL0048 (0x48008c0e), Serial Number 0x0002d159 PnP Version 1.0, Vendor Version 16 Device Description: Creative SB32 PnP Logical Device ID: CTL0031 0x31008c0e #0 Device Description: Audio TAG Start DF Good Configuration IRQ: 5 - only one type (true/edge) DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 [16-bit addr] I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 10 11 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG End DF Logical Device ID: CTL2011 0x11208c0e #1 Compatible Device ID: PNP0600 (0006d041) Device Description: IDE TAG Start DF Good Configuration IRQ: 10 - only one type (true/edge) I/O Range 0x168 .. 0x168, alignment 0x1, len 0x8 [16-bit addr] I/O Range 0x36e .. 0x36e, alignment 0x1, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 11 - only one type (true/edge) I/O Range 0x1e8 .. 0x1e8, alignment 0x1, len 0x8 [16-bit addr] I/O Range 0x3ee .. 0x3ee, alignment 0x1, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 10 11 12 15 - only one type (true/edge) I/O Range 0x100 .. 0x1f8, alignment 0x8, len 0x8 [16-bit addr] I/O Range 0x300 .. 0x3fe, alignment 0x2, len 0x2 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 15 - only one type (true/edge) I/O Range 0x170 .. 0x170, alignment 0x1, len 0x8 [16-bit addr] I/O Range 0x376 .. 0x376, alignment 0x1, len 0x1 [16-bit addr] TAG End DF Logical Device ID: CTL0021 0x21008c0e #2 Device Description: WaveTable TAG Start DF Good Configuration I/O Range 0x620 .. 0x620, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x620 .. 0x680, alignment 0x20, len 0x4 [16-bit addr] TAG End DF Logical Device ID: CTL7001 0x01708c0e #3 Compatible Device ID: PNPb02f (2fb0d041) Device Description: Game I/O Range 0x200 .. 0x200, alignment 0x1, len 0x8 [16-bit addr] End Tag Successfully got 76 resources, 4 logical fdevs -- card select # 0x0001 CSN CTL0048 (0x48008c0e), Serial Number 0x0002d159 Logical device #0 IO: 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 IRQ 5 0 DMA 1 5 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x036e 0x036e 0x036e 0x036e 0x036e 0x036e 0x036e 0x036e IRQ 10 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #2 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #3 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 --8t9RHnE3ZwKMSgU+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 11:38:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id 5FA5B14C49; Tue, 7 Dec 1999 11:38:14 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id UAA67948; Tue, 7 Dec 1999 20:38:13 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9C3775.dip.t-dialin.net [62.156.55.117]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id UAA67923; Tue, 7 Dec 1999 20:38:07 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (laptop.rock.net [172.23.7.128]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id UAA54961; Tue, 7 Dec 1999 20:38:11 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <384D53E8.27ABF47D@dead-end.net> Date: Tue, 07 Dec 1999 19:37:28 +0100 From: "D. Rock" X-Mailer: Mozilla 4.7 [de] (Win98; U) X-Accept-Language: de MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: ATA driver as the default References: <19991205193638.B74670@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien schrieb: > > Since the ATA driver is destined to be the default in 4.0-R, and we hare > hitting the feature freeze date; can we make the switch now? > > I think it is very important to get ATA into more hands to see where it > breaks. It certainly has problems on my Vaio 505 laptop; and I wonder > where else it will have problems. Better to find them now than right > before release. I occasionaly tested the new ATA driver on my laptop but decided to go back to the old wd driver: There seems to be a problem if I enable DMA for the hard disk. With DMA turned on the disk sometimes hung for a few seconds, then got resetted and worked again. No data corruption occured. This happened under FreeBSD and Windows. I therefor disabled DMA transfer for the disk. The CD-ROM works just happily with DMA turned on though. Disk and CD-ROM are connected to the same IDE controller (Intel standard). I just want a flag to selectively disable DMA transfer for certain files, just like I could for the old wd driver. I just re-enabled the ATA driver again after reading the change log of better error handling and automatic falldown DMA->PIO under specific circumstances. But a few days later, while making world (with the ata driver), the system crashed quite heavily. The file system was totally screwed up afterwards (I found my /usr/local after some heavy searching: It magically moved to /usr/obj/usr/src/tmp/usr/share/zoneinfo (!) and got tons of fsck messages). The file system had softupdates enabled. I don't know the last kernel messages before the crash (was running X at that time). Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 12:11:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id BFA9014C29 for ; Tue, 7 Dec 1999 12:11:09 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (ibmpc.whistle.com [207.76.205.196]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA24827 for ; Tue, 7 Dec 1999 12:11:09 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id LAA31946 for current@FreeBSD.ORG; Tue, 7 Dec 1999 11:57:31 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199912071957.LAA31946@whistle.com> Subject: Re: ATA driver as the default In-Reply-To: <384D53E8.27ABF47D@dead-end.net> from "D. Rock" at "Dec 7, 1999 07:37:28 pm" To: current@FreeBSD.ORG Date: Tue, 7 Dec 1999 11:57:31 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG D. Rock writes: | I just re-enabled the ATA driver again after reading the change log | of better error handling and automatic falldown DMA->PIO under specific | circumstances. | But a few days later, while making world (with the ata driver), the | system | crashed quite heavily. The file system was totally screwed up afterwards | (I found my /usr/local after some heavy searching: It magically | moved to /usr/obj/usr/src/tmp/usr/share/zoneinfo (!) and got tons of | fsck | messages). The file system had softupdates enabled. I don't know the | last kernel messages before the crash (was running X at that time). You might want to look at ata-disk.c and the timeout value around line 438: /* start timeout for this transfer */ if (panicstr) request->timeout_handle.callout = NULL; else request->timeout_handle = timeout((timeout_t*)ad_timeout, request, 5*hz); Originally it was 3s and recently increased to 5s. Personally I switched it to 30s after it trashed my filesystem when it was 3s. The issue was that 3s, is that it is to short to wait for my laptop's drive to spin back up. Sometimes I would get a corrupted read sometimes on a write it would trash things. I noticed in the old wd driver that it tried 10s first then a couple 3s timeouts. After making this change my system has been rock solid when the drive spins down. Note I haven't tried to tune this value since trashing a 14G filesystem is pain full. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 12:22:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 8B8A014BFC; Tue, 7 Dec 1999 12:22:42 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id MAA28281; Tue, 7 Dec 1999 12:22:24 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda28279; Tue Dec 7 12:22:17 1999 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id MAA02186; Tue, 7 Dec 1999 12:22:16 -0800 (PST) Message-Id: <199912072022.MAA02186@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdzo2178; Tue Dec 7 12:21:36 1999 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.3-RELEASE X-Sender: cschuber To: Garance A Drosihn Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: [PATCHES] Two fixes for lpd/lpc for review and test In-reply-to: Your message of "Tue, 07 Dec 1999 13:00:33 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Dec 1999 12:21:35 -0800 From: Cy Schubert Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Garance A Drosihn writes: I've been using the patch from PR 13549 on 4 -stable stable machines for about 3 weeks with no ill effects -- and it fixes the problem. > In my next installment, I'm going to try a subject of > "Make Money Fast via Sex With Green Card Lawyers" You can get screwed by a lawyer without sex. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 13: 6:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B097F14CCC; Tue, 7 Dec 1999 13:06:51 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA43444; Tue, 7 Dec 1999 14:06:49 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA44391; Tue, 7 Dec 1999 14:06:49 -0700 (MST) Message-Id: <199912072106.OAA44391@harmony.village.org> To: Garance A Drosihn Subject: Re: [PATCHES] Two fixes for lpd/lpc for review and test Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 07 Dec 1999 13:00:33 EST." References: Date: Tue, 07 Dec 1999 14:06:49 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been reviewing this patch with someone and I think the last version is ready to commit. I'll take a look at my tree to make sure. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 13: 9:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay1.smtp.psi.net (relay1.smtp.psi.net [38.8.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 38B7E14CCC for ; Tue, 7 Dec 1999 13:09:18 -0800 (PST) (envelope-from keichii@mail.utexas.edu) Received: from [38.192.209.90] (helo=mail.utexas.edu) by relay1.smtp.psi.net with esmtp (Exim 1.90 #1) id 11vRr1-0007YF-00; Tue, 7 Dec 1999 16:09:00 -0500 Message-ID: <384D776D.9127AAB5@mail.utexas.edu> Date: Tue, 07 Dec 1999 21:09:01 +0000 From: Michael Chin-Yuan Wu Organization: Keichii, Univ of Texas at Austin-ECE X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: zh-TW, en MIME-Version: 1.0 To: marc.solsona@nokia.com Cc: Hostas Red , current@freebsd.org Subject: Re: 3.3-stable -> 4.0-current problem... References: <19991207072658.D59056@dragon.nuxi.com> Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Tue, Dec 07, 1999 at 11:41:43AM +0300, Hostas Red wrote: > > I've cvsup'ed my 3.3-stable source tree to 4.0-current source tree, and > ... > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c > > Bad system call - core dumped > > mkdep: compile failed > > *** Error code 1 > ..snip.. > > > > Anybody knows where can be a problem? On my another 4.0 box make world > > goes just fine... > > (*sigh, this comes up again....*) > > Yes, you are both running -CURRENT when you have *NO* business doing so. All they need is a simple pointer, why not be a bit nicer? :) Please try this tutorial when you move from -stable to -current www.external.org/freebsd/current.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 13:24:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id 0D9E214DA5 for ; Tue, 7 Dec 1999 13:24:16 -0800 (PST) (envelope-from fn@gatekeeper.radio-do.de) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by gatekeeper.radio-do.de (Postfix) with ESMTP id B40C7BECB; Tue, 7 Dec 1999 22:23:31 +0100 (MET) Received: (from fn@localhost) by trinity.radio-do.de (8.9.3/8.9.3) id WAA00659; Tue, 7 Dec 1999 22:24:15 +0100 (CET) (envelope-from fn@gatekeeper.radio-do.de) Date: Tue, 7 Dec 1999 22:24:15 +0100 From: Frank Nobis To: Thomas Schuerger , freebsd-current@FreeBSD.ORG Subject: Re: AWE64 problems Message-ID: <19991207222414.A555@radio-do.de> References: <199912071743.SAA12567@wjpserver.cs.uni-sb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912071743.SAA12567@wjpserver.cs.uni-sb.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 07, 1999 at 06:43:55PM +0100, Thomas Schuerger wrote: > Hi! > > I am still having problems getting my AWE64 soundcard to > work with the newpcm driver (the "old" pcm driver worked > fine). > > Any ideas what I am doing wrong? Are there more people > having problems with their AWE64? > > Any help is appreciated! I had the same problem with my AWE64. An older kernel @(#)FreeBSD 4.0-CURRENT #1: Sun Nov 28 18:54:55 CET 1999 was working correct with "device pcm" and "device sbc" I dived into the source and put some printf's. I noticed that the sbc_attach never got called. This is my patch. Now it is working again, but I don't have a clue if I did it the right way. --- sbc.c.orig Mon Dec 6 19:26:31 1999 +++ sbc.c Tue Dec 7 22:15:25 1999 @@ -110,7 +110,7 @@ if (error) return error; else - return -100; + return -1; } static int Frank -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 13:44:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from ares.maths.adelaide.edu.au (ares.maths.adelaide.edu.au [129.127.246.5]) by hub.freebsd.org (Postfix) with ESMTP id A017514D0E; Tue, 7 Dec 1999 13:44:25 -0800 (PST) (envelope-from glewis@ares.maths.adelaide.edu.au) Received: (from glewis@localhost) by ares.maths.adelaide.edu.au (8.9.3/8.9.3) id IAA47852; Wed, 8 Dec 1999 08:14:02 +1030 (CST) (envelope-from glewis) From: Greg Lewis Message-Id: <199912072144.IAA47852@ares.maths.adelaide.edu.au> Subject: Re: Samba Performance In-Reply-To: <384BCDB1.BD599C68@altavista.net> from Maxim Sobolev at "Dec 6, 1999 04:52:33 pm" To: sobomax@altavista.net Date: Wed, 8 Dec 1999 08:14:02 +1030 (CST) Cc: l.farr@epcdirect.co.uk, stable@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Try to look into the ports/samba/patches for the patch-ah file (which provided > to resolve such misbehaviour). If that file doesn't exist than either try to > cvsup your ports, or manually add following patch and recompile/reinstall samba: This patch is only relevant for Samba 2.0.5a. If you look at the Changelog for 2.0.6 you'll see that MSG_WAITALL was removed specifically because of the performance problems under FreeBSD it caused. -- Greg Lewis glewis@trc.adelaide.edu.au Computing Officer +61 8 8303 5083 Teletraffic Research Centre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 14: 0:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 6C87514EEE for ; Tue, 7 Dec 1999 14:00:07 -0800 (PST) (envelope-from schuerge@wjpserver.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999070600) with ESMTP id XAA09843; Tue, 7 Dec 1999 23:00:03 +0100 (CET) Received: from wjpserver.cs.uni-sb.de (wjpserver.cs.uni-sb.de [134.96.247.42]) by cs.uni-sb.de (8.9.3/1999031900) with ESMTP id XAA09140; Tue, 7 Dec 1999 23:00:02 +0100 (CET) Received: (from schuerge@localhost) by wjpserver.cs.uni-sb.de (8.9.3/8.9.3/wjp-SVR4/1999052600) id XAA14065; Tue, 7 Dec 1999 23:00:02 +0100 (MET) From: Thomas Schuerger Message-Id: <199912072200.XAA14065@wjpserver.cs.uni-sb.de> Subject: Re: AWE64 problems In-Reply-To: <19991207222414.A555@radio-do.de> from Frank Nobis at "Dec 7, 1999 10:24:15 pm" To: Frank Nobis Date: Tue, 7 Dec 1999 23:00:02 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL57 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am still having problems getting my AWE64 soundcard to > > work with the newpcm driver (the "old" pcm driver worked > > fine). > > > > Any ideas what I am doing wrong? Are there more people > > having problems with their AWE64? > > I had the same problem with my AWE64. An older kernel > @(#)FreeBSD 4.0-CURRENT #1: Sun Nov 28 18:54:55 CET 1999 > was working correct with "device pcm" and "device sbc" > > I dived into the source and put some printf's. I noticed that the > sbc_attach never got called. This is my patch. Now it is working again, > but I don't have a clue if I did it the right way. > > > --- sbc.c.orig Mon Dec 6 19:26:31 1999 > +++ sbc.c Tue Dec 7 22:15:25 1999 > @@ -110,7 +110,7 @@ > if (error) > return error; > else > - return -100; > + return -1; > } > > static int Works fine for me. Thanks!!! Ciao, Thomas Schürger. http://www.menden.augustin.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 14: 6:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 4A7E914A09 for ; Tue, 7 Dec 1999 14:06:52 -0800 (PST) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (postal.sr.hp.com [15.4.46.173]) by palrel1.hp.com (Postfix) with ESMTP id 65650558; Tue, 7 Dec 1999 14:06:47 -0800 (PST) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id OAA04979; Tue, 7 Dec 1999 14:05:53 -0800 (PST) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id OAA26284; Tue, 7 Dec 1999 14:05:29 -0800 (PST) Message-Id: <199912072205.OAA26284@mina.sr.hp.com> To: Michael Chin-Yuan Wu Cc: current@FreeBSD.ORG Subject: Re: 3.3-stable -> 4.0-current problem... Reply-To: Darryl Okahata In-reply-to: Your message of "Tue, 07 Dec 1999 21:09:01 GMT." <384D776D.9127AAB5@mail.utexas.edu> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Tue, 07 Dec 1999 14:05:28 -0800 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Chin-Yuan Wu wrote: > Please try this tutorial when you move from -stable to -current > > www.external.org/freebsd/current.html I think you're missing the recent block device obsolescence change. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 14:18:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from natsoft.com.au (natsoft.com.au [203.39.138.130]) by hub.freebsd.org (Postfix) with ESMTP id 9E98014A09; Tue, 7 Dec 1999 14:18:46 -0800 (PST) (envelope-from craig@natsoft.com.au) Received: from Win95.natsoft.com.au (Win95 [203.39.138.131]) by natsoft.com.au (8.8.5/8.8.5) with SMTP id JAA04493; Wed, 8 Dec 1999 09:22:08 GMT Message-ID: <384D869D.6093@natsoft.com.au> Date: Wed, 08 Dec 1999 09:13:49 +1100 From: Craig Wilson Organization: National Software Pty Ltd X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: Greg Lewis Cc: sobomax@altavista.net, l.farr@epcdirect.co.uk, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Samba Performance References: <199912072144.IAA47852@ares.maths.adelaide.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have FreeBSD 3.3-RELEASE on a computer that is having Samba performance problems. Using an Intel EtherExpress Pro100 (100MBit) it takes 10 times as long to copy the same large file from a Win98 computer to the FreeBSD computer than it takes to copy from a Win98 to Win98 computer. On looking at the Samba man page I see that FeeBSD 3.3-RELEASE is using Samba 2.0.5a. This Samba was installed as a precompiled package from the 3.3-RELEASE CD-ROM. Could someone please advise me if the Samba package on the CD-ROM contains this problem. If so I assume it is best to download Samba 2.0.6. Thanks in advance Craig Wilson National software Pty Ltd Greg Lewis wrote: > > > Try to look into the ports/samba/patches for the patch-ah file (which provided > > to resolve such misbehaviour). If that file doesn't exist than either try to > > cvsup your ports, or manually add following patch and recompile/reinstall samba: > > This patch is only relevant for Samba 2.0.5a. If you look at the Changelog > for 2.0.6 you'll see that MSG_WAITALL was removed specifically because of > the performance problems under FreeBSD it caused. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 14:26:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E0A1714E4A; Tue, 7 Dec 1999 14:26:12 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id OAA17645; Tue, 7 Dec 1999 14:55:38 -0800 (PST) Date: Tue, 7 Dec 1999 14:55:37 -0800 (PST) From: Alfred Perlstein To: Warner Losh Cc: Garance A Drosihn , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test In-Reply-To: <199912072106.OAA44391@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Dec 1999, Warner Losh wrote: > I've been reviewing this patch with someone and I think the last > version is ready to commit. I'll take a look at my tree to make > sure. please do not, the patch in PR 11997 introduces a major security flaw. someone can hardlink to any file and clobber it with a file owned by them: try this: as root: # cd /var/tmp ; touch rootfile ; chown root:wheel rootfile ; chmod 600 rootfile as a user: % cd /var/tmp ; echo foo > foo % lpr -r foo sleeping in another session as user: % rm foo ; ln rootfile foo wait a second... # ls -l rootfile -rw-rw---- 3 user daemon 5 Dec 7 13:38 rootfile # cat rootfile foo # ouch! -Alfred use this patch to make the race condition apparrent: Index: usr.sbin/lpr/lpr/lpr.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/lpr/lpr/lpr.c,v retrieving revision 1.27.2.2 diff -u -u -r1.27.2.2 lpr.c --- lpr.c 1999/08/29 15:43:29 1.27.2.2 +++ lpr.c 1999/12/08 01:47:47 @@ -370,6 +370,27 @@ } if (sflag) printf("%s: %s: not linked, copying instead\n", name, arg); + if( f ) { /* means that the file should be deleted */ + printf("sleeping\n"); + sleep(5); + printf("done.\n"); + seteuid(euid); /* needed for rename() to succeed */ + if( ! rename( arg, dfname ) ) { + register int i; + chmod( dfname, S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP ); + chown( dfname, userid, getgrnam("daemon")->gr_gid ); + seteuid(uid); + if (format == 'p') + card('T', title ? title : arg); + for (i = 0; i < ncopies; i++) + card(format, &dfname[inchar-2]); + card('U', &dfname[inchar-2]); + card('N', arg); + nact++; + continue; + } + seteuid(uid); + } if ((i = open(arg, O_RDONLY)) < 0) { printf("%s: cannot open %s\n", name, arg); } else { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 14:29:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id AA7CA14EC7 for ; Tue, 7 Dec 1999 14:29:17 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id QAA98213; Tue, 7 Dec 1999 16:26:16 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Tue, 7 Dec 1999 16:26:16 -0600 (CST) From: David Scheidt To: Darryl Okahata Cc: Michael Chin-Yuan Wu , current@FreeBSD.ORG Subject: Re: 3.3-stable -> 4.0-current problem... In-Reply-To: <199912072205.OAA26284@mina.sr.hp.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, 7 Dec 1999, Darryl Okahata wrote: > Michael Chin-Yuan Wu wrote: > > > Please try this tutorial when you move from -stable to -current > > > > www.external.org/freebsd/current.html > > I think you're missing the recent block device obsolescence > change. I had to build and install a -CURRENT yacc when I upgraded right before thanks giving. I haven't looked to see if this has been changed. (I think it was a Makefile.inc? problem.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 14:36:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 3AC1C14E4A; Tue, 7 Dec 1999 14:36:16 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 629311C2B; Tue, 7 Dec 1999 16:37:02 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 52400381B; Tue, 7 Dec 1999 16:37:02 -0500 (EST) Date: Tue, 7 Dec 1999 16:37:02 -0500 (EST) From: Bill Fumerola To: current@FreeBSD.org Cc: dfr@FreeBSD.org Subject: gasp broke world. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug, 'gasp' broke world. targ-env.h: No such file or directory -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 15: 7:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 2FAB114E8E for ; Tue, 7 Dec 1999 15:07:16 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id SAA00335 for ; Tue, 7 Dec 1999 18:07:11 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Tue, 7 Dec 1999 18:07:11 -0500 (EST) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: this is wierd, PCM madness Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alright, Now with the last patch that was on here, FreeBSD detects my ViBRA16X, but for some reason, whenever I try to play something, it doesn't work... eg: culverk:~/.licq/data> esdplay message.wav unsupported sound format: 4112 culverk:~/.licq/data> This file played fine with the Voxware drivers, I can't use those anymore though because they only worked when I was using PNP OS = NO in BIOS... With the most recent PnP fixes I've had to go back to using PnP OS = yes in Bios... ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 15:45: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id C11BE14F22 for ; Tue, 7 Dec 1999 15:44:53 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id SAA00348 for ; Tue, 7 Dec 1999 18:44:48 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Tue, 7 Dec 1999 18:44:48 -0500 (EST) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: Re: this is wierd, PCM madness 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 In addition to the soundcard... my modem won't attach to the sio driver... this is driving me nuts; any help would be appreciated... Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 16:26: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 8C15414C91 for ; Tue, 7 Dec 1999 16:26:01 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id KAA71038 for current@freebsd.org; Wed, 8 Dec 1999 10:56:00 +1030 (CST) (envelope-from newton) Date: Wed, 8 Dec 1999 10:56:00 +1030 From: Mark Newton To: current@freebsd.org Subject: "make world" broken on a 3 month old system Message-ID: <19991208105600.A71026@internode.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to "make world" on a system last built on Sep 29th; it's failing like so: ===> f77doc /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH /usr/obj/usr/src/gnu/lib/libgcc/GRTAGS /usr/obj/usr/src/gnu/lib/libgcc/GSYMS /usr/obj/usr/src/gnu/lib/libgcc/GTAGS echo '#include ' > config.h echo '#include ' >> config.h echo '#include "gansidecl.h"' > tconfig.h echo '#include "i386/xm-i386.h"' >> tconfig.h echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"' >> tm.h echo '#include "svr4.h"' >> tm.h echo '#include ' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "i386/perform.h"' >> tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c *** Signal 12 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Should I be expecting this? :-) - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 17: 2:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from fLuFFy.iNt.tElE.dK (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (Postfix) with ESMTP id 2287114BC3 for ; Tue, 7 Dec 1999 17:02:17 -0800 (PST) (envelope-from kvindeservice@vsZbr.cZ) Received: from localhost (kvindeservice@localhost) by fLuFFy.iNt.tElE.dK (8.9.3/8.9.3) with SMTP id CAA69451 for ; Wed, 8 Dec 1999 02:02:06 +0100 (CET) (envelope-from kvindeservice@vsZbr.cZ) X-Authentication-Warning: fLuFFy.iNt.tElE.dK: kvindeservice owned process doing -bs Date: Wed, 8 Dec 1999 02:02:06 +0100 (CET) From: tele danmarQ kvindeservice X-Sender: kvindeservice@fLuFFy.iNt.tElE.dK Reply-To: luserboy@netscum.dk To: current@freebsd.org Subject: installation floppy and big disks Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG moin moin I've just grabbed the latest -current installation floppies and used them to add freebsd in the third partition of a large disk (can you even get small disks nowadays?) When I attempted to allocate the root partition in the BSD disklabel, it scolded me that it couldn't put the root filesystem there. This time I didn't just give up as I did before when seeing this failure, and after trying a couple other things, it worked. As far as I can see, the system boots just fine in spite of the initial warning, with freebsd in the third partition. If this really is okay, is it possible that this warning is a little off-putting and could be removed, for those cases where the installation should be successful? thanks, barry bouwsma (use reply-to header if you feel compelled to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 18:30:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 07B4B14BE1 for ; Tue, 7 Dec 1999 18:30:50 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with ESMTP id LAA39699; Wed, 8 Dec 1999 11:30:47 +0900 (JST) Date: Wed, 08 Dec 1999 11:30:46 +0900 Message-ID: <14413.49878.644230.10865D@rina.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: schuerge@wjpserver.CS.Uni-SB.DE Cc: fn@radio-do.de, freebsd-current@FreeBSD.ORG Subject: Re: AWE64 problems In-Reply-To: In your message of "Tue, 7 Dec 1999 23:00:02 +0100 (MET)" <199912072200.XAA14065@wjpserver.cs.uni-sb.de> References: <19991207222414.A555@radio-do.de> <199912072200.XAA14065@wjpserver.cs.uni-sb.de> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Dec 1999 23:00:02 +0100 (MET), Thomas Schuerger said: >> --- sbc.c.orig Mon Dec 6 19:26:31 1999 >> +++ sbc.c Tue Dec 7 22:15:25 1999 >> @@ -110,7 +110,7 @@ >> if (error) >> return error; >> else >> - return -100; >> + return -1; >> } >> >> static int Thomas> Works fine for me. Thanks!!! Yes, this patch should work. The probe likelyhood(do we call it so?) for unknown device is -100, so it does not make sense for sbc to return -100. -1 might be too high, -50 sounds good to me. -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 18:43:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from frabjous.viren.org (leesburg-109.cybercable.com [204.188.46.109]) by hub.freebsd.org (Postfix) with ESMTP id 8B28414CFD for ; Tue, 7 Dec 1999 18:43:35 -0800 (PST) (envelope-from root@frabjous.viren.org) Received: (from root@localhost) by frabjous.viren.org (8.9.3/8.9.3) id VAA00222; Tue, 7 Dec 1999 21:24:51 -0500 (EST) (envelope-from root) Date: Tue, 7 Dec 1999 21:24:51 -0500 (EST) Message-Id: <199912080224.VAA00222@frabjous.viren.org> From: Charlie & MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="uePjVVlT3W" Content-Transfer-Encoding: 7bit To: yokota@zodiac.mech.utsunomiya-u.ac.jp Cc: freebsd-current@freebsd.org, viren@rstcorp.com Reply-To: "Viren R. Shah" Subject: Re: Using USB modules with an USB keyboard... X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --uePjVVlT3W Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit >>Is there any way to use only the USB KLDs (i.e. remove all the USB >>options from the kernel config file) on a machine that has an USB >>keyboard? > >Add "flags 0x100" to syscons. Note this is still an experimental >flag. >device sc0 at isa? flags 0x100 ... >But, if it still bothers you, you may "disable" the atkbd driver >included in the kernel, by specifying > >device atkbd0 at atkbdc? disable irq 1 I added your recommendations above to the kernel config file (TWELVE). It didn't work. As can be seen from the dmesg below, when the USB options are present in the kernel, ukbd0 is found. When USB KLDs are used, uhid0 seems to grab the keyboard. [This is the dmesg from a kernel (ELEVEN) that works. The config file for this includes all the USB options except for ums, which is loaded at bootup] As seen below, I have an USB mouse (ums0), and an USB keyboard (which seems to register as an USB keyboard and a mouse -- ums1). The keyboard does have a PS/2 mouse connector on it. Dec 7 20:38:35 frabjous /kernel.old: ata1 at 0x0170 irq 15 on ata-pci0 Dec 7 20:38:35 frabjous /kernel.old: uhci0: irq 10 at device 7.2 on pci0 Dec 7 20:38:35 frabjous /kernel.old: usb0: on uhci0 Dec 7 20:38:35 frabjous /kernel.old: usb0: USB revision 1.0 Dec 7 20:38:35 frabjous /kernel.old: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Dec 7 20:38:35 frabjous /kernel.old: uhub0: 2 ports with 2 removable, self powered Dec 7 20:38:35 frabjous /kernel.old: ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 2, iclass 3/1 Dec 7 20:38:35 frabjous /kernel.old: ums0: 4 buttons and Z dir. Dec 7 20:38:35 frabjous /kernel.old: ukbd0: QTRONIX USB Keyboard and Mouse, rev 1.00/1.10, addr 3, iclass 3/1 Dec 7 20:38:35 frabjous /kernel.old: kbd0 at ukbd0 Dec 7 20:38:35 frabjous /kernel.old: ums1: QTRONIX USB Keyboard and Mouse, rev 1.00/1.10, addr 3, iclass 3/1 Dec 7 20:38:35 frabjous /kernel.old: ums1: 3 buttons Dec 7 20:38:35 frabjous /kernel.old: chip1: at device 7.3 on pci0 Dec 7 20:38:35 frabjous /kernel.old: pcm0: irq 12 at device 11.0 on pci0 Dec 7 20:38:35 frabjous /kernel.old: pci0: unknown card (vendor=0x10b7, dev=0x9050) at 15.0 irq 11 Dec 7 20:38:35 frabjous /kernel.old: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 Dec 7 20:38:35 frabjous /kernel.old: fdc0: FIFO enabled, 8 bytes threshold Dec 7 20:38:35 frabjous /kernel.old: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Dec 7 20:38:35 frabjous /kernel.old: vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 Dec 7 20:38:35 frabjous /kernel.old: sc0: on isa0 Dec 7 20:38:35 frabjous /kernel.old: sc0: VGA <16 virtual consoles, flags=0x200> [This is the kernel (TWELVE) that has no USB options. All the USB modules are loaded at bootup by the loader.conf scripts.] Dec 7 19:57:33 frabjous /kernel: real memory = 134217728 (131072K bytes) Dec 7 19:57:33 frabjous /kernel: avail memory = 127352832 (124368K bytes) Dec 7 19:57:33 frabjous /kernel: Preloaded elf kernel "kernel" at 0xc02ae000. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "vesa.ko" at 0xc02ae09c. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "cd9660.ko" at 0xc02ae138. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "procfs.ko" at 0xc02ae1d8. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "green_saver.ko" at 0xc02ae278. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "usb.ko" at 0xc02ae31c. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ugen.ko" at 0xc02ae3b8. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "uhid.ko" at 0xc02ae454. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ukbd.ko" at 0xc02ae4f0. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ulpt.ko" at 0xc02ae58c. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ums.ko" at 0xc02ae628. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "umass.ko" at 0xc02ae6c4. Dec 7 19:57:33 frabjous /kernel: link_elf: symbol cam_simq_alloc undefined ... Dec 7 19:57:33 frabjous /kernel: uhci0: irq 10 at device 7.2 on pci0 Dec 7 19:57:33 frabjous /kernel: usb0: on uhci0 Dec 7 19:57:33 frabjous /kernel: usb0: USB revision 1.0 Dec 7 19:57:33 frabjous /kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Dec 7 19:57:33 frabjous /kernel: uhub0: 2 ports with 2 removable, self powered Dec 7 19:57:33 frabjous /kernel: ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 2, iclass 3/1 Dec 7 19:57:33 frabjous /kernel: ums0: 4 buttons and Z dir. Dec 7 19:57:33 frabjous /kernel: uhid0: QTRONIX USB Keyboard and Mouse, rev 1.00/1.10, addr 3, iclass 3/1 Dec 7 19:57:33 frabjous /kernel: ums1: QTRONIX USB Keyboard and Mouse, rev 1.00/1.10, addr 3, iclass 3/1 Dec 7 19:57:33 frabjous /kernel: ums1: 3 buttons Dec 7 19:57:33 frabjous /kernel: chip1: at device 7.3 on pci0 Dec 7 19:57:33 frabjous /kernel: pcm0: irq 12 at device 11.0 on pci0 Dec 7 19:57:33 frabjous /kernel: pci0: unknown card (vendor=0x10b7, dev=0x9050) at 15.0 irq 11 Dec 7 19:57:33 frabjous /kernel: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 Dec 7 19:57:33 frabjous /kernel: fdc0: FIFO enabled, 8 bytes threshold Dec 7 19:57:33 frabjous /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Dec 7 19:57:33 frabjous /kernel: vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 Dec 7 19:57:33 frabjous /kernel: sc0: at flags 0x100 on isa0 Dec 7 19:57:33 frabjous /kernel: sc0: VGA <16 virtual consoles, flags=0x300> Dec 7 19:57:33 frabjous /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 I figured that teh uhid module was messing up the ukbd module, so I booted up TWELVE and loaded only certain USB modules as seen below: Dec 7 21:02:34 frabjous /kernel: real memory = 134217728 (131072K bytes) Dec 7 21:02:34 frabjous /kernel: avail memory = 127483904 (124496K bytes) Dec 7 21:02:34 frabjous /kernel: Preloaded elf kernel "kernel" at 0xc028e000. Dec 7 21:02:34 frabjous /kernel: Preloaded elf module "usb.ko" at 0xc028e09c. Dec 7 21:02:34 frabjous /kernel: Preloaded elf module "ugen.ko" at 0xc028e138. Dec 7 21:02:34 frabjous /kernel: Preloaded elf module "ukbd.ko" at 0xc028e1d4. Dec 7 21:02:34 frabjous /kernel: Preloaded elf module "ums.ko" at 0xc028e270. Dec 7 21:02:34 frabjous /kernel: Preloaded elf module "umass.ko" at 0xc028e30c. Dec 7 21:02:34 frabjous /kernel: link_elf: symbol cam_simq_alloc undefined Dec 7 21:02:34 frabjous /kernel: Pentium Pro MTRR support enabled Dec 7 21:02:34 frabjous /kernel: npx0: on motherboard Dec 7 21:02:34 frabjous /kernel: npx0: INT 16 interface Dec 7 21:02:34 frabjous /kernel: pcib0: on motherboard Dec 7 21:02:34 frabjous /kernel: pci0: on pcib0 Dec 7 21:02:34 frabjous /kernel: pcib1: at device 1.0 on pci0 Dec 7 21:02:34 frabjous /kernel: pci1: on pcib1 Dec 7 21:02:34 frabjous /kernel: vga-pci0: irq 11 at device 0.0 on pci1 Dec 7 21:02:34 frabjous /kernel: isab0: at device 7.0 on pci0 Dec 7 21:02:34 frabjous /kernel: isa0: on isab0 Dec 7 21:02:34 frabjous /kernel: ata-pci0: at device 7.1 on pci0 Dec 7 21:02:34 frabjous /kernel: ata-pci0: Busmastering DMA supported Dec 7 21:02:34 frabjous /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Dec 7 21:02:34 frabjous /kernel: ata1 at 0x0170 irq 15 on ata-pci0 Dec 7 21:02:34 frabjous /kernel: uhci0: irq 10 at device 7.2 on pci0 Dec 7 21:02:34 frabjous /kernel: usb0: on uhci0 Dec 7 21:02:34 frabjous /kernel: usb0: USB revision 1.0 Dec 7 21:02:34 frabjous /kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Dec 7 21:02:34 frabjous /kernel: uhub0: 2 ports with 2 removable, self powered Dec 7 21:02:34 frabjous /kernel: ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 2, iclass 3/1 Dec 7 21:02:34 frabjous /kernel: ums0: 4 buttons and Z dir. Dec 7 21:02:34 frabjous /kernel: ums1: QTRONIX USB Keyboard and Mouse, rev 1.00/1.10, addr 3, iclass 3/1 Dec 7 21:02:34 frabjous /kernel: ums1: 3 buttons Dec 7 21:02:34 frabjous /kernel: chip1: at device 7.3 on pci0 Dec 7 21:02:34 frabjous /kernel: pcm0: irq 12 at device 11.0 on pci0 Dec 7 21:02:34 frabjous /kernel: pci0: unknown card (vendor=0x10b7, dev=0x9050) at 15.0 irq 11 Dec 7 21:02:34 frabjous /kernel: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 Dec 7 21:02:34 frabjous /kernel: fdc0: FIFO enabled, 8 bytes threshold Dec 7 21:02:34 frabjous /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Dec 7 21:02:34 frabjous /kernel: vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 Dec 7 21:02:34 frabjous /kernel: sc0: at flags 0x100 on isa0 Dec 7 21:02:34 frabjous /kernel: sc0: VGA <16 virtual consoles, flags=0x300> Here's the config file for the non-working kernel (TWELVE): --uePjVVlT3W Content-Type: application/octet-stream Content-Description: non-working kernel Content-Disposition: attachment; filename="TWELVE" Content-Transfer-Encoding: base64 IwojIEdFTkVSSUMgLS0gR2VuZXJpYyBtYWNoaW5lIHdpdGggV0QvQUh4L05DUi9CVHggZmFt aWx5IGRpc2tzCiMKIyBGb3IgbW9yZSBpbmZvcm1hdGlvbiByZWFkIHRoZSBoYW5kYm9vayBw YXJ0IFN5c3RlbSBBZG1pbmlzdHJhdGlvbiAtPiAKIyBDb25maWd1cmluZyB0aGUgRnJlZUJT RCBLZXJuZWwgLT4gVGhlIENvbmZpZ3VyYXRpb24gRmlsZS4gCiMgVGhlIGhhbmRib29rIGlz IGF2YWlsYWJsZSBpbiAvdXNyL3NoYXJlL2RvYy9oYW5kYm9vayBvciBvbmxpbmUgYXMKIyBs YXRlc3QgdmVyc2lvbiBmcm9tIHRoZSBGcmVlQlNEIFdvcmxkIFdpZGUgV2ViIHNlcnZlciAK IyA8VVJMOmh0dHA6Ly93d3cuRnJlZUJTRC5PUkcvPgojCiMgQW4gZXhoYXVzdGl2ZSBsaXN0 IG9mIG9wdGlvbnMgYW5kIG1vcmUgZGV0YWlsZWQgZXhwbGFuYXRpb25zIG9mIHRoZSAKIyBk ZXZpY2UgbGluZXMgaXMgcHJlc2VudCBpbiB0aGUgLi9MSU5UIGNvbmZpZ3VyYXRpb24gZmls ZS4gSWYgeW91IGFyZSAKIyBpbiBkb3VidCBhcyB0byB0aGUgcHVycG9zZSBvciBuZWNlc3Np dHkgb2YgYSBsaW5lLCBjaGVjayBmaXJzdCBpbiBMSU5ULgojCiMJJElkOiBHRU5FUklDLHYg MS4xNTYgMTk5OS8wMy8yOSAxNzo1NjoyNyBrZW4gRXhwICQKCm1hY2hpbmUJCSJpMzg2Igpj cHUJCSJJNjg2X0NQVSIKaWRlbnQJCVRXRUxWRQptYXh1c2Vycwk2NAoKb3B0aW9ucwkJSU5F VAkJCSNJbnRlck5FVHdvcmtpbmcKb3B0aW9ucwkJRkZTCQkJI0JlcmtlbGV5IEZhc3QgRmls ZXN5c3RlbQpvcHRpb25zCQlGRlNfUk9PVAkJI0ZGUyB1c2FibGUgYXMgcm9vdCBkZXZpY2Ug W2tlZXAgdGhpcyFdCm9wdGlvbnMJCSJDT01QQVRfNDMiCQkjQ29tcGF0aWJsZSB3aXRoIEJT RCA0LjMgW0tFRVAgVEhJUyFdCm9wdGlvbnMJCVVDT05TT0xFCQkjQWxsb3cgdXNlcnMgdG8g Z3JhYiB0aGUgY29uc29sZQoKY29uZmlnCQlrZXJuZWwJCgoKY29udHJvbGxlcglpc2EwCiNj b250cm9sbGVyCXBucDAJCQkjIFBuUCBzdXBwb3J0IGZvciBJU0EKY29udHJvbGxlcglwY2kw Cgpjb250cm9sbGVyCWZkYzAJYXQgaXNhPyBwb3J0ICJJT19GRDEiICBpcnEgNiBkcnEgMgpk ZXZpY2UJCWZkMAlhdCBmZGMwIGRyaXZlIDAKCmNvbnRyb2xsZXIgICAgIGF0YTAKZGV2aWNl ICAgICAgICAgYXRhZGlzazAgICAgICAgICMgQVRBIGRpc2sgZHJpdmVzCmRldmljZSAgICAg ICAgIGF0YXBpY2QwICAgICAgICAjIEFUQVBJIENEUk9NIGRyaXZlcwpkZXZpY2UgICAgICAg ICBhdGFwaWZkMCAgICAgICAgIyBBVEFQSSBmbG9wcHkgZHJpdmVzCgoKCgpkZXZpY2UJCXZn YTAJYXQgaXNhPyBwb3J0ID8gY29uZmxpY3RzCgojIHNwbGFzaCBzY3JlZW4vc2NyZWVuIHNh dmVyCnBzZXVkby1kZXZpY2UJc3BsYXNoCgojIHN5c2NvbnMgaXMgdGhlIGRlZmF1bHQgY29u c29sZSBkcml2ZXIsIHJlc2VtYmxpbmcgYW4gU0NPIGNvbnNvbGUKZGV2aWNlCQlzYzAJYXQg aXNhPyAgZmxhZ3MgMHgxMDAKCmRldmljZQkJbnB4MAlhdCBuZXh1cz8gcG9ydCBJT19OUFgg aXJxIDEzCiNkZXZpY2UgICAgICAgICAgYXBtMCAgICBhdCBuZXh1cz8gZmxhZ3MgMHgzMQoK ZGV2aWNlCQlzaW8wCWF0IGlzYT8gcG9ydCAiSU9fQ09NMSIgZmxhZ3MgMHgxMCAgaXJxIDQK I2RldmljZQkJc2lvMQlhdCBpc2E/IHBvcnQgIklPX0NPTTIiICBpcnEgMwoKIyBQYXJhbGxl bCBwb3J0CmRldmljZQkJcHBjMAlhdCBpc2E/IHBvcnQ/ICBpcnEgNwpjb250cm9sbGVyCXBw YnVzMApkZXZpY2UJCWxwdDAJYXQgcHBidXM/CgoKcHNldWRvLWRldmljZQlsb29wCnBzZXVk by1kZXZpY2UJZXRoZXIKcHNldWRvLWRldmljZQlwdHkJMTYKcHNldWRvLWRldmljZSAgIHNw ZWFrZXIKcHNldWRvLWRldmljZQlicGYgCTIKCiMgS1RSQUNFIGVuYWJsZXMgdGhlIHN5c3Rl bS1jYWxsIHRyYWNpbmcgZmFjaWxpdHkga3RyYWNlKDIpLgojIFRoaXMgYWRkcyA0IEtCIGJs b2F0IHRvIHlvdXIga2VybmVsLCBhbmQgc2xpZ2h0bHkgaW5jcmVhc2VzCiMgdGhlIGNvc3Rz IG9mIGVhY2ggc3lzY2FsbC4Kb3B0aW9ucwkJS1RSQUNFCQkja2VybmVsIHRyYWNpbmcKCiMg VGhpcyBwcm92aWRlcyBzdXBwb3J0IGZvciBTeXN0ZW0gViBzaGFyZWQgbWVtb3J5IGFuZCBt ZXNzYWdlIHF1ZXVlcy4KIwpvcHRpb25zICAgICAgICAgU1lTVlNITQpvcHRpb25zICAgICAg ICAgU1lTVk1TRwoKIyBVU0Igc3VwcG9ydAojY29udHJvbGxlciAgICB1aGNpMAojY29udHJv bGxlciAgICBvaGNpMAojY29udHJvbGxlciAgICB1c2IwCiMKIyBmb3IgdGhlIG1vbWVudCB3 ZSBoYXZlIHRvIHNwZWNpZnkgdGhlIHByaW9yaXRpZXMgb2YgdGhlIGRldmljZQojIGRyaXZl cnMgZXhwbGljaXRseSBieSB0aGUgb3JkZXJpbmcgaW4gdGhlIGxpc3QgYmVsb3cuIFRoaXMg d2lsbAojIGJlIGNoYW5nZWQgaW4gdGhlIGZ1dHVyZS4KIwojZGV2aWNlICAgICAgICB1bXMw CiNkZXZpY2UgICAgICAgIHVrYmQwCiNkZXZpY2UgICAgICAgIHVscHQwCiNkZXZpY2UgICAg ICAgIHVoaWQwCiNkZXZpY2UgICAgICAgIHVnZW4wCgoKZGV2aWNlIHBjbTAgCiNhdCBpc2E/ IHBvcnQgPyAgaXJxID8gZHJxID8gZmxhZ3MgMHgwCmRldmljZSBwY2EwIGF0IGlzYT8gcG9y dCAiSU9fVElNRVIxIiAKCgpvcHRpb25zICAgICAgICAgICAgICAgIFNPRlRVUERBVEVTCgoK b3B0aW9ucyAgICAgICAgIElERV9ERUxBWT04MDAwCm9wdGlvbnMJCUtCRF9JTlNUQUxMX0NE RVYKCgojIGF0a2JkYzAgY29udHJvbHMgYm90aCB0aGUga2V5Ym9hcmQgYW5kIHRoZSBQUy8y IG1vdXNlCmNvbnRyb2xsZXIJYXRrYmRjMAlhdCBpc2E/IHBvcnQgSU9fS0JECmRldmljZQkJ YXRrYmQwCWF0IGF0a2JkYz8gZGlzYWJsZSBpcnEgMQo= --uePjVVlT3W Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Here's the config file for the working kernel (ELEVEN): --uePjVVlT3W Content-Type: application/octet-stream Content-Description: working kernel Content-Disposition: attachment; filename="ELEVEN" Content-Transfer-Encoding: base64 IwojIEdFTkVSSUMgLS0gR2VuZXJpYyBtYWNoaW5lIHdpdGggV0QvQUh4L05DUi9CVHggZmFt aWx5IGRpc2tzCiMKIyBGb3IgbW9yZSBpbmZvcm1hdGlvbiByZWFkIHRoZSBoYW5kYm9vayBw YXJ0IFN5c3RlbSBBZG1pbmlzdHJhdGlvbiAtPiAKIyBDb25maWd1cmluZyB0aGUgRnJlZUJT RCBLZXJuZWwgLT4gVGhlIENvbmZpZ3VyYXRpb24gRmlsZS4gCiMgVGhlIGhhbmRib29rIGlz IGF2YWlsYWJsZSBpbiAvdXNyL3NoYXJlL2RvYy9oYW5kYm9vayBvciBvbmxpbmUgYXMKIyBs YXRlc3QgdmVyc2lvbiBmcm9tIHRoZSBGcmVlQlNEIFdvcmxkIFdpZGUgV2ViIHNlcnZlciAK IyA8VVJMOmh0dHA6Ly93d3cuRnJlZUJTRC5PUkcvPgojCiMgQW4gZXhoYXVzdGl2ZSBsaXN0 IG9mIG9wdGlvbnMgYW5kIG1vcmUgZGV0YWlsZWQgZXhwbGFuYXRpb25zIG9mIHRoZSAKIyBk ZXZpY2UgbGluZXMgaXMgcHJlc2VudCBpbiB0aGUgLi9MSU5UIGNvbmZpZ3VyYXRpb24gZmls ZS4gSWYgeW91IGFyZSAKIyBpbiBkb3VidCBhcyB0byB0aGUgcHVycG9zZSBvciBuZWNlc3Np dHkgb2YgYSBsaW5lLCBjaGVjayBmaXJzdCBpbiBMSU5ULgojCiMJJElkOiBHRU5FUklDLHYg MS4xNTYgMTk5OS8wMy8yOSAxNzo1NjoyNyBrZW4gRXhwICQKCm1hY2hpbmUJCSJpMzg2Igpj cHUJCSJJNjg2X0NQVSIKaWRlbnQJCUVMRVZFTgptYXh1c2Vycwk2NAoKb3B0aW9ucwkJSU5F VAkJCSNJbnRlck5FVHdvcmtpbmcKb3B0aW9ucwkJRkZTCQkJI0JlcmtlbGV5IEZhc3QgRmls ZXN5c3RlbQpvcHRpb25zCQlGRlNfUk9PVAkJI0ZGUyB1c2FibGUgYXMgcm9vdCBkZXZpY2Ug W2tlZXAgdGhpcyFdCm9wdGlvbnMJCSJDT01QQVRfNDMiCQkjQ29tcGF0aWJsZSB3aXRoIEJT RCA0LjMgW0tFRVAgVEhJUyFdCm9wdGlvbnMJCVVDT05TT0xFCQkjQWxsb3cgdXNlcnMgdG8g Z3JhYiB0aGUgY29uc29sZQoKY29uZmlnCQlrZXJuZWwJCgoKY29udHJvbGxlcglpc2EwCmNv bnRyb2xsZXIJcG5wMAkJCSMgUG5QIHN1cHBvcnQgZm9yIElTQQpjb250cm9sbGVyCXBjaTAK CmNvbnRyb2xsZXIJZmRjMAlhdCBpc2E/IHBvcnQgIklPX0ZEMSIgIGlycSA2IGRycSAyCmRl dmljZQkJZmQwCWF0IGZkYzAgZHJpdmUgMAoKY29udHJvbGxlciAgICAgYXRhMApkZXZpY2Ug ICAgICAgICBhdGFkaXNrMCAgICAgICAgIyBBVEEgZGlzayBkcml2ZXMKZGV2aWNlICAgICAg ICAgYXRhcGljZDAgICAgICAgICMgQVRBUEkgQ0RST00gZHJpdmVzCmRldmljZSAgICAgICAg IGF0YXBpZmQwICAgICAgICAjIEFUQVBJIGZsb3BweSBkcml2ZXMKCgoKCmRldmljZQkJdmdh MAlhdCBpc2E/IHBvcnQgPyBjb25mbGljdHMKCiMgc3BsYXNoIHNjcmVlbi9zY3JlZW4gc2F2 ZXIKcHNldWRvLWRldmljZQlzcGxhc2gKCiMgc3lzY29ucyBpcyB0aGUgZGVmYXVsdCBjb25z b2xlIGRyaXZlciwgcmVzZW1ibGluZyBhbiBTQ08gY29uc29sZQpkZXZpY2UJCXNjMAlhdCBp c2E/ICAKCmRldmljZQkJbnB4MAlhdCBuZXh1cz8gcG9ydCBJT19OUFggaXJxIDEzCiNkZXZp Y2UgICAgICAgICAgYXBtMCAgICBhdCBuZXh1cz8gZmxhZ3MgMHgzMQoKZGV2aWNlCQlzaW8w CWF0IGlzYT8gcG9ydCAiSU9fQ09NMSIgZmxhZ3MgMHgxMCAgaXJxIDQKI2RldmljZQkJc2lv MQlhdCBpc2E/IHBvcnQgIklPX0NPTTIiICBpcnEgMwoKIyBQYXJhbGxlbCBwb3J0CmRldmlj ZQkJcHBjMAlhdCBpc2E/IHBvcnQ/ICBpcnEgNwpjb250cm9sbGVyCXBwYnVzMApkZXZpY2UJ CWxwdDAJYXQgcHBidXM/CgoKcHNldWRvLWRldmljZQlsb29wCnBzZXVkby1kZXZpY2UJZXRo ZXIKcHNldWRvLWRldmljZQlwdHkJMTYKcHNldWRvLWRldmljZSAgIHNwZWFrZXIKcHNldWRv LWRldmljZQlicGYgCTIKCiMgS1RSQUNFIGVuYWJsZXMgdGhlIHN5c3RlbS1jYWxsIHRyYWNp bmcgZmFjaWxpdHkga3RyYWNlKDIpLgojIFRoaXMgYWRkcyA0IEtCIGJsb2F0IHRvIHlvdXIg a2VybmVsLCBhbmQgc2xpZ2h0bHkgaW5jcmVhc2VzCiMgdGhlIGNvc3RzIG9mIGVhY2ggc3lz Y2FsbC4Kb3B0aW9ucwkJS1RSQUNFCQkja2VybmVsIHRyYWNpbmcKCiMgVGhpcyBwcm92aWRl cyBzdXBwb3J0IGZvciBTeXN0ZW0gViBzaGFyZWQgbWVtb3J5IGFuZCBtZXNzYWdlIHF1ZXVl cy4KIwpvcHRpb25zICAgICAgICAgU1lTVlNITQpvcHRpb25zICAgICAgICAgU1lTVk1TRwoK IyBVU0Igc3VwcG9ydApjb250cm9sbGVyICAgIHVoY2kwCmNvbnRyb2xsZXIgICAgb2hjaTAK Y29udHJvbGxlciAgICB1c2IwCiMKIyBmb3IgdGhlIG1vbWVudCB3ZSBoYXZlIHRvIHNwZWNp ZnkgdGhlIHByaW9yaXRpZXMgb2YgdGhlIGRldmljZQojIGRyaXZlcnMgZXhwbGljaXRseSBi eSB0aGUgb3JkZXJpbmcgaW4gdGhlIGxpc3QgYmVsb3cuIFRoaXMgd2lsbAojIGJlIGNoYW5n ZWQgaW4gdGhlIGZ1dHVyZS4KIwojZGV2aWNlICAgICAgICB1bXMwCmRldmljZSAgICAgICAg dWtiZDAKI2RldmljZSAgICAgICAgdWxwdDAKI2RldmljZSAgICAgICAgdWhpZDAKI2Rldmlj ZSAgICAgICAgdWdlbjAKCgpkZXZpY2UgcGNtMCAKI2F0IGlzYT8gcG9ydCA/ICBpcnEgPyBk cnEgPyBmbGFncyAweDAKZGV2aWNlIHBjYTAgYXQgaXNhPyBwb3J0ICJJT19USU1FUjEiIAoK Cm9wdGlvbnMgICAgICAgICAgICAgICAgU09GVFVQREFURVMKCgpvcHRpb25zICAgICAgICAg SURFX0RFTEFZPTgwMDAKb3B0aW9ucwkJS0JEX0lOU1RBTExfQ0RFVgoKCg== --uePjVVlT3W Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hope all this information helps. Viren viren@rstcorp.com --uePjVVlT3W-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 18:44:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from frabjous.viren.org (leesburg-109.cybercable.com [204.188.46.109]) by hub.freebsd.org (Postfix) with ESMTP id 69B5814EC6 for ; Tue, 7 Dec 1999 18:43:50 -0800 (PST) (envelope-from root@frabjous.viren.org) Received: (from root@localhost) by frabjous.viren.org (8.9.3/8.9.3) id VAA00222; Tue, 7 Dec 1999 21:24:51 -0500 (EST) (envelope-from root) Date: Tue, 7 Dec 1999 21:24:51 -0500 (EST) Message-Id: <199912080224.VAA00222@frabjous.viren.org> From: Charlie & MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="uePjVVlT3W" Content-Transfer-Encoding: 7bit To: yokota@zodiac.mech.utsunomiya-u.ac.jp Cc: freebsd-current@freebsd.org, viren@rstcorp.com Reply-To: "Viren R. Shah" Subject: Re: Using USB modules with an USB keyboard... X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --uePjVVlT3W Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit >>Is there any way to use only the USB KLDs (i.e. remove all the USB >>options from the kernel config file) on a machine that has an USB >>keyboard? > >Add "flags 0x100" to syscons. Note this is still an experimental >flag. >device sc0 at isa? flags 0x100 ... >But, if it still bothers you, you may "disable" the atkbd driver >included in the kernel, by specifying > >device atkbd0 at atkbdc? disable irq 1 I added your recommendations above to the kernel config file (TWELVE). It didn't work. As can be seen from the dmesg below, when the USB options are present in the kernel, ukbd0 is found. When USB KLDs are used, uhid0 seems to grab the keyboard. [This is the dmesg from a kernel (ELEVEN) that works. The config file for this includes all the USB options except for ums, which is loaded at bootup] As seen below, I have an USB mouse (ums0), and an USB keyboard (which seems to register as an USB keyboard and a mouse -- ums1). The keyboard does have a PS/2 mouse connector on it. Dec 7 20:38:35 frabjous /kernel.old: ata1 at 0x0170 irq 15 on ata-pci0 Dec 7 20:38:35 frabjous /kernel.old: uhci0: irq 10 at device 7.2 on pci0 Dec 7 20:38:35 frabjous /kernel.old: usb0: on uhci0 Dec 7 20:38:35 frabjous /kernel.old: usb0: USB revision 1.0 Dec 7 20:38:35 frabjous /kernel.old: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Dec 7 20:38:35 frabjous /kernel.old: uhub0: 2 ports with 2 removable, self powered Dec 7 20:38:35 frabjous /kernel.old: ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 2, iclass 3/1 Dec 7 20:38:35 frabjous /kernel.old: ums0: 4 buttons and Z dir. Dec 7 20:38:35 frabjous /kernel.old: ukbd0: QTRONIX USB Keyboard and Mouse, rev 1.00/1.10, addr 3, iclass 3/1 Dec 7 20:38:35 frabjous /kernel.old: kbd0 at ukbd0 Dec 7 20:38:35 frabjous /kernel.old: ums1: QTRONIX USB Keyboard and Mouse, rev 1.00/1.10, addr 3, iclass 3/1 Dec 7 20:38:35 frabjous /kernel.old: ums1: 3 buttons Dec 7 20:38:35 frabjous /kernel.old: chip1: at device 7.3 on pci0 Dec 7 20:38:35 frabjous /kernel.old: pcm0: irq 12 at device 11.0 on pci0 Dec 7 20:38:35 frabjous /kernel.old: pci0: unknown card (vendor=0x10b7, dev=0x9050) at 15.0 irq 11 Dec 7 20:38:35 frabjous /kernel.old: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 Dec 7 20:38:35 frabjous /kernel.old: fdc0: FIFO enabled, 8 bytes threshold Dec 7 20:38:35 frabjous /kernel.old: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Dec 7 20:38:35 frabjous /kernel.old: vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 Dec 7 20:38:35 frabjous /kernel.old: sc0: on isa0 Dec 7 20:38:35 frabjous /kernel.old: sc0: VGA <16 virtual consoles, flags=0x200> [This is the kernel (TWELVE) that has no USB options. All the USB modules are loaded at bootup by the loader.conf scripts.] Dec 7 19:57:33 frabjous /kernel: real memory = 134217728 (131072K bytes) Dec 7 19:57:33 frabjous /kernel: avail memory = 127352832 (124368K bytes) Dec 7 19:57:33 frabjous /kernel: Preloaded elf kernel "kernel" at 0xc02ae000. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "vesa.ko" at 0xc02ae09c. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "cd9660.ko" at 0xc02ae138. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "procfs.ko" at 0xc02ae1d8. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "green_saver.ko" at 0xc02ae278. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "usb.ko" at 0xc02ae31c. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ugen.ko" at 0xc02ae3b8. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "uhid.ko" at 0xc02ae454. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ukbd.ko" at 0xc02ae4f0. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ulpt.ko" at 0xc02ae58c. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ums.ko" at 0xc02ae628. Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "umass.ko" at 0xc02ae6c4. Dec 7 19:57:33 frabjous /kernel: link_elf: symbol cam_simq_alloc undefined ... Dec 7 19:57:33 frabjous /kernel: uhci0: irq 10 at device 7.2 on pci0 Dec 7 19:57:33 frabjous /kernel: usb0: on uhci0 Dec 7 19:57:33 frabjous /kernel: usb0: USB revision 1.0 Dec 7 19:57:33 frabjous /kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Dec 7 19:57:33 frabjous /kernel: uhub0: 2 ports with 2 removable, self powered Dec 7 19:57:33 frabjous /kernel: ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 2, iclass 3/1 Dec 7 19:57:33 frabjous /kernel: ums0: 4 buttons and Z dir. Dec 7 19:57:33 frabjous /kernel: uhid0: QTRONIX USB Keyboard and Mouse, rev 1.00/1.10, addr 3, iclass 3/1 Dec 7 19:57:33 frabjous /kernel: ums1: QTRONIX USB Keyboard and Mouse, rev 1.00/1.10, addr 3, iclass 3/1 Dec 7 19:57:33 frabjous /kernel: ums1: 3 buttons Dec 7 19:57:33 frabjous /kernel: chip1: at device 7.3 on pci0 Dec 7 19:57:33 frabjous /kernel: pcm0: irq 12 at device 11.0 on pci0 Dec 7 19:57:33 frabjous /kernel: pci0: unknown card (vendor=0x10b7, dev=0x9050) at 15.0 irq 11 Dec 7 19:57:33 frabjous /kernel: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 Dec 7 19:57:33 frabjous /kernel: fdc0: FIFO enabled, 8 bytes threshold Dec 7 19:57:33 frabjous /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Dec 7 19:57:33 frabjous /kernel: vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 Dec 7 19:57:33 frabjous /kernel: sc0: at flags 0x100 on isa0 Dec 7 19:57:33 frabjous /kernel: sc0: VGA <16 virtual consoles, flags=0x300> Dec 7 19:57:33 frabjous /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 I figured that teh uhid module was messing up the ukbd module, so I booted up TWELVE and loaded only certain USB modules as seen below: Dec 7 21:02:34 frabjous /kernel: real memory = 134217728 (131072K bytes) Dec 7 21:02:34 frabjous /kernel: avail memory = 127483904 (124496K bytes) Dec 7 21:02:34 frabjous /kernel: Preloaded elf kernel "kernel" at 0xc028e000. Dec 7 21:02:34 frabjous /kernel: Preloaded elf module "usb.ko" at 0xc028e09c. Dec 7 21:02:34 frabjous /kernel: Preloaded elf module "ugen.ko" at 0xc028e138. Dec 7 21:02:34 frabjous /kernel: Preloaded elf module "ukbd.ko" at 0xc028e1d4. Dec 7 21:02:34 frabjous /kernel: Preloaded elf module "ums.ko" at 0xc028e270. Dec 7 21:02:34 frabjous /kernel: Preloaded elf module "umass.ko" at 0xc028e30c. Dec 7 21:02:34 frabjous /kernel: link_elf: symbol cam_simq_alloc undefined Dec 7 21:02:34 frabjous /kernel: Pentium Pro MTRR support enabled Dec 7 21:02:34 frabjous /kernel: npx0: on motherboard Dec 7 21:02:34 frabjous /kernel: npx0: INT 16 interface Dec 7 21:02:34 frabjous /kernel: pcib0: on motherboard Dec 7 21:02:34 frabjous /kernel: pci0: on pcib0 Dec 7 21:02:34 frabjous /kernel: pcib1: at device 1.0 on pci0 Dec 7 21:02:34 frabjous /kernel: pci1: on pcib1 Dec 7 21:02:34 frabjous /kernel: vga-pci0: irq 11 at device 0.0 on pci1 Dec 7 21:02:34 frabjous /kernel: isab0: at device 7.0 on pci0 Dec 7 21:02:34 frabjous /kernel: isa0: on isab0 Dec 7 21:02:34 frabjous /kernel: ata-pci0: at device 7.1 on pci0 Dec 7 21:02:34 frabjous /kernel: ata-pci0: Busmastering DMA supported Dec 7 21:02:34 frabjous /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Dec 7 21:02:34 frabjous /kernel: ata1 at 0x0170 irq 15 on ata-pci0 Dec 7 21:02:34 frabjous /kernel: uhci0: irq 10 at device 7.2 on pci0 Dec 7 21:02:34 frabjous /kernel: usb0: on uhci0 Dec 7 21:02:34 frabjous /kernel: usb0: USB revision 1.0 Dec 7 21:02:34 frabjous /kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Dec 7 21:02:34 frabjous /kernel: uhub0: 2 ports with 2 removable, self powered Dec 7 21:02:34 frabjous /kernel: ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 2, iclass 3/1 Dec 7 21:02:34 frabjous /kernel: ums0: 4 buttons and Z dir. Dec 7 21:02:34 frabjous /kernel: ums1: QTRONIX USB Keyboard and Mouse, rev 1.00/1.10, addr 3, iclass 3/1 Dec 7 21:02:34 frabjous /kernel: ums1: 3 buttons Dec 7 21:02:34 frabjous /kernel: chip1: at device 7.3 on pci0 Dec 7 21:02:34 frabjous /kernel: pcm0: irq 12 at device 11.0 on pci0 Dec 7 21:02:34 frabjous /kernel: pci0: unknown card (vendor=0x10b7, dev=0x9050) at 15.0 irq 11 Dec 7 21:02:34 frabjous /kernel: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 Dec 7 21:02:34 frabjous /kernel: fdc0: FIFO enabled, 8 bytes threshold Dec 7 21:02:34 frabjous /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Dec 7 21:02:34 frabjous /kernel: vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 Dec 7 21:02:34 frabjous /kernel: sc0: at flags 0x100 on isa0 Dec 7 21:02:34 frabjous /kernel: sc0: VGA <16 virtual consoles, flags=0x300> Here's the config file for the non-working kernel (TWELVE): --uePjVVlT3W Content-Type: application/octet-stream Content-Description: non-working kernel Content-Disposition: attachment; filename="TWELVE" Content-Transfer-Encoding: base64 IwojIEdFTkVSSUMgLS0gR2VuZXJpYyBtYWNoaW5lIHdpdGggV0QvQUh4L05DUi9CVHggZmFt aWx5IGRpc2tzCiMKIyBGb3IgbW9yZSBpbmZvcm1hdGlvbiByZWFkIHRoZSBoYW5kYm9vayBw YXJ0IFN5c3RlbSBBZG1pbmlzdHJhdGlvbiAtPiAKIyBDb25maWd1cmluZyB0aGUgRnJlZUJT RCBLZXJuZWwgLT4gVGhlIENvbmZpZ3VyYXRpb24gRmlsZS4gCiMgVGhlIGhhbmRib29rIGlz IGF2YWlsYWJsZSBpbiAvdXNyL3NoYXJlL2RvYy9oYW5kYm9vayBvciBvbmxpbmUgYXMKIyBs YXRlc3QgdmVyc2lvbiBmcm9tIHRoZSBGcmVlQlNEIFdvcmxkIFdpZGUgV2ViIHNlcnZlciAK IyA8VVJMOmh0dHA6Ly93d3cuRnJlZUJTRC5PUkcvPgojCiMgQW4gZXhoYXVzdGl2ZSBsaXN0 IG9mIG9wdGlvbnMgYW5kIG1vcmUgZGV0YWlsZWQgZXhwbGFuYXRpb25zIG9mIHRoZSAKIyBk ZXZpY2UgbGluZXMgaXMgcHJlc2VudCBpbiB0aGUgLi9MSU5UIGNvbmZpZ3VyYXRpb24gZmls ZS4gSWYgeW91IGFyZSAKIyBpbiBkb3VidCBhcyB0byB0aGUgcHVycG9zZSBvciBuZWNlc3Np dHkgb2YgYSBsaW5lLCBjaGVjayBmaXJzdCBpbiBMSU5ULgojCiMJJElkOiBHRU5FUklDLHYg MS4xNTYgMTk5OS8wMy8yOSAxNzo1NjoyNyBrZW4gRXhwICQKCm1hY2hpbmUJCSJpMzg2Igpj cHUJCSJJNjg2X0NQVSIKaWRlbnQJCVRXRUxWRQptYXh1c2Vycwk2NAoKb3B0aW9ucwkJSU5F VAkJCSNJbnRlck5FVHdvcmtpbmcKb3B0aW9ucwkJRkZTCQkJI0JlcmtlbGV5IEZhc3QgRmls ZXN5c3RlbQpvcHRpb25zCQlGRlNfUk9PVAkJI0ZGUyB1c2FibGUgYXMgcm9vdCBkZXZpY2Ug W2tlZXAgdGhpcyFdCm9wdGlvbnMJCSJDT01QQVRfNDMiCQkjQ29tcGF0aWJsZSB3aXRoIEJT RCA0LjMgW0tFRVAgVEhJUyFdCm9wdGlvbnMJCVVDT05TT0xFCQkjQWxsb3cgdXNlcnMgdG8g Z3JhYiB0aGUgY29uc29sZQoKY29uZmlnCQlrZXJuZWwJCgoKY29udHJvbGxlcglpc2EwCiNj b250cm9sbGVyCXBucDAJCQkjIFBuUCBzdXBwb3J0IGZvciBJU0EKY29udHJvbGxlcglwY2kw Cgpjb250cm9sbGVyCWZkYzAJYXQgaXNhPyBwb3J0ICJJT19GRDEiICBpcnEgNiBkcnEgMgpk ZXZpY2UJCWZkMAlhdCBmZGMwIGRyaXZlIDAKCmNvbnRyb2xsZXIgICAgIGF0YTAKZGV2aWNl ICAgICAgICAgYXRhZGlzazAgICAgICAgICMgQVRBIGRpc2sgZHJpdmVzCmRldmljZSAgICAg ICAgIGF0YXBpY2QwICAgICAgICAjIEFUQVBJIENEUk9NIGRyaXZlcwpkZXZpY2UgICAgICAg ICBhdGFwaWZkMCAgICAgICAgIyBBVEFQSSBmbG9wcHkgZHJpdmVzCgoKCgpkZXZpY2UJCXZn YTAJYXQgaXNhPyBwb3J0ID8gY29uZmxpY3RzCgojIHNwbGFzaCBzY3JlZW4vc2NyZWVuIHNh dmVyCnBzZXVkby1kZXZpY2UJc3BsYXNoCgojIHN5c2NvbnMgaXMgdGhlIGRlZmF1bHQgY29u c29sZSBkcml2ZXIsIHJlc2VtYmxpbmcgYW4gU0NPIGNvbnNvbGUKZGV2aWNlCQlzYzAJYXQg aXNhPyAgZmxhZ3MgMHgxMDAKCmRldmljZQkJbnB4MAlhdCBuZXh1cz8gcG9ydCBJT19OUFgg aXJxIDEzCiNkZXZpY2UgICAgICAgICAgYXBtMCAgICBhdCBuZXh1cz8gZmxhZ3MgMHgzMQoK ZGV2aWNlCQlzaW8wCWF0IGlzYT8gcG9ydCAiSU9fQ09NMSIgZmxhZ3MgMHgxMCAgaXJxIDQK I2RldmljZQkJc2lvMQlhdCBpc2E/IHBvcnQgIklPX0NPTTIiICBpcnEgMwoKIyBQYXJhbGxl bCBwb3J0CmRldmljZQkJcHBjMAlhdCBpc2E/IHBvcnQ/ICBpcnEgNwpjb250cm9sbGVyCXBw YnVzMApkZXZpY2UJCWxwdDAJYXQgcHBidXM/CgoKcHNldWRvLWRldmljZQlsb29wCnBzZXVk by1kZXZpY2UJZXRoZXIKcHNldWRvLWRldmljZQlwdHkJMTYKcHNldWRvLWRldmljZSAgIHNw ZWFrZXIKcHNldWRvLWRldmljZQlicGYgCTIKCiMgS1RSQUNFIGVuYWJsZXMgdGhlIHN5c3Rl bS1jYWxsIHRyYWNpbmcgZmFjaWxpdHkga3RyYWNlKDIpLgojIFRoaXMgYWRkcyA0IEtCIGJs b2F0IHRvIHlvdXIga2VybmVsLCBhbmQgc2xpZ2h0bHkgaW5jcmVhc2VzCiMgdGhlIGNvc3Rz IG9mIGVhY2ggc3lzY2FsbC4Kb3B0aW9ucwkJS1RSQUNFCQkja2VybmVsIHRyYWNpbmcKCiMg VGhpcyBwcm92aWRlcyBzdXBwb3J0IGZvciBTeXN0ZW0gViBzaGFyZWQgbWVtb3J5IGFuZCBt ZXNzYWdlIHF1ZXVlcy4KIwpvcHRpb25zICAgICAgICAgU1lTVlNITQpvcHRpb25zICAgICAg ICAgU1lTVk1TRwoKIyBVU0Igc3VwcG9ydAojY29udHJvbGxlciAgICB1aGNpMAojY29udHJv bGxlciAgICBvaGNpMAojY29udHJvbGxlciAgICB1c2IwCiMKIyBmb3IgdGhlIG1vbWVudCB3 ZSBoYXZlIHRvIHNwZWNpZnkgdGhlIHByaW9yaXRpZXMgb2YgdGhlIGRldmljZQojIGRyaXZl cnMgZXhwbGljaXRseSBieSB0aGUgb3JkZXJpbmcgaW4gdGhlIGxpc3QgYmVsb3cuIFRoaXMg d2lsbAojIGJlIGNoYW5nZWQgaW4gdGhlIGZ1dHVyZS4KIwojZGV2aWNlICAgICAgICB1bXMw CiNkZXZpY2UgICAgICAgIHVrYmQwCiNkZXZpY2UgICAgICAgIHVscHQwCiNkZXZpY2UgICAg ICAgIHVoaWQwCiNkZXZpY2UgICAgICAgIHVnZW4wCgoKZGV2aWNlIHBjbTAgCiNhdCBpc2E/ IHBvcnQgPyAgaXJxID8gZHJxID8gZmxhZ3MgMHgwCmRldmljZSBwY2EwIGF0IGlzYT8gcG9y dCAiSU9fVElNRVIxIiAKCgpvcHRpb25zICAgICAgICAgICAgICAgIFNPRlRVUERBVEVTCgoK b3B0aW9ucyAgICAgICAgIElERV9ERUxBWT04MDAwCm9wdGlvbnMJCUtCRF9JTlNUQUxMX0NE RVYKCgojIGF0a2JkYzAgY29udHJvbHMgYm90aCB0aGUga2V5Ym9hcmQgYW5kIHRoZSBQUy8y IG1vdXNlCmNvbnRyb2xsZXIJYXRrYmRjMAlhdCBpc2E/IHBvcnQgSU9fS0JECmRldmljZQkJ YXRrYmQwCWF0IGF0a2JkYz8gZGlzYWJsZSBpcnEgMQo= --uePjVVlT3W Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Here's the config file for the working kernel (ELEVEN): --uePjVVlT3W Content-Type: application/octet-stream Content-Description: working kernel Content-Disposition: attachment; filename="ELEVEN" Content-Transfer-Encoding: base64 IwojIEdFTkVSSUMgLS0gR2VuZXJpYyBtYWNoaW5lIHdpdGggV0QvQUh4L05DUi9CVHggZmFt aWx5IGRpc2tzCiMKIyBGb3IgbW9yZSBpbmZvcm1hdGlvbiByZWFkIHRoZSBoYW5kYm9vayBw YXJ0IFN5c3RlbSBBZG1pbmlzdHJhdGlvbiAtPiAKIyBDb25maWd1cmluZyB0aGUgRnJlZUJT RCBLZXJuZWwgLT4gVGhlIENvbmZpZ3VyYXRpb24gRmlsZS4gCiMgVGhlIGhhbmRib29rIGlz IGF2YWlsYWJsZSBpbiAvdXNyL3NoYXJlL2RvYy9oYW5kYm9vayBvciBvbmxpbmUgYXMKIyBs YXRlc3QgdmVyc2lvbiBmcm9tIHRoZSBGcmVlQlNEIFdvcmxkIFdpZGUgV2ViIHNlcnZlciAK IyA8VVJMOmh0dHA6Ly93d3cuRnJlZUJTRC5PUkcvPgojCiMgQW4gZXhoYXVzdGl2ZSBsaXN0 IG9mIG9wdGlvbnMgYW5kIG1vcmUgZGV0YWlsZWQgZXhwbGFuYXRpb25zIG9mIHRoZSAKIyBk ZXZpY2UgbGluZXMgaXMgcHJlc2VudCBpbiB0aGUgLi9MSU5UIGNvbmZpZ3VyYXRpb24gZmls ZS4gSWYgeW91IGFyZSAKIyBpbiBkb3VidCBhcyB0byB0aGUgcHVycG9zZSBvciBuZWNlc3Np dHkgb2YgYSBsaW5lLCBjaGVjayBmaXJzdCBpbiBMSU5ULgojCiMJJElkOiBHRU5FUklDLHYg MS4xNTYgMTk5OS8wMy8yOSAxNzo1NjoyNyBrZW4gRXhwICQKCm1hY2hpbmUJCSJpMzg2Igpj cHUJCSJJNjg2X0NQVSIKaWRlbnQJCUVMRVZFTgptYXh1c2Vycwk2NAoKb3B0aW9ucwkJSU5F VAkJCSNJbnRlck5FVHdvcmtpbmcKb3B0aW9ucwkJRkZTCQkJI0JlcmtlbGV5IEZhc3QgRmls ZXN5c3RlbQpvcHRpb25zCQlGRlNfUk9PVAkJI0ZGUyB1c2FibGUgYXMgcm9vdCBkZXZpY2Ug W2tlZXAgdGhpcyFdCm9wdGlvbnMJCSJDT01QQVRfNDMiCQkjQ29tcGF0aWJsZSB3aXRoIEJT RCA0LjMgW0tFRVAgVEhJUyFdCm9wdGlvbnMJCVVDT05TT0xFCQkjQWxsb3cgdXNlcnMgdG8g Z3JhYiB0aGUgY29uc29sZQoKY29uZmlnCQlrZXJuZWwJCgoKY29udHJvbGxlcglpc2EwCmNv bnRyb2xsZXIJcG5wMAkJCSMgUG5QIHN1cHBvcnQgZm9yIElTQQpjb250cm9sbGVyCXBjaTAK CmNvbnRyb2xsZXIJZmRjMAlhdCBpc2E/IHBvcnQgIklPX0ZEMSIgIGlycSA2IGRycSAyCmRl dmljZQkJZmQwCWF0IGZkYzAgZHJpdmUgMAoKY29udHJvbGxlciAgICAgYXRhMApkZXZpY2Ug ICAgICAgICBhdGFkaXNrMCAgICAgICAgIyBBVEEgZGlzayBkcml2ZXMKZGV2aWNlICAgICAg ICAgYXRhcGljZDAgICAgICAgICMgQVRBUEkgQ0RST00gZHJpdmVzCmRldmljZSAgICAgICAg IGF0YXBpZmQwICAgICAgICAjIEFUQVBJIGZsb3BweSBkcml2ZXMKCgoKCmRldmljZQkJdmdh MAlhdCBpc2E/IHBvcnQgPyBjb25mbGljdHMKCiMgc3BsYXNoIHNjcmVlbi9zY3JlZW4gc2F2 ZXIKcHNldWRvLWRldmljZQlzcGxhc2gKCiMgc3lzY29ucyBpcyB0aGUgZGVmYXVsdCBjb25z b2xlIGRyaXZlciwgcmVzZW1ibGluZyBhbiBTQ08gY29uc29sZQpkZXZpY2UJCXNjMAlhdCBp c2E/ICAKCmRldmljZQkJbnB4MAlhdCBuZXh1cz8gcG9ydCBJT19OUFggaXJxIDEzCiNkZXZp Y2UgICAgICAgICAgYXBtMCAgICBhdCBuZXh1cz8gZmxhZ3MgMHgzMQoKZGV2aWNlCQlzaW8w CWF0IGlzYT8gcG9ydCAiSU9fQ09NMSIgZmxhZ3MgMHgxMCAgaXJxIDQKI2RldmljZQkJc2lv MQlhdCBpc2E/IHBvcnQgIklPX0NPTTIiICBpcnEgMwoKIyBQYXJhbGxlbCBwb3J0CmRldmlj ZQkJcHBjMAlhdCBpc2E/IHBvcnQ/ICBpcnEgNwpjb250cm9sbGVyCXBwYnVzMApkZXZpY2UJ CWxwdDAJYXQgcHBidXM/CgoKcHNldWRvLWRldmljZQlsb29wCnBzZXVkby1kZXZpY2UJZXRo ZXIKcHNldWRvLWRldmljZQlwdHkJMTYKcHNldWRvLWRldmljZSAgIHNwZWFrZXIKcHNldWRv LWRldmljZQlicGYgCTIKCiMgS1RSQUNFIGVuYWJsZXMgdGhlIHN5c3RlbS1jYWxsIHRyYWNp bmcgZmFjaWxpdHkga3RyYWNlKDIpLgojIFRoaXMgYWRkcyA0IEtCIGJsb2F0IHRvIHlvdXIg a2VybmVsLCBhbmQgc2xpZ2h0bHkgaW5jcmVhc2VzCiMgdGhlIGNvc3RzIG9mIGVhY2ggc3lz Y2FsbC4Kb3B0aW9ucwkJS1RSQUNFCQkja2VybmVsIHRyYWNpbmcKCiMgVGhpcyBwcm92aWRl cyBzdXBwb3J0IGZvciBTeXN0ZW0gViBzaGFyZWQgbWVtb3J5IGFuZCBtZXNzYWdlIHF1ZXVl cy4KIwpvcHRpb25zICAgICAgICAgU1lTVlNITQpvcHRpb25zICAgICAgICAgU1lTVk1TRwoK IyBVU0Igc3VwcG9ydApjb250cm9sbGVyICAgIHVoY2kwCmNvbnRyb2xsZXIgICAgb2hjaTAK Y29udHJvbGxlciAgICB1c2IwCiMKIyBmb3IgdGhlIG1vbWVudCB3ZSBoYXZlIHRvIHNwZWNp ZnkgdGhlIHByaW9yaXRpZXMgb2YgdGhlIGRldmljZQojIGRyaXZlcnMgZXhwbGljaXRseSBi eSB0aGUgb3JkZXJpbmcgaW4gdGhlIGxpc3QgYmVsb3cuIFRoaXMgd2lsbAojIGJlIGNoYW5n ZWQgaW4gdGhlIGZ1dHVyZS4KIwojZGV2aWNlICAgICAgICB1bXMwCmRldmljZSAgICAgICAg dWtiZDAKI2RldmljZSAgICAgICAgdWxwdDAKI2RldmljZSAgICAgICAgdWhpZDAKI2Rldmlj ZSAgICAgICAgdWdlbjAKCgpkZXZpY2UgcGNtMCAKI2F0IGlzYT8gcG9ydCA/ICBpcnEgPyBk cnEgPyBmbGFncyAweDAKZGV2aWNlIHBjYTAgYXQgaXNhPyBwb3J0ICJJT19USU1FUjEiIAoK Cm9wdGlvbnMgICAgICAgICAgICAgICAgU09GVFVQREFURVMKCgpvcHRpb25zICAgICAgICAg SURFX0RFTEFZPTgwMDAKb3B0aW9ucwkJS0JEX0lOU1RBTExfQ0RFVgoKCg== --uePjVVlT3W Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hope all this information helps. Viren viren@rstcorp.com --uePjVVlT3W-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 19:24:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 4332C14FC1 for ; Tue, 7 Dec 1999 19:24:22 -0800 (PST) (envelope-from eculp@MexComUSA.Net) Received: from MexComUSA.Net (local-27.local.net [192.168.1.27]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id TAA34449; Tue, 7 Dec 1999 19:24:14 -0800 (PST) (envelope-from eculp@MexComUSA.Net) Message-ID: <384DCFB7.61583B15@MexComUSA.Net> Date: Tue, 07 Dec 1999 19:25:43 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Newton Cc: current@FreeBSD.ORG Subject: Re: "make world" broken on a 3 month old system References: <19991208105600.A71026@internode.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Newton wrote: > I'm trying to "make world" on a system last built on Sep 29th; it's > failing like so: > > ===> f77doc > /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc > cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj > rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH /usr/obj/usr/src/gnu/lib/libgcc/GRTAGS /usr/obj/usr/src/gnu/lib/libgcc/GSYMS /usr/obj/usr/src/gnu/lib/libgcc/GTAGS > echo '#include ' > config.h > echo '#include ' >> config.h > echo '#include "gansidecl.h"' > tconfig.h > echo '#include "i386/xm-i386.h"' >> tconfig.h > echo '#include "i386/i386.h"' > tm.h > echo '#include "i386/att.h"' >> tm.h > echo '#include "svr4.h"' >> tm.h > echo '#include ' >> tm.h > echo '#include "i386/freebsd.h"' >> tm.h > echo '#include "i386/perform.h"' >> tm.h > cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c > *** Signal 12 > > Stop in /usr/src/gnu/lib/libgcc. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > Should I be expecting this? :-) > > - mark I think that your problem is covered in this cut and paste from /usr/src/UPDATING that has very interesting content:-) Be sure and read everything previous to this also. 19990929: The sigset_t datatype has been changed from an integral type to a compound type and can hold 128 signals. Syscalls directly or indirectly using the new sigset_t have been added as to maintain compatibility with existing binaries. A new kernel must be made and installed and booted with before a make world can be done. Hope that helps. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 20:55:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 215E114EB0; Tue, 7 Dec 1999 20:55:08 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from skylink.it (va-149.skylink.it [194.185.55.149]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id FAA24940; Wed, 8 Dec 1999 05:55:12 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id XAA01233; Tue, 7 Dec 1999 23:05:41 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Tue, 7 Dec 1999 23:05:40 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Bruce Evans Cc: Mike Smith , Alex Zepeda , FreeBSD CURRENT Mailing List Subject: Re: mount(2) broken? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That sounds like the conclusion I came to as well. I had a different patch, but looking at yours, mine looks wrong. Nick > "mount -f /" on a dirty root file system causes the clean flag to stay off > forever. (I forgot to change the unclean flag for mount -u.) > > diff -c2 ffs_vfsops.c~ ffs_vfsops.c > *** ffs_vfsops.c~ Thu Nov 25 23:27:44 1999 > --- ffs_vfsops.c Sun Dec 5 05:12:51 1999 > *************** > *** 218,222 **** > --- 220,226 ---- > } > > + fs->fs_flags &= ~FS_UNCLEAN; > if (fs->fs_clean == 0) { > + fs->fs_flags |= FS_UNCLEAN; > if (mp->mnt_flag & MNT_FORCE) { > printf( > > Bruce > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 21: 7:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (m5.columbus.rr.com [204.210.252.249]) by hub.freebsd.org (Postfix) with ESMTP id 2B77E14EB0 for ; Tue, 7 Dec 1999 21:07:48 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([24.95.60.151]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Wed, 8 Dec 1999 00:07:41 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id AAA01654; Wed, 8 Dec 1999 00:07:46 -0500 (EST) (envelope-from caa) Date: Wed, 8 Dec 1999 00:07:46 -0500 From: "Charles Anderson" To: Seigo Tanimura Cc: schuerge@wjpserver.CS.Uni-SB.DE, fn@radio-do.de, freebsd-current@FreeBSD.ORG Subject: Re: AWE64 problems Message-ID: <19991208000746.A1622@midgard.dhs.org> References: <19991207222414.A555@radio-do.de> <199912072200.XAA14065@wjpserver.cs.uni-sb.de> <14413.49878.644230.10865D@rina.r.dl.itc.u-tokyo.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <14413.49878.644230.10865D@rina.r.dl.itc.u-tokyo.ac.jp>; from Seigo Tanimura on Wed, Dec 08, 1999 at 11:30:46AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I looked for some meaning to the -100, is this documented somewhere? Who calls it? -Charlie On Wed, Dec 08, 1999 at 11:30:46AM +0900, Seigo Tanimura wrote: > On Tue, 7 Dec 1999 23:00:02 +0100 (MET), > Thomas Schuerger said: > > >> --- sbc.c.orig Mon Dec 6 19:26:31 1999 > >> +++ sbc.c Tue Dec 7 22:15:25 1999 > >> @@ -110,7 +110,7 @@ > >> if (error) > >> return error; > >> else > >> - return -100; > >> + return -1; > >> } > >> > >> static int > > Thomas> Works fine for me. Thanks!!! > > > Yes, this patch should work. The probe likelyhood(do we call it so?) for > unknown device is -100, so it does not make sense for sbc to return > -100. > > -1 might be too high, -50 sounds good to me. > > -- > Seigo Tanimura > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 21:12:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles521.castles.com [208.214.165.85]) by hub.freebsd.org (Postfix) with ESMTP id 328F414EB0 for ; Tue, 7 Dec 1999 21:12:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA07525; Tue, 7 Dec 1999 21:13:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912080513.VAA07525@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Charles Anderson" Cc: Seigo Tanimura , schuerge@wjpserver.CS.Uni-SB.DE, fn@radio-do.de, freebsd-current@FreeBSD.ORG Subject: Re: AWE64 problems In-reply-to: Your message of "Wed, 08 Dec 1999 00:07:46 EST." <19991208000746.A1622@midgard.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Dec 1999 21:13:41 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I looked for some meaning to the -100, is this documented somewhere? It's not, yet. We should move to using some defines for this. A while back I proposed something like: #define DEVICE_MATCH_EXACT -100 #define DEVICE_MATCH_CLASS -200 #define DEVICE_MATCH_GENERIC -300 The 'exact' response is still < 0 so that you can tune between two 'exact' drivers on a per-instance basis. The meanings should be pretty obvious... > Who calls it? > > -Charlie > > On Wed, Dec 08, 1999 at 11:30:46AM +0900, Seigo Tanimura wrote: > > On Tue, 7 Dec 1999 23:00:02 +0100 (MET), > > Thomas Schuerger said: > > > > >> --- sbc.c.orig Mon Dec 6 19:26:31 1999 > > >> +++ sbc.c Tue Dec 7 22:15:25 1999 > > >> @@ -110,7 +110,7 @@ > > >> if (error) > > >> return error; > > >> else > > >> - return -100; > > >> + return -1; > > >> } > > >> > > >> static int > > > > Thomas> Works fine for me. Thanks!!! > > > > > > Yes, this patch should work. The probe likelyhood(do we call it so?) for > > unknown device is -100, so it does not make sense for sbc to return > > -100. > > > > -1 might be too high, -50 sounds good to me. > > > > -- > > Seigo Tanimura > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > Charles Anderson caa@columbus.rr.com > > No quote, no nothin' > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 21:27: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id B762214BD4 for ; Tue, 7 Dec 1999 21:26:57 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id LAA13126; Wed, 8 Dec 1999 11:26:54 +0600 (NOVT) (envelope-from nnd) Date: Wed, 8 Dec 1999 11:26:54 +0600 (NOVT) Message-Id: <199912080526.LAA13126@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: current@freebsd.org Subject: Re: gasp broke world. In-Reply-To: User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Bill Fumerola wrote: > Doug, > > 'gasp' broke world. > > targ-env.h: No such file or directory The next patch at least unbroke 'make buildworld'. N.Dudorov ========================================================================= --- src/gnu/usr.bin/binutils/gasp/Makefile.ORIG Wed Dec 8 09:52:19 1999 +++ src/gnu/usr.bin/binutils/gasp/Makefile Wed Dec 8 09:52:19 1999 @@ -11,7 +11,7 @@ CFLAGS+= -I${SRCDIR} CFLAGS+= -I${SRCDIR}/gas CFLAGS+= -I${SRCDIR}/gas/config -CFLAGS+= -I${.CURDIR}/../as/as_${MACHINE_ARCH} +CFLAGS+= -I${.CURDIR}/../as/${MACHINE_ARCH}-freebsd CFLAGS+= -DBFD_ASSEMBLER LDADD+= -L${RELTOP}/libiberty -liberty DPADD+= ${RELTOP}/libiberty/libiberty.a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 21:46:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 466C214BD4 for ; Tue, 7 Dec 1999 21:46:27 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:6svwZfkDWGcF7ym734RD7la9mDm8Q7Dz@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id OAA06003; Wed, 8 Dec 1999 14:46:14 +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 OAA25688; Wed, 8 Dec 1999 14:51:06 +0900 (JST) Message-Id: <199912080551.OAA25688@zodiac.mech.utsunomiya-u.ac.jp> To: "Viren R. Shah" Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Using USB modules with an USB keyboard... In-reply-to: Your message of "Tue, 07 Dec 1999 21:24:51 EST." <199912080224.VAA00222@frabjous.viren.org> References: <199912080224.VAA00222@frabjous.viren.org> Date: Wed, 08 Dec 1999 14:51:05 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you for your detailed report. >I added your recommendations above to the kernel config file >(TWELVE). It didn't work. As can be seen from the dmesg below, when >the USB options are present in the kernel, ukbd0 is found. When USB >KLDs are used, uhid0 seems to grab the keyboard. > >[This is the dmesg from a kernel (ELEVEN) that works. The config file for this >includes all the USB options except for ums, which is loaded at bootup] > >As seen below, I have an USB mouse (ums0), and an USB keyboard (which >seems to register as an USB keyboard and a mouse -- ums1). The >keyboard does have a PS/2 mouse connector on it. This is the correct hehavior. If a USB device has more than one interface, it may require multiple drivers; one driver for each interface. >[This is the kernel (TWELVE) that has no USB options. All the USB modules are >loaded at bootup by the loader.conf scripts.] >Dec 7 19:57:33 frabjous /kernel: real memory = 134217728 (131072K bytes) >Dec 7 19:57:33 frabjous /kernel: avail memory = 127352832 (124368K bytes) >Dec 7 19:57:33 frabjous /kernel: Preloaded elf kernel "kernel" at 0xc02ae000. >Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "vesa.ko" at 0xc02ae09c >. >Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "cd9660.ko" at 0xc02ae1 >38. >Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "procfs.ko" at 0xc02ae1 >d8. >Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "green_saver.ko" at 0xc >02ae278. >Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "usb.ko" at 0xc02ae31c. >Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ugen.ko" at 0xc02ae3b8 >. >Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "uhid.ko" at 0xc02ae454 >. >Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ukbd.ko" at 0xc02ae4f0 >. >Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ulpt.ko" at 0xc02ae58c >. >Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "ums.ko" at 0xc02ae628. >Dec 7 19:57:33 frabjous /kernel: Preloaded elf module "umass.ko" at 0xc02ae6c >4. >Dec 7 19:57:33 frabjous /kernel: link_elf: symbol cam_simq_alloc undefined >... >Dec 7 19:57:33 frabjous /kernel: uhci0: ler> irq 10 at device 7.2 on pci0 >Dec 7 19:57:33 frabjous /kernel: usb0: er> on uhci0 >Dec 7 19:57:33 frabjous /kernel: usb0: USB revision 1.0 >Dec 7 19:57:33 frabjous /kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1 >.00/1.00, addr 1 >Dec 7 19:57:33 frabjous /kernel: uhub0: 2 ports with 2 removable, self powere >d >Dec 7 19:57:33 frabjous /kernel: ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1. >00/1.10, addr 2, iclass 3/1 >Dec 7 19:57:33 frabjous /kernel: ums0: 4 buttons and Z dir. >Dec 7 19:57:33 frabjous /kernel: uhid0: QTRONIX USB Keyboard and Mouse, rev 1 >.00/1.10, addr 3, iclass 3/1 >Dec 7 19:57:33 frabjous /kernel: ums1: QTRONIX USB Keyboard and Mouse, rev 1. >00/1.10, addr 3, iclass 3/1 >Dec 7 19:57:33 frabjous /kernel: ums1: 3 buttons [...] Ok, I got the picture. The fix is on the way. I will contact you later. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 7 22:51: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay5.smtp.psi.net (relay5.smtp.psi.net [38.9.28.2]) by hub.freebsd.org (Postfix) with ESMTP id 0CA41154E8 for ; Tue, 7 Dec 1999 22:51:03 -0800 (PST) (envelope-from keichii@mail.utexas.edu) Received: from [38.192.209.90] (helo=mail.utexas.edu) by relay5.smtp.psi.net with esmtp (Exim 1.90 #1) id 11vawI-0004Ek-00; Wed, 8 Dec 1999 01:51:02 -0500 Message-ID: <384DFFD7.8C022E15@mail.utexas.edu> Date: Wed, 08 Dec 1999 06:51:03 +0000 From: Michael Chin-Yuan Wu Organization: Keichii, Univ of Texas at Austin-ECE X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: zh-TW, en MIME-Version: 1.0 To: Keith Jang Cc: freebsd-current@FreeBSD.ORG Subject: Re: Cannot mount cd9660 References: <384D1D88.B2F7F062@mail.utexas.edu> <384DAD92.3856003D@gcn.net.tw> Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Keith Jang wrote: > > Michael Chin-Yuan Wu wrote: > > > P.S. I did a patch for cd9660 and patch for reading Chinese filenames > > > [patch is in attachment] > [...] > > > chinese_joliet.patch.for_3.2-19990615.gz Type: application/x-gzip > > > chinese_vfat-3.0.patch.gz Type: application/x-gzip > > Come on, these patches have been available at > ftp://freebsd.csie.nctu.edu.tw/pub/taiwan/CSIE/kernel_patch/ > since 2.2.7, and the author is mills.bbs@bbs.iim.nctu.edu.tw. > Now you just rip it off and claim that's your work? I didn't take credit for this. :) Sorry if I didnt make myself clear. If you will look at my email again, > P.S. I did a patch for cd9660 and patch for reading Chinese filenames > [patch is in attachment] > =========uname -a============ > FreeBSD keichii.internal.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0 > 8:09 CST 1999 keichii@keichii.internal.org:/usr/current/src > .ATA i386 > ===============dmesg========= > as attachment > =============kernel========= > as attachment > ============patches for chinese filesystems====== > as attachment > ============================== The ======= lined parts are all information meant to help people debug/understand my problem. The "p.s." part was also meant to help solve the problem. Sorry for not making myself clear. What I meant was, "I applied the patches to the sources, which may have caused the cdrom to not mount" Apologies for bad English usage and causing the confusion. [Doing/did a patch can mean two things in English A. to write the patch B. to patch the source with the I know that A is usually the default definition, but it was 3am in the morning when I wrote that email. I apologize. > -- Many humble apologies, Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 1: 2:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 362FE14D8A for ; Wed, 8 Dec 1999 01:02:10 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id KAA14179 for freebsd-current@FreeBSD.ORG; Wed, 8 Dec 1999 10:02:10 +0100 (CET) (envelope-from olli) Date: Wed, 8 Dec 1999 10:02:10 +0100 (CET) From: Oliver Fromme Message-Id: <199912080902.KAA14179@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Memory leak in syscons? Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not 100% sure, but I think I have found a memory leak in syscons. The following patch should fix it. Would someone please have a look at this? The diff is against this file: src/sys/dev/syscons/schistory.c,v 1.5 1999/09/19 08:58:53 Regards Oliver --- src/sys/dev/syscons.orig/schistory.c Sun Sep 19 10:58:53 1999 +++ src/sys/dev/syscons/schistory.c Wed Dec 8 09:53:33 1999 @@ -135,6 +135,7 @@ if (prev_history != NULL) { extra_history_size += delta; sc_vtb_destroy(prev_history); + free(prev_history, M_DEVBUF); } scp->history = history; -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 1: 9:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id E368014D8A for ; Wed, 8 Dec 1999 01:09:23 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id EAA24223 for ; Wed, 8 Dec 1999 04:09:23 -0500 (EST) Date: Wed, 8 Dec 1999 04:09:22 -0500 (EST) From: "Matthew N. Dodd" To: current@freebsd.org Subject: OHCI weirdness? Message-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 get this same panic with both devices I've tried; a Kodak DC265 and a Sandisk CompactFlash reader. Its not obvious why this is happening (at least from where I'm sitting.) Any ideas? Should I report back with a kernel compiled with OHCI_DEBUG? Thanks. ... ohci0: irq 9 at device 11.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered panic: ohci_hash_find_td: addr 0x03e7c770 not found Debugger("panic") Stopped at Debugger+0x37: movl $0,in_Debugger db> t Debugger(c0289aa3) at Debugger+0x37 panic(c029c0c0,3e7c770,c0373cbc,c0225142,c07a5800) at panic+0x74 ohci_hash_find_td(c07a5800,3e7c770,6,c07a5800,2) at ohci_hash_find_td+0x33 ohci_process_done(c07a5800,3e7c7d0,6b9457,c07a5800,c07a6e80) at ohci_process_done+0x1e ohci_intr1(c07a5800) at ohci_intr1+0x10c ohci_waitintr(c07a5800,c07a6e80,c07a6e80,c07a6e80,c0373d20) at ohci_waitintr+0x69 ohci_device_ctrl_start(c07a6e80,0,c0373d44,c02277a1,c07a6e80) at ohci_device_ctrl_start+0x2c ohci_device_ctrl_transfer(c07a6e80,0,c07a6e80,c0373da4,c07a6e80) at ohci_device_ctrl_transfer+0x1e usbd_transfer(c07a6e80,c0373d74,c0228022,c07a6e80,c07a6e00) at usbd_transfer+0x95 usbd_sync_transfer(c07a6e80,c07a6e00,0,0,ffffffff) at usbd_sync_transfer+0x10 usbd_do_request_flags(c07a6e00,c0373da4,c07a6e34,0,0) at usbd_do_request_flags+0x5e usbd_do_request(c07a6e00,c0373da4,c07a6e34,1000680,80000) at usbd_do_request+0x15 usbd_get_desc(c07a6e00,1,0,8,c07a6e34) at usbd_get_desc+0x62 usbd_new_device(c07a3000,c07a5800,1,0,1,c07a6fb0) at usbd_new_device+0x10c uhub_explore(c07a3180,9,0,c07a3400,c0373e3c) at uhub_explore+0x1b3 usb_attach(c07a3200,c07a3200,c0373e54,c0168683,c07a3200) at usb_attach+0xf1 DEVICE_ATTACH(c07a3200,0,c07a5800,c07a3400,c0373e90) at DEVICE_ATTACH+0x33 device_probe_and_attach(c07a3200,9,0,c07a3600,0) at device_probe_and_attach+0x4f ohci_pci_attach(c07a3400,c07a3400,c0373eb8,c0168683,c07a3400) at ohci_pci_attach+0x2bb DEVICE_ATTACH(c07a3400,c07a3400,0,c07a3680,c0373ec8) at DEVICE_ATTACH+0x33 device_probe_and_attach(c07a3400) at device_probe_and_attach+0x4f bus_generic_attach(c07a3600,c07a3600,c0373ef0,c0168683,c07a3600) at bus_generic_attach+0x16 DEVICE_ATTACH(c07a3600,c07a3600,0,c07a3780,c0373f00) at DEVICE_ATTACH+0x33 device_probe_and_attach(c07a3600) at device_probe_and_attach+0x4f bus_generic_attach(c07a3680,c07a3680,c0373f28,c0168683,c07a3680) at bus_generic_attach+0x16 DEVICE_ATTACH(c07a3680,c07a3680,0,c0517700,c0373f38) at DEVICE_ATTACH+0x33 device_probe_and_attach(c07a3680) at device_probe_and_attach+0x4f bus_generic_attach(c07a3780,9,c0373f58,c0120bd3,c07a3780) at bus_generic_attach+0x16 nexus_attach(c07a3780,c07a3780,c0373f70,c0168683,c07a3780) at nexus_attach+0xd DEVICE_ATTACH(c07a3780,c07a3780,c02c37f0,378000,c0373f80) at DEVICE_ATTACH+0x33 device_probe_and_attach(c07a3780) at device_probe_and_attach+0x4f root_bus_configure(c0517700,c02a22ac,0) at root_bus_configure+0x16 configure(0,371c00,378000,0,c01205c6) at configure+0x37 mi_startup(c0373fb4,ffe,378000,c016d101,c037b000) at mi_startup+0x70 begin() at begin+0x4b -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 1:19:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4C9E81556E for ; Wed, 8 Dec 1999 01:19:48 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA56559 for current@freebsd.org; Wed, 8 Dec 1999 10:19:47 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912080919.KAA56559@freebsd.dk> Subject: HEADS UP!! ata driver now default in GENERIC & PCCARD. To: current@freebsd.org Date: Wed, 8 Dec 1999 10:19:47 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well subject says it all, the ata driver is now default in GENRIC & PCCARD. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 1:47:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id F031D14C5A; Wed, 8 Dec 1999 01:47:10 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA58918; Wed, 8 Dec 1999 09:55:15 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 8 Dec 1999 09:55:15 +0000 (GMT) From: Doug Rabson To: Bill Fumerola Cc: current@FreeBSD.org, dfr@FreeBSD.org Subject: Re: gasp broke world. 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, 7 Dec 1999, Bill Fumerola wrote: > Doug, > > 'gasp' broke world. > > targ-env.h: No such file or directory Bah. Ok, I'll fix it in a couple of hours when I get to work. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 2: 1:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id C682614CEB for ; Wed, 8 Dec 1999 02:01:04 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA59030; Wed, 8 Dec 1999 10:08:55 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 8 Dec 1999 10:08:55 +0000 (GMT) From: Doug Rabson To: nnd@mail.nsk.ru Cc: current@freebsd.org Subject: Re: gasp broke world. In-Reply-To: <199912080526.LAA13126@wint.itfs.nsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Dec 1999 nnd@mail.nsk.ru wrote: > In Bill Fumerola wrote: > > Doug, > > > > 'gasp' broke world. > > > > targ-env.h: No such file or directory > > The next patch at least unbroke 'make buildworld'. > > N.Dudorov The source tree I was working from wasn't sufficiently up-to-date. Sorry for the inconvenience. I'll commit a fix (if noone has already done it) in a couple of hours. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 3:55:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A6DDC14CF2 for ; Wed, 8 Dec 1999 03:55:44 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id MAA32908 for ; Wed, 8 Dec 1999 12:55:35 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: HEADSUP: wd driver will be retired! From: Poul-Henning Kamp Date: Wed, 08 Dec 1999 12:55:35 +0100 Message-ID: <32906.944654135@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In a few days time the wd driver will be retired from FreeBSDs i386 architecture. Users, please: Update your kernel config file (see GENERIC) Update your /etc/fstab (use /dev/ad* instead of /dev/wd* or /dev/rwd* Copy MAKEDEV from src/etc/MAKEDEV to /dev/MAKEDEV and make all the ad* disk devices you need for your system. Unfortunately current is broken right now, so I can't point you at a snapshot to reinstall from should you prefer that option, but I'm sure that current.freebsd.org will be able to deliver one RSN. PC98: I would like to discuss with the PC98 responsible commmitters what the prospects for wd vs ata in PC98 are, please get in touch with me. Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 4:38:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id 06B0214CF2 for ; Wed, 8 Dec 1999 04:38:50 -0800 (PST) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.43.2]) by matrix.eurocontrol.fr (Postfix) with ESMTP id 015483E36 for ; Wed, 8 Dec 1999 13:38:50 +0100 (CET) (envelope-from roberto@caerdonn.eurocontrol.fr) Received: by caerdonn.eurocontrol.fr (Postfix, from userid 1193) id 265D34E32; Wed, 8 Dec 1999 13:38:49 +0100 (CET) Date: Wed, 8 Dec 1999 13:38:49 +0100 From: Ollivier Robert To: current@freebsd.org Subject: [call for import] if_ef module Message-ID: <19991208133849.Q13603@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The current client IPX support thanks to Boris is alive and runs very well on CURRENT. But to make it really interesting, the if_ef driver, which enable the use of multiple ethernet frame types on the same wire, must be imported into -CURRENT as well. It would be nice to have it into 4.0 as without it, the IPX client support is quite limited. I've been running it for weeks now without any problem. lnc0: flags=8843 mtu 1500 inet 147.196.43.2 netmask 0xffffff00 broadcast 147.196.43.255 ether 00:10:83:35:20:9d lnc0f1: flags=8843 mtu 1500 ipx 43000H.108335209d ether 00:10:83:35:20:9d lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 Id Refs Address Size Name 1 12 0xc0100000 19dc28 kernel 3 1 0xc02b2000 6f64 procfs.ko 4 1 0xc02b9000 5278 vesa.ko 5 1 0xc02bf000 2604 if_ef.ko 6 1 0xc0de6000 4000 logo_saver.ko 7 1 0xc0e4b000 13000 usb.ko 10 1 0xc1014000 a000 nwfs.ko 11 1 0xc101f000 a000 ncp.ko 12 1 0xc144f000 5000 linprocfs.ko 13 1 0xc146e000 10000 linux.ko 14 1 0xc1483000 8000 vmmon.ko 15 1 0xc148d000 3000 vmnet.ko I agree that the naming of the interfaces could be better but it works. Active NCP connections: refid server:user(connid), owner:group(mode), refs, 3 EEC0012:ROBERTO(438), root:wheel(775), 2, 2 EEC0011:ROBERTO(1931), root:wheel(775), 1, /EEC0011:ROBERTO/USERS 2048000 1933312 114688 94% /net/public /EEC0012:ROBERTO/HOME4 5120000 5003328 116672 98% /net/roberto /EEC0012:ROBERTO/SHARED4 17297280 5813056 11484224 34% /net/telecom -- Ollivier ROBERT -=- Eurocontrol EEC/TEC -=- Ollivier.Robert@eurocontrol.fr The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 5:27:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 4A68614EF5; Wed, 8 Dec 1999 05:27:29 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id HAA55641; Wed, 8 Dec 1999 07:27:29 -0600 (CST) (envelope-from dick) Date: Wed, 8 Dec 1999 07:27:28 -0600 From: "Richard Seaman, Jr." To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991208072728.K44207@tar.com> References: <32906.944654135@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <32906.944654135@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 08, 1999 at 12:55:35PM +0100, Poul-Henning Kamp wrote: > > In a few days time the wd driver will be retired from FreeBSDs > i386 architecture. > Since the ata driver does not support DMA on my chipset, at least the last time I tried (SiS 5591), it would be nice to leave the wd driver in the tree for a while, even if its not the default. Possibly there are others in the same boat? -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 5:48: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 3F49A14EF5; Wed, 8 Dec 1999 05:47:58 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11vhRi-0005M2-00; Wed, 08 Dec 1999 15:47:54 +0200 From: Sheldon Hearn To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Wed, 08 Dec 1999 12:55:35 +0100." <32906.944654135@critter.freebsd.dk> Date: Wed, 08 Dec 1999 15:47:54 +0200 Message-ID: <20585.944660874@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 08 Dec 1999 12:55:35 +0100, Poul-Henning Kamp wrote: > In a few days time the wd driver will be retired from FreeBSDs > i386 architecture. I know there are issues that make it awkward to support both drivers, but it's probably a good idea to keep the wd driver available for those who need it, even if it requires more work to get it going than it does to get the ata driver going. That said, this is one way to get the folks who're having trouble with the ata driver to get off their butts and provide Soren with feedback, so maybe it's not a bad idea to nuke wd after all. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 5:54:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (m4.columbus.rr.com [204.210.252.19]) by hub.freebsd.org (Postfix) with ESMTP id C332214EF5; Wed, 8 Dec 1999 05:54:18 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([24.95.60.151]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Wed, 8 Dec 1999 08:54:11 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id IAA00549; Wed, 8 Dec 1999 08:54:15 -0500 (EST) (envelope-from caa) Date: Wed, 8 Dec 1999 08:54:15 -0500 From: "Charles Anderson" To: Mike Smith Cc: Charles Anderson , Seigo Tanimura , schuerge@wjpserver.CS.Uni-SB.DE, fn@radio-do.de, freebsd-current@FreeBSD.ORG Subject: Re: AWE64 problems Message-ID: <19991208085415.A534@midgard.dhs.org> References: <19991208000746.A1622@midgard.dhs.org> <199912080513.VAA07525@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199912080513.VAA07525@mass.cdrom.com>; from Mike Smith on Tue, Dec 07, 1999 at 09:13:41PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So then what is -1 and why does it work when -100 doesn't? (I tried it) -Charlie On Tue, Dec 07, 1999 at 09:13:41PM -0800, Mike Smith wrote: > > I looked for some meaning to the -100, is this documented somewhere? > > It's not, yet. We should move to using some defines for this. > A while back I proposed something like: > > #define DEVICE_MATCH_EXACT -100 > #define DEVICE_MATCH_CLASS -200 > #define DEVICE_MATCH_GENERIC -300 > > The 'exact' response is still < 0 so that you can tune between two > 'exact' drivers on a per-instance basis. The meanings should be pretty > obvious... > > > Who calls it? > > > > -Charlie > > > > On Wed, Dec 08, 1999 at 11:30:46AM +0900, Seigo Tanimura wrote: > > > On Tue, 7 Dec 1999 23:00:02 +0100 (MET), > > > Thomas Schuerger said: > > > > > > >> --- sbc.c.orig Mon Dec 6 19:26:31 1999 > > > >> +++ sbc.c Tue Dec 7 22:15:25 1999 > > > >> @@ -110,7 +110,7 @@ > > > >> if (error) > > > >> return error; > > > >> else > > > >> - return -100; > > > >> + return -1; > > > >> } > > > >> > > > >> static int > > > > > > Thomas> Works fine for me. Thanks!!! > > > > > > > > > Yes, this patch should work. The probe likelyhood(do we call it so?) for > > > unknown device is -100, so it does not make sense for sbc to return > > > -100. > > > > > > -1 might be too high, -50 sounds good to me. -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 6: 2:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 1D8581550A; Wed, 8 Dec 1999 06:02:31 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 60C472CE53; Wed, 8 Dec 1999 16:02:26 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 8A852FB; Wed, 8 Dec 1999 16:02:29 +0200 (EET) Date: Wed, 8 Dec 1999 16:02:29 +0200 From: Vallo Kallaste To: "Richard Seaman, Jr." Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991208160229.A38441@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <32906.944654135@critter.freebsd.dk> <19991208072728.K44207@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19991208072728.K44207@tar.com>; from Richard Seaman, Jr. on Wed, Dec 08, 1999 at 07:27:28AM -0600 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 08, 1999 at 07:27:28AM -0600, "Richard Seaman, Jr." wrote: > > In a few days time the wd driver will be retired from FreeBSDs > > i386 architecture. > > Since the ata driver does not support DMA on my chipset, at > least the last time I tried (SiS 5591), it would be nice > to leave the wd driver in the tree for a while, even if its > not the default. Possibly there are others in the same boat? It does WDMA2 for me. MB is pcchips one, type M598, uses SiS530. Strange. -- 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 Dec 8 6: 2:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id ADE0C1550E; Wed, 8 Dec 1999 06:02:48 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA23215; Wed, 8 Dec 1999 15:02:37 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912081402.PAA23215@freebsd.dk> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991208072728.K44207@tar.com> from "Richard Seaman, Jr." at "Dec 8, 1999 07:27:28 am" To: dick@tar.com (Richard Seaman, Jr.) Date: Wed, 8 Dec 1999 15:02:37 +0100 (CET) Cc: phk@FreeBSD.ORG (Poul-Henning Kamp), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Richard Seaman, Jr. wrote: > On Wed, Dec 08, 1999 at 12:55:35PM +0100, Poul-Henning Kamp wrote: > > > > In a few days time the wd driver will be retired from FreeBSDs > > i386 architecture. > > > > Since the ata driver does not support DMA on my chipset, at > least the last time I tried (SiS 5591), it would be nice > to leave the wd driver in the tree for a while, even if its > not the default. Possibly there are others in the same boat? OK, you asked for it, following is a patch to support the sis 5591 chipset. Remember this is done blindfolded, I have no HW to test on, but you guys do :) Let me know what happens... Index: ata-all.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.33 diff -u -r1.33 ata-all.c --- ata-all.c 1999/12/07 22:07:18 1.33 +++ ata-all.c 1999/12/08 13:57:27 @@ -195,12 +195,6 @@ return "Intel PIIX4 ATA controller"; case 0x522910b9: return "AcerLabs Aladdin ATA controller"; - case 0x4d33105a: - return "Promise Ultra/33 ATA controller"; - case 0x4d38105a: - return "Promise Ultra/66 ATA controller"; - case 0x00041103: - return "HighPoint HPT366 ATA controller"; case 0x05711106: /* 82c586 & 82c686 */ switch (pci_read_config(dev, 0x08, 1)) { case 1: @@ -209,6 +203,14 @@ return "VIA 82C686 ATA controller"; } return "VIA Apollo ATA controller"; + case 0x55131039: + return "SiS 5591 ATA controller"; + case 0x4d33105a: + return "Promise Ultra/33 ATA controller"; + case 0x4d38105a: + return "Promise Ultra/66 ATA controller"; + case 0x00041103: + return "HighPoint HPT366 ATA controller"; /* unsupported but known chipsets, generic DMA only */ case 0x05961106: Index: ata-dma.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-dma.c,v retrieving revision 1.21 diff -u -r1.21 ata-dma.c --- ata-dma.c 1999/12/07 22:07:18 1.21 +++ ata-dma.c 1999/12/08 13:57:34 @@ -297,6 +297,42 @@ /* we could set PIO mode timings, but we assume the BIOS did that */ break; + case 0x55131039: /* SiS 5591 */ + devno = (scp->unit << 1) + ((device == ATA_MASTER) ? 0 : 1); + if (udmamode >= 2) { + int16_t word4x = pci_read_config(scp->dev, 0x40 + (devno << 1), 2); + + pci_write_config(scp->dev, 0x40 + (devno << 1), 0xa301, 2); + error = ata_command(scp, device, ATA_C_SETFEATURES, 0, 0, 0, + ATA_UDMA2, ATA_C_F_SETXFER, ATA_WAIT_READY); + if (bootverbose) + printf("ata%d: %s: %s setting up UDMA2 mode on SiS chip\n", + scp->lun, (device == ATA_MASTER) ? "master" : "slave", + (error) ? "failed" : "success"); + if (!error) { + scp->mode[(device == ATA_MASTER) ? 0 : 1] = ATA_MODE_UDMA2; + return 0; + } + pci_write_config(scp->dev, 0x40 + (devno << 1), word4x, 2); + } + if (wdmamode >=2 && apiomode >= 4) { + int16_t word4x = pci_read_config(scp->dev, 0x40 + (devno << 1), 2); + + pci_write_config(scp->dev, 0x40 + (devno << 1), 0x0301, 2); + error = ata_command(scp, device, ATA_C_SETFEATURES, 0, 0, 0, + ATA_WDMA2, ATA_C_F_SETXFER, ATA_WAIT_READY); + if (bootverbose) + printf("ata%d: %s: %s setting up WDMA2 mode on SiS chip\n", + scp->lun, (device == ATA_MASTER) ? "master" : "slave", + (error) ? "failed" : "success"); + if (!error) { + scp->mode[(device == ATA_MASTER) ? 0 : 1] = ATA_MODE_WDMA2; + return 0; + } + pci_write_config(scp->dev, 0x40 + (devno << 1), word4x, 2); + } + break; + case 0x4d33105a: /* Promise Ultra33 / FastTrak33 controllers */ case 0x4d38105a: /* Promise Ultra66 / FastTrak66 controllers */ /* the Promise can only do DMA on ATA disks not on ATAPI devices */ -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 6:18:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 6493215590 for ; Wed, 8 Dec 1999 06:17:43 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcl225.cvzoom.net (lcl225.cvzoom.net [208.226.155.225]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id IAA09771 for ; Wed, 8 Dec 1999 08:58:19 -0500 (EST) Date: Wed, 8 Dec 1999 09:16:45 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: Cleaning house on /usr/src/* Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the course of development of -current, a bunch of directories are added and taken away from /usr/src. So, about every month or so, I like to clean out /usr/src/* and start from scratch. (Well, you know, sometimes you have so much of your own old code in there.) What is the best way to refresh /usr/src then? Do I do an ftp of the current src at current.freebsd.org, or is it OK to cvsup from scratch from cvsup[n].freebsd.org? Someone told me it puts too big of a load on the cvs servers by checking out the whole tree from scratch like this. I would say it actually puts a lighter load on the cvsup servers, because there's no files on your machine to compare the tree with. So, you're basically trading bandwidth for load. So, what's the best way to "clean house"? Of course, I only do this once a month or so if even that. I normally cvsup every 1 or 2 days, but you know, every once in a while you've got to clean out the /usr/src because of all the junk directories. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 6:23:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 3B27814C11; Wed, 8 Dec 1999 06:23:43 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id IAA59277; Wed, 8 Dec 1999 08:23:36 -0600 (CST) From: Joe Greco Message-Id: <199912081423.IAA59277@aurora.sol.net> Subject: Re: Route table leaks In-Reply-To: from John Polstra at "Nov 21, 1999 11:55:24 pm" To: jdp@polstra.com (John Polstra) Date: Wed, 8 Dec 1999 08:23:35 -0600 (CST) Cc: current@freebsd.org, stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Have any of you been seeing route table leaks in -current? I noticed > this week that cvsup-master.freebsd.org is suffering from them. I > actually had to reboot it because it couldn't allocate any more. From > the "vmstat -m" output: > > Memory statistics by type Type Kern > Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) > [...] > routetbl150907 21221K 21221K 21221K 462184 0 0 16,32,64,128,256 > [...] > I can think of some experiments to try in order to start to diagnose > it. But first, have any of you seen this problem? Hell, I've been seeing this for well over a year. The last time I mentioned it, everybody seemed to think I was nuts. :-) FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 When it gets like that, it starts losing the ability to add further ARP table entries and essentially starts going randomly deaf to local hosts (and to a lesser extent remote hosts). I've also seen it on a 3.3-RELEASE box, but it's not currently happening to any of them right now. Machines in question are SMP boxes, and get hit fairly heavily in various Usenet news server roles. Seems to happen quite a bit more often on boxes that talk to a wide variety of host types, and I can't recall having seen it on boxes that only talk to other FreeBSD boxes. But that could also be because the network environment is much more controlled internally. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 6:42:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 5828D14C32 for ; Wed, 8 Dec 1999 06:42:38 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11viIS-0005iJ-00; Wed, 08 Dec 1999 16:42:24 +0200 From: Sheldon Hearn To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: Cleaning house on /usr/src/* In-reply-to: Your message of "Wed, 08 Dec 1999 09:16:45 EST." Date: Wed, 08 Dec 1999 16:42:24 +0200 Message-ID: <21966.944664144@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 08 Dec 1999 09:16:45 EST, Donn Miller wrote: > In the course of development of -current, a bunch of directories are > added and taken away from /usr/src. So, about every month or so, I > like to clean out /usr/src/* and start from scratch. (Well, you know, > sometimes you have so much of your own old code in there.) The best way to do this is to use CVS as your means of updating the source tree and capture its output to some logfile. On inspection of the logfile, you'll see at a glance those files that can be deleted. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 6:46:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id C584914C92; Wed, 8 Dec 1999 06:46:05 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id JAA23041; Wed, 8 Dec 1999 09:46:04 -0500 (EST) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id JAA11510; Wed, 8 Dec 1999 09:46:04 -0500 (EST) Message-Id: <3.0.5.32.19991208094433.01610ac0@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 08 Dec 1999 09:44:33 -0500 To: Joe Greco , jdp@polstra.com (John Polstra) From: Mike Tancsa Subject: Re: Route table leaks Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199912081423.IAA59277@aurora.sol.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hell, I've been seeing this for well over a year. The last time I mentioned >it, everybody seemed to think I was nuts. :-) > >FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 Well, I havent seen problems of this nature (yet), but for reference, netstat -nr | wc 69585 419164 4875822 routetbl143718 19653K 21229K 21229K 6527152 0 0 16,32,64,128,256 FreeBSD 3.3-RC #0: Wed Sep 8 13:37:19 EDT 1999 uptime 9:44AM up 90 days, 20:35, 2 users, load averages: 0.00, 0.01, 0.00 This is a border router with 2 views of the net running defaultless. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 6:51:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 15DF514BDC; Wed, 8 Dec 1999 06:51:20 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id IAA61233; Wed, 8 Dec 1999 08:51:03 -0600 (CST) From: Joe Greco Message-Id: <199912081451.IAA61233@aurora.sol.net> Subject: Re: Route table leaks In-Reply-To: <3.0.5.32.19991208094433.01610ac0@staff.sentex.ca> from Mike Tancsa at "Dec 8, 1999 9:44:33 am" To: mike@sentex.net (Mike Tancsa) Date: Wed, 8 Dec 1999 08:51:03 -0600 (CST) Cc: jgreco@ns.sol.net, jdp@polstra.com, stable@FreeBSD.ORG, 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 > >Hell, I've been seeing this for well over a year. The last time I mentioned > >it, everybody seemed to think I was nuts. :-) > > > >FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > > > routetbl289178 40961K 40961K 40960K 435741 0 0 > 16,32,64,128,256 > > Well, I havent seen problems of this nature (yet), but for reference, > > > netstat -nr | wc > 69585 419164 4875822 > > routetbl143718 19653K 21229K 21229K 6527152 0 0 16,32,64,128,256 > > FreeBSD 3.3-RC #0: Wed Sep 8 13:37:19 EDT 1999 > uptime > 9:44AM up 90 days, 20:35, 2 users, load averages: 0.00, 0.01, 0.00 > > This is a border router with 2 views of the net running defaultless. Yeah, nice :-), but the machine I'm looking at is one with a default route and > netstat -rn | wc -l 16 Most of which are routes pointing at the 3 private-net interfaces on the machine. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 7: 0:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id C2FBB15540 for ; Wed, 8 Dec 1999 07:00:31 -0800 (PST) (envelope-from eculp@MexComUSA.Net) Received: from MexComUSA.Net (local-27.local.net [192.168.1.27]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id HAA67453 for ; Wed, 8 Dec 1999 07:00:27 -0800 (PST) (envelope-from eculp@MexComUSA.Net) Message-ID: <384E72EA.5DE8EE70@MexComUSA.Net> Date: Wed, 08 Dec 1999 07:02:02 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: World seems to be broken Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just looked at my logs and found that all my worlds from this morning are broken at: /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition cc -nostdinc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/tmp/usr/include -c ioctl.c ioctl.c:6: sys/dkbad.h: No such file or directory In file included from ioctl.c:79: /usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition *** Error code 1 Stop in /usr/src/usr.bin/kdump. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 7:12: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 489FA14D47; Wed, 8 Dec 1999 07:11:54 -0800 (PST) (envelope-from netchild@Leidinger.net) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id QAA1050404; Wed, 8 Dec 1999 16:11:38 +0100 (CET) Received: from Magelan.Leidinger.net (maxtnt-274.telip.uni-sb.de [134.96.71.145]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id QAA28164; Wed, 8 Dec 1999 16:11:45 +0100 (CET) Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id PAA05970; Wed, 8 Dec 1999 15:21:28 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <199912081421.PAA05970@Magelan.Leidinger.net> Date: Wed, 8 Dec 1999 15:21:27 +0100 (CET) From: Alexander Leidinger Subject: Re: HEADSUP: wd driver will be retired! To: sheldonh@uunet.co.za Cc: Poul-Henning Kamp , current@FreeBSD.ORG, sos@freebsd.dk In-Reply-To: <20585.944660874@axl.noc.iafrica.com> 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 On 8 Dec, Sheldon Hearn wrote: >> In a few days time the wd driver will be retired from FreeBSDs >> i386 architecture. > > I know there are issues that make it awkward to support both drivers, > but it's probably a good idea to keep the wd driver available for those > who need it, even if it requires more work to get it going than it does > to get the ata driver going. > > That said, this is one way to get the folks who're having trouble with > the ata driver to get off their butts and provide Soren with feedback, > so maybe it's not a bad idea to nuke wd after all. :-) It isn´t only a matter of providing feedback... the maintainer also has to work on it. I offered feedback in every mail regarding my problem with ata & msdos-ZIPs (they aren´t accessible), but most of the time I havn´t got a reply (Søren replied recently to Fritz Heinrichmeyer, he has the same problem). I´m not able to test it at the moment, but I havn´t seen a cvs-all message which said "Problems with MSDOS formated ZIPs fixed". I assume it isn´t fixed and I want to use the wd driver until it´s fixed. Poul-Henning: please wait until Søren fixed the problems some users have (we didn´t want to loose features, right?). Søren: I didn´t want to flame you, I only want to convince Paul-Henning to wait until you have time to fix those bugs. Bye, Alexander. -- We are what we eat; I'm cheap, fast, and easy. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 8:10:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B99ED15557; Wed, 8 Dec 1999 08:10:07 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA53062; Wed, 8 Dec 1999 17:09:39 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912081609.RAA53062@freebsd.dk> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912081421.PAA05970@Magelan.Leidinger.net> from Alexander Leidinger at "Dec 8, 1999 03:21:27 pm" To: Alexander@Leidinger.net (Alexander Leidinger) Date: Wed, 8 Dec 1999 17:09:39 +0100 (CET) Cc: sheldonh@uunet.co.za, phk@FreeBSD.ORG (Poul-Henning Kamp), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alexander Leidinger wrote: > > It isn´t only a matter of providing feedback... the maintainer also has > to work on it. Yeah, right... > I offered feedback in every mail regarding my problem with ata & > msdos-ZIPs (they aren´t accessible), but most of the time I havn´t got a > reply (Søren replied recently to Fritz Heinrichmeyer, he has the same > problem). > I´m not able to test it at the moment, but I havn´t seen a cvs-all > message which said "Problems with MSDOS formated ZIPs fixed". I assume > it isn´t fixed and I want to use the wd driver until it´s fixed. > > Poul-Henning: please wait until Søren fixed the problems some users have > (we didn´t want to loose features, right?). > > Søren: I didn´t want to flame you, I only want to convince Paul-Henning > to wait until you have time to fix those bugs. Welcome to the real world, I've promised to look at this and I will, but a day has only so many hours. Instead of complaining, help the project, when have you last closed a PR ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 8:26:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id 2699E14BF8 for ; Wed, 8 Dec 1999 08:26:18 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id RAA49583; Wed, 8 Dec 1999 17:24:55 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9E0E3C.dip.t-dialin.net [62.158.14.60]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id RAA49577; Wed, 8 Dec 1999 17:24:50 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (doom.rock.net [172.23.7.254]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id RAA75135 for ; Wed, 8 Dec 1999 17:23:46 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <384E8633.BD23E6CC@dead-end.net> Date: Wed, 08 Dec 1999 17:24:19 +0100 From: "D. Rock" X-Mailer: Mozilla 4.7 [de] (Win98; U) X-Accept-Language: de MIME-Version: 1.0 To: Doug Ambrisko Cc: Subject: Re: ATA driver as the default References: <199912071957.LAA31946@whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Ambrisko schrieb: > > D. Rock writes: > | I just re-enabled the ATA driver again after reading the change log > | of better error handling and automatic falldown DMA->PIO under specific > | circumstances. > | But a few days later, while making world (with the ata driver), the > | system > | crashed quite heavily. The file system was totally screwed up afterwards > | (I found my /usr/local after some heavy searching: It magically > | moved to /usr/obj/usr/src/tmp/usr/share/zoneinfo (!) and got tons of > | fsck > | messages). The file system had softupdates enabled. I don't know the > | last kernel messages before the crash (was running X at that time). > > You might want to look at ata-disk.c and the timeout value around line > 438: > > /* start timeout for this transfer */ > if (panicstr) > request->timeout_handle.callout = NULL; > else > request->timeout_handle = > timeout((timeout_t*)ad_timeout, request, 5*hz); > > Originally it was 3s and recently increased to 5s. Personally > I switched it to 30s after it trashed my filesystem when it was 3s. > The issue was that 3s, is that it is to short to wait for my laptop's > drive to spin back up. Sometimes I would get a corrupted read sometimes on > a write it would trash things. I noticed in the old wd driver that > it tried 10s first then a couple 3s timeouts. After making this > change my system has been rock solid when the drive spins down. > Note I haven't tried to tune this value since trashing a 14G filesystem > is pain full. I don't think I have the same problem. My drive definitely doesn't spin down. It sometimes occurs during heavy usage, so the drive should still be very alive. With PIO mode I also don't have any timeout problems. I also had the same DMA problems with the old wd driver and under Windows. The problem is, that the new driver doesn't allow to selectively turn off DMA for problematic devices. I now had commented out the DMA activation code in ata-disk.c (DMA is still activited on the CD-ROM drive though) and I will see how the system behaves. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 8:46:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 25DC414CEB for ; Wed, 8 Dec 1999 08:46:13 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id LAA29580 for ; Wed, 8 Dec 1999 11:46:11 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA23773; Wed, 8 Dec 1999 11:45:41 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id LAA79960 for freebsd-current@freebsd.org; Wed, 8 Dec 1999 11:45:41 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199912081645.LAA79960@bb01f39.unx.sas.com> Subject: make world: doesn't? To: freebsd-current@freebsd.org Date: Wed, 8 Dec 1999 11:45:41 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've just cvsup'd my -current source tree about 5 minutes ago and tried to make world... and got the following: FreeBSD(root)/usr/src %make world make: don't know how to make world. Stop *** Error code 2 Stop in /usr/src. FreeBSD(root)/usr/src % This was ok 24 hours ago... I receive -current as a digest, so I apologize if this is already known and I simply don't know it yet. I'll check the cvs histories to see if I can figure out what changed this afternoon. Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 8:47: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7B81415591 for ; Wed, 8 Dec 1999 08:46:59 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA62277; Wed, 8 Dec 1999 17:46:42 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912081646.RAA62277@freebsd.dk> Subject: Re: ATA driver as the default In-Reply-To: <384E8633.BD23E6CC@dead-end.net> from "D. Rock" at "Dec 8, 1999 05:24:19 pm" To: rock@dead-end.net (D. Rock) Date: Wed, 8 Dec 1999 17:46:42 +0100 (CET) Cc: ambrisko@whistle.com (Doug Ambrisko), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems D. Rock wrote: > I don't think I have the same problem. My drive definitely doesn't spin > down. It sometimes occurs during heavy usage, so the drive should still > be very alive. With PIO mode I also don't have any timeout problems. > I also had the same DMA problems with the old wd driver and under Windows. > The problem is, that the new driver doesn't allow to selectively turn > off DMA for problematic devices. > > I now had commented out the DMA activation code in ata-disk.c (DMA > is still activited on the CD-ROM drive though) and I will see how the > system behaves. I'm working on a way to select DMA or not on each device via a sysctl, that should fix your problem... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 8:50:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from beast.cdrom.com (beast.FreeBSD.ORG [204.216.27.28]) by hub.freebsd.org (Postfix) with ESMTP id 1675314D81 for ; Wed, 8 Dec 1999 08:50:34 -0800 (PST) (envelope-from jkh@beast.cdrom.com) Received: (from jkh@localhost) by beast.cdrom.com (8.9.3/8.9.3) id IAA84486 for current@freebsd.org; Wed, 8 Dec 1999 08:50:34 -0800 (PST) (envelope-from jkh) Date: Wed, 8 Dec 1999 08:50:34 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199912081650.IAA84486@beast.cdrom.com> To: current@freebsd.org Subject: -current release build breakage (at least on alpha) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/gasp -I/usr/sr c/gnu/usr.bin/binutils/gasp/../libbfd/alpha -I/usr/src/gnu/usr.bin/binutils/gasp /../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/gasp/../.. /../../contrib/binutils -I/usr/src/gnu/usr.bin/binutils/gasp/../../../../contrib /binutils/gas -I/usr/src/gnu/usr.bin/binutils/gasp/../../../../contrib/binutils/ gas/config -I/usr/src/gnu/usr.bin/binutils/gasp/../as/as_alpha -DBFD_ASSEMBLER -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/binutils/gasp/../../ ../../contrib/binutils/gas/hash.c In file included from /usr/src/gnu/usr.bin/binutils/gasp/../../../../contrib/bin utils/gas/hash.c:136: /usr/src/gnu/usr.bin/binutils/gasp/../../../../contrib/binutils/gas/as.h:599: ta rg-env.h: No such file or directory *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/gasp. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 9: 3: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 047D814D47 for ; Wed, 8 Dec 1999 09:03:04 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA54766; Wed, 8 Dec 1999 09:02:59 -0800 (PST) Date: Wed, 8 Dec 1999 09:02:58 -0800 (PST) From: Julian Elischer To: "Matthew N. Dodd" Cc: current@FreeBSD.ORG Subject: Re: OHCI weirdness? 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 "me too" (but only if there is a device plugged in) On Wed, 8 Dec 1999, Matthew N. Dodd wrote: > I get this same panic with both devices I've tried; a Kodak DC265 and a > Sandisk CompactFlash reader. Its not obvious why this is happening (at > least from where I'm sitting.) > > Any ideas? > > Should I report back with a kernel compiled with OHCI_DEBUG? > > Thanks. > > ... > ohci0: irq 9 at device 11.0 on pci0 > usb0: OHCI version 1.0, legacy support > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > panic: ohci_hash_find_td: addr 0x03e7c770 not found > > Debugger("panic") > Stopped at Debugger+0x37: movl $0,in_Debugger > db> t > Debugger(c0289aa3) at Debugger+0x37 > panic(c029c0c0,3e7c770,c0373cbc,c0225142,c07a5800) at panic+0x74 > ohci_hash_find_td(c07a5800,3e7c770,6,c07a5800,2) at ohci_hash_find_td+0x33 > ohci_process_done(c07a5800,3e7c7d0,6b9457,c07a5800,c07a6e80) at ohci_process_done+0x1e > ohci_intr1(c07a5800) at ohci_intr1+0x10c > ohci_waitintr(c07a5800,c07a6e80,c07a6e80,c07a6e80,c0373d20) at ohci_waitintr+0x69 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 9: 5:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 524AA14C27; Wed, 8 Dec 1999 09:05:26 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA54836; Wed, 8 Dec 1999 09:05:25 -0800 (PST) Date: Wed, 8 Dec 1999 09:05:24 -0800 (PST) From: Julian Elischer To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <32906.944654135@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG please do not remove it.. just make it non-default. On Wed, 8 Dec 1999, Poul-Henning Kamp wrote: > > In a few days time the wd driver will be retired from FreeBSDs > i386 architecture. > > Users, please: > > Update your kernel config file (see GENERIC) > > Update your /etc/fstab (use /dev/ad* instead of /dev/wd* or > /dev/rwd* > > Copy MAKEDEV from src/etc/MAKEDEV to /dev/MAKEDEV and make > all the ad* disk devices you need for your system. > > Unfortunately current is broken right now, so I can't point > you at a snapshot to reinstall from should you prefer that > option, but I'm sure that current.freebsd.org will be > able to deliver one RSN. > > PC98: > > I would like to discuss with the PC98 responsible commmitters > what the prospects for wd vs ata in PC98 are, please get in > touch with me. > > Poul-Henning > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 9: 6:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 897191557B; Wed, 8 Dec 1999 09:06:52 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA54877; Wed, 8 Dec 1999 09:06:45 -0800 (PST) Date: Wed, 8 Dec 1999 09:06:44 -0800 (PST) From: Julian Elischer To: Soren Schmidt Cc: "Richard Seaman, Jr." , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912081402.PAA23215@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG while you're about it the cyrix GXM? On Wed, 8 Dec 1999, Soren Schmidt wrote: > It seems Richard Seaman, Jr. wrote: > > On Wed, Dec 08, 1999 at 12:55:35PM +0100, Poul-Henning Kamp wrote: > > > > > > In a few days time the wd driver will be retired from FreeBSDs > > > i386 architecture. > > > > > > > Since the ata driver does not support DMA on my chipset, at > > least the last time I tried (SiS 5591), it would be nice > > to leave the wd driver in the tree for a while, even if its > > not the default. Possibly there are others in the same boat? > > OK, you asked for it, following is a patch to support the > sis 5591 chipset. Remember this is done blindfolded, I > have no HW to test on, but you guys do :) > > Let me know what happens... > > Index: ata-all.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v > retrieving revision 1.33 > diff -u -r1.33 ata-all.c > --- ata-all.c 1999/12/07 22:07:18 1.33 > +++ ata-all.c 1999/12/08 13:57:27 > @@ -195,12 +195,6 @@ > return "Intel PIIX4 ATA controller"; > case 0x522910b9: > return "AcerLabs Aladdin ATA controller"; > - case 0x4d33105a: > - return "Promise Ultra/33 ATA controller"; > - case 0x4d38105a: > - return "Promise Ultra/66 ATA controller"; > - case 0x00041103: > - return "HighPoint HPT366 ATA controller"; > case 0x05711106: /* 82c586 & 82c686 */ > switch (pci_read_config(dev, 0x08, 1)) { > case 1: > @@ -209,6 +203,14 @@ > return "VIA 82C686 ATA controller"; > } > return "VIA Apollo ATA controller"; > + case 0x55131039: > + return "SiS 5591 ATA controller"; > + case 0x4d33105a: > + return "Promise Ultra/33 ATA controller"; > + case 0x4d38105a: > + return "Promise Ultra/66 ATA controller"; > + case 0x00041103: > + return "HighPoint HPT366 ATA controller"; > > /* unsupported but known chipsets, generic DMA only */ > case 0x05961106: > Index: ata-dma.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/ata/ata-dma.c,v > retrieving revision 1.21 > diff -u -r1.21 ata-dma.c > --- ata-dma.c 1999/12/07 22:07:18 1.21 > +++ ata-dma.c 1999/12/08 13:57:34 > @@ -297,6 +297,42 @@ > /* we could set PIO mode timings, but we assume the BIOS did that */ > break; > > + case 0x55131039: /* SiS 5591 */ > + devno = (scp->unit << 1) + ((device == ATA_MASTER) ? 0 : 1); > + if (udmamode >= 2) { > + int16_t word4x = pci_read_config(scp->dev, 0x40 + (devno << 1), 2); > + > + pci_write_config(scp->dev, 0x40 + (devno << 1), 0xa301, 2); > + error = ata_command(scp, device, ATA_C_SETFEATURES, 0, 0, 0, > + ATA_UDMA2, ATA_C_F_SETXFER, ATA_WAIT_READY); > + if (bootverbose) > + printf("ata%d: %s: %s setting up UDMA2 mode on SiS chip\n", > + scp->lun, (device == ATA_MASTER) ? "master" : "slave", > + (error) ? "failed" : "success"); > + if (!error) { > + scp->mode[(device == ATA_MASTER) ? 0 : 1] = ATA_MODE_UDMA2; > + return 0; > + } > + pci_write_config(scp->dev, 0x40 + (devno << 1), word4x, 2); > + } > + if (wdmamode >=2 && apiomode >= 4) { > + int16_t word4x = pci_read_config(scp->dev, 0x40 + (devno << 1), 2); > + > + pci_write_config(scp->dev, 0x40 + (devno << 1), 0x0301, 2); > + error = ata_command(scp, device, ATA_C_SETFEATURES, 0, 0, 0, > + ATA_WDMA2, ATA_C_F_SETXFER, ATA_WAIT_READY); > + if (bootverbose) > + printf("ata%d: %s: %s setting up WDMA2 mode on SiS chip\n", > + scp->lun, (device == ATA_MASTER) ? "master" : "slave", > + (error) ? "failed" : "success"); > + if (!error) { > + scp->mode[(device == ATA_MASTER) ? 0 : 1] = ATA_MODE_WDMA2; > + return 0; > + } > + pci_write_config(scp->dev, 0x40 + (devno << 1), word4x, 2); > + } > + break; > + > case 0x4d33105a: /* Promise Ultra33 / FastTrak33 controllers */ > case 0x4d38105a: /* Promise Ultra66 / FastTrak66 controllers */ > /* the Promise can only do DMA on ATA disks not on ATAPI devices */ > > -Søren > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 9:11:49 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 3D85415567; Wed, 8 Dec 1999 09:11:41 -0800 (PST) From: "Jonathan M. Bresler" To: current@FreeBSD.ORG Subject: kern/kern_malloc.c:malloc_init() called twice on devbuf Message-Id: <19991208171141.3D85415567@hub.freebsd.org> Date: Wed, 8 Dec 1999 09:11:41 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [this is a brand spanking new kernel, just compiled 41 minutes ago cvsup'ped just this morning] i was reading the kern_malloc code teh other day and wondered why we have code to return is the malloc_init() has already been dont on that type.....well, we call malloc_init() twice on devbuf. that surprised me. baby:[220] cvs -R diff kern_malloc.c Index: kern_malloc.c =================================================================== RCS file: /usr/home/ncvs/src/sys/kern/kern_malloc.c,v retrieving revision 1.62 diff -r1.62 kern_malloc.c 478a479 > printf("%s ", type->ks_shortdesc); 482c483,485 < if (type->ks_limit != 0) --- > if (type->ks_limit != 0) { > printf("kern_malloc.c:malloc_init() re-init'ing %s\n", > type->ks_shortdesc); 483a487 > } Rebooting... Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. atkbddev isa_devlist memdesc mbuf devbuf isadev ZONE VM pgdata UFS mount UFS quo ta UFS ihash FFS node dirrem mkdir diradd freefile freeblks freefrag allocindir indirdep allocdirect bmsafemap newblk inodedep pagedep p1003.1b ip_moptions ip_f low in_multi igmp routetbl ether_multi ifaddr BPF Export Host vnodes mount clust er_save buffer vfscache BIO buffer pcb soname ptys ttys shm rman iov select ioct lops SWAP eventhandler disk bus sysctl cred subproc proc session pgrp free ip6nd p ip6opt temp devbuf kern_malloc.c:malloc_init() re-init'ing devbuf cache lockf KTRACE prison atfork atexit zombie proc-args sigio file file desc de v_t timecounter kld Gzip trees FreeBSD 4.0-CURRENT #0: Wed Dec 8 11:27:22 EST 1 999 jmb@baby.rad.usi.net:/usr/local/src/sys/compile/BABY Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 399062947 Hz jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 9:15:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from ra.nks.net (ra.nks.net [208.226.218.5]) by hub.freebsd.org (Postfix) with ESMTP id 5996C14D47 for ; Wed, 8 Dec 1999 09:15:18 -0800 (PST) (envelope-from joeo@cracktown.com) Received: from localhost (joeo@localhost) by ra.nks.net (8.8.7/8.8.7) with ESMTP id MAA08808 for ; Wed, 8 Dec 1999 12:15:22 -0500 Date: Wed, 8 Dec 1999 12:15:22 -0500 (EST) From: X-Sender: joeo@ra.nks.net To: current@freebsd.org Subject: PNPBIOS vs cs423B codec Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been trying to get my laptop sound to work with recent kernels. It's a thinkpad 600e with a cs4610 on board. I contacted the author of the newpcm code and he mentioned that instead of using the ac97 codec it most likely uses a cs423x in association with the cs4610. This actually jives with behavior I'd seen under openbsd and the older pnp code, where a sound blaster was probed under freebsd, while openbsd and win95 both see a window sound system lookalike. I'll note that I've never been able to get anything but static out of the older freebsd and openbsd sound drivers on this machine. Anyways, the boot messages indicate that the pnp code for some reason isn't getting any usefull info out of the 423x part (other than the midi or synth part) on bootup (most of the other hardware looks like it correctly responds to th PNPBIOS stuff)... .... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f0000:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 ..... Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask 0000 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) .... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f0000:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 ..... Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask 0000 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) .... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f0000:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 ..... Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask 0000 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) .... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f0000:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 ..... Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask 0000 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) .... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f0000:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 ..... Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask 0000 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) .... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f0000:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 ..... Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask 0000 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) .... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f0000:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 ..... Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask 0000 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) .... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f0000:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 ..... Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask 0000 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) .... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f0000:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 ..... Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask 0000 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) .... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f0000:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 ..... Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask 0000 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) .... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f0000:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 ..... Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask 0000 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) .... Dec 6 16:18:17 mongrel /kernel: avail memory = 127160320 (124180K bytes) Dec 6 16:18:17 mongrel /kernel: bios32: Found BIOS32 Service Directory header at 0xc00fd800 Dec 6 16:18:17 mongrel /kernel: bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 Dec 6 16:18:17 mongrel /kernel: pcibios: PCI BIOS entry at 0x0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Found PnP BIOS data at 0xc00fe700 Dec 6 16:18:17 mongrel /kernel: pnpbios: Entry = f0000:e724 Rev = 1.0 Dec 6 16:18:17 mongrel /kernel: pnpbios: Event flag at 415 Dec 6 16:18:17 mongrel /kernel: Other BIOS signatures found: Dec 6 16:18:17 mongrel /kernel: ACPI: 000fd6e0 ..... Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 13 device ID PNP0501 (0105d041) Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding irq mask 0000 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: adding dma mask 00 Dec 6 16:18:18 mongrel /kernel: CSC0100: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 14 device ID CSC0100 (0001630e) Dec 6 16:18:18 mongrel /kernel: CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0110: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 15 device ID CSC0110 (1001630e) Dec 6 16:18:18 mongrel /kernel: CSC0101: adding io range 0-0xffffffff, size=0, align=0 Dec 6 16:18:18 mongrel /kernel: CSC0101: start dependant Dec 6 16:18:18 mongrel /kernel: pnpbios: handle 16 device ID CSC0101 (0101630e) Any ideas? ... bios32: Found BIOS32 Service Directory header at 0xc00fd800 bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x0 pnpbios: Found PnP BIOS data at 0xc00fe700 pnpbios: Entry = f0000:e724 Rev = 1.0 pnpbios: Event flag at 415 Other BIOS signatures found: ACPI: 000fd6e0 ... csa0: irq 11 at device 6.0 on pci0 device_probe_and_attach: csa0 attach returned 6 ... pnpbios: handle 13 device ID PNP0501 (0105d041) CSC0100: adding io range 0-0xffffffff, size=0, align=0 CSC0100: adding io range 0-0xffffffff, size=0, align=0 CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 CSC0100: adding irq mask 0000 CSC0100: adding dma mask 00 CSC0100: adding dma mask 00 CSC0100: start dependant pnpbios: handle 14 device ID CSC0100 (0001630e) CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 CSC0110: start dependant pnpbios: handle 15 device ID CSC0110 (1001630e) CSC0101: adding io range 0-0xffffffff, size=0, align=0 CSC0101: start dependant pnpbios: handle 16 device ID CSC0101 (0101630e) CSC0103: adding io range 0-0xffffffff, size=0, align=0x10 CSC0103: adding irq mask 0000 CSC0103: start dependant pnpbios: handle 17 device ID CSC0103 (0301630e) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 9:16:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id BC9AD1557D for ; Wed, 8 Dec 1999 09:16:03 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA34156 for ; Wed, 8 Dec 1999 18:15:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: make world is no more ? From: Poul-Henning Kamp Date: Wed, 08 Dec 1999 18:15:54 +0100 Message-ID: <34154.944673354@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I guess this is the ultimate way to break make world... syv# make world make: don't know how to make world. Stop *** Error code 2 Stop in /usr/src. syv# -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 9:18:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 35C9D151D3 for ; Wed, 8 Dec 1999 09:18:17 -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.3/8.9.3) with ESMTP id JAA22677; Wed, 8 Dec 1999 09:18:16 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA29021; Wed, 8 Dec 1999 09:18:15 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 8 Dec 1999 09:18:15 -0800 (PST) Message-Id: <199912081718.JAA29021@vashon.polstra.com> To: dmmiller@cvzoom.net Subject: Re: Cleaning house on /usr/src/* In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Donn Miller wrote: > In the course of development of -current, a bunch of directories are added > and taken away from /usr/src. So, about every month or so, I like to > clean out /usr/src/* and start from scratch. (Well, you know, sometimes > you have so much of your own old code in there.) > > What is the best way to refresh /usr/src then? Do I do an ftp of the > current src at current.freebsd.org, or is it OK to cvsup from scratch from > cvsup[n].freebsd.org? Someone told me it puts too big of a load on the > cvs servers by checking out the whole tree from scratch like this. I > would say it actually puts a lighter load on the cvsup servers, because > there's no files on your machine to compare the tree with. So, you're > basically trading bandwidth for load. You are right. If you're building a src tree from scratch, it's "cheaper" to CVSup from scratch. The CVSup mirror sites generally have more of a bandwidth surplus than a CPU surplus. Besides, if you FTP a snapshot first, that in itself uses a lot of bandwidth. > So, what's the best way to "clean house"? Of course, I only do this once > a month or so if even that. I normally cvsup every 1 or 2 days, but you > know, every once in a while you've got to clean out the /usr/src because > of all the junk directories. Why are you getting these junk directories? CVSup should be deleting them if they're empty. You really shouldn't need to wipe out your tree and start over -- not ever. Did you omit the "delete" keyword from your supfile? John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 9:25:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2E8A9155E4; Wed, 8 Dec 1999 09:25:49 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA70567; Wed, 8 Dec 1999 18:21:57 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912081721.SAA70567@freebsd.dk> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: from Julian Elischer at "Dec 8, 1999 09:05:24 am" To: julian@whistle.com (Julian Elischer) Date: Wed, 8 Dec 1999 18:21:56 +0100 (CET) Cc: phk@FreeBSD.ORG (Poul-Henning Kamp), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Julian Elischer wrote: > please do not remove it.. And why is that ?? There is no point in having done a new one then, and you guys have known I've been working on this for ages so this cannot come as a surprise to anybody... The same thing is about to apply to the woxware sound code, we have a new shiny system that works and is much better designed... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 9:25:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5409E155F8; Wed, 8 Dec 1999 09:25:53 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA70971; Wed, 8 Dec 1999 18:23:33 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912081723.SAA70971@freebsd.dk> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: from Julian Elischer at "Dec 8, 1999 09:06:44 am" To: julian@whistle.com (Julian Elischer) Date: Wed, 8 Dec 1999 18:23:33 +0100 (CET) Cc: dick@tar.com (Richard Seaman Jr.), phk@FreeBSD.ORG (Poul-Henning Kamp), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Julian Elischer wrote: >while you're about it the cyrix GXM? Docs? HW? tester? in that order.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10: 1:58 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 816FB15649; Wed, 8 Dec 1999 09:50:35 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0CE0E1CD737 for ; Wed, 8 Dec 1999 09:50:35 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 8 Dec 1999 09:50:35 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: Reaping error(1) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is error(1) actually useful thesedays? From a look at the source and the docs, it seems like it was only ever relevant to whatever toolchain 4.xBSD used and has never been updated for the GNU toolchain: Error knows about the error messages produced by: make(1), cc(1), cpp(1), ccom(1), as(1), ld(1), lint(1), pi(1), pc(1), f77(1), and DEC Western Research Modula-2. Error knows a standard format for error messages produced by the language processors, so is sensitive to changes in these formats. For all languages except Pascal, error messages are restricted to be on one line. Some error messages refer to more than one line in more than one files; error will duplicate the error message and insert it at all of the places referenced. Is there any productive reason to keep it in our tree? If you have to look up what it does, then I dare say you don't need it :-) I'd also like to rip out fsplit into ports (the code is disgusting and was probably written by a FORTRAN programmer and/or using f2c :) but then I'd draw fire from the "people who know someone who uses FORTRAN" crowd. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10: 2: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id A1F781564A; Wed, 8 Dec 1999 09:54:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C31931CD738; Wed, 8 Dec 1999 09:54:07 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 8 Dec 1999 09:54:07 -0800 (PST) From: Kris Kennaway To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <32906.944654135@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Dec 1999, Poul-Henning Kamp wrote: > Update your /etc/fstab (use /dev/ad* instead of /dev/wd* or > /dev/rwd* Can't we keep the same device names? I thought that was the original plan way back when, once the new driver was ready for prime-time. Also, perhaps we should have a changing-over period where the old drivers are still available under a new name - until recently, Soren was advertising the driver as "WARNING: This is pre-alpha code and may trash your filesystems", etc, which may well have limited his testing base (it certainly scared me off). I'm all for moving forward, but I'd hate to eliminate a fallback path in case the transition proves less than smooth. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10: 3: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from d200.macnet.com (pt22.onlinemac.com [204.200.26.122]) by hub.freebsd.org (Postfix) with ESMTP id 6B3FF15529 for ; Wed, 8 Dec 1999 10:03:07 -0800 (PST) (envelope-from whitecap@d200.macnet.com) Received: from localhost by d200.macnet.com via sendmail with smtp id (Debian Smail3.2.0.102) for ; Thu, 25 Nov 1999 12:45:34 -0800 (PST) Date: Thu, 25 Nov 1999 12:45:34 -0800 (PST) From: Stephen Burns To: freebsd-current@FreeBSD.org Subject: subscribe Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Burns ** Debian/GNU Linux whitecap@macnet.com ** http://www.debian.org http://nite-sky.dhis.org ** Linux, the choice of the GNU generation To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10:10: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id 7D39A156F1 for ; Wed, 8 Dec 1999 10:09:51 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem25.masternet.it [194.184.65.35]) by scotty.masternet.it (8.9.3/8.9.3) with ESMTP id SAA68092; Wed, 8 Dec 1999 18:27:27 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.2.0.58.19991208181426.018f5100@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 08 Dec 1999 18:15:09 +0100 To: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG From: Gianmarco Giovannelli Subject: Re: make world: doesn't? In-Reply-To: <199912081645.LAA79960@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08/12/99, John W. DeBoskey wrote: >Hi, > > I've just cvsup'd my -current source tree about 5 minutes >ago and tried to make world... and got the following: > >FreeBSD(root)/usr/src %make world >make: don't know how to make world. Stop >*** Error code 2 > >Stop in /usr/src. >FreeBSD(root)/usr/src % > > This was ok 24 hours ago... We are in the same boat. It happens here yoo ... Cvsupped 5 minutes ago... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10:10:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B9E721516D; Wed, 8 Dec 1999 10:10:02 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA56167; Wed, 8 Dec 1999 09:42:46 -0800 (PST) Date: Wed, 8 Dec 1999 09:42:45 -0800 (PST) From: Julian Elischer To: Soren Schmidt Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912081721.SAA70567@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG because it doesn't support the chipsets that the old one does. (namely the 200 or so lines of support in pci_ide.c needed for the Cyrix GXM series). You shouldn't remove a function until it has been properly replaced. A very simple concept some people seem to have trouble grasping. On Wed, 8 Dec 1999, Soren Schmidt wrote: > It seems Julian Elischer wrote: > > > please do not remove it.. > > And why is that ?? There is no point in having done a new one then, and > you guys have known I've been working on this for ages so this cannot > come as a surprise to anybody... > > The same thing is about to apply to the woxware sound code, we have a > new shiny system that works and is much better designed... > > -Søren > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10:10:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 2D225156FC; Wed, 8 Dec 1999 10:10:09 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA56202; Wed, 8 Dec 1999 09:43:28 -0800 (PST) Date: Wed, 8 Dec 1999 09:43:26 -0800 (PST) From: Julian Elischer To: Soren Schmidt Cc: "Richard Seaman Jr." , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912081723.SAA70971@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG there is plenty of code in the original that does ALL you need, and I can test it. On Wed, 8 Dec 1999, Soren Schmidt wrote: > It seems Julian Elischer wrote: > > >while you're about it the cyrix GXM? > > Docs? HW? tester? in that order.... > > -Søren > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10:16:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (hermes.dialup.ru [194.87.16.230]) by hub.freebsd.org (Postfix) with ESMTP id 6EDD615715 for ; Wed, 8 Dec 1999 10:16:31 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.1) id VAA06016 for current@freebsd.org; Wed, 8 Dec 1999 21:16:26 +0300 (MSK) (envelope-from ache) Date: Wed, 8 Dec 1999 21:16:24 +0300 From: "Andrey A. Chernov" To: current@freebsd.org Subject: Is there any way to use ATAPI CD-R? Message-ID: <19991208211624.A6005@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I see by quick check, CD-related soft from ports understand SCSI only. Does anybody use new ATAPI CD-R (acd)? If yes, please tell me how. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10:19:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D6ABA15723 for ; Wed, 8 Dec 1999 10:19: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.3/8.9.2) with ESMTP id TAA34307; Wed, 8 Dec 1999 19:19:00 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Wed, 08 Dec 1999 09:42:45 PST." Date: Wed, 08 Dec 1999 19:19:00 +0100 Message-ID: <34305.944677140@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian, Removing wd doesn't leave anybody with a broken system, but certain code may have to be ported and tested by the people who have the hardware. If you have the hardware for some of these IDE controllers, I'm sure sos will receive and integrate your patches. Poul-Henning In message , Jul ian Elischer writes: > >because it doesn't support the chipsets that the old one does. >(namely the 200 or so lines of support in pci_ide.c needed for the Cyrix >GXM series). > >You shouldn't remove a function until it has been properly replaced. >A very simple concept some people seem to have trouble grasping. > >On Wed, 8 Dec 1999, Soren Schmidt wrote: > >> It seems Julian Elischer wrote: >> >> > please do not remove it.. >> >> And why is that ?? There is no point in having done a new one then, and >> you guys have known I've been working on this for ages so this cannot >> come as a surprise to anybody... >> >> The same thing is about to apply to the woxware sound code, we have a >> new shiny system that works and is much better designed... >> >> -Søren >> > > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10:23:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from tomts2-srv.bellnexxia.net (tomts2.bellnexxia.net [209.226.175.140]) by hub.freebsd.org (Postfix) with ESMTP id CDE2A15858 for ; Wed, 8 Dec 1999 10:20:19 -0800 (PST) (envelope-from kfarmer@sympatico.ca) Received: from sympatico.ca ([206.172.165.74]) by tomts2-srv.bellnexxia.net (InterMail vM.4.01.02.07 201-229-116-107) with ESMTP id <19991206200637.POXR29836.tomts2-srv.bellnexxia.net@sympatico.ca> for ; Mon, 6 Dec 1999 15:06:37 -0500 Message-ID: <384C1779.C3010AFA@sympatico.ca> Date: Mon, 06 Dec 1999 15:07:21 -0500 From: Kelvin Farmer X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: boot stops after "Mounting root from ufs:/dev/ad0s2a" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Problem: Computer _sometimes_ stops after the "Mounting root from ufs:/dev/ad0s2a" line. Running Current, built world yesterday. (Problem appeared fairly recently (as in ~2 weeks?, but didn't have ddb in previous kernel) dmesg: [...] ad0: ATA-3 disk at ata0 as master ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, DMA acd0: CDROM drive at ata1 as master acd0: read 1378KB/s (1378KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/ad0s2a [hit ctl-printscreen] Stopped at Debugger+0x37: mov1 $0,in_Debugger db> trace Debugger (c01fb24a) at Debugger+0x37 scgetc(c021c620,2,0,c022d380,ffffffff) at scgetc+0x3ba sckdevent(c022d380,0,c021c620,0,0) at sckbdevent+0x1a1 atkbd_intr(c022d380,0,0,c01c9802,c022d380) at atkbd_intr+0x1f atkbd_isa_intr(c022d380,0,10,10,10) at kbd_isa_intr+0x18 Xresume1() at Xresume1+0x2b --- interrupt, eip=0xc01d36b1, esp=0xc02064d4, ebp=0 --- default_halt() at default_halt+0x1 db>show all procs pid proc addr uid ppid pgrp flag stat wmesg wchan cmd 0 c0234000 E02da000 0 0 0 000204 3 biord c1be7be8 swapper db> [ctl-alt-delete], reboots and then boots ok, mounting /dev/ad0s2a with no problem. Need more info? (this is fairly new to me...) email: kfarmer@sympatico.ca -- Kelvin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10:27:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id EFC2F159D7 for ; Wed, 8 Dec 1999 10:27:34 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id TAA84883 for current@FreeBSD.org; Wed, 8 Dec 1999 19:14:07 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Wed, 08 Dec 1999 19:14:05 +0100 From: Marcel Moolenaar Message-ID: <384E9FED.F9F0D4F4@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199912081645.LAA79960@bb01f39.unx.sas.com> Subject: Re: make world: doesn't? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John W. DeBoskey" wrote: > FreeBSD(root)/usr/src %make world > make: don't know how to make world. Stop > *** Error code 2 Fixed! thanks, -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10:27:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 2D243159E1 for ; Wed, 8 Dec 1999 10:27:40 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id TAA88154 for current@FreeBSD.org; Wed, 8 Dec 1999 19:26:25 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Wed, 08 Dec 1999 19:26:23 +0100 From: Marcel Moolenaar Message-ID: <384EA2CF.B3E40E35@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: , <199912081718.JAA29021@vashon.polstra.com> Subject: Re: Cleaning house on /usr/src/* Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > Why are you getting these junk directories? CVSup should be deleting > them if they're empty. You really shouldn't need to wipe out your > tree and start over -- not ever. Did you omit the "delete" keyword > from your supfile? I recently (last week) cvsup'd a -current source tree over a -stable source tree with the assumption that cvsup would sort it all out. I found out that cvsup doesn't (always?) remove files that are no longer pertinent. This is with the delete keyword present. The -current build broke because there were leftover files (/usr/obj has been removed first). The breakage was solved by removing /usr/src and recvsup-ing from scratch. Details follow... BTW: The files in question were at a minimum /sys/netinet/altq_*.h dwarf% cvsup -v CVSup client, GUI version Software version: REL_15_4 Protocol version: 15.5 Report problems to cvsup-bugs@polstra.com dwarf% more /etc/cvsup.conf *default release=cvs tag=. *default prefix=/usr *default base=/usr *default delete use-rel-suffix *default host=cvsup4.freebsd.org ... dwarf% uname -a FreeBSD dwarf.hq.scc.nl 3.3-STABLE FreeBSD 3.3-STABLE #0: Mon Sep 27 06:10:18 CEST 1999 remco@dwarf.hq.scc.nl:/usr/src/sys/compile/DWARF i386 -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10:27:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 892AD156D4 for ; Wed, 8 Dec 1999 10:27:37 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id TAA84602 for current@FreeBSD.org; Wed, 8 Dec 1999 19:12:56 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Wed, 08 Dec 1999 19:12:53 +0100 From: Marcel Moolenaar Message-ID: <384E9FA5.E5ECEEB6@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <34154.944673354@critter.freebsd.dk> Subject: Re: make world is no more ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > I guess this is the ultimate way to break make world... > > syv# make world > make: don't know how to make world. Stop > *** Error code 2 Oops :-/ The `world' target has been added to Makefile. I guess this only shows that I'm used to use `buildworld' and `installworld'... A new round of testing has been started. Sorry for the inconvenience, -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10:58:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id F1C861516D; Wed, 8 Dec 1999 10:51:38 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id NAA56966; Wed, 8 Dec 1999 13:51:35 -0500 (EST) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id NAA10224; Wed, 8 Dec 1999 13:51:35 -0500 (EST) Message-Id: <3.0.5.32.19991208135002.01d82140@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 08 Dec 1999 13:50:02 -0500 To: Joe Greco From: Mike Tancsa Subject: Re: Route table leaks Cc: jgreco@ns.sol.net, jdp@polstra.com, stable@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199912081451.IAA61233@aurora.sol.net> References: <3.0.5.32.19991208094433.01610ac0@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:51 AM 12/8/99 -0600, Joe Greco wrote: >Most of which are routes pointing at the 3 private-net interfaces on the >machine. The info was provided more as a comparison, that quantity of routes do not necessary mean leak ? Or perhaps it does. But after 90 days, you would think the problem would have been hit no ? ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10:58:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles561.castles.com [208.214.165.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CEB615842 for ; Wed, 8 Dec 1999 10:54:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA06231; Wed, 8 Dec 1999 10:56:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912081856.KAA06231@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Wed, 08 Dec 1999 09:42:45 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Wed, 08 Dec 1999 10:56:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > = > because it doesn't support the chipsets that the old one does. > (namely the 200 or so lines of support in pci_ide.c needed for the Cyri= x > GXM series). > = > You shouldn't remove a function until it has been properly replaced. > A very simple concept some people seem to have trouble grasping. Actually, that's not at all correct. We've demonstrated a number of = times now that you reach a point where a brutal cutover is required. = Failure to do so leaves people clutching the old security blanket for = years, and massively impedes further development. This is a good time for this particular cutover. A little more public = announcement would perhaps have been nice, but that's probably asking = more of our axe-wielding friends than we're ever going to get. The right attitude to be taking now is "here is where the ata drivers = still fall down" or "here are patches to them to replace this = functionality". Think about the longer-term goals here folks. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 10:58:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from ra.nks.net (ra.nks.net [208.226.218.5]) by hub.freebsd.org (Postfix) with ESMTP id 1FE9E15A4B for ; Wed, 8 Dec 1999 10:55:06 -0800 (PST) (envelope-from joeo@cracktown.com) Received: from localhost (joeo@localhost) by ra.nks.net (8.8.7/8.8.7) with ESMTP id NAA09102 for ; Wed, 8 Dec 1999 13:55:09 -0500 Date: Wed, 8 Dec 1999 13:55:09 -0500 (EST) From: X-Sender: joeo@ra.nks.net To: current@freebsd.org Subject: PNPBIOS vs cs423B codec (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've edited the boot messages from my previous mail (the result of fighting with pine over a slow link with a little too much coffee thrown in), sorry to clog up the lines... (fwd) I've been trying to get my laptop sound to work with recent kernels. It's a thinkpad 600e with a cs4610 on board. I contacted the author of the newpcm code and he mentioned that instead of using the ac97 codec it most likely uses a cs423x in association with the cs4610. This actually jives with behavior I'd seen under openbsd and the older pnp code, where a sound blaster was probed under freebsd, while openbsd and win95 both see a window sound system lookalike. I'll note that I've never been able to get anything but static out of the older freebsd and openbsd sound drivers on this machine. Anyways, the boot messages indicate that the pnp code for some reason isn't getting any usefull info out of the 423x part (other than the midi or synth part) on bootup (most of the other hardware looks like it correctly responds to th PNPBIOS stuff)... .... bios32: Found BIOS32 Service Directory header at 0xc00fd800 bios32: Entry = 0xfd820 (c00fd820) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x0 pnpbios: Found PnP BIOS data at 0xc00fe700 pnpbios: Entry = f0000:e724 Rev = 1.0 pnpbios: Event flag at 415 Other BIOS signatures found: ACPI: 000fd6e0 ... csa0: irq 11 at device 6.0 on pci0 device_probe_and_attach: csa0 attach returned 6 ... pnpbios: handle 13 device ID PNP0501 (0105d041) CSC0100: adding io range 0-0xffffffff, size=0, align=0 CSC0100: adding io range 0-0xffffffff, size=0, align=0 CSC0100: adding io range 0-0xffffffff, size=0, align=0x20 CSC0100: adding irq mask 0000 CSC0100: adding dma mask 00 CSC0100: adding dma mask 00 CSC0100: start dependant pnpbios: handle 14 device ID CSC0100 (0001630e) CSC0110: adding io range 0x538-0x53f, size=0x8, align=0 CSC0110: start dependant pnpbios: handle 15 device ID CSC0110 (1001630e) CSC0101: adding io range 0-0xffffffff, size=0, align=0 CSC0101: start dependant pnpbios: handle 16 device ID CSC0101 (0101630e) CSC0103: adding io range 0-0xffffffff, size=0, align=0x10 CSC0103: adding irq mask 0000 CSC0103: start dependant pnpbios: handle 17 device ID CSC0103 (0301630e) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 11:28:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 436C3157F8; Wed, 8 Dec 1999 11:24:07 -0800 (PST) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id UAA17699; Wed, 8 Dec 1999 20:24:00 +0100 (MET) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id UAA11547; Wed, 8 Dec 1999 20:23:59 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912081856.KAA06231@mass.cdrom.com> References: <199912081856.KAA06231@mass.cdrom.com> Date: Wed, 8 Dec 1999 20:23:24 +0100 To: Mike Smith , Julian Elischer From: Brad Knowles Subject: Re: HEADSUP: wd driver will be retired! Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:56 AM -0800 1999/12/8, Mike Smith wrote: >=20 The right attitude to be taking now is "here is where the ata drivers >=20 still fall down" or "here are patches to them to replace this >=20 functionality". Think about the longer-term goals here folks. I understand where Julian is coming from. In fact, my initial=20 reaction was the same. However, I have reluctantly been converted to=20 be in agreement with Mike and S=F8ren (among others). This is -CURRENT. It pains me to say it, but anyone trying to=20 run anything "useful" on -CURRENT gets what they deserve. This is=20 the only place where we can make clean breaks with the past, and as=20 painful as that can be, we simply have to do that occasionally. I'm sure this isn't necessary amongst this group of people, but=20 I'll quote from =20 anyway: >> 18.1.1. What is FreeBSD-current? [ ... deletia ... ] >>=20 While many of us >> compile almost daily from FreeBSD-current sources, there are >> periods of time when the sources are literally un-compilable. --=20 =20 These are my opinions -- not to be taken as official Skynet policy =20 ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ =20 Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. =20 Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 11:29: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id E348915D2E; Wed, 8 Dec 1999 11:26:38 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id NAA80612; Wed, 8 Dec 1999 13:26:17 -0600 (CST) From: Joe Greco Message-Id: <199912081926.NAA80612@aurora.sol.net> Subject: Re: Route table leaks In-Reply-To: <3.0.5.32.19991208135002.01d82140@staff.sentex.ca> from Mike Tancsa at "Dec 8, 1999 1:50: 2 pm" To: mike@sentex.net (Mike Tancsa) Date: Wed, 8 Dec 1999 13:26:16 -0600 (CST) Cc: jdp@polstra.com, stable@FreeBSD.ORG, 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 > At 08:51 AM 12/8/99 -0600, Joe Greco wrote: > >Most of which are routes pointing at the 3 private-net interfaces on the > >machine. > > The info was provided more as a comparison, that quantity of routes do not > necessary mean leak ? Or perhaps it does. But after 90 days, you would > think the problem would have been hit no ? My _point_ was that this issue (or some variant) has been around for some time. I suspect it doesn't have to do with packet forwarding, but does somehow have to do with machines that actually establish or receive TCP connections. Why this only affects certain types of systems, I don't know. Certainly a large number of routes doesn't mean anything. However, > vmstat -m | grep routetbl|grep K routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 > netstat -rn | wc -l 16 289178 blocks (and 40960K - that's 40MB) in use to support 16 routes (that is 2.5MB of memory used per listed route) is a bit on the excessive side. Your example was more along the lines of 20MB to support 65000 routes, only a few hundred bytes per route, which is roughly on the order of what I'd expect per route. I'd think that inbound connections are less likely to be an issue than outbound ones, as inbound connections get really heavily exercised on things like web servers. But that is off-the-top-of-my-head speculation, and I've nothing to support that theory. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 11:29:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 01BEA15D6C; Wed, 8 Dec 1999 11:27:31 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA98301; Wed, 8 Dec 1999 11:25:44 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912081925.LAA98301@gndrsh.dnsmgr.net> Subject: Re: Route table leaks In-Reply-To: <199912081423.IAA59277@aurora.sol.net> from Joe Greco at "Dec 8, 1999 08:23:35 am" To: jgreco@ns.sol.net (Joe Greco) Date: Wed, 8 Dec 1999 11:25:43 -0800 (PST) Cc: jdp@polstra.com (John Polstra), current@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Have any of you been seeing route table leaks in -current? I noticed > > this week that cvsup-master.freebsd.org is suffering from them. I > > actually had to reboot it because it couldn't allocate any more. From > > the "vmstat -m" output: > > > > Memory statistics by type Type Kern > > Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) > > [...] > > routetbl150907 21221K 21221K 21221K 462184 0 0 16,32,64,128,256 > > [...] > > I can think of some experiments to try in order to start to diagnose > > it. But first, have any of you seen this problem? > > Hell, I've been seeing this for well over a year. The last time I mentioned > it, everybody seemed to think I was nuts. :-) :-) > FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 > Mine has leeked very much, and this is on a bgp4 gated box: routetbl143395 19599K 21961K 32768K 2344966 0 0 16,32,64,128,256 Note the request counts vs total table size, oh and: {104}% netstat -ran | wc 69398 418030 4862684 {105}% uptime 11:20AM up 7 days, 8:15, 1 user, load averages: 0.21, 0.06, 0.02 {106}% uname -a FreeBSD br1 3.3-STABLE FreeBSD 3.3-STABLE #0: Tue Nov 23 20:15:59 PST 1999 I haven't leaked away as much as you have, so it seems that actually having the full routing table reduces it :-) > When it gets like that, it starts losing the ability to add further ARP > table entries and essentially starts going randomly deaf to local hosts > (and to a lesser extent remote hosts). Thats what I have seen on 3 occassions now, you get a can't allocate llinfo error from arpresolve/arplookup: /var/log/messages.1.gz:Dec 1 18:01:18 br1 /kernel: arpresolve: can't allocate llinfo for 205.238.40.30rt Note the bad printf output, that ``rt'' really is in my syslogs :-( > > I've also seen it on a 3.3-RELEASE box, but it's not currently happening > to any of them right now. > > Machines in question are SMP boxes, and get hit fairly heavily in various > Usenet news server roles. Seems to happen quite a bit more often on boxes > that talk to a wide variety of host types, and I can't recall having seen > it on boxes that only talk to other FreeBSD boxes. But that could also be > because the network environment is much more controlled internally. > Running a few full blown IBGP and EBGP sessions carrying 2 or more view of the full 68K internet route routing table and it takes about 7 to 10 days of route churn on a large KVM space kernel to cause it to have the llinfo problem... or at least I think this is what I have been seeing since I upgraded our 3.2 systems to 3.3-stable about 3 weeks ago... before this we where getting at least 30 day uptimes (about all I'd let it get before some other change had has rebooting, not due to a problem on the boxes) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 11:32:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B7C4B14C12 for ; Wed, 8 Dec 1999 11:32: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.3/8.9.3) with ESMTP id LAA23164; Wed, 8 Dec 1999 11:32:27 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA29348; Wed, 8 Dec 1999 11:32:26 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 8 Dec 1999 11:32:26 -0800 (PST) Message-Id: <199912081932.LAA29348@vashon.polstra.com> To: jgreco@ns.sol.net Subject: Re: Route table leaks In-Reply-To: <199912081423.IAA59277@aurora.sol.net> References: <199912081423.IAA59277@aurora.sol.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199912081423.IAA59277@aurora.sol.net>, Joe Greco wrote: > > Hell, I've been seeing this for well over a year. The last time I mentioned > it, everybody seemed to think I was nuts. :-) > > FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 Yes, the leak is real. I posted a patch for it in this thread. I'm going to commit it soon. Why don't you try the patch? It fixed the leaks 100% on cvsup-master.freebsd.org. Yes, the leaks are probably present on -stable too. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 11:37:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id B2EDA15A83; Wed, 8 Dec 1999 11:37:10 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA98324; Wed, 8 Dec 1999 11:35:33 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912081935.LAA98324@gndrsh.dnsmgr.net> Subject: Re: Route table leaks In-Reply-To: <3.0.5.32.19991208094433.01610ac0@staff.sentex.ca> from Mike Tancsa at "Dec 8, 1999 09:44:33 am" To: mike@sentex.net (Mike Tancsa) Date: Wed, 8 Dec 1999 11:35:33 -0800 (PST) Cc: jgreco@ns.sol.net (Joe Greco), jdp@polstra.com (John Polstra), stable@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Hell, I've been seeing this for well over a year. The last time I mentioned > >it, everybody seemed to think I was nuts. :-) > > > >FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > > > routetbl289178 40961K 40961K 40960K 435741 0 0 > 16,32,64,128,256 > > Well, I havent seen problems of this nature (yet), but for reference, > > > netstat -nr | wc > 69585 419164 4875822 > > routetbl143718 19653K 21229K 21229K 6527152 0 0 16,32,64,128,256 > > FreeBSD 3.3-RC #0: Wed Sep 8 13:37:19 EDT 1999 > uptime > 9:44AM up 90 days, 20:35, 2 users, load averages: 0.00, 0.01, 0.00 > > This is a border router with 2 views of the net running defaultless. See my other email, and now upon further though having full routes without a default means the clonning code doesn't get used much, since you already have real routes :-). Thus your problem would be less. Hummmm.... let me go to a box running ``defaulted'' yet producing several 100k connections/day and see how bad it's route space looks. routetbl 329 45K 1532K 42709K 504060 0 0 16,32,64,128,256 :rgrimes{100}% netstat -ran | wc 69 403 4675 Yep... looks like it leaked 329-69==260 in 17 days uptime :-( -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 11:49: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.cioe.com (ns1.cioe.com [204.120.165.37]) by hub.freebsd.org (Postfix) with ESMTP id 2C72815A4E; Wed, 8 Dec 1999 11:46:57 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: from ny1wsh031 (tek.cioe.com [204.120.165.120]) by ns1.cioe.com (8.9.3/8.9.3) with SMTP id OAA41564; Wed, 8 Dec 1999 14:33:59 -0500 (EST) (envelope-from steve@virtual-voodoo.com) Message-ID: <023501bf41b3$242c07c0$851a050a@winstar.com> From: "Steven E. Ames" To: "Julian Elischer" , "Mike Smith" Cc: References: <199912081856.KAA06231@mass.cdrom.com> Subject: Re: HEADSUP: wd driver will be retired! Date: Wed, 8 Dec 1999 14:33:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Agreed. -CURRENT is all about development. New ideas will be tried, sometimes (sometimes a lot :) things are going to be broke. I switched to the new ATA driver on Monday. Seems to work but I have some questions. Could someone (sos?) post a quick primer on how to read the probe messages? With the old wd driver I understood the messages and it was readily apparent when something wasn't using DMA, large blocks, etc... The new ATA driver is here to stay. Yep. It needs some serious testing. Yep. If someone would post a quick how-to of stuff to do/look-for I'm sure more people would be willing to test with a smile on their face. Here's the relevant portion of my probe: ata-pci0: irq 0 at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 . . ad0: ATA-? disk at ata0 as master ad0: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, PIO ad1: ATA-? disk at ata0 as slave ad1: 4134MB (8467200 sectors), 8960 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, PIO acd0: CDROM drive at ata1 as master acd0: read 1033KB/s (1033KB/s), 256KB buffer, PIO acd0: supported read types: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked ata_command: timeout waiting for interrupt I have no idea what have of these messages mean. This is less clear to me (probably because I'm used to the old messages) than the 'wd' messages. Also, like others, I'm getting that 'ata_command: timeout waiting for interrupt' at the end. -Steve ----- Original Message ----- From: Mike Smith To: Julian Elischer Cc: Sent: Wednesday, December 08, 1999 1:56 PM Subject: Re: HEADSUP: wd driver will be retired! > > > > because it doesn't support the chipsets that the old one does. > > (namely the 200 or so lines of support in pci_ide.c needed for the Cyrix > > GXM series). > > > > You shouldn't remove a function until it has been properly replaced. > > A very simple concept some people seem to have trouble grasping. > > Actually, that's not at all correct. We've demonstrated a number of > times now that you reach a point where a brutal cutover is required. > Failure to do so leaves people clutching the old security blanket for > years, and massively impedes further development. > > This is a good time for this particular cutover. A little more public > announcement would perhaps have been nice, but that's probably asking > more of our axe-wielding friends than we're ever going to get. > > The right attitude to be taking now is "here is where the ata drivers > still fall down" or "here are patches to them to replace this > functionality". Think about the longer-term goals here folks. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 11:49:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id BEE9015648 for ; Wed, 8 Dec 1999 11:48:36 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id LAA60017; Wed, 8 Dec 1999 11:48:32 -0800 (PST) Date: Wed, 8 Dec 1999 11:48:31 -0800 (PST) From: Julian Elischer To: Poul-Henning Kamp Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <34305.944677140@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG that is not the way it should be.. Someone replacing a module and deleting th eoriginal should make a decent effort to cover all the present functionality. (OR make a decision that such functionality will never be covered, (e.g. bad144)). Just breaking things because you felt you'd rather not spend the time doing it is not an answer. Making something drop back from DMA to non DMA comes under the heading "breaking" for me. On Wed, 8 Dec 1999, Poul-Henning Kamp wrote: > > Julian, > > Removing wd doesn't leave anybody with a broken system, but certain > code may have to be ported and tested by the people who have the > hardware. > > If you have the hardware for some of these IDE controllers, I'm sure > sos will receive and integrate your patches. > > Poul-Henning > > In message , Jul > ian Elischer writes: > > > >because it doesn't support the chipsets that the old one does. > >(namely the 200 or so lines of support in pci_ide.c needed for the Cyrix > >GXM series). > > > >You shouldn't remove a function until it has been properly replaced. > >A very simple concept some people seem to have trouble grasping. > > > >On Wed, 8 Dec 1999, Soren Schmidt wrote: > > > >> It seems Julian Elischer wrote: > >> > >> > please do not remove it.. > >> > >> And why is that ?? There is no point in having done a new one then, and > >> you guys have known I've been working on this for ages so this cannot > >> come as a surprise to anybody... > >> > >> The same thing is about to apply to the woxware sound code, we have a > >> new shiny system that works and is much better designed... > >> > >> -Søren > >> > > > > > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 12:10:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 062CC161EE for ; Wed, 8 Dec 1999 11:58:47 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA34772; Wed, 8 Dec 1999 20:58:29 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Wed, 08 Dec 1999 11:48:31 PST." Date: Wed, 08 Dec 1999 20:58:28 +0100 Message-ID: <34770.944683108@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Jul ian Elischer writes: >Someone replacing a module and deleting th eoriginal should make a decent >effort to cover all the present functionality. (OR make a decision that >such functionality will never be covered, (e.g. bad144)). >Just breaking things because you felt you'd rather not spend the time >doing it is not an answer. Julian, I have not heard anybody here saying that "they'd rather not spend the time doing it". I have in fact heard Soren spend quite an amount of time calling for testers for the last many months. If you have the hardware, I suggest you either drop it in a box and ship it to soren or sit down and integrate the code yourself. Either of those approaches will be many times more efficient that the one you're taking right now. Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 12:10:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 840621628C; Wed, 8 Dec 1999 12:00:49 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA34791; Wed, 8 Dec 1999 21:00:36 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kris Kennaway Cc: current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Wed, 08 Dec 1999 09:54:07 PST." Date: Wed, 08 Dec 1999 21:00:36 +0100 Message-ID: <34789.944683236@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Kris Ken naway writes: >On Wed, 8 Dec 1999, Poul-Henning Kamp wrote: > >> Update your /etc/fstab (use /dev/ad* instead of /dev/wd* or >> /dev/rwd* > >Can't we keep the same device names? I thought that was the original plan >way back when, once the new driver was ready for prime-time. > >Also, perhaps we should have a changing-over period where the old drivers >are still available under a new name - until recently, Soren was >advertising the driver as "WARNING: This is pre-alpha code and may trash >your filesystems", etc, which may well have limited his testing base (it >certainly scared me off). I'm all for moving forward, but I'd hate to >eliminate a fallback path in case the transition proves less than smooth. The fallback path is not eliminated, and may never be, but it may become rather uncomfortable to linger on it longer than you absolutely need to. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 12:18:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id ED927164AC; Wed, 8 Dec 1999 12:08:18 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id PAA23869; Wed, 8 Dec 1999 15:08:07 -0500 (EST) Message-ID: <19991208150807.A16687@netmonger.net> Date: Wed, 8 Dec 1999 15:08:07 -0500 From: Christopher Masto To: Mike Smith , Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! References: <199912081856.KAA06231@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199912081856.KAA06231@mass.cdrom.com>; from Mike Smith on Wed, Dec 08, 1999 at 10:56:24AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: > > You shouldn't remove a function until it has been properly replaced. > > A very simple concept some people seem to have trouble grasping. > > Actually, that's not at all correct. We've demonstrated a number of > times now that you reach a point where a brutal cutover is required. > Failure to do so leaves people clutching the old security blanket for > years, and massively impedes further development. Unfortunately, FreeBSD has far too many examples of a working system being replaced with a less functional system. Just off the top of my head, there were the SCSI drivers lost to CAM, the PCCARD system, sound drivers, and now ATA. All of those things needed to be redesigned, but I think it's unfortunate and dangerous to public perception when version X has less hardware support than version X-1. Right now, I have no sound (not detected), no USB (panic on removal), can't use my sio pccard, can't eject my ed pccard, my IDE drives are taking hours to dump and fsck, and my TV card is missing every other line if I try to use the (not working anyway) closed caption decoder. Now, I running -current on this machine, I've asked for problems, and I have them. I try to fix them and/or send decent bug reports when I can, and I don't piss and moan when something breaks, because it's -current. I just get a feeling sometimes like we're moving forward on a treadmill that's moving backward just slightly faster. My opinion is that the right approach is to change the defaults sooner, but remove the old code later. In other words, -current's GENERIC should have been using new-ATA as soon as it was working, but we shouldn't remove the wd driver entirely until all of its functionality is available in its replacement. Of course, in reality, APIs change and old code isn't always worth the effort of porting, so sometimes you just have to let go. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 12:19:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from histidine.utmb.edu (histidine.utmb.edu [129.109.59.80]) by hub.freebsd.org (Postfix) with ESMTP id 3DBAC158C6; Wed, 8 Dec 1999 12:09:41 -0800 (PST) (envelope-from bdodson@scms.utmb.EDU) Received: (from bdodson@localhost) by histidine.utmb.edu (8.9.3/8.9.3) id OAA04379; Wed, 8 Dec 1999 14:09:38 -0600 (CST) (envelope-from bdodson) Date: Wed, 8 Dec 1999 14:09:38 -0600 (CST) Message-Id: <199912082009.OAA04379@histidine.utmb.edu> From: "M. L. Dodson" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Reaping error(1) In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway writes: [error(1) stuff elided] > Is there any productive reason to keep it in our tree? If you have to look > up what it does, then I dare say you don't need it :-) > > I'd also like to rip out fsplit into ports (the code is disgusting and > was probably written by a FORTRAN programmer and/or using f2c :) but then > I'd draw fire from the "people who know someone who uses FORTRAN" crowd. > > Kris > I AM someone who uses FORTRAN, and I say "Go for it!" ;-) Bud Dodson -- M. L. Dodson bdodson@scms.utmb.edu 409-772-2178 FAX: 409-772-1790 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 12:19:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id B1DE61562E; Wed, 8 Dec 1999 12:10:19 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id MAA40896; Wed, 8 Dec 1999 12:10:26 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199912082010.MAA40896@troutmask.apl.washington.edu> Subject: Re: Reaping error(1) In-Reply-To: from Kris Kennaway at "Dec 8, 1999 09:50:35 am" To: kris@hub.freebsd.org (Kris Kennaway) Date: Wed, 8 Dec 1999 12:10:26 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > I'd also like to rip out fsplit into ports (the code is disgusting and > was probably written by a FORTRAN programmer and/or using f2c :) but then > I'd draw fire from the "people who know someone who uses FORTRAN" crowd. > I was going to fix fsplit. Yes, I program in Fortran (note the proper spelling of Fortran). No, I don't use fsplit. We might also want to remove fpr(1). It should be noted that both fsplit and fpr apply to legacy Fortran 77 code (and older). Neither utility can deal with Fortran 90 or Fortran 95. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 12:21: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.topcu.com (helm.topcu.com [63.72.123.2]) by hub.freebsd.org (Postfix) with ESMTP id 6E54A14A21 for ; Wed, 8 Dec 1999 12:19:16 -0800 (PST) (envelope-from g4465g@aol.com) Received: from . (98ACE949.ipt.aol.com [152.172.233.73]) by mail.topcu.com (8.9.3/8.9.3) with SMTP id MAA25871; Wed, 8 Dec 1999 12:14:38 -0800 Date: Wed, 8 Dec 1999 12:14:38 -0800 From: g4465g@aol.com Message-Id: <199912082014.MAA25871@mail.topcu.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG DATA From: g4465g@aol.com To: Date: Thu, 09 Dec 1999 03:20:11 PST Subject: SKIN BECOMES DRAMATICALLY EVEN-TONED AND CLEAR... SKIN PROBLEMS? LET "DERMACURE" SOLVE THEM! Hello. We have good news for you. "DERMACURE" IS MADE FOR YOUR SKIN. If you suffer from any form of skin discolorations, such as dark marks, acne or pimple marks, scars, under-eye circles, razor bump marks, spots, freckles, uneven skin tone, shaving scars, shavers shadow, stretch-marks, dark areas of skin, or any other skin imperfections, you owe it to yourself to learn more about DERMACURE. Your skin can become dramatically even-toned and clear. "Dermacure" was first created in 1975. It has been thoroughly researched and perfected, has had many case studies conducted and has been improved many times over the past 24 years. This truly remarkable cosmetic treatment will eliminate your skin problems once and for all. "DERMACURE" IS MADE FOR YOUR SKIN. It's formula has been found by The U. S. Food and Drug Administration to be both safe and effective. DERMACURE is just as effective for males as it is for females, and is completely safe and gentle to sensitive skin. Our skin treatments are for all races, shades and ages of skin. If you wish to receive free additional information about "Dermacure", or If you have any questions, please email them to... improve22@usa.net We will answer you quickly. ALSO...if you have acne or pimple problems, or blackheads, whiteheads, or shaving bumps on your face or anywhere on your body, email us at improve22@usa.net for information about a remarkable acne and pimple Eliminator. ...If you suffer from stretch-marks, please let us know also. We have a stretch mark treatment made for this skin condition. Email us at improve22@usa.net ...Do you have psoriasis or eczema? We can help.. email us at improve22@usa.net We are an international company. You can be assured of fast, reliable delivery. Our elaborate shipping facilities and expert staff assure you of the highest quality service, whether you are here in the USA, or anywhere in the world. Respectfully and Sincerely, Mrs. Christine Yang, Mrs. Brenda Boykin and Mr. John Shigira P. S. It is never our intention to offend or annoy or disrespect anyone. If you do not appreciate receiving this message, please let us know by simply clicking REPLY and typing the word "REMOVE" IN THE SUBJECT LINE. (Not The Body) You will then be promptly and permanently removed from our list. We humbly apologize if you are in any way offended by receiving this email. " SKIN IS OUR BUSINESS...OUR ONLY BUSINESS". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 12:29:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 6A4A81571D for ; Wed, 8 Dec 1999 12:25:40 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991208152538.43637@mojave.sitaranetworks.com> Date: Wed, 8 Dec 1999 15:25:38 -0500 From: Greg Lehey To: Kelvin Farmer , freebsd-current@FreeBSD.ORG Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" Reply-To: Greg Lehey References: <384C1779.C3010AFA@sympatico.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <384C1779.C3010AFA@sympatico.ca>; from Kelvin Farmer on Mon, Dec 06, 1999 at 03:07:21PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 6 December 1999 at 15:07:21 -0500, Kelvin Farmer wrote: > > Problem: Computer _sometimes_ stops after the "Mounting root from > ufs:/dev/ad0s2a" line. > Running Current, built world yesterday. (Problem appeared fairly > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) > > dmesg: > [...] > ad0: ATA-3 disk at ata0 as master > ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, DMA > acd0: CDROM drive at ata1 as master > acd0: read 1378KB/s (1378KB/s), 128KB buffer, PIO > acd0: supported read types: CD-R, CD-DA > acd0: Audio: play, 256 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked > Mounting root from ufs:/dev/ad0s2a It's difficult to mount your root if there's no disk in the drive. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 12:29:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 6B80814BDC; Wed, 8 Dec 1999 12:27:19 -0800 (PST) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id VAA22995; Wed, 8 Dec 1999 21:27:07 +0100 (MET) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id VAA01416; Wed, 8 Dec 1999 21:27:02 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912081926.NAA80612@aurora.sol.net> References: <199912081926.NAA80612@aurora.sol.net> Date: Wed, 8 Dec 1999 21:26:05 +0100 To: Joe Greco , mike@sentex.net (Mike Tancsa) From: Brad Knowles Subject: Re: Route table leaks Cc: jdp@polstra.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:26 PM -0600 1999/12/8, Joe Greco wrote: >> vmstat -m | grep routetbl|grep K > routetbl289178 40961K 40961K 40960K 435741 0 0 >16,32,64,128,256 >> netstat -rn | wc -l > 16 I had never looked at this on my machines (main news peering server in the Top 100, one Intel EtherExpress Pro 10/100+ 100-Base-TX interface with a default route, running 3.2-RELEASE): $ vmstat -m | grep routetbl | grep K routetbl 246 34K 36K 40960K 920 0 0 16,32,64,128,256 $ netstat -nr | wc -l 13 $ uptime 9:07PM up 7 days, 8:06, 1 user, load averages: 2.87, 3.14, 3.15 $ ps axl | grep ':' | wc -l 379 > 289178 blocks (and 40960K - that's 40MB) in use to support 16 routes (that > is 2.5MB of memory used per listed route) is a bit on the excessive side. This machine hasn't been up very long, is running an application profile that I assume is somewhat similar to yours (although I'm sure yours is much more heavily tuned, as well as loaded), but 2,835.692 bytes per route (26K/13) still seems a bit excessive. I've got another machine (an internal mailing list server, very very lightly loaded, one Intel EtherExpress Pro 10/100+ 100-Base-TX interface with a default route, running 3.0-RELEASE) that looks much more reasonable: $ vmstat -m | grep routetbl | grep K routetbl 32 4K 8K 10400K 13212 0 0 16,32,64,128,256 $ netstat -nr | wc -l 11 $ uptime 9:25PM up 135 days, 11:04, 1 user, load averages: 0.02, 0.01, 0.00 $ ps axl | grep ':' | wc -l 30 However, even 744.727 bytes per route (8K/11) seems a little higher than what I would expect, although this is *much* better than almost 3KB/route, and especially better than 2,621,504.000 bytes/route (40MB/16). The 312.402 bytes/route (20.731MB/69585) that Mike reported seems much more realistic. > I'd think that inbound connections are less likely to be an issue than > outbound ones, as inbound connections get really heavily exercised on > things like web servers. But that is off-the-top-of-my-head speculation, > and I've nothing to support that theory. Unfortunately, I don't have any FreeBSD web servers here that I can test that theory with. I'm trying to get more FreeBSD production servers installed here, but progress has been rather slow -- I can only roll them in as old servers need to be replaced, and as FreeBSD supports the hardware & software I need to use in order to support the application. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 12:35:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 37FB51570C for ; Wed, 8 Dec 1999 12:34:38 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA17215; Wed, 8 Dec 1999 21:34:24 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912082034.VAA17215@freebsd.dk> Subject: Re: Is there any way to use ATAPI CD-R? In-Reply-To: <19991208211624.A6005@nagual.pp.ru> from "Andrey A. Chernov" at "Dec 8, 1999 09:16:24 pm" To: ache@nagual.pp.ru (Andrey A. Chernov) Date: Wed, 8 Dec 1999 21:34:24 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Andrey A. Chernov wrote: > As I see by quick check, CD-related soft from ports understand SCSI only. > Does anybody use new ATAPI CD-R (acd)? If yes, please tell me how. I use it every day, well almost :) Look in /usr/share/examples/atapi... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 12:51: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 29EB214A10; Wed, 8 Dec 1999 12:50:59 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00517; Wed, 8 Dec 1999 12:52:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912082052.MAA00517@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Christopher Masto Cc: Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Wed, 08 Dec 1999 15:08:07 EST." <19991208150807.A16687@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Dec 1999 12:52:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: > > > You shouldn't remove a function until it has been properly replaced. > > > A very simple concept some people seem to have trouble grasping. > > > > Actually, that's not at all correct. We've demonstrated a number of > > times now that you reach a point where a brutal cutover is required. > > Failure to do so leaves people clutching the old security blanket for > > years, and massively impedes further development. > > Unfortunately, FreeBSD has far too many examples of a working system > being replaced with a less functional system. Just off the top of my > head, there were the SCSI drivers lost to CAM, the PCCARD system, > sound drivers, and now ATA. Actually, most of this is histrionics. CAM didn't lose us SCSI drivers; we actually _gained_ from it. We haven't "lost" the pccard system at all, and the new sound code is on a feature-par with both of the old ones. What we need here is a commitment to these new initiatives, not a lot of fence-sitting and clutching our knitting to our chests. All of these initiatives were started to deal with massive problems in the subsystems they replace; clinging to the old code rather than getting on-board and helping with the new code directly impedes the resolution of these problems. Again, I say, think of what we're trying to achieve here. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 12:52:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id BA0BB14BC3 for ; Wed, 8 Dec 1999 12:52:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00533; Wed, 8 Dec 1999 12:54:10 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912082054.MAA00533@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Lehey Cc: Kelvin Farmer , freebsd-current@FreeBSD.ORG Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" In-reply-to: Your message of "Wed, 08 Dec 1999 15:25:38 EST." <19991208152538.43637@mojave.sitaranetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Dec 1999 12:54:10 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Monday, 6 December 1999 at 15:07:21 -0500, Kelvin Farmer wrote: > > > > Problem: Computer _sometimes_ stops after the "Mounting root from > > ufs:/dev/ad0s2a" line. > > Running Current, built world yesterday. (Problem appeared fairly > > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) > > > > dmesg: > > [...] > > ad0: ATA-3 disk at ata0 as master > > ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > > ad0: 16 secs/int, 1 depth queue, DMA > > acd0: CDROM drive at ata1 as master > > acd0: read 1378KB/s (1378KB/s), 128KB buffer, PIO > > acd0: supported read types: CD-R, CD-DA > > acd0: Audio: play, 256 volume levels > > acd0: Mechanism: ejectable tray > > acd0: Medium: no/blank disc inside, unlocked > > Mounting root from ufs:/dev/ad0s2a > > It's difficult to mount your root if there's no disk in the drive. Er, 'ad0' != 'acd0'. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 12:55: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.cioe.com (ns1.cioe.com [204.120.165.37]) by hub.freebsd.org (Postfix) with ESMTP id 98B9914BE1 for ; Wed, 8 Dec 1999 12:55:00 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: from ny1wsh031 (tek.cioe.com [204.120.165.120]) by ns1.cioe.com (8.9.3/8.9.3) with SMTP id PAA20372; Wed, 8 Dec 1999 15:54:15 -0500 (EST) (envelope-from steve@virtual-voodoo.com) Message-ID: <030901bf41be$5be61420$851a050a@winstar.com> From: "Steven E. Ames" To: "Greg Lehey" , "Kelvin Farmer" , References: <384C1779.C3010AFA@sympatico.ca> <19991208152538.43637@mojave.sitaranetworks.com> Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" Date: Wed, 8 Dec 1999 15:53:58 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ad0: ATA-3 disk at ata0 as master > > ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > > ad0: 16 secs/int, 1 depth queue, DMA > > acd0: CDROM drive at ata1 as master > > acd0: read 1378KB/s (1378KB/s), 128KB buffer, PIO > > acd0: supported read types: CD-R, CD-DA > > acd0: Audio: play, 256 volume levels > > acd0: Mechanism: ejectable tray > > acd0: Medium: no/blank disc inside, unlocked > > Mounting root from ufs:/dev/ad0s2a > > It's difficult to mount your root if there's no disk in the drive. What? He's mounting /dev/ad0s2a... ad0 was detected as a Quantum Fireball. acd0 has no disc inside. Agreed. -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 13:18:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 6810314C19 for ; Wed, 8 Dec 1999 13:17:26 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id PAA11326; Wed, 8 Dec 1999 15:17:00 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Wed, 8 Dec 1999 15:17:00 -0600 (CST) From: David Scheidt To: Greg Lehey Cc: Kelvin Farmer , freebsd-current@FreeBSD.ORG Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" In-Reply-To: <19991208152538.43637@mojave.sitaranetworks.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, 8 Dec 1999, Greg Lehey wrote: > On Monday, 6 December 1999 at 15:07:21 -0500, Kelvin Farmer wrote: > > > > Problem: Computer _sometimes_ stops after the "Mounting root from > > ufs:/dev/ad0s2a" line. > > Running Current, built world yesterday. (Problem appeared fairly > > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) > > > > dmesg: > > [...] > > ad0: ATA-3 disk at ata0 as master > > ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > > ad0: 16 secs/int, 1 depth queue, DMA > > acd0: CDROM drive at ata1 as master > > acd0: read 1378KB/s (1378KB/s), 128KB buffer, PIO > > acd0: supported read types: CD-R, CD-DA > > acd0: Audio: play, 256 volume levels > > acd0: Mechanism: ejectable tray > > acd0: Medium: no/blank disc inside, unlocked > > Mounting root from ufs:/dev/ad0s2a > > It's difficult to mount your root if there's no disk in the drive. ad0 != acd0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 13:30:40 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id A8807151D7; Wed, 8 Dec 1999 13:30:38 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 997271CD737; Wed, 8 Dec 1999 13:30:38 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 8 Dec 1999 13:30:38 -0800 (PST) From: Kris Kennaway To: "John W. DeBoskey" Cc: freebsd-current@freebsd.org Subject: Re: make world: doesn't? In-Reply-To: <199912081645.LAA79960@bb01f39.unx.sas.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Dec 1999, John W. DeBoskey wrote: > I've just cvsup'd my -current source tree about 5 minutes > ago and tried to make world... and got the following: > > FreeBSD(root)/usr/src %make world > make: don't know how to make world. Stop > *** Error code 2 Is this a candidate for 'world's largest pointy hat'? :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 13:31:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 030E115166; Wed, 8 Dec 1999 13:31:27 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA31612; Wed, 8 Dec 1999 22:31:22 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912082131.WAA31612@freebsd.dk> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991208150807.A16687@netmonger.net> from Christopher Masto at "Dec 8, 1999 03:08:07 pm" To: chris@netmonger.net (Christopher Masto) Date: Wed, 8 Dec 1999 22:31:22 +0100 (CET) Cc: msmith@FreeBSD.ORG (Mike Smith), julian@whistle.com (Julian Elischer), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Christopher Masto wrote: > On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: > > > You shouldn't remove a function until it has been properly replaced. > > > A very simple concept some people seem to have trouble grasping. > > > > Actually, that's not at all correct. We've demonstrated a number of > > times now that you reach a point where a brutal cutover is required. > > Failure to do so leaves people clutching the old security blanket for > > years, and massively impedes further development. > > Unfortunately, FreeBSD has far too many examples of a working system > being replaced with a less functional system. Just off the top of my > head, there were the SCSI drivers lost to CAM, the PCCARD system, > sound drivers, and now ATA. Hmm, well, if you want support for any of the new ata-66 controllers you have to use the ata driver, so you loose some you win some. Given that my patch for the SiS works and a patch I got from Luoqi, the ONLY support you are loosing is the Cyrix. > Right now, I have no sound (not detected), no USB (panic on removal), > can't use my sio pccard, can't eject my ed pccard, my IDE drives are > taking hours to dump and fsck, and my TV card is missing every other > line if I try to use the (not working anyway) closed caption decoder. > > Now, I running -current on this machine, I've asked for problems, and > I have them. I try to fix them and/or send decent bug reports when I > can, and I don't piss and moan when something breaks, because it's > -current. I just get a feeling sometimes like we're moving forward on > a treadmill that's moving backward just slightly faster. Well, progress doesn't come for free you know, somebody has to do the hard work of actually implementing things. So if you think its going too slowly, do something about it, help out where you can, but complaining isn't helping anybody :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 13:43:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id EE92814EA2 for ; Wed, 8 Dec 1999 13:43:24 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 72ABE1C4A; Wed, 8 Dec 1999 15:44:07 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 6F7D5381B; Wed, 8 Dec 1999 15:44:07 -0500 (EST) Date: Wed, 8 Dec 1999 15:44:07 -0500 (EST) From: Bill Fumerola To: nnd@mail.nsk.ru Cc: current@freebsd.org Subject: Re: gasp broke world. In-Reply-To: <199912080526.LAA13126@wint.itfs.nsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Dec 1999 nnd@mail.nsk.ru wrote: > --- src/gnu/usr.bin/binutils/gasp/Makefile.ORIG Wed Dec 8 09:52:19 1999 > +++ src/gnu/usr.bin/binutils/gasp/Makefile Wed Dec 8 09:52:19 1999 > @@ -11,7 +11,7 @@ > CFLAGS+= -I${SRCDIR} > CFLAGS+= -I${SRCDIR}/gas > CFLAGS+= -I${SRCDIR}/gas/config > -CFLAGS+= -I${.CURDIR}/../as/as_${MACHINE_ARCH} > +CFLAGS+= -I${.CURDIR}/../as/${MACHINE_ARCH}-freebsd > CFLAGS+= -DBFD_ASSEMBLER > LDADD+= -L${RELTOP}/libiberty -liberty > DPADD+= ${RELTOP}/libiberty/libiberty.a That's how I did it to, I just figured it was the Wrong Way. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 13:54:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 9855B14BC2; Wed, 8 Dec 1999 13:54:21 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991208165325.32169@mojave.sitaranetworks.com> Date: Wed, 8 Dec 1999 16:53:25 -0500 From: Greg Lehey To: "Steven E. Ames" , Kelvin Farmer , freebsd-current@FreeBSD.ORG, Mike Smith , David Scheidt Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" Reply-To: Greg Lehey References: <384C1779.C3010AFA@sympatico.ca> <19991208152538.43637@mojave.sitaranetworks.com> <030901bf41be$5be61420$851a050a@winstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <030901bf41be$5be61420$851a050a@winstar.com>; from Steven E. Ames on Wed, Dec 08, 1999 at 03:53:58PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 8 December 1999 at 15:53:58 -0500, Steven E. Ames wrote: >>> ad0: ATA-3 disk at ata0 as master >>> ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S >>> ad0: 16 secs/int, 1 depth queue, DMA >>> acd0: CDROM drive at ata1 as master >>> acd0: read 1378KB/s (1378KB/s), 128KB buffer, PIO >>> acd0: supported read types: CD-R, CD-DA >>> acd0: Audio: play, 256 volume levels >>> acd0: Mechanism: ejectable tray >>> acd0: Medium: no/blank disc inside, unlocked >>> Mounting root from ufs:/dev/ad0s2a >> >> It's difficult to mount your root if there's no disk in the drive. > > What? He's mounting /dev/ad0s2a... ad0 was detected as a Quantum > Fireball. acd0 has no disc inside. Agreed. On Wednesday, 8 December 1999 at 12:54:10 -0800, Mike Smith wrote: > > Er, 'ad0' != 'acd0'. On Wednesday, 8 December 1999 at 15:17:00 -0600, David Scheidt wrote: > > ad0 != acd0 Indeed. Sometimes I should engage my brain before replying. Sorry, Steven. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 14: 6:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A334D151C1; Wed, 8 Dec 1999 14:06:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA43590; Wed, 8 Dec 1999 14:06:14 -0800 (PST) (envelope-from dillon) Date: Wed, 8 Dec 1999 14:06:14 -0800 (PST) From: Matthew Dillon Message-Id: <199912082206.OAA43590@apollo.backplane.com> To: Brad Knowles Cc: Joe Greco , mike@sentex.net (Mike Tancsa), jdp@polstra.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Route table leaks References: <199912081926.NAA80612@aurora.sol.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :At 1:26 PM -0600 1999/12/8, Joe Greco wrote: : :>> vmstat -m | grep routetbl|grep K :> routetbl289178 40961K 40961K 40960K 435741 0 0 :>16,32,64,128,256 :>> netstat -rn | wc -l :> 16 Please use 'netstat -rna' to get a listing of *all* the routes, including the temporary ones, not just the non-temporary routes. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 14:12:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 4EA7615610; Wed, 8 Dec 1999 14:12:10 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 1C6E41C4A; Wed, 8 Dec 1999 17:12:08 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 18E14381B; Wed, 8 Dec 1999 17:12:08 -0500 (EST) Date: Wed, 8 Dec 1999 17:12:08 -0500 (EST) From: Bill Fumerola To: Soren Schmidt Cc: Julian Elischer , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912081721.SAA70567@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Dec 1999, Soren Schmidt wrote: > The same thing is about to apply to the woxware sound code, we have a > new shiny system that works and is much better designed... For some definitions of "works". -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 14:26:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 58A5315201 for ; Wed, 8 Dec 1999 14:26:50 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA30816; Wed, 8 Dec 1999 23:02:17 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA36023; Wed, 8 Dec 1999 22:15:32 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912082115.WAA36023@yedi.iaf.nl> Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" In-Reply-To: <19991208152538.43637@mojave.sitaranetworks.com> from Greg Lehey at "Dec 8, 1999 3:25:38 pm" To: grog@lemis.com Date: Wed, 8 Dec 1999 22:15:32 +0100 (CET) Cc: kfarmer@sympatico.ca, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Greg Lehey wrote ... > On Monday, 6 December 1999 at 15:07:21 -0500, Kelvin Farmer wrote: > > > > Problem: Computer _sometimes_ stops after the "Mounting root from > > ufs:/dev/ad0s2a" line. > > Running Current, built world yesterday. (Problem appeared fairly > > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) > > > > dmesg: > > [...] > > ad0: ATA-3 disk at ata0 as master > > ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > > ad0: 16 secs/int, 1 depth queue, DMA > > acd0: CDROM drive at ata1 as master > > acd0: read 1378KB/s (1378KB/s), 128KB buffer, PIO > > acd0: supported read types: CD-R, CD-DA > > acd0: Audio: play, 256 volume levels > > acd0: Mechanism: ejectable tray > > acd0: Medium: no/blank disc inside, unlocked > > Mounting root from ufs:/dev/ad0s2a > > It's difficult to mount your root if there's no disk in the drive. No disc in what drive? ad0 clearly is a ;-) -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 14:30:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 6961215569; Wed, 8 Dec 1999 14:29:51 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA01850; Wed, 8 Dec 1999 17:29:19 -0500 (EST) Message-ID: <19991208172918.A1282@netmonger.net> Date: Wed, 8 Dec 1999 17:29:19 -0500 From: Christopher Masto To: Soren Schmidt Cc: Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! References: <19991208150807.A16687@netmonger.net> <199912082131.WAA31612@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199912082131.WAA31612@freebsd.dk>; from Soren Schmidt on Wed, Dec 08, 1999 at 10:31:22PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 08, 1999 at 10:31:22PM +0100, Soren Schmidt wrote: > Hmm, well, if you want support for any of the new ata-66 controllers > you have to use the ata driver, so you loose some you win some. > Given that my patch for the SiS works and a patch I got from Luoqi, > the ONLY support you are loosing is the Cyrix. Personally, I've been using the new ata driver since it was first announced and haven't had any problems with it. But it appeared that a bunch of people piped up with various reasons they couldn't use it, so it seemed that it's a bit premature to delete wd entirely. > Well, progress doesn't come for free you know, somebody has to do the > hard work of actually implementing things. So if you think its going > too slowly, do something about it, help out where you can, but complaining > isn't helping anybody :) I'm not complaining. My remarks were not intended as an attack or complaint. I just think that it is a bad idea to completely delete the old driver while there are still a reasonable number of people who can't use the new one. As I said, I think it should have become the default a long time ago, so these people would have been somewhat more likely to have shown up before crunch time. I would love to do nothing more than help out with FreeBSD, but like almost all of us, my available time is limited. I have contributed my comments, bug reports, and occasional bits and pieces of code. This particular message should be interpreted more as a suggestion that new systems be made the default sooner in -current in order to get wider testing, but at the same time, the old system should be left as an option until that testing indicates it's safe for it to go away. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 14:37:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 864EF152AD; Wed, 8 Dec 1999 14:37:25 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id QAA94094; Wed, 8 Dec 1999 16:37:04 -0600 (CST) From: Joe Greco Message-Id: <199912082237.QAA94094@aurora.sol.net> Subject: Re: Route table leaks In-Reply-To: <199912082206.OAA43590@apollo.backplane.com> from Matthew Dillon at "Dec 8, 1999 2: 6:14 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 8 Dec 1999 16:37:04 -0600 (CST) Cc: blk@skynet.be, jgreco@ns.sol.net, mike@sentex.net, jdp@polstra.com, stable@FreeBSD.ORG, 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 > > : > :At 1:26 PM -0600 1999/12/8, Joe Greco wrote: > : > :>> vmstat -m | grep routetbl|grep K > :> routetbl289178 40961K 40961K 40960K 435741 0 0 > :>16,32,64,128,256 > :>> netstat -rn | wc -l > :> 16 > > Please use 'netstat -rna' to get a listing of *all* the routes, including > the temporary ones, not just the non-temporary routes. > > -Matt > netstat -rna |wc -l 17 > netstat -rn | wc -l 16 > arp -an |wc -l 0 (yes, really) I'm not sure a more recent box would be different. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 14:43:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D516F1520F; Wed, 8 Dec 1999 14:43:21 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA39479; Wed, 8 Dec 1999 14:43:20 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA11413; Wed, 8 Dec 1999 14:43:20 -0800 (PST) (envelope-from obrien) Date: Wed, 8 Dec 1999 14:43:20 -0800 From: "David O'Brien" To: Steve Kargl Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: Reaping error(1) Message-ID: <19991208144320.A11395@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199912082010.MAA40896@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912082010.MAA40896@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Wed, Dec 08, 1999 at 12:10:26PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 08, 1999 at 12:10:26PM -0800, Steve Kargl wrote: > It should be noted that both fsplit and fpr apply to legacy > Fortran 77 code (and older). Neither utility can deal with > Fortran 90 or Fortran 95. But that [Fortran 77] is all our fortran compiler supports. :) -- -- David (obrien@NUXI.com) P.S. no I'm not aruging to deleting them. If they are deleted, they should be turned into ports. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 14:43:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 5FC7715267 for ; Wed, 8 Dec 1999 14:43:46 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id XAA19500 for freebsd-current@FreeBSD.ORG; Wed, 8 Dec 1999 23:43:42 +0100 (CET) (envelope-from olli) Date: Wed, 8 Dec 1999 23:43:42 +0100 (CET) From: Oliver Fromme Message-Id: <199912082243.XAA19500@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: Memory leak in syscons? Organization: Administration TU Clausthal Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Replying to myself...) In list.freebsd-current I wrote (8 Dec 1999 10:02:39 +0100): > I'm not 100% sure, but I think I have found a memory leak in > syscons. The following patch should fix it. Would someone > please have a look at this? --> kern/15363 Regards Oliver PS: I have more patches for syscons, they will follow shortly... :) -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 14:43:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailhotel.chrillesen.dk (vax.chrillesen.dk [193.88.12.35]) by hub.freebsd.org (Postfix) with ESMTP id 779B915274; Wed, 8 Dec 1999 14:43:38 -0800 (PST) (envelope-from barry@NetScum.dK) Received: by mailhotel.chrillesen.dk (Postfix, from userid 1009) id 03F52B780; Wed, 8 Dec 1999 23:43:31 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mailhotel.chrillesen.dk (Postfix) with ESMTP id 8F7CAB77F; Wed, 8 Dec 1999 23:43:31 +0100 (CET) Date: Wed, 8 Dec 1999 23:43:31 +0100 (CET) From: Anonymous Coward X-Sender: barry@vax.chrillesen.dk Reply-To: luserboy@netscum.dk To: current@freebsd.org, stable@freebsd.org Subject: Console mouse cut'n'paste sometimes is ... well... Message-ID: 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 Hellø¸ ãll ýøu kewl hãcker ð00ðZ! Mãý Ï reþørt this ãs ã bug¸ ør wøulð ýøu ãgree thãt this is better ðescribeð ãs ãn unðøcumenteð Feãture? Ýesterðãý´s instãll fløþþies øf -STÃBLË ãnð -©Û®®ËNT... Ï think this line in /etc/rc.cønf is the þrøblem: scrnmãþ=¨isø-8859-¹_tø_cþ4³7¨ Ï´m nøt cømþlãining¸ Ï ÃM ³L³³T¸ ÞHËî M˸ ØKÃÝ? bãrrý bøuwsmã (use reþlý-tø heãðer før ãný such) --  >cliþ< es¹: <ÃuðiøÞ©Ï ËS¹³70> rev 0x0¹ int ã irq 9 øn þci0.8.0 þcm¹: using Ï/Ø sþãce register mãþþing ãt 0x¹000 es2: <ÃuðiøÞ©Ï ËS¹³7¹> rev 0x06 int ã irq ¹5 øn þci0.9.0 þcm2: using Ï/Ø sþãce register mãþþing ãt 0x¹080 es¹³7¹: cøðec venðør T®Ã revisiøn ³ es¹³7¹: cøðec feãtures Bãss & Treble es¹³7¹: stereø enhãncement: nø ³à stereø enhãncement vgã0: <©irrus Løgic Gà5446 SVGàcøntrøller> rev 0x45 øn þci0.¹³.0 Þrøbing før ðevices øn Þ©Ï bus ¹: fxþ0: <Ïntel ËtherËxþress Þrø ¹0/¹00B Ëthernet> rev 0x05 int ã irq ¹¹ øn þci¹.³. 0 fxþ0: Ëthernet ãððress 00:90:27:³ð:³5:8e ncr0:  rev 0x0¹ int ã irq ¹0 øn þci¹.4.0 Þrøbing før ÞnÞ ðevices: Þrøbing før ðevices øn the ÏSàbus: sc0 øn isã sc0: VGàcølør <¹2 virtuãl cønsøles¸ flãgs=0x0> ãtkbðc0 ãt 0x60-0x6f øn møtherbøãrð ãtkbð0 irq ¹ øn isã þsm0 irq ¹2 øn isã >©LÏÞ< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 14:54:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5D7DF15258 for ; Wed, 8 Dec 1999 14:54:48 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA39555 for ; Wed, 8 Dec 1999 14:54:47 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA11503 for current@FreeBSD.ORG; Wed, 8 Dec 1999 14:54:47 -0800 (PST) (envelope-from obrien) Date: Wed, 8 Dec 1999 14:54:46 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991208145446.B11395@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991208150807.A16687@netmonger.net> <199912082052.MAA00517@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912082052.MAA00517@mass.cdrom.com>; from msmith@freebsd.org on Wed, Dec 08, 1999 at 12:52:37PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 08, 1999 at 12:52:37PM -0800, Mike Smith wrote: > > We haven't "lost" the pccard system at all I've lost the ability to use a 3c574 10/100 card (panics), the Xircom `xe' card (will not attach), the `ep' driver now has ultra shitty performance (132.05 KB/sec) where it seems to only be working due to the watch dog timer. At least PCCARD `ed' is currently working, and at 1111.88 KB/sec sustained. Suspend? We won't even go there. -- -- David (obrien@NUXI.com) P.S. I'm not trying to cut down Warner, but I do think we really need to focus on regaining support for things we've lost in the past 6 months. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 15: 1: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 32D5515264 for ; Wed, 8 Dec 1999 15:01:01 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA39638; Wed, 8 Dec 1999 15:01:00 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA11533; Wed, 8 Dec 1999 15:00:59 -0800 (PST) (envelope-from obrien) Date: Wed, 8 Dec 1999 15:00:59 -0800 From: "David O'Brien" To: Michael Chin-Yuan Wu Cc: current@freebsd.org Subject: Re: 3.3-stable -> 4.0-current problem... Message-ID: <19991208150059.C11395@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <19991207072658.D59056@dragon.nuxi.com> <384D776D.9127AAB5@mail.utexas.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <384D776D.9127AAB5@mail.utexas.edu>; from keichii@mail.utexas.edu on Tue, Dec 07, 1999 at 09:09:01PM +0000 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 07, 1999 at 09:09:01PM +0000, Michael Chin-Yuan Wu wrote: > > All they need is a simple pointer, Feh. What do you think /usr/src/UPDATING is? > why not be a bit nicer? :) I was the first 20 times things like this came up. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 15: 5:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 5F871150C6; Wed, 8 Dec 1999 15:05:01 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id SAA03842; Wed, 8 Dec 1999 18:04:57 -0500 (EST) Message-ID: <19991208180457.B1282@netmonger.net> Date: Wed, 8 Dec 1999 18:04:57 -0500 From: Christopher Masto To: Mike Smith Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! References: <19991208150807.A16687@netmonger.net> <199912082052.MAA00517@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199912082052.MAA00517@mass.cdrom.com>; from Mike Smith on Wed, Dec 08, 1999 at 12:52:37PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 08, 1999 at 12:52:37PM -0800, Mike Smith wrote: > > Unfortunately, FreeBSD has far too many examples of a working system > > being replaced with a less functional system. Just off the top of my > > head, there were the SCSI drivers lost to CAM, the PCCARD system, > > sound drivers, and now ATA. > > Actually, most of this is histrionics. CAM didn't lose us SCSI drivers; > we actually _gained_ from it. We gained quite a bit from it, but let's not rewrite history. I remember quite clearly that there was a very popular Adaptec SCSI controller missing when the switch to CAM was made, and a lot of people were inconvenienced. That is a matter of recorded historical fact. Please don't misinterpret me; I am not suggesting that CAM shouldn't have happened, that anyone did anything wrong or that it should have been handled differently. I am merely pointing out that "CAM didn't lose us SCSI drivers" is inaccurate. > We haven't "lost" the pccard system at all Again, this is not accurate. I have a laptop with which, two months ago, I could use my LinkSys ethernet card, and I could use my digital camera's compact flash adapter. I could eject them and put them back in numerous times. I could suspend and resume. Due to some changes in the pccard system, I can no longer do these things. Due to some more recent changes, I can't even use my wireless IP card at all. So it is a simple matter of fact that functionality has been lost. Of course it is only temporary. Once again, I ask that you don't misinterpret this simple statement of fact as a complaint or attack. Warner's pccard work was desperately needed and I am confident that eventually everything will be back and better than ever. And I am not only willing, but happy to deal with these problems that I have brought upon myself by choosing to run -current on my laptop. > and the new sound code is on a feature-par with both of the old ones. When it works, it works very well. But again, the fact is that I had sound on this computer three years ago. I had sound a few weeks ago. Then I didn't. Then it came back. Now it's gone again. It'll probably come back next time I build a kernel (I have an AWE64). But the fact is that something WAS lost: $ cat > /dev/audio zsh: device not configured: /dev/audio > What we need here is a commitment to these new initiatives, not a lot of > fence-sitting and clutching our knitting to our chests. All of these > initiatives were started to deal with massive problems in the subsystems > they replace; clinging to the old code rather than getting on-board and > helping with the new code directly impedes the resolution of these > problems. > > Again, I say, think of what we're trying to achieve here. I fully agree that these things are neccessary and good. I just think we need avoid jumping the gun on removing the old code, when some people still need it to boot their machines. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 15:13:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 0B4771522C for ; Wed, 8 Dec 1999 15:13:16 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup2-40.iptelecom.net.ua [212.9.226.104]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id BAA13577; Thu, 9 Dec 1999 01:16:57 +0200 (EET) Message-ID: <384EE5DF.A55D2E3C@altavista.net> Date: Thu, 09 Dec 1999 01:12:31 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Kelvin Farmer Cc: freebsd-current@FreeBSD.ORG Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" References: <384C1779.C3010AFA@sympatico.ca> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kelvin Farmer wrote: > Problem: Computer _sometimes_ stops after the "Mounting root from > ufs:/dev/ad0s2a" line. > Running Current, built world yesterday. (Problem appeared fairly > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) I've also observed this problem and it is interesting that my HDD is Quantum FB ST 2.1 too. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 15:20:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 0CA9F152B3; Wed, 8 Dec 1999 15:20:06 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup2-40.iptelecom.net.ua [212.9.226.104]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id BAA14089; Thu, 9 Dec 1999 01:23:47 +0200 (EET) Message-ID: <384EE77A.FC42FD9@altavista.net> Date: Thu, 09 Dec 1999 01:19:22 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Julian Elischer Cc: Soren Schmidt , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > because it doesn't support the chipsets that the old one does. > (namely the 200 or so lines of support in pci_ide.c needed for the Cyrix > GXM series). > > You shouldn't remove a function until it has been properly replaced. > A very simple concept some people seem to have trouble grasping. > > On Wed, 8 Dec 1999, Soren Schmidt wrote: > > > It seems Julian Elischer wrote: > > > > > please do not remove it.. > > > > And why is that ?? There is no point in having done a new one then, and > > you guys have known I've been working on this for ages so this cannot > > come as a surprise to anybody... > > > > The same thing is about to apply to the woxware sound code, we have a > > new shiny system that works and is much better designed... > > > > -Søren > > Excuse me for possible off-topic, but I have what is seems for me fresh idea about this question. Why do not remove from wd driver support for chipsets already implemented/tested in ata driver? Thus both clans would satisfied i.e. users with unsupported by ata chips still will have a chance, while all other will be encouraged to use and test better (IMHO) ata... Eventually at some day when all wd functionality will be in ata you could remove it and nobody will complain/dissatisfied. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 15:23:50 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id A244B1558B; Wed, 8 Dec 1999 15:23:49 -0800 (PST) From: "Jonathan M. Bresler" To: chris@netmonger.net Cc: msmith@FreeBSD.ORG, julian@whistle.com, current@FreeBSD.ORG In-reply-to: <19991208180457.B1282@netmonger.net> (message from Christopher Masto on Wed, 8 Dec 1999 18:04:57 -0500) Subject: Re: HEADSUP: wd driver will be retired! Message-Id: <19991208232349.A244B1558B@hub.freebsd.org> Date: Wed, 8 Dec 1999 15:23:49 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snip] > We gained quite a bit from it, but let's not rewrite history. I > remember quite clearly that there was a very popular Adaptec SCSI > controller missing when the switch to CAM was made, and a lot of [snip] we lost teh aic controller at that time. [snip] > Again, this is not accurate. I have a laptop with which, two months > ago, I could use my LinkSys ethernet card, and I could use my digital then we need to get your LinkSys ethernet card support fixed. i am using one to write this message. mine is a LinkSys 10/100 PCMCIA card. what do you have? [snip] jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 15:26: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id A10CE15287 for ; Wed, 8 Dec 1999 15:25:54 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA67732 for ; Wed, 8 Dec 1999 18:26:38 -0500 (EST) (envelope-from bsdx@looksharp.net) Date: Wed, 8 Dec 1999 18:26:38 -0500 (EST) From: Adam To: current@freebsd.org Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" In-Reply-To: <384EE5DF.A55D2E3C@altavista.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 think I've seen the same thing with ad0: ATA-4 disk at ata0 as master ad0: 16124MB (33022080 sectors), 32760 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 But I dont reboot frequently enough to have it phase me.. On Thu, 9 Dec 1999, Maxim Sobolev wrote: >Kelvin Farmer wrote: > >> Problem: Computer _sometimes_ stops after the "Mounting root from >> ufs:/dev/ad0s2a" line. >> Running Current, built world yesterday. (Problem appeared fairly >> recently (as in ~2 weeks?, but didn't have ddb in previous kernel) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 15:36:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 1DA181523F; Wed, 8 Dec 1999 15:36:45 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA67799; Wed, 8 Dec 1999 18:37:29 -0500 (EST) (envelope-from bsdx@looksharp.net) Date: Wed, 8 Dec 1999 18:37:29 -0500 (EST) From: Adam To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: 3.3-stable -> 4.0-current problem... In-Reply-To: <19991208150059.C11395@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sounds like its time to hack cvsup to display a diff of UPDATING from before and after cvsup. If it actually happened I dont think people would mind because the average change is only a dozen lines or less it would coincide with the amount of output cvsup would show for someone who frequently cvsups, and if you are doing a big cvsup you expect copious output anyway. My $0.02 -- Adam On Wed, 8 Dec 1999, David O'Brien wrote: >On Tue, Dec 07, 1999 at 09:09:01PM +0000, Michael Chin-Yuan Wu wrote: >> >> All they need is a simple pointer, > >Feh. What do you think /usr/src/UPDATING is? > >> why not be a bit nicer? :) > >I was the first 20 times things like this came up. > >-- >-- David (obrien@NUXI.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 Wed Dec 8 15:45:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 06B5514F55; Wed, 8 Dec 1999 15:45:44 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA68537; Wed, 8 Dec 1999 15:45:40 -0800 (PST) Date: Wed, 8 Dec 1999 15:45:39 -0800 (PST) From: Julian Elischer To: "Jonathan M. Bresler" Cc: chris@netmonger.net, msmith@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991208232349.A244B1558B@hub.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 On Wed, 8 Dec 1999, Jonathan M. Bresler wrote: > > [snip] > > We gained quite a bit from it, but let's not rewrite history. I > > remember quite clearly that there was a very popular Adaptec SCSI > > controller missing when the switch to CAM was made, and a lot of > [snip] > more importantly we lost the aha driver for a while. > we lost teh aic controller at that time. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 15:51:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from stingray.ivision.co.uk (avengers.ivision.co.uk [195.50.91.40]) by hub.freebsd.org (Postfix) with ESMTP id 4A2AB152EF; Wed, 8 Dec 1999 15:51:39 -0800 (PST) (envelope-from jasper@ivision.co.uk) Received: from stingray.ivision.co.uk ([195.50.91.40]) by stingray.ivision.co.uk with esmtp (Exim 2.04 #1) id 11vqpC-00055N-00; Wed, 8 Dec 1999 23:48:46 +0000 Date: Wed, 8 Dec 1999 23:48:45 +0000 (BST) From: Jasper Wallace To: Joe Greco Cc: Matthew Dillon , blk@skynet.be, mike@sentex.net, jdp@polstra.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Route table leaks In-Reply-To: <199912082237.QAA94094@aurora.sol.net> Message-ID: X-NCC-RegID: uk.instant-web 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, 8 Dec 1999, Joe Greco wrote: > > > > : > > :At 1:26 PM -0600 1999/12/8, Joe Greco wrote: > > : > > :>> vmstat -m | grep routetbl|grep K > > :> routetbl289178 40961K 40961K 40960K 435741 0 0 > > :>16,32,64,128,256 > > :>> netstat -rn | wc -l > > :> 16 > > > > Please use 'netstat -rna' to get a listing of *all* the routes, including > > the temporary ones, not just the non-temporary routes. > > > > -Matt > > > netstat -rna |wc -l > 17 > > netstat -rn | wc -l > 16 > > arp -an |wc -l > 0 quite heavily loaded web server: # netstat -ran | wc -l 106 (that was 177 a few mins ago). # vmstat -m | grep routetbl|grep K routetbl 228 32K 649K 19661K 1120980 0 0 16,32,64,128,256 # uname -r 2.2.2-RELEASE # uptime 11:55PM up 23 days, 12:31, 1 user, load averages: 0.04, 0.03, 0.00 # Slightly more atomic mesurament: # netstat -ran | wc -l ; vmstat -m | grep routetbl | grep '[0-9]K' 175 routetbl 354 49K 649K 19661K 1121106 0 0 16,32,64,128,256 -- Internet Vision Internet Consultancy Tel: 0171 589 4500 60 Albert Court & Web development Fax: 0171 589 4522 Prince Consort Road vision@ivision.co.uk London SW7 2BE http://www.ivision.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 16: 3:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 435941556D; Wed, 8 Dec 1999 16:03:49 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA35029; Wed, 8 Dec 1999 17:03:43 -0700 (MST) (envelope-from ken) Message-Id: <199912090003.RAA35029@panzer.kdm.org> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: from Julian Elischer at "Dec 8, 1999 03:45:39 pm" To: julian@whistle.com (Julian Elischer) Date: Wed, 8 Dec 1999 17:03:43 -0700 (MST) Cc: jmb@hub.freebsd.org (Jonathan M. Bresler), chris@netmonger.net, msmith@FreeBSD.ORG, current@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote... > > > On Wed, 8 Dec 1999, Jonathan M. Bresler wrote: > > > > > [snip] > > > We gained quite a bit from it, but let's not rewrite history. I > > > remember quite clearly that there was a very popular Adaptec SCSI > > > controller missing when the switch to CAM was made, and a lot of > > [snip] > > > > more importantly we lost the aha driver for a while. Uhh, no. The aha driver went into -current along with the rest of CAM: revision 1.1 date: 1998/09/15 07:39:52; author: gibbs; state: Exp; Adaptec 154X SCSI-Host Adapter driver for CAM. Submitted by: Warner Losh > > we lost teh aic controller at that time. > > Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 16:45:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id B2115152DA; Wed, 8 Dec 1999 16:45:07 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id QAA42192; Wed, 8 Dec 1999 16:45:16 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199912090045.QAA42192@troutmask.apl.washington.edu> Subject: Re: Reaping error(1) In-Reply-To: <19991208144320.A11395@dragon.nuxi.com> from "David O'Brien" at "Dec 8, 1999 02:43:20 pm" To: obrien@FreeBSD.ORG Date: Wed, 8 Dec 1999 16:45:16 -0800 (PST) Cc: kris@hub.freebsd.org (Kris Kennaway), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > On Wed, Dec 08, 1999 at 12:10:26PM -0800, Steve Kargl wrote: > > It should be noted that both fsplit and fpr apply to legacy > > Fortran 77 code (and older). Neither utility can deal with > > Fortran 90 or Fortran 95. > > But that [Fortran 77] is all our fortran compiler supports. :) > Yeah, I know ;-) On the other hand, some people in comp.lang.fortran are discussing whether g95 is feasible. Don't worry David, you won't have to import g95 for several years. ;-0 -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 17: 0:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from manchaca.ece.utexas.edu (manchaca.ece.utexas.edu [128.83.59.38]) by hub.freebsd.org (Postfix) with ESMTP id BEA90151D9 for ; Wed, 8 Dec 1999 17:00:18 -0800 (PST) (envelope-from mwu@tick.ece.utexas.edu) Received: from tick.ece.utexas.edu (tick.ece.utexas.edu [128.83.59.31]) by manchaca.ece.utexas.edu (8.9.3/8.9.0) with SMTP id SAA03907 for ; Wed, 8 Dec 1999 18:59:10 -0600 (CST) Date: Wed, 8 Dec 1999 19:00:16 -0600 (CST) From: Michael Chin-yuan Wu To: freebsd-current@freebsd.org Subject: Re: Cannot mount cd9660 Message-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 dont know if this showed up on the list, the relay host I used was down Trying to clear my name :) Keith Jang wrote: Michael Chin-Yuan Wu wrote: > > P.S. I did a patch for cd9660 and patch for reading Chinese filenames > > > [patch is in attachment] [...] > > chinese_joliet.patch.for_3.2-19990615.gz Type: application/x-gzip > > chinese_vfat-3.0.patch.gz Type: application/x-gzip > Come on, these patches have been available at > ftp://freebsd.csie.nctu.edu.tw/pub/taiwan/CSIE/kernel_patch/ > since 2.2.7, and the author is mills.bbs@bbs.iim.nctu.edu.tw. > Now you just rip it off and claim that's your work? I didn't take credit for this. :) Sorry if I didnt make myself clear. If you will look at my email again, > P.S. I did a patch for cd9660 and patch for reading Chinese filenames > [patch is in attachment] > =========uname -a============ > FreeBSD keichii.internal.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0 > 8:09 CST 1999 keichii@keichii.internal.org:/usr/current/src > .ATA i386 > ===============dmesg========= > as attachment > =============kernel========= > as attachment > ============patches for chinese filesystems====== > as attachment > ============================== The ======= lined parts are all information meant to help people debug/understand my problem. The "p.s." part was also meant to help solve the problem. Sorry for not making myself clear. What I meant was, "I applied the patches to the sources, which may have caused the cdrom to not mount" Apologies for bad English usage and causing the confusion. [Doing/did a patch can mean two things in English A. to write the patch B. to patch the source with the I know that A is usually the default definition, but it was 3am in the morning when I wrote that email. I apologize. > -- Many humble apologies, Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 18:35:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-89.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.217]) by hub.freebsd.org (Postfix) with ESMTP id E28B714C03; Wed, 8 Dec 1999 18:35:44 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA00387; Thu, 9 Dec 1999 02:35:38 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA01369; Thu, 9 Dec 1999 02:27:09 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912090227.CAA01369@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Julian Elischer Cc: "Jonathan M. Bresler" , chris@netmonger.net, msmith@FreeBSD.ORG, current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: Message from Julian Elischer of "Wed, 08 Dec 1999 15:45:39 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Dec 1999 02:27:09 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 8 Dec 1999, Jonathan M. Bresler wrote: > > > > > [snip] > > > We gained quite a bit from it, but let's not rewrite history. I > > > remember quite clearly that there was a very popular Adaptec SCSI > > > controller missing when the switch to CAM was made, and a lot of > > [snip] > > > > more importantly we lost the aha driver for a while. > > > we lost teh aic controller at that time. Touche ! I've got my back end machine here (gate), the only machine I can test the new-busified i4b software on, I've got an aha0 driver that says ``aha0: status reg test failed ff'' stopping me from seeing /home, /var and /usr/local, I've got a failing 1.2Gb IDE boot disk (I have to physically kick the machine a few times now and again to make it recover), I've got a second IDE disk that actually functions and a third that locks up the ata driver on probe (I only found this out when I changed the IDE controller in this machine about 2 weeks ago to defeat some dodgy memory/cache). I've got a new 28Gb disk on the floor that I'd like to replace the boot disk with if I could just get a current build - but the last -current with a working ata driver is from the 5th. I just hope that the ata lockup was due to an i/o conflict with the ISDN card that has now been fixed, but I have no chance of testing this in ``the next few days''. I have no problem with ata becoming standard. I have a big problem with wd being removed. I see no good reason for not leaving it there. If people want to tear working code out of the system, at least give us some notice ! -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 18:40:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id A927A15148 for ; Wed, 8 Dec 1999 18:40:04 -0800 (PST) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 2.12 #1) id 11vtUi-00088U-00; Thu, 9 Dec 1999 08:39:48 +0600 Date: Thu, 9 Dec 1999 08:39:46 +0600 (ALMT) From: Boris Popov To: Kelvin Farmer Cc: freebsd-current@freebsd.org Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" In-Reply-To: <384C1779.C3010AFA@sympatico.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 6 Dec 1999, Kelvin Farmer wrote: > Problem: Computer _sometimes_ stops after the "Mounting root from > ufs:/dev/ad0s2a" line. > Running Current, built world yesterday. (Problem appeared fairly > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) I can confirm that behaviour of new ata driver. This happens one time per 5-6 reboots. In addition, machines with VIA chipset work fine, but all machines with i440BX chipset suffer from this problem: pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 16 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ad0: ATA-4 disk at ata0 as master ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: ATA-4 disk at ata1 as master ad1: 12949MB (26520480 sectors), 26310 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 32 depth queue, UDMA33 -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 18:51: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 76A49152C8 for ; Wed, 8 Dec 1999 18:51:01 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id UAA34219; Wed, 8 Dec 1999 20:50:55 -0600 (CST) (envelope-from dick) Date: Wed, 8 Dec 1999 20:50:55 -0600 From: "Richard Seaman, Jr." To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: SiS ata Driver (was Re: HEADSUP: wd driver will be retired!) Message-ID: <19991208205054.A34152@tar.com> References: <19991208072728.K44207@tar.com> <199912081402.PAA23215@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912081402.PAA23215@freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 08, 1999 at 03:02:37PM +0100, Soren Schmidt wrote: > OK, you asked for it, following is a patch to support the > sis 5591 chipset. Remember this is done blindfolded, I > have no HW to test on, but you guys do :) Seems to work. I'll let it run for a few days, but I'd guess it is fine. Dec 8 17:25:02 test /kernel: pcib0: on motherboard Dec 8 17:25:02 test /kernel: pci0: on pcib0 Dec 8 17:25:02 test /kernel: ata-pci0: irq 14 at device 0.1 on pci0 Dec 8 17:25:02 test /kernel: ata-pci0: Busmastering DMA supported Dec 8 17:25:02 test /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Dec 8 17:25:02 test /kernel: ata1 at 0x0170 irq 15 on ata-pci0 Dec 8 17:25:02 test /kernel: isab0: at device 1.0 on pci0 Dec 8 17:25:02 test /kernel: isa0: on isab0 Dec 8 17:25:02 test /kernel: pci0: unknown card (vendor=0x1039, dev=0x0009) at 1.1 Dec 8 17:25:02 test /kernel: pcib2: at device 2.0 on pci0 Dec 8 17:25:02 test /kernel: pci1: on pcib2 Dec 8 17:25:02 test /kernel: vga-pci0: irq 11 at device 0.0 on pci1 Dec 8 17:25:02 test /kernel: fxp0: irq 9 at device 11.0 on pci0 Dec 8 17:25:02 test /kernel: fxp0: Ethernet address 00:a0:c9:b1:23:ae Dec 8 17:25:02 test /kernel: devclass_alloc_unit: pci1 already exists, using next available unit number Dec 8 17:25:02 test /kernel: pcib1: on motherboard Dec 8 17:25:02 test /kernel: pci2: on pcib1 Dec 8 17:25:02 test /kernel: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 Dec 8 17:25:02 test /kernel: fdc0: FIFO enabled, 8 bytes threshold Dec 8 17:25:02 test /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Dec 8 17:25:02 test /kernel: ata-isa0: already registered as ata0 Dec 8 17:25:02 test /kernel: ata-isa1: already registered as ata1 [snip] Dec 8 17:25:02 test /kernel: ad0: ATA-4 disk at ata0 as master Dec 8 17:25:02 test /kernel: ad0: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S Dec 8 17:25:02 test /kernel: ad0: 16 secs/int, 32 depth queue, UDMA33 Dec 8 17:25:02 test /kernel: ad1: ATA-3 disk at ata0 as slave Dec 8 17:25:02 test /kernel: ad1: 4884MB (10003392 sectors), 9924 cyls, 16 heads, 63 S/T, 512 B/S Dec 8 17:25:02 test /kernel: ad1: 16 secs/int, 1 depth queue, DMA Dec 8 17:25:02 test /kernel: ad2: ATA-4 disk at ata1 as master Dec 8 17:25:02 test /kernel: ad2: 10991MB (22510656 sectors), 22332 cyls, 16 heads, 63 S/T, 512 B/S Dec 8 17:25:02 test /kernel: ad2: 16 secs/int, 1 depth queue, UDMA33 Dec 8 17:25:02 test /kernel: Mounting root from ufs:/dev/ad0s1a -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 19:25:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id C7336152FA; Wed, 8 Dec 1999 19:25:42 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with ESMTP id MAA09252; Thu, 9 Dec 1999 12:25:34 +0900 (JST) Date: Thu, 09 Dec 1999 12:25:33 +0900 Message-ID: <14415.8493.971538.78435L@rina.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: caa@columbus.rr.com Cc: msmith@FreeBSD.ORG, tanimura@r.dl.itc.u-tokyo.ac.jp, schuerge@wjpserver.CS.Uni-SB.DE, fn@radio-do.de, freebsd-current@FreeBSD.ORG Subject: Re: AWE64 problems In-Reply-To: In your message of "Wed, 8 Dec 1999 08:54:15 -0500" <19991208085415.A534@midgard.dhs.org> References: <19991208000746.A1622@midgard.dhs.org> <199912080513.VAA07525@mass.cdrom.com> <19991208085415.A534@midgard.dhs.org> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snipped some part] >> > > On Tue, 7 Dec 1999 23:00:02 +0100 (MET), >> > > Thomas Schuerger said: >> > > >> > > >> --- sbc.c.orig Mon Dec 6 19:26:31 1999 >> > > >> +++ sbc.c Tue Dec 7 22:15:25 1999 >> > > >> @@ -110,7 +110,7 @@ >> > > >> if (error) >> > > >> return error; >> > > >> else >> > > >> - return -100; >> > > >> + return -1; >> > > >> } >> > > >> >> > > >> static int On Wed, 8 Dec 1999 08:54:15 -0500, "Charles Anderson" said: Charles> So then what is -1 and why does it work when -100 doesn't? (I tried it) sys/kern/subr_bus.c:device_probe_child() receives the value returned by DEVICE_PROBE(child dev). If the value is zero, no further probes occur. The device then gets attached in sys/kern/subr_bus.c: device_probe_and_attach(). If the returned value is less than zero, device_probe_child() continues probing other possible drivers. For ISA devices, the unknown driver implemented in sys/isa/isa_common.c is always probed if no other drivers probe the device successfully. The DEVICE_PROBE() for any ISA devices with the unknown driver returns -100, so it is, say, the likelyhood of the unknown driver to the device. To say the truth, a driver other than the unknown might get to probe the device in this case, depending on the order to enumerate the possible drivers in device_probe_child() using {first,next}_matching_driver(). -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 19:36:35 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 8965414C5A; Wed, 8 Dec 1999 19:36:34 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7FC8D1CD738; Wed, 8 Dec 1999 19:36:34 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 8 Dec 1999 19:36:34 -0800 (PST) From: Kris Kennaway To: Steve Kargl Cc: current@FreeBSD.ORG Subject: Re: Reaping fortran cruft In-Reply-To: <199912082010.MAA40896@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, 8 Dec 1999, Steve Kargl wrote: > I was going to fix fsplit. Yes, I program in Fortran (note the > proper spelling of Fortran). No, I don't use fsplit. A rewrite is certainly desperately needed :) > We might also want to remove fpr(1). Noted. Are there any other crufty Fortran candidates you can do without? If no-one disagrees with this, I'll move them both to ports (probably in a combined fortran-utils port) in a couple of days. Would you like to be the maintainer? :) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 19:38:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from darkstar.qx.net (darkstar.qx.net [208.235.88.101]) by hub.freebsd.org (Postfix) with ESMTP id 3AF47152F1 for ; Wed, 8 Dec 1999 19:38:52 -0800 (PST) (envelope-from gchil0@pop.uky.edu) Received: from mail.qx.net (mail.qx.net [208.235.88.10]) by darkstar.qx.net (8.8.7/8.8.7) with ESMTP id WAA24439 for ; Wed, 8 Dec 1999 22:38:45 -0500 Received: from k7 ([208.200.111.57]) by mail.qx.net (Netscape Messaging Server 3.6) with ESMTP id AAA6886 for ; Wed, 8 Dec 1999 22:41:35 -0500 Message-Id: <4.2.0.58.19991208223719.00947450@pop.uky.edu> X-Sender: gchil0@pop.uky.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 08 Dec 1999 22:38:57 -0500 To: freebsd-current@freebsd.org From: Greg Childers Subject: ATA problem Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Seems now is the time to raise problems with ATA, so here goes. I have used the ATA driver since its introduction into -current without problem until recently. A kernel from October 5 worked fine. Now, it no longer works using ATA, but works fine using the old WD drivers. The console freezes after the dmesg and the keyboard is unresponsive. The ata info in MYKERNEL is a direct cut and paste from GENERIC. The motherboard is an Intel Premiere/PCI (Batman's Revenge). According to technical product summary, the primary IDE interface, on which both my drives reside, is a PCTech RZ1000 on the PCI local bus. The secondary IDE interface is a SMC 37C665 I/O controller on the ISA bus. Below is the relevant sections of a verbose dmesg. If there's any additional info I can provide to help diagnose thisproblem, please ask. Thanks, Greg ata-pci0: at device 1.0 on pci0 ata-pci0: Busmastering DMA not supported ata0: iobase=0x01f0 altiobase=0x03f4 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=50 ata0: devices = 0x3 ata0 at 0x01f0 irq 0 on ata-pci0 ata-isa0: already registered as ata0 BIOS Geometries: 0:020a1f3f 0..522=523 cylinders, 0..31=32 heads, 1..63=63 sectors 1:026b3f3f 0..619=620 cylinders, 0..63=64 heads, 1..63=63 sectors 0 accounted for Device configuration finished. device combination doesn't support shared irq0 intr_connect(irq0) failed, result=-1 ad0: piomode=3 dmamode=1 udmamode=-1 cblid=0 ad0: ATA-? disk at ata0 as master ad0: 515MB (1056384 sectors), 1048 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, PIO Creating DISK ad0 Creating DISK wd0 ad1: piomode=3 dmamode=1 udmamode=-1 cblid=0 ad1: ATA-? disk at ata0 as slave ad1: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, PIO Creating DISK ad1 Creating DISK wd1 Mounting root from ufs:wd0s1a wd0s1: type 0xa5, start 63, end = 1056383, size 1056321 : OK microuptime() went backwards (1.4342530 -> 1,047990) start_init: trying /sbin/init ad1s1: type 0xa5, start 63, end = 2503871, size 2503809 : OK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 19:39: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (deep-thought.demos.su [195.133.1.74]) by hub.freebsd.org (Postfix) with ESMTP id B3E9314C5A for ; Wed, 8 Dec 1999 19:38:56 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id GAA11967; Thu, 9 Dec 1999 06:38:46 +0300 (MSK) (envelope-from ache) Date: Thu, 9 Dec 1999 06:38:46 +0300 From: "Andrey A. Chernov" To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: Is there any way to use ATAPI CD-R? Message-ID: <19991209063845.A11949@nagual.pp.ru> References: <19991208211624.A6005@nagual.pp.ru> <199912082034.VAA17215@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912082034.VAA17215@freebsd.dk> Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 08, 1999 at 09:34:24PM +0100, Soren Schmidt wrote: > I use it every day, well almost :) > Look in /usr/share/examples/atapi... Thanks! Do you have a plan to merge ATAPI as part of SCSI (CAM) interface as NetBSD already does? It will solve problems with all SCSI-only CD* soft automatically. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 19:40:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 2212515316; Wed, 8 Dec 1999 19:40:18 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id WAA20299; Wed, 8 Dec 1999 22:40:16 -0500 (EST) Date: Wed, 8 Dec 1999 22:40:16 -0500 (EST) From: "Matthew N. Dodd" To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991208145446.B11395@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Dec 1999, David O'Brien wrote: > I've lost the ability to use a 3c574 10/100 card (panics), the Xircom > `xe' card (will not attach), the `ep' driver now has ultra shitty > performance (132.05 KB/sec) where it seems to only be working due to the > watch dog timer. I'll take the blame for the if_ep problems which are mostly related to the ifmedia changes I put into the driver. I can't explain the watchdog problem (someone reported it under -STABLE too so I'm not quite sure when the problem started.) but am working on it. 3com sent me more manuals and has a 3c574 in the mail for me. I'm working on getting my PCMCIA bridge card working and once I've got a usable test system for PCMCIA I'll have if_ep back into shape. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 20:26:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from set.spradley.org (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (Postfix) with ESMTP id 9F07214BFE; Wed, 8 Dec 1999 20:26:10 -0800 (PST) (envelope-from tsprad@set.spradley.org) Received: from set.spradley.org (localhost.spradley.tmi.net [127.0.0.1]) by set.spradley.org (8.9.3/8.9.2) with ESMTP id WAA33754; Wed, 8 Dec 1999 22:26:04 -0600 (CST) (envelope-from tsprad@set.spradley.org) Message-Id: <199912090426.WAA33754@set.spradley.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Route table leaks In-reply-to: Your message of "Wed, 08 Dec 1999 23:48:45 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Dec 1999 22:26:03 -0600 From: Ted Spradley Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Please use 'netstat -rna' to get a listing of *all* the routes, including > > > the temporary ones, not just the non-temporary routes. FWIW, another datapoint: set$ netstat -ran | wc -l 15 set$ vmstat -m | grep routetbl|grep K routetbl 35 5K 18K 26535K 511 0 0 16,32,64,128,256 set$ uname -a FreeBSD set.spradley.org 3.3-STABLE FreeBSD 3.3-STABLE #2: Wed Oct 6 19:10:52 CDT 1999 tsprad@set.spradley.tmi.net:/scratch/source/src/sys/ compile/Set i386 set$ uptime 10:21PM up 9 days, 3:24, 0 users, load averages: 0.05, 0.11, 0.06 This is my desktop at home, used for reading mail and surfing the web, no routed or gated, mostly idle. 26.5 Mbytes looks kinda high to me... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 20:59:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id B1A301559F; Wed, 8 Dec 1999 20:58:52 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id UAA01426; Wed, 8 Dec 1999 20:58:28 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912090458.UAA01426@gndrsh.dnsmgr.net> Subject: Re: Route table leaks In-Reply-To: <199912090426.WAA33754@set.spradley.org> from Ted Spradley at "Dec 8, 1999 10:26:03 pm" To: tsprad@set.spradley.org (Ted Spradley) Date: Wed, 8 Dec 1999 20:58:28 -0800 (PST) Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > Please use 'netstat -rna' to get a listing of *all* the routes, including > > > > the temporary ones, not just the non-temporary routes. > > FWIW, another datapoint: > > set$ netstat -ran | wc -l > 15 > set$ vmstat -m | grep routetbl|grep K Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) > routetbl 35 5K 18K 26535K 511 0 0 > 16,32,64,128,256 > set$ uname -a > FreeBSD set.spradley.org 3.3-STABLE FreeBSD 3.3-STABLE #2: Wed Oct 6 > 19:10:52 CDT 1999 tsprad@set.spradley.tmi.net:/scratch/source/src/sys/ > compile/Set i386 > set$ uptime > 10:21PM up 9 days, 3:24, 0 users, load averages: 0.05, 0.11, 0.06 > > > This is my desktop at home, used for reading mail and surfing the web, > no routed or gated, mostly idle. 26.5 Mbytes looks kinda high to me... Go back and read the headings of vmstat -m, your only using 5K for routes, the 26.5M is the limit on the vmspace. The 18K was the highest usage. So you look pretty normal at 5K/35 -> 146 bytes/route. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 21: 4:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 869571556D for ; Wed, 8 Dec 1999 21:04:28 -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.3/8.9.3) with ESMTP id VAA25510; Wed, 8 Dec 1999 21:04:24 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id VAA36946; Wed, 8 Dec 1999 21:04:24 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 8 Dec 1999 21:04:24 -0800 (PST) Message-Id: <199912090504.VAA36946@vashon.polstra.com> To: marcel@scc.nl Subject: Re: Cleaning house on /usr/src/* In-Reply-To: <384EA2CF.B3E40E35@scc.nl> References: <199912081718.JAA29021@vashon.polstra.com> <384EA2CF.B3E40E35@scc.nl> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <384EA2CF.B3E40E35@scc.nl>, Marcel Moolenaar wrote: > John Polstra wrote: > > > Why are you getting these junk directories? CVSup should be > > deleting them if they're empty. You really shouldn't need to > > wipe out your tree and start over -- not ever. Did you omit the > > "delete" keyword from your supfile? > > I recently (last week) cvsup'd a -current source tree over a -stable > source tree with the assumption that cvsup would sort it all out. I > found out that cvsup doesn't (always?) remove files that are no > longer pertinent. This is with the delete keyword present. When you change the tag (e.g., go from -stable to -current or vice versa), it's a special case. That's because the "checkouts" file (which CVSup uses to decide which files to delete) contains the tag as part of its name. In the future I may recommend omitting the "use-rel-suffix" option in order to avoid this problem. Meanwhile, the CVSup FAQ has some advice about it in questions 11-13: http://www.polstra.com/projects/freeware/CVSup/ If for whatever reason you do think you have some extra files, there's a script "cvsupchk" in the contrib subdirectory of the CVSup distribution which will find them for you and delete them. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 21:39:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.az.home.com (ha1.rdc1.az.home.com [24.1.240.66]) by hub.freebsd.org (Postfix) with ESMTP id 15F531532F for ; Wed, 8 Dec 1999 21:39:13 -0800 (PST) (envelope-from straka@home.com) Received: from home.com ([24.1.209.47]) by mail.rdc1.az.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19991209053907.SICP21794.mail.rdc1.az.home.com@home.com> for ; Wed, 8 Dec 1999 21:39:07 -0800 Message-ID: <384F407B.5484C354@home.com> Date: Wed, 08 Dec 1999 22:39:07 -0700 From: "Richard S. Straka" X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: ata vs wd driver performance Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have recently performed some testing on the ata and wd drivers on my system. When writing to and reading from a file on the same file system in the same directory, the ata driver appears to take almost double the CPU time as compared to the wd driver. However, when reading from the raw disk, the ata and wd driver take about the same amount of CPU time. DMA is enabled in both driver. Can someone explain why the ata driver is using more CPU? Rich Straka straka@home.com ********* wd driver results writing to a file. $ time dd if=/dev/zero of=test.dat bs=1024k count=256 256+0 records in 256+0 records out 268435456 bytes transferred in 41.810011 secs (6420363 bytes/sec) real 0m42.136s user 0m0.002s sys 0m19.939s ********* ata driver results writing to a file. $ time dd if=/dev/zero of=test.dat bs=1024k count=256 256+0 records in 256+0 records out 268435456 bytes transferred in 39.475358 secs (6800077 bytes/sec) real 0m39.750s user 0m0.008s sys 0m35.665s ******** wd driver results reading from a file. $ time dd if=test.dat of=/dev/null bs=1024k count=256 256+0 records in 256+0 records out 268435456 bytes transferred in 39.992958 secs (6712068 bytes/sec) real 0m40.040s user 0m0.025s sys 0m13.387s ******** ata driver results reading from a file. $ time dd if=test.dat of=/dev/null bs=1024k count=256 256+0 records in 256+0 records out 268435456 bytes transferred in 37.914618 secs (7079999 bytes/sec) real 0m37.944s user 0m0.009s sys 0m28.221s ******** wd results reading from raw disk. $ time dd if=/dev/rwd0 of=/dev/null bs=1024k count=256 256+0 records in 256+0 records out 268435456 bytes transferred in 33.100446 secs (8109723 bytes/sec) real 0m33.137s user 0m0.000s sys 0m0.266s ******** ata results reading from raw disk. $ time dd if=/dev/rwd0 of=/dev/null bs=1024k count=256 256+0 records in 256+0 records out 268435456 bytes transferred in 34.518500 secs (7776568 bytes/sec) real 0m34.535s user 0m0.000s sys 0m0.222s ******************************************************* dmesg with wd driver. ******************************************************* Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Sat Dec 4 09:22:58 MST 1999 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 333189478 Hz CPU: AMD-K6(tm) 3D processor (333.19-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bf AMD Features=0x80000800 real memory = 134152192 (131008K bytes) avail memory = 127021056 (124044K bytes) Preloaded elf kernel "kernel" at 0xc0303000. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 ide_pci0: at device 7.1 on pci0 chip1: at device 7.3 on pci0 sym0: <875> irq 10 at device 8.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, parity checking sym0: open drain IRQ line driver, using on-chip SRAM vga-pci0: at device 9.0 on pci0 fxp0: irq 12 at device 10.0 on pci0 fxp0: Ethernet address 00:a0:c9:27:fc:1d fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa008a008 on isa0 wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-8 wd0: 4134MB (8467200 sectors), 8400 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 flags 0xa008a008 on isa0 wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-8 wd2: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 1 (atapi): , removable, dma, iordy wcd0: drive speed 2062KB/sec, 240KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2 at port 0x3e8-0x3ef irq 5 on isa0 sio2: type 16550A ppc0 at port 0x378-0x37f irq 7 drq 3 on isa0 ppc0: Winbond chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pcm0: at port 0x530-0x53f irq 11 drq 1 flags 0xa610 on isa0 Waiting 8 seconds for SCSI devices to settle sym0: Downloading SCSI SCRIPTS. (noperiph:sym0:0:-1:-1): SCSI bus reset delivered. Mounting root from ufs:/dev/wd0s2a da0 at sym0 bus 0 target 3 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 2170MB (4445380 512 byte sectors: 255H 63S/T 276C) ******************************************************* dmesg with ata driver. ******************************************************* Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Wed Dec 8 22:13:02 MST 1999 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 333189391 Hz CPU: AMD-K6(tm) 3D processor (333.19-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bf AMD Features=0x80000800 real memory = 134152192 (131008K bytes) avail memory = 127029248 (124052K bytes) Preloaded elf kernel "kernel" at 0xc0301000. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: at device 7.3 on pci0 sym0: <875> irq 10 at device 8.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, parity checking sym0: open drain IRQ line driver, using on-chip SRAM vga-pci0: at device 9.0 on pci0 fxp0: irq 12 at device 10.0 on pci0 fxp0: Ethernet address 00:a0:c9:27:fc:1d fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2 at port 0x3e8-0x3ef irq 5 on isa0 sio2: type 16550A ppc0 at port 0x378-0x37f irq 7 drq 3 on isa0 ppc0: Winbond chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pcm0: at port 0x530-0x53f irq 11 drq 1 flags 0xa610 on isa0 ad0: ATA-3 disk at ata0 as master ad0: 4134MB (8467200 sectors), 8400 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, DMA ad1: ATA-3 disk at ata1 as master ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, DMA acd0: CDROM drive at ata1 as slave acd0: read 2062KB/s (2062KB/s), 240KB buffer, PIO acd0: supported read types: CD-R, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Waiting 8 seconds for SCSI devices to settle sym0: Downloading SCSI SCRIPTS. (noperiph:sym0:0:-1:-1): SCSI bus reset delivered. Mounting root from ufs:/dev/wd0s2a da0 at sym0 bus 0 target 3 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 2170MB (4445380 512 byte sectors: 255H 63S/T 276C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 21:41:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.5]) by hub.freebsd.org (Postfix) with ESMTP id A5D05155E5 for ; Wed, 8 Dec 1999 21:41:39 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: from gold.amis.net (gold.amis.net [212.18.37.254]) by server.amis.net (Postfix) with ESMTP id 67939D5C21; Thu, 9 Dec 1999 06:41:34 +0100 (CET) Received: by gold.amis.net (Postfix, from userid 1000) id D5E421D5F; Thu, 9 Dec 1999 06:41:32 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id B38995805; Thu, 9 Dec 1999 06:41:32 +0100 (CET) Date: Thu, 9 Dec 1999 06:41:23 +0100 (CET) From: Blaz Zupan X-Sender: blaz@localhost To: Christopher Masto Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991208180457.B1282@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Dec 1999, Christopher Masto wrote: > I fully agree that these things are neccessary and good. I just think > we need avoid jumping the gun on removing the old code, when some > people still need it to boot their machines. Actually I completely disagree. When you leave in old code in the tree, people who can't use the new code for whatever reason (technical problems, laziness, etc.) will use the old code. Forever. And people tend to not report such things - if it works with the old code, why bother? If you take something away from them, they will at least notice that it's broken and report it to the author. From my own experience, I lost the WaveLAN driver with the newbus stuff. If it was somehow still working (for example through some compatibility code for the old bus system), I'd not have done anything about it. But as it was broken, I sat down and fixed it. Although my time is as limited as everybody else's and it took me a whole day, I leared a lot through this. Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 21:43:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A1AB21530D; Wed, 8 Dec 1999 21:43:13 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA49601; Wed, 8 Dec 1999 22:43:09 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA09400; Wed, 8 Dec 1999 22:43:09 -0700 (MST) Message-Id: <199912090543.WAA09400@harmony.village.org> To: Poul-Henning Kamp Subject: Re: HEADSUP: wd driver will be retired! Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 08 Dec 1999 12:55:35 +0100." <32906.944654135@critter.freebsd.dk> References: <32906.944654135@critter.freebsd.dk> Date: Wed, 08 Dec 1999 22:43:09 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <32906.944654135@critter.freebsd.dk> Poul-Henning Kamp writes: : In a few days time the wd driver will be retired from FreeBSDs : i386 architecture. Isn't this a bit premature? It was my understanding that it would live through the 4.x release and then die. The ata driver was just made the default a few days ago. I'd argue for a less agressive retirement schedule. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 21:49:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 19B611556D; Wed, 8 Dec 1999 21:49:27 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA49616; Wed, 8 Dec 1999 22:49:21 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA09431; Wed, 8 Dec 1999 22:49:20 -0700 (MST) Message-Id: <199912090549.WAA09431@harmony.village.org> To: Mike Smith Subject: Re: HEADSUP: wd driver will be retired! Cc: Julian Elischer , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 08 Dec 1999 10:56:24 PST." <199912081856.KAA06231@mass.cdrom.com> References: <199912081856.KAA06231@mass.cdrom.com> Date: Wed, 08 Dec 1999 22:49:20 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912081856.KAA06231@mass.cdrom.com> Mike Smith writes: : This is a good time for this particular cutover. A little more public : announcement would perhaps have been nice, but that's probably asking : more of our axe-wielding friends than we're ever going to get. I'd agree more with this if the ata driver had been default for longer, but it has been default for a very short period of time. If ata had been made default in, say, October or early November, I'd not stand in the way of the hobnail tennisshoe of progress. But only being the default for a few days is rushing things a big. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 21:53: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 92B82151AB; Wed, 8 Dec 1999 21:52:51 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA49631; Wed, 8 Dec 1999 22:52:43 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA09459; Wed, 8 Dec 1999 22:52:42 -0700 (MST) Message-Id: <199912090552.WAA09459@harmony.village.org> To: Christopher Masto Subject: Re: HEADSUP: wd driver will be retired! Cc: Mike Smith , Julian Elischer , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 08 Dec 1999 15:08:07 EST." <19991208150807.A16687@netmonger.net> References: <19991208150807.A16687@netmonger.net> <199912081856.KAA06231@mass.cdrom.com> Date: Wed, 08 Dec 1999 22:52:42 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991208150807.A16687@netmonger.net> Christopher Masto writes: : Right now, I have no sound (not detected), no USB (panic on removal), : can't use my sio pccard, can't eject my ed pccard, my IDE drives are : taking hours to dump and fsck, and my TV card is missing every other : line if I try to use the (not working anyway) closed caption decoder. I have some patches for the can't eject the network cards from a user that I'm trying out and would then need to get committed to the network layer to properly support if_detach(). What's wrong with your sio pccard? Mine works well enough... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 21:56:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1E2D714E4D; Wed, 8 Dec 1999 21:56:12 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA49652; Wed, 8 Dec 1999 22:56:09 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA09496; Wed, 8 Dec 1999 22:56:09 -0700 (MST) Message-Id: <199912090556.WAA09496@harmony.village.org> To: obrien@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 08 Dec 1999 14:54:46 PST." <19991208145446.B11395@dragon.nuxi.com> References: <19991208145446.B11395@dragon.nuxi.com> <19991208150807.A16687@netmonger.net> <199912082052.MAA00517@mass.cdrom.com> Date: Wed, 08 Dec 1999 22:56:09 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : P.S. I'm not trying to cut down Warner, but I do think we really need to : focus on regaining support for things we've lost in the past 6 months. I agree with this completely. The newbus excursion of the old code likely was a big mistake. We have a basically working system now, but I've not had time to focus on the new system because of the amount of time I've spent on legacy issues. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 21:59:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6A0E515221; Wed, 8 Dec 1999 21:59:16 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA49660; Wed, 8 Dec 1999 22:59:07 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA09519; Wed, 8 Dec 1999 22:59:06 -0700 (MST) Message-Id: <199912090559.WAA09519@harmony.village.org> To: Julian Elischer Subject: Re: HEADSUP: wd driver will be retired! Cc: "Jonathan M. Bresler" , chris@netmonger.net, msmith@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 08 Dec 1999 15:45:39 PST." References: Date: Wed, 08 Dec 1999 22:59:06 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Julian Elischer writes: : more importantly we lost the aha driver for a while. No we didn't. Well, the aha driver did loose support for the 1542A cards, but the aha driver was done so that cam could be committed to the tree. Maybe you are confusing things with the aic driver? Also, the cam uha driver hasn't gotten past the cp aha -> query replace aha with uha stage... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 22:11:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 220AC155A0; Wed, 8 Dec 1999 22:11:18 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id BAA21974; Thu, 9 Dec 1999 01:11:12 -0500 (EST) Message-ID: <19991209011112.A21519@netmonger.net> Date: Thu, 9 Dec 1999 01:11:12 -0500 From: Christopher Masto To: Warner Losh Cc: Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! References: <19991208150807.A16687@netmonger.net> <199912081856.KAA06231@mass.cdrom.com> <19991208150807.A16687@netmonger.net> <199912090552.WAA09459@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199912090552.WAA09459@harmony.village.org>; from Warner Losh on Wed, Dec 08, 1999 at 10:52:42PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 08, 1999 at 10:52:42PM -0700, Warner Losh wrote: > In message <19991208150807.A16687@netmonger.net> Christopher Masto writes: > : Right now, I have no sound (not detected), no USB (panic on removal), > : can't use my sio pccard, can't eject my ed pccard, my IDE drives are > : taking hours to dump and fsck, and my TV card is missing every other > : line if I try to use the (not working anyway) closed caption decoder. > > I have some patches for the can't eject the network cards from a user > that I'm trying out and would then need to get committed to the > network layer to properly support if_detach(). > > What's wrong with your sio pccard? Mine works well enough... After the December 2nd change, as I reported: Hmm.. something's not right. I can eject my ed card (though I get the "pccard: card removed, slot 0" message twice. But it doesn't attach if I insert it again. "driver allocation failed for Linksys(Combo PCMCIA EthernetCard (EC): Device not configured". * sio is a bit worse, it doesn't work the first time (same error: * device not configured). I have since been completely bogged down in work, and I haven't even touched the machine since then. Our major product demo is tomorrow, Friday is major construction and rewiring on top of feedback from the demo, and on Saturday there's a complete power down to change out the building's UPS and then move an OC-3. With luck, if I'm still alive on Sunday, I'll be able to confirm whether the problem is still present and if so, try to fix it. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 22:13:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 66A8B14CFA; Wed, 8 Dec 1999 22:12:54 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA49716; Wed, 8 Dec 1999 23:12:52 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA09691; Wed, 8 Dec 1999 23:12:52 -0700 (MST) Message-Id: <199912090612.XAA09691@harmony.village.org> To: Christopher Masto Subject: Re: HEADSUP: wd driver will be retired! Cc: Mike Smith , Julian Elischer , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 09 Dec 1999 01:11:12 EST." <19991209011112.A21519@netmonger.net> References: <19991209011112.A21519@netmonger.net> <19991208150807.A16687@netmonger.net> <199912081856.KAA06231@mass.cdrom.com> <19991208150807.A16687@netmonger.net> <199912090552.WAA09459@harmony.village.org> Date: Wed, 08 Dec 1999 23:12:52 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : still alive on Sunday, I'll be able to confirm whether the problem : is still present and if so, try to fix it. That would be great! Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 22:57: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-49.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.177]) by hub.freebsd.org (Postfix) with ESMTP id E94F814E6C for ; Wed, 8 Dec 1999 22:56:56 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id GAA00952; Thu, 9 Dec 1999 06:56:37 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id GAA00403; Thu, 9 Dec 1999 06:57:51 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912090657.GAA00403@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Boris Popov Cc: Kelvin Farmer , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" In-Reply-To: Message from Boris Popov of "Thu, 09 Dec 1999 08:39:46 +0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Dec 1999 06:57:51 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 6 Dec 1999, Kelvin Farmer wrote: > > > Problem: Computer _sometimes_ stops after the "Mounting root from > > ufs:/dev/ad0s2a" line. > > Running Current, built world yesterday. (Problem appeared fairly > > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) > > I can confirm that behaviour of new ata driver. This happens one > time per 5-6 reboots. In addition, machines with VIA chipset work fine, > but all machines with i440BX chipset suffer from this problem: [.....] I've got this on both my laptop and development box too. isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ..... ad0: ATA-4 disk at ata0 as master ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata1 as master acd0: read 3445KB/s (3445KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, DVD-ROM, DVD-R acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ..... ad0: ATA-? disk at ata0 as master ad0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, DMA acd0: CDROM drive at ata1 as slave acd0: read 171KB/s (4125KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked, lock protected -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 22:57: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-49.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.177]) by hub.freebsd.org (Postfix) with ESMTP id C2000152C6; Wed, 8 Dec 1999 22:57:01 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id GAA00911; Thu, 9 Dec 1999 06:21:58 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id GAA11752; Thu, 9 Dec 1999 06:23:11 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912090623.GAA11752@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Warner Losh Cc: Julian Elischer , "Jonathan M. Bresler" , chris@netmonger.net, msmith@FreeBSD.ORG, current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: Message from Warner Losh of "Wed, 08 Dec 1999 22:59:06 MST." <199912090559.WAA09519@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Dec 1999 06:23:11 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message Julian Elischer writes: > : more importantly we lost the aha driver for a while. > > No we didn't. Well, the aha driver did loose support for the 1542A > cards, but the aha driver was done so that cam could be committed to > the tree. Maybe you are confusing things with the aic driver? The aha driver broke somewhere between the 5th and 8th of this month. Boot -v says ``aha0: status reg test failed ff''. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 23:10:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 5E02A15126; Wed, 8 Dec 1999 23:10:28 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id HAA21028; Thu, 9 Dec 1999 07:47:20 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA77409; Wed, 8 Dec 1999 23:19:58 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912082219.XAA77409@yedi.iaf.nl> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912082052.MAA00517@mass.cdrom.com> from Mike Smith at "Dec 8, 1999 12:52:37 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Wed, 8 Dec 1999 23:19:58 +0100 (CET) Cc: chris@netmonger.net, msmith@FreeBSD.ORG, julian@whistle.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Mike Smith wrote ... > > On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: > > Unfortunately, FreeBSD has far too many examples of a working system > > being replaced with a less functional system. Just off the top of my > > head, there were the SCSI drivers lost to CAM, the PCCARD system, > > sound drivers, and now ATA. > > Actually, most of this is histrionics. CAM didn't lose us SCSI drivers; Not quite true: the esp driver for the alphas got lost. No attack on anyone, just stating a fact. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 23:15:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 336E814CCE; Wed, 8 Dec 1999 23:15:55 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id XAA43044; Wed, 8 Dec 1999 23:16:00 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199912090716.XAA43044@troutmask.apl.washington.edu> Subject: Re: Reaping fortran cruft In-Reply-To: from Kris Kennaway at "Dec 8, 1999 07:36:34 pm" To: kris@hub.freebsd.org (Kris Kennaway) Date: Wed, 8 Dec 1999 23:16:00 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > On Wed, 8 Dec 1999, Steve Kargl wrote: > > > I was going to fix fsplit. Yes, I program in Fortran (note the > > proper spelling of Fortran). No, I don't use fsplit. > > A rewrite is certainly desperately needed :) > > > We might also want to remove fpr(1). > > Noted. Are there any other crufty Fortran candidates you can do without? No. I haven't found any other programs. > If no-one disagrees with this, I'll move them both to ports (probably in a > combined fortran-utils port) in a couple of days. Would you like to be the > maintainer? :) The dates in fsplit suggest that it hasn't seen any development since 1983. The functionality it provided then can be accomplished with vi and cp. I haven't looked at fpr, but you can get fancy program listings with a2ps (and probably apsfilter) which is (are) already in the ports collections. I say kill them (of course asbestos under garments might be needed). It should be noted that cvs will maintain a copy of both in the attic, so anyone who wants the source can get it. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 23:27: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 55E5914FFC for ; Wed, 8 Dec 1999 23:26:58 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA73442; Thu, 9 Dec 1999 08:26:48 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912090726.IAA73442@freebsd.dk> Subject: Re: ata vs wd driver performance In-Reply-To: <384F407B.5484C354@home.com> from "Richard S. Straka" at "Dec 8, 1999 10:39:07 pm" To: straka@home.com (Richard S. Straka) Date: Thu, 9 Dec 1999 08:26:48 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG (freebsd-current@FreeBSD.ORG) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Richard S. Straka wrote: > I have recently performed some testing on the ata and wd drivers > on my system. When writing to and reading from a file on the same > file system in the same directory, the ata driver appears to take almost > > double the CPU time as compared to the wd driver. However, when > reading from the raw disk, the ata and wd driver take about the same > amount of CPU time. DMA is enabled in both driver. Since the old driver doesn't tell you which DMA mode it uses, its a bit difficult to compare, but my gues is that the wd driver set UDMA2 mode and from the ata probe it can bee seen it only sets WDMA2 mode. Besides you should upgrade your current, the ata driver has support for the VIA chip now... > Can someone explain why the ata driver is using more CPU? > > Rich Straka > straka@home.com > > ********* > wd driver results writing to a file. > > $ time dd if=/dev/zero of=test.dat bs=1024k count=256 > 256+0 records in > 256+0 records out > 268435456 bytes transferred in 41.810011 secs (6420363 bytes/sec) > > real 0m42.136s > user 0m0.002s > sys 0m19.939s > > ********* > ata driver results writing to a file. > > $ time dd if=/dev/zero of=test.dat bs=1024k count=256 > 256+0 records in > 256+0 records out > 268435456 bytes transferred in 39.475358 secs (6800077 bytes/sec) > > real 0m39.750s > user 0m0.008s > sys 0m35.665s > > > ******** > wd driver results reading from a file. > > $ time dd if=test.dat of=/dev/null bs=1024k count=256 > 256+0 records in > 256+0 records out > 268435456 bytes transferred in 39.992958 secs (6712068 bytes/sec) > > real 0m40.040s > user 0m0.025s > sys 0m13.387s > > ******** > ata driver results reading from a file. > > $ time dd if=test.dat of=/dev/null bs=1024k count=256 > 256+0 records in > 256+0 records out > 268435456 bytes transferred in 37.914618 secs (7079999 bytes/sec) > > real 0m37.944s > user 0m0.009s > sys 0m28.221s > > > ******** > wd results reading from raw disk. > > $ time dd if=/dev/rwd0 of=/dev/null bs=1024k count=256 > 256+0 records in > 256+0 records out > 268435456 bytes transferred in 33.100446 secs (8109723 bytes/sec) > > real 0m33.137s > user 0m0.000s > sys 0m0.266s > > ******** > ata results reading from raw disk. > > $ time dd if=/dev/rwd0 of=/dev/null bs=1024k count=256 > 256+0 records in > 256+0 records out > 268435456 bytes transferred in 34.518500 secs (7776568 bytes/sec) > > real 0m34.535s > user 0m0.000s > sys 0m0.222s > > > > ******************************************************* > dmesg with wd driver. > ******************************************************* > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights > reserved. > FreeBSD 4.0-CURRENT #1: Sat Dec 4 09:22:58 MST 1999 > > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 333189478 Hz > CPU: AMD-K6(tm) 3D processor (333.19-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 > Features=0x8001bf > AMD Features=0x80000800 > real memory = 134152192 (131008K bytes) > avail memory = 127021056 (124044K bytes) > Preloaded elf kernel "kernel" at 0xc0303000. > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 > on pci0 > pci1: on pcib1 > isab0: at device 7.0 on pci0 > isa0: on isab0 > ide_pci0: at device 7.1 > on pci0 > chip1: at device 7.3 on pci0 > sym0: <875> irq 10 at device 8.0 on pci0 > sym0: Symbios NVRAM, ID 7, Fast-20, parity checking > sym0: open drain IRQ line driver, using on-chip SRAM > vga-pci0: at device 9.0 on pci0 > fxp0: irq 12 at device 10.0 on > pci0 > fxp0: Ethernet address 00:a0:c9:27:fc:1d > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa008a008 on isa0 > wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-8 > wd0: 4134MB (8467200 sectors), 8400 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at port 0x170-0x177 irq 15 flags 0xa008a008 on isa0 > wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-8 > wd2: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S > wdc1: unit 1 (atapi): , removable, dma, iordy > wcd0: drive speed 2062KB/sec, 240KB cache > wcd0: supported read types: CD-R, CD-DA > wcd0: Audio: play, 255 volume levels > wcd0: Mechanism: ejectable tray > wcd0: Medium: no/blank disc inside, unlocked > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on > isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > sio2 at port 0x3e8-0x3ef irq 5 on isa0 > sio2: type 16550A > ppc0 at port 0x378-0x37f irq 7 drq 3 on isa0 > ppc0: Winbond chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/16 bytes threshold > lpt0: on ppbus 0 > lpt0: Interrupt-driven port > ppi0: on ppbus 0 > pcm0: at port 0x530-0x53f irq 11 drq 1 flags 0xa610 on isa0 > Waiting 8 seconds for SCSI devices to settle > sym0: Downloading SCSI SCRIPTS. > (noperiph:sym0:0:-1:-1): SCSI bus reset delivered. > Mounting root from ufs:/dev/wd0s2a > da0 at sym0 bus 0 target 3 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing > Enabled > da0: 2170MB (4445380 512 byte sectors: 255H 63S/T 276C) > > > ******************************************************* > dmesg with ata driver. > ******************************************************* > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights > reserved. > FreeBSD 4.0-CURRENT #0: Wed Dec 8 22:13:02 MST 1999 > > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 333189391 Hz > CPU: AMD-K6(tm) 3D processor (333.19-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 > Features=0x8001bf > AMD Features=0x80000800 > real memory = 134152192 (131008K bytes) > avail memory = 127029248 (124052K bytes) > Preloaded elf kernel "kernel" at 0xc0301000. > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 > on pci0 > pci1: on pcib1 > isab0: at device 7.0 on pci0 > isa0: on isab0 > ata-pci0: at device 7.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > chip1: at device 7.3 on pci0 > sym0: <875> irq 10 at device 8.0 on pci0 > sym0: Symbios NVRAM, ID 7, Fast-20, parity checking > sym0: open drain IRQ line driver, using on-chip SRAM > vga-pci0: at device 9.0 on pci0 > fxp0: irq 12 at device 10.0 on > pci0 > fxp0: Ethernet address 00:a0:c9:27:fc:1d > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on > isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > sio2 at port 0x3e8-0x3ef irq 5 on isa0 > sio2: type 16550A > ppc0 at port 0x378-0x37f irq 7 drq 3 on isa0 > ppc0: Winbond chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/16 bytes threshold > lpt0: on ppbus 0 > lpt0: Interrupt-driven port > ppi0: on ppbus 0 > pcm0: at port 0x530-0x53f irq 11 drq 1 flags 0xa610 on isa0 > ad0: ATA-3 disk at ata0 as master > ad0: 4134MB (8467200 sectors), 8400 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, DMA > ad1: ATA-3 disk at ata1 as master > ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 1 depth queue, DMA > acd0: CDROM drive at ata1 as slave > acd0: read 2062KB/s (2062KB/s), 240KB buffer, PIO > acd0: supported read types: CD-R, CD-DA > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked > Waiting 8 seconds for SCSI devices to settle > sym0: Downloading SCSI SCRIPTS. > (noperiph:sym0:0:-1:-1): SCSI bus reset delivered. > Mounting root from ufs:/dev/wd0s2a > da0 at sym0 bus 0 target 3 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing > Enabled > da0: 2170MB (4445380 512 byte sectors: 255H 63S/T 276C) > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 23:35: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6]) by hub.freebsd.org (Postfix) with ESMTP id 36AF115209 for ; Wed, 8 Dec 1999 23:34:56 -0800 (PST) (envelope-from shigeru@iij.ad.jp) Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8]) by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id QAA05985 for ; Thu, 9 Dec 1999 16:34:54 +0900 (JST) Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id QAA18284 for ; Thu, 9 Dec 1999 16:34:54 +0900 (JST) Received: from mercury.iij.ad.jp (root@mercury.iij.ad.jp [192.168.4.89]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id QAA17497 for ; Thu, 9 Dec 1999 16:34:54 +0900 (JST) Received: from localhost (shigeru@localhost [127.0.0.1]) by mercury.iij.ad.jp (8.9.3/3.5W) with ESMTP id QAA27830 for ; Thu, 9 Dec 1999 16:34:53 +0900 (JST) To: current@FreeBSD.ORG Subject: why 'The legacy aout build' was removed from current ? X-Mailer: Mew version 1.93b38 on XEmacs 21.2 (Shinjuku) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991209163452O.shigeru@iij.ad.jp> Date: Thu, 09 Dec 1999 16:34:52 +0900 From: YAMAMOTO Shigeru X-Dispatcher: imput version 991025(IM133) Lines: 13 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In a log of @src/Makefile, revision 1.230, o The legacy aout build has been removed. Why 'The legacy aout build' was removed from current? Are we now living in the TRUE ELF world? Thanks, ------- YAMAMOTO Shigeru Internet Initiative Japan Inc. Network Engineering Div. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 23:45:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [36.118.0.70]) by hub.freebsd.org (Postfix) with ESMTP id 29508155B4; Wed, 8 Dec 1999 23:45:32 -0800 (PST) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.9.3/8.9.1) id XAA19457; Wed, 8 Dec 1999 23:43:34 -0800 (PST) Date: Wed, 8 Dec 1999 23:43:34 -0800 (PST) From: Bob Vaughan Message-Id: <199912090743.XAA19457@tantivy.stanford.edu> To: freebsd@gndrsh.dnsmgr.net, mike@sentex.net Subject: Re: Route table leaks Cc: current@FreeBSD.ORG, jdp@polstra.com, jgreco@ns.sol.net, stable@FreeBSD.ORG In-Reply-To: <199912081935.LAA98324@gndrsh.dnsmgr.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG here's mine.. this is from a single homed machine, with a default route. it's also a IRC server (irc.stanford.edu), with a LOT of filtering of inbound traffic. FreeBSD 3.3-STABLE #8: Sat Nov 27 17:15:49 PST 1999 11:33PM up 2 days, 20:41, 1 user, load averages: 0.03, 0.03, 0.00 routetbl 205 29K 10489K 10489K 3479960 0 0 16,32,64,128,256 note that the table maxed out at some point (during a DoS attack.) root-irc.stanford.edu-[11:34pm-52]#t> netstat -ran | wc 70 409 4741 looks like it leaked 135 in 2.8 days.. -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org | P.O. Box 9792, Stanford, Ca 94309-9792 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 23:51:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5EE6E15221 for ; Wed, 8 Dec 1999 23:51:24 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA79179; Thu, 9 Dec 1999 08:51:18 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912090751.IAA79179@freebsd.dk> Subject: Re: SiS ata Driver (was Re: HEADSUP: wd driver will be retired!) In-Reply-To: <19991208205054.A34152@tar.com> from "Richard Seaman, Jr." at "Dec 8, 1999 08:50:55 pm" To: dick@tar.com (Richard Seaman, Jr.) Date: Thu, 9 Dec 1999 08:51:18 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Richard Seaman, Jr. wrote: > On Wed, Dec 08, 1999 at 03:02:37PM +0100, Soren Schmidt wrote: > > > OK, you asked for it, following is a patch to support the > > sis 5591 chipset. Remember this is done blindfolded, I > > have no HW to test on, but you guys do :) > > Seems to work. I'll let it run for a few days, but I'd guess it > is fine. Great, I have a sligthly modified version that I'd like you to test, but it'll have to wait until I get home to my dev box. Thanks for testing it out!! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 8 23:59:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 7E05E14A1D; Wed, 8 Dec 1999 23:59:15 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id CAA26001; Thu, 9 Dec 1999 02:59:06 -0500 (EST) Date: Thu, 9 Dec 1999 02:59:06 -0500 (EST) From: "Matthew N. Dodd" To: Brian Somers Cc: Warner Losh , Julian Elischer , "Jonathan M. Bresler" , chris@netmonger.net, msmith@FreeBSD.ORG, current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912090623.GAA11752@hak.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 Thu, 9 Dec 1999, Brian Somers wrote: > The aha driver broke somewhere between the 5th and 8th of this month. > Boot -v says ``aha0: status reg test failed ff''. Are you sure? I don't see any changes to the driver during this month. aha.c: 1.33 date: 1999/10/25 04:28:53; author: imp; state: Exp; lines: +1 -2 1.32 date: 1999/10/11 19:05:20; author: imp; state: Exp; lines: +1 -2 aha_isa.c: 1.16 date: 1999/10/12 21:35:42; author: dfr; state: Exp; lines: +7 -9 1.15 date: 1999/10/11 19:05:21; author: imp; state: Exp; lines: +1 -2 ahareg.h: 1.7 date: 1999/08/28 00:41:21; author: peter; state: Exp; lines: +1 -1 1.6 date: 1999/05/25 20:15:20; author: gibbs; state: Exp; lines: +1 -3 -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 0: 1: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from snipe.rim.or.jp (p84b10a.kofu.ap.so-net.ne.jp [210.132.177.10]) by hub.freebsd.org (Postfix) with ESMTP id DF65E14BD6 for ; Thu, 9 Dec 1999 00:01:01 -0800 (PST) (envelope-from motoyuki@snipe.rim.or.jp) Received: from tomoyo.snipe.rim.or.jp (tomoyo.snipe.rim.or.jp [192.168.11.8]) by snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id RAA08360 for ; Thu, 9 Dec 1999 17:00:50 +0900 (JST) Received: from tomoyo.snipe.rim.or.jp (localhost [127.0.0.1]) by tomoyo.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id RAA01655 for ; Thu, 9 Dec 1999 17:00:50 +0900 (JST) Message-Id: <199912090800.RAA01655@tomoyo.snipe.rim.or.jp> To: current@FreeBSD.ORG Subject: Re: why 'The legacy aout build' was removed from current ? X-Mailer: mh-e on Mule 2.3 / Emacs 19.34.1 References: <19991209163452O.shigeru@iij.ad.jp> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Thu, 09 Dec 1999 17:00:50 +0900 From: Motoyuki Konno Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, YAMAMOTO Shigeru wrote: > In a log of @src/Makefile, revision 1.230, > > o The legacy aout build has been removed. > > Why 'The legacy aout build' was removed from current? > > Are we now living in the TRUE ELF world? I also wonder why a.out support was removed from -current. I think we don't need "a.out world" any more, but a.out support (a.out lib/shared lib, etc.) is still needed. Some commercial programs such as Netscape are in a.out only, so we still have to make a.out binaries. Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. Thanks. -- ------------------------------------------------------------------------ Motoyuki Konno mkonno@res.yamanashi-med.ac.jp (Univ) motoyuki@snipe.rim.or.jp (Home) motoyuki@FreeBSD.ORG (FreeBSD Project) Yamanashi Medical University http://www.freebsd.org/~motoyuki/ (WWW) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 0:10:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 064D515281 for ; Thu, 9 Dec 1999 00:10:44 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA83704; Thu, 9 Dec 1999 09:10:33 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912090810.JAA83704@freebsd.dk> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: from Blaz Zupan at "Dec 9, 1999 06:41:23 am" To: blaz@gold.amis.net (Blaz Zupan) Date: Thu, 9 Dec 1999 09:10:33 +0100 (CET) Cc: chris@netmonger.net (Christopher Masto), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Blaz Zupan wrote: > On Wed, 8 Dec 1999, Christopher Masto wrote: > > I fully agree that these things are neccessary and good. I just think > > we need avoid jumping the gun on removing the old code, when some > > people still need it to boot their machines. > > Actually I completely disagree. When you leave in old code in the tree, > people who can't use the new code for whatever reason (technical problems, > laziness, etc.) will use the old code. Forever. And people tend to not > report such things - if it works with the old code, why bother? If you > take something away from them, they will at least notice that it's broken > and report it to the author. > > >From my own experience, I lost the WaveLAN driver with the newbus stuff. > If it was somehow still working (for example through some compatibility > code for the old bus system), I'd not have done anything about it. But as > it was broken, I sat down and fixed it. Although my time is as limited as > everybody else's and it took me a whole day, I leared a lot through this. Wonderfully put, this is the _exact_ problem we are facing here. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 0:13:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 86B2D155E1 for ; Thu, 9 Dec 1999 00:13:13 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p24-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.121]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id RAA16353; Thu, 9 Dec 1999 17:13:08 +0900 (JST) Message-ID: <384F559E.B6386C5D@newsguy.com> Date: Thu, 09 Dec 1999 16:09:18 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Kelvin Farmer , freebsd-current@freebsd.org Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" References: <384C1779.C3010AFA@sympatico.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kelvin Farmer wrote: > > Problem: Computer _sometimes_ stops after the "Mounting root from > ufs:/dev/ad0s2a" line. > Running Current, built world yesterday. (Problem appeared fairly > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) > > dmesg: > [...] > ad0: ATA-3 disk at ata0 as master > ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S ^^^^^^ Is this the correct size of your hard disk? -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 0:13:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C36C615596 for ; Thu, 9 Dec 1999 00:13:15 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p24-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.121]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id RAA16334; Thu, 9 Dec 1999 17:13:05 +0900 (JST) Message-ID: <384F555A.CDC87592@newsguy.com> Date: Thu, 09 Dec 1999 16:08:10 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Maxim Sobolev Cc: Kelvin Farmer , freebsd-current@FreeBSD.ORG Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" References: <384C1779.C3010AFA@sympatico.ca> <384EE5DF.A55D2E3C@altavista.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > > Kelvin Farmer wrote: > > > Problem: Computer _sometimes_ stops after the "Mounting root from > > ufs:/dev/ad0s2a" line. > > Running Current, built world yesterday. (Problem appeared fairly > > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) > > I've also observed this problem and it is interesting that my HDD is Quantum FB ST 2.1 too. Does it report the correct size, btw? If not, does it report 4092 cylinders? -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 0:13:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A3C76155E4; Thu, 9 Dec 1999 00:13:19 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p24-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.121]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id RAA16367; Thu, 9 Dec 1999 17:13:11 +0900 (JST) Message-ID: <384F5BDA.9B4FDEC9@newsguy.com> Date: Thu, 09 Dec 1999 16:35:54 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Julian Elischer Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! References: 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: > > please do not remove it.. > just make it non-default. Retire it to LINT if you must, but I'd also like to see it around until the last release on RELENG_3. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 0:14: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A7E9B14BF9; Thu, 9 Dec 1999 00:13:34 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p24-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.121]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id RAA16384; Thu, 9 Dec 1999 17:13:16 +0900 (JST) Message-ID: <384F5CCC.8B116E7F@newsguy.com> Date: Thu, 09 Dec 1999 16:39:56 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Soren Schmidt Cc: Julian Elischer , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! References: <199912081721.SAA70567@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > It seems Julian Elischer wrote: > > > please do not remove it.. > > And why is that ?? There is no point in having done a new one then, and > you guys have known I've been working on this for ages so this cannot > come as a surprise to anybody... Not true. We can (and should) replace it with the new one in GENERIC, but it can be left to rot for a while in LINT. The point is having the driver in -current until the last release of RELENG_3, so that changes (such as the one you vetoed for your new driver) can be changed. When RELENG_3 is dead, we can remove it from RELENG_4. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 0:15:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 40B43152C8 for ; Thu, 9 Dec 1999 00:15:42 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcm211.cvzoom.net (lcm211.cvzoom.net [208.230.69.211]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id CAA14837 for ; Thu, 9 Dec 1999 02:56:16 -0500 (EST) Date: Thu, 9 Dec 1999 03:14:44 -0500 (EST) From: Donn Miller To: current@FreeBSD.ORG Subject: Sound card support In-Reply-To: <199912090800.RAA01655@tomoyo.snipe.rim.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [subject changes and thread hijacked] On Thu, 9 Dec 1999, Motoyuki Konno wrote: > Please see Netscape plugin port (ports/www/flashplugin) to find > out why we still have to need a.out support. Wow -- there's a flash plugin for Netscape? That's what I needed for a couple of web sites. Also, I hope to contribute in some way to broaden FreeBSD's sound card support. I have the ESS 1868. I just made a printout of the data sheets for this particular sound card. If anyone out there needs the pdf version of the ESS 1868 datasheet/specs, just email me and I can send you a copy via email. So far, it looks like the 1868 only does full duplex in mono. ;-( (Is the 1868 even worth worrying about?) Also, how well does the ProAudio Spectrum 16 work at this point right now in -current? Does it work flawlessly? Whatever happened to the company that made the PAS 16? I saw where MediaVision doesn't exist anymore. Has another company taken over PAS development? Anyhow, as far as ISA cards go... how does the PAS 16 compare to the ESS 1868? I think the PAS only gets full duplex when you've got both the PAS and the SB compatibility side working in tandem. Well, I've got a PCI machine (Pentium), so I imagine a PCI sound card would be worlds better. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 0:23:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 68CA01515E for ; Thu, 9 Dec 1999 00:23:52 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11vyrU-000BB2-00; Thu, 09 Dec 1999 10:23:40 +0200 From: Sheldon Hearn To: Motoyuki Konno Cc: current@FreeBSD.ORG Subject: Re: why 'The legacy aout build' was removed from current ? In-reply-to: Your message of "Thu, 09 Dec 1999 17:00:50 +0900." <199912090800.RAA01655@tomoyo.snipe.rim.or.jp> Date: Thu, 09 Dec 1999 10:23:40 +0200 Message-ID: <42967.944727820@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 09 Dec 1999 17:00:50 +0900, Motoyuki Konno wrote: > I think we don't need "a.out world" any more, but a.out support > (a.out lib/shared lib, etc.) is still needed. Some commercial > programs such as Netscape are in a.out only, so we still have to > make a.out binaries. Are you sure? Any a.out binaries for FreeBSD are going to be desgined to work with 3.x or older. So producing a.out libraries for CURRENT is silly. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 0:37:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 2E3AD1531C for ; Thu, 9 Dec 1999 00:37:11 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id AAA79252; Thu, 9 Dec 1999 00:37:00 -0800 (PST) Date: Thu, 9 Dec 1999 00:36:59 -0800 (PST) From: Julian Elischer To: Soren Schmidt Cc: Blaz Zupan , Christopher Masto , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912090810.JAA83704@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Dec 1999, Soren Schmidt wrote: > > >From my own experience, I lost the WaveLAN driver with the newbus stuff. > > If it was somehow still working (for example through some compatibility > > code for the old bus system), I'd not have done anything about it. But as > > it was broken, I sat down and fixed it. Although my time is as limited as > > everybody else's and it took me a whole day, I leared a lot through this. > > Wonderfully put, this is the _exact_ problem we are facing here. > Besides if you leave the old subsystem fully functional, then some individual working on their own can decide to totally delete your new working subsystem from the tree just for fun. But then THAT would never happen would it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 1: 3:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 15D3F15496 for ; Thu, 9 Dec 1999 01:03:52 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11vzUA-000LdV-00; Thu, 9 Dec 1999 09:03:38 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id KAA40913; Thu, 9 Dec 1999 10:03:49 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <384F7075.C17EF1B8@scc.nl> Date: Thu, 09 Dec 1999 10:03:49 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: current@freebsd.org Subject: Re: Cleaning house on /usr/src/* References: <199912081718.JAA29021@vashon.polstra.com> <384EA2CF.B3E40E35@scc.nl> <199912090504.VAA36946@vashon.polstra.com> 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: > > When you change the tag (e.g., go from -stable to -current or vice > versa), it's a special case. Thanks, I'll remember that. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 1:11:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6]) by hub.freebsd.org (Postfix) with ESMTP id 59A761557D for ; Thu, 9 Dec 1999 01:11:31 -0800 (PST) (envelope-from shigeru@iij.ad.jp) Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8]) by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id SAA08122 for ; Thu, 9 Dec 1999 18:11:29 +0900 (JST) Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id SAA04329 for ; Thu, 9 Dec 1999 18:11:29 +0900 (JST) Received: from mercury.iij.ad.jp (root@mercury.iij.ad.jp [192.168.4.89]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id SAA28734 for ; Thu, 9 Dec 1999 18:11:29 +0900 (JST) Received: from localhost (shigeru@localhost [127.0.0.1]) by mercury.iij.ad.jp (8.9.3/3.5W) with ESMTP id SAA27949 for ; Thu, 9 Dec 1999 18:11:28 +0900 (JST) To: current@freebsd.org Subject: which is right? 'controller pcic0 at isa?' or 'device pcic0 at isa?'? X-Mailer: Mew version 1.93b38 on XEmacs 21.2 (Shinjuku) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991209181127N.shigeru@iij.ad.jp> Date: Thu, 09 Dec 1999 18:11:27 +0900 From: YAMAMOTO Shigeru X-Dispatcher: imput version 991025(IM133) Lines: 12 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wonder about configuration for pcic in -current. In GENERIC, '#device pcic0 at isa?' In LINT and PCCARD, 'controller pcic0 at isa?' Which is right? Thanks, ------- YAMAMOTO Shigeru Internet Initiative Japan Inc. Network Engineering Div. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 1:26:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id BA8AB155C9 for ; Thu, 9 Dec 1999 01:25:38 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id LAA97643 for freebsd-current@FreeBSD.ORG; Thu, 9 Dec 1999 11:25:25 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199912090925.LAA97643@zibbi.mikom.csir.co.za> Subject: make release broken To: freebsd-current@FreeBSD.ORG (FreeBSD-current) Date: Thu, 9 Dec 1999 11:25:25 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Make release in a -current cvsuped just now broke. It looks like the aout directory is not there. --------- ===> libtacplus sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 /usr/src/lib/libtacplus/taclib.h /usr/obj/usr/src/tmp/usr/include sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 libtacplus.a /usr/obj/usr/src/tmp/usr/lib sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 libtacplus_p.a /usr/obj/usr/src/tmp/usr/lib sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 444 libtacplus.so.1 /usr/obj/usr/src/tmp/usr/lib ln -sf libtacplus.so.1 /usr/obj/usr/src/tmp/usr/lib/libtacplus.so ===> compat ===> compat/compat1x sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 libc.so.1.1 libcurses.so.1.1 libf2c.so.1.1 libg++.so.1.1 libgcc.so.1.1 libgnumalloc.so.1.1 libgnuregex.so.1.1 libln.so.1.1 libm.so.1.1 libmalloc.so.1.1 libreadline.so.1.1 libresolv.so.1.1 librpcsvc.so.1.1 libskey.so.1.1 libtelnet.so.1.1 libtermcap.so.1.1 libutil.so.1.1 liby.so.1.1 /usr/obj/usr/src/tmp/usr/lib/compat/aout usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory *** Error code 1 Stop in /usr/src/lib/compat/compat1x. *** Error code 1 Stop in /usr/src/lib/compat. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 ---------- John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 1:30:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id EF30C15179 for ; Thu, 9 Dec 1999 01:30:19 -0800 (PST) (envelope-from vallo@solaris.matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id BA2F22CE4F; Thu, 9 Dec 1999 11:30:14 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id D4A3B106; Thu, 9 Dec 1999 11:30:15 +0200 (EET) Date: Thu, 9 Dec 1999 11:30:15 +0200 From: Vallo Kallaste To: Boris Popov Cc: Kelvin Farmer , freebsd-current@freebsd.org Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" Message-ID: <19991209113015.A41360@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <384C1779.C3010AFA@sympatico.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Boris Popov on Thu, Dec 09, 1999 at 08:39:46AM +0600 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 09, 1999 at 08:39:46AM +0600, Boris Popov wrote: > > Problem: Computer _sometimes_ stops after the "Mounting root from > > ufs:/dev/ad0s2a" line. > > Running Current, built world yesterday. (Problem appeared fairly > > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) > > I can confirm that behaviour of new ata driver. This happens one > time per 5-6 reboots. In addition, machines with VIA chipset work fine, > but all machines with i440BX chipset suffer from this problem: Same here, one for about 10 reboots. Just sits quietly after "Mounting root from .." message. No other ill effects. SiS 530 chipset (5591), Seagate 6GB ATA-3 disk, new ata driver. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 1:32: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 343D315601 for ; Thu, 9 Dec 1999 01:31:56 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from cvzoom.net (lcm211.cvzoom.net [208.230.69.211]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id EAA17502 for ; Thu, 9 Dec 1999 04:12:30 -0500 (EST) Message-ID: <384F76D2.938FD166@cvzoom.net> Date: Thu, 09 Dec 1999 04:30:58 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: MCA support Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wondering how far along MCA support is. I tried booting up a kern.flp from the latest snapshot circa dec. 7. and I got a "Read error" during boot, which halted the machine. My machine was an IBM PS/2 model 77s. I'd like to make an mca picobsd release as well. -- - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 2:16:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1F7291509D for ; Thu, 9 Dec 1999 02:16:41 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA13261; Thu, 9 Dec 1999 11:16:10 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912091016.LAA13261@freebsd.dk> Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" In-Reply-To: <19991209113015.A41360@myhakas.matti.ee> from Vallo Kallaste at "Dec 9, 1999 11:30:15 am" To: vallo@matti.ee Date: Thu, 9 Dec 1999 11:16:10 +0100 (CET) Cc: bp@butya.kz (Boris Popov), kfarmer@sympatico.ca (Kelvin Farmer), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Vallo Kallaste wrote: > On Thu, Dec 09, 1999 at 08:39:46AM +0600, Boris Popov wrote: > > > > Problem: Computer _sometimes_ stops after the "Mounting root from > > > ufs:/dev/ad0s2a" line. > > > Running Current, built world yesterday. (Problem appeared fairly > > > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) > > > > I can confirm that behaviour of new ata driver. This happens one > > time per 5-6 reboots. In addition, machines with VIA chipset work fine, > > but all machines with i440BX chipset suffer from this problem: > > Same here, one for about 10 reboots. Just sits quietly after "Mounting > root from .." message. No other ill effects. SiS 530 chipset (5591), > Seagate 6GB ATA-3 disk, new ata driver. I just searched a bit in the lists etc, and this problem also exists in 3.x with the old driver, hmm, there is even one mentioning it on a SCSI only system, more hmmm.... I guess its not only related to the ata driver alone.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 2:27:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 130171534B for ; Thu, 9 Dec 1999 02:27:32 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA23617 for current@FreeBSD.org; Thu, 9 Dec 1999 11:27:21 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 09 Dec 1999 11:27:15 +0100 From: Marcel Moolenaar Message-ID: <384F8403.875CB81D@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19991209163452O.shigeru@iij.ad.jp> Subject: Re: why 'The legacy aout build' was removed from current ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG YAMAMOTO Shigeru wrote: > > In a log of @src/Makefile, revision 1.230, > > o The legacy aout build has been removed. > > Why 'The legacy aout build' was removed from current? There's no point in building legacy a.out stuff from -current sources. The result has nothing to do with legacy but only with a.out. Compatibility with legacy a.out binaries can best be achieved by installing the proper compat distribution (compat22 for example). -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 2:33:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id 203A61531C; Thu, 9 Dec 1999 02:33:12 -0800 (PST) (envelope-from fn@gatekeeper.radio-do.de) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by gatekeeper.radio-do.de (Postfix) with ESMTP id 36A82A124; Thu, 9 Dec 1999 11:33:09 +0100 (MET) Received: (from fn@localhost) by trinity.radio-do.de (8.9.3/8.9.3) id LAA29041; Thu, 9 Dec 1999 11:33:09 +0100 (CET) (envelope-from fn@gatekeeper.radio-do.de) Date: Thu, 9 Dec 1999 11:33:09 +0100 From: Frank Nobis To: Seigo Tanimura Cc: caa@columbus.rr.com, msmith@FreeBSD.ORG, schuerge@wjpserver.CS.Uni-SB.DE, freebsd-current@FreeBSD.ORG Subject: Re: AWE64 problems Message-ID: <19991209113308.A28987@radio-do.de> References: <19991208000746.A1622@midgard.dhs.org> <199912080513.VAA07525@mass.cdrom.com> <19991208085415.A534@midgard.dhs.org> <14415.8493.971538.78435L@rina.r.dl.itc.u-tokyo.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <14415.8493.971538.78435L@rina.r.dl.itc.u-tokyo.ac.jp> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 09, 1999 at 12:25:33PM +0900, Seigo Tanimura wrote: > [snipped some part] > >> > > On Tue, 7 Dec 1999 23:00:02 +0100 (MET), > >> > > Thomas Schuerger said: > >> > > > >> > > >> --- sbc.c.orig Mon Dec 6 19:26:31 1999 > >> > > >> +++ sbc.c Tue Dec 7 22:15:25 1999 > >> > > >> @@ -110,7 +110,7 @@ > >> > > >> if (error) > >> > > >> return error; > >> > > >> else > >> > > >> - return -100; > >> > > >> + return -1; > >> > > >> } > >> > > >> > >> > > >> static int > > On Wed, 8 Dec 1999 08:54:15 -0500, > "Charles Anderson" said: > > Charles> So then what is -1 and why does it work when -100 doesn't? (I tried it) > > > sys/kern/subr_bus.c:device_probe_child() receives the value returned > by DEVICE_PROBE(child dev). If the value is zero, no further probes > occur. The device then gets attached in sys/kern/subr_bus.c: > device_probe_and_attach(). > Ahh, now it makes sense to me. In case of an unknown device, error = ISA_PNP_PROBE(...) set error to a value larger than 0. In case of a successfull match error is set to 0. IMHO the correct probe should be: sbc_probe(device_t dev) { int error; /* Check pnp ids */ error = ISA_PNP_PROBE(device_get_parent(dev), dev, sbc_ids); if (error >= 0) return error; else return -100; } Is it possible that error gets a value below 0 ? In that case the probe should arrange for this case. Any comments ? Frank -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 2:55:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 056B814DDD for ; Thu, 9 Dec 1999 02:54:33 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from mboxes.jrc.it (mboxes.jrc.it [139.191.1.63]) by mrelay.jrc.it (LMC5692) with ESMTP id LAA26893; Thu, 9 Dec 1999 11:53:15 +0100 (MET) Received: from mboxes (139.191.1.63) by mboxes.jrc.it; 9 Dec 1999 11:49:36 +0100 MIME-Version: 1.0 Date: Thu, 9 Dec 1999 11:49:36 +0100 From: Message-Id: <944736576.webexpressdV2.1b1@mboxes.jrc.it> To: "Julian Elischer" Cc: "Matthew N. Dodd" , Subject: Re: OHCI weirdness? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen this problem under stress, not normally during boot. Time permitting I will have a look into this next week. Probably a race condition somewhere. Could you tell me whether the panic appears after a lengthy wait or is it directly related to a an event like plugging in a device or starting to talk to it (usbd, ugen, etc.) Cheers, Nick > "me too" (but only if there is a device plugged in) > > > I get this same panic with both devices I've tried; a Kodak DC265 and a > > Sandisk CompactFlash reader. Its not obvious why this is happening (at > > least from where I'm sitting.) > > > > Any ideas? > > > > Should I report back with a kernel compiled with OHCI_DEBUG? > > > > Thanks. > > > > ... > > ohci0: irq 9 at device 11.0 on pci0 > > usb0: OHCI version 1.0, legacy support > > usb0: on ohci0 > > usb0: USB revision 1.0 > > uhub0: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 2 ports with 2 removable, self powered > > panic: ohci_hash_find_td: addr 0x03e7c770 not found > > > > Debugger("panic") > > Stopped at Debugger+0x37: movl $0,in_Debugger > > db> t > > Debugger(c0289aa3) at Debugger+0x37 > > panic(c029c0c0,3e7c770,c0373cbc,c0225142,c07a5800) at panic+0x74 > > ohci_hash_find_td(c07a5800,3e7c770,6,c07a5800,2) at ohci_hash_find_td+0x33 > > ohci_process_done(c07a5800,3e7c7d0,6b9457,c07a5800,c07a6e80) at > ohci_process_done+0x1e > > ohci_intr1(c07a5800) at ohci_intr1+0x10c > > ohci_waitintr(c07a5800,c07a6e80,c07a6e80,c07a6e80,c0373d20) at > ohci_waitintr+0x69 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ---------End of Included Message---------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 2:56: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id DFEC0155A3 for ; Thu, 9 Dec 1999 02:55:58 -0800 (PST) (envelope-from netchild@Leidinger.net) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id LAA12834148; Thu, 9 Dec 1999 11:55:33 +0100 (CET) Received: from Magelan.Leidinger.net (maxtnt-196.telip.uni-sb.de [134.96.71.67]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id LAA18207; Thu, 9 Dec 1999 11:55:42 +0100 (CET) Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id LAA00711; Thu, 9 Dec 1999 11:51:41 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <199912091051.LAA00711@Magelan.Leidinger.net> Date: Thu, 9 Dec 1999 11:51:40 +0100 (CET) From: Alexander Leidinger Subject: Re: HEADSUP: wd driver will be retired! To: sos@freebsd.dk Cc: current@FreeBSD.ORG In-Reply-To: <199912081609.RAA53062@freebsd.dk> 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 On 8 Dec, Soren Schmidt wrote: >> Søren: I didn´t want to flame you, I only want to convince Paul-Henning >> to wait until you have time to fix those bugs. > > Welcome to the real world, I've promised to look at this and I will, > but a day has only so many hours. I asumed this, and because of this I made my statement above. > Instead of complaining, help the project, when have you last closed a PR ?? Am I allowed to repeat your "real world" statement? Bye, Alexander. -- Withdrawal is for quitters. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 2:57:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 09B9D15200 for ; Thu, 9 Dec 1999 02:57:32 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA28984 for current@FreeBSD.org; Thu, 9 Dec 1999 11:49:14 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 09 Dec 1999 11:49:09 +0100 From: Marcel Moolenaar Message-ID: <384F8925.EB62F76C@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199912090925.LAA97643@zibbi.mikom.csir.co.za> Subject: Re: make release broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > Make release in a -current cvsuped just now broke. It looks like the aout > directory is not there. Fixed. Thanks. I'm testing as well, so if anything comes up, let me know. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 2:57:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 6651D15315 for ; Thu, 9 Dec 1999 02:57:33 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA25818 for current@FreeBSD.org; Thu, 9 Dec 1999 11:35:59 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 09 Dec 1999 11:35:54 +0100 From: Marcel Moolenaar Message-ID: <384F860A.499A29EA@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19991209163452O.shigeru@iij.ad.jp>, <199912090800.RAA01655@tomoyo.snipe.rim.or.jp> Subject: Re: why 'The legacy aout build' was removed from current ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Motoyuki Konno wrote: > I also wonder why a.out support was removed from -current. a.out support has not been removed. We just don't do any legacy a.out building. > I think we don't need "a.out world" any more, but a.out support > (a.out lib/shared lib, etc.) is still needed. For this, the proper compat distribution should/can be installed. > Some commercial > programs such as Netscape are in a.out only, so we still have to > make a.out binaries. No, we only have to *run* them. This we do. If Netscape were to compile on -current, they would have an ELF version... > Please see Netscape plugin port (ports/www/flashplugin) to find > out why we still have to need a.out support. The port has nothing to do with building a legacy a.out world and consequently works fine (yes, I tested it :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 2:57:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id BFD8E15344 for ; Thu, 9 Dec 1999 02:57:34 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA25944 for current@FreeBSD.org; Thu, 9 Dec 1999 11:36:37 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 09 Dec 1999 11:36:35 +0100 From: Marcel Moolenaar Message-ID: <384F8633.F40337BC@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19991209163452O.shigeru@iij.ad.jp>, <199912090800.RAA01655@tomoyo.snipe.rim.or.jp> Subject: Re: why 'The legacy aout build' was removed from current ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Motoyuki Konno wrote: > I also wonder why a.out support was removed from -current. a.out support has not been removed. We just don't do any legacy a.out building. > I think we don't need "a.out world" any more, but a.out support > (a.out lib/shared lib, etc.) is still needed. For this, the proper compat distribution should/can be installed. > Some commercial > programs such as Netscape are in a.out only, so we still have to > make a.out binaries. No, we only have to *run* them. This we do. If Netscape were to compile on -current, they would have an ELF version... > Please see Netscape plugin port (ports/www/flashplugin) to find > out why we still have to need a.out support. The port has nothing to do with building a legacy a.out world and consequently works fine (yes, I tested it :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 3:17:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 8E07A14E6C for ; Thu, 9 Dec 1999 03:17:30 -0800 (PST) (envelope-from vallo@solaris.matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 23C6E2CE54; Thu, 9 Dec 1999 13:17:25 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 0900B106; Thu, 9 Dec 1999 13:17:28 +0200 (EET) Date: Thu, 9 Dec 1999 13:17:27 +0200 From: Vallo Kallaste To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" Message-ID: <19991209131727.A41814@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <19991209113015.A41360@myhakas.matti.ee> <199912091016.LAA13261@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199912091016.LAA13261@freebsd.dk>; from Soren Schmidt on Thu, Dec 09, 1999 at 11:16:10AM +0100 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 09, 1999 at 11:16:10AM +0100, Soren Schmidt wrote: > > Same here, one for about 10 reboots. Just sits quietly after "Mounting > > root from .." message. No other ill effects. SiS 530 chipset (5591), > > Seagate 6GB ATA-3 disk, new ata driver. > > I just searched a bit in the lists etc, and this problem also exists > in 3.x with the old driver, hmm, there is even one mentioning it > on a SCSI only system, more hmmm.... > > I guess its not only related to the ata driver alone.... Hard to say.. my work machine is SCSI only and I track -current on both my home and work machine. Haven't had such behavior on my work machine. I can't remember that I had such problems using 3.0-current or are you pointing to -stable? I'm running only -current for a while now and we don't reboot our -stable machines often :-) -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 3:22: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 4580D155CB for ; Thu, 9 Dec 1999 03:22:01 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 6A3021CA0; Thu, 9 Dec 1999 19:21:57 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: YAMAMOTO Shigeru Cc: current@freebsd.org Subject: Re: which is right? 'controller pcic0 at isa?' or 'device pcic0 at isa?'? In-Reply-To: Message from YAMAMOTO Shigeru of "Thu, 09 Dec 1999 18:11:27 +0900." <19991209181127N.shigeru@iij.ad.jp> Date: Thu, 09 Dec 1999 19:21:57 +0800 From: Peter Wemm Message-Id: <19991209112157.6A3021CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG YAMAMOTO Shigeru wrote: > > I wonder about configuration for pcic in -current. > > In GENERIC, '#device pcic0 at isa?' > In LINT and PCCARD, 'controller pcic0 at isa?' "device" is just about the same as "controller", there is only one difference. If you use "controller", then config allows you to have other lines: device foo at pcic0 This is solely to keep config(8) happy. It makes no difference to the kernel at all. > Which is right? > > Thanks, > ------- > YAMAMOTO Shigeru Internet Initiative Japan Inc. > Network Engineering Div. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 3:22:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 97BDB15604 for ; Thu, 9 Dec 1999 03:22:09 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from mboxes.jrc.it (mboxes.jrc.it [139.191.1.63]) by mrelay.jrc.it (LMC5692) with ESMTP id MAA28380 for ; Thu, 9 Dec 1999 12:22:07 +0100 (MET) Received: from mboxes (139.191.1.63) by mboxes.jrc.it; 9 Dec 1999 12:18:26 +0100 MIME-Version: 1.0 Date: Thu, 9 Dec 1999 12:18:26 +0100 From: Message-Id: <944738306.webexpressdV2.1b1@mboxes.jrc.it> To: "Kazutaka YOKOTA" , "Viren R. Shah" Cc: , Subject: Re: Using USB modules with an USB keyboard... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I added your recommendations above to the kernel config file > >(TWELVE). It didn't work. As can be seen from the dmesg below, when > >the USB options are present in the kernel, ukbd0 is found. When USB > >KLDs are used, uhid0 seems to grab the keyboard. this is correct. Both drivers know how to handle a HID device, but ukbd has a higher priority. if you load the ukbd driver and then unplug-plug the keyboard, the ukbd driver will attach to the keyboard. > >Dec 7 19:57:33 frabjous /kernel: ums0: Logitech USB-PS/2 Mouse M-BA47, rev > 1. > >00/1.10, addr 2, iclass 3/1 Could you send me the output of usbdevs -v when the mouse is connected? usbdevs -v | mail n_hibma@webweaving.org > >Dec 7 19:57:33 frabjous /kernel: ums0: 4 buttons and Z dir. > >Dec 7 19:57:33 frabjous /kernel: uhid0: QTRONIX USB Keyboard and Mouse, > >Dec 7 19:57:33 frabjous /kernel: ums1: QTRONIX USB Keyboard and Mouse, You have a QTronix keyboard. It has been reported to me that the keyboard repeats keys sometimes. Let me know whether this is the case. Also, the firmware in the keyboard is very broken. If you hook up a PS/2 mouse to the keyboard, and notice that you get spurious button up events (in X windows the window is dropped and picked up several times when moving it), make sure you have an up to date version of the ums driver. If you don't run current and run into this problem, let me know and I'll see whether I can back port that fix to STABLE. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 3:30: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 0F70C155CB for ; Thu, 9 Dec 1999 03:30:04 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id DAA28782; Thu, 9 Dec 1999 03:16:45 -0800 (PST) Date: Thu, 9 Dec 1999 03:16:45 -0800 (PST) From: Annelise Anderson To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: why 'The legacy aout build' was removed from current ? In-Reply-To: <384F860A.499A29EA@scc.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried to build -current tonight with the following uncommented in /etc/make.conf: # # If you want the "compat" shared libraries installed as part of your normal # builds, uncomment these: # #COMPAT1X= yes #COMPAT20= yes #COMPAT21= yes #COMPAT22= yes #COMPAT3X= yes # and it didn't work, so I re-commented them. Probably no point in having them anyway. Annelise On Thu, 9 Dec 1999, Marcel Moolenaar wrote: > Motoyuki Konno wrote: > > > I also wonder why a.out support was removed from -current. > > a.out support has not been removed. We just don't do any legacy a.out > building. > > > I think we don't need "a.out world" any more, but a.out support > > (a.out lib/shared lib, etc.) is still needed. > > For this, the proper compat distribution should/can be installed. > > > Some commercial > > programs such as Netscape are in a.out only, so we still have to > > make a.out binaries. > > No, we only have to *run* them. This we do. If Netscape were to compile > on -current, they would have an ELF version... > > > Please see Netscape plugin port (ports/www/flashplugin) to find > > out why we still have to need a.out support. > > The port has nothing to do with building a legacy a.out world and > consequently works fine (yes, I tested it :-) > > -- > Marcel Moolenaar mailto:marcel@scc.nl > SCC Internetworking & Databases http://www.scc.nl/ > The FreeBSD project mailto:marcel@FreeBSD.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 3:32:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id E0FB814CFA; Thu, 9 Dec 1999 03:32:41 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id GAA06112; Thu, 9 Dec 1999 06:32:35 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id GAA02336; Thu, 9 Dec 1999 06:32:33 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id GAA41598; Thu, 9 Dec 1999 06:32:33 -0500 (EST) Date: Thu, 9 Dec 1999 06:32:33 -0500 (EST) From: Thomas David Rivers Message-Id: <199912091132.GAA41598@lakes.dignus.com> To: imp@village.org, julian@whistle.com Subject: Re: HEADSUP: wd driver will be retired! Cc: chris@netmonger.net, current@FreeBSD.ORG, jmb@hub.freebsd.org, msmith@FreeBSD.ORG In-Reply-To: <199912090559.WAA09519@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In message Julian Elischer writes: > : more importantly we lost the aha driver for a while. > > No we didn't. Well, the aha driver did loose support for the 1542A > cards, but the aha driver was done so that cam could be committed to > the tree. Maybe you are confusing things with the aic driver? > > Also, the cam uha driver hasn't gotten past the cp aha -> query > replace aha with uha stage... > > Warner > I lost support on my 1542B until I came up with a patch, which I believe was incorporated into 3.3-R. - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 3:48:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id ECE741557D for ; Thu, 9 Dec 1999 03:48:08 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from mboxes.jrc.it (mboxes.jrc.it [139.191.1.63]) by mrelay.jrc.it (LMC5692) with ESMTP id MAA29381 for ; Thu, 9 Dec 1999 12:48:06 +0100 (MET) Received: from mboxes (139.191.1.63) by mboxes.jrc.it; 9 Dec 1999 12:44:26 +0100 MIME-Version: 1.0 Date: Thu, 9 Dec 1999 12:44:26 +0100 From: Message-Id: <944739866.webexpressdV2.1b1@mboxes.jrc.it> To: "Maxim Sobolev" , "Kelvin Farmer" Cc: Subject: Re: boot stops after Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Problem: Computer _sometimes_ stops after the "Mounting root from > > ufs:/dev/ad0s2a" line. > > Running Current, built world yesterday. (Problem appeared fairly > > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) > > I've also observed this problem and it is interesting that my HDD is Quantum FB > ST 2.1 too. I've seen this on a Toshiba Disk, A WD 2.1Gb drive (which almost but not quite dead), and two Seagate 106Mb drives (flakey). So I guess you'r assumption is flakey. Also, with respect to the trace shown somewhere earlier, I've not seen consistent behaviour in where it stops, but this could be EBADMEM. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 4:16:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-004.rp-plus.de [149.221.237.4]) by hub.freebsd.org (Postfix) with ESMTP id 92F7D1560D for ; Thu, 9 Dec 1999 04:16:33 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 12B68AB87; Thu, 9 Dec 1999 13:02:48 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id NAA13455; Thu, 9 Dec 1999 13:02:51 +0100 (CET) (envelope-from alex) Date: Thu, 9 Dec 1999 13:02:51 +0100 From: Alexander Langer To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: Is there any way to use ATAPI CD-R? Message-ID: <19991209130251.A7398@cichlids.cichlids.com> Mail-Followup-To: "Andrey A. Chernov" , current@FreeBSD.ORG References: <19991208211624.A6005@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991208211624.A6005@nagual.pp.ru>; from ache@nagual.pp.ru on Wed, Dec 08, 1999 at 09:16:24PM +0300 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Andrey A. Chernov (ache@nagual.pp.ru): > As I see by quick check, CD-related soft from ports understand SCSI only. > Does anybody use new ATAPI CD-R (acd)? If yes, please tell me how. Take a look at /usr/share/examples/atapi/burn* Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 5:18:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id EF66D155F1 for ; Thu, 9 Dec 1999 05:18:54 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id C5ED02DC09; Thu, 9 Dec 1999 14:19:44 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 90C737811; Thu, 9 Dec 1999 14:16:25 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 8C0A410E10; Thu, 9 Dec 1999 14:16:25 +0100 (CET) Date: Thu, 9 Dec 1999 14:16:25 +0100 (CET) From: Andrzej Bialecki To: Marcel Moolenaar Cc: current@FreeBSD.org Subject: Re: why 'The legacy aout build' was removed from current ? In-Reply-To: <384F8633.F40337BC@scc.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Dec 1999, Marcel Moolenaar wrote: > > Please see Netscape plugin port (ports/www/flashplugin) to find > > out why we still have to need a.out support. > > The port has nothing to do with building a legacy a.out world and > consequently works fine (yes, I tested it :-) Not really. You have to have a.out crt0.o and friends to be able to link it. You probably have some old versions around in your system, but they are not built by "world" target. Hence, they are not a part of binary distrib. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 5:33:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 0E2061531C for ; Thu, 9 Dec 1999 05:33:47 -0800 (PST) (envelope-from forrie@forrie.com) Received: from Forrest (getbent@forrie.ne.mediaone.net [24.128.72.15]) by forrie.net (8.9.3/8.9.3) with ESMTP id IAA41633 for ; Thu, 9 Dec 1999 08:33:44 -0500 (EST) Message-Id: <4.2.2.19991209083218.00a2adb0@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 09 Dec 1999 08:32:54 -0500 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Make world breakage (12/09/99) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Getting this from this morning's make world (after doing a make clean, just for good measure): -------------------------------------------------------------- >>> Rebuilding dependencies -------------------------------------------------------------- cd /usr/src; COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/ bin LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib OBJFORMA T_PATH=/usr/obj/usr/src/tmp/usr/libexec CFLAGS="-nostdinc -O -pipe" PERL5LIB=/usr/l ibdata/perl/5.00503 PATH=/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/loca l/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/ssl/bin:/usr/ X11R6/bin :/usr/local/samba/bin:/usr/local/home/forrie/bin make DESTDIR=/usr/obj/usr/src/tmp I NSTALL="sh /usr/src/tools/install.sh" -f Makefile.inc1 par-depend ===> share/info ===> include ===> include/rpcsvc ===> lib ===> lib/csu/i386-elf rm -f .depend mkdep -f .depend -a -nostdinc -I/usr/obj/usr/src/tmp/usr/include /usr/src/lib/cs u/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S mkdep -f .depend -a -nostdinc -I/usr/obj/usr/src/tmp/usr/include /usr/src/lib/csu/ i386-elf/crt1.c /usr/src/lib/csu/i386-elf/crtbegin.c /usr/src/lib/csu/i386-elf/crtend .c In file included from /usr/src/lib/csu/i386-elf/crt1.c:32: /usr/obj/usr/src/tmp/usr/include/stddef.h:39: machine/ansi.h: No such file or directo ry In file included from /usr/src/lib/csu/i386-elf/crt1.c:33: /usr/obj/usr/src/tmp/usr/include/stdlib.h:39: sys/cdefs.h: No such file or directory /usr/obj/usr/src/tmp/usr/include/stdlib.h:41: machine/ansi.h: No such file or directo ry /usr/src/lib/csu/i386-elf/crtbegin.c:28: sys/cdefs.h: No such file or directory /usr/src/lib/csu/i386-elf/crtend.c:28: sys/cdefs.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/lib/csu/i386-elf. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 5:46:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 07D0214C03; Thu, 9 Dec 1999 05:46:14 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id IAA29671; Thu, 9 Dec 1999 08:46:13 -0500 (EST) Date: Thu, 9 Dec 1999 08:46:13 -0500 (EST) From: Daniel Eischen Message-Id: <199912091346.IAA29671@pcnet1.pcnet.com> To: chris@netmonger.net, imp@village.org Subject: Re: HEADSUP: wd driver will be retired! Cc: current@FreeBSD.ORG, julian@whistle.com, msmith@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <19991208150807.A16687@netmonger.net> Christopher Masto writes: > : Right now, I have no sound (not detected), no USB (panic on removal), > : can't use my sio pccard, can't eject my ed pccard, my IDE drives are > : taking hours to dump and fsck, and my TV card is missing every other > : line if I try to use the (not working anyway) closed caption decoder. > > I have some patches for the can't eject the network cards from a user > that I'm trying out and would then need to get committed to the > network layer to properly support if_detach(). > > What's wrong with your sio pccard? Mine works well enough... Mine hasn't worked since a kernel built from Nov 23 sources. It broke sometime between then and December 4th. Just built a new kernel from todays sources, and still no go. pccardd[47]: driver allocation failed for Motorola(MONTANA 33.6 FAX/MODEM): Device not configured My 3c589D luckily still works correctly: ep0: <3Com Etherlink III 3C589> at port 0x240-0x24f irq 9 slot 1 on pccard1 ep0: Ethernet address 00:60:08:8c:32:34 Excerpt from dmesg: pcic0: at irq 3 on isa0 pccard0: on pcic0 pccard1: on pcic0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 ppc0: not probed (disabled) pcm0: at irq 7 drq 1 flags 0x10 on isa0 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled Mounting root from ufs:/dev/wd0s3a pccard: card inserted, slot 0 pccard: card inserted, slot 1 ep0: <3Com Etherlink III 3C589> at port 0x240-0x24f irq 9 slot 1 on pccard1 ep0: Ethernet address 00:60:08:8c:32:34 `pccardc dumpcis` now behaves as `pccardc dumpcore` :-) Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 1 000: 00 Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = 512b, 1 units Tuple #2, code = 0x15 (Version 1 info), length = 39 000: 04 01 4d 6f 74 6f 72 6f 6c 61 00 4d 4f 4e 54 41 010: 4e 41 20 33 33 2e 36 20 46 41 58 2f 4d 4f 44 45 020: 4d 00 56 32 2e 30 00 Version = 4.1, Manuf = [Motorola],card vers = [MONTANA 33.6 FAX/MODEM] Addit. info = [V2.0],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[�],[/ ` [ and much more garbage before dumping core] Email me privately if you need other info. 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 Thu Dec 9 5:49:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 0847315616 for ; Thu, 9 Dec 1999 05:49:03 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11w3w8-0000Q3-00; Thu, 9 Dec 1999 13:48:48 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id OAA58918; Thu, 9 Dec 1999 14:48:56 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <384FB348.2AABDE76@scc.nl> Date: Thu, 09 Dec 1999 14:48:56 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrzej Bialecki Cc: current@FreeBSD.org Subject: Re: why 'The legacy aout build' was removed from current ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > > On Thu, 9 Dec 1999, Marcel Moolenaar wrote: > > > > Please see Netscape plugin port (ports/www/flashplugin) to find > > > out why we still have to need a.out support. > > > > The port has nothing to do with building a legacy a.out world and > > consequently works fine (yes, I tested it :-) > > Not really. You have to have a.out crt0.o and friends to be able to link > it. You probably have some old versions around in your system, but they > are not built by "world" target. Hence, they are not a part of binary > distrib. Yes, I have c++rt0.o in /usr/lib/aout. If I didn't have it, I would be given directions on how to get it (from the port): 1. extract /usr/src/lib (distribution files: src/slib.??) 2. cd /usr/src/lib/csu/i386 3. make depend 4. make OBJFORMAT=aout clean all install -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 5:57:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 8709814A11 for ; Thu, 9 Dec 1999 05:57:32 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id OAA73178 for current@FreeBSD.org; Thu, 9 Dec 1999 14:52:06 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 09 Dec 1999 14:52:02 +0100 From: Marcel Moolenaar Message-ID: <384FB402.A6ABE5B3@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <4.2.2.19991209083218.00a2adb0@216.67.12.69> Subject: Re: Make world breakage (12/09/99) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forrest Aldrich wrote: > > Getting this from this morning's make world (after doing a make clean, just > for good measure): re-cvsup. The problem should be fixed already. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6: 9: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 79C6C15617 for ; Thu, 9 Dec 1999 06:08:55 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id AFAC22DC0A; Thu, 9 Dec 1999 15:09:45 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id E05C87812; Thu, 9 Dec 1999 15:06:20 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id DE16810E10; Thu, 9 Dec 1999 15:06:20 +0100 (CET) Date: Thu, 9 Dec 1999 15:06:20 +0100 (CET) From: Andrzej Bialecki To: Marcel Moolenaar Cc: current@FreeBSD.org Subject: Re: why 'The legacy aout build' was removed from current ? In-Reply-To: <384FB348.2AABDE76@scc.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Dec 1999, Marcel Moolenaar wrote: > Andrzej Bialecki wrote: > > > > On Thu, 9 Dec 1999, Marcel Moolenaar wrote: > > > > > > Please see Netscape plugin port (ports/www/flashplugin) to find > > > > out why we still have to need a.out support. > > > > > > The port has nothing to do with building a legacy a.out world and > > > consequently works fine (yes, I tested it :-) > > > > Not really. You have to have a.out crt0.o and friends to be able to link > > it. You probably have some old versions around in your system, but they > > are not built by "world" target. Hence, they are not a part of binary > > distrib. > > Yes, I have c++rt0.o in /usr/lib/aout. If I didn't have it, I would be > given directions on how to get it (from the port): > > 1. extract /usr/src/lib (distribution files: src/slib.??) > 2. cd /usr/src/lib/csu/i386 > 3. make depend > 4. make OBJFORMAT=aout clean all install True. But this adds a dependency for this port on the src/lib tree. I was thinking about average people that have binary distribution + kernel sources. They are screwed. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6:34:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from thoth.mch.sni.de (thoth.mch.sni.de [192.35.17.2]) by hub.freebsd.org (Postfix) with ESMTP id 1ADAD15617 for ; Thu, 9 Dec 1999 06:33:48 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer thoth.mch.sni.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by thoth.mch.sni.de (8.9.3/8.9.3) with ESMTP id PAA09793 for ; Thu, 9 Dec 1999 15:33:21 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id PAA02715 for ; Thu, 9 Dec 1999 15:33:21 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id PAA98457 for ; Thu, 9 Dec 1999 15:33:21 +0100 (CET) Date: Thu, 9 Dec 1999 15:33:20 +0100 From: Andre Albsmeier To: Alfred Perlstein Cc: Warner Losh , Garance A Drosihn , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test Message-ID: <19991209153320.A62121@internal> References: <199912072106.OAA44391@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bright@wintelcom.net on Tue, Dec 07, 1999 at 02:55:37PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 07-Dec-1999 at 14:55:37 -0800, Alfred Perlstein wrote: I think the (really big) security hole can be closed by not doing the chown/chmod commands. I inserted them because I wanted the file in the spool directory to appear exactly as if lpr would have copied it. I am currently running the patch with the chown/chmod removed and lpd doesn't seem to have any problems with it. The side effect now is that the file in the spool directory keeps it's permissions. I don't think that this is a problem because if the file was set to 666 by the creator before, he doesn't care a lot about it anyway :-) What do people think about this? Alfred, Warner ? For better reference, here is the current patch: *** lpr.c.ORI Thu Dec 9 15:30:18 1999 --- lpr.c Thu Dec 9 15:30:35 1999 *************** *** 370,375 **** --- 370,405 ---- } if (sflag) printf("%s: %s: not linked, copying instead\n", name, arg); + /* + * If lpr was invoked with -r we try to move the file to + * be printed instead of copying and deleting it later. + * This works if the file and lpd's spool directory are + * on the same filesystem as it is often the case for files + * printed by samba or pcnfsd. In this case, a lot of I/O + * and temporary disk space can be avoided. Otherwise, we + * will continue normally. + */ + if (f) { /* file should be deleted */ + seteuid(euid); /* needed for rename() */ + if (!rename(arg, dfname)) { + int i; + #if 0 + chown(dfname, userid, getegid()); + chmod(dfname, S_IRUSR | S_IWUSR | + S_IRGRP | S_IWGRP); + #endif + seteuid(uid); /* restore old uid */ + if (format == 'p') + card('T', title ? title : arg); + for (i = 0; i < ncopies; i++) + card(format, &dfname[inchar-2]); + card('U', &dfname[inchar-2]); + card('N', arg); + nact++; + continue; + } + seteuid(uid); /* restore old uid */ + } if ((i = open(arg, O_RDONLY)) < 0) { printf("%s: cannot open %s\n", name, arg); } else { > On Tue, 7 Dec 1999, Warner Losh wrote: > > > I've been reviewing this patch with someone and I think the last > > version is ready to commit. I'll take a look at my tree to make > > sure. > > please do not, the patch in PR 11997 introduces a major security flaw. > > someone can hardlink to any file and clobber it with a file owned by > them: > > try this: > > as root: > > # cd /var/tmp ; touch rootfile ; chown root:wheel rootfile ; chmod 600 rootfile > > as a user: > > % cd /var/tmp ; echo foo > foo > % lpr -r foo > sleeping > > in another session as user: > > % rm foo ; ln rootfile foo > > wait a second... > > # ls -l rootfile > -rw-rw---- 3 user daemon 5 Dec 7 13:38 rootfile > # cat rootfile > foo > # > > ouch! > > -Alfred > > use this patch to make the race condition apparrent: > > > Index: usr.sbin/lpr/lpr/lpr.c > =================================================================== > RCS file: /home/ncvs/src/usr.sbin/lpr/lpr/lpr.c,v > retrieving revision 1.27.2.2 > diff -u -u -r1.27.2.2 lpr.c > --- lpr.c 1999/08/29 15:43:29 1.27.2.2 > +++ lpr.c 1999/12/08 01:47:47 > @@ -370,6 +370,27 @@ > } > if (sflag) > printf("%s: %s: not linked, copying instead\n", name, arg); > + if( f ) { /* means that the file should be deleted */ > + printf("sleeping\n"); > + sleep(5); > + printf("done.\n"); > + seteuid(euid); /* needed for rename() to succeed */ > + if( ! rename( arg, dfname ) ) { > + register int i; > + chmod( dfname, S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP ); > + chown( dfname, userid, getgrnam("daemon")->gr_gid ); > + seteuid(uid); > + if (format == 'p') > + card('T', title ? title : arg); > + for (i = 0; i < ncopies; i++) > + card(format, &dfname[inchar-2]); > + card('U', &dfname[inchar-2]); > + card('N', arg); > + nact++; > + continue; > + } > + seteuid(uid); > + } > if ((i = open(arg, O_RDONLY)) < 0) { > printf("%s: cannot open %s\n", name, arg); > } else { > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- "In a world without walls and fences, who needs windows and gates?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6:36:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 21C8C15642 for ; Thu, 9 Dec 1999 06:36:43 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 11w4gT-0005FY-00; Thu, 9 Dec 1999 14:36:41 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id PAA25690; Thu, 9 Dec 1999 15:36:37 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <384FBE75.68B333BC@scc.nl> Date: Thu, 09 Dec 1999 15:36:37 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrzej Bialecki Cc: current@FreeBSD.org Subject: Re: why 'The legacy aout build' was removed from current ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > > > 1. extract /usr/src/lib (distribution files: src/slib.??) > > 2. cd /usr/src/lib/csu/i386 > > 3. make depend > > 4. make OBJFORMAT=aout clean all install > > True. But this adds a dependency for this port on the src/lib tree. I was > thinking about average people that have binary distribution + kernel > sources. They are screwed. The dependency always existed, because people without src/lib cannot make legacy a.out as part of their world, for which you also need more than kernel sources alone :-) The point here is that you don't need a legacy a.out build as part of your world to get this port working. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6:50:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from histidine.utmb.edu (histidine.utmb.edu [129.109.59.80]) by hub.freebsd.org (Postfix) with ESMTP id 8AA7F155DA; Thu, 9 Dec 1999 06:50:44 -0800 (PST) (envelope-from bdodson@scms.utmb.EDU) Received: (from bdodson@localhost) by histidine.utmb.edu (8.9.3/8.9.3) id IAA06875; Thu, 9 Dec 1999 08:50:42 -0600 (CST) (envelope-from bdodson) Date: Thu, 9 Dec 1999 08:50:42 -0600 (CST) Message-Id: <199912091450.IAA06875@histidine.utmb.edu> From: "M. L. Dodson" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Steve Kargl Cc: kris@hub.freebsd.org (Kris Kennaway), current@FreeBSD.ORG Subject: Re: Reaping fortran cruft In-Reply-To: <199912090716.XAA43044@troutmask.apl.washington.edu> References: <199912090716.XAA43044@troutmask.apl.washington.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl writes: > Kris Kennaway wrote: > > On Wed, 8 Dec 1999, Steve Kargl wrote: > > > > > I was going to fix fsplit. Yes, I program in Fortran (note the > > > proper spelling of Fortran). No, I don't use fsplit. > > > > A rewrite is certainly desperately needed :) > > > > > We might also want to remove fpr(1). > > > > Noted. Are there any other crufty Fortran candidates you can do without? > > No. I haven't found any other programs. > > > If no-one disagrees with this, I'll move them both to ports (probably in a > > combined fortran-utils port) in a couple of days. Would you like to be the > > maintainer? :) > > The dates in fsplit suggest that it hasn't seen any development > since 1983. The functionality it provided then can be accomplished > with vi and cp. > Yes, and one can do text editing with cat and sed. Fsplit has its place, as does fpr. Please keep them as ports rather than nuke them completely. Being in the attic is substantially more difficult for casual *BSD users than being available as a port. I wholeheartedly endorse a fortran-utils port. > I haven't looked at fpr, but you can get fancy program listings > with a2ps (and probably apsfilter) which is (are) already in the > ports collections. > Yes, but as a shell script it is easier to teach apsfilter about Fortran if fpr is available to do the heavy lifting. That is easier than hacking a2ps. I do not find any mention of Fortran knowledge in the man page for the version of a2ps-letter I installed on this workstation about 6 weeks ago. (I used the port.) Sorry. I'm all in favor of this bike shed but disagree with the suggested paint color. > I say kill them (of course asbestos under garments might be needed). > It should be noted that cvs will maintain a copy of both in the attic, > so anyone who wants the source can get it. > > -- > Steve > Bud Dodson -- M. L. Dodson bdodson@scms.utmb.edu 409-772-2178 FAX: 409-772-1790 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6:51:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 08A3F15607; Thu, 9 Dec 1999 06:51:52 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991208214832.58332@mojave.sitaranetworks.com> Date: Wed, 8 Dec 1999 21:48:32 -0500 From: Greg Lehey To: Poul-Henning Kamp , Kris Kennaway Cc: current@FreeBSD.ORG Subject: Fallback paths (was: HEADSUP: wd driver will be retired!) Reply-To: Greg Lehey References: <34789.944683236@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <34789.944683236@critter.freebsd.dk>; from Poul-Henning Kamp on Wed, Dec 08, 1999 at 09:00:36PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 8 December 1999 at 21:00:36 +0100, Poul-Henning Kamp wrote: > In message , Kris Ken > naway writes: >> On Wed, 8 Dec 1999, Poul-Henning Kamp wrote: >> >>> Update your /etc/fstab (use /dev/ad* instead of /dev/wd* or >>> /dev/rwd* >> >> Can't we keep the same device names? I thought that was the original plan >> way back when, once the new driver was ready for prime-time. >> >> Also, perhaps we should have a changing-over period where the old drivers >> are still available under a new name - until recently, Soren was >> advertising the driver as "WARNING: This is pre-alpha code and may trash >> your filesystems", etc, which may well have limited his testing base (it >> certainly scared me off). I'm all for moving forward, but I'd hate to >> eliminate a fallback path in case the transition proves less than smooth. > > The fallback path is not eliminated, and may never be, but it may become > rather uncomfortable to linger on it longer than you absolutely need to. Would you care to expand on that statement? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6:52:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 10F6E15254; Thu, 9 Dec 1999 06:52:15 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991208214001.56508@mojave.sitaranetworks.com> Date: Wed, 8 Dec 1999 21:40:01 -0500 From: Greg Lehey To: Brad Knowles , Mike Smith , Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Reply-To: Greg Lehey References: <199912081856.KAA06231@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: ; from Brad Knowles on Wed, Dec 08, 1999 at 08:23:24PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 8 December 1999 at 20:23:24 +0100, Brad Knowles wrote: > At 10:56 AM -0800 1999/12/8, Mike Smith wrote: > >> The right attitude to be taking now is "here is where the ata drivers >> still fall down" or "here are patches to them to replace this >> functionality". Think about the longer-term goals here folks. > > I understand where Julian is coming from. In fact, my initial > reaction was the same. However, I have reluctantly been converted to > be in agreement with Mike and Søren (among others). > > This is -CURRENT. It pains me to say it, but anyone trying to > run anything "useful" on -CURRENT gets what they deserve. This is > the only place where we can make clean breaks with the past, and as > painful as that can be, we simply have to do that occasionally. Next month it'll be -RELEASE. This isn't the time to remove such significant functionality. If it weren't for that, I'd agree with you. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6:53: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 98108154A5; Thu, 9 Dec 1999 06:53:00 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991208215049.46304@mojave.sitaranetworks.com> Date: Wed, 8 Dec 1999 21:50:49 -0500 From: Greg Lehey To: Mike Smith , Christopher Masto Cc: Julian Elischer , current@FreeBSD.ORG Subject: Continuity (was: HEADSUP: wd driver will be retired!) Reply-To: Greg Lehey References: <19991208150807.A16687@netmonger.net> <199912082052.MAA00517@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199912082052.MAA00517@mass.cdrom.com>; from Mike Smith on Wed, Dec 08, 1999 at 12:52:37PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 8 December 1999 at 12:52:37 -0800, Mike Smith wrote: >> On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: >>>> You shouldn't remove a function until it has been properly replaced. >>>> A very simple concept some people seem to have trouble grasping. >>> >>> Actually, that's not at all correct. We've demonstrated a number of >>> times now that you reach a point where a brutal cutover is required. >>> Failure to do so leaves people clutching the old security blanket for >>> years, and massively impedes further development. >> >> Unfortunately, FreeBSD has far too many examples of a working system >> being replaced with a less functional system. Just off the top of my >> head, there were the SCSI drivers lost to CAM, the PCCARD system, >> sound drivers, and now ATA. > > Actually, most of this is histrionics. CAM didn't lose us SCSI drivers; > we actually _gained_ from it. If you were the owner of a number of older SCSI host adaptors, you lost. > We haven't "lost" the pccard system at all, We certainly seem to have mislaid it. My modem has got lost again, and the number of supported cards is greatly diminished. > and the new sound code is on a feature-par with both of the old > ones. I don't have a comparison there. > What we need here is a commitment to these new initiatives, not a > lot of fence-sitting and clutching our knitting to our chests. All > of these initiatives were started to deal with massive problems in > the subsystems they replace; clinging to the old code rather than > getting on-board and helping with the new code directly impedes the > resolution of these problems. I don't think this is an accurate view of the objections. > Again, I say, think of what we're trying to achieve here. One thing, I hope, is continuity. I don't see this helping. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6:53:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 6C9AF1568F; Thu, 9 Dec 1999 06:53:11 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991208215409.48501@mojave.sitaranetworks.com> Date: Wed, 8 Dec 1999 21:54:09 -0500 From: Greg Lehey To: "Jonathan M. Bresler" , chris@netmonger.net Cc: msmith@FreeBSD.ORG, julian@whistle.com, current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Reply-To: Greg Lehey References: <19991208180457.B1282@netmonger.net> <19991208232349.A244B1558B@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19991208232349.A244B1558B@hub.freebsd.org>; from Jonathan M. Bresler on Wed, Dec 08, 1999 at 03:23:49PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 8 December 1999 at 15:23:49 -0800, Jonathan M. Bresler wrote: > > [snip] >> We gained quite a bit from it, but let's not rewrite history. I >> remember quite clearly that there was a very popular Adaptec SCSI >> controller missing when the switch to CAM was made, and a lot of > [snip] > > we lost teh aic controller at that time. > > [snip] >> Again, this is not accurate. I have a laptop with which, two months >> ago, I could use my LinkSys ethernet card, and I could use my digital > > then we need to get your LinkSys ethernet card support fixed. > i am using one to write this message. mine is a LinkSys 10/100 PCMCIA > card. what do you have? What version of -CURRENT are you using? Mine is a PCMPC200, and I haven't been able to get it to work for 6 weeks. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6:55:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id CD012155FF; Thu, 9 Dec 1999 06:55:18 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991208213714.33783@mojave.sitaranetworks.com> Date: Wed, 8 Dec 1999 21:37:14 -0500 From: Greg Lehey To: Soren Schmidt , Alexander Leidinger Cc: sheldonh@uunet.co.za, Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Reply-To: Greg Lehey References: <199912081421.PAA05970@Magelan.Leidinger.net> <199912081609.RAA53062@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <199912081609.RAA53062@freebsd.dk>; from Soren Schmidt on Wed, Dec 08, 1999 at 05:09:39PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 8 December 1999 at 17:09:39 +0100, Soren Schmidt wrote: > It seems Alexander Leidinger wrote: >> >> It isn´t only a matter of providing feedback... the maintainer also has >> to work on it. > > Yeah, right... > >> I offered feedback in every mail regarding my problem with ata & >> msdos-ZIPs (they aren´t accessible), but most of the time I havn´t got a >> reply (Søren replied recently to Fritz Heinrichmeyer, he has the same >> problem). >> I´m not able to test it at the moment, but I havn´t seen a cvs-all >> message which said "Problems with MSDOS formated ZIPs fixed". I assume >> it isn´t fixed and I want to use the wd driver until it´s fixed. >> >> Poul-Henning: please wait until Søren fixed the problems some users have >> (we didn´t want to loose features, right?). >> >> Søren: I didn´t want to flame you, I only want to convince Paul-Henning >> to wait until you have time to fix those bugs. > > Welcome to the real world, I've promised to look at this and I will, > but a day has only so many hours. We're not talking about deadlines here, we're talking about sequences: 1. Write a new driver with sexy new features. 2. Make sure it can do everything the old driver can do. 3. Remove the old driver. At the moment, we seem to be trying to do (3) before (2). No question of hours/day or anything else. > Instead of complaining, help the project, when have you last closed > a PR ?? It's been a while. The day has only so many hours. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6:57:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id AE3A3154A5; Thu, 9 Dec 1999 06:57:27 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991208214634.48366@mojave.sitaranetworks.com> Date: Wed, 8 Dec 1999 21:46:34 -0500 From: Greg Lehey To: Soren Schmidt , Christopher Masto Cc: Mike Smith , Julian Elischer , current@FreeBSD.ORG, johnh@sitaranetworks.com Subject: Progress or procedure? (was: HEADSUP: wd driver will be retired!) Reply-To: Greg Lehey References: <19991208150807.A16687@netmonger.net> <199912082131.WAA31612@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199912082131.WAA31612@freebsd.dk>; from Soren Schmidt on Wed, Dec 08, 1999 at 10:31:22PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 8 December 1999 at 22:31:22 +0100, Soren Schmidt wrote: > It seems Christopher Masto wrote: >> On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: >>>> You shouldn't remove a function until it has been properly replaced. >>>> A very simple concept some people seem to have trouble grasping. >>> >>> Actually, that's not at all correct. We've demonstrated a number of >>> times now that you reach a point where a brutal cutover is required. >>> Failure to do so leaves people clutching the old security blanket for >>> years, and massively impedes further development. >> >> Unfortunately, FreeBSD has far too many examples of a working system >> being replaced with a less functional system. Just off the top of my >> head, there were the SCSI drivers lost to CAM, the PCCARD system, >> sound drivers, and now ATA. > > Hmm, well, if you want support for any of the new ata-66 controllers > you have to use the ata driver, so you loose some you win some. > Given that my patch for the SiS works and a patch I got from Luoqi, > the ONLY support you are loosing is the Cyrix. If we maintain wd for the Cyrix people, we don't lose anything. >> Right now, I have no sound (not detected), no USB (panic on removal), >> can't use my sio pccard, can't eject my ed pccard, my IDE drives are >> taking hours to dump and fsck, and my TV card is missing every other >> line if I try to use the (not working anyway) closed caption decoder. >> >> Now, I running -current on this machine, I've asked for problems, and >> I have them. I try to fix them and/or send decent bug reports when I >> can, and I don't piss and moan when something breaks, because it's >> -current. I just get a feeling sometimes like we're moving forward on >> a treadmill that's moving backward just slightly faster. > > Well, progress doesn't come for free you know, somebody has to do > the hard work of actually implementing things. So if you think its > going too slowly, do something about it, help out where you can, but > complaining isn't helping anybody :) We're not talking progress here, we're talking procedure. Nobody doubts that the new driver will be better than the old one, and nobody doubts that the new one should be the default (at least, I haven't seen anybody doubting it). But why throw away functionality? People need time to adapt, and we have a perfectly good solution: keep the wd driver for 4.0, make it clear it's deprecated, and remove it (functionality permitting) for 4.1. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6:58:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id A401515680; Thu, 9 Dec 1999 06:58:13 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991208213429.28285@mojave.sitaranetworks.com> Date: Wed, 8 Dec 1999 21:34:29 -0500 From: Greg Lehey To: Soren Schmidt , "Richard Seaman, Jr." Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Breaking DMA support for multiple chipsets? (was: HEADSUP: wd driver will be retired!) Reply-To: Greg Lehey References: <19991208072728.K44207@tar.com> <199912081402.PAA23215@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199912081402.PAA23215@freebsd.dk>; from Soren Schmidt on Wed, Dec 08, 1999 at 03:02:37PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 8 December 1999 at 15:02:37 +0100, Soren Schmidt wrote: > It seems Richard Seaman, Jr. wrote: >> On Wed, Dec 08, 1999 at 12:55:35PM +0100, Poul-Henning Kamp wrote: >>> >>> In a few days time the wd driver will be retired from FreeBSDs >>> i386 architecture. >>> >> >> Since the ata driver does not support DMA on my chipset, at >> least the last time I tried (SiS 5591), it would be nice >> to leave the wd driver in the tree for a while, even if its >> not the default. Possibly there are others in the same boat? > > OK, you asked for it, following is a patch to support the > sis 5591 chipset. Remember this is done blindfolded, I > have no HW to test on, but you guys do :) > > Let me know what happens... OK. Let's defer removing wd until we know that ata DMA works on these platforms. We'll have a lot of unhappy customers otherwise, myself (wearing another hat) included. If nobody else gets there first, I'll look at this next week. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6:58:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from dead-end.net (dead-end.net [216.15.131.2]) by hub.freebsd.org (Postfix) with ESMTP id 02DFF15675; Thu, 9 Dec 1999 06:58:03 -0800 (PST) (envelope-from rock@dead-end.net) Received: (from nopriv@localhost) by dead-end.net (8.9.3/DEAD-END/1999102300-Deliver) id PAA21888; Thu, 9 Dec 1999 15:57:54 +0100 (CET) (envelope-from rock@dead-end.net) Date: Thu, 9 Dec 1999 15:57:54 +0100 (CET) From: "D. Rock" Message-Id: <199912091457.PAA21888@dead-end.net> X-Authentication-Warning: dead-end.net: nopriv set sender to rock@dead-end.net using -f To: Daniel Eischen Reply-To: rock@dead-end.net Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="-MOQ94475147400318d51268831008a1842cc1db59fb8" User-Agent: IMP/PHP3 Imap webMail Program 2.0.11 Subject: pccard sio problems (Re: HEADSUP: wd driver will be retired!) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. ---MOQ94475147400318d51268831008a1842cc1db59fb8 Content-Type: text/plain Content-Transfer-Encoding: 8bit Zitiere Daniel Eischen : > > In message <19991208150807.A16687@netmonger.net> Christopher Masto > writes: > > : Right now, I have no sound (not detected), no USB (panic on removal), > > : can\\\\\\\\\\\\\\\'t use my sio pccard, can\\\\\\\\\\\\\\\'t eject my ed pccard, my IDE drives are > > : taking hours to dump and fsck, and my TV card is missing every other > > : line if I try to use the (not working anyway) closed caption decoder. > > > > I have some patches for the can\'t eject the network cards from a user > > that I\'m trying out and would then need to get committed to the > > network layer to properly support if_detach(). > > > > What\'s wrong with your sio pccard? Mine works well enough... > > Mine hasn\'t worked since a kernel built from Nov 23 sources. It > broke sometime between then and December 4th. Just built a new > kernel from todays sources, and still no go. > > pccardd[47]: driver allocation failed for Motorola (MONTANA 33.6 FAX/MODEM): > Device not configured > I also had problems with latest -current. After a little debugging I noticed that sio.c doesn\'t include \"card.h\" which defines NCARD, so the pccard stuff isn\'t compiled in. I added that line to sio.c, recompiled, and sio for pccard was at least again partially functional. I have two pccard sio devices, one seems to work, the other one freezes the machine during a simple \"stty -a < /dev/cuaaX\". I have attached the CIS information of these cards with my pccard.conf. Ejecting sio also doesn\'t seem to work. The machine is freezed afterwards. I can eject my DLink ed card, but after a re-insertion the driver isn\'t attached any more. Daniel ---MOQ94475147400318d51268831008a1842cc1db59fb8 Content-Type: text/plain; name="cis.crash" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="cis.crash" Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #2, code = 0x15 (Version 1 info), length = 32 000: 04 01 49 6e 74 65 6c 6c 69 67 65 6e 74 00 50 43 010: 4d 43 49 41 20 46 41 58 2b 4d 4f 44 45 4d 00 ff Version = 4.1, Manuf = [Intelligent],card vers = [PCMCIA FAX+MODEM] Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 00 02 01 00 PCMCIA ID = 0x200, OEM ID = 0x1 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 02 00 Serial port/modem Tuple #5, code = 0x22 (Functional EXT), length = 4 000: 00 02 0f 5c Serial interface extension: 16550 UART, Parity - Space,Mark,Odd,Even, Tuple #6, code = 0x22 (Functional EXT), length = 9 000: 05 1f 1f 00 04 00 00 04 00 Modem interface capabilities: Tuple #7, code = 0x22 (Functional EXT), length = 9 000: 06 1f 1f 00 04 00 00 04 00 Modem interface capabilities: Tuple #8, code = 0x22 (Functional EXT), length = 12 000: 02 06 00 3f 1c 03 03 0f 07 00 01 b5 Data modem services available: Tuple #9, code = 0x22 (Functional EXT), length = 8 000: 13 06 00 1f 00 02 00 b5 Tuple #10, code = 0x22 (Functional EXT), length = 8 000: 23 06 00 1f 00 02 00 b5 Tuple #11, code = 0x1a (Configuration map), length = 5 000: 01 27 80 ff 67 Reg len = 2, config register addr = 0xff80, last config = 0x27 Registers: XXX--XX- Tuple #12, code = 0x1b (Configuration entry), length = 19 000: cf 41 99 79 55 3d 86 46 26 4c aa 60 f8 03 07 f0 010: bc 86 28 Config index = 0xf(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 3.5 x 10mA Max current average over 1 second: 1 x 100mA, ext = 0x46 Max current average over 10 ms: 2 x 100mA Power down supply current: 4.5 x 1mA Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3f8 block length = 0x8 IRQ modes: Level, Pulse, Shared IRQs: 4 5 6 7 10 11 12 13 15 Max twin cards = 0 Misc attr: (Audio-BVD2) (Power down supported) Tuple #13, code = 0x1b (Configuration entry), length = 7 000: 17 08 aa 60 f8 02 07 Config index = 0x17 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2f8 block length = 0x8 Tuple #14, code = 0x1b (Configuration entry), length = 7 000: 1f 08 aa 60 e8 03 07 Config index = 0x1f Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3e8 block length = 0x8 Tuple #15, code = 0x1b (Configuration entry), length = 7 000: 27 08 aa 60 e8 02 07 Config index = 0x27 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2e8 block length = 0x8 Tuple #16, code = 0xff (Terminator), length = 0 ---MOQ94475147400318d51268831008a1842cc1db59fb8 Content-Type: text/plain; name="cis.working" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="cis.working" Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #2, code = 0x15 (Version 1 info), length = 15 000: 04 01 47 53 4d 00 44 53 41 20 43 61 72 64 00 Version = 4.1, Manuf = [GSM],card vers = [DSA Card] Addit. info = [],[ð],[],[],[],[],[],[€ð$],[],[],[],[],[],[],[],[],[],[],[],[°ð],[],[],[],[],[],[ ðà™PõPª`øp¼ž`Ðð],[],[],[],[],[],[Àð!ª`ø],[],[],[],[],[],[],[],[],[ðð],[],[],[],[],[],[àð"ª`è],[],[],[],[],[],[],[],[],[ñ],[],[],[],[],[],[],[ñ#ª`è],[],[],[],[],[],[],[],[],[0ñ],[],[],[],[],[],[ ñ$ @],[],[],[],[],[],[],[],[],[],[],[Pñ!],[],[],[],[],[],[@ñ],[],[],[],[],[],[],[],[],[],[],[],[],[],[`ñ],[],[],[],[],[],[],[],[],[],[],[],[],[],[] Tuple #3, code = 0x1a (Configuration map), length = 5 000: 01 24 00 01 03 Reg len = 2, config register addr = 0x100, last config = 0x24 Registers: XX------ Tuple #4, code = 0x1b (Configuration entry), length = 16 000: e0 01 99 50 f5 50 05 aa 60 f8 03 07 70 bc 9e 60 Config index = 0x20(default) Interface byte = 0x1 (I/O) Vcc pwr: Max current average over 1 second: 8 x 10mA, ext = 0x50 Power down supply current: 1 x 10mA Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3f8 block length = 0x8 IRQ modes: Level, Pulse IRQs: 4 5 6 10 11 12 13 15 Max twin cards = 0 Misc attr: (Power down supported) Tuple #5, code = 0x1b (Configuration entry), length = 7 000: 21 08 aa 60 f8 02 07 Config index = 0x21 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2f8 block length = 0x8 Tuple #6, code = 0x1b (Configuration entry), length = 7 000: 22 08 aa 60 e8 03 07 Config index = 0x22 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3e8 block length = 0x8 Tuple #7, code = 0x1b (Configuration entry), length = 7 000: 23 08 aa 60 e8 02 07 Config index = 0x23 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2e8 block length = 0x8 Tuple #8, code = 0x1b (Configuration entry), length = 5 000: 24 08 a0 40 07 Config index = 0x24 Card provides address decode, 8 Bit I/O only I/O address # 1: block length = 0x8 Tuple #9, code = 0x21 (Functional ID), length = 2 000: 02 01 Serial port/modem - POST initialize Tuple #10, code = 0x14 (No link), length = 0 Tuple #11, code = 0xff (Terminator), length = 0 ---MOQ94475147400318d51268831008a1842cc1db59fb8 Content-Type: text/plain; name="pccard.conf" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="pccard.conf" # Sample PCCARD configuration file # # Removing all IRQ conflicts from this file can't be done because of some # IRQ-selfish PC-cards. So if you want to use some of these cards in # your machine, you will be forced to modify their IRQ parameters from # the following list. # # IRQ == 0 means "allocate free IRQ from IRQ pool" # IRQ == 16 means "do not use IRQ (e.g. PIO mode)" # # $FreeBSD: src/etc/pccard.conf.sample,v 1.50 1999/11/21 09:48:15 msmith Exp $ # Generally available IO ports io 0x240-0x400 # Generally available IRQs (Built-in sound-card owners remove 5) irq 11 15 # Available memory slots memory 0xd4000 96k #debuglevel 9 card "D-Link" "DE-660" config 0x20 "ed0" ? 0x10 insert /etc/pccard_ether ed0 remove /etc/pccard_ether ed0 delete down card "Intelligent" "PCMCIA FAX+MODEM" config 0x1f "sio2" ? # config 0x27 "sio3" ? card "GSM" "DSA Card" config 0x23 "sio3" ? # config 0x22 "sio2" ? ---MOQ94475147400318d51268831008a1842cc1db59fb8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 6:59:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id CE97115660; Thu, 9 Dec 1999 06:59:27 -0800 (PST) (envelope-from netchild@Leidinger.net) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id PAA14297318; Thu, 9 Dec 1999 15:58:59 +0100 (CET) Received: from Magelan.Leidinger.net (maxtnt-144.telip.uni-sb.de [134.96.71.15]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id PAA02075; Thu, 9 Dec 1999 15:59:07 +0100 (CET) Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id PAA42318; Thu, 9 Dec 1999 15:45:10 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <199912091445.PAA42318@Magelan.Leidinger.net> Date: Thu, 9 Dec 1999 15:45:09 +0100 (CET) From: Alexander Leidinger Subject: Re: HEADSUP: wd driver will be retired! To: sobomax@altavista.net Cc: sos@freebsd.dk, phk@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <384EE77A.FC42FD9@altavista.net> 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 On 9 Dec, Maxim Sobolev wrote: > Excuse me for possible off-topic, but I have what is seems for me fresh idea > about this question. Why do not remove from wd driver support for chipsets > already implemented/tested in ata driver? Thus both clans would satisfied > i.e. users with unsupported by ata chips still will have a chance, while all > other will be encouraged to use and test better (IMHO) ata... Eventually at There also exist cases where the chipset is supported but a particular functionality isn´t supported yet (in my case it´s the possibility to access MS-DOS formated ZIP-disks, harddisk access works well, and I´m not the only one with this problem (not counting the people which have not tried to use the ata driver but need to access MS-DOS-ZIPs too)). And I think it´s better to spend someones time with other issues than with digging into the wd driver. Bye, Alexander. -- Go fascinate someone else. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 7: 4:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2A61F1511A; Thu, 9 Dec 1999 07:04:22 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id QAA81292; Thu, 9 Dec 1999 16:03:58 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912091503.QAA81292@freebsd.dk> Subject: Re: Breaking DMA support for multiple chipsets? (was: HEADSUP: wd driver will be retired!) In-Reply-To: <19991208213429.28285@mojave.sitaranetworks.com> from Greg Lehey at "Dec 8, 1999 09:34:29 pm" To: grog@lemis.com (Greg Lehey) Date: Thu, 9 Dec 1999 16:03:58 +0100 (CET) Cc: dick@tar.com (Richard Seaman Jr.), phk@FreeBSD.ORG (Poul-Henning Kamp), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Greg Lehey wrote: > > OK, you asked for it, following is a patch to support the > > sis 5591 chipset. Remember this is done blindfolded, I > > have no HW to test on, but you guys do :) > > > > Let me know what happens... > > OK. Let's defer removing wd until we know that ata DMA works on these > platforms. We'll have a lot of unhappy customers otherwise, myself > (wearing another hat) included. If nobody else gets there first, I'll > look at this next week. It already being tested, and it works, but at the same tike I found out that the code in the old driver for the sis is schizofrenic, it has one way of setting things up, and another way of reporting how it is set :(, that way it is difficult to compare results from the two drivers.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 7: 6: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.43.150]) by hub.freebsd.org (Postfix) with ESMTP id D83D415687; Thu, 9 Dec 1999 07:05:58 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id QAA01719; Thu, 9 Dec 1999 16:05:38 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: Fallback paths (was: HEADSUP: wd driver will be retired!) In-reply-to: Your message of "Wed, 08 Dec 1999 21:48:32 EST." <19991208214832.58332@mojave.sitaranetworks.com> Date: Thu, 09 Dec 1999 16:05:38 +0100 Message-ID: <1717.944751938@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991208214832.58332@mojave.sitaranetworks.com>, Greg Lehey writes: >> The fallback path is not eliminated, and may never be, but it may become >> rather uncomfortable to linger on it longer than you absolutely need to. > >Would you care to expand on that statement? Apart from the fsck/root/reload issue (for which there is a manual work-around) is the only thing which doesn't work with block devices in /dev. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 7:16:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id B1DA71560A for ; Thu, 9 Dec 1999 07:16:29 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id KAA04891; Thu, 9 Dec 1999 10:16:21 -0500 (EST) Date: Thu, 9 Dec 1999 10:16:21 -0500 (EST) From: "Matthew N. Dodd" To: nick.hibma@jrc.it Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: OHCI weirdness? In-Reply-To: <944736576.webexpressdV2.1b1@mboxes.jrc.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Dec 1999 nick.hibma@jrc.it wrote: > Could you tell me whether the panic appears after a lengthy wait or is > it directly related to a an event like plugging in a device or > starting to talk to it (usbd, ugen, etc.) It happens on bootup during the probe. It didn't look like it was waiting at all. I can unplug the devices and make it panic later when the box is multiuser by running 'usbd -ev' after plugging in a device. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 7:26:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 295251563E; Thu, 9 Dec 1999 07:26:51 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup3-11.iptelecom.net.ua [212.9.226.139]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id RAA03606; Thu, 9 Dec 1999 17:31:00 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id RAA05756; Thu, 9 Dec 1999 17:26:09 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <384FCA0E.C7C2001E@altavista.net> Date: Thu, 09 Dec 1999 17:26:06 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Alexander Leidinger Cc: sos@freebsd.dk, phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! References: <199912091445.PAA42318@Magelan.Leidinger.net> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Leidinger wrote: > On 9 Dec, Maxim Sobolev wrote: > > > Excuse me for possible off-topic, but I have what is seems for me fresh idea > > about this question. Why do not remove from wd driver support for chipsets > > already implemented/tested in ata driver? Thus both clans would satisfied > > i.e. users with unsupported by ata chips still will have a chance, while all > > other will be encouraged to use and test better (IMHO) ata... Eventually at > > There also exist cases where the chipset is supported but a particular > functionality isn´t supported yet (in my case it´s the possibility to > access MS-DOS formated ZIP-disks, harddisk access works well, and I´m > not the only one with this problem (not counting the people which have > not tried to use the ata driver but need to access MS-DOS-ZIPs too)). Does Soren know about that? > And I think it´s better to spend someones time with other issues than > with digging into the wd driver. IMHO not much digging - several #ifdef 0 here and there will do the trick. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 7:35:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id BF36615647 for ; Thu, 9 Dec 1999 07:35:01 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id JAA01435; Thu, 9 Dec 1999 09:34:36 -0600 (CST) (envelope-from dick) Date: Thu, 9 Dec 1999 09:34:36 -0600 From: "Richard Seaman Jr." To: Soren Schmidt Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: Breaking DMA support for multiple chipsets? (was: HEADSUP: wd driver will be retired!) Message-ID: <19991209093436.A782@tar.com> References: <19991208213429.28285@mojave.sitaranetworks.com> <199912091503.QAA81292@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912091503.QAA81292@freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 09, 1999 at 04:03:58PM +0100, Soren Schmidt wrote: > It seems Greg Lehey wrote: > > > OK, you asked for it, following is a patch to support the > > > sis 5591 chipset. Remember this is done blindfolded, I > > > have no HW to test on, but you guys do :) > > > > > > Let me know what happens... > > > > OK. Let's defer removing wd until we know that ata DMA works on these > > platforms. We'll have a lot of unhappy customers otherwise, myself > > (wearing another hat) included. If nobody else gets there first, I'll > > look at this next week. > > It already being tested, and it works, but at the same tike I found > out that the code in the old driver for the sis is schizofrenic, it > has one way of setting things up, and another way of reporting how > it is set :(, that way it is difficult to compare results from > the two drivers.. I think the old wd code was broken on reporting. The reporting was changed from the original submission, when it was committed. See the attached message: From dick@tar.com Thu May 6 15:14:56 1999 Date: Thu, 6 May 1999 15:14:56 -0500 From: "Richard Seaman, Jr." To: grog@freebsd.org Subject: Buglet in SiS support in ide_pci.c Message-ID: <19990506151456.A454@tar.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=tKW2IUtsqtDRztdT X-Mailer: Mutt 0.95.4i Status: RO Content-Length: 1468 Lines: 44 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii I was just installing a new drive on the machine with the SiS 5591 chipset, and noticed strange results on the verbose status probes. It appears to me that the UDMA status register reported somehow got flipped. It appears to only affect the status report in verbose mode, and not the actual setting of the controller. If you would like me to commit this fix, let me know. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ide_pci.c.diff" Index: sys/pci/ide_pci.c =================================================================== RCS file: /home/ncvs/src/sys/pci/ide_pci.c,v retrieving revision 1.33 diff -u -r1.33 ide_pci.c --- ide_pci.c 1999/04/24 20:13:58 1.33 +++ ide_pci.c 1999/05/06 18:36:30 @@ -1161,8 +1161,8 @@ printf ("SiS 5591 status: %s drive %d Ultra DMA %s", unitno < 2 ? "primary" : "secondary", unitno & 1, - (DATC & 0x80) ? "disabled\n" : "enabled"); - if ((DATC & 0x80) == 0) + (DATC & 0x80) ? "enabled" : "disabled\n"); + if (DATC & 0x80) printf (", %d PCICLK data out\n", ((DATC >> 5) & 0x3) + 1); printf ("SiS 5591 status: %s drive %d postwrite %s, prefetch %s prefetch count is %d\n", unitno < 2 ? "primary" : "secondary", --tKW2IUtsqtDRztdT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 7:36:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 4E412150C8 for ; Thu, 9 Dec 1999 07:36:49 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id KAA05399; Thu, 9 Dec 1999 10:36:47 -0500 (EST) Date: Thu, 9 Dec 1999 10:36:47 -0500 (EST) From: "Matthew N. Dodd" To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: MCA support In-Reply-To: <384F76D2.938FD166@cvzoom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Dec 1999, Donn Miller wrote: > Just wondering how far along MCA support is. I tried booting up a > kern.flp from the latest snapshot circa dec. 7. and I got a "Read > error" during boot, which halted the machine. My machine was an IBM > PS/2 model 77s. MCA support isn't in GENERIC and wouldn't be on kern.flp. My m77 has weird problems reading the floppy drive. I'm fairly sure this has everything to do with code in the loader/bootstrap that doesn't like the 2.88M drive. I used the 1.2M drive and it works great. I suspect a normal 1.44M drive would be good too. I've observed problems with the graphics console keyboard. I suspect I'm not doing something about the differences b/t a PS2 keyboard controller and a normal AT controller but I've no idea what needs to be done. The baseboard SCSI on the m77 isn't supported. You'll want an Adaptec AHA-1640. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 7:39:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4522C155F3; Thu, 9 Dec 1999 07:39:23 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id QAA89596; Thu, 9 Dec 1999 16:38:52 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912091538.QAA89596@freebsd.dk> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <384FCA0E.C7C2001E@altavista.net> from Maxim Sobolev at "Dec 9, 1999 05:26:06 pm" To: sobomax@altavista.net Date: Thu, 9 Dec 1999 16:38:52 +0100 (CET) Cc: Alexander@Leidinger.net (Alexander Leidinger), phk@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Maxim Sobolev wrote: > > There also exist cases where the chipset is supported but a particular > > functionality isn_t supported yet (in my case it_s the possibility to > > access MS-DOS formated ZIP-disks, harddisk access works well, and I_m > > not the only one with this problem (not counting the people which have > > not tried to use the ata driver but need to access MS-DOS-ZIPs too)). > > Does Soren know about that? Yes I do, I just have to get my ZIP drive in a machine and find the hours to work on it... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 7:42:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2007114EDC for ; Thu, 9 Dec 1999 07:42:21 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id QAA90420; Thu, 9 Dec 1999 16:42:01 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912091542.QAA90420@freebsd.dk> Subject: Re: Breaking DMA support for multiple chipsets? (was: HEADSUP: wd driver will be retired!) In-Reply-To: <19991209093436.A782@tar.com> from "Richard Seaman Jr." at "Dec 9, 1999 09:34:36 am" To: dick@tar.com (Richard Seaman Jr.) Date: Thu, 9 Dec 1999 16:42:01 +0100 (CET) Cc: grog@lemis.com (Greg Lehey), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Richard Seaman Jr. wrote: > > > > It already being tested, and it works, but at the same tike I found > > out that the code in the old driver for the sis is schizofrenic, it > > has one way of setting things up, and another way of reporting how > > it is set :(, that way it is difficult to compare results from > > the two drivers.. > > I think the old wd code was broken on reporting. The reporting > was changed from the original submission, when it was committed. Yep, but it does mean that people _belive_ they are running UDMA where in fact they aren't, and now they blaim the ata driver for doing worse :( I'm not sure the other values reported are valid either as they are reported differently from what they are set to.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 8:46:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 705DF14FFB for ; Thu, 9 Dec 1999 08:46:21 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991209114541.59531@mojave.sitaranetworks.com> Date: Thu, 9 Dec 1999 11:45:41 -0500 From: Greg Lehey To: Soren Schmidt , "Richard Seaman Jr." Cc: current@FreeBSD.ORG Subject: Re: Breaking DMA support for multiple chipsets? (was: HEADSUP: wd driver will be retired!) Reply-To: Greg Lehey References: <19991209093436.A782@tar.com> <199912091542.QAA90420@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199912091542.QAA90420@freebsd.dk>; from Soren Schmidt on Thu, Dec 09, 1999 at 04:42:01PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 9 December 1999 at 16:42:01 +0100, Soren Schmidt wrote: > It seems Richard Seaman Jr. wrote: >>> >>> It already being tested, and it works, but at the same tike I found >>> out that the code in the old driver for the sis is schizofrenic, it >>> has one way of setting things up, and another way of reporting how >>> it is set :(, that way it is difficult to compare results from >>> the two drivers.. >> >> I think the old wd code was broken on reporting. The reporting >> was changed from the original submission, when it was committed. > > Yep, but it does mean that people _belive_ they are running UDMA > where in fact they aren't, and now they blaim the ata driver > for doing worse :( Well, the wd driver definitely ran DMA on the 5591. And the fix Richard reports is not normally output; IIRC it's only on a verbose boot. On my machine, the driver reports: ide_pci0: irq 14 at device 0.1 on pci0 ... wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xb0ffb0ff on isa0 wdc0: unit 0 (wd0): , LBA, DMA, 32-bit, multi-block-32 wd0: 1223MB (2504880 sectors), 621 cyls, 64 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 flags 0xb0ffb0ff on isa0 wdc1: unit 0 (wd2): , LBA, DMA, 32-bit, multi-block-16 wd2: 6197MB (12692736 sectors), 790 cyls, 255 heads, 63 S/T, 512 B/S wdc1: unit 1 (wd3): , LBA, DMA, 32-bit, multi-block-16 wd3: 8063MB (16514064 sectors), 1027 cyls, 255 heads, 63 S/T, 512 B/S DMA is definitely enabled. There's no mistaking the difference between DMA and no DMA. > I'm not sure the other values reported are valid either as they > are reported differently from what they are set to.... I took a look at this a while back and never got round to committing the changes. I believe most of the discrepancies were minor. I'll take charge of fixing that if you like. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 9: 7:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 285151565C for ; Thu, 9 Dec 1999 09:07:49 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA11953; Thu, 9 Dec 1999 18:07:34 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912091707.SAA11953@freebsd.dk> Subject: Re: Breaking DMA support for multiple chipsets? (was: HEADSUP: wd driver will be retired!) In-Reply-To: <19991209114541.59531@mojave.sitaranetworks.com> from Greg Lehey at "Dec 9, 1999 11:45:41 am" To: grog@lemis.com (Greg Lehey) Date: Thu, 9 Dec 1999 18:07:33 +0100 (CET) Cc: dick@tar.com (Richard Seaman Jr.), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Greg Lehey wrote: > >> > >> I think the old wd code was broken on reporting. The reporting > >> was changed from the original submission, when it was committed. > > > > Yep, but it does mean that people _belive_ they are running UDMA > > where in fact they aren't, and now they blaim the ata driver > > for doing worse :( > > Well, the wd driver definitely ran DMA on the 5591. And the fix > Richard reports is not normally output; IIRC it's only on a verbose > boot. On my machine, the driver reports: > > ide_pci0: irq 14 at device 0.1 on pci0 > ... > wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xb0ffb0ff on isa0 > wdc0: unit 0 (wd0): , LBA, DMA, 32-bit, multi-block-32 > wd0: 1223MB (2504880 sectors), 621 cyls, 64 heads, 63 S/T, 512 B/S > wdc1 at port 0x170-0x177 irq 15 flags 0xb0ffb0ff on isa0 > wdc1: unit 0 (wd2): , LBA, DMA, 32-bit, multi-block-16 > wd2: 6197MB (12692736 sectors), 790 cyls, 255 heads, 63 S/T, 512 B/S > wdc1: unit 1 (wd3): , LBA, DMA, 32-bit, multi-block-16 > wd3: 8063MB (16514064 sectors), 1027 cyls, 255 heads, 63 S/T, 512 B/S > > DMA is definitely enabled. There's no mistaking the difference > between DMA and no DMA. That was not what I said, it may run DMA but it says UDMA when not and vice versa, there is a difference between WDMA and UDMA.... > > I'm not sure the other values reported are valid either as they > > are reported differently from what they are set to.... > > I took a look at this a while back and never got round to committing > the changes. I believe most of the discrepancies were minor. I'll > take charge of fixing that if you like. I dont care, but for 3.x that might be a good idea.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 9: 9: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 3A2CB1565B for ; Thu, 9 Dec 1999 09:09:04 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 13C302DC07; Thu, 9 Dec 1999 18:09:45 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id B7D127811; Thu, 9 Dec 1999 18:06:41 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id B5DE810E10 for ; Thu, 9 Dec 1999 18:06:41 +0100 (CET) Date: Thu, 9 Dec 1999 18:06:41 +0100 (CET) From: Andrzej Bialecki To: freebsd-current@freebsd.org Subject: Modules and sysctl tree Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'd like to know whether we reached some conclusions concerning the naming of sysctl variables created (or related to) KLDs. I know that Linux emulator creates "compat.linux". I don't know if any other module creates sysctls (well, except my SPY module.. :-). So, what is the current thinking? Should we use modules.my_module.whatever, or kld.my_kld.whatever, or just sprinkle the new sysctls randomly over the tree, according to their functions, e.g. kern.my_module_kern_hook net.inet.my_module_inet_hook ... Also, it seems that you cannot create new sysctls (leaves and nodes) at runtime, i.e. after the module has been loaded. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 10:17: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 6653214BDE; Thu, 9 Dec 1999 10:17:05 -0800 (PST) From: "Jonathan M. Bresler" To: grog@lemis.com Cc: chris@netmonger.net, msmith@FreeBSD.ORG, julian@whistle.com, current@FreeBSD.ORG In-reply-to: <19991208215409.48501@mojave.sitaranetworks.com> (message from Greg Lehey on Wed, 8 Dec 1999 21:54:09 -0500) Subject: Re: HEADSUP: wd driver will be retired! Message-Id: <19991209181705.6653214BDE@hub.freebsd.org> Date: Thu, 9 Dec 1999 10:17:05 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > [snip] > >> Again, this is not accurate. I have a laptop with which, two months > >> ago, I could use my LinkSys ethernet card, and I could use my digital > > > > then we need to get your LinkSys ethernet card support fixed. > > i am using one to write this message. mine is a LinkSys 10/100 PCMCIA > > card. what do you have? > > What version of -CURRENT are you using? Mine is a PCMPC200, and I > haven't been able to get it to work for 6 weeks. PCMPC100 LinkSys PCMCIA 10/100 jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 10:28: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 4364614D0D; Thu, 9 Dec 1999 10:28:04 -0800 (PST) From: "Jonathan M. Bresler" To: jmb@hub.freebsd.org Cc: grog@lemis.com, chris@netmonger.net, msmith@FreeBSD.ORG, julian@whistle.com, current@FreeBSD.ORG In-reply-to: <19991209181705.6653214BDE@hub.freebsd.org> (jmb@hub.freebsd.org) Subject: Re: HEADSUP: wd driver will be retired! Message-Id: <19991209182804.4364614D0D@hub.freebsd.org> Date: Thu, 9 Dec 1999 10:28:04 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > What version of -CURRENT are you using? Mine is a PCMPC200, and I > > haven't been able to get it to work for 6 weeks. > > PCMPC100 LinkSys PCMCIA 10/100 > > jmb Greg, yours is a card bus card. it is not supported at this time. i have one right next to me with the label melted. you might not want to try using it until card bus is better supported. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 11:25:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4F6CA1515C; Thu, 9 Dec 1999 11:25:30 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA52112; Thu, 9 Dec 1999 12:25:22 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA13446; Thu, 9 Dec 1999 12:25:20 -0700 (MST) Message-Id: <199912091925.MAA13446@harmony.village.org> To: Brian Somers Subject: Re: HEADSUP: wd driver will be retired! Cc: Julian Elischer , "Jonathan M. Bresler" , chris@netmonger.net, msmith@FreeBSD.ORG, current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org In-reply-to: Your message of "Thu, 09 Dec 1999 06:23:11 GMT." <199912090623.GAA11752@hak.lan.Awfulhak.org> References: <199912090623.GAA11752@hak.lan.Awfulhak.org> Date: Thu, 09 Dec 1999 12:25:20 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912090623.GAA11752@hak.lan.Awfulhak.org> Brian Somers writes: : The aha driver broke somewhere between the 5th and 8th of this month. : Boot -v says ``aha0: status reg test failed ff''. Odd.. What kind of card do you have? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 11:26:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 35F8F14A05; Thu, 9 Dec 1999 11:26:08 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA52121; Thu, 9 Dec 1999 12:26:03 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA13459; Thu, 9 Dec 1999 12:26:03 -0700 (MST) Message-Id: <199912091926.MAA13459@harmony.village.org> To: Wilko Bulte Subject: Re: HEADSUP: wd driver will be retired! Cc: msmith@FreeBSD.ORG (Mike Smith), chris@netmonger.net, julian@whistle.com, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 08 Dec 1999 23:19:58 +0100." <199912082219.XAA77409@yedi.iaf.nl> References: <199912082219.XAA77409@yedi.iaf.nl> Date: Thu, 09 Dec 1999 12:26:03 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912082219.XAA77409@yedi.iaf.nl> Wilko Bulte writes: : Not quite true: the esp driver for the alphas got lost. No attack on anyone, : just stating a fact. As did the sea and uha drivers. I had a fantacy that I'd have time to write one. However, I didn't... :-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 11:28:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A80A614E57 for ; Thu, 9 Dec 1999 11:28:14 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA52136; Thu, 9 Dec 1999 12:28:10 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA13486; Thu, 9 Dec 1999 12:28:08 -0700 (MST) Message-Id: <199912091928.MAA13486@harmony.village.org> To: YAMAMOTO Shigeru Subject: Re: which is right? 'controller pcic0 at isa?' or 'device pcic0 at isa?'? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 09 Dec 1999 18:11:27 +0900." <19991209181127N.shigeru@iij.ad.jp> References: <19991209181127N.shigeru@iij.ad.jp> Date: Thu, 09 Dec 1999 12:28:08 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991209181127N.shigeru@iij.ad.jp> YAMAMOTO Shigeru writes: : I wonder about configuration for pcic in -current. : : In GENERIC, '#device pcic0 at isa?' : In LINT and PCCARD, 'controller pcic0 at isa?' : : Which is right? LINT and PCCARD is right, although there is little difference between a controller and a device anymore, iirc. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 11:29:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 938F014D2F; Thu, 9 Dec 1999 11:29:45 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA52145; Thu, 9 Dec 1999 12:29:44 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA13506; Thu, 9 Dec 1999 12:29:43 -0700 (MST) Message-Id: <199912091929.MAA13506@harmony.village.org> To: Thomas David Rivers Subject: Re: HEADSUP: wd driver will be retired! Cc: julian@whistle.com, chris@netmonger.net, current@FreeBSD.ORG, jmb@hub.freebsd.org, msmith@FreeBSD.ORG In-reply-to: Your message of "Thu, 09 Dec 1999 06:32:33 EST." <199912091132.GAA41598@lakes.dignus.com> References: <199912091132.GAA41598@lakes.dignus.com> Date: Thu, 09 Dec 1999 12:29:43 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912091132.GAA41598@lakes.dignus.com> Thomas David Rivers writes: : I lost support on my 1542B until I came up with a patch, which : I believe was incorporated into 3.3-R. Yes. I stand corrected. The B that I had worked w/o the patch, but many B's in the field didn't :-(. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 11:55: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 403C214EBF for ; Thu, 9 Dec 1999 11:54:54 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id UAA00963 for freebsd-current@freebsd.org; Thu, 9 Dec 1999 20:54:52 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 8BD2A8863; Thu, 9 Dec 1999 20:25:26 +0100 (CET) Date: Thu, 9 Dec 1999 20:25:26 +0100 From: Ollivier Robert To: freebsd-current@freebsd.org Subject: Re: boot stops after "Mounting root from ufs:/dev/ad0s2a" Message-ID: <19991209202526.A61101@keltia.freenix.fr> Mail-Followup-To: freebsd-current@freebsd.org References: <384C1779.C3010AFA@sympatico.ca> <384F559E.B6386C5D@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <384F559E.B6386C5D@newsguy.com> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Daniel C. Sobral: > > ad0: ATA-3 disk at ata0 as master ^^^^^^ > > ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > ^^^^^^ > Is this the correct size of your hard disk? Yes, see above. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 12: 2:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id EBD01156C9; Thu, 9 Dec 1999 12:02:16 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.198.50]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAC59D3; Thu, 9 Dec 1999 21:02:11 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id UAA79380; Thu, 9 Dec 1999 20:57:02 +0100 (CET) (envelope-from asmodai) Date: Thu, 9 Dec 1999 20:57:02 +0100 From: Jeroen Ruigrok/Asmodai To: Wilko Bulte Cc: Mike Smith , chris@netmonger.net, julian@whistle.com, current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991209205701.D65692@daemon.ninth-circle.org> References: <199912082052.MAA00517@mass.cdrom.com> <199912082219.XAA77409@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912082219.XAA77409@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Wed, Dec 08, 1999 at 11:19:58PM +0100 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991209 12:00], Wilko Bulte (wilko@yedi.iaf.nl) wrote: >As Mike Smith wrote ... >> > On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: > >> > [there] were the SCSI drivers lost to CAM >> >> Actually, most of this is histrionics. CAM didn't lose us SCSI drivers; > >Not quite true: the esp driver for the alphas got lost. No attack on anyone, >just stating a fact. Another state of fact, until no-one finds it annoying enough to fix it it will be Atticised for quite some time longer. Apparantly the people whom caused a ruckus about losing some functionality when moving to better designed new driver framework weren't quite that bothered at all. Else we would've seen submissions for those drivers to be upgraded to the new framework. Luoqi is a prime example for aic. (If my memory serves me right.) -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project Atone me to my throes curtail... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 12: 2:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id BF64B1563B; Thu, 9 Dec 1999 12:02:12 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.198.50]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB59D3; Thu, 9 Dec 1999 21:02:10 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id UAA83067; Thu, 9 Dec 1999 20:58:57 +0100 (CET) (envelope-from asmodai) Date: Thu, 9 Dec 1999 20:58:57 +0100 From: Jeroen Ruigrok/Asmodai To: Warner Losh Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991209205857.E65692@daemon.ninth-circle.org> References: <19991208145446.B11395@dragon.nuxi.com> <19991208150807.A16687@netmonger.net> <199912082052.MAA00517@mass.cdrom.com> <19991208145446.B11395@dragon.nuxi.com> <199912090556.WAA09496@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912090556.WAA09496@harmony.village.org>; from imp@village.org on Wed, Dec 08, 1999 at 10:56:09PM -0700 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991209 06:59], Warner Losh (imp@village.org) wrote: >: P.S. I'm not trying to cut down Warner, but I do think we really need to >: focus on regaining support for things we've lost in the past 6 months. > >I agree with this completely. The newbus excursion of the old code >likely was a big mistake. We have a basically working system now, but >I've not had time to focus on the new system because of the amount of >time I've spent on legacy issues. Part of this is too blame on the sparse documentation available about newbus. The relevant people clued about newbus know I am working on manpages/documents to get into the basesystem. It's coming (and hopefully with less typo's as in elf.5 ;) ) -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project Atone me to my throes curtail... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 12: 2:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id F40D2156C6; Thu, 9 Dec 1999 12:02:15 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.198.50]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAD59D3; Thu, 9 Dec 1999 21:02:13 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id UAA71514; Thu, 9 Dec 1999 20:53:02 +0100 (CET) (envelope-from asmodai) Date: Thu, 9 Dec 1999 20:53:02 +0100 From: Jeroen Ruigrok/Asmodai To: Greg Lehey Cc: Brad Knowles , Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991209205302.C65692@daemon.ninth-circle.org> References: <199912081856.KAA06231@mass.cdrom.com> <19991208214001.56508@mojave.sitaranetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991208214001.56508@mojave.sitaranetworks.com>; from grog@mojave.sitaranetworks.com on Wed, Dec 08, 1999 at 09:40:01PM -0500 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991209 16:03], Greg Lehey (grog@mojave.sitaranetworks.com) wrote: >On Wednesday, 8 December 1999 at 20:23:24 +0100, Brad Knowles wrote: >> >> This is -CURRENT. It pains me to say it, but anyone trying to >> run anything "useful" on -CURRENT gets what they deserve. This is >> the only place where we can make clean breaks with the past, and as >> painful as that can be, we simply have to do that occasionally. > >Next month it'll be -RELEASE. This isn't the time to remove such >significant functionality. If it weren't for that, I'd agree with >you. Think about that some more. After that it will be 4.1. Nice to give people a driver and then rip it out when 4.1 comes when Soren fixes the last of the things people needed to have into the ata driver. I was already testing the ata driver and even procured some more info for Soren than he already had. Same goes for a bunch of other people. But the opposite goes for a lot of people. People running CURRENT to be cutting edge as in being elite with the latest FreeBSD thus get bitten. I'd say, cut loose the wd driver. (VoxWare removed would be cool too.) -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project Atone me to my throes curtail... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 12: 2:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id DB14E156E6 for ; Thu, 9 Dec 1999 12:02:23 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.198.50]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA59D3; Thu, 9 Dec 1999 21:02:09 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id UAA66231; Thu, 9 Dec 1999 20:32:05 +0100 (CET) (envelope-from asmodai) Date: Thu, 9 Dec 1999 20:32:05 +0100 From: Jeroen Ruigrok/Asmodai To: Donn Miller Cc: current@FreeBSD.ORG Subject: Flash (was: Re: Sound card support) Message-ID: <19991209203205.B65692@daemon.ninth-circle.org> References: <199912090800.RAA01655@tomoyo.snipe.rim.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dmmiller@cvzoom.net on Thu, Dec 09, 1999 at 03:14:44AM -0500 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [again subject changes] -On [19991209 16:00], Donn Miller (dmmiller@cvzoom.net) wrote: >On Thu, 9 Dec 1999, Motoyuki Konno wrote: > >> Please see Netscape plugin port (ports/www/flashplugin) to find >> out why we still have to need a.out support. > >Wow -- there's a flash plugin for Netscape? That's what I needed for a >couple of web sites. Good luck using it under current. First site you hit quits netscape without reasons... ...until you drop out of X and see a __sh_getcontext IIRC warning on your console. I already mailed maintainer about this. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project Atone me to my throes curtail... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 12:12: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id EFA3015721 for ; Thu, 9 Dec 1999 12:12:06 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 52143144; Thu, 9 Dec 1999 12:12:06 -0800 (PST) Date: Thu, 9 Dec 1999 12:12:06 -0800 From: Chris Piazza To: Jeroen Ruigrok/Asmodai Cc: Donn Miller , current@FreeBSD.ORG Subject: Re: Flash (was: Re: Sound card support) Message-ID: <19991209121206.A73879@norn.ca.eu.org> References: <199912090800.RAA01655@tomoyo.snipe.rim.or.jp> <19991209203205.B65692@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991209203205.B65692@daemon.ninth-circle.org>; from asmodai@wxs.nl on Thu, Dec 09, 1999 at 08:32:05PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 09, 1999 at 08:32:05PM +0100, Jeroen Ruigrok/Asmodai wrote: > [again subject changes] > > -On [19991209 16:00], Donn Miller (dmmiller@cvzoom.net) wrote: > >On Thu, 9 Dec 1999, Motoyuki Konno wrote: > > > >> Please see Netscape plugin port (ports/www/flashplugin) to find > >> out why we still have to need a.out support. > > > >Wow -- there's a flash plugin for Netscape? That's what I needed for a > >couple of web sites. > > Good luck using it under current. > > First site you hit quits netscape without reasons... > > ...until you drop out of X and see a __sh_getcontext IIRC warning on > your console. > > I already mailed maintainer about this. I don't even use the FreeBSD Netscape any more. As far as I'm concerned, there might as well NOT be a native binary for FreeBSD, because it's not very stable. I use the Linux netscape with macromedia's flash4 plugin and it works very well. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 12:18:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (Postfix) with ESMTP id A76FA15682 for ; Thu, 9 Dec 1999 12:18:46 -0800 (PST) (envelope-from tejblum@arc.hq.cti.ru) Received: from arc.hq.cti.ru (localhost [127.0.0.1]) by arc.hq.cti.ru (8.9.3/8.9.3) with ESMTP id XAA46056; Thu, 9 Dec 1999 23:17:02 +0300 (MSK) (envelope-from tejblum@arc.hq.cti.ru) Message-Id: <199912092017.XAA46056@arc.hq.cti.ru> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jeroen Ruigrok/Asmodai Cc: Donn Miller , current@FreeBSD.ORG Subject: Re: Flash (was: Re: Sound card support) In-reply-to: Your message of "Thu, 09 Dec 1999 20:32:05 +0100." <19991209203205.B65692@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Dec 1999 23:16:58 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Good luck using it under current. > > First site you hit quits netscape without reasons... > > ...until you drop out of X and see a __sh_getcontext IIRC warning on > your console. If you can hack on the flash plugin's Makefile, try add -fno-exceptions there. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 12:25:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.cioe.com (ns1.cioe.com [204.120.165.37]) by hub.freebsd.org (Postfix) with ESMTP id 9F63514E4F; Thu, 9 Dec 1999 12:25:32 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: from ny1wsh031 (tek.cioe.com [204.120.165.120]) by ns1.cioe.com (8.9.3/8.9.3) with SMTP id PAA62403; Thu, 9 Dec 1999 15:24:16 -0500 (EST) (envelope-from steve@virtual-voodoo.com) Message-ID: <016a01bf4283$56f92220$851a050a@winstar.com> From: "Steven E. Ames" To: "Jeroen Ruigrok/Asmodai" , "Greg Lehey" Cc: "Brad Knowles" , "Mike Smith" , "Julian Elischer" , References: <199912081856.KAA06231@mass.cdrom.com> <19991208214001.56508@mojave.sitaranetworks.com> <19991209205302.C65692@daemon.ninth-circle.org> Subject: Re: HEADSUP: wd driver will be retired! Date: Thu, 9 Dec 1999 15:24:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Next month it'll be -RELEASE. This isn't the time to remove such > >significant functionality. If it weren't for that, I'd agree with > >you. > > Think about that some more. Ditto :) The idea that seems to be here is to definately make ATA the default driver. Definately it should be the default driver for 4.0... but leave the 'wd' driver there as a fallback. After we've had a wide test audience of 4.0 users using the ATA driver it will likely cover every bit of hardware that 'wd' already does and do a better job. At that point 'wd' can be scrapped for 4.1-RELEASE. Big changes that have been little tested shouldn't be made just before RELEASE... not without a safety net. -Steve > > After that it will be 4.1. Nice to give people a driver and then rip it > out when 4.1 comes when Soren fixes the last of the things people > needed to have into the ata driver. > > I was already testing the ata driver and even procured some more info > for Soren than he already had. Same goes for a bunch of other people. > But the opposite goes for a lot of people. > > People running CURRENT to be cutting edge as in being elite with the > latest FreeBSD thus get bitten. > > I'd say, cut loose the wd driver. (VoxWare removed would be cool too.) > > -- > Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] > Documentation nutter. *BSD: Technical excellence at its best... > The BSD Programmer's Documentation Project > Atone me to my throes curtail... > > > 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 Dec 9 12:47:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id D400514D5C for ; Thu, 9 Dec 1999 12:47:24 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.198.50]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB6961; Thu, 9 Dec 1999 21:47:17 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA99943; Thu, 9 Dec 1999 21:43:13 +0100 (CET) (envelope-from asmodai) Date: Thu, 9 Dec 1999 21:43:13 +0100 From: Jeroen Ruigrok/Asmodai To: "Andrey A. Chernov" Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: Is there any way to use ATAPI CD-R? Message-ID: <19991209214313.H65692@daemon.ninth-circle.org> References: <19991208211624.A6005@nagual.pp.ru> <199912082034.VAA17215@freebsd.dk> <19991209063845.A11949@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991209063845.A11949@nagual.pp.ru>; from ache@nagual.pp.ru on Thu, Dec 09, 1999 at 06:38:46AM +0300 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991209 06:58], Andrey A. Chernov (ache@nagual.pp.ru) wrote: >Do you have a plan to merge ATAPI as part of SCSI (CAM) interface as >NetBSD already does? It will solve problems with all SCSI-only CD* soft >automatically. I thought this was the original idea back then when work started on the new drivers. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project Atone me to my throes curtail... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 12:48:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id 1193F15687; Thu, 9 Dec 1999 12:48:27 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.198.50]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAC6961; Thu, 9 Dec 1999 21:47:39 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA99936; Thu, 9 Dec 1999 21:37:09 +0100 (CET) (envelope-from asmodai) Date: Thu, 9 Dec 1999 21:37:09 +0100 From: Jeroen Ruigrok/Asmodai To: Bill Fumerola Cc: Soren Schmidt , Julian Elischer , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991209213709.G65692@daemon.ninth-circle.org> References: <199912081721.SAA70567@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from billf@chc-chimes.com on Wed, Dec 08, 1999 at 05:12:08PM -0500 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991209 00:03], Bill Fumerola (billf@chc-chimes.com) wrote: >On Wed, 8 Dec 1999, Soren Schmidt wrote: > >> The same thing is about to apply to the woxware sound code, we have a >> new shiny system that works and is much better designed... > >For some definitions of "works". Low shot. If not for Cameron and Sanimura-san we would still be left dangling with the hopeless kludge of pcm vs VoxWare. They finally put their effort into something which all questions plus remarks on the topic would already have released a long time ago. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project Atone me to my throes curtail... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 13: 0:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id D0AA6156C5 for ; Thu, 9 Dec 1999 13:00:53 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id A90E31C5C; Thu, 9 Dec 1999 16:00:50 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id A4172381B; Thu, 9 Dec 1999 16:00:50 -0500 (EST) Date: Thu, 9 Dec 1999 16:00:50 -0500 (EST) From: Bill Fumerola To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991209213709.G65692@daemon.ninth-circle.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Dec 1999, Jeroen Ruigrok/Asmodai wrote: > >For some definitions of "works". > > Low shot. If not for Cameron and Sanimura-san we would still be left > dangling with the hopeless kludge of pcm vs VoxWare. They finally put > their effort into something which all questions plus remarks on the > topic would already have released a long time ago. It wasn't meant to be low or insulting. I'm making the simple obervation that my office has been oddly silent ever since switching to newpcm. It's not for unwillingness to test patches either. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 13:16:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E596D1568B for ; Thu, 9 Dec 1999 13:16:40 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p01-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.98]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id GAA23104; Fri, 10 Dec 1999 06:16:37 +0900 (JST) Message-ID: <384F656B.52F01F9B@newsguy.com> Date: Thu, 09 Dec 1999 17:16:43 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Motoyuki Konno Cc: current@FreeBSD.ORG Subject: Re: why 'The legacy aout build' was removed from current ? References: <19991209163452O.shigeru@iij.ad.jp> <199912090800.RAA01655@tomoyo.snipe.rim.or.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Motoyuki Konno wrote: > > I think we don't need "a.out world" any more, but a.out support > (a.out lib/shared lib, etc.) is still needed. Some commercial > programs such as Netscape are in a.out only, so we still have to > make a.out binaries. > > Please see Netscape plugin port (ports/www/flashplugin) to find > out why we still have to need a.out support. Current is not a general use platform. And if we want them (third party) to support FreeBSD-elf by the time 4.x becomes -stable, we better lock them out of it *now*. The main reason for removing the legacy support is forcing people to switch. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 13:31:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id C88F214C01 for ; Thu, 9 Dec 1999 13:31:25 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id QAA00829; Thu, 9 Dec 1999 16:31:14 -0500 (EST) Message-ID: <19991209163114.A26029@netmonger.net> Date: Thu, 9 Dec 1999 16:31:14 -0500 From: Christopher Masto To: "Andrey A. Chernov" , Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: Is there any way to use ATAPI CD-R? References: <19991208211624.A6005@nagual.pp.ru> <199912082034.VAA17215@freebsd.dk> <19991209063845.A11949@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19991209063845.A11949@nagual.pp.ru>; from Andrey A. Chernov on Thu, Dec 09, 1999 at 06:38:46AM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 09, 1999 at 06:38:46AM +0300, Andrey A. Chernov wrote: > On Wed, Dec 08, 1999 at 09:34:24PM +0100, Soren Schmidt wrote: > > I use it every day, well almost :) > > Look in /usr/share/examples/atapi... > > Thanks! Do you have a plan to merge ATAPI as part of SCSI (CAM) interface > as NetBSD already does? It will solve problems with all SCSI-only CD* soft > automatically. I'd love to see that. I have an ATAPI CD-R that doesn't seem to work properly with the worm stuff, but is supposedly supported by the cdrecord program. But we don't yet have the interface cdrecord wants. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 13:38:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 5F9A3156B6 for ; Thu, 9 Dec 1999 13:38:19 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id QAA62027; Thu, 9 Dec 1999 16:36:49 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Thu, 9 Dec 1999 16:36:48 -0500 (EST) From: Chuck Robey To: "Daniel C. Sobral" Cc: Motoyuki Konno , current@FreeBSD.ORG Subject: Re: why 'The legacy aout build' was removed from current ? In-Reply-To: <384F656B.52F01F9B@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Dec 1999, Daniel C. Sobral wrote: > Motoyuki Konno wrote: > > > > I think we don't need "a.out world" any more, but a.out support > > (a.out lib/shared lib, etc.) is still needed. Some commercial > > programs such as Netscape are in a.out only, so we still have to > > make a.out binaries. > > > > Please see Netscape plugin port (ports/www/flashplugin) to find > > out why we still have to need a.out support. > > Current is not a general use platform. And if we want them (third > party) to support FreeBSD-elf by the time 4.x becomes -stable, we > better lock them out of it *now*. > > The main reason for removing the legacy support is forcing people to > switch. This isn't taking the execution of aout binaries out, just stopping a world build. This is only going to stop 3rd party developers from making a 4.0 aout platform to create *more* aout binaries. They'll probably hang on for dear life on 2.2, just as long as they can. Looking at copious examples from real life, forcing 3rd party developers to upgrade is a good way to lose 3rd party developers. It just *sounds* like a good way to go. As long as this is a change for building world, and not making changes to the kern/imgact things (so we keep on executing aout binaries) then this is probably the best way to go. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 13:44:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D30481522E for ; Thu, 9 Dec 1999 13:44:46 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA82913; Thu, 9 Dec 1999 22:44:38 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912092144.WAA82913@freebsd.dk> Subject: Re: Is there any way to use ATAPI CD-R? In-Reply-To: <19991209214313.H65692@daemon.ninth-circle.org> from Jeroen Ruigrok/Asmodai at "Dec 9, 1999 09:43:13 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Thu, 9 Dec 1999 22:44:38 +0100 (CET) Cc: ache@nagual.pp.ru (Andrey A. Chernov), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Jeroen Ruigrok/Asmodai wrote: > -On [19991209 06:58], Andrey A. Chernov (ache@nagual.pp.ru) wrote: > >Do you have a plan to merge ATAPI as part of SCSI (CAM) interface as > >NetBSD already does? It will solve problems with all SCSI-only CD* soft > >automatically. > > I thought this was the original idea back then when work started on the > new drivers. No, the idea was to get all the lowlevel ata/atapi stuff sorted out and layered so that it was maintainable and extendable. You could add a CAM top to the atapisubsystem instead of the "native" atapi drivers, it would be more work for the disks (lots more). My priority is still to get all the lowlevel stuff stabilized, and to get support for various controller HW, including top notch performance. Also CAM has to be de-SCSIfied before any of this is possible, and frankly I dont se anybody having the time/knowledge to do that for the foreseable future... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 13:46:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 69A61151F9; Thu, 9 Dec 1999 13:45:55 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id PAA91916; Thu, 9 Dec 1999 15:44:05 -0600 (CST) From: Joe Greco Message-Id: <199912092144.PAA91916@aurora.sol.net> Subject: Re: Route table leaks In-Reply-To: <199912090743.XAA19457@tantivy.stanford.edu> from Bob Vaughan at "Dec 8, 1999 11:43:34 pm" To: techie@tantivy.stanford.edu (Bob Vaughan) Date: Thu, 9 Dec 1999 15:44:05 -0600 (CST) Cc: freebsd@gndrsh.dnsmgr.net, mike@sentex.net, current@FreeBSD.ORG, jdp@polstra.com, jgreco@ns.sol.net, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The patch previously mentioned has completely fixed my problem, as far as I can tell. routetbl 131 17K 25K 40960K 93624 0 0 16,32,64,128,256 after a day of uptime. > here's mine.. > this is from a single homed machine, with a default route. it's also a IRC > server (irc.stanford.edu), with a LOT of filtering of inbound traffic. > > FreeBSD 3.3-STABLE #8: Sat Nov 27 17:15:49 PST 1999 > > 11:33PM up 2 days, 20:41, 1 user, load averages: 0.03, 0.03, 0.00 > > routetbl 205 29K 10489K 10489K 3479960 0 0 16,32,64,128,256 > > note that the table maxed out at some point (during a DoS attack.) > > root-irc.stanford.edu-[11:34pm-52]#t> netstat -ran | wc > 70 409 4741 > > looks like it leaked 135 in 2.8 days.. > > > -- Welcome My Son, Welcome To The Machine -- > Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org > | P.O. Box 9792, Stanford, Ca 94309-9792 > -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- > -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 13:46:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id BAEFA1571D for ; Thu, 9 Dec 1999 13:46:35 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA83439; Thu, 9 Dec 1999 22:46:27 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912092146.WAA83439@freebsd.dk> Subject: Re: Is there any way to use ATAPI CD-R? In-Reply-To: <19991209163114.A26029@netmonger.net> from Christopher Masto at "Dec 9, 1999 04:31:14 pm" To: chris@netmonger.net (Christopher Masto) Date: Thu, 9 Dec 1999 22:46:27 +0100 (CET) Cc: ache@nagual.pp.ru (Andrey A. Chernov), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Christopher Masto wrote: > On Thu, Dec 09, 1999 at 06:38:46AM +0300, Andrey A. Chernov wrote: > > On Wed, Dec 08, 1999 at 09:34:24PM +0100, Soren Schmidt wrote: > > > I use it every day, well almost :) > > > Look in /usr/share/examples/atapi... > > > > Thanks! Do you have a plan to merge ATAPI as part of SCSI (CAM) interface > > as NetBSD already does? It will solve problems with all SCSI-only CD* soft > > automatically. > > I'd love to see that. I have an ATAPI CD-R that doesn't seem to work > properly with the worm stuff, but is supposedly supported by the > cdrecord program. But we don't yet have the interface cdrecord wants. I wouldn't hold my breath :) What CD-R is that, and whats the problem. There has been a period until a week or so ago where the fixating didn't work right... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 13:48:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id DB7881522E for ; Thu, 9 Dec 1999 13:48:38 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA01310; Thu, 9 Dec 1999 13:50:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912092150.NAA01310@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Donn Miller Cc: current@freebsd.org Subject: Re: MCA support In-reply-to: Your message of "Thu, 09 Dec 1999 04:30:58 EST." <384F76D2.938FD166@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Dec 1999 13:50:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just wondering how far along MCA support is. I tried booting up > a kern.flp from the latest snapshot circa dec. 7. and I got a > "Read error" during boot, which halted the machine. My machine > was an IBM PS/2 model 77s. That's probably a bad floppy. You should at least get the kernel and mfsroot loaded before MCA becomes an issue at all. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 13:55:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id C708814FDF for ; Thu, 9 Dec 1999 13:55:26 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id PAA06088; Thu, 9 Dec 1999 15:55:12 -0600 (CST) (envelope-from dan) Date: Thu, 9 Dec 1999 15:55:12 -0600 From: Dan Nelson To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: NFS client zeroing out blocks on write? Message-ID: <19991209155512.A5898@dan.emsphone.com> References: <19991203112518.A43843@dan.emsphone.com> <199912042051.MAA56920@apollo.backplane.com> <19991205024034.A77822@dan.emsphone.com> <199912061912.LAA71576@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912061912.LAA71576@apollo.backplane.com>; from "Matthew Dillon" on Mon Dec 6 11:12:21 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Dec 06), Matthew Dillon said: > Dan, I know this may be placing an undue burden on you, but can you > try installing a 3.x snapshot to see if the bug exists there? If the > bug exists in 3.x then I'll know that it isn't due to changes I've > made in 4.x (or at least not likely due to those changes). If the > bug does not exist then it gives me a place to start looking. I don't have a spare machine at the moment to install 3.3 onto at the moment, but will keep an eye out for one. > The weird thing is that we are talking about a single process here, > and I would expect this type of bug to occur with multiple contending > processes. If it had just been an NFSv3 mount I would have suspected > the commit rpc code, but if it is occuring on NFSv2 as well it kinda > sounds like a preexisting bug that has just been brought out into the > light due to changes in the way NFS works (major NFS performance > improvements have been made in -current, for example, that allow NFS > to saturate the network more easily). I am going to have to retract my earlier NFSv2 statement; I can't for the life of me reproduce the glitch over any v2 mount now. The corrupted file I saw across a v2 mount must have been bad to start with. I can definitely reproduce it over an NFSv3 mount to a FreeBSD, Solaris, or Dec Unix server. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 13:56:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 7369215118; Thu, 9 Dec 1999 13:56:45 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA01406; Thu, 9 Dec 1999 13:57:54 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912092157.NAA01406@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexander Leidinger Cc: sobomax@altavista.net, sos@freebsd.dk, phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Thu, 09 Dec 1999 15:45:09 +0100." <199912091445.PAA42318@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 09 Dec 1999 13:57:54 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 9 Dec, Maxim Sobolev wrote: > = > > Excuse me for possible off-topic, but I have what is seems for me fre= sh idea > > about this question. Why do not remove from wd driver support for chi= psets > > already implemented/tested in ata driver? Thus both clans would satis= fied > > i.e. users with unsupported by ata chips still will have a chance, wh= ile all > > other will be encouraged to use and test better (IMHO) ata... Eventua= lly at > = > There also exist cases where the chipset is supported but a particular > functionality isn=B4t supported yet (in my case it=B4s the possibility = to > access MS-DOS formated ZIP-disks, harddisk access works well, and I=B4m= > not the only one with this problem (not counting the people which have > not tried to use the ata driver but need to access MS-DOS-ZIPs too)). I'm completely at a loss as to how the ata driver could be responsible = for your inability to read these disks. I don't have a copy of your = original problem report to hand, but since I have all the hardware here = I'd appreciate it if you could be a little more explicit about your = problem. The ata driver just moves bytes; it doesn't give a damn what they are. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 13:58: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 946B215789 for ; Thu, 9 Dec 1999 13:58:05 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA01426; Thu, 9 Dec 1999 13:59:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912092159.NAA01426@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Matthew N. Dodd" Cc: current@FreeBSD.ORG Subject: Re: MCA support In-reply-to: Your message of "Thu, 09 Dec 1999 10:36:47 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Dec 1999 13:59:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My m77 has weird problems reading the floppy drive. I'm fairly sure this > has everything to do with code in the loader/bootstrap that doesn't like > the 2.88M drive. I used the 1.2M drive and it works great. I suspect a > normal 1.44M drive would be good too. The loader just uses the BIOS; you can't blame it. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 14: 2: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 65868157F0; Thu, 9 Dec 1999 14:02:06 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id RAA15098; Thu, 9 Dec 1999 17:02:01 -0500 (EST) Date: Thu, 9 Dec 1999 17:02:01 -0500 (EST) From: "Matthew N. Dodd" To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: MCA support In-Reply-To: <199912092159.NAA01426@mass.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 Thu, 9 Dec 1999, Mike Smith wrote: > > My m77 has weird problems reading the floppy drive. I'm fairly sure this > > has everything to do with code in the loader/bootstrap that doesn't like > > the 2.88M drive. I used the 1.2M drive and it works great. I suspect a > > normal 1.44M drive would be good too. > > The loader just uses the BIOS; you can't blame it. 8) Well, there you have it. My second guess would be an issue with the 2.88M drive reading a 1.44M floppy that was created in a 1.44M drive. I was going to try burning a 1.44M floppy in the 2.88M drive to see if it allowed the disk to boot without errors but I got local disk and network working before I got around to it. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 14:15:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 4FCD414FDF; Thu, 9 Dec 1999 14:15:32 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA03733; Thu, 9 Dec 1999 14:15:31 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912092215.OAA03733@gndrsh.dnsmgr.net> Subject: Re: MCA support In-Reply-To: <199912092159.NAA01426@mass.cdrom.com> from Mike Smith at "Dec 9, 1999 01:59:40 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Thu, 9 Dec 1999 14:15:31 -0800 (PST) Cc: winter@jurai.net (Matthew N. Dodd), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My m77 has weird problems reading the floppy drive. I'm fairly sure this > > has everything to do with code in the loader/bootstrap that doesn't like > > the 2.88M drive. I used the 1.2M drive and it works great. I suspect a > > normal 1.44M drive would be good too. > > The loader just uses the BIOS; you can't blame it. 8) I can confirm the loader problem on IBM MCA machines with 2.88M drives, and you _CAN_ blame the loader if it does not make the _CORRECT_ calls to the BIOS :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 14:16:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id EB4FC14FDF; Thu, 9 Dec 1999 14:16:27 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01708; Thu, 9 Dec 1999 14:18:53 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912092218.OAA01708@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: Alexander Leidinger , sobomax@altavista.net, sos@freebsd.dk, phk@freebsd.org, current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Thu, 09 Dec 1999 13:57:54 PST." <199912092157.NAA01406@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 09 Dec 1999 14:18:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm completely at a loss as to how the ata driver could be responsible = > for your inability to read these disks. I don't have a copy of your = > original problem report to hand, but since I have all the hardware here= = > I'd appreciate it if you could be a little more explicit about your = > problem. Re-reading this, it's not clear that what I'm saying here is "please tell= = me a little more about what you're doing so that I can reproduce the = problem", not "your problem report is terrible, please go away and die". Sorry if that's caused any consternation. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 14:16:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id DA5391522E; Thu, 9 Dec 1999 14:16:36 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA03743; Thu, 9 Dec 1999 14:16:35 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912092216.OAA03743@gndrsh.dnsmgr.net> Subject: Re: MCA support In-Reply-To: <199912092159.NAA01426@mass.cdrom.com> from Mike Smith at "Dec 9, 1999 01:59:40 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Thu, 9 Dec 1999 14:16:35 -0800 (PST) Cc: winter@jurai.net (Matthew N. Dodd), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My m77 has weird problems reading the floppy drive. I'm fairly sure this > > has everything to do with code in the loader/bootstrap that doesn't like > > the 2.88M drive. I used the 1.2M drive and it works great. I suspect a > > normal 1.44M drive would be good too. > > The loader just uses the BIOS; you can't blame it. 8) Ohh... and if you need a box to fix this just let me know, I've got a pile of old MCA 486's that won't boot the loader code from thier 2.88MB drives, I could ship you one... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 15: 4: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id D8F32156B0; Thu, 9 Dec 1999 15:03:57 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA02150; Thu, 9 Dec 1999 15:00:31 -0800 (PST) Date: Thu, 9 Dec 1999 15:00:30 -0800 (PST) From: Julian Elischer To: Joe Greco Cc: Bob Vaughan , freebsd@gndrsh.dnsmgr.net, mike@sentex.net, current@FreeBSD.ORG, jdp@polstra.com, stable@FreeBSD.ORG Subject: Re: Route table leaks In-Reply-To: <199912092144.PAA91916@aurora.sol.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 so can it be committed? On Thu, 9 Dec 1999, Joe Greco wrote: > The patch previously mentioned has completely fixed my problem, as far as I > can tell. > > routetbl 131 17K 25K 40960K 93624 0 0 16,32,64,128,256 > > after a day of uptime. > > > here's mine.. > > this is from a single homed machine, with a default route. it's also a IRC > > server (irc.stanford.edu), with a LOT of filtering of inbound traffic. > > > > FreeBSD 3.3-STABLE #8: Sat Nov 27 17:15:49 PST 1999 > > > > 11:33PM up 2 days, 20:41, 1 user, load averages: 0.03, 0.03, 0.00 > > > > routetbl 205 29K 10489K 10489K 3479960 0 0 16,32,64,128,256 > > > > note that the table maxed out at some point (during a DoS attack.) > > > > root-irc.stanford.edu-[11:34pm-52]#t> netstat -ran | wc > > 70 409 4741 > > > > looks like it leaked 135 in 2.8 days.. > > > > > > -- Welcome My Son, Welcome To The Machine -- > > Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org > > | P.O. Box 9792, Stanford, Ca 94309-9792 > > -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 15:12:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from ra.nks.net (ra.nks.net [208.226.218.5]) by hub.freebsd.org (Postfix) with ESMTP id 126AD15715 for ; Thu, 9 Dec 1999 15:12:56 -0800 (PST) (envelope-from joeo@cracktown.com) Received: from localhost (joeo@localhost) by ra.nks.net (8.8.7/8.8.7) with ESMTP id SAA13732 for ; Thu, 9 Dec 1999 18:13:02 -0500 Date: Thu, 9 Dec 1999 18:13:02 -0500 (EST) From: X-Sender: joeo@ra.nks.net To: current@freebsd.org Subject: PNPBIOS vs cs423B codec Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Managed to get the sound stuff working on this thinkpad 600e, for anyone who cares... Had to update to the most recent bios, and made sure "quick boot" was disabled (hold down F1 while powering on to get into bios). I removed the "csa0" device from the kernel config, despite having a CS4610 probed during boot. Also set up a pcm0 config line of the sort... device pcm0 at isa? port ? irq 5 drq 1 flags 0x10 % cat /dev/sndstat FreeBSD Audio Driver (newpcm) Dec 9 1999 17:28:08 Installed devices: pcm0: at io 0x220 irq 5 drq 0:1 (1/1 channels duplex) the relevant PNP boot messages without pcm enabled... CSC0100: adding io range 0x530-0x537, size=0x8, align=0 CSC0100: adding io range 0x388-0x38b, size=0x4, align=0 CSC0100: adding io range 0x220-0x233, size=0x14, align=0x20 CSC0100: adding irq mask 0x20 CSC0100: adding dma mask 0x2 CSC0100: adding dma mask 0x1 CSC0100: start dependant pnpbios: handle 14 device ID CSC0100 (0001630e) ... unknown6: at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 5 drq 1,0 on isa0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 15:18:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id BAF7C14CC8; Thu, 9 Dec 1999 15:18:18 -0800 (PST) (envelope-from blk@skynet.be) Received: from [194.78.238.58] (dialup890.brussels2.skynet.be [194.78.238.58]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id AAA10851; Fri, 10 Dec 1999 00:17:42 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Fri, 10 Dec 1999 00:17:26 +0100 To: Julian Elischer , Joe Greco From: Brad Knowles Subject: Re: Route table leaks Cc: Bob Vaughan , freebsd@gndrsh.dnsmgr.net, mike@sentex.net, current@FreeBSD.ORG, jdp@polstra.com, stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:00 PM -0800 1999/12/9, Julian Elischer wrote: > so can it be committed? In -CURRENT, I would say that this could probably be committed, if John feels safe. I am not yet convinced that it should be committed to -STABLE, although things do look good so far. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 15:32:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9606E14D29; Thu, 9 Dec 1999 15:32: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.3/8.9.3) with ESMTP id PAA01254; Thu, 9 Dec 1999 15:32:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA39382; Thu, 9 Dec 1999 15:32:38 -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: Thu, 09 Dec 1999 15:32:38 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Brad Knowles Subject: Re: Route table leaks Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > In -CURRENT, I would say that this could probably be committed, > if John feels safe. I am not yet convinced that it should be > committed to -STABLE, although things do look good so far. Just to clarify, I committed it to -current already this morning. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 15:59:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 7C1F715475 for ; Thu, 9 Dec 1999 15:59:38 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id PAA76217; Thu, 9 Dec 1999 15:59:35 -0800 (PST) From: Archie Cobbs Message-Id: <199912092359.PAA76217@bubba.whistle.com> Subject: Re: Modules and sysctl tree In-Reply-To: from Andrzej Bialecki at "Dec 9, 1999 06:06:41 pm" To: abial@webgiro.com (Andrzej Bialecki) Date: Thu, 9 Dec 1999 15:59:35 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki writes: > I'd like to know whether we reached some conclusions concerning the naming > of sysctl variables created (or related to) KLDs. I know that Linux > emulator creates "compat.linux". I don't know if any other module creates > sysctls (well, except my SPY module.. :-). > > So, what is the current thinking? Should we use > > modules.my_module.whatever, or > > kld.my_kld.whatever, or > > just sprinkle the new sysctls randomly over the tree, according to their > functions, e.g. > > kern.my_module_kern_hook > net.inet.my_module_inet_hook > ... I think the latter. In 'theory' there should be no discernable difference between functionality from a KLD vs. the same functionality compiled directly into the kernel. KLD's are just a linking mechanism, and shouldn't have any more significance than that from a usability perspective. -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 Thu Dec 9 16:25:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 74A7E15631; Thu, 9 Dec 1999 16:25:38 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id BAA16623; Fri, 10 Dec 1999 01:02:51 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA01858; Fri, 10 Dec 1999 00:58:17 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912092358.AAA01858@yedi.iaf.nl> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912091926.MAA13459@harmony.village.org> from Warner Losh at "Dec 9, 1999 12:26: 3 pm" To: imp@village.org (Warner Losh) Date: Fri, 10 Dec 1999 00:58:17 +0100 (CET) Cc: msmith@FreeBSD.ORG, chris@netmonger.net, julian@whistle.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Warner Losh wrote ... > In message <199912082219.XAA77409@yedi.iaf.nl> Wilko Bulte writes: > : Not quite true: the esp driver for the alphas got lost. No attack on anyone, > : just stating a fact. > > As did the sea and uha drivers. I had a fantacy that I'd have time to > write one. However, I didn't... :-( uha, yeah. I have an Ultrastor somewhere around here. But no active EISA box anymore. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 16:25:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id AF43515631; Thu, 9 Dec 1999 16:25:45 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id BAA16617; Fri, 10 Dec 1999 01:02:48 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA01850; Fri, 10 Dec 1999 00:56:58 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912092356.AAA01850@yedi.iaf.nl> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991209205701.D65692@daemon.ninth-circle.org> from Jeroen Ruigrok/Asmodai at "Dec 9, 1999 8:57: 2 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Fri, 10 Dec 1999 00:56:58 +0100 (CET) Cc: msmith@FreeBSD.ORG, chris@netmonger.net, julian@whistle.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Jeroen Ruigrok/Asmodai wrote ... > -On [19991209 12:00], Wilko Bulte (wilko@yedi.iaf.nl) wrote: > >As Mike Smith wrote ... > >> > On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote: > > > >> > [there] were the SCSI drivers lost to CAM > >> > >> Actually, most of this is histrionics. CAM didn't lose us SCSI drivers; > > > >Not quite true: the esp driver for the alphas got lost. No attack on anyone, > >just stating a fact. > > Another state of fact, until no-one finds it annoying enough to fix it > it will be Atticised for quite some time longer. True. No doubt. > Apparantly the people whom caused a ruckus about losing some > functionality when moving to better designed new driver framework > weren't quite that bothered at all. Else we would've seen submissions > for those drivers to be upgraded to the new framework. Luoqi is a prime > example for aic. (If my memory serves me right.) FWIW: I only discovered the esp thingy when I found myself with a Turbochannel Alpha box. Not earlier. ;) -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 16:25:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 993A415777; Thu, 9 Dec 1999 16:25:53 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id BAA16622; Fri, 10 Dec 1999 01:02:50 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA01866; Fri, 10 Dec 1999 00:59:17 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912092359.AAA01866@yedi.iaf.nl> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912091925.MAA13446@harmony.village.org> from Warner Losh at "Dec 9, 1999 12:25:20 pm" To: imp@village.org (Warner Losh) Date: Fri, 10 Dec 1999 00:59:17 +0100 (CET) Cc: brian@Awfulhak.org, julian@whistle.com, jmb@hub.freebsd.org, chris@netmonger.net, msmith@FreeBSD.ORG, current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Warner Losh wrote ... > In message <199912090623.GAA11752@hak.lan.Awfulhak.org> Brian Somers writes: > : The aha driver broke somewhere between the 5th and 8th of this month. > : Boot -v says ``aha0: status reg test failed ff''. > > Odd.. What kind of card do you have? Does it make a difference if you run boot without -v ? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 18:32:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-105.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.233]) by hub.freebsd.org (Postfix) with ESMTP id A955414C02; Thu, 9 Dec 1999 18:32:37 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA03291; Fri, 10 Dec 1999 00:16:38 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA04551; Fri, 10 Dec 1999 00:17:51 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912100017.AAA04551@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Warner Losh Cc: Brian Somers , Julian Elischer , "Jonathan M. Bresler" , chris@netmonger.net, msmith@FreeBSD.ORG, current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org, brian@hak.lan.Awfulhak.org Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: Message from Warner Losh of "Thu, 09 Dec 1999 12:25:20 MST." <199912091925.MAA13446@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 00:17:51 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199912090623.GAA11752@hak.lan.Awfulhak.org> Brian Somers writes: > : The aha driver broke somewhere between the 5th and 8th of this month. > : Boot -v says ``aha0: status reg test failed ff''. > > Odd.. What kind of card do you have? aha0 at port 0x330-0x333 irq 11 drq 7 on isa0 aha0: AHA-1542CP FW Rev. D.0 (ID=46) SCSI Host Adapter, SCSI ID 7, 16 CCBs It's PnP, but the BIOS says non-PnP OS and is assigning irq11/drq7 both with the old & new kernels. The working kernel is a ``cd /sys; cvs up -D991205'' kernel and the broken one is anything more recent (although I don't know exactly where it broke). I'll try to get some time on the weekend to roll things forward 'till they break.... I moved my ISDN card from 0x160 because it was causing problems with wdc1 (@ 0x170) (which may be why ata1 was jamming up) to 0x260, but the card uses a whole bunch of i/o addresses.... The working kernel from the 5th has no ISDN support because I had to build it on another machine (one without the i4b patches installed). It's a horrible mess. If nobody else complains about ata, I'd assume it's just pilot error. > Warner -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 18:36:12 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 1653714C02; Thu, 9 Dec 1999 18:36:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id F38861CD750 for ; Thu, 9 Dec 1999 18:36:10 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 9 Dec 1999 18:36:10 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: OpenSSL update Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Due to time constraints (exams) I haven't been able to do much more towards the OpenSSL build infrastructure (specifically, jumping through the requisite hoops for US stupidity). I have it building fine, although compiling without RSA seems broken in openssl 0.9.4. Unfortunately, the openssl binary seems to depend nontrivially on both libcrypto and libssl, so we can't get away with just importing the former, without some recoding. Since I'm flying back home to australia next tuesday, and we have a feature freeze for -current coming up, what I'll probably do is just import all of openssl into the international repository, and enable the build only for people who have defined USA_RESIDENT==NO. When I get back in January I can get the munged version (i.e. w/o RSA sources, optionally building with RSAREF) imported and enabled for US people, as well as solving the binary distribution problem. The alternative, given the feature freeze, seems to be to forgo any kind of enhanced crypto support in 4.x, which would suck. Sound okay to everyone? Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 22:25:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-29.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.157]) by hub.freebsd.org (Postfix) with ESMTP id 624C4153B3; Thu, 9 Dec 1999 22:25:43 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id GAA04237; Fri, 10 Dec 1999 06:25:46 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id GAA01203; Fri, 10 Dec 1999 06:26:59 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912100626.GAA01203@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Wilko Bulte Cc: imp@village.org (Warner Losh), brian@Awfulhak.org, julian@whistle.com, jmb@hub.freebsd.org, chris@netmonger.net, msmith@FreeBSD.ORG, current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org, brian@hak.lan.Awfulhak.org Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: Message from Wilko Bulte of "Fri, 10 Dec 1999 00:59:17 +0100." <199912092359.AAA01866@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 06:26:59 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As Warner Losh wrote ... > > In message <199912090623.GAA11752@hak.lan.Awfulhak.org> Brian Somers writes: > > : The aha driver broke somewhere between the 5th and 8th of this month. > > : Boot -v says ``aha0: status reg test failed ff''. > > > > Odd.. What kind of card do you have? > > Does it make a difference if you run boot without -v ? Nope :-( > -- > Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project > WWW : http://www.tcja.nl http://www.freebsd.org > -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 22:42:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id AD62214FCF for ; Thu, 9 Dec 1999 22:42:12 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id HAA15284 for ; Fri, 10 Dec 1999 07:42:10 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id HAA11864 for ; Fri, 10 Dec 1999 07:42:09 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id HAA20660 for ; Fri, 10 Dec 1999 07:42:09 +0100 (CET) Date: Fri, 10 Dec 1999 07:42:05 +0100 From: Andre Albsmeier To: Alfred Perlstein Cc: Andre Albsmeier , Warner Losh , Garance A Drosihn , current@FreeBSD.ORG Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test Message-ID: <19991210074205.B12325@internal> References: <19991209153320.A62121@internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bright@wintelcom.net on Thu, Dec 09, 1999 at 03:02:41PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 09-Dec-1999 at 15:02:41 -0800, Alfred Perlstein wrote: > On Thu, 9 Dec 1999, Andre Albsmeier wrote: > > ... > > > For better reference, here is the current patch: > > > > *** lpr.c.ORI Thu Dec 9 15:30:18 1999 > > --- lpr.c Thu Dec 9 15:30:35 1999 > > *************** > > *** 370,375 **** > > --- 370,405 ---- > > } > > if (sflag) > > printf("%s: %s: not linked, copying instead\n", name, arg); > > + /* > > + * If lpr was invoked with -r we try to move the file to > > + * be printed instead of copying and deleting it later. > > + * This works if the file and lpd's spool directory are > > + * on the same filesystem as it is often the case for files > > + * printed by samba or pcnfsd. In this case, a lot of I/O > > + * and temporary disk space can be avoided. Otherwise, we > > + * will continue normally. > > + */ > > + if (f) { /* file should be deleted */ > > + seteuid(euid); /* needed for rename() */ > > + if (!rename(arg, dfname)) { > > + int i; > > + #if 0 > > + chown(dfname, userid, getegid()); > > + chmod(dfname, S_IRUSR | S_IWUSR | > > + S_IRGRP | S_IWGRP); > > + #endif > > + seteuid(uid); /* restore old uid */ > > + if (format == 'p') > > + card('T', title ? title : arg); > > + for (i = 0; i < ncopies; i++) > > + card(format, &dfname[inchar-2]); > > + card('U', &dfname[inchar-2]); > > + card('N', arg); > > + nact++; > > + continue; > > + } > > + seteuid(uid); /* restore old uid */ > > + } > > if ((i = open(arg, O_RDONLY)) < 0) { > > printf("%s: cannot open %s\n", name, arg); > > } else { > > > > > > I don't have too much time to think about this, argue me this: Sure, please tell me if you don't want to get CC'ed on this anymore. > > why should I allow a user to print any file on the system? > > the race condition is still there. Right :-(. The file won't be given to the user anymore but he can print everything. However, there must be a solution for this... > > -Alfred > -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 22:45:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from oskar.dev.nanoteq.co.za (oskar.dev.nanoteq.co.za [196.7.114.5]) by hub.freebsd.org (Postfix) with ESMTP id 2F7DE14FCF for ; Thu, 9 Dec 1999 22:45:35 -0800 (PST) (envelope-from rbezuide@oskar.dev.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id IAA29289; Fri, 10 Dec 1999 08:43:55 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199912100643.IAA29289@oskar.dev.nanoteq.co.za> Subject: Re: Flash (was: Re: Sound card support) In-Reply-To: <19991209203205.B65692@daemon.ninth-circle.org> from Jeroen Ruigrok/Asmodai at "Dec 9, 99 08:32:05 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Fri, 10 Dec 1999 08:43:55 +0200 (SAT) Cc: dmmiller@cvzoom.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 .. Under current the flash plugin works with the linux version of Netscape and the linuxelator ... Sound etc, everything works ok ... except for the odd crash of netscape which is normal :) Just get the linux netscape and the linux flash plugin. Reinier > [again subject changes] > > -On [19991209 16:00], Donn Miller (dmmiller@cvzoom.net) wrote: > >On Thu, 9 Dec 1999, Motoyuki Konno wrote: > > > >> Please see Netscape plugin port (ports/www/flashplugin) to find > >> out why we still have to need a.out support. > > > >Wow -- there's a flash plugin for Netscape? That's what I needed for a > >couple of web sites. > > Good luck using it under current. > > First site you hit quits netscape without reasons... > > ...until you drop out of X and see a __sh_getcontext IIRC warning on > your console. > > I already mailed maintainer about this. > > -- > Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] > Documentation nutter. *BSD: Technical excellence at its best... > The BSD Programmer's Documentation Project > Atone me to my throes curtail... > > > 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 Dec 9 23:38: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 080D915388; Thu, 9 Dec 1999 23:36:49 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id CAA24068; Fri, 10 Dec 1999 02:28:51 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Fri, 10 Dec 1999 02:28:51 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: OpenSSL update 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, 9 Dec 1999, Kris Kennaway wrote: > Due to time constraints (exams) I haven't been able to do much more > towards the OpenSSL build infrastructure (specifically, jumping through > the requisite hoops for US stupidity). I have it building fine, although > compiling without RSA seems broken in openssl 0.9.4. Unfortunately, the > openssl binary seems to depend nontrivially on both libcrypto and libssl, > so we can't get away with just importing the former, without some > recoding. Why don't you want libssl, too? If we don't have that, then we'll end up having to install the port for using SSL and there will be redundancy (wasted space) and two copies of OpenSSL to maintain, still. > > Since I'm flying back home to australia next tuesday, and we have a > feature freeze for -current coming up, what I'll probably do is just > import all of openssl into the international repository, and enable the > build only for people who have defined USA_RESIDENT==NO. When I get back > in January I can get the munged version (i.e. w/o RSA sources, optionally > building with RSAREF) imported and enabled for US people, as well as > solving the binary distribution problem. The alternative, given the > feature freeze, seems to be to forgo any kind of enhanced crypto support > in 4.x, which would suck. > > Sound okay to everyone? Sounds great. I hope this means I get to import OpenSSH! > Kris > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 9 23:49:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D2B421564D; Thu, 9 Dec 1999 23:49:09 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id CAA24127; Fri, 10 Dec 1999 02:37:21 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Fri, 10 Dec 1999 02:37:21 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Soren Schmidt Cc: Julian Elischer , Poul-Henning Kamp , current@FreeBSD.org Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912081721.SAA70567@freebsd.dk> Message-ID: 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 On Wed, 8 Dec 1999, Soren Schmidt wrote: > It seems Julian Elischer wrote: > > > please do not remove it.. > > And why is that ?? There is no point in having done a new one then, and > you guys have known I've been working on this for ages so this cannot > come as a surprise to anybody... > > The same thing is about to apply to the woxware sound code, we have a > new shiny system that works and is much better designed... ATA doesn't do ESDI, does it? Therefore, wd(4) should still be available. NewPCM doesn't work with all the equipment VoxWare does, does it? I don't want to lose my SB16 (non-PnP) FM, certainly. > > -Søren > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 0:25: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 939D415176; Fri, 10 Dec 1999 00:25:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7E4D01CD79D; Fri, 10 Dec 1999 00:25:01 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 10 Dec 1999 00:25:01 -0800 (PST) From: Kris Kennaway To: Brian Fundakowski Feldman Cc: current@FreeBSD.org Subject: Re: OpenSSL update In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Dec 1999, Brian Fundakowski Feldman wrote: > Why don't you want libssl, too? If we don't have that, then we'll > end up having to install the port for using SSL and there will be > redundancy (wasted space) and two copies of OpenSSL to maintain, > still. Since it wasn't going to be used immediately it was suggested to leave it out for now. However it doesn't seem feasible anyway. > > Since I'm flying back home to australia next tuesday, and we have a > > feature freeze for -current coming up, what I'll probably do is just > > import all of openssl into the international repository, and enable the > > build only for people who have defined USA_RESIDENT==NO. When I get back > > in January I can get the munged version (i.e. w/o RSA sources, optionally > > building with RSAREF) imported and enabled for US people, as well as > > solving the binary distribution problem. The alternative, given the > > feature freeze, seems to be to forgo any kind of enhanced crypto support > > in 4.x, which would suck. > > > > Sound okay to everyone? > > Sounds great. I hope this means I get to import OpenSSH! Due to the US export stupidity someone else would probably have to import it into internat so the actual code doesn't leave the US, but historically we seem to have allowed non-crypto commits once it's there (e.g. minor changes, etc). Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 0:49: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id CF16C15244 for ; Fri, 10 Dec 1999 00:48:59 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 671A52DC07; Fri, 10 Dec 1999 09:49:44 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id EF13C7811; Fri, 10 Dec 1999 09:48:13 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id DB93010E10; Fri, 10 Dec 1999 09:48:13 +0100 (CET) Date: Fri, 10 Dec 1999 09:48:12 +0100 (CET) From: Andrzej Bialecki To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree In-Reply-To: <199912092359.PAA76217@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 Thu, 9 Dec 1999, Archie Cobbs wrote: > Andrzej Bialecki writes: > > I'd like to know whether we reached some conclusions concerning the naming > > of sysctl variables created (or related to) KLDs. I know that Linux > > emulator creates "compat.linux". I don't know if any other module creates > > sysctls (well, except my SPY module.. :-). > > > > So, what is the current thinking? Should we use > > > > modules.my_module.whatever, or > > > > kld.my_kld.whatever, or > > > > just sprinkle the new sysctls randomly over the tree, according to their > > functions, e.g. > > > > kern.my_module_kern_hook > > net.inet.my_module_inet_hook > > ... > > I think the latter. In 'theory' there should be no discernable > difference between functionality from a KLD vs. the same functionality > compiled directly into the kernel. Yes, assuming that the same functionality CAN be compiled in statically. IMHO the kernel modularity is a laudable goal, and if it works well, there are only few cases when you would want to make a monolithic kernel. IMHO, of course :-) > KLD's are just a linking mechanism, and shouldn't have any more > significance than that from a usability perspective. Hah. If it were so simple... Let's take the example of a module foo, which provides unique features of bar and baz. They are unrelated to any already existing category. Where they should be hooked up? kernel? machdep? Then these categories will become a messy, amorphic trashcans. Also, it will be difficult to see which sysctls will disappear when the module is unloaded. Also, if we say that modules should register their sysctls in easily discernible place in the tree, we set up a good example for third party vendors, who otherwise will sprinkle their own sysctls all over the tree... You can probably see from the above what is my preference.. ;-) More or less, my question is: how the sysctl tree will look like when _most_ of the kernel will be in modules? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 1:22:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 4DF4515728 for ; Fri, 10 Dec 1999 01:22:07 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id LAA18023; Fri, 10 Dec 1999 11:21:23 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199912100921.LAA18023@zibbi.mikom.csir.co.za> Subject: Re: make release broken In-Reply-To: <384F8925.EB62F76C@scc.nl> from Marcel Moolenaar at "Dec 9, 1999 11:49:09 am" To: marcel@scc.nl (Marcel Moolenaar) Date: Fri, 10 Dec 1999 11:21:23 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Make release in a -current cvsuped just now broke. It looks like the aout > > directory is not there. > > Fixed. Thanks. I'm testing as well, so if anything comes up, let me > know. Ok, It got a little further. It now dies with during the "Rebuilding dependencies" phase with: ---------- mkdep -f .depend -a -nostdinc -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/c++filt/../cc_tools -I/usr/src/gnu/usr.bin/cc/c++filt/../cc_tools -I/usr/src/gnu/usr.bin/cc/c++filt/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/c++filt/../../../../contrib/gcc/config -DMAIN -DIN_GCC -DVERSION=\"2.95.2\" -I/usr/obj/usr/src/tmp/usr/include /usr/src/gnu/usr.bin/cc/c++filt/../../../../contrib/gcc/cplus-dem.c /usr/src/gnu/usr.bin/cc/c++filt/../../../../contrib/gcc/getopt.c /usr/src/gnu/usr.bin/cc/c++filt/../../../../contrib/gcc/getopt1.c underscore.c cd /usr/src/gnu/usr.bin/cc/c++filt; make _EXTRADEPEND echo c++filt: /usr/obj/usr/src/tmp/usr/lib/libc.a >> .depend ===> gnu/usr.bin/cc/doc ===> gnu/usr.bin/cc/cc1obj make: don't know how to make objc-parse.c. Stop *** Error code 2 ---------- The reason is that in Makefile.inc1 BMAKE sets -DNO_OBJC (and a lot of others). BMAKE is used to do the cleanup and make the obj dirs, so the /usr/obj/usr/src/gnu/usr.bin/cc/cc1obj dir is never created. To make the dependencies and the rest XMAKE is used and then -DNO_OBJC and friends are not defined... Wipe your /usr/obj dir and do a make world, and you will see. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 1:36:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 2375615827 for ; Fri, 10 Dec 1999 01:36:35 -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.3/8.9.3) with ESMTP id BAA61582; Fri, 10 Dec 1999 01:35:26 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912100935.BAA61582@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Reinier Bezuidenhout Cc: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai), dmmiller@cvzoom.net, current@FreeBSD.ORG Subject: Re: Flash (was: Re: Sound card support) In-reply-to: Your message of "Sat, 10 Dec 1999 08:43:55 +0200." <199912100643.IAA29289@oskar.dev.nanoteq.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 01:35:25 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi .. > > Under current the flash plugin works with the linux version of > Netscape and the linuxelator ... Sound etc, everything works ok ... > except for the odd crash of netscape which is normal :) Hmmm. The developers of mozilla are dying to get bug reports http://www.mozilla.org 8) Someone for berkeley.edu last week reported 36 bugs which made the developers very happy ... -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 1:41: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (Postfix) with SMTP id 71FBD1539D for ; Fri, 10 Dec 1999 01:40:53 -0800 (PST) (envelope-from ab@paert.tse-online.de) Received: (qmail 32154 invoked by uid 1000); 10 Dec 1999 09:45:38 -0000 Date: Fri, 10 Dec 1999 10:45:38 +0100 From: Andreas Braukmann To: Dmitrij Tejblum Cc: knu@idaemons.org, current@FreeBSD.ORG Subject: Re: Flash (was: Re: Sound card support) Message-ID: <19991210104538.T802@paert.tse-online.de> References: <19991209203205.B65692@daemon.ninth-circle.org> <199912092017.XAA46056@arc.hq.cti.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912092017.XAA46056@arc.hq.cti.ru> Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Thu, Dec 09, 1999 at 11:16:58PM +0300, Dmitrij Tejblum wrote: > > Good luck using it under current. > > > > First site you hit quits netscape without reasons... ... yes. I built the port for the first time just yesterday and made the same experience. > > ...until you drop out of X and see a __sh_getcontext IIRC warning on > > your console. > > If you can hack on the flash plugin's Makefile, try add -fno-exceptions > there. ... many thanks for the tip. It's up and running. Regards, Andreas P.S.: ... the port's maintainer is cc-ed ... -- : TSE GmbH Neue Medien : Gsf: Arne Reuter : : : Hovestrasse 14 : Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP : :--------------------------------------------------------------------: : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 2: 3:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2012E15154 for ; Fri, 10 Dec 1999 02:03:48 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id CAA14691; Fri, 10 Dec 1999 02:33:29 -0800 (PST) Date: Fri, 10 Dec 1999 02:33:29 -0800 (PST) From: Alfred Perlstein To: Andre Albsmeier Cc: Warner Losh , Garance A Drosihn , current@FreeBSD.ORG Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test In-Reply-To: <19991210074205.B12325@internal> Message-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, 10 Dec 1999, Andre Albsmeier wrote: > On Thu, 09-Dec-1999 at 15:02:41 -0800, Alfred Perlstein wrote: > > On Thu, 9 Dec 1999, Andre Albsmeier wrote: > > > > ... > > > > > For better reference, here is the current patch: > > > > > > > I don't have too much time to think about this, argue me this: > > Sure, please tell me if you don't want to get CC'ed on this anymore. I'm sorry if I sounded like that, I didn't mean to. :) > > why should I allow a user to print any file on the system? > > > > the race condition is still there. > > Right :-(. The file won't be given to the user anymore but he can > print everything. However, there must be a solution for this... Can someone take a look at this? Basically, it makes the link to the file, if it can unlink the original it will then chown the spool file if it can't delete or read the original then the user didn't have permission and it backs out. Index: lpr.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/lpr/lpr/lpr.c,v retrieving revision 1.31 diff -u -r1.31 lpr.c --- lpr.c 1999/11/30 16:15:22 1.31 +++ lpr.c 1999/12/10 14:09:08 @@ -384,6 +384,46 @@ } if (sflag) printf("%s: %s: not linked, copying instead\n", name, arg); + if (f) { + seteuid(euid); + if (link(arg, dfname) == 0) { + int ret; + + seteuid(uid); + /* + * if we can access and remove the file without + * special setuid-ness then allow it. + */ + ret = access(dfname, R_OK); + if (ret == 0) + ret = unlink(arg); + seteuid(euid); + if (ret == 0) { + /* unlink was successful fixup perms */ + chown(dfname, userid, getegid()); + chmod(dfname, S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP); + } else { + /* + * the user handed me a file the don't have access to, + * remove it from the spooldir and try other methods + */ + unlink(dfname); + seteuid(uid); + goto nohardlink; + } + seteuid(uid); + if (format == 'p') + card('T', title ? title : arg); + for (i = 0; i < ncopies; i++) + card(format, &dfname[inchar-2]); + card('U', &dfname[inchar-2]); + card('N', arg); + nact++; + continue; + } + seteuid(uid); /* restore old uid */ + } +nohardlink: if ((i = open(arg, O_RDONLY)) < 0) { printf("%s: cannot open %s\n", name, arg); } else { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 2:10:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id B272C15235 for ; Fri, 10 Dec 1999 02:10:12 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11wMzs-000EXV-00; Fri, 10 Dec 1999 10:09:56 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id LAA08587; Fri, 10 Dec 1999 11:10:06 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <3850D17E.63C6B2D8@scc.nl> Date: Fri, 10 Dec 1999 11:10:06 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Hay Cc: current@FreeBSD.ORG Subject: Re: make release broken References: <199912100921.LAA18023@zibbi.mikom.csir.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > The reason is that in Makefile.inc1 BMAKE sets -DNO_OBJC (and a lot of > others). BMAKE is used to do the cleanup and make the obj dirs, so the > /usr/obj/usr/src/gnu/usr.bin/cc/cc1obj dir is never created. To make > the dependencies and the rest XMAKE is used and then -DNO_OBJC and > friends are not defined... I already have a fix for this. The object tree should not be created using BMAKE, but must be created using XMAKE. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 2:29:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 1299E15372; Fri, 10 Dec 1999 02:29:30 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id LAA20403; Fri, 10 Dec 1999 11:28:59 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Fri, 10 Dec 1999 11:28:43 +0100 To: Julian Elischer , Joe Greco From: Brad Knowles Subject: Re: Route table leaks Cc: Bob Vaughan , freebsd@gndrsh.dnsmgr.net, mike@sentex.net, current@FreeBSD.ORG, jdp@polstra.com, stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:17 AM +0100 1999/12/10, Brad Knowles wrote: > In -CURRENT, I would say that this could probably be committed, > if John feels safe. I am not yet convinced that it should be > committed to -STABLE, although things do look good so far. Well, things continue to look good: Fri Dec 10 10:59:55 CET 1999 netstat -ran | wc -l 121 vmstat -m | grep routetbl | grep K routetbl 246 34K 35K 40960K 275 0 0 16,32,64,128,256 uptime 10:59AM up 16:08, 0 users, load averages: 3.49, 3.83, 3.61 Fri Dec 10 11:00:56 CET 1999 netstat -ran | wc -l 120 vmstat -m | grep routetbl | grep K routetbl 244 34K 35K 40960K 275 0 0 16,32,64,128,256 uptime 11:00AM up 16:09, 0 users, load averages: 3.41, 3.81, 3.62 Looking at our stats for yesterday on this machine, we came pretty close to setting some new records for volume, and did quite a lot of articles. At this stage, given that this patch has fixed John's problems, that the previous patch appears to have fixed Joe's problems, and that I seem to be running fine after almost a day, I'd feel more comfortable if John decides he wants to commit this patch to -STABLE. When that happens, I'll cvsup & rebuild all the machines I can, so that they can all get the benefit of this patch and the other changes that have gone in recently. Thanks! -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 2:43:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 8E13C15235; Fri, 10 Dec 1999 02:43:42 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-3.iptelecom.net.ua [212.9.227.3]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id MAA23757; Fri, 10 Dec 1999 12:47:57 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id MAA08163; Fri, 10 Dec 1999 12:43:04 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <3850D936.FC555200@altavista.net> Date: Fri, 10 Dec 1999 12:43:02 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Peter Jeremy , current@freebsd.org Cc: soren@freebsd.org Subject: Partial disabling of wd functionality (Was: Re: HEADSUP: wd driver will be retired!) References: <384EE77A.FC42FD9@altavista.net> <99Dec10.124407est.40329@border.alcanet.com.au> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > On 1999-Dec-09 10:19:22 +1100, Maxim Sobolev wrote: > > Why do not remove from wd driver support for chipsets > >already implemented/tested in ata driver? > > This requires additional developer effort - appropriate changes have to > be determined and tested. It's easy to totally remove the old driver, > it would be a fair amount of effort to disable the functionality also > provided by the new driver, without affecting the other functionality. I'm not talking about disabling all functionality for partcular chips. It would be sufficient to disable in wd DMA/UDMA support for chipsets already supported by ata, which will encourage all users with these chipsets to use ata (while in case of any problems they still will be able to fallback to wd though it would work somewhat slower). -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 3: 1:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8A8F415388; Fri, 10 Dec 1999 03:01:29 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA71445; Fri, 10 Dec 1999 12:00:18 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912101100.MAA71445@freebsd.dk> Subject: Re: Partial disabling of wd functionality (Was: Re: HEADSUP: wd driver will be retired!) In-Reply-To: <3850D936.FC555200@altavista.net> from Maxim Sobolev at "Dec 10, 1999 12:43:02 pm" To: sobomax@altavista.net Date: Fri, 10 Dec 1999 12:00:18 +0100 (CET) Cc: peter.jeremy@alcatel.com.au (Peter Jeremy), current@FreeBSD.ORG, soren@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Maxim Sobolev wrote: > Peter Jeremy wrote: > > > On 1999-Dec-09 10:19:22 +1100, Maxim Sobolev wrote: > > > Why do not remove from wd driver support for chipsets > > >already implemented/tested in ata driver? > > > > This requires additional developer effort - appropriate changes have to > > be determined and tested. It's easy to totally remove the old driver, > > it would be a fair amount of effort to disable the functionality also > > provided by the new driver, without affecting the other functionality. > > I'm not talking about disabling all functionality for partcular chips. It would > be sufficient to disable in wd DMA/UDMA support for chipsets already supported > by ata, which will encourage all users with these chipsets to use ata (while in > case of any problems they still will be able to fallback to wd though it would > work somewhat slower). When I do my next commit to the ata driver suite, only the Cyrix chipset will be unsupported, and that is AFAIK used in embedded systems, not in ordinary PC's. I've got the docs on the Cyrix, so support for that might actually come too... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 3:19:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id EE3781534F for ; Fri, 10 Dec 1999 03:19:33 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcm211.cvzoom.net (lcm211.cvzoom.net [208.230.69.211]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id GAA02585 for ; Fri, 10 Dec 1999 06:00:06 -0500 (EST) Date: Fri, 10 Dec 1999 06:18:34 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: SiS 5591 ATA controller and latest -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I rebuilt my kernel on Tuesday or thereabouts with the new ata controller. It worked perfectly with my SiS 5591. But, with the latest cvsup, now the boot hangs and the hard drive is on solid when it gets to the part mounting root on /dev/ad0s1a. Also, my UDMA/33 drive gets probed as a regular DMA drive before the hang occurs. I had to boot into kernel.old, which had a slightly older (3 days old) version of the ata driver. Here's the output of dmesg with kernel.old: ad0: ATA-3 disk at ata0 as master ad0: 3093MB (6335280 sectors), 6704 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 Now, here's the output I get before my machine hangs: ad0: ATA-3 disk at ata0 as master ad0: 3093MB (6335280 sectors), 6704 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, DMA I used identical kernel config files, and I had these options enabled: options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices Well, this was the same config file that gave me the correct UDMA33 probe previously. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 3:41: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8E5BC151CD for ; Fri, 10 Dec 1999 03:41:06 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA81039; Fri, 10 Dec 1999 12:40:57 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912101140.MAA81039@freebsd.dk> Subject: Re: SiS 5591 ATA controller and latest -current' In-Reply-To: from Donn Miller at "Dec 10, 1999 06:18:34 am" To: dmmiller@cvzoom.net (Donn Miller) Date: Fri, 10 Dec 1999 12:40:57 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Donn Miller wrote: > I rebuilt my kernel on Tuesday or thereabouts with the new ata > controller. It worked perfectly with my SiS 5591. But, with the latest > cvsup, now the boot hangs and the hard drive is on solid when it gets to > the part mounting root on /dev/ad0s1a. Also, my UDMA/33 drive gets probed > as a regular DMA drive before the hang occurs. Erhm, there is NO support for the SIS5591 in the official sources, so I dont see how you should have gotten UDMA33 with that, are you sure you havn't applied the experimental patches I posted here to the older kernel ?? > I had to boot into kernel.old, which had a slightly older (3 days > old) version of the ata driver. Here's the output of dmesg with > kernel.old: > > ad0: ATA-3 disk at ata0 as master > ad0: 3093MB (6335280 sectors), 6704 cyls, 15 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, UDMA33 > > Now, here's the output I get before my machine hangs: > > ad0: ATA-3 disk at ata0 as master > ad0: 3093MB (6335280 sectors), 6704 cyls, 15 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, DMA > > I used identical kernel config files, and I had these options enabled: > > options ATA_STATIC_ID #Static device numbering > options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices > > Well, this was the same config file that gave me the correct UDMA33 probe > previously. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 3:49:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 0B10B1507F for ; Fri, 10 Dec 1999 03:49:09 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcm211.cvzoom.net (lcm211.cvzoom.net [208.230.69.211]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id GAA03779; Fri, 10 Dec 1999 06:29:39 -0500 (EST) Date: Fri, 10 Dec 1999 06:48:07 -0500 (EST) From: Donn Miller To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: SiS 5591 ATA controller and latest -current' In-Reply-To: <199912101140.MAA81039@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Dec 1999, Soren Schmidt wrote: > Erhm, there is NO support for the SIS5591 in the official sources, so > I dont see how you should have gotten UDMA33 with that, are you sure > you havn't applied the experimental patches I posted here to the > older kernel ?? Yes, come to think of it, I did remember applying the patches to the "older", previous kernel. When I cvsup'd the new sources, I didn't apply the patch. Thanks for the info. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 5: 0:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 6A9AD1525B for ; Fri, 10 Dec 1999 05:00:16 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p24-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.121]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id VAA23060; Fri, 10 Dec 1999 21:59:36 +0900 (JST) Message-ID: <3850F88D.92172FB0@newsguy.com> Date: Fri, 10 Dec 1999 21:56:45 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Chuck Robey Cc: Motoyuki Konno , current@FreeBSD.ORG Subject: Re: why 'The legacy aout build' was removed from current ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > This isn't taking the execution of aout binaries out, just stopping a > world build. This is only going to stop 3rd party developers from making > a 4.0 aout platform to create *more* aout binaries. They'll probably hang > on for dear life on 2.2, just as long as they can. Heh. :-) True enough. But *new* developments won't. What Motoyuki-san is complaining about is that applications that depend on a.out libraries will suffer. Alas, I don't think that's the case, since all these libraries are (or ought to be, anyway) in compat. > Looking at copious examples from real life, forcing 3rd party developers > to upgrade is a good way to lose 3rd party developers. It just *sounds* > like a good way to go. As long as this is a change for building world, > and not making changes to the kern/imgact things (so we keep on executing > aout binaries) then this is probably the best way to go. OTOH, going the other way around is the reason why we (users) had to deal with things like 1 Mb RAM and 64 Kb segments in the age of 486s, one generation after the introduction of the 80386. As a free operating system supported by volunteer effort, we are interested in driving the hardware to it's limits instead of being limited by the ways we once did things. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 6:31:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 75F5F14D5F for ; Fri, 10 Dec 1999 06:31:19 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id PAA27635 for freebsd-current@freebsd.org; Fri, 10 Dec 1999 15:31:17 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id MAA29532 for freebsd-current@freebsd.org; Fri, 10 Dec 1999 12:30:21 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: OpenSSL update Date: 10 Dec 1999 12:30:21 +0100 Message-ID: <82qo8d$sqj$1@bigeye.rhein-neckar.de> References: To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > I have it building fine, although compiling without RSA seems > broken in openssl 0.9.4. Well, it works fine in the OpenBSD tree. You might want to take a look at what's been done there. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 7:12:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 9CF0D15356; Fri, 10 Dec 1999 07:12:32 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id KAA08195; Fri, 10 Dec 1999 10:12:20 -0500 (EST) Date: Fri, 10 Dec 1999 10:12:19 -0500 (EST) From: "Matthew N. Dodd" To: "Rodney W. Grimes" Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: MCA support In-Reply-To: <199912092215.OAA03733@gndrsh.dnsmgr.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Dec 1999, Rodney W. Grimes wrote: > > > My m77 has weird problems reading the floppy drive. I'm fairly sure this > > > has everything to do with code in the loader/bootstrap that doesn't like > > > the 2.88M drive. I used the 1.2M drive and it works great. I suspect a > > > normal 1.44M drive would be good too. > > > > The loader just uses the BIOS; you can't blame it. 8) > > I can confirm the loader problem on IBM MCA machines with 2.88M drives, > and you _CAN_ blame the loader if it does not make the _CORRECT_ calls > to the BIOS :-) Well, I stayed up hacking on boot1 last night and couldn't figure anything out. I did manage to get the 'correct' A20 setup switch implemented but that doesn't change anything. Color me confused. Any ideas? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 7:20:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 8FCD1157B4 for ; Fri, 10 Dec 1999 07:20:25 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Date: Thu, 9 Dec 1999 22:54:05 -0500 From: Greg Lehey To: Soren Schmidt Cc: Blaz Zupan , Christopher Masto , current@FreeBSD.org Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991209225405.E866@mojave.sitaranetworks.com> Reply-To: Greg Lehey References: <199912090810.JAA83704@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199912090810.JAA83704@freebsd.dk>; from sos@freebsd.dk on Thu, Dec 09, 1999 at 09:10:33AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 9 December 1999 at 9:10:33 +0100, Soren Schmidt wrote: > It seems Blaz Zupan wrote: >> On Wed, 8 Dec 1999, Christopher Masto wrote: >>> I fully agree that these things are neccessary and good. I just think >>> we need avoid jumping the gun on removing the old code, when some >>> people still need it to boot their machines. >> >> Actually I completely disagree. When you leave in old code in the tree, >> people who can't use the new code for whatever reason (technical problems, >> laziness, etc.) will use the old code. Forever. And people tend to not >> report such things - if it works with the old code, why bother? If you >> take something away from them, they will at least notice that it's broken >> and report it to the author. >> >>> From my own experience, I lost the WaveLAN driver with the newbus stuff. >> If it was somehow still working (for example through some compatibility >> code for the old bus system), I'd not have done anything about it. But as >> it was broken, I sat down and fixed it. Although my time is as limited as >> everybody else's and it took me a whole day, I leared a lot through this. > > Wonderfully put, this is the _exact_ problem we are facing here. That's certainly not the problem I see. Once the functionality is available in the new driver, I have absolutely no objections. We're getting off track again: the real issue is that you shouldn't completely replace old drivers with new, better written, less buggy drivers which have significantly less than the full functionality of the old driver. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 7:26: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 8861E1579B; Fri, 10 Dec 1999 07:25:57 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Date: Thu, 9 Dec 1999 23:01:16 -0500 From: Greg Lehey To: Daniel Eischen Cc: chris@netmonger.net, imp@village.org, current@FreeBSD.org, julian@whistle.com, msmith@FreeBSD.org Subject: Lost PCMCIA sio (was: HEADSUP: wd driver will be retired!) Message-ID: <19991209230116.F866@mojave.sitaranetworks.com> Reply-To: Greg Lehey References: <199912091346.IAA29671@pcnet1.pcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199912091346.IAA29671@pcnet1.pcnet.com>; from eischen@vigrid.com on Thu, Dec 09, 1999 at 08:46:13AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 9 December 1999 at 8:46:13 -0500, Daniel Eischen wrote: >> In message <19991208150807.A16687@netmonger.net> Christopher Masto writes: >> : Right now, I have no sound (not detected), no USB (panic on removal), >> : can't use my sio pccard, can't eject my ed pccard, my IDE drives are >> : taking hours to dump and fsck, and my TV card is missing every other >> : line if I try to use the (not working anyway) closed caption decoder. >> >> I have some patches for the can't eject the network cards from a user >> that I'm trying out and would then need to get committed to the >> network layer to properly support if_detach(). >> >> What's wrong with your sio pccard? Mine works well enough... > > Mine hasn't worked since a kernel built from Nov 23 sources. It > broke sometime between then and December 4th. Just built a new > kernel from todays sources, and still no go. > > pccardd[47]: driver allocation failed for Motorola(MONTANA 33.6 FAX/MODEM): Device not configured This closely parallels my experience. I used to get: Dec 5 11:57:53 mojave /kernel.old: sio1 at port 0x2e8-0x2ef irq 5 slot 1 on pccard0 Dec 5 11:57:53 mojave /kernel.old: sio1: type 16550A Now I get: Dec 9 20:08:02 mojave pccardd[53]: driver allocation failed for CIRRUS LOGIC 56K MODEM(CL-MD56XX): Device not configured This happened some time towards the end of last month. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 7:34:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 46A0615235 for ; Fri, 10 Dec 1999 07:34:34 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 377871CA0; Fri, 10 Dec 1999 23:34:31 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: joeo@cracktown.com Cc: current@freebsd.org Subject: Re: PNPBIOS vs cs423B codec In-Reply-To: Message from of "Thu, 09 Dec 1999 18:13:02 EST." Date: Fri, 10 Dec 1999 23:34:31 +0800 From: Peter Wemm Message-Id: <19991210153431.377871CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG joeo@cracktown.com wrote: > Managed to get the sound stuff working on this thinkpad 600e, for anyone > who cares... > > Had to update to the most recent bios, and made sure "quick boot" was > disabled (hold down F1 while powering on to get into bios). I removed the > "csa0" device from the kernel config, despite having a CS4610 probed > during boot. Also set up a pcm0 config line of the sort... > > device pcm0 at isa? port ? irq 5 drq 1 flags 0x10 > > % cat /dev/sndstat > FreeBSD Audio Driver (newpcm) Dec 9 1999 17:28:08 > Installed devices: > pcm0: at io 0x220 irq 5 drq 0:1 (1/1 channels > duplex) > > > the relevant PNP boot messages without pcm enabled... > > CSC0100: adding io range 0x530-0x537, size=0x8, align=0 > CSC0100: adding io range 0x388-0x38b, size=0x4, align=0 > CSC0100: adding io range 0x220-0x233, size=0x14, align=0x20 > CSC0100: adding irq mask 0x20 > CSC0100: adding dma mask 0x2 > CSC0100: adding dma mask 0x1 > CSC0100: start dependant > pnpbios: handle 14 device ID CSC0100 (0001630e) > > ... > > unknown6: at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 5 drq > 1,0 on isa0 Hmm.. My CS4236B chip reports as "CSC0000" pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 Vendor ID CSC0b36 (0x360b630e), Serial Number 0xffffffff PnP Version 1.0, Vendor Version 1 Device Description: CS4236 Audio Logical Device ID: CSC0000 0x0000630e #0 Device Description: WSS/SB You might try this patch to sys/dev/sound/isa: Index: mss.c =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/isa/mss.c,v retrieving revision 1.37 diff -u -r1.37 mss.c --- mss.c 1999/12/06 18:26:30 1.37 +++ mss.c 1999/12/10 15:31:49 @@ -1343,6 +1343,7 @@ switch (logical_id) { case 0x0000630e: /* CSC0000 */ + case 0x0001630e: /* CSC0100 */ if (id == 0x3700630e) s = "CS4237"; else if (id == 0x2500630e) s = "CS4235"; else if (id == 0x3600630e) s = "CS4236"; Please try this again with 'options PNPBIOS' and *only* 'device pcm0' with no 'at isa...' cruft. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 7:51:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4A01515238; Fri, 10 Dec 1999 07:51:13 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id IAA55556; Fri, 10 Dec 1999 08:51:10 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id IAA22251; Fri, 10 Dec 1999 08:51:10 -0700 (MST) Message-Id: <199912101551.IAA22251@harmony.village.org> To: Greg Lehey Subject: Re: Lost PCMCIA sio (was: HEADSUP: wd driver will be retired!) Cc: Daniel Eischen , chris@netmonger.net, current@FreeBSD.org, julian@whistle.com, msmith@FreeBSD.org In-reply-to: Your message of "Thu, 09 Dec 1999 23:01:16 EST." <19991209230116.F866@mojave.sitaranetworks.com> References: <19991209230116.F866@mojave.sitaranetworks.com> <199912091346.IAA29671@pcnet1.pcnet.com> Date: Fri, 10 Dec 1999 08:51:10 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991209230116.F866@mojave.sitaranetworks.com> Greg Lehey writes: : This happened some time towards the end of last month. Try my latest fixes. Towards the end of November, I broke sio, but spent a couple of hours last night fixing it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 8: 2:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id CD28D1523D; Fri, 10 Dec 1999 08:02:51 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id DF62D1CA0; Sat, 11 Dec 1999 00:02:47 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Jeroen Ruigrok/Asmodai Cc: Greg Lehey , Brad Knowles , Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: Message from Jeroen Ruigrok/Asmodai of "Thu, 09 Dec 1999 20:53:02 +0100." <19991209205302.C65692@daemon.ninth-circle.org> Date: Sat, 11 Dec 1999 00:02:47 +0800 From: Peter Wemm Message-Id: <19991210160247.DF62D1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > -On [19991209 16:03], Greg Lehey (grog@mojave.sitaranetworks.com) wrote: > >On Wednesday, 8 December 1999 at 20:23:24 +0100, Brad Knowles wrote: > >> > >> This is -CURRENT. It pains me to say it, but anyone trying to > >> run anything "useful" on -CURRENT gets what they deserve. This is > >> the only place where we can make clean breaks with the past, and as > >> painful as that can be, we simply have to do that occasionally. > > > >Next month it'll be -RELEASE. This isn't the time to remove such > >significant functionality. If it weren't for that, I'd agree with > >you. > > Think about that some more. > > After that it will be 4.1. Nice to give people a driver and then rip it > out when 4.1 comes when Soren fixes the last of the things people > needed to have into the ata driver. > > I was already testing the ata driver and even procured some more info > for Soren than he already had. Same goes for a bunch of other people. > But the opposite goes for a lot of people. > > People running CURRENT to be cutting edge as in being elite with the > latest FreeBSD thus get bitten. > > I'd say, cut loose the wd driver. (VoxWare removed would be cool too.) If half as much energy was spent adding the missing bits of functionality to the new systems as people have been spending complaining it then we'd be there ages ago. Trying desperately to prolong the agony by keeping the old stuff on life support is counter productive. Damn it people! If you want cyrix busmaster support, then the code is there, it's not all that hard to extract and adapt the cyrix code to ata. If you have got cyrix hardware and can test your work, then even better. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 8:12:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B007115276 for ; Fri, 10 Dec 1999 08:12:22 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id RAA05388; Fri, 10 Dec 1999 17:11:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: Soren Schmidt , Blaz Zupan , Christopher Masto , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Thu, 09 Dec 1999 22:54:05 EST." <19991209225405.E866@mojave.sitaranetworks.com> Date: Fri, 10 Dec 1999 17:11:53 +0100 Message-ID: <5386.944842313@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991209225405.E866@mojave.sitaranetworks.com>, Greg Lehey writes: >We're getting off track again: the real issue is that you shouldn't >completely replace old drivers with new, better written, less buggy >drivers which have significantly less than the full functionality of >the old driver. And while that attitude might work for an organization where some PHB type can dictate what people should or shouldn't do, experience has taught us that at some point you draw a line in the sand and force people to concentrate on the path forward. Look at the sound code to see why your proposal doesn't work in our reality. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 8:16:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B8813158A9; Fri, 10 Dec 1999 08:16:14 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id RAA05463; Fri, 10 Dec 1999 17:15:30 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: Jeroen Ruigrok/Asmodai , Greg Lehey , Brad Knowles , Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sat, 11 Dec 1999 00:02:47 +0800." <19991210160247.DF62D1CA0@overcee.netplex.com.au> Date: Fri, 10 Dec 1999 17:15:29 +0100 Message-ID: <5461.944842529@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991210160247.DF62D1CA0@overcee.netplex.com.au>, Peter Wemm writes : >> I'd say, cut loose the wd driver. (VoxWare removed would be cool too.) > >If half as much energy was spent adding the missing bits of functionality >to the new systems as people have been spending complaining it then we'd be >there ages ago. Trying desperately to prolong the agony by keeping the old >stuff on life support is counter productive. I can only agree, with all the stuff there is on front of us, the entire of energy people put into defending code which is rotting away is wasted. Please, help Sos fix ATA if you know of a problem. Please, help fix PCCARD if you know of a problem. Please DO SOMETHING PRODUCTIVE, rather than whine. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 8:34:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id D4F7914D0A; Fri, 10 Dec 1999 08:34:08 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id LAA16031; Fri, 10 Dec 1999 11:33:57 -0500 (EST) Message-ID: <19991210113357.B26029@netmonger.net> Date: Fri, 10 Dec 1999 11:33:57 -0500 From: Christopher Masto To: Greg Lehey , Daniel Eischen Cc: imp@village.org, current@FreeBSD.ORG, julian@whistle.com, msmith@FreeBSD.ORG Subject: Re: Lost PCMCIA sio (was: HEADSUP: wd driver will be retired!) References: <199912091346.IAA29671@pcnet1.pcnet.com> <19991209230116.F866@mojave.sitaranetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19991209230116.F866@mojave.sitaranetworks.com>; from Greg Lehey on Thu, Dec 09, 1999 at 11:01:16PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 09, 1999 at 11:01:16PM -0500, Greg Lehey wrote: > > pccardd[47]: driver allocation failed for Motorola(MONTANA 33.6 FAX/MODEM): Device not configured > > This closely parallels my experience. I used to get: > > Dec 5 11:57:53 mojave /kernel.old: sio1 at port 0x2e8-0x2ef irq 5 slot 1 on pccard0 > Dec 5 11:57:53 mojave /kernel.old: sio1: type 16550A > > Now I get: > > Dec 9 20:08:02 mojave pccardd[53]: driver allocation failed for CIRRUS LOGIC 56K MODEM(CL-MD56XX): Device not configured > > This happened some time towards the end of last month. I saw the message about the missing #include "card.h", and that was it (along with a broken prototype). Still freezes when I eject, but I'll try again after cvsupping Warner's latest. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 8:39: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2983415425; Fri, 10 Dec 1999 08:39:05 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA55792; Fri, 10 Dec 1999 09:39:03 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA22800; Fri, 10 Dec 1999 09:39:02 -0700 (MST) Message-Id: <199912101639.JAA22800@harmony.village.org> To: Christopher Masto Subject: Re: Lost PCMCIA sio (was: HEADSUP: wd driver will be retired!) Cc: Greg Lehey , Daniel Eischen , current@FreeBSD.ORG, julian@whistle.com, msmith@FreeBSD.ORG In-reply-to: Your message of "Fri, 10 Dec 1999 11:33:57 EST." <19991210113357.B26029@netmonger.net> References: <19991210113357.B26029@netmonger.net> <199912091346.IAA29671@pcnet1.pcnet.com> <19991209230116.F866@mojave.sitaranetworks.com> Date: Fri, 10 Dec 1999 09:39:02 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991210113357.B26029@netmonger.net> Christopher Masto writes: : I saw the message about the missing #include "card.h", and that was it : (along with a broken prototype). Still freezes when I eject, but I'll : try again after cvsupping Warner's latest. No. That wasn't it. There are still resource problems and bad memory frees in the code before I fixed it. I also just committed the kludge to sys/net/if.c to make if_detach more stable. We'll see if I catch hell for it or not. You might want to grab that as well. This is the last I plan on doing to the old pccard code for a while. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 9:52:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 80A9C15797; Fri, 10 Dec 1999 09:52:07 -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.9.3/8.9.3) with SMTP id KAA23911; Fri, 10 Dec 1999 10:52:06 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA19725; Fri, 10 Dec 1999 10:52:05 -0700 Date: Fri, 10 Dec 1999 10:52:05 -0700 Message-Id: <199912101752.KAA19725@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <32906.944654135@critter.freebsd.dk> References: <32906.944654135@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In a few days time the wd driver will be retired from FreeBSDs > i386 architecture. Given that the ATA driver just went active a few minutes ago, I think a period of shakeout time would be called for. I think that time should be longer than a few days, and should be in 4.0, and then retired in 4.1. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 9:57:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 8C14E15026; Fri, 10 Dec 1999 09:57:54 -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.9.3/8.9.3) with SMTP id KAA23972; Fri, 10 Dec 1999 10:57:45 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA19772; Fri, 10 Dec 1999 10:57:44 -0700 Date: Fri, 10 Dec 1999 10:57:44 -0700 Message-Id: <199912101757.KAA19772@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Christopher Masto , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912082052.MAA00517@mass.cdrom.com> References: <19991208150807.A16687@netmonger.net> <199912082052.MAA00517@mass.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What we need here is a commitment to these new initiatives, not a lot of > fence-sitting and clutching our knitting to our chests. If all our users were developers I would agree. But *most* of our users are not developers. > Again, I say, think of what we're trying to achieve here. Good question. What are we trying to achieve here? I thought it was to provide the best OS that is usable to the largest number of users? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10: 2: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 5B37B14D32 for ; Fri, 10 Dec 1999 10:02:03 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA06122; Fri, 10 Dec 1999 19:01:49 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: nate@mt.sri.com (Nate Williams) Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 10:52:05 MST." <199912101752.KAA19725@mt.sri.com> Date: Fri, 10 Dec 1999 19:01:49 +0100 Message-ID: <6120.944848909@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912101752.KAA19725@mt.sri.com>, Nate Williams writes: >> In a few days time the wd driver will be retired from FreeBSDs >> i386 architecture. > >Given that the ATA driver just went active a few minutes ago, I think a >period of shakeout time would be called for. I think that time should >be longer than a few days, and should be in 4.0, and then retired in >4.1. The ata driver has been available for you and other to test for a long time. 4.0-REL is still some time away, so if you are quick you can still give it a good shakeout and have any bugs you find fixed before 4.0-RELEASE. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10: 2:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 1B9EA152B1 for ; Fri, 10 Dec 1999 10:02:31 -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.3/8.9.3) with ESMTP id KAA65218 for ; Fri, 10 Dec 1999 10:01:40 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912101801.KAA65218@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 17:11:53 +0100." <5386.944842313@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 10:01:40 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The sound drivers are fine . What we need are people willing to work on the sound drivers . -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10: 4:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 115B7152B1; Fri, 10 Dec 1999 10:04:39 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA06154; Fri, 10 Dec 1999 19:04:33 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: nate@mt.sri.com (Nate Williams) Cc: Mike Smith , Christopher Masto , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 10:57:44 MST." <199912101757.KAA19772@mt.sri.com> Date: Fri, 10 Dec 1999 19:04:33 +0100 Message-ID: <6152.944849073@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912101757.KAA19772@mt.sri.com>, Nate Williams writes: >> What we need here is a commitment to these new initiatives, not a lot of >> fence-sitting and clutching our knitting to our chests. > >If all our users were developers I would agree. But *most* of our users >are not developers. -CURRENT should have very few users who are not developers in some capacity. >Good question. What are we trying to achieve here? I thought it was to >provide the best OS that is usable to the largest number of users? And this requires us to move away the old cruft so we force the people on the bleeding edge to test the new stuff. All in all, it sounds to me like a lot of people are presenting a stance which can be summarized as: "why should *I* have to be guinea-pig for the ata driver in -current make somebody else test it first." To which the answer is: If you decide to run -current you have tacitly agreed to be a guinea-pig for FreeBSD developers, so shut up and test. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10: 9:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id E49FE14E2C for ; Fri, 10 Dec 1999 10:09:50 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 7359C1CA0; Sat, 11 Dec 1999 02:09:48 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: nate@mt.sri.com (Nate Williams), current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: Message from Poul-Henning Kamp of "Fri, 10 Dec 1999 19:01:49 +0100." <6120.944848909@critter.freebsd.dk> Date: Sat, 11 Dec 1999 02:09:48 +0800 From: Peter Wemm Message-Id: <19991210180948.7359C1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message <199912101752.KAA19725@mt.sri.com>, Nate Williams writes: > >> In a few days time the wd driver will be retired from FreeBSDs > >> i386 architecture. > > > >Given that the ATA driver just went active a few minutes ago, I think a > >period of shakeout time would be called for. I think that time should > >be longer than a few days, and should be in 4.0, and then retired in > >4.1. > > The ata driver has been available for you and other to test for a long > time. 4.0-REL is still some time away, so if you are quick you can > still give it a good shakeout and have any bugs you find fixed before > 4.0-RELEASE. Also, I'd like to reiterate something again.. Not running as fast as possible is *not* a showstopper. If a device runs in generic PIO or WDMA mode instead of udma mode, it's *not* the end of the earth. People in that scenario won't be stranded. What is a killer is if a large number of people on popular hardware can't even boot, *at all*, in no, way, shape or form. Only that. The only way to find that out for sure before 4.0 is to push the issue *now*. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10:10:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id EC279157D0; Fri, 10 Dec 1999 10:10:12 -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.9.3/8.9.3) with SMTP id LAA24138; Fri, 10 Dec 1999 11:10:09 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA19928; Fri, 10 Dec 1999 11:10:08 -0700 Date: Fri, 10 Dec 1999 11:10:08 -0700 Message-Id: <199912101810.LAA19928@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: nate@mt.sri.com (Nate Williams), Mike Smith , Christopher Masto , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <6152.944849073@critter.freebsd.dk> References: <199912101757.KAA19772@mt.sri.com> <6152.944849073@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199912101757.KAA19772@mt.sri.com>, Nate Williams writes: > >> What we need here is a commitment to these new initiatives, not a lot of > >> fence-sitting and clutching our knitting to our chests. > > > >If all our users were developers I would agree. But *most* of our users > >are not developers. > > -CURRENT should have very few users who are not developers in some > capacity. Sure, but in a couple of weeks, -current will be 4.0-Release, which is not -current anymore. > >Good question. What are we trying to achieve here? I thought it was to > >provide the best OS that is usable to the largest number of users? > > And this requires us to move away the old cruft so we force the > people on the bleeding edge to test the new stuff. Force people is what I'm having problems with. *Most* people will install 4.0, and give it a good shakeout. The rest of the people are choosing to stick with the old driver for their reasons, and you're (in effect) telling them that you know better than they do what their needs are. And, you're 'forcing' them to either cod or have their systems not work as well as they used to do. From my experience, this is unacceptable if we're in the business of providing a product/service to our users. So, I ask again, what exactly are we trying to accomplish here? > All in all, it sounds to me like a lot of people are presenting > a stance which can be summarized as: > > "why should *I* have to be guinea-pig for the ata driver > in -current make somebody else test it first." Right, there are people *WILLING* to test it. > To which the answer is: If you decide to run -current you have > tacitly agreed to be a guinea-pig for FreeBSD developers, so > shut up and test. I'm with Warner. If the ATA driver went golden 2-3 months ago, then I'd say go for it. But not 2-3 days ago. You're only telling your user-base that they are less important than you are. (Although, this may be what you believe, so who am I to tell you otherwise). Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10:10:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 10607157D6 for ; Fri, 10 Dec 1999 10:10:25 -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.9.3/8.9.3) with SMTP id LAA24143; Fri, 10 Dec 1999 11:10:21 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA19935; Fri, 10 Dec 1999 11:10:21 -0700 Date: Fri, 10 Dec 1999 11:10:21 -0700 Message-Id: <199912101810.LAA19935@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: nate@mt.sri.com (Nate Williams), current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <6120.944848909@critter.freebsd.dk> References: <199912101752.KAA19725@mt.sri.com> <6120.944848909@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> In a few days time the wd driver will be retired from FreeBSDs > >> i386 architecture. > > > >Given that the ATA driver just went active a few minutes ago, I think a > >period of shakeout time would be called for. I think that time should > >be longer than a few days, and should be in 4.0, and then retired in > >4.1. > > The ata driver has been available for you and other to test for a long > time. And your point is? I'm a user, not a developer. If I wanted to be a developer, I'd have written my own device driver. I want to *USE* FreeBSD, not develop it. It's been considered 'alpha quality' until a couple of days ago. I wouldn't install beta software on any of my systems, and now you're telling me that in order to use FreeBSD, I have to become a beta-tester, since it may/may not work on my systems. > 4.0-REL is still some time away, so if you are quick you can still > give it a good shakeout and have any bugs you find fixed before > 4.0-RELEASE. So, again, who are our customers here? A bunch of developers who enjoy beta-testing other people's code, or people who want to *USE* FreeBSD? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10:10:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 427D815085 for ; Fri, 10 Dec 1999 10:10:49 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA86168; Fri, 10 Dec 1999 13:10:26 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Fri, 10 Dec 1999 13:16:16 -0500 To: Alfred Perlstein , Andre Albsmeier From: Garance A Drosihn Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test Cc: Warner Losh , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:33 AM -0800 12/10/99, Alfred Perlstein wrote: >Can someone take a look at this? > >Basically, it makes the link to the file, if it can unlink the original >it will then chown the spool file if it can't delete or read the original >then the user didn't have permission and it backs out. I'm thinking you'd what to add an lstat call after creating the hardlink. Check the new file to see if it's a symlink, and if it is, then delete the new file and go to nohardlink. Then proceed with the rest of your code (which looks fine to me, but remember I'm the guy who wrote a message explicitly for one mailing list, and then sent it to the other one...). I'm not sure on that, and haven't had time to look at the code yet. I'm just wondering about the case where a user might do a lpr -r -s somesymlink and want to be sure this does the right thing. I suspect that currently (without this patch) lpr will copy the REAL file, and then remove the symlink. I don't think we want to hard-link to the symlink, and then remove the original symlink. Remember, my mind is tired enough that I could easily be making things up here... It may be that the situation I'm wondering about is already covered by other checks in the code. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10:11:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id B39F214D28 for ; Fri, 10 Dec 1999 10:11:23 -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.9.3/8.9.3) with SMTP id LAA24155; Fri, 10 Dec 1999 11:11:19 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA19972; Fri, 10 Dec 1999 11:11:18 -0700 Date: Fri, 10 Dec 1999 11:11:18 -0700 Message-Id: <199912101811.LAA19972@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Peter Wemm Cc: Poul-Henning Kamp , nate@mt.sri.com (Nate Williams), current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991210180948.7359C1CA0@overcee.netplex.com.au> References: <6120.944848909@critter.freebsd.dk> <19991210180948.7359C1CA0@overcee.netplex.com.au> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What is a killer is if a large number of people on popular hardware can't > even boot, *at all*, in no, way, shape or form. Only that. The only way > to find that out for sure before 4.0 is to push the issue *now*. I disagree, but I'm not making the decision. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10:14:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id F2B1F14FD9; Fri, 10 Dec 1999 10:14:06 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA06237; Fri, 10 Dec 1999 19:14:01 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: nate@mt.sri.com (Nate Williams) Cc: Mike Smith , Christopher Masto , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 11:10:08 MST." <199912101810.LAA19928@mt.sri.com> Date: Fri, 10 Dec 1999 19:14:01 +0100 Message-ID: <6235.944849641@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912101810.LAA19928@mt.sri.com>, Nate Williams writes: >I'm with Warner. If the ATA driver went golden 2-3 months ago, then I'd >say go for it. But not 2-3 days ago. You're only telling your >user-base that they are less important than you are. (Although, this >may be what you believe, so who am I to tell you otherwise). The ATA driver went golden now, and to make sure nobody is distracted from testing it before 4.0-RELEASE is cut, the wd driver will be removed. It's really that simple. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10:14:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id AD719157B3 for ; Fri, 10 Dec 1999 10:14:26 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA06248; Fri, 10 Dec 1999 19:14:21 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: nate@mt.sri.com (Nate Williams) Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 11:10:21 MST." <199912101810.LAA19935@mt.sri.com> Date: Fri, 10 Dec 1999 19:14:21 +0100 Message-ID: <6246.944849661@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912101810.LAA19935@mt.sri.com>, Nate Williams writes: >> >> In a few days time the wd driver will be retired from FreeBSDs >> >> i386 architecture. >> > >> >Given that the ATA driver just went active a few minutes ago, I think a >> >period of shakeout time would be called for. I think that time should >> >be longer than a few days, and should be in 4.0, and then retired in >> >4.1. >> >> The ata driver has been available for you and other to test for a long >> time. > >And your point is? I'm a user, not a developer. If I wanted to be a >developer, I'd have written my own device driver. I want to *USE* >FreeBSD, not develop it. Then don't run -current. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10:15:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id A18C3157FD for ; Fri, 10 Dec 1999 10:15:49 -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.9.3/8.9.3) with SMTP id LAA24231; Fri, 10 Dec 1999 11:15:47 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA20053; Fri, 10 Dec 1999 11:15:46 -0700 Date: Fri, 10 Dec 1999 11:15:46 -0700 Message-Id: <199912101815.LAA20053@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: nate@mt.sri.com (Nate Williams), current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <6246.944849661@critter.freebsd.dk> References: <199912101810.LAA19935@mt.sri.com> <6246.944849661@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> >> In a few days time the wd driver will be retired from FreeBSDs > >> >> i386 architecture. > >> > > >> >Given that the ATA driver just went active a few minutes ago, I think a > >> >period of shakeout time would be called for. I think that time should > >> >be longer than a few days, and should be in 4.0, and then retired in > >> >4.1. > >> > >> The ata driver has been available for you and other to test for a long > >> time. > > > >And your point is? I'm a user, not a developer. If I wanted to be a > >developer, I'd have written my own device driver. I want to *USE* > >FreeBSD, not develop it. > > Then don't run -current. I don't, but I will be running 4.0, which won't have a WD driver. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10:20:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B6316153A0 for ; Fri, 10 Dec 1999 10:19:58 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA06334; Fri, 10 Dec 1999 19:19:43 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: nate@mt.sri.com (Nate Williams) Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 11:15:46 MST." <199912101815.LAA20053@mt.sri.com> Date: Fri, 10 Dec 1999 19:19:43 +0100 Message-ID: <6332.944849983@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912101815.LAA20053@mt.sri.com>, Nate Williams writes: >> >And your point is? I'm a user, not a developer. If I wanted to be a >> >developer, I'd have written my own device driver. I want to *USE* >> >FreeBSD, not develop it. >> >> Then don't run -current. > >I don't, but I will be running 4.0, which won't have a WD driver. Maybe we should put a special marker in -currents sendmail and reject all email to the current list if they don't originate from such a system. So, if you're not running -current, please stop whining on the -current list will you ? 4.0 will have a perfectly good diskdriver, we probably have two entire months to find and nail any remaning bugs, so what the proton do you think you're acheiving by whining here ? I'll tell you in case you can't figure out the answer to that rather simple question: You're annoying people and wasting developer time. That's what. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10:22:16 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 10F38157D3; Fri, 10 Dec 1999 10:21:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id F0D861CD621; Fri, 10 Dec 1999 10:21:01 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 10 Dec 1999 10:21:01 -0800 (PST) From: Kris Kennaway To: Christian Weisgerber Cc: freebsd-current@freebsd.org Subject: Re: OpenSSL update In-Reply-To: <82qo8d$sqj$1@bigeye.rhein-neckar.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10 Dec 1999, Christian Weisgerber wrote: > > I have it building fine, although compiling without RSA seems > > broken in openssl 0.9.4. > > Well, it works fine in the OpenBSD tree. You might want to take a > look at what's been done there. Yes, I just haven't had the time to check yet. The important thing is going to be just getting it in the tree at all and at least semi-working, it can be tweaked later. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10:22:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 0F069153D9 for ; Fri, 10 Dec 1999 10:22:04 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id KAA84629; Fri, 10 Dec 1999 10:21:48 -0800 (PST) From: Archie Cobbs Message-Id: <199912101821.KAA84629@bubba.whistle.com> Subject: Re: Modules and sysctl tree In-Reply-To: from Andrzej Bialecki at "Dec 10, 1999 09:48:12 am" To: abial@webgiro.com (Andrzej Bialecki) Date: Fri, 10 Dec 1999 10:21:48 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki writes: > > KLD's are just a linking mechanism, and shouldn't have any more > > significance than that from a usability perspective. > > Hah. If it were so simple... > > Let's take the example of a module foo, which provides unique features of > bar and baz. They are unrelated to any already existing category. Where > they should be hooked up? kernel? machdep? Then these categories will > become a messy, amorphic trashcans. Also, it will be difficult to see > which sysctls will disappear when the module is unloaded. Well, IMHO the problem of how to organize the sysctl tree is orthogonal (ie, completely independent) from how the kernel is linked. I guess if you imagine a world where hundreds of third party vendors are distributing KLD's that do all kinds of crazy things, then yes perhaps we need a "miscellaneous" category eg, misc.foo.bar .. But right now it looks like 99% of KLD's are part of FreeBSD itself. So there's no reason we can't put them in their correct sysctl location right from the beginning. > More or less, my question is: how the sysctl tree will look like when > _most_ of the kernel will be in modules? Just like it does now. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10:22:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 908C0157E9; Fri, 10 Dec 1999 10:22:08 -0800 (PST) (envelope-from netchild@Leidinger.net) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id TAA11248155; Fri, 10 Dec 1999 19:22:06 +0100 (CET) Received: from Magelan.Leidinger.net (maxtnt-145.telip.uni-sb.de [134.96.71.16]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id TAA15437; Fri, 10 Dec 1999 19:22:14 +0100 (CET) Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id RAA01801; Fri, 10 Dec 1999 17:41:02 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <199912101641.RAA01801@Magelan.Leidinger.net> Date: Fri, 10 Dec 1999 17:41:01 +0100 (CET) From: Alexander Leidinger Subject: Re: HEADSUP: wd driver will be retired! To: msmith@freebsd.org Cc: current@freebsd.org In-Reply-To: <199912092157.NAA01406@mass.cdrom.com> 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 On 9 Dec, Mike Smith wrote: >> There also exist cases where the chipset is supported but a particular >> functionality isn´t supported yet (in my case it´s the possibility to >> access MS-DOS formated ZIP-disks, harddisk access works well, and I´m >> not the only one with this problem (not counting the people which have >> not tried to use the ata driver but need to access MS-DOS-ZIPs too)). > > I'm completely at a loss as to how the ata driver could be responsible > for your inability to read these disks. I don't have a copy of your > original problem report to hand, but since I have all the hardware here > I'd appreciate it if you could be a little more explicit about your > problem. > > The ata driver just moves bytes; it doesn't give a damn what they are. Try to mount a MS-DOS formatted ZIP-disk (or to access it with mtools). With wfd I´m able to access it, with afd I can´t access it. - Yes, I´m used the right /dev entries and remade them with the newest MAKEDEV, everytime I tested it. - Yes, I´m used the right fstab/mtools.conf entries ({,r}{a,w}fd0s4). If you need more info (dmesg of boot -v with ata and/or wd driver, {g,b}zipped image of an empty, unaccessible ZIP-disk, ...) just ask. Bye, Alexander. -- The best things in life are free, but the expensive ones are still worth a look. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 10:24:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id EE76415235 for ; Fri, 10 Dec 1999 10:24:17 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id TAA14662 for ; Fri, 10 Dec 1999 19:24:06 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id TAA29768 for ; Fri, 10 Dec 1999 19:24:05 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id TAA27224 for ; Fri, 10 Dec 1999 19:24:05 +0100 (CET) Date: Fri, 10 Dec 1999 19:24:03 +0100 From: Andre Albsmeier To: Garance A Drosihn Cc: Alfred Perlstein , Andre Albsmeier , Warner Losh , current@FreeBSD.ORG Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test Message-ID: <19991210192403.A19799@internal> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from drosih@rpi.edu on Fri, Dec 10, 1999 at 01:16:16PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10-Dec-1999 at 13:16:16 -0500, Garance A Drosihn wrote: > At 2:33 AM -0800 12/10/99, Alfred Perlstein wrote: > >Can someone take a look at this? > > > >Basically, it makes the link to the file, if it can unlink the original > >it will then chown the spool file if it can't delete or read the original > >then the user didn't have permission and it backs out. > > I'm thinking you'd what to add an lstat call after creating the > hardlink. Check the new file to see if it's a symlink, and if it Can a symlink be created by link() ? If I look at link(2), it seems that it will create only hardlinks... But, I am new to this and maybe talking nonsense only :-) > is, then delete the new file and go to nohardlink. Then proceed > with the rest of your code (which looks fine to me, but remember > I'm the guy who wrote a message explicitly for one mailing list, > and then sent it to the other one...). > > I'm not sure on that, and haven't had time to look at the code > yet. I'm just wondering about the case where a user might do a > lpr -r -s somesymlink > and want to be sure this does the right thing. I suspect that > currently (without this patch) lpr will copy the REAL file, and From my experience, lpr -s -r does the same as lpr -s : Create a symlink in the spooldir which points to the file to be printed. After printing, the symlink is being removed and the file won't be touched. IIRC, this is due to security reasons when doing remote printing. No files are removed that start with a /. The unlink command is ignored by printjob.c. But, again I maybe false... > then remove the symlink. I don't think we want to hard-link to > the symlink, and then remove the original symlink. > > Remember, my mind is tired enough that I could easily be making > things up here... It may be that the situation I'm wondering > about is already covered by other checks in the code. I have just looked at Alfred's patch and it seems nice to me but that doesn't mean a lot :-) -Andre > > > --- > Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu > Senior Systems Programmer or drosih@rpi.edu > Rensselaer Polytechnic Institute -- "In a world without walls and fences, who needs windows and gates?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 11:23:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (Postfix) with ESMTP id AF8411599C for ; Fri, 10 Dec 1999 11:12:33 -0800 (PST) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id LAA29288; Fri, 10 Dec 1999 11:12:29 -0800 (PST) (envelope-from sef) Date: Fri, 10 Dec 1999 11:12:29 -0800 (PST) From: Sean Eric Fagan Message-Id: <199912101912.LAA29288@kithrup.com> To: current@freebsd.org Reply-To: current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <6332.944849983.kithrup.freebsd.current@critter.freebsd.dk> References: Your message of "Fri, 10 Dec 1999 11:15:46 MST." <199912101815.LAA20053@mt.sri.com> Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <6332.944849983.kithrup.freebsd.current@critter.freebsd.dk> PHK writes: > >Maybe we should put a special marker in -currents sendmail and >reject all email to the current list if they don't originate >from such a system. > >I'll tell you in case you can't figure out the answer to that rather >simple question: You're annoying people and wasting developer >time. That's what. And further evidence that FreeBSD is turning into PHKBSD: what PHK wants, despite objections from other people, PHK does, and damn any consequences, whether they be social, political, or technical. Several people have raised valid objections to PHK's actions (again -- at least he bothered warning people this time), and have proposed an alternate solution, which PHK has ignored (again -- at least this time he bothered saying so). And, once again, PHK's response is: shut up and go away. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 11:23:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from jester.ti.com (jester.ti.com [192.94.94.1]) by hub.freebsd.org (Postfix) with ESMTP id 60A6E15A86 for ; Fri, 10 Dec 1999 11:14:43 -0800 (PST) (envelope-from ntakpe@ffab.tide.ti.com) Received: from dlep8.itg.ti.com ([157.170.134.88]) by jester.ti.com (8.9.3/8.9.3) with ESMTP id NAA09018 for ; Fri, 10 Dec 1999 13:14:09 -0600 (CST) Received: from dlep8.itg.ti.com (localhost [127.0.0.1]) by dlep8.itg.ti.com (8.9.3/8.9.3) with ESMTP id NAA16383 for ; Fri, 10 Dec 1999 13:14:16 -0600 (CST) Received: from wrks2host.ffab.tide.ti.com (wrks2host.ffab.tide.ti.com [137.167.200.37]) by dlep8.itg.ti.com (8.9.3/8.9.3) with ESMTP id NAA15781 for ; Fri, 10 Dec 1999 13:13:45 -0600 (CST) Received: from ishtar.ffab.tide.ti.com (ishtar.ffab.tide.ti.com [137.167.200.61]) by wrks2host.ffab.tide.ti.com (8.8.8+Sun/8.8.8) with ESMTP id UAA13564 for ; Fri, 10 Dec 1999 20:14:01 +0100 (MET) Received: from ishtar.ffab.tide.ti.com (IDENT:ntakpe@localhost.ffab.tide.ti.com [127.0.0.1]) by ishtar.ffab.tide.ti.com (8.9.3/8.9.3) with ESMTP id UAA02864 for ; Fri, 10 Dec 1999 20:14:00 +0100 Message-Id: <199912101914.UAA02864@ishtar.ffab.tide.ti.com> X-Mailer: exmh version 2.1.1 (devel) To: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: Message from Poul-Henning Kamp of "Fri, 10 Dec 1999 19:19:43 +0100." <6332.944849983@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 20:14:00 +0100 From: "Jean Louis Ntakpe" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm new to this list. I was running the new ATA driver on an IBM UDMA/66 HighPoint HPT366 IDE controller until last week (sometimes after CTM src-cur-4110). I've recompiled my system and my kernel and the system was not able to find the partition on my UDM66-Disk, was not able to disklabel, after a fresh fdisk. I've connected the disk back to the UDM33 controller and it works fine. Now I get the message twice a day: ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done I've applied the patches until 4133 and will try to reconnect the disk to the UDMA66 controller. Am I missing something about UDMA33/UDMA66 or specifically about the HighPoint controller ? regards, -- Jean Louis Ntakpe Texas Instruments - Freising Wafer Fab Automation Group Haggerty Str. 1 D-85350 Freising, Germany Phone +49 8161 80-3816 Fax +49 8161 80-3762 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 11:51:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 100E1157FA for ; Fri, 10 Dec 1999 11:39:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA60264; Fri, 10 Dec 1999 11:39:27 -0800 (PST) (envelope-from dillon) Date: Fri, 10 Dec 1999 11:39:27 -0800 (PST) From: Matthew Dillon Message-Id: <199912101939.LAA60264@apollo.backplane.com> To: Dan Nelson Cc: freebsd-current@freebsd.org Subject: Re: NFS client zeroing out blocks on write? References: <19991203112518.A43843@dan.emsphone.com> <199912042051.MAA56920@apollo.backplane.com> <19991205024034.A77822@dan.emsphone.com> <199912061912.LAA71576@apollo.backplane.com> <19991209155512.A5898@dan.emsphone.com> <199912092233.OAA53484@apollo.backplane.com> <19991210113631.A982@dan.emsphone.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I've managed to reproduce the NFS zeroing problem that Dan reported. bfileaa bfileab bfileac bfileaa bfileab 915136512-915144191(7680) bfileac It sure doesn't happen very often (each bfile is 1G), but hopefully often enough that I can track down what is going on. I'm Ccing -current on this to give everyone an update - plus I think a few other certified NFS loons might be interested in attempting to help locate the problem too. At the moment I am focusing my attention on the nfs_write() code. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 11:54: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 50C62157DD for ; Fri, 10 Dec 1999 11:51:07 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id MAA28120; Fri, 10 Dec 1999 12:20:55 -0800 (PST) Date: Fri, 10 Dec 1999 12:20:55 -0800 (PST) From: Alfred Perlstein To: Garance A Drosihn Cc: Andre Albsmeier , Warner Losh , current@FreeBSD.ORG Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Dec 1999, Garance A Drosihn wrote: > At 2:33 AM -0800 12/10/99, Alfred Perlstein wrote: > >Can someone take a look at this? > > > >Basically, it makes the link to the file, if it can unlink the original > >it will then chown the spool file if it can't delete or read the original > >then the user didn't have permission and it backs out. > > I'm thinking you'd what to add an lstat call after creating the > hardlink. Check the new file to see if it's a symlink, and if it > is, then delete the new file and go to nohardlink. Then proceed > with the rest of your code (which looks fine to me, but remember > I'm the guy who wrote a message explicitly for one mailing list, > and then sent it to the other one...). > > I'm not sure on that, and haven't had time to look at the code > yet. I'm just wondering about the case where a user might do a > lpr -r -s somesymlink > and want to be sure this does the right thing. I suspect that > currently (without this patch) lpr will copy the REAL file, and > then remove the symlink. I don't think we want to hard-link to > the symlink, and then remove the original symlink. > > Remember, my mind is tired enough that I could easily be making > things up here... It may be that the situation I'm wondering > about is already covered by other checks in the code. ugh, good call. i'll look into it. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 12:16: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 956DD15A2D for ; Fri, 10 Dec 1999 11:56:37 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id OAA06165 for ; Fri, 10 Dec 1999 14:56:26 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Fri, 10 Dec 1999 14:56:25 -0500 (EST) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: SB ViBRA16X Message-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 checked the mailing list archives and havn't been able to find anything on this so here goes: I have a SoundBlaster ViBRA16X, and a Diamond SupraExpress 56i modem. The SoundBlaster worked fine with PnP OS turned off in Bios, as did the modem. They were detected as non PnP devices by FreeBSD. With the recent changes (controller pnp0 is no longer an option) Neither of these devices works correctly. The Soundcard is detected ok, but it won't play any sound through /dev/dsp, the modem won't even attach to sio0 anymore. Here is a dmesg output, if any other information is needed, I would be glad to provide it: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Dec 7 18:31:44 EST 1999 culverk@culverk.student.umd.edu:/usr/src/sys/compile/MYKERNEL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134152192 (131008K bytes) avail memory = 127414272 (124428K bytes) Preloaded elf kernel "kernel" at 0xc029c000. Preloaded elf module "bktr.ko" at 0xc029c09c. Pentium Pro MTRR support enabled apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 11 chip1: at device 7.3 on pci0 pci0: unknown card (vendor=0x121a, dev=0x0002) at 13.0 pci0: unknown card (vendor=0x121a, dev=0x0002) at 15.0 bktr0: irq 5 at device 17.0 on pci0 bktr0: Hauppauge Model 61291 D110 Warning - Unknown Hauppauge Tuner 0xa Hauppauge WinCast/TV, Philips NTSC tuner. pci0: unknown card (vendor=0x109e, dev=0x0878) at 17.1 irq 5 de0: irq 10 at device 19.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:1f:21:02 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 vpo0: on ppbus 0 vpo0: EPP 1.9 mode unknown0: at port 0x2f8-0x2ff irq 3 on isa0 sbc0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 9 drq 0,1 on isa0 pcm0: on sbc0 unknown1: at port 0x201 on isa0 ad0: ATA-4 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: ATA-3 disk at ata0 as slave ad1: 4120MB (8438850 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad2: ATA-3 disk at ata1 as master ad2: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata1 as slave , 128KB buffer, PIO acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data/audio disc loaded, unlocked da0 at vpo0 bus 0 target 6 lun 0 da0: Removable Direct Access SCSI-2 device da0: Attempt to query device size failed: NOT READY, Medium not present Mounting root from ufs:/dev/wd1s1a de0: enabling 10baseT port To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 12:39:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4119215218 for ; Fri, 10 Dec 1999 12:32:12 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA10133; Fri, 10 Dec 1999 21:31:57 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912102031.VAA10133@freebsd.dk> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912101914.UAA02864@ishtar.ffab.tide.ti.com> from Jean Louis Ntakpe at "Dec 10, 1999 08:14:00 pm" To: ntakpe@ffab.tide.ti.com (Jean Louis Ntakpe) Date: Fri, 10 Dec 1999 21:31:57 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Jean Louis Ntakpe wrote: > Hi, > > I'm new to this list. > I was running the new ATA driver on an IBM UDMA/66 > HighPoint HPT366 IDE controller until last week (sometimes after > CTM src-cur-4110). I've recompiled my system and my kernel and > the system was not able to find the partition on my UDM66-Disk, > was not able to disklabel, after a fresh fdisk. > I've connected the disk back to the UDM33 controller and it works > fine. Now I get the message twice a day: > > ata0-master: ad_timeout: lost disk contact - resetting > ata0: resetting devices .. done > > I've applied the patches until 4133 and will try to reconnect > the disk to the UDMA66 controller. > > Am I missing something about UDMA33/UDMA66 or specifically about > the HighPoint controller ? Hmm, I have one in my development machine, so it takes a fair bit of beating, I haven't seen any of these problems. Could you mail me a dmesg, preferably from a verbose boot. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 12:57: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B087015417 for ; Fri, 10 Dec 1999 12:56:47 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA56785; Fri, 10 Dec 1999 13:56:45 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA24999; Fri, 10 Dec 1999 13:56:44 -0700 (MST) Message-Id: <199912102056.NAA24999@harmony.village.org> To: Poul-Henning Kamp Subject: Re: HEADSUP: wd driver will be retired! Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 10 Dec 1999 17:15:29 +0100." <5461.944842529@critter.freebsd.dk> References: <5461.944842529@critter.freebsd.dk> Date: Fri, 10 Dec 1999 13:56:44 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5461.944842529@critter.freebsd.dk> Poul-Henning Kamp writes: : Please, help fix PCCARD if you know of a problem. Yes. I think I've been the only one fixing bugs lately in PCCARD. :-< Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 13:16: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id ED0C614DA1 for ; Fri, 10 Dec 1999 13:15:40 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA56860; Fri, 10 Dec 1999 14:15:34 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA25113; Fri, 10 Dec 1999 14:15:33 -0700 (MST) Message-Id: <199912102115.OAA25113@harmony.village.org> To: Poul-Henning Kamp Subject: Re: HEADSUP: wd driver will be retired! Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 10 Dec 1999 19:14:01 +0100." <6235.944849641@critter.freebsd.dk> References: <6235.944849641@critter.freebsd.dk> Date: Fri, 10 Dec 1999 14:15:33 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <6235.944849641@critter.freebsd.dk> Poul-Henning Kamp writes: : In message <199912101810.LAA19928@mt.sri.com>, Nate Williams writes: : : >I'm with Warner. If the ATA driver went golden 2-3 months ago, then I'd : >say go for it. But not 2-3 days ago. You're only telling your : >user-base that they are less important than you are. (Although, this : >may be what you believe, so who am I to tell you otherwise). : : The ATA driver went golden now, and to make sure nobody is distracted : from testing it before 4.0-RELEASE is cut, the wd driver will be : removed. : : It's really that simple. Isn't that unprecidented? In the past there has always been a period of shakeout between the two events longer than a couple of days. That's the part that you are ignoring. It isn't how we've done things before. You should make it clear that this is a departure from the past, and you should also make sure that the pc98 folks aren't left holding the bag. We've been telling people for a long time that the wd driver would remain around even after ata went golden to support the ESDI systems still in service. That sounds like it is changing now. It just feels like it is being rushed too much. My objections would go away if you said it is going to die in the week between xmas and new years. remove it from files today, to make sure that only the really clueful can get to it, but don't do a cvs remove until after the holidays... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 13:24: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id CC7A9152B2; Fri, 10 Dec 1999 13:23:59 -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.9.3/8.9.3) with SMTP id OAA26406; Fri, 10 Dec 1999 14:23:23 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA21691; Fri, 10 Dec 1999 14:23:21 -0700 Date: Fri, 10 Dec 1999 14:23:21 -0700 Message-Id: <199912102123.OAA21691@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Peter Wemm Cc: Jeroen Ruigrok/Asmodai , Greg Lehey , Brad Knowles , Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991210160247.DF62D1CA0@overcee.netplex.com.au> References: <19991209205302.C65692@daemon.ninth-circle.org> <19991210160247.DF62D1CA0@overcee.netplex.com.au> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If half as much energy was spent adding the missing bits of functionality > to the new systems as people have been spending complaining it then we'd be > there ages ago. Not true. It doesn't take a disk expert to complain about a policy, but it takes one to fix bugs/add features to the existing driver. :) :) :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 13:33: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2ADFD14E7F for ; Fri, 10 Dec 1999 13:33:02 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA07284; Fri, 10 Dec 1999 22:32:50 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 14:15:33 MST." <199912102115.OAA25113@harmony.village.org> Date: Fri, 10 Dec 1999 22:32:50 +0100 Message-ID: <7282.944861570@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912102115.OAA25113@harmony.village.org>, Warner Losh writes: >: The ATA driver went golden now, and to make sure nobody is distracted >: from testing it before 4.0-RELEASE is cut, the wd driver will be >: removed. >: >: It's really that simple. > >Isn't that unprecidented? In the past there has always been a period >of shakeout between the two events longer than a couple of days. Well, the only precedent we have is CAM/SCSI, and it was done the same way. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 13:36:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 6216115162 for ; Fri, 10 Dec 1999 13:36:38 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA170584; Fri, 10 Dec 1999 16:36:29 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <19991210192403.A19799@internal> References: <19991210192403.A19799@internal> Date: Fri, 10 Dec 1999 16:42:19 -0500 To: Andre Albsmeier From: Garance A Drosihn Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test Cc: Alfred Perlstein , Andre Albsmeier , Warner Losh , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:24 PM +0100 12/10/99, Andre Albsmeier wrote: >On Fri, 10-Dec-1999 at 13:16:16 -0500, Garance A Drosihn wrote: > > I'm thinking you'd what to add an lstat call after creating the > > hardlink. Check the new file to see if it's a symlink, and if it > >Can a symlink be created by link() ? If I look at link(2), it seems >that it will create only hardlinks... But, I am new to this and >maybe talking nonsense only :-) I'm thinking about what happens if the link() is given a source file which already is a symlink. Eg: touch dumbfile ln -s dumbfile dumbfile.sym ln dumbfile.sym dumbfile.hard ls -li dumbfile* Hmm. In testing the above, it is an issue under aix, although not in the way I was expecting. The hardlink succeeds, and you end up with dumbfile.hard as a hard link to the 'dumbfile'. So, the given patch (under aix) would make a hardlink OK, but I'll have to do some testing to determine how that effects the rest of the checks in the most recent suggested patch. It looks like freebsd won't let me create the hardlink to the symlink, so this problem wouldn't come up under freebsd. However, I do take freebsd's lpr/lpd and compile it for use on aix, irix, and solaris here at RPI, so I do want to look into this in detail on all four platforms. > > I'm not sure on that, and haven't had time to look at the code > > yet. I'm just wondering about the case where a user might do a > > lpr -r -s somesymlink > > and want to be sure this does the right thing. I suspect that > > currently (without this patch) lpr will copy the REAL file, and > >From my experience, lpr -s -r does the same as lpr -s : Create >a symlink in the spooldir which points to the file to be printed. Sorry. Brain-error on my part. I meant just lpr -r somesymlink but I was thinking "symlink" so I added the -s in there by mistake. Clearly I need more sleep before tackling this topic again... --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 13:46: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 26ED415190; Fri, 10 Dec 1999 13:46:01 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA27469; Fri, 10 Dec 1999 22:44:36 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912102144.WAA27469@freebsd.dk> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912102123.OAA21691@mt.sri.com> from Nate Williams at "Dec 10, 1999 02:23:21 pm" To: nate@mt.sri.com (Nate Williams) Date: Fri, 10 Dec 1999 22:44:36 +0100 (CET) Cc: peter@netplex.com.au (Peter Wemm), asmodai@wxs.nl (Jeroen Ruigrok/Asmodai), grog@lemis.com (Greg Lehey), blk@skynet.be (Brad Knowles), msmith@FreeBSD.ORG (Mike Smith), julian@whistle.com (Julian Elischer), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Nate Williams wrote: > > If half as much energy was spent adding the missing bits of functionality > > to the new systems as people have been spending complaining it then we'd be > > there ages ago. > > Not true. It doesn't take a disk expert to complain about a policy, but > it takes one to fix bugs/add features to the existing driver. :) :) :) Yeah, and some of them is spending valueable time going thru all this garbage in their mailbox instead of doing something usefull. Excuse me for not taking part in this, but I _really_ think I can use my time for better things... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 13:47: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 27F3E14D62 for ; Fri, 10 Dec 1999 13:47:02 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA52602; Fri, 10 Dec 1999 14:46:36 -0700 (MST) (envelope-from ken) Message-Id: <199912102146.OAA52602@panzer.kdm.org> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <7282.944861570@critter.freebsd.dk> from Poul-Henning Kamp at "Dec 10, 1999 10:32:50 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Fri, 10 Dec 1999 14:46:36 -0700 (MST) Cc: imp@village.org (Warner Losh), current@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote... > In message <199912102115.OAA25113@harmony.village.org>, Warner Losh writes: > > >: The ATA driver went golden now, and to make sure nobody is distracted > >: from testing it before 4.0-RELEASE is cut, the wd driver will be > >: removed. > >: > >: It's really that simple. > > > >Isn't that unprecidented? In the past there has always been a period > >of shakeout between the two events longer than a couple of days. > > Well, the only precedent we have is CAM/SCSI, and it was done the > same way. I don't think you should look at the CAM integration as a precendent for the current ATA situation. We had a switchover from the old SCSI layer to CAM instead of a transition because it would have been much more difficult to have both SCSI layers in the tree at the same time. In the case of the ATA code, both it and the wd driver have existed in the tree for quite a while, apparantly without problems. So I don't think there is a real parallel there. IMO, if the ATA driver supports all the chipsets that the wd driver does, then it's probably okay to throw the switch to get people testing the new driver. If it doesn't, though, I think we should wait on throwing the switch until it supports them all. Unlike the CAM case, there isn't a compelling reason to throw the switch before the new code supports every chipset. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 13:49:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 286BA15162 for ; Fri, 10 Dec 1999 13:49:16 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.25.55] (dialup567.brussels2.skynet.be [195.238.25.55]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id WAA16951; Fri, 10 Dec 1999 22:48:54 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <7282.944861570@critter.freebsd.dk> References: <7282.944861570@critter.freebsd.dk> Date: Fri, 10 Dec 1999 22:47:22 +0100 To: Poul-Henning Kamp , Warner Losh From: Brad Knowles Subject: Re: HEADSUP: wd driver will be retired! Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:32 PM +0100 1999/12/10, Poul-Henning Kamp wrote: > Well, the only precedent we have is CAM/SCSI, and it was done the > same way. Given some of the things I've heard about the CAM/SCSI debacle, I'm not sure that this is a good example to be trotting out right now. Personally, I don't think that this is an experience we'd want to be repeating -- especially not with something related to disk devices. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 14: 6:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 3996F15175 for ; Fri, 10 Dec 1999 14:06:23 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA52840; Fri, 10 Dec 1999 15:05:53 -0700 (MST) (envelope-from ken) Message-Id: <199912102205.PAA52840@panzer.kdm.org> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: from Brad Knowles at "Dec 10, 1999 10:47:22 pm" To: blk@skynet.be (Brad Knowles) Date: Fri, 10 Dec 1999 15:05:53 -0700 (MST) Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), imp@village.org (Warner Losh), current@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote... > At 10:32 PM +0100 1999/12/10, Poul-Henning Kamp wrote: > > > Well, the only precedent we have is CAM/SCSI, and it was done the > > same way. > > Given some of the things I've heard about the CAM/SCSI debacle, > I'm not sure that this is a good example to be trotting out right > now. Personally, I don't think that this is an experience we'd want > to be repeating -- especially not with something related to disk > devices. I agree that the CAM integration shouldn't be used as a precedent here. I don't agree with your characterization of it as a "debacle", though. On the whole, we gained a whole lot and lost very little. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 14:13:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 7EB971542A for ; Fri, 10 Dec 1999 14:12:59 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id OAA38475; Fri, 10 Dec 1999 14:12:52 -0800 (PST) Date: Fri, 10 Dec 1999 14:12:51 -0800 (PST) From: Julian Elischer To: Poul-Henning Kamp Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <7282.944861570@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think there has been enough objections to the idea of just removing wd.c for it to stay for a few months. It doesn't hurt to keep it. Especially if it's not on by default. I think this argument can go away for a while. On Fri, 10 Dec 1999, Poul-Henning Kamp wrote: > In message <199912102115.OAA25113@harmony.village.org>, Warner Losh writes: > > >: The ATA driver went golden now, and to make sure nobody is distracted > >: from testing it before 4.0-RELEASE is cut, the wd driver will be > >: removed. > >: > >: It's really that simple. > > > >Isn't that unprecidented? In the past there has always been a period > >of shakeout between the two events longer than a couple of days. > > Well, the only precedent we have is CAM/SCSI, and it was done the > same way. > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 14:15:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 5F5521544C for ; Fri, 10 Dec 1999 14:15:53 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id RAA24287 for current@FreeBSD.ORG; Fri, 10 Dec 1999 17:15:52 -0500 (EST) (envelope-from luoqi) Date: Fri, 10 Dec 1999 17:15:52 -0500 (EST) From: Luoqi Chen Message-Id: <199912102215.RAA24287@lor.watermarkgroup.com> To: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This discussion is not going anywhere. Why can't everyone calm down and find a comprise? Here's my proposal: 1. leave the the code and config option in the source tree for now 2. remove all traces of wd in documentation/GENERIC/LINT/MAKEDEV that is, anyone who wants to use the wd driver still can, but it is officially unsupported. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 14:22:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 02F6A152A9 for ; Fri, 10 Dec 1999 14:22:32 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id XAA07596; Fri, 10 Dec 1999 23:22:24 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 17:15:52 EST." <199912102215.RAA24287@lor.watermarkgroup.com> Date: Fri, 10 Dec 1999 23:22:24 +0100 Message-ID: <7594.944864544@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912102215.RAA24287@lor.watermarkgroup.com>, Luoqi Chen writes: >This discussion is not going anywhere. Why can't everyone calm down and >find a comprise? Here's my proposal: > >1. leave the the code and config option in the source tree for now >2. remove all traces of wd in documentation/GENERIC/LINT/MAKEDEV > >that is, anyone who wants to use the wd driver still can, but it is officially >unsupported. This fails the most important criteria for the transistion to ATA: it doesn't break existing kernel configs. Listen guys, this is a tempest in a tea-cup, we are not loosing any functionality here, we are gaining functionality. The wd driver doesn't have anything to recommend it on the i386 platform and we need to switch to ATA. This is *CURRENT* remember ? We want this transistion done and tested before current becomes 4.0-RELEASE. The time is NOW! If we don't force people over to the ata driver it will not get tested as much as it needs to. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 14:23:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from minubian.houabg.com (minubian.houabg.com [206.109.247.11]) by hub.freebsd.org (Postfix) with ESMTP id D584515428 for ; Fri, 10 Dec 1999 14:23:22 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from houcbs2.houabg.com (HOUABG.COM [206.109.247.20]) by minubian.houabg.com (8.8.8/8.8.8) with ESMTP id QAA18375 for ; Fri, 10 Dec 1999 16:59:01 -0600 (CST) (envelope-from dchapman@houabg.com) Received: from 216-118-21-147.pdq.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id Y1KZY2F9; Fri, 10 Dec 1999 16:26:05 -0600 Message-ID: <058101bf435c$880144e0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: References: <199912102215.RAA24287@lor.watermarkgroup.com> Subject: Re: HEADSUP: wd driver will be retired! Date: Fri, 10 Dec 1999 16:18:47 -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 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't think anyone wants to stay with the old drivers with the exception of when the new ones don't work on their hardware, I think they should just stay around for a little longer unless the drivers "conflict" with each other in the source tree. ----- Original Message ----- From: "Luoqi Chen" To: Sent: Friday, December 10, 1999 4:15 PM Subject: Re: HEADSUP: wd driver will be retired! > This discussion is not going anywhere. Why can't everyone calm down and > find a comprise? Here's my proposal: > > 1. leave the the code and config option in the source tree for now > 2. remove all traces of wd in documentation/GENERIC/LINT/MAKEDEV > > that is, anyone who wants to use the wd driver still can, but it is officially > unsupported. > > -lq > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 14:24:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id D451214E09 for ; Fri, 10 Dec 1999 14:24:20 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.25.55] (dialup567.brussels2.skynet.be [195.238.25.55]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id XAA26458; Fri, 10 Dec 1999 23:23:54 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912102205.PAA52840@panzer.kdm.org> References: <199912102205.PAA52840@panzer.kdm.org> Date: Fri, 10 Dec 1999 23:22:57 +0100 To: "Kenneth D. Merry" From: Brad Knowles Subject: Re: HEADSUP: wd driver will be retired! Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), imp@village.org (Warner Losh), current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:05 PM -0700 1999/12/10, Kenneth D. Merry wrote: > I agree that the CAM integration shouldn't be used as a precedent here. I > don't agree with your characterization of it as a "debacle", though. > > On the whole, we gained a whole lot and lost very little. Long-term, yes I believe we gained a lot. Short-term, what I recall having heard from some of the people who lived through it, well let's just say it was really ugly and nasty for a certain period of time. If possible, I'd like to see us avoid the same kind of problems with wd vs. ata, if we can. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 14:29:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from nowcool.dhs.org (fx3-3-071.mgfairfax.rr.com [24.28.202.71]) by hub.freebsd.org (Postfix) with ESMTP id B68B015462 for ; Fri, 10 Dec 1999 14:29:44 -0800 (PST) (envelope-from freebsd@nowcool.dhs.org) Received: from localhost (freebsd@localhost) by nowcool.dhs.org (8.9.3/8.9.3) with ESMTP id RAA01712 for ; Fri, 10 Dec 1999 17:29:38 -0500 (EST) (envelope-from freebsd@nowcool.dhs.org) Date: Fri, 10 Dec 1999 17:29:38 -0500 (EST) From: Byung Yang To: current@freebsd.org Subject: snd0 & pcm0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's the status on the newpcm? is it still broken? When I use newpcm, these problems occur: 1. when I use waveplay to play a file, even after it completely plays the file (and return to the shell prompt), I still hear about 1-2 seconds of sound playing repeatedly. 2. when I use xmms or mpg123, it plays the first file ok, and when I press the stop button and play another, sound applications freeze. 3. when using mtv, sound doesn't work and freezes all sound apps. When using snd0, I have access to all sound apps but when I play mp3 files using any mp3 players, I hear the first 2-3 min fine and then I start hearing statics (nasty statics that don't go away until i press "pause" and play "start" again.) Any reference pages for the answers to these problems? or anybody knows this? FreeBSD nowcool.dhs.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Dec 2 00:35:27 EST 1999 byung@nowcool.dhs.org:/usr/src/sys/compile/NOWCOOL i386 that's when I supped and my snd configurations look like: # for snd0, I use following four lines. controller snd0 device css0 at isa? port 0x534 irq 5 drq 1 flags 0x08 device opl0 at isa? port 0x388 device mpu0 at isa? port 0x330 irq 6 drq 0 ------------ # for newpcm, I use following lines options PNPBIOS controller pnp0 # PnP support for ISA device pcm0 any clues would be appreciated thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 15:20:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp.uky.edu (smtp.uky.edu [128.163.2.17]) by hub.freebsd.org (Postfix) with ESMTP id 6239B153D4 for ; Fri, 10 Dec 1999 15:20:37 -0800 (PST) (envelope-from gchil0@pop.uky.edu) Received: from pop.uky.edu (pop.uky.edu [128.163.2.16]) by smtp.uky.edu (8.9.3/8.9.3) with ESMTP id SAA01130; Fri, 10 Dec 1999 18:20:31 -0500 (EST) Received: from e2e1.pa.uky.edu (e2e1.pa.uky.edu [128.163.161.125]) by pop.uky.edu (8.9.3/8.9.3) with ESMTP id SAA21798; Fri, 10 Dec 1999 18:20:30 -0500 (EST) Message-Id: <4.2.0.58.19991210180808.00945190@pop.uky.edu> X-Sender: gchil0@pop.uky.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 10 Dec 1999 18:18:55 -0500 To: Poul-Henning Kamp From: Greg Childers Subject: Re: HEADSUP: wd driver will be retired! Cc: current@FreeBSD.ORG In-Reply-To: <7594.944864544@critter.freebsd.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:22 PM 12/10/99 +0100, Poul-Henning Kamp wrote: > >This discussion is not going anywhere. Why can't everyone calm down and > >find a comprise? Here's my proposal: > > > >1. leave the the code and config option in the source tree for now > >2. remove all traces of wd in documentation/GENERIC/LINT/MAKEDEV > > >Listen guys, this is a tempest in a tea-cup, we are not loosing any >functionality here, we are gaining functionality. Except that ATA currently does not work on my system. So I assume I'm not the only one. I am not a developer but I am running current on a test system to see what's in line for stable. I do not mind when things break for a while. But, since others did not seem to have this problem, I sent an email to the list. The link is below. So far, I've heard no word, and things are still broken. For this reason, I'd like wd to stay in the tree until ATA is fixed. Otherwise, my machine is unusable. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=761360+0+current/freebsd-current Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 15:43:16 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 360A91536D; Fri, 10 Dec 1999 15:42:44 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 1A9051CD733; Fri, 10 Dec 1999 15:42:44 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 10 Dec 1999 15:42:44 -0800 (PST) From: Kris Kennaway To: Poul-Henning Kamp Cc: Luoqi Chen , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <7594.944864544@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Dec 1999, Poul-Henning Kamp wrote: > Listen guys, this is a tempest in a tea-cup, we are not loosing any > functionality here, we are gaining functionality. Poul-Henning, what I'm seeing here is a LOT of voices raised against this idea, both from key developers and other citizens of -current. Regardless of whether or not you think you're right and what reasons you have for thinking so, what this is saying is that there a lot of people who do not want this, and you would do well to listen to them. No-one (as far as I can see) is objecting to making ata the default (which it already is), and to kill wd in some number of weeks. Why can't you just do that, and put and end to this discussion happily? Will a few weeks really harm the development process? Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 15:44:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id A479514C8C for ; Fri, 10 Dec 1999 15:44:32 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA53269; Fri, 10 Dec 1999 16:44:17 -0700 (MST) (envelope-from ken) Message-Id: <199912102344.QAA53269@panzer.kdm.org> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: from Brad Knowles at "Dec 10, 1999 11:22:57 pm" To: blk@skynet.be (Brad Knowles) Date: Fri, 10 Dec 1999 16:44:16 -0700 (MST) Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), imp@village.org (Warner Losh), current@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote... > At 3:05 PM -0700 1999/12/10, Kenneth D. Merry wrote: > > > I agree that the CAM integration shouldn't be used as a precedent here. I > > don't agree with your characterization of it as a "debacle", though. > > > > On the whole, we gained a whole lot and lost very little. > > Long-term, yes I believe we gained a lot. Short-term, what I > recall having heard from some of the people who lived through it, > well let's just say it was really ugly and nasty for a certain period > of time. I don't think it was ugly and nasty at all. You're basing your opinions on second hand hearsay. If you can produce specific examples of why it was "really ugly and nasty", fine, but why not avoid making statements you can't support? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 15:51: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 1CD3B14C9D for ; Fri, 10 Dec 1999 15:51:04 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA43025; Fri, 10 Dec 1999 15:50:57 -0800 (PST) Date: Fri, 10 Dec 1999 15:50:55 -0800 (PST) From: Julian Elischer To: Poul-Henning Kamp Cc: Luoqi Chen , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <7594.944864544@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Dec 1999, Poul-Henning Kamp wrote: > > This fails the most important criteria for the transistion to ATA: > it doesn't break existing kernel configs. > > Listen guys, this is a tempest in a tea-cup, we are not loosing any > functionality here, we are gaining functionality. > > The wd driver doesn't have anything to recommend it on the i386 > platform and we need to switch to ATA. Then go and switch.. I'm not stopping you. Just leave the old files there in the meanwhile! It's not hurting you to do so, so stop being so unwilling to listen to other people's opinions and get on with your development! In the meanwhile I'll look at Cyrix support. But first I have to learn about the ata driver and I have too much on my plate as it is.. > > This is *CURRENT* remember ? We want this transistion done and > tested before current becomes 4.0-RELEASE. The time is NOW! So add your new stuff.. there is no hurry to remove the old one. The fact that there is an objection from more than 2 committers on this should have killed the argument already. You'd complain if someone other than you went ahead with something with this amount of objection. Stop trying to steamroll and just Leave the files alone. The same rules apply to you as others and the over-riding rule has always been that a decent level of objection on a non crucial point is enough to stop it reagrdless of what the author of the point feels. That's the way it goes. for adding new stuff, and for deleting old stuff. If you feel that you are excempt from peer review and that the committers as a group should be ignorable, just let us know. > > If we don't force people over to the ata driver it will not get > tested as much as it needs to. It'll get tested well and truely enough if it's teh default. and if it DOESN't work for someone, havingn the wd to fall back on would be a bloody good idea (TM). > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 15:55:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B7FDD14CB0; Fri, 10 Dec 1999 15:55: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.3/8.9.2) with ESMTP id AAA07883; Sat, 11 Dec 1999 00:55:15 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kris Kennaway Cc: Luoqi Chen , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 15:42:44 PST." Date: Sat, 11 Dec 1999 00:55:15 +0100 Message-ID: <7881.944870115@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Kris Ken naway writes: >No-one (as far as I can see) is objecting to making ata the default (which >it already is), and to kill wd in some number of weeks. Why can't you just >do that, and put and end to this discussion happily? Will a few weeks >really harm the development process? You overlook one simple thing here: If we want the ata driver tested, we need to make existing kernel configs break, otherwise people will not change them to use ata. We know this from bitter experience. The removal of wd has many discrete steps, but the first one is to make it clear to people that it is going away, this has been done by now I belive. The next thing is to break all the kernel configs, this has yet to happen, but it will happen real soon. This means that you have to really insist badly to make the wd driver work for you. Once we have established that the new driver doesn't leave a large number of people stranded it will be killed for good. What we need right NOW is for people to test the ata driver, and if it doesn't work, to debug as well as they can and report in excrutiating detail to sos so that he has a chance to analyze the problems. Just saying "It doesn't work for me" will simply not do. The more senior the person reporting, the more detail and quality information should be able to expect. Now, get back to work! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 16: 9:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id 3D03114A0D for ; Fri, 10 Dec 1999 16:09:53 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id BAA95350 for ; Sat, 11 Dec 1999 01:09:52 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9C3755.dip.t-dialin.net [62.156.55.85]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id BAA95342 for ; Sat, 11 Dec 1999 01:09:51 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3) with ESMTP id BAA01613 for ; Sat, 11 Dec 1999 01:08:18 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <38519601.75B59555@dead-end.net> Date: Sat, 11 Dec 1999 01:08:33 +0100 From: "D. Rock" X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: current@freebsd.org Subject: pcm driver breakage Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, something broke between rev 1.8 and 1.9 of /sys/dev/sound/pcm/channel.c The driver probes as a: pcm0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 The relevant kernel config entries are device pcm0 options PNPBIOS With the new revision, while playing pcm audio, I can only hear sound for fractions of a second and then the system freezes. Only the keyboard responds, so I could at least generate a crash dump: #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 #1 0xc014103d in panic (fmt=0xc0227914 "from debugger") at ../../kern/kern_shutdown.c:553 #2 0xc01278f5 in db_panic (addr=-1071627701, have_addr=0, count=-1, modif=0xcdcccb7c "") at ../../ddb/db_command.c:433 #3 0xc0127894 in db_command (last_cmdp=0xc02509bc, cmd_table=0xc025081c, aux_cmd_tablep=0xc026dcac) at ../../ddb/db_command.c:333 #4 0xc012795a in db_command_loop () at ../../ddb/db_command.c:455 #5 0xc0129977 in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xc0203ff5 in kdb_trap (type=3, code=0, regs=0xcdcccc90) at ../../i386/i386/db_interface.c:157 #7 0xc020fb30 in trap (frame={tf_fs = 16, tf_es = -1071251440, tf_ds = -1071185904, tf_edi = 0, tf_esi = 134, tf_ebp = -842216232, tf_isp = -842216260, tf_ebx = -1071124096, tf_edx = 0, tf_ecx = 525312, tf_eax = 38, tf_trapno = 3, tf_err = 0, tf_eip = -1071627701, tf_cs = 8, tf_eflags = 582, tf_esp = -1071359777, tf_ss = -1071373974}) at ../../i386/i386/trap.c:533 #8 0xc020424b in Debugger (msg=0xc024216a "manual escape to debugger") at machine/cpufunc.h:64 #9 0xc0200272 in scgetc (sc=0xc026c3e0, flags=2) at ../../dev/syscons/syscons.c:3737 #10 0xc01fbb41 in sckbdevent (thiskbd=0xc027d900, event=0, arg=0xc026c3e0) at ../../dev/syscons/syscons.c:643 #11 0xc01efccf in atkbd_intr (kbd=0xc027d900, arg=0x0) at ../../dev/kbd/atkbd.c:438 #12 0xc021b568 in atkbd_isa_intr (arg=0xc027d900) at ../../isa/atkbd_isa.c:123 #13 0xc01dd5e8 in chn_write (c=0xc0741f00, buf=0xcdcccee0) at ../../dev/sound/pcm/channel.c:315 #14 0xc01dc70b in dsp_write (d=0xc072c600, chan=0, buf=0xcdcccee0, flag=1) at ../../dev/sound/pcm/dsp.c:205 #15 0xc01dbc3d in sndwrite (i_dev=0xc073d080, buf=0xcdcccee0, flag=1) at ../../dev/sound/pcm/sound.c:311 #16 0xc0174cc1 in spec_write (ap=0xcdccce94) at ../../miscfs/specfs/spec_vnops.c:280 #17 0xc01c1980 in ufsspec_write (ap=0xcdccce94) at ../../ufs/ufs/ufs_vnops.c:1864 #18 0xc01c1ec1 in ufs_vnoperatespec (ap=0xcdccce94) at ../../ufs/ufs/ufs_vnops.c:2319 #19 0xc016f3e7 in vn_write (fp=0xc0773f80, uio=0xcdcccee0, cred=0xc05a8800, flags=0, p=0xcd7f6500) at vnode_if.h:359 #20 0xc014dbf5 in dofilewrite (p=0xcd7f6500, fp=0xc0773f80, fd=4, buf=0x8084000, nbyte=1024, offset=-1, flags=0) at ../../sys/file.h:156 #21 0xc014daf7 in write (p=0xcd7f6500, uap=0xcdcccf80) at ../../kern/sys_generic.c:297 #22 0xc02103aa in syscall (frame={tf_fs = 47, tf_es = -1078001617, tf_ds = 47, tf_edi = 134601232, tf_esi = 0, tf_ebp = -1, tf_isp = -842215468, tf_ebx = 0, tf_edx = 0, tf_ecx = 2804, tf_eax = 4, tf_trapno = 22, tf_err = 2, tf_eip = 671919968, tf_cs = 31, tf_eflags = 663, tf_esp = -1077945804, tf_ss = 47}) at ../../i386/i386/trap.c:1057 #23 0xc02048f6 in Xint0x80_syscall () Cannot access memory at address 0xffffffff. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 16:35:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 0D20815255; Fri, 10 Dec 1999 16:35:33 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01708; Thu, 9 Dec 1999 14:18:53 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912092218.OAA01708@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: Alexander Leidinger , sobomax@altavista.net, sos@freebsd.dk, phk@freebsd.org, current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Thu, 09 Dec 1999 13:57:54 PST." <199912092157.NAA01406@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 09 Dec 1999 14:18:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm completely at a loss as to how the ata driver could be responsible = > for your inability to read these disks. I don't have a copy of your = > original problem report to hand, but since I have all the hardware here= = > I'd appreciate it if you could be a little more explicit about your = > problem. Re-reading this, it's not clear that what I'm saying here is "please tell= = me a little more about what you're doing so that I can reproduce the = problem", not "your problem report is terrible, please go away and die". Sorry if that's caused any consternation. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 16:35:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from atlrel1.hp.com (atlrel1.hp.com [156.153.255.210]) by hub.freebsd.org (Postfix) with ESMTP id E52141546C for ; Fri, 10 Dec 1999 16:35:56 -0800 (PST) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (postal.sr.hp.com [15.4.46.173]) by atlrel1.hp.com (Postfix) with ESMTP id BCCC8A7AB; Fri, 10 Dec 1999 19:35:54 -0500 (EST) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id QAA22507; Fri, 10 Dec 1999 16:36:18 -0800 (PST) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id QAA13911; Fri, 10 Dec 1999 16:35:52 -0800 (PST) Message-Id: <199912110035.QAA13911@mina.sr.hp.com> To: Poul-Henning Kamp Cc: Kris Kennaway , Luoqi Chen , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Reply-To: Darryl Okahata In-reply-to: Your message of "Sat, 11 Dec 1999 00:55:15 +0100." <7881.944870115@critter.freebsd.dk> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Fri, 10 Dec 1999 16:35:52 -0800 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > Once we have established that the new driver doesn't leave a large > number of people stranded it will be killed for good. I think this is a key issue, if not *THE* key issue. Please correct me if I'm wrong, but PHK and others are basically saying: 1. If we allow the old drivers to exist, many people will not use the new drivers, and the new drivers will get little testing. 2. We, therefore, need to force people to use the new drivers by getting rid of the old ones. The concerns that other people have are: 1. "I'm worried about ATA. It was just called ``alpha-quality'' a few days ago, and now you want to promote it to something past ``beta-quality'', where, during a typical beta-test, both old and new drivers coexist. I'm worried about the stability of the ATA drivers." The timing is extremely unfortunate. Many people would have much fewer concerns (or "whining", as has been poorly said) if there were a "testing period" longer than a few days (where the ATA drivers are the default, but the old wd drivers still existed). 2. Functionality is currently missing. I hope I'm wrong, but the attitude seems to be: "If the ATA drivers are missing functionality, either fix it yourself or send hardware to the developers. If you can't fix it, you shouldn't be running -current". Well, this is fine to say, but I'd like to point out: * Many -current users have newer hardware, and tend to have fewer hardware that may not be supported by the new ATA drivers. Many -current users can afford to buy newer hardware (or do so because of business/consulting reasons). * I believe that many users of -release or -stable (who are not running -current and are not reading -current) tend to use older hardware -- the kind that may not be supported by the ATA drivers. The problem here is that we are potentially preventing users of older hardware from running 4.0-release/-stable when it comes out, because no one running -current has an example of their older hardware, and we removed the old drivers which may have worked. In other words, it's unclear as to whether or not the new driver will leave any significant number of people stranded, even if all -current developers test the h*ll out of ATA. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 17:33: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9778114D4F; Fri, 10 Dec 1999 17:32:58 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA57673; Fri, 10 Dec 1999 18:32:56 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA26623; Fri, 10 Dec 1999 18:32:56 -0700 (MST) Message-Id: <199912110132.SAA26623@harmony.village.org> To: Poul-Henning Kamp Subject: Re: HEADSUP: wd driver will be retired! Cc: Kris Kennaway , Luoqi Chen , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 11 Dec 1999 00:55:15 +0100." <7881.944870115@critter.freebsd.dk> References: <7881.944870115@critter.freebsd.dk> Date: Fri, 10 Dec 1999 18:32:56 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <7881.944870115@critter.freebsd.dk> Poul-Henning Kamp writes: : You overlook one simple thing here: If we want the ata driver tested, : we need to make existing kernel configs break, otherwise people : will not change them to use ata. We know this from bitter experience. If all you are talking about is something like: Index: files.i386 =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/sys/i386/conf/files.i386,v retrieving revision 1.282 diff -u -r1.282 files.i386 --- files.i386 1999/11/28 17:51:06 1.282 +++ files.i386 1999/12/11 01:31:00 @@ -318,6 +318,7 @@ i386/isa/stallion.c optional stl i386/isa/tw.c optional tw i386/isa/vesa.c optional vga +i386/isa/SirNotAppaeringInThisKerenl.c optional wd i386/isa/wd.c optional wd i386/isa/wd.c optional wdc i386/isa/wfd.c optional wfd I could go along with that. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 17:52:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 752A8153D4 for ; Fri, 10 Dec 1999 17:52:09 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA04860; Fri, 10 Dec 1999 17:54:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912110154.RAA04860@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nate@mt.sri.com (Nate Williams) Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 14:23:21 MST." <199912102123.OAA21691@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 17:54:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If half as much energy was spent adding the missing bits of functionality > > to the new systems as people have been spending complaining it then we'd be > > there ages ago. > > Not true. It doesn't take a disk expert to complain about a policy, but > it takes one to fix bugs/add features to the existing driver. :) :) :) That's ignoring the fact that it takes less energy to become enough of a "disk expert" to do something useful than it takes to engage in the sort of protracted whining that we're seeing. It does take more foresight and commitment to actually doing something though, and given the popularity of graffiti and mindless vandalism these days perhaps that's just par for the course. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 17:56:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id A1D2114E55 for ; Fri, 10 Dec 1999 17:56:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA04944; Fri, 10 Dec 1999 17:58:59 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912110158.RAA04944@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brad Knowles Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 22:47:22 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 17:58:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 10:32 PM +0100 1999/12/10, Poul-Henning Kamp wrote: > > > Well, the only precedent we have is CAM/SCSI, and it was done the > > same way. > > Given some of the things I've heard about the CAM/SCSI debacle, > I'm not sure that this is a good example to be trotting out right > now. Personally, I don't think that this is an experience we'd want > to be repeating -- especially not with something related to disk > devices. The same mentality that made the CAM cutover a "debacle" is making the ata cutover a "debacle". Fortunately, the CAM folks persisted despite the criticism, and I'm glad to see that Soren is taking the same stance. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 18:30:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id 5A8EF14E8A for ; Fri, 10 Dec 1999 18:30:45 -0800 (PST) (envelope-from haro@tk.kubota.co.jp) Received: by kbtfw.kubota.co.jp; id LAA20594; Sat, 11 Dec 1999 11:30:38 +0900 (JST) Received: from unknown(133.253.31.1) by kbtfw.kubota.co.jp via smap (V4.2) id xmaa20572; Sat, 11 Dec 99 11:29:39 +0900 Received: (from uucp@localhost) by lemond.gkn.kubota.co.jp (8.9.3+3.2W/3.7W99070916) with UUCP id LAA02996 for freebsd-current@freebsd.org; Sat, 11 Dec 1999 11:29:38 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by jkpc15.tk.kubota.co.jp (8.9.3/3.7W-uucp) with ESMTP id JAA59823 for ; Sat, 11 Dec 1999 09:10:54 +0900 (JST) To: freebsd-current@freebsd.org Subject: ATA weird message? X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991211091053B.haro@tk.kubota.co.jp> Date: Sat, 11 Dec 1999 09:10:53 +0900 From: haro@tk.kubota.co.jp (Munehiro Matsuda) X-Dispatcher: imput version 980905(IM100) Lines: 75 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I am using -current as of December 9 (CTM:src-cur.4130.gz), and got following weird ATA related messages while 'make -j4 buildworld'. I never had this kind of message when using wd drivers. ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata1-master: ad_timeout: lost disk contact - resetting ata1: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata1-master: ad_timeout: lost disk contact - resetting ata1: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata1-master: ad_timeout: lost disk contact - resetting ata1: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0-master: ad_timeout: trying fallback to PIO mode ata0: resetting devices .. done ata1-master: ad_timeout: lost disk contact - resetting ata1-master: ad_timeout: trying fallback to PIO mode ata1: resetting devices .. done What's happening here? System configuration follows: ------8<--------8<--------8<--------8<--------8<--------8<--------8<------ FreeBSD 4.0-CURRENT #0: Thu Dec 9 22:17:58 JST 1999 haro@jkpc15.gkn.kubota.co.jp:/usr/src/sys/compile/JKPC15 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (266.62-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping = 0 Features=0x183f9ff real memory = 67043328 (65472K bytes) avail memory = 61542400 (60100K bytes) Preloaded elf kernel "kernel" at 0xc0346000. Pentium Pro MTRR support enabled ------8<--------8<--------8<--------8<--------8<--------8<--------8<------ ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ad0: ATA-4 disk at ata0 as master ad0: 9590MB (19640880 sectors), 19485 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad2: ATA-3 disk at ata1 as master ad2: 4789MB (9809100 sectors), 10380 cyls, 15 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA33 ------8<--------8<--------8<--------8<--------8<--------8<--------8<------ # ATA and ATAPI devices controller ata0 controller ata1 #controller ata2 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives device atapifd0 # ATAPI floppy drives #device atapist0 # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices ------------------------------------------------------------------------------- _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Office of Business Planning & Developement, Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103, Japan Tel: +81-3-3245-3318 Fax: +81-3-32454-3315 Email: haro@tk.kubota.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 18:34:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 8E27A14E26 for ; Fri, 10 Dec 1999 18:34:13 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id VAA36883; Fri, 10 Dec 1999 21:32:56 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 10 Dec 1999 21:32:55 -0500 (EST) From: Chuck Robey To: "Daniel C. Sobral" Cc: Motoyuki Konno , current@FreeBSD.ORG Subject: Re: why 'The legacy aout build' was removed from current ? In-Reply-To: <3850F88D.92172FB0@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Dec 1999, Daniel C. Sobral wrote: > What Motoyuki-san is complaining about is that applications that > depend on a.out libraries will suffer. Alas, I don't think that's > the case, since all these libraries are (or ought to be, anyway) in > compat. > > > Looking at copious examples from real life, forcing 3rd party developers > > to upgrade is a good way to lose 3rd party developers. It just *sounds* > > like a good way to go. As long as this is a change for building world, > > and not making changes to the kern/imgact things (so we keep on executing > > aout binaries) then this is probably the best way to go. > > OTOH, going the other way around is the reason why we (users) had to > deal with things like 1 Mb RAM and 64 Kb segments in the age of > 486s, one generation after the introduction of the 80386. As a free > operating system supported by volunteer effort, we are interested in > driving the hardware to it's limits instead of being limited by the > ways we once did things. Absolutely, but (here's the caveat) if it *doesn't* hold up any new development, and there's a significant base of users actually deriving benefit from it, then I wouldn't agree. I'm kinda binary about that test, because I fully agree that, if it holds up technology in a project like ours, it's out the door! Stopping the new aout world builds doesn't injure users of aout software, it only *really* strongly discourages new development in aout. I think it just needed to be emphasized that the aout imgact stuff isn't being tossed, so aout executables will still work (those that aren't otherwise incompatible). ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 18:39:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 64DD514DFA for ; Fri, 10 Dec 1999 18:39:55 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id MAA05254; Sat, 11 Dec 1999 12:39:27 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd005249; Sat Dec 11 12:39:17 1999 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id MAA21780; Sat, 11 Dec 1999 12:39:17 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id MAA13288; Sat, 11 Dec 1999 12:39:16 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id MAA01680; Sat, 11 Dec 1999 12:39:16 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199912110239.MAA01680@nymph.detir.qld.gov.au> To: "Kenneth D. Merry" Cc: freebsd-current@freebsd.org, syssgm@detir.qld.gov.au, blk@skynet.be (Brad Knowles) Subject: Re: HEADSUP: wd driver will be retired! References: <199912102344.QAA53269@panzer.kdm.org> In-Reply-To: <199912102344.QAA53269@panzer.kdm.org> from "Kenneth D. Merry" at "Fri, 10 Dec 1999 16:44:16 -0700" Date: Sat, 11 Dec 1999 12:39:15 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 10th December 1999, "Kenneth D. Merry" wrote: >Brad Knowles wrote... >> At 3:05 PM -0700 1999/12/10, Kenneth D. Merry wrote: >> >> > I agree that the CAM integration shouldn't be used as a precedent here. >> > I don't agree with your characterization of it as a "debacle", though. >> > >> > On the whole, we gained a whole lot and lost very little. >> >> Long-term, yes I believe we gained a lot. Short-term, what I >> recall having heard from some of the people who lived through it, >> well let's just say it was really ugly and nasty for a certain period >> of time. > >I don't think it was ugly and nasty at all. You're basing your opinions >on second hand hearsay. If you can produce specific examples of why it >was "really ugly and nasty", fine, but why not avoid making statements you >can't support? This must depend on your perspective. My first hand view is that it was ugly and nasty. This is because I lost support for hardware I was actively using (some temporarily, some permanently), and because I had no control over the pace of change. For a bunch of reasons, there was no way I could keep up (and that meant porting old drivers to keep up). It sure felt ugly to me. The unnecessary renaming of device files made it worse. But that shouldn't stop us from moving forward with the ata driver. I think that a small slowing of the pace, and a bit more understanding toward those with unusual hardware will help. And I support PHK's hard line stance (except for the rushed pace) toward making the kernel break for users of wd. It has to be so, or no one will move. The wd code will still be in the CVS tree for desperate people to revive to use, and to port the missing bits into the ata driver. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 20: 6:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 4025D15816 for ; Fri, 10 Dec 1999 20:06:13 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id UAA07754; Fri, 10 Dec 1999 20:06:00 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912110406.UAA07754@gndrsh.dnsmgr.net> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912102115.OAA25113@harmony.village.org> from Warner Losh at "Dec 10, 1999 02:15:33 pm" To: imp@village.org (Warner Losh) Date: Fri, 10 Dec 1999 20:05:59 -0800 (PST) Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We've been telling people for a long time that the wd driver would > remain around even after ata went golden to support the ESDI systems > still in service. That sounds like it is changing now. Real support for ESDI died with bad144... Error free ESDI disks are very rare, even the best in my collection has 1 hard error and 3 soft. > It just feels like it is being rushed too much. My objections would > go away if you said it is going to die in the week between xmas and > new years. remove it from files today, to make sure that only the > really clueful can get to it, but don't do a cvs remove until after > the holidays... Someone needs to dull the dane's axe, it's cutting a bit deep and fast! :-) :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 20:23: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 0FC0514F02 for ; Fri, 10 Dec 1999 20:23:00 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id VAA00723; Fri, 10 Dec 1999 21:22:55 -0700 (MST) (envelope-from ken) Message-Id: <199912110422.VAA00723@panzer.kdm.org> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912110239.MAA01680@nymph.detir.qld.gov.au> from Stephen McKay at "Dec 11, 1999 12:39:15 pm" To: syssgm@detir.qld.gov.au (Stephen McKay) Date: Fri, 10 Dec 1999 21:22:55 -0700 (MST) Cc: freebsd-current@freebsd.org, blk@skynet.be (Brad Knowles) From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen McKay wrote... > On Friday, 10th December 1999, "Kenneth D. Merry" wrote: > >Brad Knowles wrote... > >> At 3:05 PM -0700 1999/12/10, Kenneth D. Merry wrote: > >> > >> > I agree that the CAM integration shouldn't be used as a precedent here. > >> > I don't agree with your characterization of it as a "debacle", though. > >> > > >> > On the whole, we gained a whole lot and lost very little. > >> > >> Long-term, yes I believe we gained a lot. Short-term, what I > >> recall having heard from some of the people who lived through it, > >> well let's just say it was really ugly and nasty for a certain period > >> of time. > > > >I don't think it was ugly and nasty at all. You're basing your opinions > >on second hand hearsay. If you can produce specific examples of why it > >was "really ugly and nasty", fine, but why not avoid making statements you > >can't support? > > This must depend on your perspective. My first hand view is that it was > ugly and nasty. This is because I lost support for hardware I was actively > using (some temporarily, some permanently), and because I had no control > over the pace of change. For a bunch of reasons, there was no way I could > keep up (and that meant porting old drivers to keep up). It sure felt > ugly to me. The unnecessary renaming of device files made it worse. I suppose it does depend on your perspective. We gave people about a year's worth of notice that some drivers would be going away unless someone stepped forward to port them. In most cases, no one stepped forward, and in one notable case, someone did step forward but never delivered. There was no way around the pace of the change -- it was an all or nothing transition. And as for the device renaming, you didn't have to change anything from sd->da. The old device names and nodes were supported in most every way. There were a lot of mis-informed people on the lists who claimed that you had to change your device names. That was completely untrue, and I attempted to correct people, but the myth and FUD continued to propagate. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 20:38: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 027A714F4F for ; Fri, 10 Dec 1999 20:38:07 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id UAA53426; Fri, 10 Dec 1999 20:37:53 -0800 (PST) Date: Fri, 10 Dec 1999 20:37:52 -0800 (PST) From: Julian Elischer To: "Kenneth D. Merry" Cc: Stephen McKay , freebsd-current@FreeBSD.ORG, Brad Knowles Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912110422.VAA00723@panzer.kdm.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, 10 Dec 1999, Kenneth D. Merry wrote: > And as for the device renaming, you didn't have to change anything from > sd->da. The old device names and nodes were supported in most every way. > There were a lot of mis-informed people on the lists who claimed that you > had to change your device names. That was completely untrue, and I > attempted to correct people, but the myth and FUD continued to propagate. Of course the whole idea of changing from sd to da was (in my opinion) rather silly in the first place since it actually didn't achieve anything except to make people wonder how such silliness was allowed to occur. (i.e the pain far outweighed the asthetic gain, because there was some minor pain and the asthetic gain existed in the minds of about 3 people on the planet) It would have hurt absolutely nothing to keep calling them sd0 etc. > > Ken > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 21: 4: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 3742714D52; Fri, 10 Dec 1999 21:04:01 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id PAA09409; Sat, 11 Dec 1999 15:03:24 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd009407; Sat Dec 11 15:03:21 1999 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id PAA22877; Sat, 11 Dec 1999 15:03:21 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id PAA15883; Sat, 11 Dec 1999 15:03:22 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id PAA01950; Sat, 11 Dec 1999 15:03:19 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199912110503.PAA01950@nymph.detir.qld.gov.au> To: Mike Smith Cc: freebsd-current@freebsd.org, syssgm@detir.qld.gov.au Subject: Re: HEADSUP: wd driver will be retired! References: <199912110158.RAA04944@mass.cdrom.com> In-Reply-To: <199912110158.RAA04944@mass.cdrom.com> from Mike Smith at "Fri, 10 Dec 1999 17:58:59 -0800" Date: Sat, 11 Dec 1999 15:03:19 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 10th December 1999, Mike Smith wrote: >The same mentality that made the CAM cutover a "debacle" is making the >ata cutover a "debacle". This "mentality" might be an unavoidable part of human nature. I found my first reaction was "How dare they take away something I have now?!" and it took some careful thinking to see that my loss was actually very small against future benefits. It might be that these things have to be predicted by -core and handled "touchy feely" like: core: What if we do this ? public: Um, sounds scary. When will you do it? Will I lose anything? core: We think a month from now, and you will lose support for and . public: We don't use and any more, so fine. instead of the current (caricatured for emphasis): core: We will do soon. Probably today. public: Oh my God! core: It's for your own good. You always complain and make it difficult! public: We don't want to change anything, ever! It's so hard! You must support all my hardware for ever and ever! >Fortunately, the CAM folks persisted despite the criticism, and I'm glad >to see that Soren is taking the same stance. Not everything improved with CAM. Personally I'm only receiving the benifits of CAM now, about a year after it replaced the old system. On the balance it has been good for FreeBSD, but you have to remember that there will be small pockets of users that will get the short end of the stick. How the project deals with the losers in these deals is important for its long term health. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 21:32:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from p.wl.vg (209-9-69-194.sdsl.cais.net [209.9.69.194]) by hub.freebsd.org (Postfix) with ESMTP id 4F39614F7D for ; Fri, 10 Dec 1999 21:32:29 -0800 (PST) (envelope-from patrick@p.wl.vg) Received: (from patrick@localhost) by p.wl.vg (8.9.3/8.9.3) id AAA00696; Sat, 11 Dec 1999 00:31:33 -0500 (EST) (envelope-from patrick) Message-Id: <199912110531.AAA00696@p.wl.vg> Date: Sat, 11 Dec 1999 00:31:33 -0500 (EST) From: patrick@whetstonelogic.com Subject: Re: ATA weird message? To: haro@tk.kubota.co.jp, freebsd-current@FreeBSD.org In-Reply-To: <19991211091053B.haro@tk.kubota.co.jp> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11 Dec, Munehiro Matsuda wrote: > Hi all, > > I am using -current as of December 9 (CTM:src-cur.4130.gz), and > got following weird ATA related messages while 'make -j4 buildworld'. > I never had this kind of message when using wd drivers. > > ata0-master: ad_timeout: lost disk contact - resetting > ata0: resetting devices .. done > ata1-master: ad_timeout: lost disk contact - resetting > ata1: resetting devices .. done I too am seeing this. I decided tonight to go from -STABLE (3.4-RC) to -CURRENT. After I built a 4.0-CURRENT kernel and rebooted into single user mode, I started to "make -j10 buildworld" with /usr mounted async. In about 10 minutes, I got a similar error to the above error: ata1-master: ad_timeout: lost disk contact - resetting ata1: resetting devices .. done ad_transfer: timeout waiting for DRQ At that point, my system freezes up. I have to reboot. I thought it was the "-j10", so when I rebooted back into -CURRENT kernel single user mode, I did just a "make buildworld". After some time, it again gave me the same error. I booted into -STABLE and verified that everything was working and it was. So I recompiled the -CURRENT kernel without SOFTUPDATES (and all other "extras"), just in case. It went further this time in the build, but still froze with the above error. Summary: The error occurred no matter if I was using softupdates, async mount, or normal mount. I cannot build -CURRENT. In -STABLE, I am fine, and have been running -STABLE for over a year now on this machine. Information on System: Dual Pentium 200 on ASUS P/E-P55T2P4D motherboard with 128Megs EDO RAM. dmesg from -STABLE: FreeBSD 3.4-RC #1: Thu Dec 9 19:45:30 EST 1999 root@p.wl.vg:/usr/src/sys/compile/PATRICK Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x3bf real memory = 134217728 (131072K bytes) avail memory = 128000000 (125000K bytes) Programming 16 pins in IOAPIC #0 EISA INTCONTROL = 00000c00 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 Preloaded elf kernel "kernel.stable" at 0xc025e000. eisa0: Probing for devices on the EISA bus Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x05 on pci0.7.0 vga0: rev 0x5c int a irq 10 on pci0.10.0 fxp0: rev 0x08 int a irq 11 on pci0.1 1.0 fxp0: Ethernet address 00:90:27:cb:0f:32 ide_pci0: rev 0x01 int a irq 14 on pci 0.13.0 Probing for PnP devices: CSN 1 Vendor ID: ALS0120 [0x20019305] Serial 0xffffffff Comp ID: @@@0000 [0x000 00000] Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 on isa ed0: address 00:e0:29:17:73:26, type NE2000 (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0x90ff on isa wdc0: unit 0 (wd0): , LBA, 32-bit, multi-block-32 wd0: 4103MB (8404830 sectors), 523 cyls, 255 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0x90ff90ff on isa wdc1: unit 0 (wd2): , LBA, 32-bit, multi-block-32 wd2: 4103MB (8404830 sectors), 523 cyls, 255 heads, 63 S/T, 512 B/S wdc1: unit 1 (atapi): , removable, accel, ovlap, dma, iordis acd0: drive speed 4134KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface joy0 at 0x201 on isa joy0: joystick Intel Pentium detected, installing workaround for F00F bug APIC_IO: routing 8254 via pin 2 changing root device to wd2s1a SMP: AP CPU #1 Launched! Some probes from -CURRENT: mainboard0: on eisa 0 slot 0 ata-pci0: irq 14 at device 13.0 on pci0 ata-pci0: Busmastering DMA Supported If someone needs more information or for me to do any testing, please let me know. I'm not a developer, but I'm certainly willing to be a tester! Patrick Gardella To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 21:51:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles536.castles.com [208.214.165.100]) by hub.freebsd.org (Postfix) with ESMTP id B59E214F7D for ; Fri, 10 Dec 1999 21:51:55 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA00494; Fri, 10 Dec 1999 21:53:30 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912110553.VAA00494@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 21:22:55 MST." <199912110422.VAA00723@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 21:53:30 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And as for the device renaming, you didn't have to change anything from > sd->da. The old device names and nodes were supported in most every way. > There were a lot of mis-informed people on the lists who claimed that you > had to change your device names. That was completely untrue, and I > attempted to correct people, but the myth and FUD continued to propagate. Changing the device nodes' names was the only sensible thing to do when everything else that referred to the device by name (source files, kernel config, boot-time messages) used the new name. Ther -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 21:54:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles536.castles.com [208.214.165.100]) by hub.freebsd.org (Postfix) with ESMTP id 452F814E7E for ; Fri, 10 Dec 1999 21:54:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA00518; Fri, 10 Dec 1999 21:57:17 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912110557.VAA00518@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Stephen McKay Cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sat, 11 Dec 1999 15:03:19 +1000." <199912110503.PAA01950@nymph.detir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 21:57:17 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Friday, 10th December 1999, Mike Smith wrote: > > >The same mentality that made the CAM cutover a "debacle" is making the > >ata cutover a "debacle". > > This "mentality" might be an unavoidable part of human nature. I found That was my musing in the next paragraph. > my first reaction was "How dare they take away something I have now?!" > and it took some careful thinking to see that my loss was actually very > small against future benefits. It might be that these things have to be > predicted by -core and handled "touchy feely" like: Core isn't typically involved in these decisions, nor should it be. I also raised the point you make here when I said that it'd have been nice for the parties responsible for the change to soften the blow a bit. > >Fortunately, the CAM folks persisted despite the criticism, and I'm glad > >to see that Soren is taking the same stance. > > Not everything improved with CAM. Personally I'm only receiving the > benifits of CAM now, about a year after it replaced the old system. > On the balance it has been good for FreeBSD, but you have to remember > that there will be small pockets of users that will get the short end > of the stick. How the project deals with the losers in these deals is > important for its long term health. It's more how the losers deal with the project, to be honest. There has to be a way to make them realise that it's not reasonable to expect everyone else to live in pain just because they (think they) are still comfortable. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 22:18:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 75C2414F7D; Fri, 10 Dec 1999 22:18:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA02440; Fri, 10 Dec 1999 22:18:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Soren Schmidt Cc: julian@whistle.com (Julian Elischer), phk@FreeBSD.ORG (Poul-Henning Kamp), current@FreeBSD.ORG Subject: Audio support [was Re: HEADSUP: wd driver will be retired!] In-reply-to: Your message of "Wed, 08 Dec 1999 18:21:56 +0100." <199912081721.SAA70567@freebsd.dk> Date: Fri, 10 Dec 1999 22:18:24 -0800 Message-ID: <2436.944893104@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The same thing is about to apply to the woxware sound code, we have a > new shiny system that works and is much better designed... Actually, I'm sad to say that our shiny new sound system does *not* work for some of the most popular audio chipsets on the market today (where the older "luigi" sound system did support them) and this is a matter of significant concern to some folks, myself included. We're getting a larger population of people who expect FreeBSD to simply continue to work from release to release, and this is not an unreasonable expectation when you think about it. Unfortunately, when we remove support for a piece of hardware which was formerly supported (the aic driver being a good example) and this particular hardware happens to be in those people's machines, well, it's easy to see where "continuing to work" is no longer a claim we can make for FreeBSD's progress in such cases. When this is also for some really old and grotty piece of hardware, like floppy tape drives, and nobody is interested in actively maintaining the driver for it, then that's a reasonably justifable argument for taking that kind of public relations trade-off. When the hardware in question is something that's currently being sold on the open market and is still quite popular, like the SB16 PCI or Vibra16X on-board audio chipset, then killing off support for it is quite another thing. Both of those device currently refuse to work in any of my -current test boxes and perhaps you should have chosen a better example in making your argument. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 22:44:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 5D1CA14BF5 for ; Fri, 10 Dec 1999 22:44:55 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id BAA00372 for ; Sat, 11 Dec 1999 01:44:53 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Sat, 11 Dec 1999 01:44:53 -0500 (EST) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: timecounter Message-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 not sure the timecounters are being detected properly on my home computer. A while back (around August) -CURRENT's kernel detected 2 timecounters, and using systat -vm, I could see clk generating 100 interrupts (I'm assuming per second) and rtc0 generating about 128 per second. Around the time we changed over to gcc-2.95.2, I noticed that rtc0 is no longer detected, and only one timecounter is detected at boot. The bad effect of this is that the system doesn't accurately show the cpu usage. Any suggestions on how to fix this, or pointers to where the cpu_initclocks() function would be nice :-) Thanks ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 22:45:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 1E9DA1506A; Fri, 10 Dec 1999 22:45: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.3/8.9.3) with ESMTP id WAA70398; Fri, 10 Dec 1999 22:44:22 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912110644.WAA70398@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" Cc: Soren Schmidt , julian@whistle.com (Julian Elischer), phk@FreeBSD.ORG (Poul-Henning Kamp), current@FreeBSD.ORG Subject: Re: Audio support [was Re: HEADSUP: wd driver will be retired!] In-reply-to: Your message of "Fri, 10 Dec 1999 22:18:24 PST." <2436.944893104@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 22:44:22 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You better watch it Jordan , you are starting to sound like a multimedia guy 8) -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 22:45:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 57C9815074; Fri, 10 Dec 1999 22:45: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.3/8.9.3) with ESMTP id WAA70398; Fri, 10 Dec 1999 22:44:22 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912110644.WAA70398@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" Cc: Soren Schmidt , julian@whistle.com (Julian Elischer), phk@FreeBSD.ORG (Poul-Henning Kamp), current@FreeBSD.ORG Subject: Re: Audio support [was Re: HEADSUP: wd driver will be retired!] In-reply-to: Your message of "Fri, 10 Dec 1999 22:18:24 PST." <2436.944893104@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 22:44:22 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You better watch it Jordan , you are starting to sound like a multimedia guy 8) -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 22:59:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id B603C14E2B for ; Fri, 10 Dec 1999 22:59:07 -0800 (PST) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.1a/8.9.1) id OAA20899 for freebsd-current@freebsd.org; Sat, 11 Dec 1999 14:21:26 +0800 (WST) From: Michael Kennett Message-Id: <199912110621.OAA20899@laurasia.com.au> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912110553.VAA00494@mass.cdrom.com> from Mike Smith at "Dec 10, 99 09:53:30 pm" To: freebsd-current@freebsd.org Date: Sat, 11 Dec 1999 14:21:25 +0800 (WST) 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 FWIW, here are my experiences with the new ATA driver. Firstly, I've been following the discussion on -current, and decided that this weekend I'd convert over to the new ata drivers - but with a bit of trepidation, given the discussion that's been going on. Anyway, I've rebuild my kernel, rebooted once, rebooted again, and the system seems to be holding together. The sky has not fallen on my head... Firstly, my old set up had: controller wdc0 at isa? port IO_WD1 irq14 controller wdc1 at isa? port IO_WD2 irq15 device wd0 at wdc0 drive 0 device wd2 at wdc2 drive 0 Note that wd1 is not present. This caused a mild hickup when rebooting the new kernel, since the new ata controller assigned the labels ad0 and ad1 to the drives. It was not possible to boot into multiuser mode without changing the /etc/fstab file to rename the /dev/wd2* entries to /dev/ad1*. That was easy to fix, however for a newbie it might cause problems. I mention it now, since the upgrade from 3.x might need special handling of this case (?). Finally, I've noticed the following messages: Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0 retrying Dec 11 13:54:50 rabbit last message repeated 2 times Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0 falling back to PIO mode It strikes me that these aren't serious - just that my hardware is rather crappy (and doesn't support the faster UDMA modes) :-) In case the developers are interested, here are selected portions of dmesg of the pre/post changes... Dec 11 13:41:29 rabbit /kernel.991204: FreeBSD 4.0-CURRENT #0: Sat Dec 4 19:07:15 WST 1999 Dec 11 13:41:29 rabbit /kernel.991204: pcib0: on motherboard Dec 11 13:41:29 rabbit /kernel.991204: pci0: on pcib0 Dec 11 13:41:29 rabbit /kernel.991204: isab0: at device 7.0 on pci0 Dec 11 13:41:29 rabbit /kernel.991204: isa0: on isab0 Dec 11 13:41:29 rabbit /kernel.991204: chip1: at device 7.1 on pci0 Dec 11 13:41:29 rabbit /kernel.991204: wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 Dec 11 13:41:29 rabbit /kernel.991204: wdc0: unit 0 (wd0): Dec 11 13:41:29 rabbit /kernel.991204: wd0: 696MB (1427328 sectors), 1416 cyls, 16 heads, 63 S/T, 512 B/S Dec 11 13:41:29 rabbit /kernel.991204: wdc1 at port 0x170-0x177 irq 15 on isa0 Dec 11 13:41:29 rabbit /kernel.991204: wdc1: unit 0 (wd2): Dec 11 13:41:29 rabbit /kernel.991204: wd2: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S Dec 11 13:54:50 rabbit /kernel: FreeBSD 4.0-CURRENT #0: Sat Dec 11 13:34:57 WST 1999 Dec 11 13:54:50 rabbit /kernel: pcib0: on motherboard Dec 11 13:54:50 rabbit /kernel: pci0: on pcib0 Dec 11 13:54:50 rabbit /kernel: isab0: at device 7.0 on pci0 Dec 11 13:54:50 rabbit /kernel: isa0: on isab0 Dec 11 13:54:50 rabbit /kernel: ata-pci0: at device 7.1 on pci0 Dec 11 13:54:50 rabbit /kernel: ata-pci0: Busmastering DMA supported Dec 11 13:54:50 rabbit /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Dec 11 13:54:50 rabbit /kernel: ata1 at 0x0170 irq 15 on ata-pci0 Dec 11 13:54:50 rabbit /kernel: ata-isa0: already registered as ata0 Dec 11 13:54:50 rabbit /kernel: ata-isa1: already registered as ata1 Dec 11 13:54:50 rabbit /kernel: ad0: ATA-? disk at ata0 as master Dec 11 13:54:50 rabbit /kernel: ad0: 696MB (1427328 sectors), 1416 cyls, 16 heads, 63 S/T, 512 B/S Dec 11 13:54:50 rabbit /kernel: ad0: 16 secs/int, 1 depth queue, PIO Dec 11 13:54:50 rabbit /kernel: ad1: ATA-4 disk at ata1 as master Dec 11 13:54:50 rabbit /kernel: ad1: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S Dec 11 13:54:50 rabbit /kernel: ad1: 16 secs/int, 1 depth queue, UDMA66 Dec 11 13:54:50 rabbit /kernel: Mounting root from ufs:/dev/ad0a Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0 retrying Dec 11 13:54:50 rabbit last message repeated 2 times Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0 falling back to PIO mode To summarise, I've experienced no difficulty in changing to the new ATA drivers. I'm in the midst of rebuilding world, and so far there have been no errors in the process (and I don't expect any) Thank you to the Soren, and the developers of this new driver. Mike Kennett (mike@laurasia.com.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 22:59:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 183F214BF5; Fri, 10 Dec 1999 22:59:17 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA00670; Fri, 10 Dec 1999 23:59:15 -0700 (MST) (envelope-from ken) Message-Id: <199912110659.XAA00670@panzer.kdm.org> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912110553.VAA00494@mass.cdrom.com> from Mike Smith at "Dec 10, 1999 09:53:30 pm" To: msmith@freebsd.org (Mike Smith) Date: Fri, 10 Dec 1999 23:59:15 -0700 (MST) Cc: freebsd-current@freebsd.org From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote... > > And as for the device renaming, you didn't have to change anything from > > sd->da. The old device names and nodes were supported in most every way. > > There were a lot of mis-informed people on the lists who claimed that you > > had to change your device names. That was completely untrue, and I > > attempted to correct people, but the myth and FUD continued to propagate. > > Changing the device nodes' names was the only sensible thing to do when > everything else that referred to the device by name (source files, kernel > config, boot-time messages) used the new name. Ther Looks like your mail got a little truncated. In any case, yes, it does make more sense to be consistent and use the new names, but what I was getting at is that there were some folks who said things like: "You have to change all your device names to da* in order to use CAM." That isn't true, of course, but it certainly caused some confusion and consternation. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 23: 7:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A989D14D56 for ; Fri, 10 Dec 1999 23:07:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA02549; Fri, 10 Dec 1999 23:07:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Poul-Henning Kamp Cc: Greg Lehey , Soren Schmidt , Blaz Zupan , Christopher Masto , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 17:11:53 +0100." <5386.944842313@critter.freebsd.dk> Date: Fri, 10 Dec 1999 23:07:12 -0800 Message-ID: <2545.944896032@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Look at the sound code to see why your proposal doesn't work in our > reality. Again, bad example. The sound card may very well turn out to be an area where we fucked up; it's far too early to say yet. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 23:20:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 5092A14D2C; Fri, 10 Dec 1999 23:20:43 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA02594; Fri, 10 Dec 1999 23:20:19 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Poul-Henning Kamp Cc: nate@mt.sri.com (Nate Williams), Mike Smith , Christopher Masto , Julian Elischer , current@FreeBSD.ORG Subject: Reasonable decision-making [Re: HEADSUP: wd driver will be retired!] In-reply-to: Your message of "Fri, 10 Dec 1999 19:14:01 +0100." <6235.944849641@critter.freebsd.dk> Date: Fri, 10 Dec 1999 23:20:19 -0800 Message-ID: <2590.944896819@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The ATA driver went golden now, and to make sure nobody is distracted > from testing it before 4.0-RELEASE is cut, the wd driver will be > removed. > > It's really that simple. Well, I'm not sure that's really true yet and I would honestly prefer it if you wouldn't make "conclusive statements" like this without waiting for a reasonable period of time, *after* the flame war in progress has died down and everyone's done venting and flapping their arms, to come to a decision with all the "votes" carefully weighed (and appropriately weighted). To do otherwise would send a strong message that your intention was to procede regardless of public opinion, which would further imply that the more consensus-based process of deciding these things somehow does not apply to you. People would then ask why this process does not apply to you when it appears to apply to others, raising embarassing and annoying questions about equality, egalitarianism, core Stalins, the insidious effects of space aliens genetically modifying Danish dairy cows, etc. etc. From what I've seen of the thread so far, this has already sort of begun to happen and my strategy on the whole affair at this point has been to simply make marks on a tally-sheet near my keyboard, whacking `delete' in the mailer after making the appropriate check mark under the "yes", "no", "undecided" or "went off into the weeds on a completely unrelated tangent" columns. This allows me to try and sift out all the emoting from the Real Issue(tm) to be decided and, hopefully, come to my own conclusions based on the tally-sheet and further discussion with those parties directly involved (no, I didn't forget them). I'll even be happy to post my little tally of this whole sorry thread to -committers, assuming there's any interest in such a synopsis. In any case, the Real Issue here appears to be whether or not it's necessary to socially engineer people by removing the wd driver one week after the ata driver was declared "golden" or whether it's perhaps more prudent to simply leave the damn thing there for now and just stop maintaining it, leaving its future to Darwin and/or some future committer who takes an axe to it because it's rotted for so long that it finally no longer even builds and/or functions at all. All other discussion has been more or less tangental to that issue. I have my own opinions on this, of course, but I'm more interested in what everyone else here has to say about it right now. Maybe I'll change my mind once I've finished making my little marks and talking to people, and you yourself would certainly not lose any points with your audience by demonstrating a similar degree of flexibility. It certainly doesn't seem like too much to ask for. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 23:22:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id 92EEB14F7A for ; Fri, 10 Dec 1999 23:22:11 -0800 (PST) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.1a/8.9.1) id PAA08605 for freebsd-current@freebsd.org; Sat, 11 Dec 1999 15:22:05 +0800 (WST) From: Michael Kennett Message-Id: <199912110722.PAA08605@laurasia.com.au> Subject: Install of 4.0-19991208-CURRENT To: freebsd-current@freebsd.org Date: Sat, 11 Dec 1999 15:22:04 +0800 (WST) 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 I've just tried installing the last current snapshot (4.0-19991208-CURRENT) onto an IBM laptop (365, type 2625-2E9) with a Xircom networking card (CE3B-100BTX). It failed -- the pccard was not recognized. I mention this because the floppies/pccard/README.TXT mentioned the systems that have been tested. Regards, Mike Kennett (mike@laurasia.com.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 23:30:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles536.castles.com [208.214.165.100]) by hub.freebsd.org (Postfix) with ESMTP id EDA9D14F60 for ; Fri, 10 Dec 1999 23:30:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA01032; Fri, 10 Dec 1999 23:32:27 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912110732.XAA01032@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Childers Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 18:18:55 EST." <4.2.0.58.19991210180808.00945190@pop.uky.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 23:32:27 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Except that ATA currently does not work on my system. So I assume I'm not > the only one. Actually, to quote from your original message: ] According to technical product summary, the primary IDE interface, on ] which both my drives reside, is a PCTech RZ1000 on the PCI local bus. Nobody in their right mind uses the RZ1000 chipset for IDE. It's one of the classic "broken" parts (along with several of the CMD64x family) that you just don't use. You're probably not the only one out there with one of these controllers, but there aren't anywhere near that many of them still circulating after the massive problems that were encountered with that part _many_ years ago. > I am not a developer but I am running current on a test > system to see what's in line for stable. I do not mind when things break > for a while. But, since others did not seem to have this problem, I sent > an email to the list. The link is below. So far, I've heard no word, and > things are still broken. For this reason, I'd like wd to stay in the tree > until ATA is fixed. Otherwise, my machine is unusable. I'm not really in a position to determine what will or won't happen regarding support for known-defective hardware like the RZ1000 or the CMD640, but I'd say that it's likely to receive fairly low-priority treatment. It's not, of course, clear from your message whether the problem is actually related to the RZ1000 part itself, or whether it's actually a manifestation of the "system goes nowhere at startup" problem that other people are seeing (seems to be related to interrupt handling by the 'ata' driver). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 23:52:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 6171B14E34; Fri, 10 Dec 1999 23:52:34 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA12378; Sat, 11 Dec 1999 08:52:28 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: Kris Kennaway , Luoqi Chen , current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Fri, 10 Dec 1999 18:32:56 MST." <199912110132.SAA26623@harmony.village.org> Date: Sat, 11 Dec 1999 08:52:28 +0100 Message-ID: <12376.944898748@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912110132.SAA26623@harmony.village.org>, Warner Losh writes: >In message <7881.944870115@critter.freebsd.dk> Poul-Henning Kamp writes: >: You overlook one simple thing here: If we want the ata driver tested, >: we need to make existing kernel configs break, otherwise people >: will not change them to use ata. We know this from bitter experience. > >If all you are talking about is something like: > >Index: files.i386 >=================================================================== >RCS file: /home/imp/FreeBSD/CVS/src/sys/i386/conf/files.i386,v >retrieving revision 1.282 >diff -u -r1.282 files.i386 >--- files.i386 1999/11/28 17:51:06 1.282 >+++ files.i386 1999/12/11 01:31:00 >@@ -318,6 +318,7 @@ > i386/isa/stallion.c optional stl > i386/isa/tw.c optional tw > i386/isa/vesa.c optional vga >+i386/isa/SirNotAppaeringInThisKerenl.c optional wd > i386/isa/wd.c optional wd > i386/isa/wd.c optional wdc > i386/isa/wfd.c optional wfd > > >I could go along with that. And probably an #error "Don't use this driver, use ata-disk instead" in wd.d -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 10 23:59: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id DE48614D04 for ; Fri, 10 Dec 1999 23:59:00 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA12509; Sat, 11 Dec 1999 08:58:53 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kenneth Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: timecounter In-reply-to: Your message of "Sat, 11 Dec 1999 01:44:53 EST." Date: Sat, 11 Dec 1999 08:58:53 +0100 Message-ID: <12507.944899133@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The rtc is not a timecounter, and I doubt the the problem is related to timecounters at all. The RTC is always detected, because we know it is there, but it may be that you don't get any interrupts from it, I don't know why that might be. Poul-Henning In message , Ke nneth Culver writes: >I am not sure the timecounters are being detected properly on my home >computer. A while back (around August) -CURRENT's kernel detected 2 >timecounters, and using systat -vm, I could see clk generating 100 >interrupts (I'm assuming per second) and rtc0 generating about 128 per >second. Around the time we changed over to gcc-2.95.2, I noticed that rtc0 >is no longer detected, and only one timecounter is detected at boot. The >bad effect of this is that the system doesn't accurately show the cpu >usage. Any suggestions on how to fix this, or pointers to where the >cpu_initclocks() function would be nice :-) Thanks > > >================================================================= >| Kenneth Culver | FreeBSD: The best OS around. | >| Unix Systems Administrator | ICQ #: 24767726 | >| and student at The | AIM: AgRSkaterq | >| The University of Maryland, | Website: (Under Construction) | >| College Park. | http://www.wam.umd.edu/~culverk/| >================================================================= > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 0: 0:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 17E3814E23 for ; Sat, 11 Dec 1999 00:00:55 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA12543; Sat, 11 Dec 1999 09:00:38 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Michael Kennett Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sat, 11 Dec 1999 14:21:25 +0800." <199912110621.OAA20899@laurasia.com.au> Date: Sat, 11 Dec 1999 09:00:38 +0100 Message-ID: <12541.944899238@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912110621.OAA20899@laurasia.com.au>, Michael Kennett writes: >Finally, I've noticed the following messages: > >Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0 retrying >Dec 11 13:54:50 rabbit last message repeated 2 times >Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0 falling back to PIO mode > This is actually a very good example of where the new driver gives us a marked improvement: It has a fall back path for troubled hardware, to safe modes. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 0: 4:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3DE4514E7D; Sat, 11 Dec 1999 00:04:08 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA12571; Sat, 11 Dec 1999 09:03:53 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Jordan K. Hubbard" Cc: nate@mt.sri.com (Nate Williams), Mike Smith , Christopher Masto , Julian Elischer , current@FreeBSD.ORG Subject: Re: Reasonable decision-making [Re: HEADSUP: wd driver will be retired!] In-reply-to: Your message of "Fri, 10 Dec 1999 23:20:19 PST." <2590.944896819@zippy.cdrom.com> Date: Sat, 11 Dec 1999 09:03:52 +0100 Message-ID: <12569.944899432@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <2590.944896819@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> The ATA driver went golden now, and to make sure nobody is distracted >> from testing it before 4.0-RELEASE is cut, the wd driver will be >> removed. >> >> It's really that simple. > >Well, I'm not sure that's really true yet and I would honestly prefer >it if you wouldn't make "conclusive statements" like this without >waiting for a reasonable period of time, *after* the flame war in >progress has died down and everyone's done venting and flapping their >arms, to come to a decision with all the "votes" carefully weighed >(and appropriately weighted). > >To do otherwise would send a strong message that your intention was to >procede regardless of public opinion, which would further imply that >the more consensus-based process of deciding these things somehow does >not apply to you. I am keeping very close track of the messages from people who report problems with the new drivers, but I am totally ignoring the noise by people who "just on principle" are against this move. >In any case, the Real Issue here appears to be whether or not it's >necessary to socially engineer people by removing the wd driver one >week after the ata driver was declared "golden" or whether it's >perhaps more prudent to simply leave the damn thing there for now and >just stop maintaining it, leaving its future to Darwin and/or some >future committer who takes an axe to it because it's rotted for so >long that it finally no longer even builds and/or functions at all. >All other discussion has been more or less tangental to that issue. Unless we break kernel configs with the wd driver in it, we will never get rid of it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 1: 2:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from darkstar.qx.net (darkstar.qx.net [208.235.88.101]) by hub.freebsd.org (Postfix) with ESMTP id 87EE214F98 for ; Sat, 11 Dec 1999 01:02:28 -0800 (PST) (envelope-from gchil0@pop.uky.edu) Received: from mail.qx.net (mail.qx.net [208.235.88.10]) by darkstar.qx.net (8.8.7/8.8.7) with ESMTP id EAA03203 for ; Sat, 11 Dec 1999 04:02:21 -0500 Received: from k7 ([208.200.111.71]) by mail.qx.net (Netscape Messaging Server 3.6) with ESMTP id AAA4685; Sat, 11 Dec 1999 04:05:10 -0500 Message-Id: <4.2.0.58.19991211021308.00955600@pop.uky.edu> X-Sender: gchil0@pop.uky.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sat, 11 Dec 1999 02:23:35 -0500 To: sos@freebsd.dk From: Greg Childers Subject: Re: ATA problem Cc: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, With a bit of investigating, I've found the problem described in my previous email quoted at the end of this message started with the commits listed below. A kernel built using sources just before these commits works fine, whereas a kernel build just after freezes after the line Mounting root from ufs:wd0s1a Hope this helps. If you need any more info, just ask. Greg sos 1999/10/09 12:57:15 PDT Modified files: sys/dev/ata ata-all.c ata-all.h ata-disk.c ata-disk.h ata-dma.c atapi-all.c atapi-all.h atapi-cd.c atapi-fd.c atapi-fd.h atapi-tape.c atapi-tape.h Log: Add support for the HPT366 chip, this is used on the Abit boards and their HotRod controller and on SIIG PCI ultra DMA controller. These changes also made lots of the Promise code go away, its all much more generic this way. Get rid of atapi_immed_cmd, instead use the queue to move atapi commands from interrupt context if nessesary, the entire atapi layer has gotten an overhaul. Lots of fixes to utililize the new features in subr_disk.c etc, and get rid of the last biots of softc arrays in the drivers, the only one left is atadevices which cannot easily go away (yet). Use our own malloc names, its a lot easier to track memory usage this way. General cleanup overall. Revision Changes Path 1.24 +191 -160 src/sys/dev/ata/ata-all.c 1.12 +21 -14 src/sys/dev/ata/ata-all.h 1.30 +57 -56 src/sys/dev/ata/ata-disk.c 1.13 +14 -5 src/sys/dev/ata/ata-disk.h 1.14 +174 -59 src/sys/dev/ata/ata-dma.c 1.18 +146 -169 src/sys/dev/ata/atapi-all.c 1.12 +25 -27 src/sys/dev/ata/atapi-all.h 1.21 +68 -92 src/sys/dev/ata/atapi-cd.c 1.21 +20 -20 src/sys/dev/ata/atapi-fd.c 1.6 +11 -11 src/sys/dev/ata/atapi-fd.h 1.18 +50 -60 src/sys/dev/ata/atapi-tape.c 1.8 +50 -50 src/sys/dev/ata/atapi-tape.h sos 1999/10/09 13:22:02 PDT Modified files: sys/conf options Log: Add the options for the ATA driver. Revision Changes Path 1.159 +5 -1 src/sys/conf/options >Hello, > >Seems now is the time to raise problems with ATA, so here goes. I have used the ATA driver >since its introduction into -current without problem until recently. A kernel from October >5 worked fine. Now, it no longer works using ATA, but works fine using the old WD drivers. >The console freezes after the dmesg and the keyboard is unresponsive. The ata info in >MYKERNEL is a direct cut and paste from GENERIC. The motherboard is an Intel Premiere/PCI >(Batman's Revenge). According to technical product summary, the primary IDE interface, on >which both my drives reside, is a PCTech RZ1000 on the PCI local bus. The secondary IDE >interface is a SMC 37C665 I/O controller on the ISA bus. Below is the relevant sections of >a verbose dmesg. If there's any additional info I can provide to help diagnose thisproblem, >please ask. > >Thanks, >Greg > >ata-pci0: at device 1.0 on pci0 >ata-pci0: Busmastering DMA not supported >ata0: iobase=0x01f0 altiobase=0x03f4 >ata0: mask=03 status0=50 status1=50 >ata0: mask=03 status0=50 status1=50 >ata0: devices = 0x3 >ata0 at 0x01f0 irq 0 on ata-pci0 > >ata-isa0: already registered as ata0 > >BIOS Geometries: > 0:020a1f3f 0..522=523 cylinders, 0..31=32 heads, 1..63=63 sectors > 1:026b3f3f 0..619=620 cylinders, 0..63=64 heads, 1..63=63 sectors > 0 accounted for >Device configuration finished. > device combination doesn't support shared irq0 > intr_connect(irq0) failed, result=-1 > >ad0: piomode=3 dmamode=1 udmamode=-1 cblid=0 >ad0: ATA-? disk at ata0 as master >ad0: 515MB (1056384 sectors), 1048 cyls, 16 heads, 63 S/T, 512 B/S >ad0: 16 secs/int, 1 depth queue, PIO >Creating DISK ad0 >Creating DISK wd0 >ad1: piomode=3 dmamode=1 udmamode=-1 cblid=0 >ad1: ATA-? disk at ata0 as slave >ad1: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S >ad1: 16 secs/int, 1 depth queue, PIO >Creating DISK ad1 >Creating DISK wd1 >Mounting root from ufs:wd0s1a >wd0s1: type 0xa5, start 63, end = 1056383, size 1056321 : OK >microuptime() went backwards (1.4342530 -> 1,047990) >start_init: trying /sbin/init >ad1s1: type 0xa5, start 63, end = 2503871, size 2503809 : OK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 1:37:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 5E75F1501C for ; Sat, 11 Dec 1999 01:37:40 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup1-59.iptelecom.net.ua [212.9.226.59]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA03936 for ; Sat, 11 Dec 1999 11:41:59 +0200 (EET) Message-ID: <385219FB.AFC3C7B8@altavista.net> Date: Sat, 11 Dec 1999 11:31:39 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Vibra 16 doesn't recognised anymore Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some time ago my soundcard (Vibra 16C), which worked just fine previously, stopped being recognised/attached. Following is relevant pieces of dmesg and pnpinfo: CTL0001: start dependant CTL0001: adding irq mask 0x20 CTL0001: adding dma mask 0x2 CTL0001: adding dma mask 0x20 CTL0001: adding io range 0x220-0x22f, size=0x10, align=0x1 CTL0001: adding io range 0x330-0x331, size=0x2, align=0x1 CTL0001: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0001: start dependant CTL0001: adding irq mask 0x6a0 CTL0001: adding dma mask 0xa CTL0001: adding dma mask 0xa0 CTL0001: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0001: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0001: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0001: start dependant CTL0001: adding irq mask 0x6a0 CTL0001: adding dma mask 0xa CTL0001: adding dma mask 0xa0 CTL0001: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0001: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0001: start dependant CTL0001: adding irq mask 0x6a0 CTL0001: adding dma mask 0xa CTL0001: adding dma mask 0xa0 CTL0001: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0001: start dependant CTL0001: adding irq mask 0x6a0 CTL0001: adding dma mask 0xa CTL0001: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0001: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0001: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0001: start dependant CTL0001: adding irq mask 0x6a0 CTL0001: adding dma mask 0xa CTL0001: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0001: end dependant [...] isa_probe_children: probing PnP devices unknown0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 unknown1: at port 0x200-0x207 on isa0 pnpinfo: Card assigned CSN #1 Vendor ID CTL0070 (0x70008c0e), Serial Number 0xffffffff PnP Version 1.0, Vendor Version 16 Device Description: Creative ViBRA16C PnP Logical Device ID: CTL0001 0x01008c0e #0 Device Description: Audio TAG Start DF Good Configuration IRQ: 5 - only one type (true/edge) DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 [16-bit addr] I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG End DF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 1:58:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id AEC3814FA4 for ; Sat, 11 Dec 1999 01:58:27 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: (from uucp@localhost) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with UUCP id SAA01078; Sat, 11 Dec 1999 18:58:25 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.9.3/3.7W) with ESMTP id SAA02622; Sat, 11 Dec 1999 18:55:38 +0900 (JST) Date: Sat, 11 Dec 1999 18:55:38 +0900 Message-ID: <14418.8090.86742.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: current@freebsd.org Subject: The secondary buffer in pcm channel for DSPs with small DMA buffers Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Carrots MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: multipart/mixed; boundary="Multipart_Sat_Dec_11_18:55:37_1999-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Sat_Dec_11_18:55:37_1999-1 Content-Type: text/plain; charset=US-ASCII My CS4614 has got only 4KB of the DMA buffer, frequently failing to play pcm blocks continuously. The following patch adds the secondary pcm channel buffers with the size independent from that of a DSP. The patch works quite well with mpg123 and x11amp. For those who has the similar problem could you please try that? --Multipart_Sat_Dec_11_18:55:37_1999-1 Content-Type: text/plain; type=patch; charset=US-ASCII Content-Disposition: attachment; filename="2ndbuffer.diff" Content-Transfer-Encoding: 7bit Index: channel.c =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/pcm/channel.c,v retrieving revision 1.9 diff -u -r1.9 channel.c --- channel.c 1999/12/05 19:09:12 1.9 +++ channel.c 1999/12/11 09:34:25 @@ -33,6 +33,13 @@ #define DMA_ALIGN_THRESHOLD 4 #define DMA_ALIGN_MASK (~(DMA_ALIGN_THRESHOLD - 1)) +/* + * This should be large enough to hold all pcm data between + * tsleeps in chn_{read,write} at the highest sample rate. + * (which is usually 48kHz * 16bit * stereo = 192000 bytes/sec) + */ +#define CHN_2NDBUFSIZE (12 * 1024) + #define ISA_DMA(b) (((b)->chan >= 0 && (b)->chan != 4 && (b)->chan < 8)) #define CANCHANGE(c) (!(c)->buffer.dl) @@ -131,9 +138,8 @@ } /* - * chn_dmadone() updates pointers and wakes up any process sleeping - * or waiting on a select(). - * Must be called at spltty(). + * chn_dmadone() updates pointers and wakes up any process waiting + * on a select(). Must be called at spltty(). */ static void chn_dmadone(pcm_channel *c) @@ -142,12 +148,23 @@ chn_dmaupdate(c); if (ISA_DMA(b)) chn_isadmabounce(c); /* sync bounce buffer */ - wakeup(b); b->int_count++; if (b->sel.si_pid && chn_polltrigger(c)) selwakeup(&b->sel); } /* + * chn_dmawakeup() wakes up any process sleeping. + * Must be called at spltty(). + */ +static void +chn_dmawakeup(pcm_channel *c) +{ + snd_dbuf *b = &c->buffer; + + wakeup(b); +} + +/* * chn_dmaupdate() tracks the status of a dma transfer, * updating pointers. It must be called at spltty(). * @@ -181,8 +198,9 @@ } /* - * Check channel for underflow occured, reset DMA buffer in case of - * underflow. It must be called at spltty(). + * Check channel for underflow occured. Reset DMA buffer in case of + * underflow, so that new data can go into the buffer. It must be + * called at spltty(). */ static void chn_checkunderflow(pcm_channel *c) @@ -201,6 +219,61 @@ } /* + * Feeds new data to the write dma buffer. Can be called in the bottom half. + * Must be called at spltty. + */ +static int +chn_wrfeed(pcm_channel *c) +{ + snd_dbuf *b = &c->buffer; + snd_dbuf *bs = &c->buffer2nd; + int a, l, lacc; + + /* ensure we always have a whole number of samples */ + a = (1 << c->align) - 1; + lacc = 0; + /* Don't allow write unaligned data */ + while (bs->rl > a && b->fl > a) { + /* ensure we always have a whole number of samples */ + l = min(min(bs->rl, bs->bufsize - bs->rp), min(b->fl, b->bufsize - b->fp)) & ~a; + if (l == 0) + return lacc; + bcopy(bs->buf + bs->rp, b->buf + b->fp, l); + bs->fl += l; + bs->rl -= l; + bs->rp = (bs->rp + l) % bs->bufsize; + b->rl += l; + b->fl -= l; + b->fp = (b->fp + l) % b->bufsize; + lacc += l; + } + + return lacc; +} + +/* Feeds new data to the secondary write buffer. */ +static int +chn_wrfeed2nd(pcm_channel *c, struct uio *buf) +{ + snd_dbuf *bs = &c->buffer2nd; + int l, w, wacc; + + /* ensure we always have a whole number of samples */ + wacc = 0; + while (buf->uio_resid > 0 && bs->fl > 0) { + l = min(bs->fl, bs->bufsize - bs->fp); + w = c->feeder->feed(c->feeder, c, bs->buf + bs->fp, l, buf); + if (w == 0) panic("no feed"); + bs->rl += w; + bs->fl -= w; + bs->fp = (bs->fp + w) % bs->bufsize; + wacc += w; + } + + return wacc; +} + +/* * Write interrupt routine. Can be called from other places (e.g. * to start a paused transfer), but with interrupts disabled. */ @@ -222,7 +295,14 @@ * needed when doing stereo and 16-bit. */ if (c->flags & CHN_F_MAPPED) start = c->flags & CHN_F_TRIGGERED; - else start = (b->rl >= DMA_ALIGN_THRESHOLD && !(c->flags & CHN_F_ABORTING)); + else { + /* Fill up the DMA buffer. */ + if (chn_wrfeed(c) > 0) { + chn_dmawakeup(c); + while(chn_wrfeed(c) > 0); + } + start = (b->rl >= DMA_ALIGN_THRESHOLD && !(c->flags & CHN_F_ABORTING)); + } if (start) { int l; chn_dmaupdate(c); @@ -237,13 +317,13 @@ /* Start DMA operation */ b->dl = c->blocksize ; /* record new transfer size */ chn_trigger(c, PCMTRIG_START); - } else if (b->dl != l) { + } + if (b->dl != l) /* * we are near to underflow condition, so to prevent * audio 'clicks' clear next 1.5*dl bytes */ chn_clearbuf(c, (b->dl*3)/2); - } } else { /* cannot start a new dma transfer */ DEB(printf("cannot start wr-dma flags 0x%08x rp %d rl %d\n", @@ -274,10 +354,9 @@ int chn_write(pcm_channel *c, struct uio *buf) { - int a, l, w, timeout, ret = 0, rc; + int ret = 0, timeout; long s; snd_dbuf *b = &c->buffer; - int threshold, maxthreshold, minthreshold; if (c->flags & CHN_F_WRITING) { /* This shouldn't happen and is actually silly @@ -286,57 +365,36 @@ tsleep(&s, PZERO, "pcmwrW", hz); return EBUSY; } - a = (1 << c->align) - 1; - maxthreshold = (b->dl / 4 + a) & ~a; - minthreshold = a; c->flags |= CHN_F_WRITING; + /* + * Fill up the secondary and DMA buffer. + * chn_wrfeed*() takes care of the alignment. + */ s = spltty(); chn_checkunderflow(c); - splx(s); - while ((buf->uio_resid + c->smegcnt) > minthreshold ) { /* Don't allow write unaligned data */ - threshold = min((buf->uio_resid + c->smegcnt), maxthreshold); - if (b->fl < threshold) { - if (c->flags & CHN_F_NBIO) { - ret = -1; - break; - } - timeout = (buf->uio_resid >= b->dl)? hz : 1; - rc = tsleep(b, PRIBIO | PCATCH, "pcmwr", timeout); - if (rc == 0 || rc == EWOULDBLOCK) { - s = spltty(); - chn_checkunderflow(c); - splx(s); - if (b->fl < minthreshold) continue; /* write only alligned chunk of data */ - } else { -#if 0 - if (ret == EINTR) chn_abort(c); -#endif - ret = rc; - break; - } - } - /* ensure we always have a whole number of samples */ - l = min(b->fl, b->bufsize - b->fp) & ~a; - if (l == 0) continue; - w = c->feeder->feed(c->feeder, c, b->buf + b->fp, l, buf); - KASSERT(w, ("chn_write: no feed")); - s = spltty(); - b->rl += w; - b->fl -= w; - b->fp = (b->fp + w) % b->bufsize; - splx(s); - DEB(if(1) printf("write %d bytes fp %d rl %d\n",w ,b->fp, b->rl)); - if (!b->dl) chn_stintr(c); - } - if ((ret == 0) && (buf->uio_resid > 0)) { - s = spltty(); - l = buf->uio_resid; - KASSERT( (c->smegcnt + l) < SMEGBUFSZ, ("resid overflow %d", l)); - uiomove(c->smegbuf + c->smegcnt, l, buf); - c->smegcnt += l; - splx(s); - } + while (chn_wrfeed2nd(c, buf) > 0 || chn_wrfeed(c) > 0); + /* Start playing if not yet. */ + if (b->rl && !b->dl) chn_wrintr(c); + if (!(c->flags & CHN_F_NBIO)) { + /* Wait until all samples are played in blocking mode. */ + while (buf->uio_resid > 0) { + splx(s); + timeout = (buf->uio_resid >= b->dl)? hz / 20 : 1; + ret = tsleep(b, PRIBIO | PCATCH, "pcmwr", timeout); + s = spltty(); +#if notdef + if (ret == EINTR) chn_abort(c); +#endif /* notdef */ + if (ret == EINTR || ret == ERESTART) break; + chn_checkunderflow(c); + /* Fill up the buffers with new pcm data. */ + while (chn_wrfeed2nd(c, buf) > 0 || chn_wrfeed(c) > 0); + /* Start playing if necessary. */ + if (b->rl && !b->dl) chn_wrintr(c); + } + } c->flags &= ~CHN_F_WRITING; + splx(s); return (ret > 0)? ret : 0; } @@ -370,6 +428,56 @@ */ +/* + * Feed new data from the read buffer. Can be called in the bottom half. + * Must be called at spltty. + */ +static int +chn_rdfeed(pcm_channel *c) +{ + snd_dbuf *b = &c->buffer; + snd_dbuf *bs = &c->buffer2nd; + int l, lacc; + + /* ensure we always have a whole number of samples */ + lacc = 0; + while (bs->fl >= DMA_ALIGN_THRESHOLD && b->rl >= DMA_ALIGN_THRESHOLD) { + l = min(min(bs->fl, bs->bufsize - bs->fp), min(b->rl, b->bufsize - b->rp)) & DMA_ALIGN_MASK; + bcopy(b->buf + b->rp, bs->buf + bs->fp, l); + bs->fl -= l; + bs->rl += l; + bs->fp = (bs->fp + l) % bs->bufsize; + b->rl -= l; + b->fl += l; + b->rp = (b->rp + l) % b->bufsize; + lacc += l; + } + + return lacc; +} + +/* Feeds new data from the secondary read buffer. */ +static int +chn_rdfeed2nd(pcm_channel *c, struct uio *buf) +{ + snd_dbuf *bs = &c->buffer2nd; + int l, w, wacc; + + /* ensure we always have a whole number of samples */ + wacc = 0; + while (buf->uio_resid > 0 && bs->rl > 0) { + l = min(bs->rl, bs->bufsize - bs->rp); + w = c->feeder->feed(c->feeder, c, bs->buf + bs->rp, l, buf); + if (w == 0) panic("no feed"); + bs->fl += w; + bs->rl -= w; + bs->rp = (bs->rp + w) % bs->bufsize; + wacc += w; + } + + return wacc; +} + /* read interrupt routine. Must be called with interrupts blocked. */ static void chn_rdintr(pcm_channel *c) @@ -383,7 +491,14 @@ b->dl, b->rp, b->rl, b->fp, b->fl)); /* Restart if have enough free space to absorb overruns */ if (c->flags & CHN_F_MAPPED) start = c->flags & CHN_F_TRIGGERED; - else start = (b->fl > 0x200 && !(c->flags & CHN_F_ABORTING)); + else { + /* Suck up the DMA buffer. */ + if (chn_rdfeed(c) > 0) { + chn_dmawakeup(c); + while (chn_rdfeed(c) > 0); + } + start = (b->fl > 0x200 && !(c->flags & CHN_F_ABORTING)); + } if (start) { int l = min(b->fl - 0x100, c->blocksize); if (c->flags & CHN_F_MAPPED) l = c->blocksize; @@ -431,7 +546,7 @@ int chn_read(pcm_channel *c, struct uio *buf) { - int w, l, timeout, limit, ret = 0; + int ret = 0, timeout, limit; long s; snd_dbuf *b = &c->buffer; @@ -441,33 +556,31 @@ return (EBUSY); } - if (!b->rl & !b->dl) chn_stintr(c); + s = spltty(); c->flags |= CHN_F_READING; limit = buf->uio_resid - c->blocksize; if (limit < 0) limit = 0; - while (buf->uio_resid > limit) { - s = spltty(); - chn_dmaupdate(c); - splx(s); - if (b->rl < DMA_ALIGN_THRESHOLD) { - if (c->flags & CHN_F_NBIO) break; - timeout = (buf->uio_resid - limit >= b->dl)? hz : 1; - ret = tsleep(b, PRIBIO | PCATCH, "pcmrd", timeout); + /* Start capturing if not yet. */ + if (!b->rl & !b->dl) chn_rdintr(c); + /* Suck up the DMA and secondary buffers. */ + while (chn_rdfeed(c) > 0 || chn_rdfeed2nd(c, buf) > 0); + if (!(c->flags & CHN_F_NBIO)) { + /* Wait until all samples are captured. */ + while (buf->uio_resid > 0) { + splx(s); + timeout = (buf->uio_resid - limit >= b->dl)? hz / 20 : 1; + ret = tsleep(b, PRIBIO | PCATCH, "pcmrd", timeout); + s = spltty(); if (ret == EINTR) chn_abort(c); if (ret == EINTR || ret == ERESTART) break; - ret = 0; - continue; + /* Start capturing if necessary. */ + if (!b->rl & !b->dl) chn_rdintr(c); + /* Suck up the DMA and secondary buffers. */ + while (chn_rdfeed(c) > 0 || chn_rdfeed2nd(c, buf) > 0); } - /* ensure we always have a whole number of samples */ - l = min(b->rl, b->bufsize - b->rp) & DMA_ALIGN_MASK; - w = c->feeder->feed(c->feeder, c, b->buf + b->rp, l, buf); - s = spltty(); - b->rl -= w; - b->fl += w; - b->rp = (b->rp + w) % b->bufsize; - splx(s); } c->flags &= ~CHN_F_READING; + splx(s); return ret; } @@ -534,6 +647,7 @@ chn_resetbuf(pcm_channel *c) { snd_dbuf *b = &c->buffer; + snd_dbuf *bs = &c->buffer2nd; c->smegcnt = 0; c->buffer.sample_size = 1; @@ -547,6 +661,9 @@ b->prev_int_count = b->int_count = 0; b->first_poll = 1; b->underflow=0; + bs->rp = bs->fp = 0; + bs->dl = bs->rl = 0; + bs->fl = bs->bufsize; } void @@ -631,6 +748,7 @@ long s; int missing = 0; snd_dbuf *b = &c->buffer; + snd_dbuf *bs = &c->buffer2nd; s = spltty(); if (b->dl) { @@ -639,7 +757,7 @@ chn_trigger(c, PCMTRIG_ABORT); chn_dmadone(c); } - missing = b->rl; + missing = b->rl + bs->rl; splx(s); return missing; } @@ -708,11 +826,18 @@ int chn_init(pcm_channel *c, void *devinfo, int dir) { + snd_dbuf *bs = &c->buffer2nd; + c->flags = 0; c->feeder = &feeder_root; c->buffer.chan = -1; c->devinfo = c->init(devinfo, &c->buffer, c, dir); chn_setdir(c, dir); + bs->bufsize = CHN_2NDBUFSIZE; + bs->buf = malloc(bs->bufsize, M_DEVBUF, M_NOWAIT); + bzero(bs->buf, bs->bufsize); + bs->rl = bs->rp = bs->fp = 0; + bs->fl = bs->bufsize; return 0; } Index: datatypes.h =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/pcm/datatypes.h,v retrieving revision 1.5 diff -u -r1.5 datatypes.h --- datatypes.h 1999/12/05 19:09:12 1.5 +++ datatypes.h 1999/12/11 09:34:25 @@ -127,6 +127,7 @@ u_int8_t smegbuf[SMEGBUFSZ]; u_int32_t smegcnt; void *devinfo; + snd_dbuf buffer2nd; }; #define SND_STATUSLEN 64 -- Seigo Tanimura --Multipart_Sat_Dec_11_18:55:37_1999-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 2:10:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatesrv.rz.unibw-muenchen.de (gatesrv.RZ.UniBw-Muenchen.de [137.193.10.21]) by hub.freebsd.org (Postfix) with ESMTP id E3ACD14E75 for ; Sat, 11 Dec 1999 02:10:27 -0800 (PST) (envelope-from didi@Xterminator.STUDFB.UniBw-Muenchen.de) Received: from XTerminator.StudFb.UniBw-Muenchen.De (Xterminator.STUDFB.UniBw-Muenchen.de [137.193.211.64]) by gatesrv.rz.unibw-muenchen.de (8.9.1b+Sun/8.9.3) with ESMTP id LAA00750; Sat, 11 Dec 1999 11:10:24 +0100 (MET) Received: from didi.STUDFB.UniBw-Muenchen.de (didi.STUDFB.UniBw-Muenchen.de [137.193.211.220]) by XTerminator.StudFb.UniBw-Muenchen.De (8.8.7/8.8.6) with SMTP id LAA02862; Sat, 11 Dec 1999 11:09:37 +0100 From: Dieter Rothacker To: Michael Kennett Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Date: Sat, 11 Dec 1999 11:10:20 +0100 Organization: Organized ? No way... Message-ID: References: <199912110553.VAA00494@mass.cdrom.com> <199912110621.OAA20899@laurasia.com.au> In-Reply-To: <199912110621.OAA20899@laurasia.com.au> X-Mailer: Forte Agent 1.6/32.661 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 11 Dec 1999 14:21:25 +0800 (WST), Michael Kennett wrote: >Note that wd1 is not present. This caused a mild hickup when rebooting the >new kernel, since the new ata controller assigned the labels ad0 and ad1 to >the drives. It was not possible to boot into multiuser mode without changing >the /etc/fstab file to rename the /dev/wd2* entries to /dev/ad1*. That was >easy to fix, however for a newbie it might cause problems. I mention it now, >since the upgrade from 3.x might need special handling of this case (?). You should use the kernel option "options ATA_STATIC_ID" for such cases. At least it works for me :-) -- Dieter Rothacker To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 2:15:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rexnet.net (mail.rexnet.net [206.246.149.3]) by hub.freebsd.org (Postfix) with ESMTP id 9DC1F14F8E for ; Sat, 11 Dec 1999 02:15:09 -0800 (PST) (envelope-from er787e@aol.com) Received: from 98AA04E2.ipt.aol.com by mail.rexnet.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8) id X8531CMD; Sat, 11 Dec 1999 05:14:07 -0500 Message-Id: <19991211101509.9DC1F14F8E@hub.freebsd.org> Date: Sat, 11 Dec 1999 02:15:09 -0800 (PST) From: er787e@aol.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG DATA From: er787e@aol.com To: Date: Sat, 11 Dec 1999 17:16:58 PST Subject: SKIN BECOMES DRAMATICALLY EVEN-TONED AND CLEAR... SKIN PROBLEMS? LET "DERMACURE" SOLVE THEM! Hello. We have good news for you. "DERMACURE" IS MADE FOR YOUR SKIN. If you suffer from any form of skin discolorations, such as dark marks, acne or pimple marks, scars, under-eye circles, razor bump marks, spots, freckles, uneven skin tone, shaving scars, shavers shadow, stretch-marks, dark areas of skin, or any other skin imperfections, you owe it to yourself to learn more about DERMACURE. Your skin can become dramatically even-toned and clear. "Dermacure" was first created in 1975. It has been thoroughly researched and perfected, has had many case studies conducted and has been improved many times over the past 24 years. This truly remarkable cosmetic treatment will eliminate your skin problems once and for all. "DERMACURE" IS MADE FOR YOUR SKIN. It's formula has been found by The U. S. Food and Drug Administration to be both safe and effective. DERMACURE is just as effective for males as it is for females, and is completely safe and gentle to sensitive skin. Our skin treatments are for all races, shades and ages of skin. If you wish to receive free additional information about "Dermacure", or If you have any questions, please email them to... improve40@usa.net We will answer you quickly. ALSO...if you have acne or pimple problems, or blackheads, whiteheads, or shaving bumps on your face or anywhere on your body, email us at improve40@usa.net for information about a remarkable acne and pimple Eliminator. ...If you suffer from stretch-marks, please let us know also. We have a stretch mark treatment made for this skin condition. Email us at improve40@usa.net ...Do you have psoriasis or eczema? We can help.. email us at improve40@usa.net We are an international company. You can be assured of fast, reliable delivery. Our elaborate shipping facilities and expert staff assure you of the highest quality service, whether you are here in the USA, or anywhere in the world. Respectfully and Sincerely, Mrs. Christine Yang, Mrs. Brenda Boykin and Mr. John Shigira P. S. It is never our intention to offend or annoy or disrespect anyone. If you do not appreciate receiving this message, please let us know by simply clicking REPLY and typing the word "REMOVE" IN THE SUBJECT LINE. (Not The Body) You will then be promptly and permanently removed from our list. We humbly apologize if you are in any way offended by receiving this email. " SKIN IS OUR BUSINESS...OUR ONLY BUSINESS". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 2:29: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 4A1CC14F66 for ; Sat, 11 Dec 1999 02:28:54 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id C18331CA0; Sat, 11 Dec 1999 18:28:42 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Dieter Rothacker Cc: Michael Kennett , freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: Message from Dieter Rothacker of "Sat, 11 Dec 1999 11:10:20 +0100." Date: Sat, 11 Dec 1999 18:28:42 +0800 From: Peter Wemm Message-Id: <19991211102842.C18331CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dieter Rothacker wrote: > On Sat, 11 Dec 1999 14:21:25 +0800 (WST), Michael Kennett wrote: > > >Note that wd1 is not present. This caused a mild hickup when rebooting the > >new kernel, since the new ata controller assigned the labels ad0 and ad1 to > >the drives. It was not possible to boot into multiuser mode without changin g > >the /etc/fstab file to rename the /dev/wd2* entries to /dev/ad1*. That was > >easy to fix, however for a newbie it might cause problems. I mention it now , > >since the upgrade from 3.x might need special handling of this case (?). > > You should use the kernel option > "options ATA_STATIC_ID" > for such cases. At least it works for me :-) I think this should only apply to the /dev/wd* compatability devices. ie: use the correct numbering for new installs onto ad*, but still support the old spread-out naming for wd*. This used to be more important as it required fiddling with $root_disk_unit, but the new mountroot code has relieved the pressure there. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 2:41:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatesrv.rz.unibw-muenchen.de (gatesrv.RZ.UniBw-Muenchen.de [137.193.10.21]) by hub.freebsd.org (Postfix) with ESMTP id ECE1914FA4 for ; Sat, 11 Dec 1999 02:41:26 -0800 (PST) (envelope-from didi@Xterminator.STUDFB.UniBw-Muenchen.de) Received: from XTerminator.StudFb.UniBw-Muenchen.De (Xterminator.STUDFB.UniBw-Muenchen.de [137.193.211.64]) by gatesrv.rz.unibw-muenchen.de (8.9.1b+Sun/8.9.3) with ESMTP id LAA00891; Sat, 11 Dec 1999 11:41:25 +0100 (MET) Received: from didi.STUDFB.UniBw-Muenchen.de (didi.STUDFB.UniBw-Muenchen.de [137.193.211.220]) by XTerminator.StudFb.UniBw-Muenchen.De (8.8.7/8.8.6) with SMTP id LAA04017; Sat, 11 Dec 1999 11:40:40 +0100 From: Dieter Rothacker To: Peter Wemm Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Date: Sat, 11 Dec 1999 11:41:22 +0100 Organization: Organized ? No way... Message-ID: References: of "Sat, 11 Dec 1999 11:10:20 +0100." <19991211102842.C18331CA0@overcee.netplex.com.au> In-Reply-To: <19991211102842.C18331CA0@overcee.netplex.com.au> X-Mailer: Forte Agent 1.6/32.661 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 11 Dec 1999 18:28:42 +0800, Peter Wemm wrote: >Dieter Rothacker wrote: >> >> You should use the kernel option >> "options ATA_STATIC_ID" >> for such cases. At least it works for me :-) > >I think this should only apply to the /dev/wd* compatability devices. ie: >use the correct numbering for new installs onto ad*, but still support the old >spread-out naming for wd*. This used to be more important as it required >fiddling with $root_disk_unit, but the new mountroot code has relieved the >pressure there. Why would you want to define "correct" numbering the non-spread-out numbering? Or did I misunderstand you? I have all my disks as master drives on the channels. Now, when I hook up another disk for backup or maintenance purposes, my numbering is messed up. With spread-out numbering I do not have to worry about anything... sounds more "correct" to me. -- Dieter Rothacker To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 2:49:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7874514F02 for ; Sat, 11 Dec 1999 02:49:51 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA81203; Sat, 11 Dec 1999 02:50:04 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Archie Cobbs Cc: abial@webgiro.com (Andrzej Bialecki), freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree In-reply-to: Your message of "Thu, 09 Dec 1999 15:59:35 PST." <199912092359.PAA76217@bubba.whistle.com> Date: Sat, 11 Dec 1999 02:50:03 -0800 Message-ID: <81199.944909403@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think the latter. In 'theory' there should be no discernable > difference between functionality from a KLD vs. the same functionality > compiled directly into the kernel. Only in theory, of course. :) As Andrzej has already pointed out, modules can also be loaded and unloaded, creating a sysctl space where things enter and leave dynamically. Let's say I'm somebody who creates a nifty little GUI sysctl editor for the CLI-challenged and, because it's time-consuming to build a form with fields for all the relevant sysctl variables, I take the obvious shortcut of parsing the output of `sysctl -A' once at startup time and then dealing with the individual field callbacks thereafter. On my "classic" system with a config-generated kernel, this works just fine and my GUI front-end for sysctl is eventually declared "useful enough" that I start handing it around. Then somebody who actually loads and unloads klds tries to use it, and results (needless to say) are no longer quite in alignment with expectations. :) Just a hypothetical scenario, of course, but I simply wanted to make the point that "no discernable difference" might be hard to achieve for certain values of discernment. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 4: 5:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 8CAE914EED for ; Sat, 11 Dec 1999 04:05:49 -0800 (PST) (envelope-from netchild@Leidinger.net) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id NAA14307590; Sat, 11 Dec 1999 13:05:41 +0100 (CET) Received: from Magelan.Leidinger.net (maxtnt-280.telip.uni-sb.de [134.96.71.151]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id NAA20480; Sat, 11 Dec 1999 13:05:39 +0100 (CET) Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id LAA01684; Sat, 11 Dec 1999 11:40:51 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <199912111040.LAA01684@Magelan.Leidinger.net> Date: Sat, 11 Dec 1999 11:40:48 +0100 (CET) From: Alexander Leidinger Subject: Re: Vibra 16 doesn't recognised anymore To: sobomax@altavista.net Cc: current@FreeBSD.ORG In-Reply-To: <385219FB.AFC3C7B8@altavista.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11 Dec, Maxim Sobolev wrote: > Some time ago my soundcard (Vibra 16C), which worked just fine > previously, stopped being recognised/attached. Following is relevant > pieces of dmesg and pnpinfo: last cvsup: Dec, 9. sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 pcm0: on sbc0 Same pnpinfo. Works well here. Relevant cut&paste from my kernel-config: ---snip--- device pcm0 device sbc0 ---snip--- Bye, Alexander. -- What we really need is a moment of science in public schools. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 4:19:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop-c.netway.at (pop-c.netway.at [195.96.0.132]) by hub.freebsd.org (Postfix) with ESMTP id 8B5D714CFF for ; Sat, 11 Dec 1999 04:19:33 -0800 (PST) (envelope-from Christian.Gusenbauer@netway.at) Received: from pop-d.netway.at (pop-d.netway.at [195.96.0.131]) by pop-c.netway.at (8.9.1/8.9.1) with ESMTP id NAA03587 for ; Sat, 11 Dec 1999 13:19:32 +0100 Received: from bones.my.domain (t2p115.at-732.netway.at [212.27.73.115]) by pop-d.netway.at (8.9.1/8.9.1) with SMTP id NAA08626 for ; Sat, 11 Dec 1999 13:19:30 +0100 From: Christian Gusenbauer Reply-To: Christian.Gusenbauer@netway.at To: current@FreeBSD.ORG Subject: Re: Current hangs when dump is run? Date: Sat, 11 Dec 1999 13:17:06 +0100 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain References: MIME-Version: 1.0 Message-Id: <99121113174301.00227@bones.my.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Since Nov 12th, I've been having this problem, too. Is there a solution/workaround available yet? I'm using a SCSI DAT drive and making backups using dump or tar works, but amanda still manages to hang the machine! Many thanks, Christian. AFAIR Taavi Talvik wrote on Sa , 20 Nov 1999: > On Fri, 19 Nov 1999, Poul-Henning Kamp wrote: > > > If you're using the ata driver, please remove the ad_sleep() call > > at the bottom of the adopen() in ata-disk.c and see if that > > helps you. > > Yes, i am using ata driver, but your suggestion didn't help. Still > same story. Crash dumps are available.. > > > >Current seems to hangs, when amanda tries to run dump. > > >This appeared approximately 2 weeks ago, and is present in > > >yesterdays current also. > > #0 0xc013daa4 in boot () > #1 0xc013de41 in panic () > #2 0xc011d739 in db_panic () > #3 0xc011d6d9 in db_command () > #4 0xc011d79e in db_command_loop () > #5 0xc011f82f in db_trap () > #6 0xc02011ef in kdb_trap () > #7 0xc020f434 in trap () > #8 0xc020144b in Debugger () > #9 0xc01fcb06 in scgetc () > #10 0xc01f8271 in sckbdevent () > #11 0xc01f1a8f in atkbd_intr () > #12 0xc021cd74 in atkbd_isa_intr () > #13 0xc0217c66 in splx () > #14 0xc0140a55 in tsleep () > #15 0xc0146889 in diskopen () > #16 0xc0170251 in spec_open () > #17 0xc017014d in spec_vnoperate () > #18 0xc01bb579 in ufs_vnoperatespec () > #19 0xc016a57c in vn_open () > #20 0xc01669dd in open () > #21 0xc020fd02 in syscall () > #22 0xc0201af6 in Xint0x80_syscall () > #23 0x804b91a in ?? () > #24 0x804b6b3 in ?? () > > [109:0] taavi@tt:/var/crash #ps -raxwu -M vmcore.5 -N kernel.5 > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > amanda 1365 99.0 0.0 628 0 ?? R 1Jan70 0:00.00 (dump) > root 1 0.0 0.0 516 0 ?? ILs 1Jan70 0:00.02 /sbin/init > -- > root 2 0.0 0.0 0 0 ?? RL 1Jan70 0:00.03 > (pagedaemon) > root 3 0.0 0.0 0 0 ?? DL 1Jan70 0:00.00 (vmdaemon) > root 4 0.0 0.0 0 0 ?? RL 1Jan70 0:00.03 (bufdaemon) > root 5 0.0 0.0 0 0 ?? RL 1Jan70 0:00.88 (syncer) > > > ----------------------------------------------------------- > Taavi Talvik | Internet: taavi@uninet.ee > Unineti Andmeside AS | phone: +372 6405150 > Ravala pst. 10 | fax: +372 6405151 > Tallinn 10143, Estonia | > > > > 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 Dec 11 5:29:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from gatesrv.rz.unibw-muenchen.de (gatesrv.RZ.UniBw-Muenchen.de [137.193.10.21]) by hub.freebsd.org (Postfix) with ESMTP id B81D314EB8 for ; Sat, 11 Dec 1999 05:29:41 -0800 (PST) (envelope-from didi@Xterminator.STUDFB.UniBw-Muenchen.de) Received: from XTerminator.StudFb.UniBw-Muenchen.De (Xterminator.STUDFB.UniBw-Muenchen.de [137.193.211.64]) by gatesrv.rz.unibw-muenchen.de (8.9.1b+Sun/8.9.3) with ESMTP id OAA02026; Sat, 11 Dec 1999 14:29:35 +0100 (MET) Received: from didi.STUDFB.UniBw-Muenchen.de (didi.STUDFB.UniBw-Muenchen.de [137.193.211.220]) by XTerminator.StudFb.UniBw-Muenchen.De (8.8.7/8.8.6) with SMTP id OAA10137; Sat, 11 Dec 1999 14:28:50 +0100 From: Dieter Rothacker To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: FYI: Benchmarked ATA driver Date: Sat, 11 Dec 1999 14:29:33 +0100 Organization: Organized ? No way... Message-ID: X-Mailer: Forte Agent 1.6/32.661 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, here I have my Bonnie++ 0.99d output: machine is a P233MMX, 128MB, Hotrod66 with IBM DJNA-352500. (One slice, one partition UFS) -- Version 0.99d ------Sequential Output------ --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- Machine MB K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP Unknown 256 6578 91 13484 71 3976 27 6539 92 13550 50 297.4 8 ------Sequential Create------ --------Random Create-------- -Create-- --Stat--- -Delete-- -Create-- --Stat--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 30 121 83 7781 67 1079 92 135 91 184 99 80 25 -- This really rocks, and the driver is perfectly stable. Very good work. -- Dieter Rothacker To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 5:57:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 2D0B014E7E for ; Sat, 11 Dec 1999 05:57:41 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id OAA77580 for current@FreeBSD.org; Sat, 11 Dec 1999 14:55:16 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Sat, 11 Dec 1999 14:55:10 +0100 From: Marcel Moolenaar Message-ID: <385257BE.761B4F92@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199912081721.SAA70567@freebsd.dk>, <2436.944893104@zippy.cdrom.com> Subject: Re: Audio support [was Re: HEADSUP: wd driver will be retired!] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > Actually, I'm sad to say that our shiny new sound system does *not* > work for some of the most popular audio chipsets on the market today > (where the older "luigi" sound system did support them) and this is a > matter of significant concern to some folks, myself included. The recent commits made existing support even worse. Yes, I'm talking about the ESS1888. It's more dead than before. I'll have to make the noise myself these days, and I can tell you it's no opera :-) In short: Gimme patches! I'll be happy to test and, in a spare hour, can even do some trial and error on my own. I'm not going to beg... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 6: 6: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs0.catv.ne.jp (cs0.catv.ne.jp [202.232.171.20]) by hub.freebsd.org (Postfix) with ESMTP id 7C676150D1 for ; Sat, 11 Dec 1999 06:05:55 -0800 (PST) (envelope-from nyan@dd.catv.ne.jp) Received: from localhost by cs0.catv.ne.jp (8.9.1/3.7W) id XAA01564; Sat, 11 Dec 1999 23:04:57 +0900 (JST) To: current@FreeBSD.org Subject: make world is failed on pc98 From: Takahashi Yoshihiro X-Mailer: Mew version 1.94 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991211230552P.nyan@dd.catv.ne.jp> Date: Sat, 11 Dec 1999 23:05:52 +0900 (JST) X-Dispatcher: imput version 990905(IM130) Lines: 37 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The boot2 for pc98 (sys/boot/pc98/boot2) is a.out program. So, several tools for a.out are needed to make boot2. I make the patch to fix this. Is there any problem? --- Makefile.inc1 1999/12/10 16:13:41 1.102 +++ Makefile.inc1 1999/12/11 10:01:21 @@ -143,6 +143,10 @@ USRDIRS= usr/bin usr/lib/compat/aout usr/games usr/libdata/ldscripts \ usr/libexec/${OBJFORMAT} usr/share/misc +.if ${MACHINE} == "pc98" && ${OBJFORMAT} == "elf" +USRDIRS+= usr/libexec/aout +.endif + INCDIRS= arpa g++/std objc protocols readline rpc rpcsvc security ss # @@ -330,9 +334,13 @@ _strfile= games/fortune/strfile .endif +.if ${MACHINE} == "pc98" && ${OBJFORMAT} == "elf" +_aout_tools= usr.bin/size usr.bin/strip gnu/usr.bin/as gnu/usr.bin/ld +.endif + tools:: .for _tool in ${_strfile} gnu/usr.bin/binutils usr.bin/objformat \ - usr.bin/yacc gnu/usr.bin/bison gnu/usr.bin/cc + usr.bin/yacc gnu/usr.bin/bison gnu/usr.bin/cc ${_aout_tools} cd ${.CURDIR}/${_tool}; \ ${MAKE} obj; \ ${MAKE} depend; \ --- Takahashi Yoshihiro / nyan@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 6:14:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from p.wl.vg (209-9-69-194.sdsl.cais.net [209.9.69.194]) by hub.freebsd.org (Postfix) with ESMTP id 941E414EB8 for ; Sat, 11 Dec 1999 06:14:25 -0800 (PST) (envelope-from patrick@p.wl.vg) Received: (from patrick@localhost) by p.wl.vg (8.9.3/8.9.3) id JAA03757; Sat, 11 Dec 1999 09:13:57 -0500 (EST) (envelope-from patrick) Message-Id: <199912111413.JAA03757@p.wl.vg> Date: Sat, 11 Dec 1999 09:13:57 -0500 (EST) From: patrick@whetstonelogic.com Subject: Re: Install of 4.0-19991208-CURRENT To: mike@laurasia.com.au Cc: freebsd-current@freebsd.org In-Reply-To: <199912110722.PAA08605@laurasia.com.au> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11 Dec, Michael Kennett wrote: > I've just tried installing the last current snapshot (4.0-19991208-CURRENT) > onto an IBM laptop (365, type 2625-2E9) with a Xircom networking card > (CE3B-100BTX). It failed -- the pccard was not recognized. > > I mention this because the floppies/pccard/README.TXT mentioned the systems > that have been tested. Did you rebuild the kernel with pccard support enabled? You didn't mention in the message. Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 6:23: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with SMTP id 50F9F14E65 for ; Sat, 11 Dec 1999 06:22:53 -0800 (PST) (envelope-from matt@camtech.net.au) Received: from dialup-ad-17-64.camtech.net.au ([203.55.241.192]) by camtech.net.au ; Sun, 12 Dec 1999 00:52:42 +1030 Date: Sun, 12 Dec 1999 00:53:18 +1030 (CST) From: Matthew Thyer X-Sender: matt@localhost Reply-To: thyerm@camtech.net.au To: Greg Childers Cc: sos@freebsd.dk, current@freebsd.org Subject: Re: ATA problem In-Reply-To: <4.2.0.58.19991211021308.00955600@pop.uky.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 Does your /etc/fstab have character devices listed or block devices ? If it has character devices (aka raw devices), change them to block (remove the 'r' at the front) e.g. change: "/dev/rad0s2a" to "/dev/ad0s2a". It seems to be only necessary for the root filesystem. Some people (like me) changed their fstabs to raw devices after a message from Poul Henning-Kamp (I hope thats the spelling) saying that it should be possible to use only raw devices throughout the system. This worked for a while but then other changes made it unable to boot. On Sat, 11 Dec 1999, Greg Childers wrote: > Hi, > > With a bit of investigating, I've found the problem described in my previous email quoted at > the end of this message started with the commits listed below. A kernel built using > sources just before these commits works fine, whereas a kernel build just after freezes > after the line > > Mounting root from ufs:wd0s1a > > Hope this helps. If you need any more info, just ask. > > Greg > > > sos 1999/10/09 12:57:15 PDT > > Modified files: > sys/dev/ata ata-all.c ata-all.h ata-disk.c ata-disk.h > ata-dma.c atapi-all.c atapi-all.h > atapi-cd.c atapi-fd.c atapi-fd.h > atapi-tape.c atapi-tape.h > Log: > Add support for the HPT366 chip, this is used on the Abit boards and > their HotRod controller and on SIIG PCI ultra DMA controller. These > changes also made lots of the Promise code go away, its all much more > generic this way. > > Get rid of atapi_immed_cmd, instead use the queue to move atapi commands > from interrupt context if nessesary, the entire atapi layer has > gotten an overhaul. > > Lots of fixes to utililize the new features in subr_disk.c etc, and > get rid of the last biots of softc arrays in the drivers, the > only one left is atadevices which cannot easily go away (yet). > > Use our own malloc names, its a lot easier to track memory usage this way. > > General cleanup overall. > > Revision Changes Path > 1.24 +191 -160 src/sys/dev/ata/ata-all.c > 1.12 +21 -14 src/sys/dev/ata/ata-all.h > 1.30 +57 -56 src/sys/dev/ata/ata-disk.c > 1.13 +14 -5 src/sys/dev/ata/ata-disk.h > 1.14 +174 -59 src/sys/dev/ata/ata-dma.c > 1.18 +146 -169 src/sys/dev/ata/atapi-all.c > 1.12 +25 -27 src/sys/dev/ata/atapi-all.h > 1.21 +68 -92 src/sys/dev/ata/atapi-cd.c > 1.21 +20 -20 src/sys/dev/ata/atapi-fd.c > 1.6 +11 -11 src/sys/dev/ata/atapi-fd.h > 1.18 +50 -60 src/sys/dev/ata/atapi-tape.c > 1.8 +50 -50 src/sys/dev/ata/atapi-tape.h > > > > sos 1999/10/09 13:22:02 PDT > > Modified files: > sys/conf options > Log: > Add the options for the ATA driver. > > Revision Changes Path > 1.159 +5 -1 src/sys/conf/options > > > > >Hello, > > > >Seems now is the time to raise problems with ATA, so here goes. I have used the ATA driver > >since its introduction into -current without problem until recently. A kernel from October > >5 worked fine. Now, it no longer works using ATA, but works fine using the old WD drivers. > >The console freezes after the dmesg and the keyboard is unresponsive. The ata info in > >MYKERNEL is a direct cut and paste from GENERIC. The motherboard is an Intel Premiere/PCI > >(Batman's Revenge). According to technical product summary, the primary IDE interface, on > >which both my drives reside, is a PCTech RZ1000 on the PCI local bus. The secondary IDE > >interface is a SMC 37C665 I/O controller on the ISA bus. Below is the relevant sections of > >a verbose dmesg. If there's any additional info I can provide to help diagnose thisproblem, > >please ask. > > > >Thanks, > >Greg > > > >ata-pci0: at device 1.0 on pci0 > >ata-pci0: Busmastering DMA not supported > >ata0: iobase=0x01f0 altiobase=0x03f4 > >ata0: mask=03 status0=50 status1=50 > >ata0: mask=03 status0=50 status1=50 > >ata0: devices = 0x3 > >ata0 at 0x01f0 irq 0 on ata-pci0 > > > >ata-isa0: already registered as ata0 > > > >BIOS Geometries: > > 0:020a1f3f 0..522=523 cylinders, 0..31=32 heads, 1..63=63 sectors > > 1:026b3f3f 0..619=620 cylinders, 0..63=64 heads, 1..63=63 sectors > > 0 accounted for > >Device configuration finished. > > device combination doesn't support shared irq0 > > intr_connect(irq0) failed, result=-1 > > > >ad0: piomode=3 dmamode=1 udmamode=-1 cblid=0 > >ad0: ATA-? disk at ata0 as master > >ad0: 515MB (1056384 sectors), 1048 cyls, 16 heads, 63 S/T, 512 B/S > >ad0: 16 secs/int, 1 depth queue, PIO > >Creating DISK ad0 > >Creating DISK wd0 > >ad1: piomode=3 dmamode=1 udmamode=-1 cblid=0 > >ad1: ATA-? disk at ata0 as slave > >ad1: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S > >ad1: 16 secs/int, 1 depth queue, PIO > >Creating DISK ad1 > >Creating DISK wd1 > >Mounting root from ufs:wd0s1a > >wd0s1: type 0xa5, start 63, end = 1056383, size 1056321 : OK > >microuptime() went backwards (1.4342530 -> 1,047990) > >start_init: trying /sbin/init > >ad1s1: type 0xa5, start 63, end = 2503871, size 2503809 : OK > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 6:46:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A78BA14D66; Sat, 11 Dec 1999 06:46:12 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id PAA13601; Sat, 11 Dec 1999 15:45:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Stephen McKay Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sat, 11 Dec 1999 15:03:19 +1000." <199912110503.PAA01950@nymph.detir.qld.gov.au> Date: Sat, 11 Dec 1999 15:45:54 +0100 Message-ID: <13599.944923554@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912110503.PAA01950@nymph.detir.qld.gov.au>, Stephen McKay writes : >On Friday, 10th December 1999, Mike Smith wrote: > >>The same mentality that made the CAM cutover a "debacle" is making the >>ata cutover a "debacle". First of all, "core" is not really involved in this per se. >It might be that these things have to be >predicted by -core and handled "touchy feely" like: > >core: What if we do this ? >public: Um, sounds scary. When will you do it? Will I lose anything? >core: We think a month from now, and you will lose support for and . >public: We don't use and any more, so fine. So far, whenever this has been tried, the public reponse have been: public: We don't want to change anything, ever! It's so hard! You must support all my hardware for ever and ever! >instead of the current (caricatured for emphasis): > >core: We will do soon. Probably today. >public: Oh my God! >core: It's for your own good. You always complain and make it difficult! >public: We don't want to change anything, ever! It's so hard! You must > support all my hardware for ever and ever! I'm sure you will notice the similarity. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 6:50:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from homer.mkintl.com (242671hfc111.tampabay.rr.com [24.26.71.111]) by hub.freebsd.org (Postfix) with ESMTP id 2F85514A0B for ; Sat, 11 Dec 1999 06:50:01 -0800 (PST) (envelope-from joeo@homer.mkintl.com) Received: from localhost (joeo@localhost) by homer.mkintl.com (8.9.3/8.9.3) with ESMTP id JAA13797 for ; Sat, 11 Dec 1999 09:49:57 -0500 Date: Sat, 11 Dec 1999 09:49:57 -0500 (EST) From: To: freebsd-current@freebsd.org Subject: Errors from the ata disk driver Message-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 striped vinum partition that is occasionally going stale when I get spurrious errors from the ata driver. I can setstate the drives and the volume back up and an fsck of the partition doesn't show any obvious corruption. What do these errors indicate? ad5: status=51 error=84 ad_interrupt: hard error vinum0.p0.s3: fatal read I/O error ad6: status=51 error=84 ad_interrupt: hard error vinum0.p0.s4: fatal read I/O error These drives are hanging off this controller; ata-pci1: irq 9 at device 9.0 on pci0 ata-pci1: Busmastering DMA supported Thanks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 7:27:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 2D30514F60 for ; Sat, 11 Dec 1999 07:27:41 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id QAA93287 for current@FreeBSD.org; Sat, 11 Dec 1999 16:00:18 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Sat, 11 Dec 1999 16:00:16 +0100 From: Marcel Moolenaar Message-ID: <38526700.70C5CBF@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19991211230552P.nyan@dd.catv.ne.jp> Subject: Re: make world is failed on pc98 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Takahashi Yoshihiro wrote: > +.if ${MACHINE} == "pc98" && ${OBJFORMAT} == "elf" > +USRDIRS+= usr/libexec/aout > +.endif I don't think you need to test for OBJFORMAT. Also, include MACHINE_ARCH in case of cross-building. eg: .if ${MACHINE_ARCH} == "i386" && ${MACHINE} == "pc98" > +.if ${MACHINE} == "pc98" && ${OBJFORMAT} == "elf" > +_aout_tools= usr.bin/size usr.bin/strip gnu/usr.bin/as gnu/usr.bin/ld > +.endif Same here. > .for _tool in ${_strfile} gnu/usr.bin/binutils usr.bin/objformat \ > - usr.bin/yacc gnu/usr.bin/bison gnu/usr.bin/cc > + usr.bin/yacc gnu/usr.bin/bison gnu/usr.bin/cc ${_aout_tools} Don't build anything after cc has been built, because cc will be a cross-compiler when cross-building. Try putting it as early as possible. Other than that: Go ahead! BTW: Is there a special reason to have boot2 in aout? -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 8:11:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 72EC814F7F for ; Sat, 11 Dec 1999 08:11:18 -0800 (PST) (envelope-from vallo@solaris.matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id EE4EA2CE4F; Sat, 11 Dec 1999 18:11:11 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id AB4B5EC; Sat, 11 Dec 1999 18:11:15 +0200 (EET) Date: Sat, 11 Dec 1999 18:11:15 +0200 From: Vallo Kallaste To: Soren Schmidt Cc: Jean Louis Ntakpe , current@FreeBSD.ORG Subject: ata: lost disk contact errors [was: Re: HEADSUP: wd driver will be retired!] Message-ID: <19991211181115.A36357@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <199912101914.UAA02864@ishtar.ffab.tide.ti.com> <199912102031.VAA10133@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199912102031.VAA10133@freebsd.dk>; from Soren Schmidt on Fri, Dec 10, 1999 at 09:31:57PM +0100 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 10, 1999 at 09:31:57PM +0100, Soren Schmidt wrote: > > I've connected the disk back to the UDM33 controller and it works > > fine. Now I get the message twice a day: > > > > ata0-master: ad_timeout: lost disk contact - resetting > > ata0: resetting devices .. done > > > > I've applied the patches until 4133 and will try to reconnect > > the disk to the UDMA66 controller. > > > > Am I missing something about UDMA33/UDMA66 or specifically about > > the HighPoint controller ? > > Hmm, I have one in my development machine, so it takes a fair bit > of beating, I haven't seen any of these problems. Could you mail > me a dmesg, preferably from a verbose boot. I'm getting the "lost disk contact" messages every now and then, but only on our mp3 machine with PIIX3 controller and IBM UDMA/66 disk. It's an PPro machine with Intel mobo. Can it be related to newer IBM disks? Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Nov 25 13:23:02 EET 1999 root@myhakas.matti.ee:/usr/src/sys/compile/Muzz Timecounter "i8254" frequency 1193200 Hz Timecounter "TSC" frequency 166195509 Hz CPU: Pentium Pro (166.20-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x612 Stepping = 2 Features=0xf9ff real memory = 33554432 (32768K bytes) avail memory = 29683712 (28988K bytes) Preloaded elf kernel "kernel" at 0xc02bf000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02bf09c. module_register_init: MOD_LOAD (vesa, c02194a4, 0) error 6 Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 xl0: <3Com 3c905-TX Fast Etherlink XL> irq 10 at device 11.0 on pci0 xl0: Ethernet address: 00:60:08:05:58:14 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vga-pci0: at device 17.0 on pci0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <8 virtual consoles, flags=0x200> fdc0: direction bit not set fdc0: cmd 3 failed at out byte 1 of 3 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 gusc0: at port 0x220-0x22f,0x320-0x327,0x32c-0x32f irq 11 drq 5,7 on isa0 pcm0: on gusc0 unknown0: on isa0 unknown1: on isa0 unknown2: on isa0 unknown3: on isa0 ad0: ATA-4 disk at ata0 as master ad0: 35772MB (73261440 sectors), 7144 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 31 depth queue, DMA acd0: <685A/8.4D> CDROM drive at ata1 as master acd0: read 1171KB/s (1171KB/s), 120KB buffer, PIO acd0: supported read types: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/wd0s1a WARNING: / was not properly dismounted xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 120 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 180 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 240 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 300 bytes ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done ata0-master: ad_timeout: lost disk contact - resetting ata0: resetting devices .. done -- 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 Sat Dec 11 8:11:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 6945B1511F for ; Sat, 11 Dec 1999 08:11:36 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id LAA00349 for ; Sat, 11 Dec 1999 11:11:31 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Sat, 11 Dec 1999 11:11:30 -0500 (EST) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: the PnP stuff Message-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 would like to add an option to revert back to the old behavior of not using the PnP stuff to probe the ISA bus. My reason for this is that my soundcard (SB ViBRA16X) and Modem (Diamond SupraExpress 56i) both were detected and worked fine (the SB with voxware drivers, the modem with the sio driver) before the switch to the PnP stuff, and the controller being taken out. My computer won't even boot with the PnP stuff unless I turn PnP OS to on in bios. I want PnP OS to be off when I boot so that the soundcard and the Modem will be usable. I can try to make the necessary changes to the kernel myself by adding an option like options PNPOFF or something like that and making it revert back to the old behavior before controller pnp0 was taken out of the kernel, and made the default behavior. I say I will try because this will be my first time doing such a thing. If anyone else is having the same problems, let me know, reply to me directly because the address I have the mailing list mail going to is temporarily down. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 8:28:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from darkstar.qx.net (darkstar.qx.net [208.235.88.101]) by hub.freebsd.org (Postfix) with ESMTP id 6531D14FDA for ; Sat, 11 Dec 1999 08:28:26 -0800 (PST) (envelope-from gchil0@pop.uky.edu) Received: from mail.qx.net (mail.qx.net [208.235.88.10]) by darkstar.qx.net (8.8.7/8.8.7) with ESMTP id LAA10620 for ; Sat, 11 Dec 1999 11:28:24 -0500 Received: from k7 ([208.200.111.92]) by mail.qx.net (Netscape Messaging Server 3.6) with ESMTP id AAADA7; Sat, 11 Dec 1999 11:31:13 -0500 Message-Id: <4.2.0.58.19991211111913.0095d100@pop.uky.edu> X-Sender: gchil0@pop.uky.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sat, 11 Dec 1999 11:24:24 -0500 To: thyerm@camtech.net.au From: Greg Childers Subject: Re: ATA problem Cc: sos@freebsd.dk, current@freebsd.org In-Reply-To: References: <4.2.0.58.19991211021308.00955600@pop.uky.edu> 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 my fstab: # Device Mountpoint FStype Options Dump Pass# /dev/ad0s1b none swap sw 0 0 /dev/ad1s1b none swap sw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad1s1e /usr ufs rw 2 2 /dev/ad0s1f /usr/obj ufs rw 2 2 /dev/ad0s1e /var ufs rw 2 2 proc /proc procfs rw 0 0 The lockup also occurs if I boot into single user mode. The message for a shell or for sh never comes up. At 12:53 AM 12/12/99 +1030, Matthew Thyer wrote: >Does your /etc/fstab have character devices listed or block devices ? > >If it has character devices (aka raw devices), change them to block >(remove the 'r' at the front) e.g. change: "/dev/rad0s2a" to >"/dev/ad0s2a". > >It seems to be only necessary for the root filesystem. > >Some people (like me) changed their fstabs to raw devices after a >message from Poul Henning-Kamp (I hope thats the spelling) saying that >it should be possible to use only raw devices throughout the system. >This worked for a while but then other changes made it unable to boot. > >On Sat, 11 Dec 1999, Greg Childers wrote: > > > Hi, > > > > With a bit of investigating, I've found the problem described in my previous email quoted at > > the end of this message started with the commits listed below. A kernel built using > > sources just before these commits works fine, whereas a kernel build just after freezes > > after the line > > > > Mounting root from ufs:wd0s1a > > > > Hope this helps. If you need any more info, just ask. > > > > Greg > > > > > > sos 1999/10/09 12:57:15 PDT > > > > Modified files: > > sys/dev/ata ata-all.c ata-all.h ata-disk.c ata-disk.h > > ata-dma.c atapi-all.c atapi-all.h > > atapi-cd.c atapi-fd.c atapi-fd.h > > atapi-tape.c atapi-tape.h > > Log: > > Add support for the HPT366 chip, this is used on the Abit boards and > > their HotRod controller and on SIIG PCI ultra DMA controller. These > > changes also made lots of the Promise code go away, its all much more > > generic this way. > > > > Get rid of atapi_immed_cmd, instead use the queue to move atapi commands > > from interrupt context if nessesary, the entire atapi layer has > > gotten an overhaul. > > > > Lots of fixes to utililize the new features in subr_disk.c etc, and > > get rid of the last biots of softc arrays in the drivers, the > > only one left is atadevices which cannot easily go away (yet). > > > > Use our own malloc names, its a lot easier to track memory usage this way. > > > > General cleanup overall. > > > > Revision Changes Path > > 1.24 +191 -160 src/sys/dev/ata/ata-all.c > > 1.12 +21 -14 src/sys/dev/ata/ata-all.h > > 1.30 +57 -56 src/sys/dev/ata/ata-disk.c > > 1.13 +14 -5 src/sys/dev/ata/ata-disk.h > > 1.14 +174 -59 src/sys/dev/ata/ata-dma.c > > 1.18 +146 -169 src/sys/dev/ata/atapi-all.c > > 1.12 +25 -27 src/sys/dev/ata/atapi-all.h > > 1.21 +68 -92 src/sys/dev/ata/atapi-cd.c > > 1.21 +20 -20 src/sys/dev/ata/atapi-fd.c > > 1.6 +11 -11 src/sys/dev/ata/atapi-fd.h > > 1.18 +50 -60 src/sys/dev/ata/atapi-tape.c > > 1.8 +50 -50 src/sys/dev/ata/atapi-tape.h > > > > > > > > sos 1999/10/09 13:22:02 PDT > > > > Modified files: > > sys/conf options > > Log: > > Add the options for the ATA driver. > > > > Revision Changes Path > > 1.159 +5 -1 src/sys/conf/options > > > > > > > > >Hello, > > > > > >Seems now is the time to raise problems with ATA, so here goes. I have used the ATA driver > > >since its introduction into -current without problem until recently. A kernel from October > > >5 worked fine. Now, it no longer works using ATA, but works fine using the old WD drivers. > > >The console freezes after the dmesg and the keyboard is unresponsive. The ata info in > > >MYKERNEL is a direct cut and paste from GENERIC. The motherboard is an Intel Premiere/PCI > > >(Batman's Revenge). According to technical product summary, the primary IDE interface, on > > >which both my drives reside, is a PCTech RZ1000 on the PCI local bus. The secondary IDE > > >interface is a SMC 37C665 I/O controller on the ISA bus. Below is the relevant sections of > > >a verbose dmesg. If there's any additional info I can provide to help diagnose thisproblem, > > >please ask. > > > > > >Thanks, > > >Greg > > > > > >ata-pci0: at device 1.0 on pci0 > > >ata-pci0: Busmastering DMA not supported > > >ata0: iobase=0x01f0 altiobase=0x03f4 > > >ata0: mask=03 status0=50 status1=50 > > >ata0: mask=03 status0=50 status1=50 > > >ata0: devices = 0x3 > > >ata0 at 0x01f0 irq 0 on ata-pci0 > > > > > >ata-isa0: already registered as ata0 > > > > > >BIOS Geometries: > > > 0:020a1f3f 0..522=523 cylinders, 0..31=32 heads, 1..63=63 sectors > > > 1:026b3f3f 0..619=620 cylinders, 0..63=64 heads, 1..63=63 sectors > > > 0 accounted for > > >Device configuration finished. > > > device combination doesn't support shared irq0 > > > intr_connect(irq0) failed, result=-1 > > > > > >ad0: piomode=3 dmamode=1 udmamode=-1 cblid=0 > > >ad0: ATA-? disk at ata0 as master > > >ad0: 515MB (1056384 sectors), 1048 cyls, 16 heads, 63 S/T, 512 B/S > > >ad0: 16 secs/int, 1 depth queue, PIO > > >Creating DISK ad0 > > >Creating DISK wd0 > > >ad1: piomode=3 dmamode=1 udmamode=-1 cblid=0 > > >ad1: ATA-? disk at ata0 as slave > > >ad1: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S > > >ad1: 16 secs/int, 1 depth queue, PIO > > >Creating DISK ad1 > > >Creating DISK wd1 > > >Mounting root from ufs:wd0s1a > > >wd0s1: type 0xa5, start 63, end = 1056383, size 1056321 : OK > > >microuptime() went backwards (1.4342530 -> 1,047990) > > >start_init: trying /sbin/init > > >ad1s1: type 0xa5, start 63, end = 2503871, size 2503809 : OK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 8:31:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id BE3C615000; Sat, 11 Dec 1999 08:31:32 -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.9.3/8.9.3) with SMTP id JAA07110; Sat, 11 Dec 1999 09:31:31 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA25635; Sat, 11 Dec 1999 09:31:30 -0700 Date: Sat, 11 Dec 1999 09:31:30 -0700 Message-Id: <199912111631.JAA25635@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: nate@mt.sri.com (Nate Williams), current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912110154.RAA04860@mass.cdrom.com> References: <199912102123.OAA21691@mt.sri.com> <199912110154.RAA04860@mass.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> If half as much energy was spent adding the missing bits of >>> functionality to the new systems as people have been spending >>> complaining it then we'd be there ages ago. >> >> Not true. It doesn't take a disk expert to complain about a policy, >> but it takes one to fix bugs/add features to the existing driver. :) >> :) :) > > That's ignoring the fact that it takes less energy to become enough of a > "disk expert" to do something useful than it takes to engage in the sort > of protracted whining that we're seeing. That's simply not true. It's taken me less than 5 minutes total to respond to these silly emails, and it'd take me at least a week to get familiar enough with the code to do anything useful, and another 3-4 weeks to get it past the maintainer's filters (validly so), because my one week of understanding would be missing alot of lessons learned that I'm not aware of. However, it appears to be the mindset of the developers that the problems that people complain about are either trivially easy to solve that it's expected that unless they have a solution to it, they're stupid. Or, the problem is so hard that they want people not to complain unless they have a solution for it, since expecting *THE DEVELOPERS* to solve such a protracted and complex set of problems is ludicrous. You must be an idiot to not understand this, or a complete boob for expecting a member of a volunteer project to spend his free time working on it. In other words, and opion shared that is contrary to the developers implies stupidity on the part of the user. It's a no-win situation for everyone involved. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 8:52:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from icc.ru (ccsoan.irkutsk.su [195.206.40.177]) by hub.freebsd.org (Postfix) with ESMTP id 9209114E15 for ; Sat, 11 Dec 1999 08:52:46 -0800 (PST) (envelope-from olegd@esrr.irk.ru) Received: from esrr.irk.ru (vsgd.irk.ru [195.206.40.38] (may be forged)) by icc.ru (8.9.3/8.9.3) with SMTP id AAA12637 for ; Sun, 12 Dec 1999 00:50:35 +0800 (IRKT) X-Envelope-To: Date: Sat, 11 Dec 1999 12:59:24 +0300 From: Oleg Dobrokhotov X-Mailer: The Bat! (v1.36) S/N F29DEE5D / Educational Reply-To: Oleg Dobrokhotov X-Priority: 3 (Normal) Message-ID: <17541.991211@esrr.irk.ru> To: freebsd-current@freebsd.org Subject: make release broken Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ALL, After Making hierarchy, in Installig everything >install -C -o root -g wheel -m 444 /usr/src/include/osreldate.h >/usr/SNAP/include >install: osreldate.h - no such file or directory... >***Error code 71 >Stop in /usr/src/include >Error code 1 -- Best regards, Oleg mailto:olegd@esrr.irk.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 9: 2:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [36.118.0.70]) by hub.freebsd.org (Postfix) with ESMTP id 3AEAA14FA3 for ; Sat, 11 Dec 1999 09:02:32 -0800 (PST) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.9.3/8.9.1) id JAA34096; Sat, 11 Dec 1999 09:00:52 -0800 (PST) Date: Sat, 11 Dec 1999 09:00:52 -0800 (PST) From: Bob Vaughan Message-Id: <199912111700.JAA34096@tantivy.stanford.edu> To: nate@mt.sri.com, phk@critter.freebsd.dk Subject: Re: HEADSUP: wd driver will be retired! Cc: current@FreeBSD.ORG In-Reply-To: <6332.944849983@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Subject: Re: HEADSUP: wd driver will be retired! > Date: Fri, 10 Dec 1999 19:19:43 +0100 > From: Poul-Henning Kamp > > > Maybe we should put a special marker in -currents sendmail and > reject all email to the current list if they don't originate > from such a system. > > Bad idea.. this would create problems for people who run -current, but read mail on -stable boxes.. If -current is broken, how are they going to report it? -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org | P.O. Box 9792, Stanford, Ca 94309-9792 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 9: 3:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 86B6114F6B for ; Sat, 11 Dec 1999 09:02:59 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id MAA17909; Sat, 11 Dec 1999 12:02:52 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA04015; Sat, 11 Dec 1999 12:02:22 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 11 Dec 1999 12:02:22 -0500 (EST) To: Cc: freebsd-current@freebsd.org Subject: Re: Errors from the ata disk driver In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14418.32732.945550.170250@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG joeo@nks.net writes: > I've got a striped vinum partition that is occasionally going stale when > I get spurrious errors from the ata driver. > > I can setstate the drives and the volume back up and an fsck of the > partition doesn't show any obvious corruption. > > What do these errors indicate? > > ad5: status=51 error=84 > ad_interrupt: hard error > vinum0.p0.s3: fatal read I/O error > ad6: status=51 error=84 > ad_interrupt: hard error > vinum0.p0.s4: fatal read I/O error > > These drives are hanging off this controller; > ata-pci1: irq 9 at device 9.0 on pci0 > ata-pci1: Busmastering DMA supported These are UDMA CRC errors. Whatever you do, DO NOT upgrade to a recent current without reading the ata driver's commit logs very carefully. The ata-driver has recently grown recovery code where it will try to back down to PIO mode to fetch such blocks. As recently as last week, the ata driver would lock a machine solid (unpingable, reset or power-cycle required) when attempting to back down to PIO mode when the drive in question was attached to a Promise Ultra controller. Soren knows about the problem & is going to fix it. ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 9:16:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E2A7014D4F for ; Sat, 11 Dec 1999 09:16:30 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id MAA18077; Sat, 11 Dec 1999 12:16:29 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA04045; Sat, 11 Dec 1999 12:15:59 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 11 Dec 1999 12:15:59 -0500 (EST) To: Greg Childers Cc: freebsd-current@freebsd.org Subject: Re: ATA problem In-Reply-To: <4.2.0.58.19991208223719.00947450@pop.uky.edu> References: <4.2.0.58.19991208223719.00947450@pop.uky.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14418.33865.945738.983367@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Childers writes: > Hello, > > Seems now is the time to raise problems with ATA, so here goes. I have used the ATA driver > since its introduction into -current without problem until recently. A kernel from October > 5 worked fine. Now, it no longer works using ATA, but works fine using the old WD drivers. > The console freezes after the dmesg and the keyboard is unresponsive. The ata info in I'm having similar problems, however mine are spurrious. They happen maybe 1 in 15 or so reboots. I'm seeing them on two kinds of machines, both alpha & i386. All the machines I'm seeing this on have serial consoles, but since about 95% of the machines I take care of do, they might not mean anything. I haven't seen it on a SCSI machine, but I'm not sure if that means anything either, since nearly all our machines boot from IDE disks. When they happen, the machine is unresponsive. It will ignore attempts to break into ddb. I'd have tried to debug it already, but its pretty damned hard to catch. Usually it only seems to happen when I reboot a machine from home & cannot walk up & hit the reset button. :-( Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 ######################################################################## i386: Asus P2BLS: ######################################################################## Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #5: Fri Dec 10 15:40:34 EST 1999 gallatin@omelette.cs.duke.edu:/usr/project/ari_scratch2/gallatin/zsrc/sys/co mpile/SLICEX86 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 451024998 Hz CPU: Pentium III/Xeon (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x387f9ff real memory = 67108864 (65536K bytes) avail memory = 61386752 (59948K bytes) Preloaded elf kernel "kernel" at 0xc0300000. <...> ata-pci0: at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 <...> ad0: ATA-4 disk at ata0 as master ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 Mounting root from ufs:/dev/ad0s1a ######################################################################## alpha: AlphaServer DS10: ######################################################################## Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #21: Mon Nov 8 12:07:51 EST 1999 gallatin@verdi.cs.duke.edu:/a/muffin/export/ari_scratch2/gallatin/src/sys/co mpile/ALPHA Compaq Professional Workstation (Monet) COMPAQ AlphaServer DS10 466 MHz, 462MHz 8192 byte page size, 1 processor. CPU: EV6 (21264) major=8 minor=4 extensions=0x303 OSF PAL rev: 0x1003300020133 real memory = 534282240 (521760K bytes) avail memory = 515039232 (502968K bytes) Preloaded elf kernel "kernel" at 0xfffffc0000644000. pcib0: <21271 PCI host bus adapter> on tsunami0 <...> ata-pci0: irq 238 at device 13.0 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 <...> ad0: ATA-4 disk at ata1 as master ad0: 9541MB (19541088 sectors), 19386 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=04 acd0: CDROM drive at ata0 as master acd0: read 5512KB/s (5512KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked Mounting root from ufs:/dev/wd0a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 9:27:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 863A614E9E for ; Sat, 11 Dec 1999 09:27:41 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id SAA24924 for current@FreeBSD.org; Sat, 11 Dec 1999 18:09:43 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Sat, 11 Dec 1999 18:09:42 +0100 From: Marcel Moolenaar Message-ID: <38528556.865E578C@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <17541.991211@esrr.irk.ru> Subject: Re: make release broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oleg Dobrokhotov wrote: > > Hello ALL, > After Making hierarchy, in Installig everything > >install -C -o root -g wheel -m 444 /usr/src/include/osreldate.h > >/usr/SNAP/include > >install: osreldate.h - no such file or directory... > >***Error code 71 > >Stop in /usr/src/include > >Error code 1 Fixed. Thanks, -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 9:30:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C086B14C97 for ; Sat, 11 Dec 1999 09:30:48 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA04573; Sat, 11 Dec 1999 18:30:35 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912111730.SAA04573@freebsd.dk> Subject: Re: Errors from the ata disk driver In-Reply-To: from "joeo@nks.net" at "Dec 11, 1999 09:49:57 am" To: joeo@nks.net Date: Sat, 11 Dec 1999 18:30:34 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems joeo@nks.net wrote: > I've got a striped vinum partition that is occasionally going stale when > I get spurrious errors from the ata driver. > > I can setstate the drives and the volume back up and an fsck of the > partition doesn't show any obvious corruption. > > What do these errors indicate? > > ad5: status=51 error=84 > ad_interrupt: hard error > vinum0.p0.s3: fatal read I/O error > ad6: status=51 error=84 These are UDMA CRC errors, if you upgrade to the latest current, ata knows to retry these, only if they persist, something is wrong. However it could indicate cable problems, ie bad connectors or maybe too long cables.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 9:52:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 1B4BD1510B for ; Sat, 11 Dec 1999 09:52:46 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id LAA00460; Sat, 11 Dec 1999 11:52:39 -0600 (CST) (envelope-from dick) Date: Sat, 11 Dec 1999 11:52:39 -0600 From: "Richard Seaman Jr." To: Soren Schmidt Cc: current@freebsd.org Subject: Re: SiS ata Driver (was Re: HEADSUP: wd driver will be retired!) Message-ID: <19991211115239.A339@tar.com> References: <199912090751.IAA79179@freebsd.dk> <199912091028.LAA16181@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912091028.LAA16181@freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 09, 1999 at 11:28:20AM +0100, Soren Schmidt wrote: > It seems Soren Schmidt wrote: > > It seems Richard Seaman, Jr. wrote: > > > On Wed, Dec 08, 1999 at 03:02:37PM +0100, Soren Schmidt wrote: > > > > > > > OK, you asked for it, following is a patch to support the > > > > sis 5591 chipset. Remember this is done blindfolded, I > > > > have no HW to test on, but you guys do :) > > > > > > Seems to work. I'll let it run for a few days, but I'd guess it > > > is fine. > > > > Great, I have a sligthly modified version that I'd like you to test, > > but it'll have to wait until I get home to my dev box. > > Thanks for testing it out!! > > Can I have you try this patch instead, it is much simpler, and > should give the same results if I read the SiS specs right.. Tried it. Same result as the last patch. Seems to work fine. If you want the dmesg, let me know (same as last time, which I sent you). No problems over the last 2 days with the ata driver. FYI: wd vs ata on AMD 266 with SiS 5591 and IBM-DJNA-371800: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU WD 512 9204 95.1 13615 68.5 5741 34.0 10051 92.2 15282 45.4 135.9 3.6 ATA 512 9446 95.2 13723 72.1 4430 25.4 10187 92.0 14836 42.9 132.0 3.5 -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 9:55:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 064FA14FBB for ; Sat, 11 Dec 1999 09:55:38 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA04647; Sat, 11 Dec 1999 18:55:27 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912111755.SAA04647@freebsd.dk> Subject: Re: FYI: Benchmarked ATA driver In-Reply-To: from Dieter Rothacker at "Dec 11, 1999 02:29:33 pm" To: didi@Xterminator.STUDFB.UniBw-Muenchen.de (Dieter Rothacker) Date: Sat, 11 Dec 1999 18:55:27 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Dieter Rothacker wrote: > Hi, > > here I have my Bonnie++ 0.99d output: > machine is a P233MMX, 128MB, Hotrod66 with IBM DJNA-352500. > (One slice, one partition UFS) > -- > Version 0.99d ------Sequential Output------ --Sequential Input- --Random- > -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- > Machine MB K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP > Unknown 256 6578 91 13484 71 3976 27 6539 92 13550 50 297.4 8 > ------Sequential Create------ --------Random Create-------- > -Create-- --Stat--- -Delete-- -Create-- --Stat--- -Delete-- > files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP > 30 121 83 7781 67 1079 92 135 91 184 99 80 25 > -- > This really rocks, and the driver is perfectly stable. Very good work. Thanks, very much appreciated!! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 10:43:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 526E014CB1 for ; Sat, 11 Dec 1999 10:43:50 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id NAA19532; Sat, 11 Dec 1999 13:43:44 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id NAA19757; Sat, 11 Dec 1999 13:43:14 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 11 Dec 1999 13:43:13 -0500 (EST) To: Soren Schmidt Cc: joeo@nks.net, freebsd-current@FreeBSD.ORG Subject: Re: Errors from the ata disk driver In-Reply-To: <199912111730.SAA04573@freebsd.dk> References: <199912111730.SAA04573@freebsd.dk> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14418.39524.290684.380673@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt writes: > It seems joeo@nks.net wrote: > > I've got a striped vinum partition that is occasionally going stale when > > I get spurrious errors from the ata driver. > > > > I can setstate the drives and the volume back up and an fsck of the > > partition doesn't show any obvious corruption. > > > > What do these errors indicate? > > > > ad5: status=51 error=84 > > ad_interrupt: hard error > > vinum0.p0.s3: fatal read I/O error > > ad6: status=51 error=84 > > These are UDMA CRC errors, if you upgrade to the latest current, ata > knows to retry these, only if they persist, something is wrong. > However it could indicate cable problems, ie bad connectors or maybe > too long cables.. > He said the disk was attached to a Promise Ultra/33. Does the backdown to PIO on Promise Ultra controllers work now? I've been watching the commits to the ata driver, and haven't seen anything that makes me think that it would.. but I haven't tried it since last week. Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 10:57:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 08B6E14CEC for ; Sat, 11 Dec 1999 10:57:08 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id MAA60834; Sat, 11 Dec 1999 12:56:53 -0600 (CST) (envelope-from dick) Date: Sat, 11 Dec 1999 12:56:53 -0600 From: "Richard Seaman, Jr." To: "Jordan K. Hubbard" Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: Reasonable decision-making [Re: HEADSUP: wd driver will be retired!] Message-ID: <19991211125653.B339@tar.com> References: <6235.944849641@critter.freebsd.dk> <2590.944896819@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <2590.944896819@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 10, 1999 at 11:20:19PM -0800, Jordan K. Hubbard wrote: > my strategy on the whole affair at this point has > been to simply make marks on a tally-sheet near my keyboard, While there is now working support for SiS 5591, and thus my initial objection to removal of the wd drivers is now gone, I would still vote to retain it for some intermediate period. You can put my vote in the appropriate column of your tally. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 11: 5:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id BBA4514A2A for ; Sat, 11 Dec 1999 11:05:40 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA30136; Sat, 11 Dec 1999 19:15:13 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA77830; Sat, 11 Dec 1999 19:29:25 +0100 (CET) (envelope-from wilko) Date: Sat, 11 Dec 1999 19:29:25 +0100 From: Wilko Bulte To: Bob Vaughan Cc: nate@mt.sri.com, phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211192925.C77444@yedi.iaf.nl> References: <6332.944849983@critter.freebsd.dk> <199912111700.JAA34096@tantivy.stanford.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912111700.JAA34096@tantivy.stanford.edu>; from techie@tantivy.stanford.edu on Sat, Dec 11, 1999 at 09:00:52AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 11, 1999 at 09:00:52AM -0800, Bob Vaughan wrote: > > Subject: Re: HEADSUP: wd driver will be retired! > > Date: Fri, 10 Dec 1999 19:19:43 +0100 > > From: Poul-Henning Kamp > > > > > > Maybe we should put a special marker in -currents sendmail and > > reject all email to the current list if they don't originate > > from such a system. > > > > > > Bad idea.. this would create problems for people who run -current, but > read mail on -stable boxes.. If -current is broken, how are they going to > report it? Maybe phk will volunteer his private phone number for those cases? ;-) ;-) Seriously: I don't expect to be meant seriously. Right? [has -current on 3 axp and 2 intels, mails from -stable] -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 11:37:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id D330015139; Sat, 11 Dec 1999 11:37:22 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id MAA06773; Sat, 11 Dec 1999 12:32:04 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199912111932.MAA06773@freeway.dcfinc.com> Subject: Re: Route table leaks In-Reply-To: <199912081423.IAA59277@aurora.sol.net> from Joe Greco at "Dec 8, 99 08:23:35 am" To: jgreco@ns.sol.net (Joe Greco) Date: Sat, 11 Dec 1999 12:32:03 -0700 (MST) Cc: jdp@polstra.com, current@FreeBSD.ORG, stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Joe Greco wrote: > Hell, I've been seeing this for well over a year. The last time I mentioned > it, everybody seemed to think I was nuts. :-) > > FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 Doesn't happen on 2.2... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= chad> uname -v FreeBSD 2.2.8-STABLE #5: Sun Sep 19 19:18:11 MST 1999 toor@freeway.dcfinc.com:/usr/src/sys/compile/freeway chad> uptime 12:26PM up 80 days, 13:51, 3 users, load averages: 1.06, 1.03, 1.00 chad> vmstat -m | grep routetbl routetbl 46 6K 19K 18468K 2386 0 0 16,32,64,128,256 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 12:16:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 27A6114E16; Sat, 11 Dec 1999 12:16:54 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id PAA63528; Sat, 11 Dec 1999 15:16:40 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <199912112016.PAA63528@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <12376.944898748@critter.freebsd.dk> Date: Sat, 11 Dec 1999 15:16:40 -0500 (EST) From: John Baldwin To: Poul-Henning Kamp Subject: Re: HEADSUP: wd driver will be retired! Cc: current@FreeBSD.org, Luoqi Chen , Kris Kennaway , Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Dec-99 Poul-Henning Kamp wrote: > In message <199912110132.SAA26623@harmony.village.org>, Warner Losh writes: >>In message <7881.944870115@critter.freebsd.dk> Poul-Henning Kamp writes: >>: You overlook one simple thing here: If we want the ata driver tested, >>: we need to make existing kernel configs break, otherwise people >>: will not change them to use ata. We know this from bitter experience. >> >>If all you are talking about is something like: >> >>Index: files.i386 >>=================================================================== >>RCS file: /home/imp/FreeBSD/CVS/src/sys/i386/conf/files.i386,v >>retrieving revision 1.282 >>diff -u -r1.282 files.i386 >>--- files.i386 1999/11/28 17:51:06 1.282 >>+++ files.i386 1999/12/11 01:31:00 >>@@ -318,6 +318,7 @@ >> i386/isa/stallion.c optional stl >> i386/isa/tw.c optional tw >> i386/isa/vesa.c optional vga >>+i386/isa/SirNotAppaeringInThisKerenl.c optional wd >> i386/isa/wd.c optional wd >> i386/isa/wd.c optional wdc >> i386/isa/wfd.c optional wfd >> >> >>I could go along with that. > > And probably an > #error "Don't use this driver, use ata-disk instead" > in wd.d What about no change to files.i386 (so that if someone's computer can't handle ata for the moment its one less step they have to go to compile a kernel with the old system), keep the #error above, but wrap it in a #ifndef FORCE_WD/#endif or something similar. Then, if someone does have to have the old drivers for some reason, they can stick 'option FORCE_WD' in their kernel config. You could then choose where to document FORCE_WD.. either in expanding the #error message to be more verbose and detailing the existance of this option if it's use is necessary (my preference), or make it a "closely guarded secret" you have to post a question to -current to get. -current people are not bozos, if you complete the ata driver enough in the ata message, they will switch to it, and they will know to even if they are a luser who's not reading -current like they should. FWIW, I've been using ata on my -current test box since I've started running -current (about two months) w/o any problems. > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 12:23:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id AD11D15008 for ; Sat, 11 Dec 1999 12:23:07 -0800 (PST) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.1a/8.9.1) id EAA26327; Sun, 12 Dec 1999 04:22:51 +0800 (WST) From: Michael Kennett Message-Id: <199912112022.EAA26327@laurasia.com.au> Subject: Re: Install of 4.0-19991208-CURRENT In-Reply-To: <199912111413.JAA03757@p.wl.vg> from "patrick@whetstonelogic.com" at "Dec 11, 99 09:13:57 am" To: patrick@whetstonelogic.com Date: Sun, 12 Dec 1999 04:22:50 +0800 (WST) 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 > On 11 Dec, Michael Kennett wrote: > > I've just tried installing the last current snapshot (4.0-19991208-CURRENT) > > onto an IBM laptop (365, type 2625-2E9) with a Xircom networking card > > (CE3B-100BTX). It failed -- the pccard was not recognized. > > > > I mention this because the floppies/pccard/README.TXT mentioned the systems > > that have been tested. > > Did you rebuild the kernel with pccard support enabled? > > You didn't mention in the message. No. I used the boot floppies (mfsroot.flp, kern.flp) as found in the directory 4.0-19991208-CURRENT/floppies/pccard on the ftp site current.freebsd.org. Mike Kennett (mike@laurasia.com.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 12:36: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from homer.mkintl.com (242671hfc111.tampabay.rr.com [24.26.71.111]) by hub.freebsd.org (Postfix) with ESMTP id 6967515216 for ; Sat, 11 Dec 1999 12:36:01 -0800 (PST) (envelope-from joeo@homer.mkintl.com) Received: from localhost (joeo@localhost) by homer.mkintl.com (8.9.3/8.9.3) with ESMTP id PAA14143 for ; Sat, 11 Dec 1999 15:35:24 -0500 Date: Sat, 11 Dec 1999 15:35:24 -0500 (EST) From: To: freebsd-current@freebsd.org Subject: Re: Errors from the ata disk driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will the backdown to PIO mode be permanent till the next reboot of the machine, or will the driver be able to attempt to return to DMA mode after a timeout period. I'm only seeing these errors under really heavy disk activity (mutlitple nfs readers and writers plus rsync/mirror jobs to the vinum volume in question). On the vinum front, does vinum have the ability to retry writing a block (or whatever the correct abstration is) to the same device if an error like this comes up from the underlying device? Thanks, keep up the great work (Yes, I know I should be using scsi for something like this, but the price of a 200GB raid0 unit built out of IDE equipment compared to the same built out of SCSI hardware is quite shocking. Especially for a non-mission critical role.) On Sat, 11 Dec 1999, Andrew Gallatin wrote: > These are UDMA CRC errors. Whatever you do, DO NOT upgrade to a > recent current without reading the ata driver's commit logs very > carefully. > > The ata-driver has recently grown recovery code where it will try to > back down to PIO mode to fetch such blocks. As recently as last week, > the ata driver would lock a machine solid (unpingable, reset or > power-cycle required) when attempting to back down to PIO mode when > the drive in question was attached to a Promise Ultra controller. > > Soren knows about the problem & is going to fix it. > >------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email:gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 12:40:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 042F5151A9 for ; Sat, 11 Dec 1999 12:40:20 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac10.wam.umd.edu (root@rac10.wam.umd.edu [128.8.10.150]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA18321; Sat, 11 Dec 1999 15:40:13 -0500 (EST) Received: from rac10.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac10.wam.umd.edu (8.9.3/8.9.3) with SMTP id PAA24030; Sat, 11 Dec 1999 15:40:10 -0500 (EST) Received: from localhost (culverk@localhost) by rac10.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA24026; Sat, 11 Dec 1999 15:40:09 -0500 (EST) X-Authentication-Warning: rac10.wam.umd.edu: culverk owned process doing -bs Date: Sat, 11 Dec 1999 15:40:08 -0500 (EST) From: Kenneth Wayne Culver To: "Jordan K. Hubbard" Cc: freebsd-current@freebsd.org Subject: Re: Audio support [was Re: HEADSUP: wd driver will be retired!] In-Reply-To: <2436.944893104@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 > > The same thing is about to apply to the woxware sound code, we have a > > new shiny system that works and is much better designed... > > Actually, I'm sad to say that our shiny new sound system does *not* > work for some of the most popular audio chipsets on the market today > (where the older "luigi" sound system did support them) and this is a > matter of significant concern to some folks, myself included. I'll have to second you on that one, I've been applying patchs of my own as well as other's patchs to make my soundcard even detect. I used to be able to get my ViBRA16X to work using the Voxware drivers, but since the PnP changes, I've had to use pcm because Voxware will no longer detect my soundcard with the bios in PnP OS mode. (And when I turn PnP OS off, the OS won't boot) My modem which used to be detected simply as sio1, now won't even attach to the sio driver. > We're getting a larger population of people who expect FreeBSD to > simply continue to work from release to release, and this is not an > unreasonable expectation when you think about it. Unfortunately, when > we remove support for a piece of hardware which was formerly supported > (the aic driver being a good example) and this particular hardware > happens to be in those people's machines, well, it's easy to see where > "continuing to work" is no longer a claim we can make for FreeBSD's > progress in such cases. > > When this is also for some really old and grotty piece of hardware, > like floppy tape drives, and nobody is interested in actively > maintaining the driver for it, then that's a reasonably justifable > argument for taking that kind of public relations trade-off. When the > hardware in question is something that's currently being sold on the > open market and is still quite popular, like the SB16 PCI or Vibra16X > on-board audio chipset, then killing off support for it is quite > another thing. Both of those device currently refuse to work in any > of my -current test boxes and perhaps you should have chosen a better > example in making your argument. :-) > I agree, we need to start supporting that hardware that currently doesn't work, but used to work if we want to keep our user base growing (I personally have won 30 converts from Linux, and about 4 new users). ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 12:50:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 4A1B5150AC for ; Sat, 11 Dec 1999 12:50:46 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu (root@rac7.wam.umd.edu [128.8.10.147]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA18716; Sat, 11 Dec 1999 15:50:45 -0500 (EST) Received: from rac7.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.3/8.9.3) with SMTP id PAA00321; Sat, 11 Dec 1999 15:50:42 -0500 (EST) Received: from localhost (culverk@localhost) by rac7.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA00317; Sat, 11 Dec 1999 15:50:41 -0500 (EST) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Sat, 11 Dec 1999 15:50:41 -0500 (EST) From: Kenneth Wayne Culver To: "Jordan K. Hubbard" Cc: freebsd-current@freebsd.org Subject: Re: Audio support [was Re: HEADSUP: wd driver will be retired!] 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 Just a question which I'm not sure is soundcard related. My xmms no longer starts up anymore, it just hangs in Poll before it actually puts anything on the display, is that because /dev/dsp isn't working? ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sat, 11 Dec 1999, Kenneth Wayne Culver wrote: > > > The same thing is about to apply to the woxware sound code, we have a > > > new shiny system that works and is much better designed... > > > > Actually, I'm sad to say that our shiny new sound system does *not* > > work for some of the most popular audio chipsets on the market today > > (where the older "luigi" sound system did support them) and this is a > > matter of significant concern to some folks, myself included. > > > I'll have to second you on that one, I've been applying patchs of my own > as well as other's patchs to make my soundcard even detect. I used to be > able to get my ViBRA16X to work using the Voxware drivers, but since the > PnP changes, I've had to use pcm because Voxware will no longer detect my > soundcard with the bios in PnP OS mode. (And when I turn PnP OS off, the > OS won't boot) My modem which used to be detected simply as sio1, now > won't even attach to the sio driver. > > > We're getting a larger population of people who expect FreeBSD to > > simply continue to work from release to release, and this is not an > > unreasonable expectation when you think about it. Unfortunately, when > > we remove support for a piece of hardware which was formerly supported > > (the aic driver being a good example) and this particular hardware > > happens to be in those people's machines, well, it's easy to see where > > "continuing to work" is no longer a claim we can make for FreeBSD's > > progress in such cases. > > > > When this is also for some really old and grotty piece of hardware, > > like floppy tape drives, and nobody is interested in actively > > maintaining the driver for it, then that's a reasonably justifable > > argument for taking that kind of public relations trade-off. When the > > hardware in question is something that's currently being sold on the > > open market and is still quite popular, like the SB16 PCI or Vibra16X > > on-board audio chipset, then killing off support for it is quite > > another thing. Both of those device currently refuse to work in any > > of my -current test boxes and perhaps you should have chosen a better > > example in making your argument. :-) > > > I agree, we need to start supporting that hardware that currently doesn't > work, but used to work if we want to keep our user base growing (I > personally have won 30 converts from Linux, and about 4 new users). > > > ================================================================= > | Kenneth Culver | FreeBSD: The best OS around. | > | Unix Systems Administrator | ICQ #: 24767726 | > | and student at The | AIM: AgRSkaterq | > | The University of Maryland, | Website: (Under Construction) | > | College Park. | http://www.wam.umd.edu/~culverk/| > ================================================================= > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 12:57:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 637C414C97 for ; Sat, 11 Dec 1999 12:57:45 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id MAA98559; Sat, 11 Dec 1999 12:57:04 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sat, 11 Dec 1999 12:57:04 -0800 (PST) From: Doug White To: Vallo Kallaste Cc: Soren Schmidt , Jean Louis Ntakpe , current@FreeBSD.ORG Subject: Re: ata: lost disk contact errors [was: Re: HEADSUP: wd driver will be retired!] In-Reply-To: <19991211181115.A36357@myhakas.matti.ee> Message-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, 11 Dec 1999, Vallo Kallaste wrote: > I'm getting the "lost disk contact" messages every now and then, but > only on our mp3 machine with PIIX3 controller and IBM UDMA/66 disk. It's > an PPro machine with Intel mobo. Can it be related to newer IBM disks? Depends on what 'now and then' is. The Deskstar series of drives was not intended to run 24/7, and therefore shut themselves down every week to clean the heads. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 13: 9: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6FAA015251 for ; Sat, 11 Dec 1999 13:09:04 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA96793; Sat, 11 Dec 1999 13:09:03 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA68974; Sat, 11 Dec 1999 13:09:02 -0800 (PST) (envelope-from obrien) Date: Sat, 11 Dec 1999 13:09:02 -0800 From: "David O'Brien" To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: why 'The legacy aout build' was removed from current ? Message-ID: <19991211130902.C14998@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199912090800.RAA01655@tomoyo.snipe.rim.or.jp> <42967.944727820@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <42967.944727820@axl.noc.iafrica.com>; from sheldonh@uunet.co.za on Thu, Dec 09, 1999 at 10:23:40AM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 09, 1999 at 10:23:40AM +0200, Sheldon Hearn wrote: > > Are you sure? Any a.out binaries for FreeBSD are going to be desgined > to work with 3.x or older. Why??? A.out runs just fine on 4.0-R, and had better on 5.0-R. > So producing a.out libraries for CURRENT is silly. :-) Nope. You really need to think about the ISV's. Why do you think Netscape is still a.out? ISV's want to produce one binary that runs across multiple generations of FreeBSD. Take Applixware for instance. It is built on 3.1. It needs compat3x to run on CURRENT. Don't be surprised if Applixware is still built on 3.1 when 5.0-R hits the streets. What I'm getting at here is ISV's needs are different from ours as OS developers. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 13:23:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4404D151D5 for ; Sat, 11 Dec 1999 13:23:18 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA96854; Sat, 11 Dec 1999 13:23:18 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA69072; Sat, 11 Dec 1999 13:23:17 -0800 (PST) (envelope-from obrien) Date: Sat, 11 Dec 1999 13:23:16 -0800 From: "David O'Brien" To: "Kenneth D. Merry" Cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211132316.D14998@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <199912110239.MAA01680@nymph.detir.qld.gov.au> <199912110422.VAA00723@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912110422.VAA00723@panzer.kdm.org>; from ken@kdm.org on Fri, Dec 10, 1999 at 09:22:55PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 10, 1999 at 09:22:55PM -0700, Kenneth D. Merry wrote: > And as for the device renaming, you didn't have to change anything from > sd->da. The old device names and nodes were supported in most every way. BUT not any longer. Thus we have no choice but fully make the sd->da change. [David says this as last weekend he had to change fstabs and /dev for 5 of his machines] -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 13:23:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 6C84515290 for ; Sat, 11 Dec 1999 13:23:11 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 029B01CD1; Sun, 12 Dec 1999 05:22:54 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Kenneth Wayne Culver Cc: "Jordan K. Hubbard" , freebsd-current@freebsd.org Subject: Re: Audio support [was Re: HEADSUP: wd driver will be retired!] In-Reply-To: Message from Kenneth Wayne Culver of "Sat, 11 Dec 1999 15:40:08 EST." Date: Sun, 12 Dec 1999 05:22:54 +0800 From: Peter Wemm Message-Id: <19991211212254.029B01CD1@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > > > The same thing is about to apply to the woxware sound code, we have a > > > new shiny system that works and is much better designed... > > > > Actually, I'm sad to say that our shiny new sound system does *not* > > work for some of the most popular audio chipsets on the market today > > (where the older "luigi" sound system did support them) and this is a > > matter of significant concern to some folks, myself included. > > > I'll have to second you on that one, I've been applying patchs of my own > as well as other's patchs to make my soundcard even detect. I used to be > able to get my ViBRA16X to work using the Voxware drivers, but since the > PnP changes, I've had to use pcm because Voxware will no longer detect my > soundcard with the bios in PnP OS mode. (And when I turn PnP OS off, the > OS won't boot) My modem which used to be detected simply as sio1, now > won't even attach to the sio driver. Regarding the modem.. Look in sys/isa/sio.c for sio_ids[]. Look up the ID of your modem (pnpinfo) and add the logical ID (not the vendor ID) to the table. It should work, and when it does, please send a patch. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 13:25: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id C548E15251; Sat, 11 Dec 1999 13:24:58 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA77568; Sat, 11 Dec 1999 16:24:57 -0500 (EST) (envelope-from wollman) Date: Sat, 11 Dec 1999 16:24:57 -0500 (EST) From: Garrett Wollman Message-Id: <199912112124.QAA77568@khavrinen.lcs.mit.edu> To: obrien@FreeBSD.ORG Cc: Sheldon Hearn , current@FreeBSD.ORG Subject: Re: why 'The legacy aout build' was removed from current ? In-Reply-To: <19991211130902.C14998@dragon.nuxi.com> References: <199912090800.RAA01655@tomoyo.snipe.rim.or.jp> <42967.944727820@axl.noc.iafrica.com> <19991211130902.C14998@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> [Attribution lost.] >> So producing a.out libraries for CURRENT is silly. :-) > Nope. You really need to think about the ISV's. Why do you think > Netscape is still a.out? ISV's want to produce one binary that runs > across multiple generations of FreeBSD. Which, of course, is the whole point. There is no forward compatibility, only backward. a.out binaries compiled on 4.0 simply WILL NOT WORK on 3.x, unless they're in that tiny class of trivial programs which do not invoke any sort of signal handling. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 13:48:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 72A1614F50 for ; Sat, 11 Dec 1999 13:48:17 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBBLmCQ85894 for ; Sat, 11 Dec 1999 14:48:13 -0700 (MST) Message-Id: <199912112148.dBBLmCQ85894@orthanc.ab.ca> To: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sat, 11 Dec 1999 11:41:22 +0100." Date: Sat, 11 Dec 1999 14:48:12 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Dieter" == Dieter Rothacker writes: Dieter> Why would you want to define "correct" numbering the Dieter> non-spread-out numbering? Or did I misunderstand you? I Dieter> have all my disks as master drives on the channels. Now, Dieter> when I hook up another disk for backup or maintenance Dieter> purposes, my numbering is messed up. Or worse, on a file server where you lose a low-numbered disk, not only does that one go away, but everything higher numbered loses as well. This "feature" does nothing other than introduce a gratuitous backwards-incompatibility. There is nothing wrong with the "old" scheme. I've loathed this behaviour since it was introduced into SCSI/CAM, and would rejoice at its removal. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 13:49:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id E4AAF14E3C for ; Sat, 11 Dec 1999 13:49:50 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id NAA71033; Sat, 11 Dec 1999 13:49:16 -0800 (PST) From: Archie Cobbs Message-Id: <199912112149.NAA71033@bubba.whistle.com> Subject: Re: Modules and sysctl tree In-Reply-To: <81199.944909403@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 11, 1999 02:50:03 am" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sat, 11 Dec 1999 13:49:16 -0800 (PST) Cc: abial@webgiro.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard writes: > > I think the latter. In 'theory' there should be no discernable > > difference between functionality from a KLD vs. the same functionality > > compiled directly into the kernel. > > Only in theory, of course. :) > > As Andrzej has already pointed out, modules can also be loaded and > unloaded, creating a sysctl space where things enter and leave > dynamically. Let's say I'm somebody who creates a nifty little GUI > sysctl editor for the CLI-challenged and, because it's time-consuming > to build a form with fields for all the relevant sysctl variables, I > take the obvious shortcut of parsing the output of `sysctl -A' once at > startup time and then dealing with the individual field callbacks > thereafter. On my "classic" system with a config-generated kernel, > this works just fine and my GUI front-end for sysctl is eventually > declared "useful enough" that I start handing it around. Then > somebody who actually loads and unloads klds tries to use it, and > results (needless to say) are no longer quite in alignment with > expectations. :) Just a hypothetical scenario, of course, but > I simply wanted to make the point that "no discernable difference" > might be hard to achieve for certain values of discernment. I think sysctl nodes appearing and disappearing falls into the same category as /dev files appearing and disappearing -- it's a natural thing to do in this day of dynamic devices, etc. but some programs were written with an implicit assumption that that would never happen. In other words, it's not a problem specific to KLD's .. but it's still a problem :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 13:51:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 293AE15042 for ; Sat, 11 Dec 1999 13:51:27 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id QAA95091; Sat, 11 Dec 1999 16:51:16 -0500 (EST) (envelope-from bsdx@looksharp.net) Date: Sat, 11 Dec 1999 16:51:16 -0500 (EST) From: Adam To: Lyndon Nerenberg Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912112148.dBBLmCQ85894@orthanc.ab.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 11 Dec 1999, Lyndon Nerenberg wrote: >>>>>> "Dieter" == Dieter Rothacker writes: > > Dieter> Why would you want to define "correct" numbering the > Dieter> non-spread-out numbering? Or did I misunderstand you? I > Dieter> have all my disks as master drives on the channels. Now, > Dieter> when I hook up another disk for backup or maintenance > Dieter> purposes, my numbering is messed up. > >Or worse, on a file server where you lose a low-numbered disk, not >only does that one go away, but everything higher numbered loses as >well. This "feature" does nothing other than introduce a gratuitous >backwards-incompatibility. There is nothing wrong with the "old" scheme. >I've loathed this behaviour since it was introduced into SCSI/CAM, >and would rejoice at its removal. > >--lyndon > As I understand it, cam or pre-cam or wd or ata it is simply an issue of defaults. If you plan to use disks that die or become removed, simply read LINT on how to wire your disk id's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 13:55:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 527BF14D11 for ; Sat, 11 Dec 1999 13:55:49 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA96977; Sat, 11 Dec 1999 13:55:48 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id NAA69124; Sat, 11 Dec 1999 13:55:48 -0800 (PST) (envelope-from obrien) Date: Sat, 11 Dec 1999 13:55:48 -0800 From: "David O'Brien" To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211135548.E14998@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991210160247.DF62D1CA0@overcee.netplex.com.au> <5461.944842529@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <5461.944842529@critter.freebsd.dk>; from phk@critter.freebsd.dk on Fri, Dec 10, 1999 at 05:15:29PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 10, 1999 at 05:15:29PM +0100, Poul-Henning Kamp wrote: > > Please, help Sos fix ATA if you know of a problem. > Please, help fix PCCARD if you know of a problem. Ok, so now the attitude is I need to spend all my time: 1. Fix ATA to work on my laptop (there are timeout issues) 2. Fix PCCARD on my laptop so I can suspend 3. Fix if_ep so my 574tx works again. 4. Fix if_xe so I could use my other 10/100 PCCard while the 574tx support is broke. 5. Fix if_ep so the 389d doesn't run only on the watchdog timer 6. Fix if_ed if that becomes broken *again* on the laptop 7. Fix newpcm so I have sounds support (was broken on two of my machines) 8. Fix `make world' so I can fully sync things again. 9. Fix if_fxp to not crash on my Alpha? Is this list long enough yet? I only have X amount of FreeBSD time. Should I just start O'BrienBSD since I'm now have to develop the whole OS? OR, I can work on the compiler and close my open PRs. Of course if I simply don't update my machine for 3 months, god knows if my compiler changes won't break world or cause other problems. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 13:55:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 813F31534C for ; Sat, 11 Dec 1999 13:55:55 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBBLtkQ88825; Sat, 11 Dec 1999 14:55:47 -0700 (MST) Message-Id: <199912112155.dBBLtkQ88825@orthanc.ab.ca> To: Adam Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sat, 11 Dec 1999 16:51:16 EST." Date: Sat, 11 Dec 1999 14:55:46 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Adam" == Adam writes: Adam> As I understand it, cam or pre-cam or wd or ata it is simply Adam> an issue of defaults. If you plan to use disks that die or Adam> become removed, simply read LINT on how to wire your disk Adam> id's. I understand. The point is: why? I had a perfectly good working system. Why should I have to make changes to support this new behaviour? What is the "benefit" of the new system? All I see is a make-work project for all my kernel configuration files. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 13:59:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BA98C14BE4 for ; Sat, 11 Dec 1999 13:59:47 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA91990; Sat, 11 Dec 1999 14:00:04 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Archie Cobbs Cc: abial@webgiro.com, freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree In-reply-to: Your message of "Sat, 11 Dec 1999 13:49:16 PST." <199912112149.NAA71033@bubba.whistle.com> Date: Sat, 11 Dec 1999 14:00:03 -0800 Message-ID: <91986.944949603@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In other words, it's not a problem specific to KLD's .. but > it's still a problem :-) Which raises an important issue - other than walking the sysctl tree regularly looking for changes, how does such an application become aware that the sysctl space has changed? The same holds true for a dynamic /dev, of course, though one assumes one can at least hack a solution with devfs where you stat the directory and compare its current mod time with a saved one, only walking the directory if you see a change. I don't see any kind of mechanism for doing this with sysctl, even as a gross hack. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 14: 2:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id C0BC514C4B for ; Sat, 11 Dec 1999 14:02:48 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id RAA76379; Sat, 11 Dec 1999 17:02:40 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <199912112202.RAA76379@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <91986.944949603@zippy.cdrom.com> Date: Sat, 11 Dec 1999 17:02:40 -0500 (EST) From: John Baldwin To: "Jordan K. Hubbard" Subject: Re: Modules and sysctl tree Cc: freebsd-current@FreeBSD.org, abial@webgiro.com, Archie Cobbs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Dec-99 Jordan K. Hubbard wrote: >> In other words, it's not a problem specific to KLD's .. but >> it's still a problem :-) > > Which raises an important issue - other than walking the sysctl tree > regularly looking for changes, how does such an application become > aware that the sysctl space has changed? The same holds true for a > dynamic /dev, of course, though one assumes one can at least hack a > solution with devfs where you stat the directory and compare its > current mod time with a saved one, only walking the directory if you > see a change. I don't see any kind of mechanism for doing this > with sysctl, even as a gross hack. Perhaps a modtime on the sysctl tree as a gross hack? Inside of sysctl() and the SYSCTL() macros you would update the time every time a write was made, node added, node removed, etc. However, it is a gross hack. > - Jordan -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 14: 9:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from radio.bicnet.net (radio.bicnet.net [199.190.243.202]) by hub.freebsd.org (Postfix) with ESMTP id 2C02A15002 for ; Sat, 11 Dec 1999 14:09:40 -0800 (PST) (envelope-from john@loverso.southborough.ma.us) Received: from loverso.southborough.ma.us (dial-pop2-141.bicnet.net [208.220.71.141]) by radio.bicnet.net (8.8.5/8.6.12) with ESMTP id RAA02777; Sat, 11 Dec 1999 17:13:18 -0500 (EST) Received: from loverso.southborough.ma.us (localhost [127.0.0.1]) by loverso.southborough.ma.us (8.9.3/8.6.9) with ESMTP id RAA02788; Sat, 11 Dec 1999 17:09:36 -0500 (EST) Message-Id: <199912112209.RAA02788@loverso.southborough.ma.us> To: "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree In-reply-to: Message from "Jordan K. Hubbard" <91986.944949603@zippy.cdrom.com> . X-Face: "UZ!}1W2N?eJdN(`1%|/OOPqJ).Idk?UyvWw'W-%`Gto8^IkEm>.g1O$[.;~}8E=Ire0|lO .o>:NlJS1@vO9bVmswRoq3j DdX9YGSeJ5a(mfX[1u>Z63G5_^+'8LVqjqvn X-Url: http://surf.to/loverso Date: Sat, 11 Dec 1999 17:09:36 -0500 From: John Robert LoVerso Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > other than walking the sysctl tree regularly looking for changes Use a similar hack: map the sysctl tree to the filesystem (ala kernfs) and then stat the directory nodes. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 14:10:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1AD0014F50; Sat, 11 Dec 1999 14:10:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA92069; Sat, 11 Dec 1999 14:10:42 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Baldwin Cc: freebsd-current@FreeBSD.org, abial@webgiro.com, Archie Cobbs Subject: Re: Modules and sysctl tree In-reply-to: Your message of "Sat, 11 Dec 1999 17:02:40 EST." <199912112202.RAA76379@server.baldwin.cx> Date: Sat, 11 Dec 1999 14:10:42 -0800 Message-ID: <92065.944950242@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Perhaps a modtime on the sysctl tree as a gross hack? Inside of sysctl() and > the SYSCTL() macros you would update the time every time a write was made, no de > added, node removed, etc. However, it is a gross hack. You're right, it would be a gross hack. :) Also, I can see where it would be valuable to be able to distinguish between tree modification (nodes entered or left) and an existing node simply being written to. Maybe a compound type, just to make it even grosser! :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 14:12:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7E79D14F6A for ; Sat, 11 Dec 1999 14:12:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA92098; Sat, 11 Dec 1999 14:12:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Robert LoVerso Cc: freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree In-reply-to: Your message of "Sat, 11 Dec 1999 17:09:36 EST." <199912112209.RAA02788@loverso.southborough.ma.us> Date: Sat, 11 Dec 1999 14:12:55 -0800 Message-ID: <92094.944950375@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Use a similar hack: map the sysctl tree to the filesystem (ala kernfs) and > then stat the directory nodes. AAIEEEEEE! sysctlfs!! :-) It's an interesting idea and I'm not sure why it also horrifies me at some inner, almost cellular, level. If somebody's actually willing to do the work of creating such a thing, however, I'll probably get over it. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 14:19:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 1D450150F6 for ; Sat, 11 Dec 1999 14:19:21 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup5-9.iptelecom.net.ua [212.9.227.9]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id AAA29466; Sun, 12 Dec 1999 00:23:37 +0200 (EET) Message-ID: <3852CDC6.92B55991@altavista.net> Date: Sun, 12 Dec 1999 00:18:46 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: Vibra 16 doesn't recognised anymore References: <199912111040.LAA01684@Magelan.Leidinger.net> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Leidinger wrote: > On 11 Dec, Maxim Sobolev wrote: > > Some time ago my soundcard (Vibra 16C), which worked just fine > > previously, stopped being recognised/attached. Following is relevant > > pieces of dmesg and pnpinfo: > > last cvsup: Dec, 9. > > sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 > drq 1,5 on isa0 > pcm0: on sbc0 > > Same pnpinfo. > > Works well here. > > Relevant cut&paste from my kernel-config: > ---snip--- > device pcm0 > device sbc0 Same is here but it doesn't being attached... Really strange, heh? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 14:23: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 2F82B1517D for ; Sat, 11 Dec 1999 14:22:56 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 00ADB1CD3; Sun, 12 Dec 1999 06:22:53 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Lyndon Nerenberg Cc: Adam , freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: Message from Lyndon Nerenberg of "Sat, 11 Dec 1999 14:55:46 MST." <199912112155.dBBLtkQ88825@orthanc.ab.ca> Date: Sun, 12 Dec 1999 06:22:53 +0800 From: Peter Wemm Message-Id: <19991211222254.00ADB1CD3@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lyndon Nerenberg wrote: > >>>>> "Adam" == Adam writes: > > Adam> As I understand it, cam or pre-cam or wd or ata it is simply > Adam> an issue of defaults. If you plan to use disks that die or > Adam> become removed, simply read LINT on how to wire your disk > Adam> id's. > > I understand. The point is: why? I had a perfectly good working system. > Why should I have to make changes to support this new behaviour? What > is the "benefit" of the new system? All I see is a make-work project > for all my kernel configuration files. The old wd driver was *solely* this way. It was not possible to have a dynamic system. If you didn't have a 'device wdX at wdcY drive Z', you had to recompile the kernel just to get to it. The scsi system has always been dynamic with a wiring *option* right from as far back as 2.0. CAM didn't change this. What is different with ata is that it has a strange hybrid of the two. By default (no options) it behaves like scsi. With ATA_STATIC_ID, it does something different - it emulates the old GENERIC layout, and it's not possible to change that. It used to be possible to have wd0 on wdc0 drive 1, and wd1 on wdc0 drive 0 (ie: backwards). It has no wiring option, but this isn't hard to add for isa-compatable devices. However, I point you to this example: ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA not enabled ata-pci1: irq 11 at device 10.0 on pci0 ata-pci1: Busmastering DMA supported ata2 at 0x9800 irq 11 on ata-pci1 ata-pci2: irq 11 at device 10.1 on pci0 ata-pci2: Busmastering DMA supported ata3 at 0xa400 irq 11 on ata-pci2 ata-pci3: irq 10 at device 11.0 on pci0 ata-pci3: Busmastering DMA supported ata4 at 0xb000 irq 10 on ata-pci3 ata-pci4: irq 10 at device 11.1 on pci0 ata-pci4: Busmastering DMA supported ata5 at 0xbc00 irq 10 on ata-pci4 ata-pci5: irq 12 at device 12.0 on pci0 ata-pci5: Busmastering DMA supported ata6 at 0xc800 irq 12 on ata-pci5 ata-pci6: irq 12 at device 12.1 on pci0 ata-pci6: Busmastering DMA supported ata7 at 0xd400 irq 12 on ata-pci6 ad0: ATA-4 disk at ata2 as master ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: ATA-4 disk at ata3 as master ad1: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad2: ATA-4 disk at ata4 as master ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA33 ad3: ATA-4 disk at ata5 as master ad3: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad3: 16 secs/int, 1 depth queue, UDMA33 ad4: ATA-4 disk at ata6 as master ad4: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad4: 16 secs/int, 1 depth queue, UDMA33 ad5: ATA-4 disk at ata7 as master ad5: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad5: 16 secs/int, 1 depth queue, UDMA33 Note that ata0 and ata1 are missing and that there are no fixed or anchorable points. It's *impossible* to wire this down with config(8), either for wdc or ata. I know it isn't wired because I got burned setting it up. I started with a controller in the right-most slot. It just happened that this motherboard that's the highest pci device ID slot. So, after setting up and adding the other two controllers, ata2 suddenly became ata7. ad0 became ad4. ATA_STATIC_ID wouldn't help because it would still have changed (ad0 would be ad4 in static mode, and after plugging in the new controllers, ad4 would have changed to at14. ie: no use at all.) wdc does not support this configuration. It can't hook onto arbitary pci ide devices. With a largely dynamic bus system like PCI etc, we need a better solution. Static wiring is not it. What Mike Smith suggested is probably about the best we can do and that requires devfs support. Each disk label would have some identifier which would be a name for the disk when attached. ie: you name your boot ide disk "foo" and it's device nodes become "foo", "foos1a" or whatever. If you move that disk from one cable to another, the device name remains constant. If you add a new controller to the motherboard and the PCI bus is renumbered, you're still ok. But.. that requires devfs to make it work. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 14:37:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 660A114D3F for ; Sat, 11 Dec 1999 14:37:13 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA10803; Sat, 11 Dec 1999 14:36:18 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912112236.OAA10803@gndrsh.dnsmgr.net> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <19991211222254.00ADB1CD3@overcee.netplex.com.au> from Peter Wemm at "Dec 12, 1999 06:22:53 am" To: peter@netplex.com.au (Peter Wemm) Date: Sat, 11 Dec 1999 14:36:18 -0800 (PST) Cc: lyndon@orthanc.ab.ca (Lyndon Nerenberg), bsdx@looksharp.net (Adam), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... > > The scsi system has always been dynamic with a wiring *option* right from > as far back as 2.0. CAM didn't change this. as far back as 386BSD and the patchkit. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 15: 2:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from tulum.brsys.com (tulum.brsys.com [216.15.105.2]) by hub.freebsd.org (Postfix) with ESMTP id 14EFB1530F for ; Sat, 11 Dec 1999 15:00:56 -0800 (PST) (envelope-from adamw@holonet.net) Received: from holonet.net (ifmxoak.informix.com [192.147.88.2]) by tulum.brsys.com (8.8.8/8.6.12) with ESMTP id PAA08304 for ; Sat, 11 Dec 1999 15:09:07 -0800 (PST) Received: by holonet.net (Postfix, from userid 667) id BD993216F; Sat, 11 Dec 1999 15:00:48 +0000 (GMT) Date: Sat, 11 Dec 1999 15:00:47 +0000 From: Adam Wight To: current@freebsd.org Subject: make world broken by choose-temp.c Message-ID: <19991211150046.A47179@> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> cc cc -O -pipe -m486 -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr2/src/gnu/usr.bin/cc/cc/../cc_tools -I/usr2/src/gnu/usr.bin/cc/cc/../cc_tools -I/usr2/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc -I/usr2/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/config -I/usr/obj/usr2/src/tmp/usr/include -o cc gcc.o gccspec.o /usr/obj/usr2/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a /usr/obj/usr2/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(choose-temp.o): In function `make_temp_file': choose-temp.o(.text+0x286): undefined reference to `mkstemps' *** Error code 1 After my hard drive died, I was put in the unfortunate position of building current from a 3.3-RELEASE system and found what is apparently a known problem with this compilation path... The fix was checked in as rev 1.8 of gnu/usr.bin/cc/cc_drv/Makefile, but was backed out several hours later. Considering that 3.x is where many -current users have to begin, either this fix should be re-inserted or the reference to mkstemps should be removed. -adam wight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 15:27:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.iol.ie (mail1.mail.iol.ie [194.125.2.192]) by hub.freebsd.org (Postfix) with ESMTP id 5D40E14C9E for ; Sat, 11 Dec 1999 15:27:24 -0800 (PST) (envelope-from nick@iol.ie) Received: from beckett.earlsfort.iol.ie (beckett.earlsfort.iol.ie [194.125.21.2]) by mail.iol.ie Sendmail (v8.9.3) with ESMTP id XAA95274 for ; Sat, 11 Dec 1999 23:27:22 GMT Received: (from nick@localhost) by beckett.earlsfort.iol.ie Sendmail (v8.9.3) id XAA16749 for current@freebsd.org; Sat, 11 Dec 1999 23:29:02 GMT From: Nick Hilliard Message-Id: <199912112329.XAA16749@beckett.earlsfort.iol.ie> Subject: Re: HEADSUP: wd driver will be retired! To: current@freebsd.org Date: Sat, 11 Dec 1999 23:29:02 +0000 (GMT) X-NCC-RegID: ie.iol X-Mailer: ELM [version 2.5 PL1] 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 phk wrote: > This is *CURRENT* remember ? We want this transistion done and > tested before current becomes 4.0-RELEASE. The time is NOW! Not quite: this is -current, 4 days before a functionality freeze and potentially less than one month before 4.0-RELEASE. Replacing critical parts of the system at this stage is a bad idea because it's simply not going to leave enough time for the ata drivers to mature and stabilise to the same level as the wd drivers. By all means, make the transition, but if you're going to do it, please don't release 4.0 in early Jan. As an end user, I have no problem with the removal of the wd drivers (or with releasing 4.0 a little later than planned), but if making this transition is something which is going to potentially compromise either stability or hardware support due to the time-scales involved, then it is ill-advised. This isn't Linux, you know. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 15:33:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 392A314BE2 for ; Sat, 11 Dec 1999 15:33:24 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id SAA78252; Sat, 11 Dec 1999 18:33:19 -0500 (EST) (envelope-from wollman) Date: Sat, 11 Dec 1999 18:33:19 -0500 (EST) From: Garrett Wollman Message-Id: <199912112333.SAA78252@khavrinen.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: Archie Cobbs , abial@webgiro.com, freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree In-Reply-To: <91986.944949603@zippy.cdrom.com> References: <199912112149.NAA71033@bubba.whistle.com> <91986.944949603@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Which raises an important issue - other than walking the sysctl tree > regularly looking for changes, how does such an application become > aware that the sysctl space has changed? It's listening on a kernel notification socket. (Implementation is an exercise left for the reader, but there are already a few examples.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 15:35:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 09AE514D70 for ; Sat, 11 Dec 1999 15:35:07 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA08146; Sat, 11 Dec 1999 23:34:35 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA21425; Sat, 11 Dec 1999 23:18:31 +0100 (CET) (envelope-from wilko) Date: Sat, 11 Dec 1999 23:18:31 +0100 From: Wilko Bulte To: Lyndon Nerenberg Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Message-ID: <19991211231831.B21336@yedi.iaf.nl> References: <199912112148.dBBLmCQ85894@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912112148.dBBLmCQ85894@orthanc.ab.ca>; from lyndon@orthanc.ab.ca on Sat, Dec 11, 1999 at 02:48:12PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 11, 1999 at 02:48:12PM -0700, Lyndon Nerenberg wrote: > >>>>> "Dieter" == Dieter Rothacker writes: > > Dieter> Why would you want to define "correct" numbering the > Dieter> non-spread-out numbering? Or did I misunderstand you? I > Dieter> have all my disks as master drives on the channels. Now, > Dieter> when I hook up another disk for backup or maintenance > Dieter> purposes, my numbering is messed up. > > Or worse, on a file server where you lose a low-numbered disk, not > only does that one go away, but everything higher numbered loses as > well. This "feature" does nothing other than introduce a gratuitous > backwards-incompatibility. There is nothing wrong with the "old" scheme. > I've loathed this behaviour since it was introduced into SCSI/CAM, > and would rejoice at its removal. I don't see why one should not wire-down the SCSI devices to whatever one's preference is. This works just brilliantly. But maybe it is that me having a small mountain of StorageWorks hotplug SCSI devices makes me defensive in this respect.. W/ -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 16:36:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id D864814BCA for ; Sat, 11 Dec 1999 16:36:46 -0800 (PST) (envelope-from tim@scratch.demon.co.uk) Received: from scratch.demon.co.uk ([212.228.22.156] helo=franklin) by finch-post-11.mail.demon.net with smtp (Exim 2.12 #1) id 11wx0H-000L5I-0B for freebsd-current@FreeBSD.ORG; Sun, 12 Dec 1999 00:36:45 +0000 Message-ID: <001301bf4438$9c4f8e20$0100a8c0@franklin> Reply-To: "Tim Preece" From: "Tim Preece" To: Subject: trying to become current Date: Sun, 12 Dec 1999 00:34:05 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am trying to get to current from 3.3-Release and I have just sent a message to questions concerning this, however I have just seen a message from Adam Wight .... make world broken by choose-temp.c .... and this is my problem Please how do I get around this ps sorry if this is the wrong place for this mail Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 16:56:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from odin.interdestination.net (www1.interdestination.net [209.12.127.2]) by hub.freebsd.org (Postfix) with SMTP id 9A2E114D70 for ; Sat, 11 Dec 1999 16:56:53 -0800 (PST) (envelope-from Zapper@FoxChat.Net) Received: (qmail 69858 invoked from network); 11 Dec 1999 18:54:45 -0600 Received: from home.zapper.org (HELO FoxChat.Net) (Zapper@209.136.139.35) by www1.interdestination.net with SMTP; 11 Dec 1999 18:54:45 -0600 Message-ID: <3852F1D1.32505170@FoxChat.Net> Date: Sat, 11 Dec 1999 18:52:33 -0600 From: "FoxChat.Net" Organization: FoxChat.Net X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Current Subject: unsubscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 16:57:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 81D8B1511D for ; Sat, 11 Dec 1999 16:57:18 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (root@rac5.wam.umd.edu [128.8.10.145]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA05155; Sat, 11 Dec 1999 19:56:43 -0500 (EST) Received: from rac5.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id TAA16995; Sat, 11 Dec 1999 19:56:43 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA16991; Sat, 11 Dec 1999 19:56:43 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Sat, 11 Dec 1999 19:56:43 -0500 (EST) From: Kenneth Wayne Culver To: Peter Wemm Cc: "Jordan K. Hubbard" , freebsd-current@freebsd.org Subject: Re: Audio support [was Re: HEADSUP: wd driver will be retired!] In-Reply-To: <19991211212254.029B01CD1@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is a patch for my modem: --- sio.c.orig Sat Dec 11 19:51:29 1999 +++ sio.c Sat Dec 11 19:51:20 1999 @@ -553,6 +553,7 @@ {0x31307256, NULL}, /* USR3031 */ {0x8020b04e, NULL}, /* SUP2080 */ {0x8024b04e, NULL}, /* SUP2480 */ + {0x7420b04e, NULL}, /* SUP2070 */ {0} }; ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sun, 12 Dec 1999, Peter Wemm wrote: > Kenneth Wayne Culver wrote: > > > > The same thing is about to apply to the woxware sound code, we have a > > > > new shiny system that works and is much better designed... > > > > > > Actually, I'm sad to say that our shiny new sound system does *not* > > > work for some of the most popular audio chipsets on the market today > > > (where the older "luigi" sound system did support them) and this is a > > > matter of significant concern to some folks, myself included. > > > > > > I'll have to second you on that one, I've been applying patchs of my own > > as well as other's patchs to make my soundcard even detect. I used to be > > able to get my ViBRA16X to work using the Voxware drivers, but since the > > PnP changes, I've had to use pcm because Voxware will no longer detect my > > soundcard with the bios in PnP OS mode. (And when I turn PnP OS off, the > > OS won't boot) My modem which used to be detected simply as sio1, now > > won't even attach to the sio driver. > > Regarding the modem.. Look in sys/isa/sio.c for sio_ids[]. Look up the > ID of your modem (pnpinfo) and add the logical ID (not the vendor ID) to > the table. It should work, and when it does, please send a patch. > > Cheers, > -Peter > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 17: 3:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from tulum.brsys.com (tulum.brsys.com [216.15.105.2]) by hub.freebsd.org (Postfix) with ESMTP id DB37115081 for ; Sat, 11 Dec 1999 17:03:23 -0800 (PST) (envelope-from adamw@holonet.net) Received: from holonet.net (ifmxoak.informix.com [192.147.88.2]) by tulum.brsys.com (8.8.8/8.6.12) with ESMTP id RAA08445 for ; Sat, 11 Dec 1999 17:11:35 -0800 (PST) Received: by holonet.net (Postfix, from userid 667) id 8F0CE25A7; Sat, 11 Dec 1999 17:03:18 +0000 (GMT) Date: Sat, 11 Dec 1999 17:03:18 +0000 From: Adam Wight To: current@freebsd.org Subject: two more 3.3->4.0 snafus Message-ID: <19991211170317.A81663@luchar.first.world> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1) The runtime-info.h target in gnu/lib/libobjc/Makefile calls `{CC} --print-prog-name=cc1obj` -print-obj-runtime-info, which uses an absolute path and calls the 3.3 version of cc1obj. This, of course, breaks the make. I don't know the proper fix, but building and installing cc1obj by hand is a decent workaround. 2) Something (sorry, I'm hurrying and can't provide details right now) requires libc.so.4 to exist in /usr/lib in order to compile. Workaround is to copy it in by hand... If I have more time and nobody's figured this one out, I'll take the library back out, recompile, and send a more detailed report. -adam wight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 17: 4:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 085FF152ED for ; Sat, 11 Dec 1999 17:04:12 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 17-044.008.popsite.net ([209.69.196.44] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 11wxQm-0003hW-00; Sat, 11 Dec 1999 18:04:10 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id UAA32217; Sat, 11 Dec 1999 20:04:04 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <001301bf4438$9c4f8e20$0100a8c0@franklin> Date: Sat, 11 Dec 1999 20:04:04 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: Tim Preece Subject: RE: trying to become current Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Dec-99 Tim Preece wrote: > Hello, > > I am trying to get to current from 3.3-Release and I have just sent a > message to questions concerning this, however I have just seen a message > from Adam Wight .... > > make world broken by choose-temp.c > > .... and this is my problem > > Please how do I get around this > > ps sorry if this is the wrong place for this mail Please use -STABLE instead. -CURRENT is only for: a) developers. b) people who need a certain driver / piece of software only available in -CURRENT. c) testers (with a large amount of experience with FreeBSD). ..and all of the above must accept any consequences as a result of using -CURRENT. They all must be subscribed to this mailing list and actually read it, et cetera. You can cvsup to -STABLE using the stable-supfile. -CURRENT is not "supported" by Walnut Creek, or the FreeBSD Project, for that matter. You use -CURRENT at your own risk. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 17: 5:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 8B7C514E8D for ; Sat, 11 Dec 1999 17:05:42 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac9.wam.umd.edu (root@rac9.wam.umd.edu [128.8.10.149]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA27064 for ; Sat, 11 Dec 1999 20:05:43 -0500 (EST) Received: from rac9.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac9.wam.umd.edu (8.9.3/8.9.3) with SMTP id UAA17753 for ; Sat, 11 Dec 1999 20:05:40 -0500 (EST) Received: from localhost (culverk@localhost) by rac9.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA17749 for ; Sat, 11 Dec 1999 20:05:40 -0500 (EST) X-Authentication-Warning: rac9.wam.umd.edu: culverk owned process doing -bs Date: Sat, 11 Dec 1999 20:05:40 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: rtc0 Message-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 don't know if anyone else was having this problem, and I don't know that this is a proper fix, but here goes: For some reason rtc0 was not working, and I think it's because this variable was not initialized, here is the patch: --- clock.c.orig Sat Dec 11 19:58:15 1999 +++ clock.c Sat Dec 11 19:58:30 1999 @@ -132,7 +132,7 @@ int clkintr_pending; int disable_rtc_set; /* disable resettodr() if != 0 */ volatile u_int idelayed; -int statclock_disable; +int statclock_disable = 0; u_int stat_imask = SWI_CLOCK_MASK; #ifndef TIMER_FREQ #define TIMER_FREQ 1193182 the patch should go in /usr/src/sys/i386/isa ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 17:17: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 1507F14DDA for ; Sat, 11 Dec 1999 17:17:03 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac4.wam.umd.edu (root@rac4.wam.umd.edu [128.8.10.144]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA05746 for ; Sat, 11 Dec 1999 20:17:01 -0500 (EST) Received: from rac4.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id UAA26893 for ; Sat, 11 Dec 1999 20:17:01 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA26889 for ; Sat, 11 Dec 1999 20:17:01 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Sat, 11 Dec 1999 20:17:01 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@FreeBSD.ORG Subject: Re: rtc0 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 Oops, try this patch instead, again, it's done wrong, but I couldn't figure out why statclock_disable was getting a value, and I don't have time to figure it out. --- clock.c.orig Sat Dec 11 19:58:15 1999 +++ clock.c Sat Dec 11 20:15:01 1999 @@ -962,7 +962,7 @@ int apic_8254_trial; struct intrec *clkdesc; #endif /* APIC_IO */ - + statclock_disable = 0; if (statclock_disable) { /* * The stat interrupt mask is different without the ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sat, 11 Dec 1999, Kenneth Wayne Culver wrote: > I don't know if anyone else was having this problem, and I don't know that > this is a proper fix, but here goes: > > For some reason rtc0 was not working, and I think it's because this > variable was not initialized, here is the patch: > > --- clock.c.orig Sat Dec 11 19:58:15 1999 > +++ clock.c Sat Dec 11 19:58:30 1999 > @@ -132,7 +132,7 @@ > int clkintr_pending; > int disable_rtc_set; /* disable resettodr() if != 0 */ > volatile u_int idelayed; > -int statclock_disable; > +int statclock_disable = 0; > u_int stat_imask = SWI_CLOCK_MASK; > #ifndef TIMER_FREQ > #define TIMER_FREQ 1193182 > > > the patch should go in /usr/src/sys/i386/isa > > ================================================================= > | Kenneth Culver | FreeBSD: The best OS around. | > | Unix Systems Administrator | ICQ #: 24767726 | > | and student at The | AIM: AgRSkaterq | > | The University of Maryland, | Website: (Under Construction) | > | College Park. | http://www.wam.umd.edu/~culverk/| > ================================================================= > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 17:18: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 4189615327 for ; Sat, 11 Dec 1999 17:17:55 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (hoefnix.ai [209.88.68.215]) by cypherpunks.ai (Postfix) with ESMTP id 03EF03B; Sat, 11 Dec 1999 21:17:46 -0400 (AST) Message-ID: <3852F788.754F741D@vangelderen.org> Date: Sat, 11 Dec 1999 21:16:56 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Archie Cobbs , abial@webgiro.com, freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree References: <91986.944949603@zippy.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 "Jordan K. Hubbard" wrote: > > > In other words, it's not a problem specific to KLD's .. but > > it's still a problem :-) > > Which raises an important issue - other than walking the sysctl tree > regularly looking for changes, how does such an application become > aware that the sysctl space has changed? I seem to recall that John Poltstra was working on a notification system (for use with CVSup) that would allow you to subscribe to certain change events... Cheers, Jeroen -- Jeroen C. van Gelderen - jeroen@vangelderen.org Interesting read: http://www.vcnet.com/bms/ JLF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 17:19:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles535.castles.com [208.214.165.99]) by hub.freebsd.org (Postfix) with ESMTP id 1859314E8D for ; Sat, 11 Dec 1999 17:19:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA00570; Sat, 11 Dec 1999 17:21:42 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912120121.RAA00570@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Takahashi Yoshihiro Cc: current@FreeBSD.org Subject: Re: make world is failed on pc98 In-reply-to: Your message of "Sat, 11 Dec 1999 23:05:52 +0900." <19991211230552P.nyan@dd.catv.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Dec 1999 17:21:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The boot2 for pc98 (sys/boot/pc98/boot2) is a.out program. So, several > tools for a.out are needed to make boot2. > > I make the patch to fix this. Is there any problem? Only in the longer term, I think. How hard would it be to port the 'new' i386 boot2? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 17:19:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles535.castles.com [208.214.165.99]) by hub.freebsd.org (Postfix) with ESMTP id 620B5151A4 for ; Sat, 11 Dec 1999 17:19:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA00613; Sat, 11 Dec 1999 17:22:00 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912120122.RAA00613@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: joeo@nks.net Cc: freebsd-current@freebsd.org Subject: Re: Errors from the ata disk driver In-reply-to: Your message of "Sat, 11 Dec 1999 09:49:57 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Dec 1999 17:22:00 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got a striped vinum partition that is occasionally going stale when > I get spurrious errors from the ata driver. > > I can setstate the drives and the volume back up and an fsck of the > partition doesn't show any obvious corruption. > > What do these errors indicate? Your disk is going off. > ad5: status=51 error=84 > ad_interrupt: hard error > vinum0.p0.s3: fatal read I/O error Looks like an uncorrectable read error. It should go away when you actually write to that block (the drive will be able to reallocate it at that point in time). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 17:20:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles535.castles.com [208.214.165.99]) by hub.freebsd.org (Postfix) with ESMTP id 1CBD0150BC for ; Sat, 11 Dec 1999 17:20:15 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA00745; Sat, 11 Dec 1999 17:22:44 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912120122.RAA00745@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Peter Wemm Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sat, 11 Dec 1999 18:28:42 +0800." <19991211102842.C18331CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Dec 1999 17:22:43 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think this should only apply to the /dev/wd* compatability devices. ie: > use the correct numbering for new installs onto ad*, but still support the old > spread-out naming for wd*. This used to be more important as it required > fiddling with $root_disk_unit, but the new mountroot code has relieved the > pressure there. Hmm. That'd actually be quite doable, but I think it might massively confuse people running in 'compatibility' mode. IMO the 'clean break' approach may have more initial noise overhead, but in the long run it's not going to scare folks so much. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 17:25:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7EDBC15076 for ; Sat, 11 Dec 1999 17:25:22 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA97534; Sat, 11 Dec 1999 17:25:11 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA01413; Sat, 11 Dec 1999 17:25:01 -0800 (PST) (envelope-from obrien) Date: Sat, 11 Dec 1999 17:25:01 -0800 From: "David O'Brien" To: Tim Preece Cc: freebsd-current@FreeBSD.ORG Subject: Re: trying to become current Message-ID: <19991211172501.A1273@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <001301bf4438$9c4f8e20$0100a8c0@franklin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <001301bf4438$9c4f8e20$0100a8c0@franklin>; from tim@scratch.demon.co.uk on Sun, Dec 12, 1999 at 12:34:05AM -0000 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am trying to get to current from 3.3-Release and I have just sent a Right now one needs to be at the latest 3-STABLE to make the jump to 4-CURRENT. Please let us know if you have a problem once you've updated to 3-STABLE. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 17:31:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id DA56B14BF2 for ; Sat, 11 Dec 1999 17:31:53 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: (qmail 3500 invoked from network); 12 Dec 1999 01:31:48 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 12 Dec 1999 01:31:48 -0000 Date: Sat, 11 Dec 1999 17:31:08 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Lyndon Nerenberg Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912112148.dBBLmCQ85894@orthanc.ab.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 11 Dec 1999, Lyndon Nerenberg wrote: > Or worse, on a file server where you lose a low-numbered disk, not > only does that one go away, but everything higher numbered loses as > well. This "feature" does nothing other than introduce a gratuitous Amen to this. If the default kernel or GENERIC shipped with the disks wired, it would be so much nicer. NT generally gets this one right, once you assign letters to partition, they tend to stick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 17:38:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles535.castles.com [208.214.165.99]) by hub.freebsd.org (Postfix) with ESMTP id 3D0EE1501B for ; Sat, 11 Dec 1999 17:38:48 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA00880; Sat, 11 Dec 1999 17:41:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912120141.RAA00880@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Lyndon Nerenberg Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! In-reply-to: Your message of "Sat, 11 Dec 1999 14:48:12 MST." <199912112148.dBBLmCQ85894@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Dec 1999 17:41:25 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>>>> "Dieter" == Dieter Rothacker writes: > > Dieter> Why would you want to define "correct" numbering the > Dieter> non-spread-out numbering? Or did I misunderstand you? I > Dieter> have all my disks as master drives on the channels. Now, > Dieter> when I hook up another disk for backup or maintenance > Dieter> purposes, my numbering is messed up. > > Or worse, on a file server where you lose a low-numbered disk, not > only does that one go away, but everything higher numbered loses as > well. This "feature" does nothing other than introduce a gratuitous > backwards-incompatibility. There is nothing wrong with the "old" scheme. > I've loathed this behaviour since it was introduced into SCSI/CAM, > and would rejoice at its removal. This is the usual poorly thought out argument, which fails to note that when you lose a disk you're already screwed due by /etc/fstab and the need to hard-mount local filesystems. The "right" solution is and has always been to name your disks and mount them by name. Once devfs is a reality, we'll be able to do just this. Until then, the problem's not really as bad as you make it out to be. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 19:20:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgw01.execpc.com (mailgw01.execpc.com [169.207.2.78]) by hub.freebsd.org (Postfix) with ESMTP id 8ED2214F50 for ; Sat, 11 Dec 1999 19:20:36 -0800 (PST) (envelope-from hamilton@pobox.com) Received: from woodstock.monkey.net (obica-2-26.mdm.mkt.execpc.com [169.207.88.154]) by mailgw01.execpc.com (8.9.1) id VAA00999 for ; Sat, 11 Dec 1999 21:20:34 -0600 Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id 5BF1150 for ; Sat, 11 Dec 1999 21:22:01 -0600 (CST) X-Mailer: exmh version 2.1.1 10/16/1999 To: current@freebsd.org Subject: ppp over pty: trying to detect CD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Dec 1999 21:22:01 -0600 From: Jon Hamilton Message-Id: <19991212032201.5BF1150@woodstock.monkey.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Running -current from this afternoon, I am having a strange symptom with ppp over a pty; ppp does not detect that the pty does not support carrier, and will cycle once per second waiting for CD to appear. Putting ``set cd off'' in my ppp.conf for that target fixed the problem, but I thought I'd mention it nonetheless, since that didn't used to be required. Certainly not all that big a deal, but I thought it was worth a mention. FreeBSD 4.0-CURRENT #13: Sat Dec 11 20:31:42 CST 1999 The section from my ppp.conf: vpn: set ipcpretry 1000 set lcpretry 1000 set timeout 0 set ifaddr 192.168.1.2/0 192.168.1.1/0 255.255.255.0 set cd off <- this guy fixed the problem enable lqr accept lqr set openmode passive set log phase ipcp Connect tun Command add 192.168.2.0/24 HISADDR and the syslog with debugging turned on, with no "set cd" in the config: Dec 11 20:48:20 woodstock ppp[3106]: Phase: Using interface: tun1 Dec 11 20:48:20 woodstock ppp[3106]: Phase: deflink: Created in closed state Dec 11 20:48:20 woodstock ppp[3106]: tun1: Command: vpn: add 192.168.2.0/24 HISADDR Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: wrote 140: cmd = Add, dst = 2a8c0, gateway = 101a8c0 Dec 11 20:48:20 woodstock ppp[3106]: tun1: Phase: PPP Started (direct mode). Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: Select changes time: no Dec 11 20:48:20 woodstock ppp[3106]: tun1: Phase: bundle: Establish Dec 11 20:48:20 woodstock ppp[3106]: tun1: Phase: deflink: closed -> opening Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: Input is a tty (/dev/ttyp0) Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: tty_Create: physical (get): fd = 0, iflag = 0, oflag = 2, cflag = 4b00 Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: physical (put): iflag = 201, oflag = 2, cflag = 3cb00 Dec 11 20:48:20 woodstock ppp[3106]: tun1: Phase: deflink: Connected! Dec 11 20:48:20 woodstock ppp[3106]: tun1: Phase: deflink: opening -> carrier Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: Waiting for carrier Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: Waiting for carrier [ and on and on and on ] -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 20: 8:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id BDA1E1510F for ; Sat, 11 Dec 1999 20:08:18 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: (from uucp@localhost) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with UUCP id NAA61645; Sun, 12 Dec 1999 13:08:01 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.9.3/3.7W) with ESMTP id NAA04037; Sun, 12 Dec 1999 13:06:57 +0900 (JST) Date: Sun, 12 Dec 1999 13:06:57 +0900 Message-ID: <14419.8033.52078.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: current@freebsd.org, gandalf@vilnya.demon.co.uk Cc: tanimura@r.dl.itc.u-tokyo.ac.jp Subject: Re: The secondary buffer in pcm channel for DSPs with small DMA buffers In-Reply-To: In your message of "Sat, 11 Dec 1999 18:55:38 +0900" <14418.8090.86742.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> References: <14418.8090.86742.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Carrots MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: multipart/mixed; boundary="Multipart_Sun_Dec_12_13:06:56_1999-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Sun_Dec_12_13:06:56_1999-1 Content-Type: text/plain; charset=US-ASCII On Sat, 11 Dec 1999 18:55:38 +0900, Seigo Tanimura said: Seigo> My CS4614 has got only 4KB of the DMA buffer, frequently failing to Seigo> play pcm blocks continuously. The following patch adds the secondary Seigo> pcm channel buffers with the size independent from that of a DSP. The Seigo> patch works quite well with mpg123 and x11amp. For those who has the Seigo> similar problem could you please try that? A few fixes and updates have been added, including recovery from DMA underflow. The value returned from chn_getptr() in chn_checkunderflow() may get a lag when we get back to chn_write(), which is likely to cause noise. Consider a DMA buffer capable to hold 10 samples, as shown below. DMA buffer 0123456789 Sample ---------- Buffer Pointer R--------- F--------- Playing Point P--------- Since a DMA keeps running even after underflow occurs, P may advance, leaving F. DMA buffer 0123456789 Sample ---------- Buffer Pointer R--------- F--------- Playing Point --P------- If we fill the buffer with new samples in this situation, play begins from somewhere in the middle of the samples. In the case shown below, the sample c is the first one to be played. The sample a and b are played after j, causing noise. DMA buffer 0123456789 Sample abcdefghij Buffer Pointer R--------- F--------- Playing Point --P------- --> cdefghijab In order to avoid the lag, we can advance F upon underflow. A quarter of the DMA buffer size would be fair. DMA buffer 0123456789 Sample --abcdefgh Buffer Pointer R--------- --F------- Playing Point --P------- --> abcdefgh With the following patch, x11amp and mpg123 play with no noise even under an extremely heavy load of more than 50 :) --Multipart_Sun_Dec_12_13:06:56_1999-1 Content-Type: text/plain; type=patch; charset=US-ASCII Content-Disposition: attachment; filename="2ndbuffer.diff" Content-Transfer-Encoding: 7bit Index: channel.c =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/pcm/channel.c,v retrieving revision 1.9 diff -u -r1.9 channel.c --- channel.c 1999/12/05 19:09:12 1.9 +++ channel.c 1999/12/12 03:46:41 @@ -131,9 +131,8 @@ } /* - * chn_dmadone() updates pointers and wakes up any process sleeping - * or waiting on a select(). - * Must be called at spltty(). + * chn_dmadone() updates pointers and wakes up any process waiting + * on a select(). Must be called at spltty(). */ static void chn_dmadone(pcm_channel *c) @@ -142,12 +141,25 @@ chn_dmaupdate(c); if (ISA_DMA(b)) chn_isadmabounce(c); /* sync bounce buffer */ - wakeup(b); b->int_count++; if (b->sel.si_pid && chn_polltrigger(c)) selwakeup(&b->sel); } /* + * chn_dmawakeup() wakes up any process sleeping. Separated from + * chn_dma_done() so that wakeup occurs only when feed from a + * secondary buffer to a DMA buffer takes place. Must be called + * at spltty(). + */ +static void +chn_dmawakeup(pcm_channel *c) +{ + snd_dbuf *b = &c->buffer; + + wakeup(b); +} + +/* * chn_dmaupdate() tracks the status of a dma transfer, * updating pointers. It must be called at spltty(). * @@ -181,8 +193,9 @@ } /* - * Check channel for underflow occured, reset DMA buffer in case of - * underflow. It must be called at spltty(). + * Check channel for underflow occured. Reset DMA buffer in case of + * underflow, so that new data can go into the buffer. It must be + * called at spltty(). */ static void chn_checkunderflow(pcm_channel *c) @@ -191,9 +204,19 @@ if (b->underflow) { DEB(printf("Clear underflow condition\n")); - b->rp = b->fp = chn_getptr(c); - b->rl = 0; - b->fl = b->bufsize; + /* + * The DMA keeps running even after underflow occurs. + * Hence the value returned by chn_getptr() here soon + * gets a lag when we get back to chn_write(). Although + * there are no easy and precise methods to figure out + * the lag, a quarter of b->bufsize would be a fair + * choice, provided that a DMA interrupt generates upon + * each transfer of a half b->bufsize. + */ + b->rp = chn_getptr(c); + b->fp = (b->rp + b->bufsize / 4) % b->bufsize; + b->rl = b->bufsize / 4; + b->fl = b->bufsize - b->rl; b->underflow=0; } else { chn_dmaupdate(c); @@ -201,6 +224,70 @@ } /* + * Feeds new data to the write dma buffer. Can be called in the bottom half. + * Hence must be called at spltty. + */ +static int +chn_wrfeed(pcm_channel *c) +{ + snd_dbuf *b = &c->buffer; + snd_dbuf *bs = &c->buffer2nd; + int a, l, lacc; + + /* ensure we always have a whole number of samples */ + a = (1 << c->align) - 1; + lacc = 0; + /* Don't allow write unaligned data */ + while (bs->rl > a && b->fl > a) { + /* ensure we always have a whole number of samples */ + l = min(min(bs->rl, bs->bufsize - bs->rp), min(b->fl, b->bufsize - b->fp)) & ~a; + if (l == 0) + return lacc; + /* Move the samples, update the markers and pointers. */ + bcopy(bs->buf + bs->rp, b->buf + b->fp, l); + bs->fl += l; + bs->rl -= l; + bs->rp = (bs->rp + l) % bs->bufsize; + b->rl += l; + b->fl -= l; + b->fp = (b->fp + l) % b->bufsize; + /* Accumulate the total bytes of the moved samples. */ + lacc += l; + } + + return lacc; +} + +/* Feeds new data to the secondary write buffer. */ +static int +chn_wrfeed2nd(pcm_channel *c, struct uio *buf) +{ + snd_dbuf *bs = &c->buffer2nd; + int l, w, wacc; + + /* ensure we always have a whole number of samples */ + wacc = 0; + while (buf->uio_resid > 0 && bs->fl > 0) { + /* + * The size of the data to move here does not have to be + * aligned. We take care of it upon moving the data to a + * DMA buffer. + */ + l = min(bs->fl, bs->bufsize - bs->fp); + /* Move the samples, update the markers and pointers. */ + w = c->feeder->feed(c->feeder, c, bs->buf + bs->fp, l, buf); + if (w == 0) panic("no feed"); + bs->rl += w; + bs->fl -= w; + bs->fp = (bs->fp + w) % bs->bufsize; + /* Accumulate the total bytes of the moved samples. */ + wacc += w; + } + + return wacc; +} + +/* * Write interrupt routine. Can be called from other places (e.g. * to start a paused transfer), but with interrupts disabled. */ @@ -222,7 +309,18 @@ * needed when doing stereo and 16-bit. */ if (c->flags & CHN_F_MAPPED) start = c->flags & CHN_F_TRIGGERED; - else start = (b->rl >= DMA_ALIGN_THRESHOLD && !(c->flags & CHN_F_ABORTING)); + else { + /* + * Fill up the DMA buffer. This may result in making new + * free space in the secondary buffer, thus we can wake up + * the top half if feed occurs. + */ + if (chn_wrfeed(c) > 0) { + chn_dmawakeup(c); + while(chn_wrfeed(c) > 0); + } + start = (b->rl >= DMA_ALIGN_THRESHOLD && !(c->flags & CHN_F_ABORTING)); + } if (start) { int l; chn_dmaupdate(c); @@ -237,13 +335,13 @@ /* Start DMA operation */ b->dl = c->blocksize ; /* record new transfer size */ chn_trigger(c, PCMTRIG_START); - } else if (b->dl != l) { + } + if (b->dl != l) /* * we are near to underflow condition, so to prevent - * audio 'clicks' clear next 1.5*dl bytes + * audio 'clicks' clear next b->fl bytes */ - chn_clearbuf(c, (b->dl*3)/2); - } + chn_clearbuf(c, b->fl); } else { /* cannot start a new dma transfer */ DEB(printf("cannot start wr-dma flags 0x%08x rp %d rl %d\n", @@ -274,10 +372,9 @@ int chn_write(pcm_channel *c, struct uio *buf) { - int a, l, w, timeout, ret = 0, rc; + int ret = 0, timeout; long s; snd_dbuf *b = &c->buffer; - int threshold, maxthreshold, minthreshold; if (c->flags & CHN_F_WRITING) { /* This shouldn't happen and is actually silly @@ -286,57 +383,39 @@ tsleep(&s, PZERO, "pcmwrW", hz); return EBUSY; } - a = (1 << c->align) - 1; - maxthreshold = (b->dl / 4 + a) & ~a; - minthreshold = a; c->flags |= CHN_F_WRITING; + /* + * Fill up the secondary and DMA buffer. + * chn_wrfeed*() takes care of the alignment. + */ s = spltty(); + /* Check for underflow before writing into the buffers. */ chn_checkunderflow(c); - splx(s); - while ((buf->uio_resid + c->smegcnt) > minthreshold ) { /* Don't allow write unaligned data */ - threshold = min((buf->uio_resid + c->smegcnt), maxthreshold); - if (b->fl < threshold) { - if (c->flags & CHN_F_NBIO) { - ret = -1; - break; - } - timeout = (buf->uio_resid >= b->dl)? hz : 1; - rc = tsleep(b, PRIBIO | PCATCH, "pcmwr", timeout); - if (rc == 0 || rc == EWOULDBLOCK) { - s = spltty(); - chn_checkunderflow(c); - splx(s); - if (b->fl < minthreshold) continue; /* write only alligned chunk of data */ - } else { -#if 0 - if (ret == EINTR) chn_abort(c); -#endif - ret = rc; - break; - } - } - /* ensure we always have a whole number of samples */ - l = min(b->fl, b->bufsize - b->fp) & ~a; - if (l == 0) continue; - w = c->feeder->feed(c->feeder, c, b->buf + b->fp, l, buf); - KASSERT(w, ("chn_write: no feed")); - s = spltty(); - b->rl += w; - b->fl -= w; - b->fp = (b->fp + w) % b->bufsize; - splx(s); - DEB(if(1) printf("write %d bytes fp %d rl %d\n",w ,b->fp, b->rl)); - if (!b->dl) chn_stintr(c); - } - if ((ret == 0) && (buf->uio_resid > 0)) { - s = spltty(); - l = buf->uio_resid; - KASSERT( (c->smegcnt + l) < SMEGBUFSZ, ("resid overflow %d", l)); - uiomove(c->smegbuf + c->smegcnt, l, buf); - c->smegcnt += l; - splx(s); - } + while (chn_wrfeed2nd(c, buf) > 0 || chn_wrfeed(c) > 0); + /* Start playing if not yet. */ + if (b->rl && !b->dl) chn_wrintr(c); + if (!(c->flags & CHN_F_NBIO)) { + /* Wait until all samples are played in blocking mode. */ + while (buf->uio_resid > 0) { + splx(s); + /* Wait for new free space to write new pcm samples. */ + timeout = (buf->uio_resid >= b->dl)? hz / 20 : 1; + ret = tsleep(b, PRIBIO | PCATCH, "pcmwr", timeout); + s = spltty(); +#if notdef + if (ret == EINTR) chn_abort(c); +#endif /* notdef */ + if (ret == EINTR || ret == ERESTART) break; + /* Check for underflow before writing into the buffers. */ + chn_checkunderflow(c); + /* Fill up the buffers with new pcm data. */ + while (chn_wrfeed2nd(c, buf) > 0 || chn_wrfeed(c) > 0); + /* Start playing if necessary. */ + if (b->rl && !b->dl) chn_wrintr(c); + } + } c->flags &= ~CHN_F_WRITING; + splx(s); return (ret > 0)? ret : 0; } @@ -370,6 +449,65 @@ */ +/* + * Feed new data from the read buffer. Can be called in the bottom half. + * Hence must be called at spltty. + */ +static int +chn_rdfeed(pcm_channel *c) +{ + snd_dbuf *b = &c->buffer; + snd_dbuf *bs = &c->buffer2nd; + int l, lacc; + + /* ensure we always have a whole number of samples */ + lacc = 0; + while (bs->fl >= DMA_ALIGN_THRESHOLD && b->rl >= DMA_ALIGN_THRESHOLD) { + l = min(min(bs->fl, bs->bufsize - bs->fp), min(b->rl, b->bufsize - b->rp)) & DMA_ALIGN_MASK; + /* Move the samples, update the markers and pointers. */ + bcopy(b->buf + b->rp, bs->buf + bs->fp, l); + bs->fl -= l; + bs->rl += l; + bs->fp = (bs->fp + l) % bs->bufsize; + b->rl -= l; + b->fl += l; + b->rp = (b->rp + l) % b->bufsize; + /* Accumulate the total bytes of the moved samples. */ + lacc += l; + } + + return lacc; +} + +/* Feeds new data from the secondary read buffer. */ +static int +chn_rdfeed2nd(pcm_channel *c, struct uio *buf) +{ + snd_dbuf *bs = &c->buffer2nd; + int l, w, wacc; + + /* ensure we always have a whole number of samples */ + wacc = 0; + while (buf->uio_resid > 0 && bs->rl > 0) { + /* + * The size of the data to move here does not have to be + * aligned. We take care of it upon moving the data to a + * DMA buffer. + */ + l = min(bs->rl, bs->bufsize - bs->rp); + /* Move the samples, update the markers and pointers. */ + w = c->feeder->feed(c->feeder, c, bs->buf + bs->rp, l, buf); + if (w == 0) panic("no feed"); + bs->fl += w; + bs->rl -= w; + bs->rp = (bs->rp + w) % bs->bufsize; + /* Accumulate the total bytes of the moved samples. */ + wacc += w; + } + + return wacc; +} + /* read interrupt routine. Must be called with interrupts blocked. */ static void chn_rdintr(pcm_channel *c) @@ -383,7 +521,18 @@ b->dl, b->rp, b->rl, b->fp, b->fl)); /* Restart if have enough free space to absorb overruns */ if (c->flags & CHN_F_MAPPED) start = c->flags & CHN_F_TRIGGERED; - else start = (b->fl > 0x200 && !(c->flags & CHN_F_ABORTING)); + else { + /* + * Suck up the DMA buffer. This may result in making new + * captured data in the secondary buffer, thus we can wake + * up the top half if feed occurs. + */ + if (chn_rdfeed(c) > 0) { + chn_dmawakeup(c); + while (chn_rdfeed(c) > 0); + } + start = (b->fl > 0x200 && !(c->flags & CHN_F_ABORTING)); + } if (start) { int l = min(b->fl - 0x100, c->blocksize); if (c->flags & CHN_F_MAPPED) l = c->blocksize; @@ -431,7 +580,7 @@ int chn_read(pcm_channel *c, struct uio *buf) { - int w, l, timeout, limit, ret = 0; + int ret = 0, timeout, limit; long s; snd_dbuf *b = &c->buffer; @@ -441,33 +590,32 @@ return (EBUSY); } - if (!b->rl & !b->dl) chn_stintr(c); + s = spltty(); c->flags |= CHN_F_READING; limit = buf->uio_resid - c->blocksize; if (limit < 0) limit = 0; - while (buf->uio_resid > limit) { - s = spltty(); - chn_dmaupdate(c); - splx(s); - if (b->rl < DMA_ALIGN_THRESHOLD) { - if (c->flags & CHN_F_NBIO) break; - timeout = (buf->uio_resid - limit >= b->dl)? hz : 1; - ret = tsleep(b, PRIBIO | PCATCH, "pcmrd", timeout); + /* Start capturing if not yet. */ + if (!b->rl & !b->dl) chn_rdintr(c); + /* Suck up the DMA and secondary buffers. */ + while (chn_rdfeed(c) > 0 || chn_rdfeed2nd(c, buf) > 0); + if (!(c->flags & CHN_F_NBIO)) { + /* Wait until all samples are captured. */ + while (buf->uio_resid > 0) { + splx(s); + /* Wait for new pcm samples. */ + timeout = (buf->uio_resid - limit >= b->dl)? hz / 20 : 1; + ret = tsleep(b, PRIBIO | PCATCH, "pcmrd", timeout); + s = spltty(); if (ret == EINTR) chn_abort(c); if (ret == EINTR || ret == ERESTART) break; - ret = 0; - continue; + /* Start capturing if necessary. */ + if (!b->rl & !b->dl) chn_rdintr(c); + /* Suck up the DMA and secondary buffers. */ + while (chn_rdfeed(c) > 0 || chn_rdfeed2nd(c, buf) > 0); } - /* ensure we always have a whole number of samples */ - l = min(b->rl, b->bufsize - b->rp) & DMA_ALIGN_MASK; - w = c->feeder->feed(c->feeder, c, b->buf + b->rp, l, buf); - s = spltty(); - b->rl -= w; - b->fl += w; - b->rp = (b->rp + w) % b->bufsize; - splx(s); } c->flags &= ~CHN_F_READING; + splx(s); return ret; } @@ -534,6 +682,7 @@ chn_resetbuf(pcm_channel *c) { snd_dbuf *b = &c->buffer; + snd_dbuf *bs = &c->buffer2nd; c->smegcnt = 0; c->buffer.sample_size = 1; @@ -547,6 +696,9 @@ b->prev_int_count = b->int_count = 0; b->first_poll = 1; b->underflow=0; + bs->rp = bs->fp = 0; + bs->dl = bs->rl = 0; + bs->fl = bs->bufsize; } void @@ -631,6 +783,7 @@ long s; int missing = 0; snd_dbuf *b = &c->buffer; + snd_dbuf *bs = &c->buffer2nd; s = spltty(); if (b->dl) { @@ -639,7 +792,7 @@ chn_trigger(c, PCMTRIG_ABORT); chn_dmadone(c); } - missing = b->rl; + missing = b->rl + bs->rl; splx(s); return missing; } @@ -708,11 +861,18 @@ int chn_init(pcm_channel *c, void *devinfo, int dir) { + snd_dbuf *bs = &c->buffer2nd; + c->flags = 0; c->feeder = &feeder_root; c->buffer.chan = -1; c->devinfo = c->init(devinfo, &c->buffer, c, dir); chn_setdir(c, dir); + bs->bufsize = CHN_2NDBUFBLKSIZE * CHN_2NDBUFBLKNUM; + bs->buf = malloc(bs->bufsize, M_DEVBUF, M_NOWAIT); + bzero(bs->buf, bs->bufsize); + bs->rl = bs->rp = bs->fp = 0; + bs->fl = bs->bufsize; return 0; } Index: channel.h =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/pcm/channel.h,v retrieving revision 1.3 diff -u -r1.3 channel.h --- channel.h 1999/09/28 21:43:34 1.3 +++ channel.h 1999/12/12 03:46:41 @@ -79,3 +79,12 @@ #define CHN_F_RESET (CHN_F_BUSY) + +/* + * This should be large enough to hold all pcm data between + * tsleeps in chn_{read,write} at the highest sample rate. + * (which is usually 48kHz * 16bit * stereo = 192000 bytes/sec) + */ +#define CHN_2NDBUFBLKSIZE (12 * 1024) +/* The total number of blocks per secondary buffer. */ +#define CHN_2NDBUFBLKNUM (3) Index: datatypes.h =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/pcm/datatypes.h,v retrieving revision 1.6 diff -u -r1.6 datatypes.h --- datatypes.h 1999/12/12 02:18:57 1.6 +++ datatypes.h 1999/12/12 03:46:41 @@ -127,6 +127,7 @@ u_int8_t smegbuf[SMEGBUFSZ]; u_int32_t smegcnt; void *devinfo; + snd_dbuf buffer2nd; }; typedef void (pcm_swap_t)(void *data, int dir); Index: dsp.c =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/pcm/dsp.c,v retrieving revision 1.11 diff -u -r1.11 dsp.c --- dsp.c 1999/12/12 02:18:57 1.11 +++ dsp.c 1999/12/12 03:46:41 @@ -325,7 +325,7 @@ #define THE_REAL_SNDCTL_DSP_GETBLKSIZE _IOWR('P', 4, int) case THE_REAL_SNDCTL_DSP_GETBLKSIZE: case SNDCTL_DSP_GETBLKSIZE: - *arg_i = wrch? wrch->blocksize : 0; /* XXX rdch? */ + *arg_i = CHN_2NDBUFBLKSIZE; break ; case SNDCTL_DSP_SETBLKSIZE: -- Seigo Tanimura --Multipart_Sun_Dec_12_13:06:56_1999-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 20:19: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs0.catv.ne.jp (cs0.catv.ne.jp [202.232.171.20]) by hub.freebsd.org (Postfix) with ESMTP id 0601714C8B; Sat, 11 Dec 1999 20:18:57 -0800 (PST) (envelope-from nyan@dd.catv.ne.jp) Received: from localhost by cs0.catv.ne.jp (8.9.1/3.7W) id NAA24846; Sun, 12 Dec 1999 13:17:51 +0900 (JST) To: marcel@scc.nl, msmith@freebsd.org Cc: current@FreeBSD.org Subject: Re: make world is failed on pc98 In-Reply-To: <38526700.70C5CBF@scc.nl> References: <19991211230552P.nyan@dd.catv.ne.jp> <38526700.70C5CBF@scc.nl> <199912120121.RAA00570@mass.cdrom.com> From: Takahashi Yoshihiro X-Mailer: Mew version 1.94 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991212131847U.nyan@dd.catv.ne.jp> Date: Sun, 12 Dec 1999 13:18:47 +0900 (JST) X-Dispatcher: imput version 990905(IM130) Lines: 25 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <38526700.70C5CBF@scc.nl> Marcel Moolenaar writes: > Other than that: Go ahead! Thank you for many comments. > BTW: Is there a special reason to have boot2 in aout? Because nobody transplant from the i386 boot2 :-). FreeBSD(98) porting team is always suffering from a shortage of workers. In article <199912120121.RAA00570@mass.cdrom.com> Mike Smith writes: > Only in the longer term, I think. How hard would it be to port the 'new' > i386 boot2? There are few people who are knowledgeable about pc98 boot sequence. And that we all have our regular work. So, it is very difficult to port the i386 boot2 to pc98. --- Takahashi Yoshihiro / nyan@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 21:49:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from m08.alpha-net.ne.jp (m08.alpha-net.ne.jp [210.229.64.38]) by hub.freebsd.org (Postfix) with ESMTP id 5627414E83 for ; Sat, 11 Dec 1999 21:49:25 -0800 (PST) (envelope-from k5@cheerful.com) Received: from kyoto-p11.alpha-net.ne.jp (kyoto-p11.alpha-net.ne.jp [210.237.118.11]) by m08.alpha-net.ne.jp (8.9.3/3.7W) with ESMTP id OAA05950 for ; Sun, 12 Dec 1999 14:49:15 +0900 (JST) Received: from souffle.bogus-local.net (souffle.bogus-local.net [192.168.1.1]) by kyoto-p11.alpha-net.ne.jp (Postfix) with ESMTP id 63ABA3EE3; Sun, 12 Dec 1999 14:49:11 +0900 (JST) Date: Sun, 12 Dec 1999 14:49:13 +0900 Message-ID: <14419.14169.298803.72159A@cheerful.com> From: FUJISHIMA Satsuki To: Greg Lehey Cc: current@freebsd.org Subject: vinum start needs block device User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) Emacs/20.4 (i386--freebsd) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Greg, Since the recent block device vanishment, MAKEDEV all and my vinum volumes have failed to start. # ls -l da[01]s1h crw-r----- 1 root operator 13, 0x00020007 Dec 12 22:56 da0s1h crw-r----- 1 root operator 13, 0x0002000f Dec 12 22:56 da1s1h # vinum start ** no drives found: No such file or directory # And, remaking old block device nodes vinum successfully starts again. # ./MAKEDEV.1.223 da0s1h da1s1h # ls -l da[01]s1h brw-r----- 1 root operator 4, 0x00020007 Dec 12 22:57 da0s1h brw-r----- 1 root operator 4, 0x0002000f Dec 12 22:57 da1s1h # vinum start vinum: reading configuration from /dev/da0s1h vinum: updating configuration from /dev/da1s1h # I'd be happy with this behavior to be corrected before -release. -- FUJISHIMA Satsuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 21:58:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id C534514F12 for ; Sat, 11 Dec 1999 21:58:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA06108; Sat, 11 Dec 1999 21:58:51 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: FUJISHIMA Satsuki Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: vinum start needs block device In-reply-to: Your message of "Sun, 12 Dec 1999 14:49:13 +0900." <14419.14169.298803.72159A@cheerful.com> Date: Sat, 11 Dec 1999 21:58:51 -0800 Message-ID: <6104.944978331@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Since the recent block device vanishment, MAKEDEV all and my vinum > volumes have failed to start. Please read /usr/src/UPDATING if you're going to track -current these days. The reason for this is clearly documented at the top of that file and won't be a problem in -release since the correct device nodes will be created initially. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 22:42:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 09F7E14F9A for ; Sat, 11 Dec 1999 22:42:30 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id WAA77398; Sat, 11 Dec 1999 22:42:26 -0800 (PST) Date: Sat, 11 Dec 1999 22:42:25 -0800 (PST) From: Julian Elischer To: "Jordan K. Hubbard" Cc: John Robert LoVerso , freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree In-Reply-To: <92094.944950375@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 Linux have basically done this in their procfs. On Sat, 11 Dec 1999, Jordan K. Hubbard wrote: > > Use a similar hack: map the sysctl tree to the filesystem (ala kernfs) and > > then stat the directory nodes. > > AAIEEEEEE! sysctlfs!! :-) > > It's an interesting idea and I'm not sure why it also horrifies me at > some inner, almost cellular, level. If somebody's actually willing to > do the work of creating such a thing, however, I'll probably get over > it. :) > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 22:56:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0E8F414F12; Sat, 11 Dec 1999 22:56:40 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA63651; Sat, 11 Dec 1999 23:56:35 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA36980; Sat, 11 Dec 1999 23:56:34 -0700 (MST) Message-Id: <199912120656.XAA36980@harmony.village.org> To: obrien@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Cc: "Kenneth D. Merry" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 11 Dec 1999 13:23:16 PST." <19991211132316.D14998@dragon.nuxi.com> References: <19991211132316.D14998@dragon.nuxi.com> <199912110239.MAA01680@nymph.detir.qld.gov.au> <199912110422.VAA00723@panzer.kdm.org> Date: Sat, 11 Dec 1999 23:56:34 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991211132316.D14998@dragon.nuxi.com> "David O'Brien" writes: : On Fri, Dec 10, 1999 at 09:22:55PM -0700, Kenneth D. Merry wrote: : > And as for the device renaming, you didn't have to change anything from : > sd->da. The old device names and nodes were supported in most every way. : : BUT not any longer. Thus we have no choice but fully make the sd->da : change. [David says this as last weekend he had to change fstabs and : /dev for 5 of his machines] Are you sure this isn't just for "special" devices (eg root, default swap and the like)? I have a machine where da0 is root, but my jaz drive is sd1c which is running a kernel that post-dates the sd removal from the kernel. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 23: 2:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7EFDE14D68; Sat, 11 Dec 1999 23:02:32 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA63670; Sun, 12 Dec 1999 00:02:30 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA37006; Sun, 12 Dec 1999 00:02:30 -0700 (MST) Message-Id: <199912120702.AAA37006@harmony.village.org> To: obrien@FreeBSD.ORG Subject: Re: HEADSUP: wd driver will be retired! Cc: Poul-Henning Kamp , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 11 Dec 1999 13:55:48 PST." <19991211135548.E14998@dragon.nuxi.com> References: <19991211135548.E14998@dragon.nuxi.com> <19991210160247.DF62D1CA0@overcee.netplex.com.au> <5461.944842529@critter.freebsd.dk> Date: Sun, 12 Dec 1999 00:02:30 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991211135548.E14998@dragon.nuxi.com> "David O'Brien" writes: : 2. Fix PCCARD on my laptop so I can suspend What's the current issue? I have 0 problems suspending/resuming. I'd like to know what is still broken, if anything, with the latest -current. : OR, I can work on the compiler and close my open PRs. Of course if I : simply don't update my machine for 3 months, god knows if my compiler : changes won't break world or cause other problems. Actually, the put up or shut up argument doesn't apply to people that have done and continue to do a significant amount of work in other areas. At least I would be greatly offended if someone hit me with it in an area other than security or pccard when I complained about (and helped to diagnose) a problem in their area of code. Me, I'm tired of maintaining the old pccard code while writing new, but I know it has to be done... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 23: 6:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DEE0214E53 for ; Sat, 11 Dec 1999 23:06:36 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA63683; Sun, 12 Dec 1999 00:06:34 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA37029; Sun, 12 Dec 1999 00:06:30 -0700 (MST) Message-Id: <199912120706.AAA37029@harmony.village.org> To: Kenneth Wayne Culver Subject: Re: rtc0 Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 11 Dec 1999 20:05:40 EST." References: Date: Sun, 12 Dec 1999 00:06:30 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kenneth Wayne Culver writes: : For some reason rtc0 was not working, and I think it's because this : variable was not initialized, here is the patch: : -int statclock_disable; : +int statclock_disable = 0; There is no difference between these two statements (well, other than statclock_disable moves from the bss area, which is zeroed, to a location in .data, which is zeroed). This cannot be the problem, although it may appear to fix it. It may be the case that some other buffer is overflowing into this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 23:12:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 44B5F150CC; Sat, 11 Dec 1999 23:12:09 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA63703; Sun, 12 Dec 1999 00:12:07 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA37066; Sun, 12 Dec 1999 00:12:07 -0700 (MST) Message-Id: <199912120712.AAA37066@harmony.village.org> To: Mike Smith Subject: Re: HEADSUP: wd driver will be retired! Cc: Lyndon Nerenberg , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 11 Dec 1999 17:41:25 PST." <199912120141.RAA00880@mass.cdrom.com> References: <199912120141.RAA00880@mass.cdrom.com> Date: Sun, 12 Dec 1999 00:12:07 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912120141.RAA00880@mass.cdrom.com> Mike Smith writes: : This is the usual poorly thought out argument, which fails to note that : when you lose a disk you're already screwed due by /etc/fstab and the : need to hard-mount local filesystems. No. You aren't screwed. I have a system that needs /, /var, /usr and /usr/local (all on one disk) to boot, but puts the fsck/mount of all the other file systems into the background. If one of them fails, all the others are still available. : The "right" solution is and has always been to name your disks and mount : them by name. Once devfs is a reality, we'll be able to do just this. : Until then, the problem's not really as bad as you make it out to be. I'd have to disagree with this. I was constantly getting burned by the scsi system until I started hard wiring my scsi disks. The JAZ drive I have had a period in its life when sometimes it wouldn't power on (due to a bad power connection it was later discovered), so sometimes at boot the system would see it and sometimes not. My /jaz partition would wound up being where my /big partition should be and my /big partition wouldn't be there at all when this happened. After hardwiring, /jaz was the only one affected. The same issue is there with ethernet interfaces too, btw. I have a server that has 2 single fxp cards and 4 dual fxp cards. We need to replace one of the single fxp cards with a dual one (no more slots and need another interface), but to do this will require lots of renumbering/cable shuffle, etc because ALL the interface numbers will change when we do this. I'm not convinced that the "right" solution is really "right" here. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 11 23:16:24 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id CC0E41502B; Sat, 11 Dec 1999 23:16:17 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B92C71CD626; Sat, 11 Dec 1999 23:16:17 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 11 Dec 1999 23:16:17 -0800 (PST) From: Kris Kennaway To: Julian Elischer Cc: "Jordan K. Hubbard" , John Robert LoVerso , freebsd-current@FreeBSD.ORG Subject: Re: Modules and sysctl tree 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, 11 Dec 1999, Julian Elischer wrote: > Linux have basically done this in their procfs. If we're looking for a gross hack, we need look no further :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message