Re: Update to UFS2 Superblock Format
Date: Fri, 29 Nov 2002 23:16:51 -0800 To: Kirk McKusick <[EMAIL PROTECTED]> From: Manfred Antar <[EMAIL PROTECTED]> Subject: Re: Update to UFS2 Superblock Format Cc: [EMAIL PROTECTED], Robert Watson <[EMAIL PROTECTED]>, [EMAIL PROTECTED], Poul-Henning Kamp <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> X-ASK-Info: Whitelist match At 11:11 PM 11/29/2002 -0800, Kirk McKusick wrote: >You will have to ask Puol-Henning Kamp, but I do not believe that >he has yet put together a bootstrap for the i386 platform that can >boot from a UFS2 filesystem. As such, I believe that you are >required to have a UFS1 root on the i386 at this time. I have >copied Poul-Henning Kamp so that he can correct me if I am incorrect >on this point. > >Kirk McKusick Ah No wonder, I tried editing the /sys/boot/i386/boot2/Makefile to enable UFS2 bootblock but then disklabel complained that boot2 was too big. I will have to revert to UFS1 Thanks Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == You have hit upon the exact problem. UFS2 has a much bigger area reserved for the boot block, but the programs that set up disk labels and boot blocks don't know about it yet so assume that they have to cram into the much smaller UFS1 boot-block area. Kirk McKusick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Update to UFS2 Superblock Format
At 11:11 PM 11/29/2002 -0800, Kirk McKusick wrote: >You will have to ask Puol-Henning Kamp, but I do not believe that >he has yet put together a bootstrap for the i386 platform that can >boot from a UFS2 filesystem. As such, I believe that you are >required to have a UFS1 root on the i386 at this time. I have >copied Poul-Henning Kamp so that he can correct me if I am incorrect >on this point. > >Kirk McKusick Ah No wonder, I tried editing the /sys/boot/i386/boot2/Makefile to enable UFS2 bootblock but then disklabel complained that boot2 was too big. I will have to revert to UFS1 Thanks Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-DP2 questions
On Fri, 29 Nov 2002, David Syphers wrote: > On Friday 29 November 2002 12:12 pm, Kris Kennaway wrote: > > On Fri, Nov 29, 2002 at 12:11:42PM -0500, Robert Ames wrote: > > > > > 2. My machine is a Pentium 166 with only 16 MB of RAM. I'm trying > > > to rebuild the kernel and so far the compile has been running for > > > almost 24 hours and it's not finished yet. Is this to be expected? > > > > Yes. gcc 3.x is slower, and the kernel contains more code. Your > > machine is probably swapping a lot just doing the compilation, which > > will make it even slower. > > Out of curiosity, how much slower is a 5.x kernel compilation than a 4.x, on > average? I'm not sure about 4.x, but a -current kernel with no modules takes about 3 times as long as a RELENG_3 kernel compiled by the 4.x compiler used to take (about 130 seconds instead of 43 seconds on an Athlon 1600 overclocked. The kernels are supposed to have a similar set of options. All times are all times are after running "make depend" which takes about 8 seconds for RELENG_3 and 11 seconds for -current. gcc-3 in April 2002 pessimized the compile times from 76 seconds to 114 seconds for -current and from 43 seconds to 66 seconds for RELENG_3. Further development of -current pessimized the compile time from 114 seconds to 130 seconds. Compiling LINT took 437 seconds on Sep 22. IIRC, compiling modules takes about the same time as compiling LINT. > My 486, 66 MHz and 16 MB RAM, compiles a 4.x kernel in about 3 > hours. Thus by Robert's data point, -current seems at least 10-15 times > slower... Ouch. I remember being happy when upgrading from a 486/33 with 16MB to a 486DX2/66 with 32MB reduced my kernel compile time from about 16 minutes to about 9 minutes. Your 16MB of RAM is probably not nearly enough for today's bloat. Look at the real, user and system times and systat/vmstat/top to see if there is a lot of idle time caused by waiting for disks and/or paging to disk. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Update to UFS2 Superblock Format
You will have to ask Puol-Henning Kamp, but I do not believe that he has yet put together a bootstrap for the i386 platform that can boot from a UFS2 filesystem. As such, I believe that you are required to have a UFS1 root on the i386 at this time. I have copied Poul-Henning Kamp so that he can correct me if I am incorrect on this point. Kirk McKusick =-=-=-=-=-= Date: Fri, 29 Nov 2002 22:57:12 -0800 To: Kirk McKusick <[EMAIL PROTECTED]>, [EMAIL PROTECTED] From: Manfred Antar <[EMAIL PROTECTED]> Subject: Re: Update to UFS2 Superblock Format Cc: Robert Watson <[EMAIL PROTECTED]>, [EMAIL PROTECTED] In-Reply-To: <[EMAIL PROTECTED]> X-ASK-Info: Confirmed by User At 09:11 PM 11/24/2002 -0800, Kirk McKusick wrote: >On Tuesday Nov 26th I plan to make an update to the UFS2 >superblock. It will not affect UFS1 filesystems so should >be generally transparent to most -current users. For those >using UFS2 filesystems, the new kernel will update the >superblock to the new format the first time that your UFS2 >filesystem is mounted read-write. Once updated it will not >be able to be mounted by older kernels unless the `zapsb' >program (see below) is run to revert it to the old format. > >The only really noticable problem arises when you are booting >from a UFS2 root partition. Here, you must follow the following >steps: > >1) boot new kernel >2) mount -u / >3) install new bootstrap > >Once the new kernel has converted the filesystem format for the >root partition, the old bootstrap will no longer recognize it, so >if you do not have a new bootstrap, you will no longer be able to >boot from it. Note that you cannot update to the new bootstrap >until the filesystem has been converted as the new bootstrap will >not recognize the old superblock format. Again, this change will >only affect you if you are using a UFS2 filesystem as your root >filesystem. > >The changes that I plan to apply can be viewed at: > >http://www.freebsd.org/~mckusick/UFS2_update.diffs > >The program `zapsb.c' that reverts a UFS2 filesystem to its >previous state can be found at: > >http://www.freebsd.org/~mckusick/zapsb.c > >If this change is going to cause you undue hardship, please >send me mail ([EMAIL PROTECTED]). > >Kirk McKusick > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message Kirk With a kernel and system current as of Thurs night. I did a dump of / , /var , /usr filesystems. I did a disklabel -B da0s1 I did a make release and booted off the cdrom. went into the fixit mode and did newfs -O2 /dev/da0s1a (root) /dev/da0s1e (/var) /dev/da0s1f (/usr) I then did a restore of the file systems. when i reboot somehow the bootstrap bypasses /boot/loader Here is what I see on the screen /boot.config -P Invalid format >>FreeBSD/i386/UFS1 BOOT Default: 0:da(0,a)/kernel boot: WARNING: loader(8) metadata is missing! I have a current kernel in the / directory so it boots that and I get to the: mountroot>and do mountroot> ufs:da0s1a I guess what ineed to know is how to install the UFS2 bootblocks Thanks Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trashed Disk Labels
Date: Sat, 30 Nov 2002 17:43:53 +1100 (EST) From: Bruce Evans <[EMAIL PROTECTED]> X-X-Sender: [EMAIL PROTECTED] To: Kirk McKusick <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] Subject: Re: Trashed Disk Labels In-Reply-To: <[EMAIL PROTECTED]> X-ASK-Info: Whitelist match On Fri, 29 Nov 2002, Kirk McKusick wrote: > I have had a report of a disk label getting trashed after booting > up to a kernel with the new UFS2 superblock format. I have just > checked in an update to ufs/ffs/ffs_vfsops.c (version 1.198) that > explicitly checks to make sure that it will not trash your disk > label. I highly recommend that you update to this version, even if > you are only running with UFS1 filesystems. Labels should be write protected, but this seems to have been broken by GEOM. Bruce Disk labels certainly used to be write protected. Not sure when that stopped, but it certainly would have been useful in this recent context. Kirk McKusick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Update to UFS2 Superblock Format
At 09:11 PM 11/24/2002 -0800, Kirk McKusick wrote: >On Tuesday Nov 26th I plan to make an update to the UFS2 >superblock. It will not affect UFS1 filesystems so should >be generally transparent to most -current users. For those >using UFS2 filesystems, the new kernel will update the >superblock to the new format the first time that your UFS2 >filesystem is mounted read-write. Once updated it will not >be able to be mounted by older kernels unless the `zapsb' >program (see below) is run to revert it to the old format. > >The only really noticable problem arises when you are booting >from a UFS2 root partition. Here, you must follow the following >steps: > >1) boot new kernel >2) mount -u / >3) install new bootstrap > >Once the new kernel has converted the filesystem format for the >root partition, the old bootstrap will no longer recognize it, so >if you do not have a new bootstrap, you will no longer be able to >boot from it. Note that you cannot update to the new bootstrap >until the filesystem has been converted as the new bootstrap will >not recognize the old superblock format. Again, this change will >only affect you if you are using a UFS2 filesystem as your root >filesystem. > >The changes that I plan to apply can be viewed at: > >http://www.freebsd.org/~mckusick/UFS2_update.diffs > >The program `zapsb.c' that reverts a UFS2 filesystem to its >previous state can be found at: > >http://www.freebsd.org/~mckusick/zapsb.c > >If this change is going to cause you undue hardship, please >send me mail ([EMAIL PROTECTED]). > >Kirk McKusick > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message Kirk With a kernel and system current as of Thurs night. I did a dump of / , /var , /usr filesystems. I did a disklabel -B da0s1 I did a make release and booted off the cdrom. went into the fixit mode and did newfs -O2 /dev/da0s1a (root) /dev/da0s1e (/var) /dev/da0s1f (/usr) I then did a restore of the file systems. when i reboot somehow the bootstrap bypasses /boot/loader Here is what I see on the screen /boot.config -P Invalid format >>FreeBSD/i386/UFS1 BOOT Default: 0:da(0,a)/kernel boot: WARNING: loader(8) metadata is missing! I have a current kernel in the / directory so it boots that and I get to the: mountroot>and do mountroot> ufs:da0s1a I guess what ineed to know is how to install the UFS2 bootblocks Thanks Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make regression tests and 4.x cross-builds
One of the big problems is that install gives a bogus error message when it can't unlink /usr/bin/make because it's non-root. Since there's no way that I'm going to suggest changing install's behavior this late in the release cycle, can we at least make buildworld's "make" target ensure that you're root, and avoid install's bogus error? Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: suggested WARNS makefile magic
On Fri, 29 Nov 2002, Poul-Henning Kamp wrote:
> Right now, if I want to ensure that a particular program compiles
> with a WARNS level of no less than 3, I have to put this in the
> Makefile:
>
> WARNS?= 3
> .if ${WARNS} < 3
> WARNS= 3
> .endif
Only in broken Makefiles. WARNS?= 3 should work in all cases (except
when WARNS is set at a higher level, e.g., on the command line, in
which case the setter really wants that level and individual makefiles
should not override it). Makefiles may be broken by including
../Makefile.inc before setting WARNS, in which case the setting may
be obained from ../Makefile.inc and any setting in the Makefile is
bogus. Another common error is "WARNS= 3" to break any setting at
a higher level.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Trashed Disk Labels
On Fri, 29 Nov 2002, Kirk McKusick wrote: > I have had a report of a disk label getting trashed after booting > up to a kernel with the new UFS2 superblock format. I have just > checked in an update to ufs/ffs/ffs_vfsops.c (version 1.198) that > explicitly checks to make sure that it will not trash your disk > label. I highly recommend that you update to this version, even if > you are only running with UFS1 filesystems. Labels should be write protected, but this seems to have been broken by GEOM. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA patches for PC98 - Please test!
In article <[EMAIL PROTECTED]>
Soeren Schmidt <[EMAIL PROTECTED]> writes:
> I'm trying to get this into 5.0 (I know its late, but life's tough)
>
> This brings ATA support to the PC98 arch will all bells and whistles.
> --- sys/conf/files28 Nov 2002 01:17:48 - 1.738
> +++ sys/conf/files28 Nov 2002 20:01:52 -
> @@ -290,6 +290,7 @@
> dev/asr/asr.coptional asr pci
> dev/ata/ata-all.coptional ata
> dev/ata/ata-isa.coptional ata isa
> +dev/ata/ata-cbus.c optional ata pc98
This should be 'dev/ata/ata-cbus.c optional ata isa' and moved into
files.pc98.
> --- sys/pc98/conf/GENERIC 31 Oct 2002 12:14:05 - 1.220
> +++ sys/pc98/conf/GENERIC 27 Nov 2002 10:06:46 -
> @@ -78,11 +78,18 @@
> # Floppy drives
> device fdc
>
> -# IDE controller and disks
> -device wdc 1
> +# ATA and ATAPI devices
> +device ata
> +device atadisk # ATA disk drives
> +device atapicd # ATAPI CDROM drives
> +device atapifd # ATAPI floppy drives
> +device atapist # ATAPI tape drives
> +options ATA_STATIC_ID # Static device numbering
>
> +# IDE controller and disks
> +#device wdc 1
> # ATAPI devices on wdc
> -device wcd 1 #IDE CD-ROM
> +#device wcd 1 #IDE CD-ROM
> #device wfd 1 #IDE Floppy (e.g. LS-120)
> #device wst 1 #IDE Tape (e.g. Travan)
What about GENERIC.hints?
> --- /dev/null Fri Nov 29 21:35:31 2002
> +++ sys/dev/ata/ata-cbus.cThu Oct 31 19:32:25 2002
> @@ -0,0 +1,270 @@
> +/*-
> + * Copyright (c) 2002 Søren Schmidt <[EMAIL PROTECTED]>
> + * All rights reserved.
The original author of this file is IMAI Takeshi. Where is his
copyright?
> +static int
> +ata_cbus_attach(device_t dev)
> +{
> +struct ata_cbus_controller *scp = device_get_softc(dev);
> +int rid;
> +
> +/* allocate resources */
> +rid = ATA_IOADDR_RID;
> +scp->io = isa_alloc_resourcev(dev, SYS_RES_IOPORT, &rid, ata_pc98_ports,
> + ATA_IOSIZE, RF_ACTIVE);
> +if (!scp->io)
> + return ENOMEM;
> +isa_load_resourcev(scp->io, ata_pc98_ports, ATA_IOSIZE);
> +
> +rid = ATA_IOADDR_RID + ATA_IOSIZE + 1;
> +scp->altio = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid,
> + rman_get_start(scp->io)+ATA_PC98_ALTOFFSET,
> + ~0, ATA_ALTIOSIZE, RF_ACTIVE);
> +if (!scp->altio)
> + return ENOMEM;
> +
> +rid = ATA_IOADDR_RID + ATA_IOSIZE + ATA_ALTIOSIZE + 1;
> +scp->bankio = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid,
> + ATA_PC98_BANK, ~0,
> + ATA_PC98_BANKIOSIZE, RF_ACTIVE);
> +if (!scp->bankio)
> + return ENOMEM;
> +
> +rid = 0;
> +scp->irq = bus_alloc_resource(dev, SYS_RES_IRQ, &rid,
> + 0, ~0, 1, RF_ACTIVE | RF_SHAREABLE);
> +
> +scp->current_bank = -1;
> +if (!device_add_child(dev, "ata", 0))
> + return ENOMEM;
> +if (!device_add_child(dev, "ata", 1))
> + return ENOMEM;
> +
> +return bus_generic_attach(dev);
> +}
Where is vaild bank checking code?
And, what about all atapi-* changes? These changes are needed to
support buggy atapi devices.
---
TAKAHASHI Yoshihiro <[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: [acpi-jp 2004] ACPI errors w/ latest ACPI code on GA BX2000based system
Hi, > A freshly built system with Now 28 sources now throws the ACPI errors > seen in the dmesg output. The former ACPI snapshot did not complain in > any way on this system. [snip] > > ACPI-0438: *** Error: Looking up [FAN_] in namespace, AE_NOT_FOUND > > ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND I think that this was caused by the following spec changes. >From CHANGES.txt: 22 October 2002. Summary of changes for version 20021022. 1) ACPI CA Core Subsystem: Implemented a restriction on the Scope operator that the target must already exist in the namespace at the time the operator is encountered (during table load or method execution). In other words, forward references are not allowed and Scope() cannot create a new object. This changes the previous behavior where the interpreter would create the name if not found. This new behavior correctly enables the search-to-root algorithm during namespace lookup of the target name. Because of this upsearch, this fixes the known Compaq _SB_.OKEC problem and makes both the AML interpreter and iASL compiler compatible with other ACPI implementations. Could you send your acpidump output to this acpi-jp ML? Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make regression tests and 4.x cross-builds
>The sparc64 tinderbox is running a stale world (about 3 months old), >so it's hitting the same problem. I'm running a not-so-stale world (19 days old) and hitting the same problem. Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem pulling particular directory from CVS
At 1:27 PM -0800 2002/11/29, Paul A. Scott wrote: Damn. I keep forgetting about the Mac OSX stupid, case-insesitive HFS+. Yeah, I've bitched about this for years. I mean, HFS was an improvement over MFS (can you imagine a filesystem structure that keeps everything at one level and doesn't use directories at all?), but they really blew chunks on this. Of course, HFS+ is only a minor improvement over HFS. But then, HFS is way, way better than MS-DOS 8.3, which is what it was being compared with at the time. Ya know, Apple stated on their Web site, "there is never any good reason to have a case-sensitive file system." Can you believe that? I wrote back to them and stated, "there is never any good reason to have a case-INsensitive filesystem." But, of course, they never replied. :) Try bitching at Jordan. Maybe he can get them to fix UFS instead. -- Brad Knowles, <[EMAIL PROTECTED]> "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
could sleep with pcm0:mixer
Hi all, Source upgraded my laptop to current a little while ago. Generally it has been quite solid though there are a couple of niggles, since upgrade and with a recent cvsup. Machine is a Dell Inspiron 4000 laptop: [cameron@opal]$ uname -a FreeBSD opal.macaroon.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Nov 29 21:25:40 GMT 2002 root@:/usr/obj/usr/src/sys/GENERIC i386 Upon booting the following messages are displayed: pcm0: port 0xc800-0xc8ff mem 0xf9ffe000-0xf9ff irq 5 at device 8.0 on pci0 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 These have been there since the upgrade and originally I wasn't sure what they were and just ignored them :) However, the computer has occasionally been locking up so that I can't even break into the debugger, (no serial console). I had also stupidly compiled out witness support though that is back in now as I am running with a generic kernel. I noticed that a couple of days ago the following went into the tree: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=496485+0+current/cvs-all I have cvsup'd since then and have verified that the above is in my local tree but the could sleep messages still appear. I am no coder but would be happy to help in whatever way I can if required. Alternativly if the messages are harmless then don't hesitate to tell me to shut up! Other point is I am seeing this pop up on the console quite a bit: Nov 30 00:29:21 opal kernel: psmintr: out of sync (00c0 != ). Nov 30 00:29:21 opal kernel: psmintr: discard a byte (14). Nov 30 00:29:21 opal kernel: psmintr: out of sync (00c0 != ). Nov 30 00:29:21 opal kernel: psmintr: discard a byte (15). Nov 30 00:29:27 opal kernel: psmintr: out of sync (0080 != ). Nov 30 00:29:27 opal kernel: psmintr: discard a byte (16). Nov 30 00:29:27 opal kernel: psmintr: out of sync (0080 != ). Nov 30 00:29:27 opal kernel: psmintr: discard a byte (17). Nov 30 00:29:27 opal kernel: psmintr: out of sync (0080 != ). Nov 30 00:29:27 opal kernel: psmintr: discard a byte (18). Not sure if it is related or not. Full dmesg is attached if it helps. Cameron Murdoch Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri Nov 29 21:25:40 GMT 2002 root@:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc06d3000. Preloaded elf module "/boot/kernel/snd_maestro3.ko" at 0xc06d30a8. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc06d315c. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06d3208. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 851934223 Hz CPU: Pentium III/Pentium III Xeon/Celeron (851.93-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383f9ff real memory = 402501632 (383 MB) avail memory = 383660032 (365 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 9 entries at 0xc00fbd70 Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf000-0xf3ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) cbb0: at device 3.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib0: slot 3 INTA is routed to irq 11 cbb1: at device 3.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pcib0: slot 3 INTA is routed to irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x860-0x86f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0
(no subject)
FreeBSD-CURRENT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Network is crazy slow in DP2
"ps auwwx | grep fsck" only shows the grep command itself, so there's no background fsck running. The output of "top -S -I -s1" shows this when transferring a file thru FTP: last pid: 33023; load averages: 1.00, 1.00, 1.00up 0+16:47:00 19:44:30 72 processes: 2 running, 62 sleeping, 8 waiting CPU states: 0.8% user, 0.0% nice, 1.9% system, 3.7% interrupt, 93.6% idle Mem: 41M Active, 54M Inact, 50M Wired, 32K Cache, 35M Buf, 103M Free Swap: 520M Total, 196K Used, 520M Free PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 11 root -160 0K12K RUN885:02 92.53% 92.53% idle 12 root -44 -163 0K12K WAIT19:56 2.78% 2.78% swi1: net 33009 root 40 1736K 1208K sbwait 0:00 0.18% 0.15% ftpd 33 root 200 0K12K syncer 1:50 0.05% 0.05% syncer 15 root 760 0K12K sleep0:42 0.05% 0.05% random 33008 craig 960 2148K 1180K RUN 0:00 0.00% 0.00% top I have ttcp installed now, what shall I do with it? -Craig Maxime Henrion wrote: >Craig Reyenga wrote: >> Sure. The cards at both ends are realtek 8139B's and according to >> ifconfig, they have negotiated a 100mbit full-duplex link. >> Uploads AND downloads are slow, using HTTP, FTP and SMB. When I >> installed DP2, I simply copied my httpd.conf and smb.conf, so I >> can't imagine that configuration of the daemons is an issue. > >OK, I have a few more questions. Does ps or top shows that background >fcsk is running while doing the transfers ? Can you install and run the >ttcp program from ports which will compute raw TCP performance and will >help us distinguish where the problem lies. > >Cheers, >Maxime > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make regression tests and 4.x cross-builds
Kris Kennaway <[EMAIL PROTECTED]> writes: > I'm cross-building 5.0 on 4.x, and I get the following: > > bento# make buildworld -j4 > Running test variables > PASS: Test variables detected no regression, output matches. > Running test targets > PASS: Test targets detected no regression. > Running test sysvmatch > PASS: Test sysvmatch detected no regression. > Running test lhs_expn > FAIL: Test failed: regression detected. See above. > *** Error code 1 > 1 error > *** Error code 2 The sparc64 tinderbox is running a stale world (about 3 months old), so it's hitting the same problem. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trashed Disk Labels
Date: Fri, 29 Nov 2002 14:53:06 -0500 (EST) From: Wesley Morgan <[EMAIL PROTECTED]> To: Kirk McKusick <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] Subject: Re: Trashed Disk Labels X-ASK-Info: Confirmed by User On Fri, 29 Nov 2002, Kirk McKusick wrote: > I have had a report of a disk label getting trashed after booting > up to a kernel with the new UFS2 superblock format. I have just > checked in an update to ufs/ffs/ffs_vfsops.c (version 1.198) that > explicitly checks to make sure that it will not trash your disk > label. I highly recommend that you update to this version, even if > you are only running with UFS1 filesystems. > > Kirk McKusick Great! Any tools available to extract my var/db/pkg dirs from this image of my trashed UFS2 filesystem? :> What seems to work is to boot from CD-ROM, use disklabel -r -w auto to reinstall the default disklabel, then disklabel -B to put back the bootstrap. At that point your existing filesystems should all come back. This of course assumes that you used the orginal default partition sizes. If not, you will need to figure them out and edit up an appropriate disk label. Kirk McKusick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sparc64 tinderbox failure
Ruslan Ermilov <[EMAIL PROTECTED]> writes: > On Fri, Nov 29, 2002 at 03:22:29AM +, Mike Barcroft wrote: > > Fri Nov 29 03:15:00 GMT 2002 > > U lib/libpam/modules/pam_ksu/pam_ksu.c > > U release/doc/en_US.ISO8859-1/early-adopter/article.sgml > > Running test variables > > PASS: Test variables detected no regression, output matches. > > Running test targets > > PASS: Test targets detected no regression. > > Running test sysvmatch > > PASS: Test sysvmatch detected no regression. > > Running test lhs_expn > > PASS: Test lhs_expn detected no regression. > > Running test notdef > > PASS: Test notdef detected no regression. > > Running test modifiers > > PASS: Test modifiers detected no regression. > > Running test funny_targets > > FAIL: Test failed: regression detected. See above. > > *** Error code 1 > > > > Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. > > *** Error code 1 > > > > Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. > > > > -- > > Upgrading the installed make > > -- > > install: /usr/bin/make: Text file busy > > *** Error code 71 > > > Are you using NFS here? Only the CVS repo is NFS mounted. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
corrupted UFS2 label after ffs_vfsops.c,v 1.198
Hi, after cvsupping a kernel with the mentioned version of ffs_vfsops.c I tried to upgrade my kernel from a some weeks aged -current. After that I'm no longer able to mount or fsck a UFS2 formatted disk. My dmesg is attached. Trying fsck_ffs /dev/da0s1a gives: (nihil)(root) # fsck_ffs /dev/da0s1a ** /dev/da0s1a Cannot find file system superblock LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y Fließkommafehler (floating point error in german) Any possible alternate superblock given with -b gives a fp-error also. How to resolve this? Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS cam: invalid value for tunable kern.cam.scsi_delay Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri Nov 29 23:57:10 CET 2002 root@nihil:/usr/src/sys/i386/compile/nihil Preloaded elf kernel "/boot/kernel/kernel" at 0xc052c000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc052c0a8. Preloaded elf module "/boot/kernel/procfs.ko" at 0xc052c0f8. Preloaded elf module "/boot/kernel/pseudofs.ko" at 0xc052c1a4. Preloaded elf module "/boot/kernel/md.ko" at 0xc052c254. Preloaded elf module "/boot/kernel/linux.ko" at 0xc052c2fc. Preloaded elf module "/boot/kernel/sysvshm.ko" at 0xc052c3a8. Preloaded elf module "/boot/kernel/sysvsem.ko" at 0xc052c454. Preloaded elf module "/boot/kernel/sysvmsg.ko" at 0xc052c500. Preloaded elf module "/boot/kernel/miibus.ko" at 0xc052c5ac. Preloaded elf module "/boot/kernel/if_dc.ko" at 0xc052c658. Preloaded elf module "/boot/kernel/if_fxp.ko" at 0xc052c704. Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc052c7b0. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc052c85c. Preloaded elf module "/boot/kernel/usb.ko" at 0xc052c908. Preloaded elf module "/boot/kernel/ums.ko" at 0xc052c9b0. Preloaded elf module "/boot/kernel/umass.ko" at 0xc052ca58. Preloaded elf module "/boot/kernel/linprocfs.ko" at 0xc052cb04. Preloaded elf module "/boot/kernel/radeon.ko" at 0xc052cbb4. Preloaded elf module "/boot/kernel/if_ep.ko" at 0xc052cc60. Preloaded elf module "/boot/kernel/aic.ko" at 0xc052cd0c. Preloaded elf module "/boot/kernel/if_ed.ko" at 0xc052cdb4. Preloaded elf module "/boot/kernel/nfsserver.ko" at 0xc052ce60. Preloaded elf module "/boot/kernel/nfsclient.ko" at 0xc052cf10. Preloaded elf module "/boot/kernel/firewire.ko" at 0xc052cfc0. Preloaded elf module "/boot/kernel/sbp.ko" at 0xc052d070. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc052d118. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1198986874 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1198.99-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383f9ff real memory = 1073086464 (1023 MB) avail memory = 1037918208 (989 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled VESA: v2.0, 32704k memory, flags:0x1, mode table:0xc0350042 (122) VESA: ATI MOBILITY RADEON npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 Using $PIR table, 14 entries at 0xc00fdeb0 ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_E
Re: suggested WARNS makefile magic
On Fri, Nov 29, 2002 at 09:18:46AM +0100, Poul-Henning Kamp wrote:
>
> Right now, if I want to ensure that a particular program compiles
> with a WARNS level of no less than 3, I have to put this in the
> Makefile:
>
> WARNS?= 3
> .if ${WARNS} < 3
> WARNS= 3
> .endif
Is this program w/in /usr/src or something else? If with-in /usr/src, is
sounds like we have Makefile's battling each other and we should fix
that.
Your change would get in the way of toolchain upgrades; as one often
wants to do "make WARNS=0" for the first couple of compiles while working
on the update.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Problem with ntpdate
On 2002-11-28 17:00, "Daniel C. Sobral" <[EMAIL PROTECTED]> wrote: > I found out that ntpdate just doesn't seem to be working at all > during boot. Ntpd dies because of the time differential (windows > changes the time two hours because of the TZ). No message from > ntpdate (I'll next try to divert it to syslog). You could always fix the broken date in the CMOS setup. This will always work, and it won't make already started processes behave in unexpected ways because of the sudden clock change when ntpdate changes the time :-/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: suggested WARNS makefile magic
On 2002-11-29 09:18, Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
>
> Right now, if I want to ensure that a particular program compiles
> with a WARNS level of no less than 3, I have to put this in the
> Makefile:
>
> WARNS?= 3
> .if ${WARNS} < 3
> WARNS= 3
> .endif
>
> That is somewhat cumbersome and obviously some relatively simple
> changes to src/share/mk/* could make it possible to simply write:
>
> LOWWARNS= 3
>
> To indicate that this program is WARNS clean _at least_ to level 3,
> and always should be checked at 3 or above.
So what happens when one sets: LOWWARNS?=3 ?
The original isn't very bad, imho. Plus, it's also very clean &
precise in what it does.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Problem pulling particular directory from CVS
>> The cvs on MacOSX does not [work]. My mistake. > From: Mike Bristow <[EMAIL PROTECTED]> > CVS works just fine - it's just that the filesystem is case insensitive > [1], so when you check out src/contrib, the distinction between > src/contrib/CVS [2] src/contrib/cvs is lost, and Bad Shit happens. Damn. I keep forgetting about the Mac OSX stupid, case-insesitive HFS+. I HATE that! It's burned me more than once. Unfortunately, moving to UFS is not an option for a whole host of reasons. Ya know, Apple stated on their Web site, "there is never any good reason to have a case-sensitive file system." Can you believe that? I wrote back to them and stated, "there is never any good reason to have a case-INsensitive filesystem." But, of course, they never replied. :) > Try using Disk Copy to setup and mount a blank (UFS) image, or having a > separate UFS partition. I did this and cvs now works perfectly. Thanks for the great tip. I REALLY appreciate it. > [1] Unless your filesystem is UFS, rather than HFS+, in which case > you'll have lots of interesting other problmes. I know. I once tried to move to UFS. Big mistake. Apple's UFS limits file sizes to 2GB, and it doesn't support meta-data. > [2] CVS keeps a shedload of metadata here Ahhh. Since the topic has moved from FreeBSD to Apple Mac OSX, it's now off-topic and I should now kill this thread. Paul -- Paul A. Scott mailto:[EMAIL PROTECTED] http://skycoast.us/pscott/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sparc64 tinderbox failure
Fri Nov 29 21:15:00 GMT 2002 U games/factor/factor.6 U lib/libc/gen/fts.3 U lib/libc/locale/iswalnum.3 U lib/libc/locale/mbrlen.3 U lib/libc/locale/mbrtowc.3 U lib/libc/locale/mbsinit.3 U lib/libc/locale/mbsrtowcs.3 U lib/libc/locale/towlower.3 U lib/libc/locale/towupper.3 U lib/libc/locale/utf8.5 U lib/libc/locale/wcrtomb.3 U lib/libc/locale/wcsftime.3 U lib/libc/locale/wcsrtombs.3 U lib/libc/locale/wcstod.3 U lib/libc/locale/wcstol.3 U lib/libc/locale/wctrans.3 U lib/libc/locale/wctype.3 U lib/libc/locale/wcwidth.3 U lib/libc/net/rcmd.3 U lib/libc/stdio/fseek.3 U lib/libc/stdlib/atexit.3 U lib/libc/stdlib/insque.3 U lib/libc/stdlib/qsort.3 U lib/libc/stdlib/strfmon.3 U lib/libc/string/strcpy.3 U lib/libc/string/strsep.3 U lib/libc/sys/intro.2 U lib/libc/sys/kse.2 U lib/libc/sys/pathconf.2 U lib/libc/sys/sigaction.2 U lib/libc/sys/sigprocmask.2 U lib/libc/sys/socketpair.2 U lib/libc/sys/uuidgen.2 U lib/libcompat/4.3/rexec.3 U lib/libpam/modules/pam_radius/pam_radius.8 U lib/libpam/modules/pam_wheel/pam_wheel.8 U lib/libtacplus/libtacplus.3 U libexec/rtld-elf/rtld.c U share/man/man4/cardbus.4 U share/man/man4/pccard.4 U sys/cam/scsi/scsi_da.c U sys/ia64/ia64/pmap.c U sys/ufs/ffs/ffs_vfsops.c U usr.sbin/getfmac/getfmac.8 U usr.sbin/setfmac/setfmac.8 Running test variables PASS: Test variables detected no regression, output matches. Running test targets PASS: Test targets detected no regression. Running test sysvmatch PASS: Test sysvmatch detected no regression. Running test lhs_expn PASS: Test lhs_expn detected no regression. Running test notdef PASS: Test notdef detected no regression. Running test modifiers PASS: Test modifiers detected no regression. Running test funny_targets FAIL: Test failed: regression detected. See above. *** Error code 1 Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. *** Error code 1 Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. -- Upgrading the installed make -- install: /usr/bin/make: Text file busy *** Error code 71 Stop in /tinderbox/sparc64/src/usr.bin/make. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Network is crazy slow in DP2
Sure. The cards at both ends are realtek 8139B's and according to ifconfig, they have negotiated a 100mbit full-duplex link. Uploads AND downloads are slow, using HTTP, FTP and SMB. When I installed DP2, I simply copied my httpd.conf and smb.conf, so I can't imagine that configuration of the daemons is an issue. I don't recall changing _anything_ at all when I setup DP2. Here's dmesg output: boss# dmesg Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-DP2 #0: Fri Nov 29 02:10:15 EST 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/BOSSKERN Preloaded elf kernel "/boot/kernel/kernel" at 0xc03d9000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc03d90a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 350797838 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x8800 real memory = 268369920 (255 MB) avail memory = 256626688 (244 MB) Initializing GEOMetry subsystem K6-family MTRR support enabled (2 registers) netsmb_dev: loaded npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard Using $PIR table, 6 entries at 0xc00fdd60 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_BUFFER_LIMIT acpi_timer0: <32-bit timer at 3.579545MHz> port 0x6008-0x600b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0x6080-0x60ff,0x6000-0x607f,0xcf8-0xcff on acpi0 initial configuration \\_SB_.PCI0.ISA_.LNKA irq 5: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.8.0 \\_SB_.PCI0.ISA_.LNKB irq 10: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.8.1 \\_SB_.PCI0.ISA_.LNKC irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.8.2 \\_SB_.PCI0.ISA_.LNKD irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.8.3 \\_SB_.PCI0.ISA_.LNKB irq 10: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.9.0 \\_SB_.PCI0.ISA_.LNKC irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.9.1 \\_SB_.PCI0.ISA_.LNKD irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.9.2 \\_SB_.PCI0.ISA_.LNKA irq 5: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.9.3 \\_SB_.PCI0.ISA_.LNKC irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.10.0 \\_SB_.PCI0.ISA_.LNKD irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.10.1 \\_SB_.PCI0.ISA_.LNKA irq 5: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.10.2 \\_SB_.PCI0.ISA_.LNKB irq 10: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.10.3 \\_SB_.PCI0.ISA_.LNKA irq 5: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.7.0 \\_SB_.PCI0.ISA_.LNKB irq 10: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.7.1 \\_SB_.PCI0.ISA_.LNKC irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.7.2 \\_SB_.PCI0.ISA_.LNKD irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.7.3 \\_SB_.PCI0.ISA_.LNKA irq 5: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.1.0 \\_SB_.PCI0.ISA_.LNKB irq 10: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.1.1 \\_SB_.PCI0.ISA_.LNKC irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.1.2 \\_SB_.PCI0.ISA_.LNKD irq 0: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.1.3 before setting priority for links \\_SB_.PCI0.ISA_.LNKC: interrupts: 1 3 4 5 6 710 11121415 penalty:101100 2100 2100 1600 2100 2100 1600 1100 2100 11100 11100 references: 5 priority: 0 \\_SB_.PCI0.ISA_.LNKD: interrupts: 1 3 4 5 6 710 11121415 penalty:101100 2100 2100 1600 2100 2100 1600 1100 2100 11100 11100 references: 5 priority: 0 before fixup boot-disabled links - \\_SB_.PCI0.ISA_.LNKC: interrupts: 1 3 4 5 6 710 11121415 penalty:101100 2100 2100 1600 2100 2100 1600 1100 2100 11100 11100 references: 5 priority: 62772 \\_SB_.PCI0.ISA_.LNKD: interrupts: 1 3 4 5 6 710 11121415 penalty:101100 2100 2100 1600 2100 2100 1600 1100 2100 11100 11100 references: 5 priority: 62772 after fixup boot-disabled links -- arbitrated configuration - \\_SB_.PCI0.ISA_.LNKA irq 5: [ 1 3 4 5 6 7 10 11 12 14 15] low,level,sharable 0.8.0 \\_SB_.PCI0.ISA_.LNKB irq
Re: 5.0-DP2 questions
>Date: Fri, 29 Nov 2002 12:20:38 -0800 >From: Kris Kennaway <[EMAIL PROTECTED]> >It's often more efficient to use binary installations/upgrades than >source, on slow machines. For example, I build world on a fast >machine, mount via NFS and then installworld on my slower machines. Quite so -- not only more efficient, but also less painful. :-} Indeed, that is how my "build machine" achieved that designation: I install -STABLE snapshots built on it about every 2 weeks or so onto my firewall & a macihne that acts as the externally-visible Web server. (And it would be faster & less hassle for me to treat my laptop similarly; on the other hand, I wanted to be able to compare UP vs. SMP if Something Weird(tm) were to happen. I also wanted to be sure that I had an independent complete (and portable) build environment on my laptop -- complete with its own copy of the FreeBSD CVS repo.) Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] I have no confidence in results obtained through the use of Microsoft products. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Harry Potter and the Disappearing Disklabel
Wesley Morgan wrote: > > On Fri, 29 Nov 2002, Steve Kargl wrote: > > > On Fri, Nov 29, 2002 at 09:41:56AM -0500, Wesley Morgan wrote: > > > > > > I've seen one post similar to this, but not much else. I think maybe the > > > UFS2 problem had to do with Kirk's recent changes, but the disklabel > > > issue... I'm wary to reboot my machine! What in the hell could be causing > > > this? I'm tempted to point the finger at GEOM, but hate to say anything > > > like that. > > > > Are your world and kernel in sync (post-kirk commit)? > > They are now, but were not before. However I fail to see what world has to > do with disappearing disklabels between boots. Unless specifically asked > to, nothing except the kernel should ever read it (at least, I am guessing > this). Well, after that commit, UFS2 partitions on the first mount would be _changed_, to a slightly different format that ought to have a longer life. Now, I don't know if the modifications are done by kernel or userland, but out of synch kernel/world can have two results: 1) Kernel expects an UFS2 partition whose format is slightly different than what it is. 2) fsck expects an UFS2 partition whose format is slightly different than what it is. Nothing good can come out of any of these. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "Fundamentalist Debianites, core children of the Linuxen sounds like it could come from the Book of Mormon, or Tolkien on a bad day..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Network is crazy slow in DP2
Craig Reyenga wrote: > Yesterday I installed 5.0-DP2 without problems, however my 100mbit link > to my desktop computer goes extremely slowly using HTTP, FTP or SMB and > proabably others. I used to be able to tranfer files using FTP at over > 7.9MB/sec in 4.7 but now the best that I can do is 800KB/sec. When I > look at 'top' it appears that the computer isn't even "trying" i.e. the > cpu usage is very low. > The network adapter in question is a Realtek 8139B. The problem exists > in polling or non-polling mode. Are you seeing this performance problems both in send and receive mode ? Can you give us a bit more info about your environment, like the type of cards at both ends, the output of ifconfig (to check if the interface successfully negotiated a 100MB link), dmesg, etc... Also, -CURRENT debugging malloc flags may be relevant though that's truly a huge performance loss... Can you confirm that these problems arise whatever protocol/software you use to transfer data ? Thanks in advance, Maxime To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can I safely enable -march=pentium4 now?
On Sat, 30 Nov 2002 04:46:47 +0800 JY <[EMAIL PROTECTED]> wrote: > Can anyone comment on this? I had a bad experience circa Nov 19, which > resulted in a very unstable kernel/world combination. Has the issue been > resolved? Meaning can I add CPUTYPE?=p4 in /etc/make.conf now? > > Thank you, > > JY > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message NO. -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Network is crazy slow in DP2
I actually don't have those options in my kernel already, and would it make _that_ much of a difference? -Craig Kris Kennaway wrote: >On Fri, Nov 29, 2002 at 03:24:24PM -0500, Craig Reyenga wrote: >> Yesterday I installed 5.0-DP2 without problems, however my 100mbit link >> to >> my desktop computer goes extremely slowly using HTTP, FTP or SMB and >> proabably others. I used to be able to tranfer files using FTP at over >> 7.9MB/sec in 4.7 but now the best that I can do is 800KB/sec. When I >> look at 'top' it appears that the computer isn't even "trying" i.e. the >> cpu usage is very low. >> The network adapter in question is a Realtek 8139B. The problem exists >> in polling or non-polling mode. >> >> Any ideas would be appreciated. > >Try removing the WITNESS and/or WITNESS_SKIPSPIN debugging options if >you want performance (at the expense of ability to catch locking bugs) > >Kris > Name: attached attachedType: application/pgp-signature Encoding: To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Network is crazy slow in DP2
On Fri, Nov 29, 2002 at 12:33:22PM -0800, Kris Kennaway wrote: > Try removing the WITNESS and/or WITNESS_SKIPSPIN debugging options if > you want performance (at the expense of ability to catch locking bugs) Sorry, I mis-spoke. If you want to leave WITNESS in, then *adding* the WITNESS_SKIPSPIN option will increase the performance. Removing both will increase the performance further (at the expense of ability to catch locking bugs). Kris msg47762/pgp0.pgp Description: PGP signature
Can I safely enable -march=pentium4 now?
Can anyone comment on this? I had a bad experience circa Nov 19, which resulted in a very unstable kernel/world combination. Has the issue been resolved? Meaning can I add CPUTYPE?=p4 in /etc/make.conf now? Thank you, JY To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATA patches for PC98 - Please test!
I'm trying to get this into 5.0 (I know its late, but life's tough)
This brings ATA support to the PC98 arch will all bells and whistles.
I want to thank the PC98 core team for getting me a PC98 machine
to do this work on, without that it would probably newer have happend..
Please get back to me with any success/failures on this ASAP...
Enjoy!
Index: sys/conf/files
===
RCS file: /home/ncvs/src/sys/conf/files,v
retrieving revision 1.738
diff -u -r1.738 files
--- sys/conf/files 28 Nov 2002 01:17:48 - 1.738
+++ sys/conf/files 28 Nov 2002 20:01:52 -
@@ -290,6 +290,7 @@
dev/asr/asr.c optional asr pci
dev/ata/ata-all.c optional ata
dev/ata/ata-isa.c optional ata isa
+dev/ata/ata-cbus.c optional ata pc98
dev/ata/ata-card.c optional ata card
dev/ata/ata-card.c optional ata pccard
dev/ata/ata-pci.c optional ata pci
Index: sys/dev/ata/ata-all.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v
retrieving revision 1.158
diff -u -r1.158 ata-all.c
--- sys/dev/ata/ata-all.c 7 Nov 2002 22:23:46 - 1.158
+++ sys/dev/ata/ata-all.c 31 Oct 2002 18:32:25 -
@@ -134,7 +134,9 @@
(int)rman_get_start(ch->r_altio),
(ch->r_bmio) ? (int)rman_get_start(ch->r_bmio) : 0);
+ch->lock_func(ch, ATA_LF_LOCK);
ata_reset(ch);
+ch->lock_func(ch, ATA_LF_UNLOCK);
ch->device[MASTER].channel = ch;
ch->device[MASTER].unit = ATA_MASTER;
@@ -186,6 +188,7 @@
* otherwise attach what the probe has found in ch->devices.
*/
if (!ata_delayed_attach) {
+ ch->lock_func(ch, ATA_LF_LOCK);
if (ch->devices & ATA_ATA_SLAVE)
if (ata_getparam(&ch->device[SLAVE], ATA_C_ATA_IDENTIFY))
ch->devices &= ~ATA_ATA_SLAVE;
@@ -213,6 +216,7 @@
#ifdef DEV_ATAPICAM
atapi_cam_attach_bus(ch);
#endif
+ ch->lock_func(ch, ATA_LF_UNLOCK);
}
return 0;
}
@@ -228,6 +232,7 @@
return ENXIO;
/* make sure channel is not busy */
+ch->lock_func(ch, ATA_LF_LOCK);
ATA_SLEEPLOCK_CH(ch, ATA_CONTROL);
s = splbio();
@@ -274,13 +279,23 @@
ch->r_bmio = NULL;
ch->r_irq = NULL;
ATA_UNLOCK_CH(ch);
+ch->lock_func(ch, ATA_LF_UNLOCK);
return 0;
}
int
ata_resume(device_t dev)
{
-return ata_reinit(device_get_softc(dev));
+struct ata_channel *ch;
+int error;
+
+if (!dev || !(ch = device_get_softc(dev)))
+ return ENXIO;
+
+ch->lock_func(ch, ATA_LF_LOCK);
+error = ata_reinit(ch);
+ch->lock_func(ch, ATA_LF_UNLOCK);
+return error;
}
static int
@@ -313,9 +328,10 @@
case ATAREINIT:
if (!device || !(ch = device_get_softc(device)))
return ENXIO;
+ ch->lock_func(ch, ATA_LF_LOCK);
ATA_SLEEPLOCK_CH(ch, ATA_ACTIVE);
- if ((error = ata_reinit(ch)))
- ATA_UNLOCK_CH(ch);
+ error = ata_reinit(ch);
+ ch->lock_func(ch, ATA_LF_UNLOCK);
return error;
case ATAGMODE:
@@ -339,6 +355,7 @@
if (!device || !(ch = device_get_softc(device)))
return ENXIO;
+ ch->lock_func(ch, ATA_LF_LOCK);
if ((iocmd->device == MASTER || iocmd->device == -1) &&
iocmd->u.mode.mode[MASTER] >= 0 && ch->device[MASTER].param) {
ata_change_mode(&ch->device[MASTER],iocmd->u.mode.mode[MASTER]);
@@ -354,6 +371,7 @@
}
else
iocmd->u.mode.mode[SLAVE] = -1;
+ ch->lock_func(ch, ATA_LF_UNLOCK);
return 0;
case ATAGPARM:
@@ -386,6 +404,7 @@
if (!device || !(ch = device_get_softc(device)))
return ENXIO;
+ ch->lock_func(ch, ATA_LF_LOCK);
ATA_SLEEPLOCK_CH(ch, ATA_ACTIVE);
if (iocmd->device == SLAVE)
@@ -399,6 +418,7 @@
id2 = ata_drawersensor(atadev, 0, 0x4f, 0);
if (id1 != 0xa3 || id2 != 0x5c) {
ATA_UNLOCK_CH(ch);
+ ch->lock_func(ch, ATA_LF_UNLOCK);
return ENXIO;
}
@@ -419,6 +439,7 @@
iocmd->u.enclosure.v12 = ata_drawersensor(atadev, 0, 0x24, 0) * 61;
ATA_UNLOCK_CH(ch);
+ ch->lock_func(ch, ATA_LF_UNLOCK);
return 0;
}
@@ -547,6 +568,7 @@
for (ctlr=0; ctlrlock_func(ch, ATA_LF_LOCK);
if (ch->devices & ATA_ATA_SLAVE)
if (ata_getparam(&ch->device[SLAVE], ATA_C_ATA_IDENTIFY))
ch->devices &= ~ATA_ATA_SLAVE;
@@ -559,6 +581,7 @@
if (ch->devices & ATA_ATAPI_MASTER)
if (ata_getparam(&ch->device[MASTER], ATA_C_ATAPI_IDENTIFY))
ch->devices &= ~ATA_ATAPI_MASTER;
+ ch->lock_func(ch, ATA_LF_UNLOCK);
}
#ifdef DEV_ATADISK
@@ -566,10 +589,12 @
Re: Network is crazy slow in DP2
On Fri, Nov 29, 2002 at 03:24:24PM -0500, Craig Reyenga wrote: > Yesterday I installed 5.0-DP2 without problems, however my 100mbit link > to > my desktop computer goes extremely slowly using HTTP, FTP or SMB and > proabably others. I used to be able to tranfer files using FTP at over > 7.9MB/sec in 4.7 but now the best that I can do is 800KB/sec. When I > look at 'top' it appears that the computer isn't even "trying" i.e. the > cpu usage is very low. > The network adapter in question is a Realtek 8139B. The problem exists > in polling or non-polling mode. > > Any ideas would be appreciated. Try removing the WITNESS and/or WITNESS_SKIPSPIN debugging options if you want performance (at the expense of ability to catch locking bugs) Kris msg47759/pgp0.pgp Description: PGP signature
Re: Trashed Disk Labels
On Fri, 29 Nov 2002 14:53:06 -0500 (EST) Wesley Morgan <[EMAIL PROTECTED]> wrote: > On Fri, 29 Nov 2002, Kirk McKusick wrote: > > > I have had a report of a disk label getting trashed after booting > > up to a kernel with the new UFS2 superblock format. I have just > > checked in an update to ufs/ffs/ffs_vfsops.c (version 1.198) that > > explicitly checks to make sure that it will not trash your disk > > label. I highly recommend that you update to this version, even if > > you are only running with UFS1 filesystems. > > > > Kirk McKusick > > Great! Any tools available to extract my var/db/pkg dirs from this image > of my trashed UFS2 filesystem? :> > > -- > Hi! I'm a .signature virus! Copy me into your ~/.signature to help me > spread! > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message I successfully used ffsfind utility to locate filesystem boundaries on a disk I trashed some time ago. I do not have the utility source available anymore, but you can track it down quite easily on google, I believe. The one I used was actually posted for NetBSD, but it compiled with minimal changes on FreeBSD and Solaris too. You will have to teach it to recognize UFS2 magic. -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Network is crazy slow in DP2
Yesterday I installed 5.0-DP2 without problems, however my 100mbit link to my desktop computer goes extremely slowly using HTTP, FTP or SMB and proabably others. I used to be able to tranfer files using FTP at over 7.9MB/sec in 4.7 but now the best that I can do is 800KB/sec. When I look at 'top' it appears that the computer isn't even "trying" i.e. the cpu usage is very low. The network adapter in question is a Realtek 8139B. The problem exists in polling or non-polling mode. Any ideas would be appreciated. -Craig To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-DP2 questions
On Fri, Nov 29, 2002 at 02:28:35PM -0500, Robert Ames wrote: > Kris Kennaway wrote: > > >> 3. When trying to rcp files to this machine I get a "rshd: Login > >> incorrect" error. I have inetd configured and running and a .rhosts > >> file in place (with proper permissions). I'm assuming this might > >> be PAM related. Any suggestions? > > > >Can you log in with plain rsh? Do the manual pages or release notes > >describe any relevant changes? > > Yes, I can log in with plain rsh. And no, I didn't notice any > relevant changes in the documentation. Thanks, that's a useful data point for someone who can investigate this further. Kris msg47756/pgp0.pgp Description: PGP signature
Re: 5.0-DP2 questions
On Fri, Nov 29, 2002 at 02:02:42PM -0600, David Syphers wrote: > On Friday 29 November 2002 01:32 pm, David Wolfskill wrote: > ... > > That should, at least, provide a reasonably valid set of comparisons. > > Thanks. > > I suppose Robert's results might be abnormally long if -current requires a lot > more memory than -stable, thus requiring a lot of swap, as Kris pointed out. > Looks like my 486 won't be jumping to -current soon :) It's often more efficient to use binary installations/upgrades than source, on slow machines. For example, I build world on a fast machine, mount via NFS and then installworld on my slower machines. Kris msg47755/pgp0.pgp Description: PGP signature
Re: 5.0-DP2 questions
On Friday 29 November 2002 01:32 pm, David Wolfskill wrote: ... > That should, at least, provide a reasonably valid set of comparisons. Thanks. I suppose Robert's results might be abnormally long if -current requires a lot more memory than -stable, thus requiring a lot of swap, as Kris pointed out. Looks like my 486 won't be jumping to -current soon :) -David -- On the whole I am against mass murder. I rarely commit it myself, and often find myself quite out of sympathy with those who make a habit of it. -Bernard Levin Astronomy and Astrophysics Center The University of Chicago To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trashed Disk Labels
On Fri, 29 Nov 2002, Kirk McKusick wrote: > I have had a report of a disk label getting trashed after booting > up to a kernel with the new UFS2 superblock format. I have just > checked in an update to ufs/ffs/ffs_vfsops.c (version 1.198) that > explicitly checks to make sure that it will not trash your disk > label. I highly recommend that you update to this version, even if > you are only running with UFS1 filesystems. > > Kirk McKusick Great! Any tools available to extract my var/db/pkg dirs from this image of my trashed UFS2 filesystem? :> -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Trashed Disk Labels
If you have updated your kernel sources on or after Nov 27th, and are running with ufs/ffs/ffs_vfsops.c version 1.197, this message applies to you. I have had a report of a disk label getting trashed after booting up to a kernel with the new UFS2 superblock format. I have just checked in an update to ufs/ffs/ffs_vfsops.c (version 1.198) that explicitly checks to make sure that it will not trash your disk label. I highly recommend that you update to this version, even if you are only running with UFS1 filesystems. Kirk McKusick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-DP2 questions
>From: David Syphers <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >Date: Fri, 29 Nov 2002 13:04:47 -0600 [Well, I'm Cc:ing -current anyway -- dhw] >Out of curiosity, how much slower is a 5.x kernel compilation than a 4.x, on >average? My 486, 66 MHz and 16 MB RAM, compiles a 4.x kernel in about 3 >hours. Thus by Robert's data point, -current seems at least 10-15 times >slower... OK; in each of the following, I was building the kernel as part of the process of upgrading from yesterday's -STABLE or -CURRENT, respectively. In each case, we are comparing -STABLE and -CURRENT running on the *same* hardware -- not merely "configured similarly"; each machine is set up to multi-boot, and runs -STABLE on slice 1 and -CURRENT on a different slice (3 for the laptop; 4 for the build machine). I track each of -STABLE and -CURRENT on a daily basis on each machine. First, the laptop: g1-9(4.7-S)[1] grep '^>>> Kernel' current stable-1 current:>>> Kernel build for LAPTOP_30W started on Fri Nov 29 08:59:55 PST 2002 current:>>> Kernel build for LAPTOP_30W completed on Fri Nov 29 09:35:30 PST 2002 stable-1:>>> Kernel build for LAPTOP_30W started on Fri Nov 29 06:12:25 PST 2002 stable-1:>>> Kernel build for LAPTOP_30W completed on Fri Nov 29 06:22:09 PST 2002 g1-9(4.7-S)[2] And now, the build machine: freebeast(4.7-S)[1] grep '^>>> Kernel' current stable-1 current:>>> Kernel build for FREEBEAST started on Fri Nov 29 06:59:37 PST 2002 current:>>> Kernel build for FREEBEAST completed on Fri Nov 29 07:25:28 PST 2002 stable-1:>>> Kernel build for FREEBEAST started on Fri Nov 29 05:14:10 PST 2002 stable-1:>>> Kernel build for FREEBEAST completed on Fri Nov 29 05:21:02 PST 2002 freebeast(4.7-S)[2] So: -STABLE -CURRENT Laptop 09:4435:35 Build machine 06:5225:51 I don't use -j for building kernels; I expect that the 2nd CPU on the build machine isn't all that significant for this workload. On the other hand, the slower disk drive in the laptop is likely fairly significant. In each case, the -CURRENT kernel that is running (& the one that is being built) has WITNESS , INVARIANTS, and DIAGNOSTIC defined. The laptop is a 750 MHz PIII with 256 MB RAM; the build machine is a 2x876 MHz PIII with 512 MB RAM. That should, at least, provide a reasonably valid set of comparisons. Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] I have no confidence in results obtained through the use of Microsoft products. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-DP2 questions
Kris Kennaway wrote: > 3. When trying to rcp files to this machine I get a "rshd: Login > incorrect" error. I have inetd configured and running and a .rhosts > file in place (with proper permissions). I'm assuming this might > be PAM related. Any suggestions? Can you log in with plain rsh? Do the manual pages or release notes describe any relevant changes? Yes, I can log in with plain rsh. And no, I didn't notice any relevant changes in the documentation. _ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-DP2 questions
On Friday 29 November 2002 12:12 pm, Kris Kennaway wrote: > On Fri, Nov 29, 2002 at 12:11:42PM -0500, Robert Ames wrote: > > > 2. My machine is a Pentium 166 with only 16 MB of RAM. I'm trying > > to rebuild the kernel and so far the compile has been running for > > almost 24 hours and it's not finished yet. Is this to be expected? > > Yes. gcc 3.x is slower, and the kernel contains more code. Your > machine is probably swapping a lot just doing the compilation, which > will make it even slower. Out of curiosity, how much slower is a 5.x kernel compilation than a 4.x, on average? My 486, 66 MHz and 16 MB RAM, compiles a 4.x kernel in about 3 hours. Thus by Robert's data point, -current seems at least 10-15 times slower... -David -- On the whole I am against mass murder. I rarely commit it myself, and often find myself quite out of sympathy with those who make a habit of it. -Bernard Levin Astronomy and Astrophysics Center The University of Chicago To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Make regression tests and 4.x cross-builds
I'm cross-building 5.0 on 4.x, and I get the following: bento# make buildworld -j4 Running test variables PASS: Test variables detected no regression, output matches. Running test targets PASS: Test targets detected no regression. Running test sysvmatch PASS: Test sysvmatch detected no regression. Running test lhs_expn FAIL: Test failed: regression detected. See above. *** Error code 1 1 error *** Error code 2 Kris msg47748/pgp0.pgp Description: PGP signature
Re: 5.0-DP2 questions
On Fri, Nov 29, 2002 at 12:11:42PM -0500, Robert Ames wrote: > 2. My machine is a Pentium 166 with only 16 MB of RAM. I'm trying > to rebuild the kernel and so far the compile has been running for > almost 24 hours and it's not finished yet. Is this to be expected? Yes. gcc 3.x is slower, and the kernel contains more code. Your machine is probably swapping a lot just doing the compilation, which will make it even slower. > 3. When trying to rcp files to this machine I get a "rshd: Login > incorrect" error. I have inetd configured and running and a .rhosts > file in place (with proper permissions). I'm assuming this might > be PAM related. Any suggestions? Can you log in with plain rsh? Do the manual pages or release notes describe any relevant changes? Kris msg47747/pgp0.pgp Description: PGP signature
Re: Harry Potter and the Disappearing Disklabel
On Fri, Nov 29, 2002 at 09:41:56AM -0500, Wesley Morgan <[EMAIL PROTECTED]> wrote: > Yesterday morning I was having some trouble with XFree consuming much more > cpu time than necessary... A truss showed that some kind of shared memory > issue going on, but also froze my system hard. After rebooting (kernel was > from Nov 26 or 27) fsck could not check my one dirty UFS2 partition. Had > to newfs and mtree to recreate /var. No big deal, and I saved an image of > it beforehand. > > After rebooting, there was... NOTHING. GRUB errored out and wouldn't boot. > Nothing could see my partitions. After a minimal 4.7-R install (DP2 > disklabel whined about offsets and some other STRANGE error messages, > so I went with 4.7) on a small fat32 partition, I discovered that the > disklabel was empty. Had to edit it by hand... Booted up fine, made > a backup, rebooted, and nothing. Not only was there NOTHING, but the > disklabel on the new 4.7 install had vanished as well. This time the > disklabel had to be recreated with -w -r AND the boot blocks had to be > reinstalled. > > I've seen one post similar to this, but not much else. I think maybe the > UFS2 problem had to do with Kirk's recent changes, but the disklabel > issue... I'm wary to reboot my machine! What in the hell could be causing > this? I'm tempted to point the finger at GEOM, but hate to say anything > like that. Same here today. I had system from Nov 21, both world and kernel. Did buildworld, installworld and then rebooted with old 21Nov kernel. At boot fsck whined about /usr (ad0s1d) partition and died with incorrect superblock message leaving the system in single user. The /usr partition has UFS2 filesystem. Why the partition had to be fsck'ed? The system went down cleanly after build-installworld. I tried to fsck_ffs -b 32 /usr but it didn't like it either and died with signal 8. Floating point exception. I know the next alternate superblock _is_ there at 32, because I converted /usr to UFS2 only few days ago and remember the newfs command exactly. After the failed attempt of fsck_ffs -b 32 suddenly some fragment of recent -current talk popped in my mind and I remember there was talk about mount command doing some trickery. So I went with mount -t ufs -f /dev/ad0s1d /usr and voila the data was there. I'm almost sure that I can reproduce it, because I have the / and /usr dumps from the time I did UFS2 converting and the live-current cd burnt for this purpose (JPSNAP). It's possible to go back in time and fully restore the system as it were before. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
5.0-DP2 questions
I usually stick to just running -RELEASE but since I had some time I thought I'd try 5.0-DP2 and now have a few questions. 1. I did an ftp install. My machine has two RealTek 8029 cards in it but only one of them has a cable attached. When sysinstall asked me which interface to use it gave me the choices of ed1 and ed2. I picked ed1 and the install worked. After FreeBSD was installed and it booted for the first time, the kernel found ed0 and ed1. rc.conf was configured by sysinstall to use ed1 which was now wrong. Editing rc.conf to use ed0 fixed things. Why didn't sysinstall show the devices as ed0 and ed1? 2. My machine is a Pentium 166 with only 16 MB of RAM. I'm trying to rebuild the kernel and so far the compile has been running for almost 24 hours and it's not finished yet. Is this to be expected? 3. When trying to rcp files to this machine I get a "rshd: Login incorrect" error. I have inetd configured and running and a .rhosts file in place (with proper permissions). I'm assuming this might be PAM related. Any suggestions? _ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Harry Potter and the Disappearing Disklabel
On Fri, Nov 29, 2002 at 06:45:48PM +0200, Vallo Kallaste <[EMAIL PROTECTED]> wrote: > > I've seen one post similar to this, but not much else. I think maybe the > > UFS2 problem had to do with Kirk's recent changes, but the disklabel > > issue... I'm wary to reboot my machine! What in the hell could be causing > > this? I'm tempted to point the finger at GEOM, but hate to say anything > > like that. > > Same here today. I had system from Nov 21, both world and kernel. > Did buildworld, installworld and then rebooted with old 21Nov > kernel. At boot fsck whined about /usr (ad0s1d) partition and died > with incorrect superblock message leaving the system in single user. > The /usr partition has UFS2 filesystem. Why the partition had to be > fsck'ed? The system went down cleanly after build-installworld. > I tried to fsck_ffs -b 32 /usr but it didn't like it either and died > with signal 8. Floating point exception. I know the next alternate > superblock _is_ there at 32, because I converted /usr to UFS2 only > few days ago and remember the newfs command exactly. > After the failed attempt of fsck_ffs -b 32 suddenly some fragment of > recent -current talk popped in my mind and I remember there was talk > about mount command doing some trickery. So I went with > mount -t ufs -f /dev/ad0s1d /usr and voila the data was there. > I'm almost sure that I can reproduce it, because I have the / and > /usr dumps from the time I did UFS2 converting and the live-current > cd burnt for this purpose (JPSNAP). It's possible to go back in time > and fully restore the system as it were before. One thought about the initial fsck issue. The system uptime was 8 days and almost all the time it did compilation/clearing up of my workstation bundle port (~100 individual port). I did it because of stability issues before, to control the kernel with only DISABLE_PSE enabled. Because space in /usr is limited on this system, the /usr/ports is mounted over ro NFS, but WRKDIRPREFIX, DISTDIR and PACKAGES are set to local filesystem, so /usr periodically filled up to ~95% and drained quickly (several concurrent rm -rf's) to 30%. This is quite a stress to softupdates and filesystem in general, so if there's a bug this explains the need for fsck after boot. Just a thought. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Harry Potter and the Disappearing Disklabel
On Fri, Nov 29, 2002 at 08:47:10AM -0800, Sam Leffler wrote the words in effect of: > > Yesterday morning I was having some trouble with XFree consuming much more > > cpu time than necessary... A truss showed that some kind of shared memory > > issue going on, but also froze my system hard. After rebooting (kernel was > > from Nov 26 or 27) fsck could not check my one dirty UFS2 partition. Had > > to newfs and mtree to recreate /var. No big deal, and I saved an image of > > it beforehand. > > > > After rebooting, there was... NOTHING. GRUB errored out and wouldn't boot. > > Nothing could see my partitions. After a minimal 4.7-R install (DP2 > > disklabel whined about offsets and some other STRANGE error messages, > > so I went with 4.7) on a small fat32 partition, I discovered that the > > disklabel was empty. Had to edit it by hand... Booted up fine, made > > a backup, rebooted, and nothing. Not only was there NOTHING, but the > > disklabel on the new 4.7 install had vanished as well. This time the > > disklabel had to be recreated with -w -r AND the boot blocks had to be > > reinstalled. > > > > I've seen one post similar to this, but not much else. I think maybe the > > UFS2 problem had to do with Kirk's recent changes, but the disklabel > > issue... I'm wary to reboot my machine! What in the hell could be causing > > this? I'm tempted to point the finger at GEOM, but hate to say anything > > like that. > > Same problem hit me yesterday. Haven't figured out the cause yet. > > Sam FWIW, find-sb in /usr/src/tools/tools, does a good job of finding UFS1 and UFS2 slices. It is somewhat similar to scan_ffs but way more advanced. -- Hiten Pandya ([EMAIL PROTECTED], [EMAIL PROTECTED]) http://www.unixdaemons.com/~hiten/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Harry Potter and the Disappearing Disklabel
> Yesterday morning I was having some trouble with XFree consuming much more > cpu time than necessary... A truss showed that some kind of shared memory > issue going on, but also froze my system hard. After rebooting (kernel was > from Nov 26 or 27) fsck could not check my one dirty UFS2 partition. Had > to newfs and mtree to recreate /var. No big deal, and I saved an image of > it beforehand. > > After rebooting, there was... NOTHING. GRUB errored out and wouldn't boot. > Nothing could see my partitions. After a minimal 4.7-R install (DP2 > disklabel whined about offsets and some other STRANGE error messages, > so I went with 4.7) on a small fat32 partition, I discovered that the > disklabel was empty. Had to edit it by hand... Booted up fine, made > a backup, rebooted, and nothing. Not only was there NOTHING, but the > disklabel on the new 4.7 install had vanished as well. This time the > disklabel had to be recreated with -w -r AND the boot blocks had to be > reinstalled. > > I've seen one post similar to this, but not much else. I think maybe the > UFS2 problem had to do with Kirk's recent changes, but the disklabel > issue... I'm wary to reboot my machine! What in the hell could be causing > this? I'm tempted to point the finger at GEOM, but hate to say anything > like that. Same problem hit me yesterday. Haven't figured out the cause yet. Sam To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Harry Potter and the Disappearing Disklabel
On Fri, 29 Nov 2002, Steve Kargl wrote: > On Fri, Nov 29, 2002 at 09:41:56AM -0500, Wesley Morgan wrote: > > > > I've seen one post similar to this, but not much else. I think maybe the > > UFS2 problem had to do with Kirk's recent changes, but the disklabel > > issue... I'm wary to reboot my machine! What in the hell could be causing > > this? I'm tempted to point the finger at GEOM, but hate to say anything > > like that. > > Are your world and kernel in sync (post-kirk commit)? They are now, but were not before. However I fail to see what world has to do with disappearing disklabels between boots. Unless specifically asked to, nothing except the kernel should ever read it (at least, I am guessing this). -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Harry Potter and the Disappearing Disklabel
On Fri, Nov 29, 2002 at 09:41:56AM -0500, Wesley Morgan wrote: > > I've seen one post similar to this, but not much else. I think maybe the > UFS2 problem had to do with Kirk's recent changes, but the disklabel > issue... I'm wary to reboot my machine! What in the hell could be causing > this? I'm tempted to point the finger at GEOM, but hate to say anything > like that. Are your world and kernel in sync (post-kirk commit)? -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem pulling particular directory from CVS
On Wednesday, November 27, 2002, at 11:34 pm, Paul A. Scott wrote: Oh, #$%@. I'm so embarrassed. My terminal session was logged into Mac OSX not FreeBSD, and I had mirrored the same directory structure, so I faked myself out. Bottom line is, cvs on Freebsd works like a champ. The cvs on MacOSX does not. My mistake. And I humbly appolgize for the stupid user error. CVS works just fine - it's just that the filesystem is case insensitive [1], so when you check out src/contrib, the distinction between src/contrib/CVS [2] src/contrib/cvs is lost, and Bad Shit happens. Try using Disk Copy to setup and mount a blank (UFS) image, or having a separate UFS partition. [1] Unless your filesystem is UFS, rather than HFS+, in which case you'll have lots of interesting other problmes. [2] CVS keeps a shedload of metadata here -- Am I getting older, or are these shows getting more entertaining? -- Flash, on Children in Need. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sparc64 tinderbox failure
Fri Nov 29 15:15:00 GMT 2002 U share/man/man3/stdarg.3 U share/man/man4/ata.4 U share/man/man4/dummynet.4 U share/man/man4/ipfirewall.4 U share/man/man4/ktr.4 U share/man/man4/stf.4 U share/man/man4/tap.4 U share/man/man4/tcp.4 U share/man/man4/umass.4 U share/man/man4/usb.4 U share/man/man5/device.hints.5 U share/man/man5/drivers.conf.5 U share/man/man5/fs.5 U share/man/man5/make.conf.5 U share/man/man5/passwd.5 U share/man/man5/rc.conf.5 U share/man/man5/remote.5 U share/man/man7/clocks.7 U share/man/man7/firewall.7 U share/man/man7/hier.7 U share/man/man7/tuning.7 U share/man/man8/rc.8 U share/man/man8/rc.sendmail.8 U share/man/man9/VOP_IOCTL.9 U share/man/man9/VOP_LINK.9 U share/man/man9/VOP_RENAME.9 U share/man/man9/ifnet.9 U share/man/man9/mbuf.9 U share/man/man9/random.9 U share/man/man9/style.9 U share/man/man9/swi.9 U share/man/man9/zone.9 Running test variables PASS: Test variables detected no regression, output matches. Running test targets PASS: Test targets detected no regression. Running test sysvmatch PASS: Test sysvmatch detected no regression. Running test lhs_expn PASS: Test lhs_expn detected no regression. Running test notdef PASS: Test notdef detected no regression. Running test modifiers PASS: Test modifiers detected no regression. Running test funny_targets FAIL: Test failed: regression detected. See above. *** Error code 1 Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. *** Error code 1 Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. -- Upgrading the installed make -- install: /usr/bin/make: Text file busy *** Error code 71 Stop in /tinderbox/sparc64/src/usr.bin/make. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Harry Potter and the Disappearing Disklabel
In message <[EMAIL PROTECTED]>, Wesley Morgan writes: >Yesterday morning I was having some trouble with XFree consuming much more >cpu time than necessary... A truss showed that some kind of shared memory >issue going on, but also froze my system hard. After rebooting (kernel was >from Nov 26 or 27) fsck could not check my one dirty UFS2 partition. Had >to newfs and mtree to recreate /var. No big deal, and I saved an image of >it beforehand. > >After rebooting, there was... NOTHING. GRUB errored out and wouldn't boot. >Nothing could see my partitions. After a minimal 4.7-R install (DP2 >disklabel whined about offsets and some other STRANGE error messages, >so I went with 4.7) on a small fat32 partition, I discovered that the >disklabel was empty. Had to edit it by hand... Booted up fine, made >a backup, rebooted, and nothing. Not only was there NOTHING, but the >disklabel on the new 4.7 install had vanished as well. This time the >disklabel had to be recreated with -w -r AND the boot blocks had to be >reinstalled. > >I've seen one post similar to this, but not much else. I think maybe the >UFS2 problem had to do with Kirk's recent changes, but the disklabel >issue... I'm wary to reboot my machine! What in the hell could be causing >this? I'm tempted to point the finger at GEOM, but hate to say anything >like that. I have absolutely no idea how this can happen, and would really appreciate if people can try to find a way to reproduce it, I've tried today and couldn't :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
suggested WARNS makefile magic
Right now, if I want to ensure that a particular program compiles
with a WARNS level of no less than 3, I have to put this in the
Makefile:
WARNS?= 3
.if ${WARNS} < 3
WARNS= 3
.endif
That is somewhat cumbersome and obviously some relatively simple
changes to src/share/mk/* could make it possible to simply write:
LOWWARNS= 3
To indicate that this program is WARNS clean _at least_ to level 3,
and always should be checked at 3 or above.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Harry Potter and the Disappearing Disklabel
Yesterday morning I was having some trouble with XFree consuming much more cpu time than necessary... A truss showed that some kind of shared memory issue going on, but also froze my system hard. After rebooting (kernel was from Nov 26 or 27) fsck could not check my one dirty UFS2 partition. Had to newfs and mtree to recreate /var. No big deal, and I saved an image of it beforehand. After rebooting, there was... NOTHING. GRUB errored out and wouldn't boot. Nothing could see my partitions. After a minimal 4.7-R install (DP2 disklabel whined about offsets and some other STRANGE error messages, so I went with 4.7) on a small fat32 partition, I discovered that the disklabel was empty. Had to edit it by hand... Booted up fine, made a backup, rebooted, and nothing. Not only was there NOTHING, but the disklabel on the new 4.7 install had vanished as well. This time the disklabel had to be recreated with -w -r AND the boot blocks had to be reinstalled. I've seen one post similar to this, but not much else. I think maybe the UFS2 problem had to do with Kirk's recent changes, but the disklabel issue... I'm wary to reboot my machine! What in the hell could be causing this? I'm tempted to point the finger at GEOM, but hate to say anything like that. WNM -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with ntpdate
Daniel O'Connor wrote: On Fri, 2002-11-29 at 05:57, Daniel C. Sobral wrote: >ntpdate_flags="-s -b 200.220.255.229": > >Nov 28 15:15:38 dcs ntpdate[259]: no server suitable for synchronization >found >Nov 28 15:15:39 dcs ntpd[377]: ntpd 4.1.1b-a Thu Nov 28 11:09:29 BRST >2002 (1) >Nov 28 15:15:39 dcs ntpd[377]: kernel time discipline status 2040 >Nov 28 15:15:50 dcs ntpd[377]: sendto(200.220.255.229): No route to host > >That is, the extra time taken NOT resolving clock.tcoip.com.br was, >apparently, enough for something in the IP stack to go up. > >This looks, after all, like a more serious bug than I first assumed. You could try running FreeBSD so that it thinks the CMOS clock is local time the same as windows does.. Have you tried ntpdate debugging? ntptrace can be handy too.. (Although if it works after boot then probably not) I see the 'no route to host message' given by ntpd - perhaps some routes aren't set when ntpdate runs? Not a FreeBSD problem, after all. I checked the interfaces, checked the routes, and then I finally got a tcpdump running. Seems like for some switching reason the arp who-has packets are taking too long to be properly propagated. Now, I seem to recall there were some tcp delay changes between 4.x and 5.x, so now 5.x is much faster. Apparently, so much so it gives up before I get an arp is-at, whereas 4.x would wait enough for the link level protocolo to get it's act together. Or maybe 4.x tried to use something before running ntpdate, so that the arp table was ok by the time it got to ntpdate. Or maybe both. I'll try using the -g option on ntpd like someone else suggested. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Ankh if you love Isis. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sparc64 tinderbox failure
Fri Nov 29 09:15:00 GMT 2002 Running test variables PASS: Test variables detected no regression, output matches. Running test targets PASS: Test targets detected no regression. Running test sysvmatch PASS: Test sysvmatch detected no regression. Running test lhs_expn PASS: Test lhs_expn detected no regression. Running test notdef PASS: Test notdef detected no regression. Running test modifiers PASS: Test modifiers detected no regression. Running test funny_targets FAIL: Test failed: regression detected. See above. *** Error code 1 Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. *** Error code 1 Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. -- Upgrading the installed make -- install: /usr/bin/make: Text file busy *** Error code 71 Stop in /tinderbox/sparc64/src/usr.bin/make. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trivial patch: fdisk doesn't recognize my partitions
Bruce Evans wrote: > On Thu, 28 Nov 2002, Poul-Henning Kamp wrote: > > In message <[EMAIL PROTECTED]>, Riccardo Torrini write > > >As far as I know it use an EXOR 0x10 to hide/unhide but fdisk doesn't > > >recognize 0x0B/0x0C fat32 when hidden (0x1B/0x1C) > > But as I said, this is rather marginal and I really don't feel > > it should go in unless this xor-0x10 convention is more widespread. > > "Hiding" partitions is a bug IMO, so it should have negative support. > This convention would break many OS's conventions. > E.g., NextSTEP | 0x10 gives BSDI. If you think about it, if there is no one to claim it, it's reasonable to treat it as raw disk space, and try to find a partition on it. Really, there's no reason to care about partition type at all, since the contents will have the right magic numbers and the right data layout for a FATFS: you don't really care. That's really only meaningful if you decide the "hiding" that "magic.com" does doesn't apply to you; if it applies to you, then, in fact, it's a good thing that it's not recognized: the "magic.com" program has successfuly accomplished what it was written to accomplish -- so it's a non-problem. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sparc64 tinderbox failure
On Fri, Nov 29, 2002 at 03:22:29AM +, Mike Barcroft wrote: > Fri Nov 29 03:15:00 GMT 2002 > U lib/libpam/modules/pam_ksu/pam_ksu.c > U release/doc/en_US.ISO8859-1/early-adopter/article.sgml > Running test variables > PASS: Test variables detected no regression, output matches. > Running test targets > PASS: Test targets detected no regression. > Running test sysvmatch > PASS: Test sysvmatch detected no regression. > Running test lhs_expn > PASS: Test lhs_expn detected no regression. > Running test notdef > PASS: Test notdef detected no regression. > Running test modifiers > PASS: Test modifiers detected no regression. > Running test funny_targets > FAIL: Test failed: regression detected. See above. > *** Error code 1 > > Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. > *** Error code 1 > > Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. > > -- > Upgrading the installed make > -- > install: /usr/bin/make: Text file busy > *** Error code 71 > Are you using NFS here? Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg47732/pgp0.pgp Description: PGP signature
