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